[bug #63176] [me] After column-count changes, -me might place running text on page below footnote

Follow-up Comment #10, bug #63176 (group groff): Yes, I waited nearly two years to respond to your last comment so as to facilitate that exact connection. My crystal ball is that accurate. Now, if I can only get it to show me lottery drawings rather than the contents of your groff-hacking screen

[bug #66040] [troff] no longer warns about unrecognized .hcode input

Follow-up Comment #13, bug #66040 (group groff): [comment #6 comment #6:] > The part I'm griefed about is "(not a special character escape sequence)". > > A "hyphenation code" (an argument to the `hcode` request): > > 1. is always permitted as the destination (first of a pair), as in > > .hco

[bug #66040] [troff] no longer warns about unrecognized .hcode input

Follow-up Comment #14, bug #66040 (group groff): [comment #9 comment #9:] > > why would it be a bug that the special character is > > unrecognized only on its second appearance? > > If you mean "as the second member of a pair with itself", I > have an answer. No, sorry for being unclear: I didn'

[bug #65936] [grohtml] crops PostScript of _tbl_ tables incorrectly

Follow-up Comment #11, bug #65936 (group groff): [comment #10 comment #10:] > [comment #8 comment #8:] > > (See bug #65960 and bug #65960 for details.) > > Those are both the same bug number. I'm afraid that my brain purged its cache of the relevant bug numbers immediately upon making that notat

[bug #66051] [troff] permit special characters to have bespoke hyphenation codes

URL: Summary: [troff] permit special characters to have bespoke hyphenation codes Group: GNU roff Submitter: gbranden Submitted: Wed 31 Jul 2024 09:08:38 PM UTC Category: Core

[bug #66051] [troff] permit special characters to have bespoke hyphenation codes

Follow-up Comment #1, bug #66051 (group groff): Added Dave to CC list; Dave, please comment if I'm making sense, and especially if I'm not. ___ Reply to this item at: _

[bug #66051] [troff] permit special characters to have bespoke hyphenation codes

Follow-up Comment #2, bug #66051 (group groff): It makes total sense and also seems a duplicate of bug #42870. I guess I'm not seeing what's "more modest" about that one. If anything, the way it's worded, _this_ one seems more modest, as it's asking for support of only special characters, and on

[bug #66051] [troff] permit special characters to have bespoke hyphenation codes

Follow-up Comment #3, bug #66051 (group groff): [comment #2 comment #2:] > #42870 (per its original submission wording) ...wording that, by the way, comes originally from Werner: http://lists.gnu.org/r/groff/2014-07/msg00127.html ___ Repl

[bug #66051] [troff] permit special characters to have bespoke hyphenation codes

Follow-up Comment #4, bug #66051 (group groff): [comment #2 comment #2:] > It makes total sense and also seems a duplicate of bug #42870. I guess I'm not seeing what's "more modest" about that one. The fix I have in mind for bug #42870 will address (I have it pending, with passing regression tes

[bug #66051] [troff] permit special characters to have bespoke hyphenation codes

Follow-up Comment #5, bug #66051 (group groff): Maybe bug #42870's future is to become a bug that depends on more recent ones. And in that sense perhaps this one really is "more modest". ___ Reply to this item at:

[bug #66051] [troff] permit special characters to have bespoke hyphenation codes

Follow-up Comment #6, bug #66051 (group groff): [comment #4 comment #4:] > Whereas *this* one will make possible: > > .hcode \[ss] \[ss] > > The fix I have in mind for bug #42780 does not. s/bug #42780/bug #42870/ If ultimately both are to be fixed, I suppose it's academic how the individual t

[bug #59397] Assign default .hcode values to alphabetic characters in groff's default character set

Follow-up Comment #5, bug #59397 (group groff): [comment #3 comment #3:] > I think it might be an open question as to whether letters > from outside the basic Latin alphabet _should_ necessarily be > hyphenated like their basic Latin "base characters". There's a little fuzz in any automated hyphe

[bug #59397] [troff] want English hyphenation codes for Latin-1 Supplement characters

Update of bug #59397 (group groff): Status: Need Info => None Summary: Assign default .hcode values to alphabetic characters in groff's default character set => [troff] want English hyphenation codes for Latin-1 Supplement charact

[bug #59397] Assign default .hcode values to alphabetic characters in groff's default character set

Update of bug #59397 (group groff): Status:None => Need Info Summary: [troff] want English hyphenation codes for Latin-1 Supplement characters => Assign default .hcode values to alphabetic characters in groff's default character

[bug #59397] [troff] want English hyphenation codes for Latin-1 Supplement characters

Update of bug #59397 (group groff): Status: Need Info => None Summary: Assign default .hcode values to alphabetic characters in groff's default character set => [troff] want English hyphenation codes for Latin-1 Supplement charact