Hi Brian, At 2023-03-16T19:39:27-0600, Brian Inglis wrote: > Output of man pages with lengthy synopses from grohtml do not disable > adjustment and hyphenation as for tty, breaking long options between > the hyphens and anywhere else available. [snip]
I cannot reproduce this problem with groff Git HEAD, viewing the generated HTML with Firefox and lynx(1).[1] My conjecture is that my heavy refactoring of groff man(7) since 1.22.4 fixed your issue. I am attaching the input I used (it is the same as yours, not changed in any way), and output from groff compiled from the tip of the 'branden-post-1.23.0' Git branch, but my guess is any snapshot of groff Git going back to about 9 January would work the same. (On 8 January I fixed a bug in hyphenation inside synopses, which might sound promising, but it was a regression _from_ 1.22.4 to the master branch from nearly a year before. Maybe the 8 January commit collaterally fixed the problem you're reporting.) https://git.savannah.gnu.org/cgit/groff.git/commit/?id=82db4baa23d5f41671197ed75613609a0553d42b So...good news, maybe? Also, are you in contact with the help2man people? We should try to wean them off of the 'OP' macro. .OP option-name [option-argument] Indicate an optional command parameter called option-name, which is set in bold. If the option takes an argument, specify option-argument using a noun, abbreviation, or hyphenated noun phrase. If present, option-argument is preceded by a space and set in italics. Square brackets in roman surround both arguments. Use of this quasi-semantic macro, an extension originating in Documenter's Workbench troff, is deprecated. It cannot easily be used to annotate options that take optional arguments or options whose arguments have internal structure (such as a mixture of literal and variable components). One could work around these limitations with font selection escape sequences, but it is preferable to use font style alternation macros, which afford greater flexibility. Regards, Branden [1] w3m does ugly things with the output, breaking after opening brackets in input like the following, ironically enough. [<b>--no-line-breaks</b>] I assume this is a w3m bug?
inglis.man
Description: Unix manual page
signature.asc
Description: PGP signature
