At 2025-02-23T17:23:35+0100, Benno Schulenberg wrote: > > Regarding the hyphenation problem, the lump in the carpet moves > > after groff 1.22.4. Because HTML output now produces − > > entities rather than hyphens from *roff minus special characters > > (`\-`), [...] > > Ouch! I don't like the look of them on the HTML page: they are > "enormous", looking like ndashes.
The _appearance_ of rendered glyphs in HTML rendered by groff is not under groff's control. Our style markup (such as it is) doesn't specify which (Web) fonts to use, so you get whatever your browser elects (or is configured) to supply. > And what's worse: when one > copy-pastes such an option (−−breaklonglines, for example) to > a terminal, nano thinks it is a file name. Aarrr! :( Yes, that's a problem just as it is on UTF-8 terminal devices. groff's man(7) and mdoc(7) packages have the following logic. .\" === Define/remap characters. === . .\" For UTF-8, map the minus sign to the hyphen-minus to facilitate .\" copy and paste of code examples, file names, and URLs embedding it. .if '\*[.T]'utf8' \ . char \- \N'45' Sounds like it would be a good idea to do this for the 'html' device as well. This is easily done and can be implemented for groff 1.24. (I note in passing that the 'pdf' device doesn't need such a provision because its "CMap" feature handles the problem for us.) I appreciate your giving grohtml some exercise. Few of its users communicate with us, possibly because their population is small; that is one reason I have not given it a lot of development attention. > > ...instead I can get... > > > > yadda yadda yadda - > > -restricted > > > > ...which I'm not sure is an improvement. > > :) No, that's not an improvement. The right thing to do is to respect hyphenation suppression for the entire word. Hence the (first) grohtml I need to file. > > I think I have enough information to file a Savannah ticket, though > > I can't promise I'll get to this specific problem before the groff > > 1.24.0 release, which is weeks overdue. Would you like to be CCed > > by Savannah on the ticket traffic? > > Yes, please. Cool. Sounds like I have _two_ new Savannah tickets to file now. :-O Regards, Branden
signature.asc
Description: PGP signature
