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

Follow-up Comment #12, bug #59397 (group groff): [comment #11 comment #11:] > One step remains for this: Handled. [http://git.savannah.gnu.org/cgit/groff.git/commit/?id=56e793e73 Commit 56e793e73]. ___ Reply to this item at:

[bug #50770] .PSPIC macro at bottom of page causes unwarranted page break

Update of bug #50770 (group groff): Status: Confirmed => Need Info Assigned to:None => barx ___ Follow-up Comment #12: [comment #11 comment #

[bug #62826] [PATCH] [tmac] clearly comment bug #44714 workaround in andoc.tmac

Update of bug #62826 (group groff): Status:None => In Progress Assigned to:None => gbranden ___ Reply to this item at:

[bug #65073] "cppcheck" reports errors, warnings, and notes

Update of bug #65073 (group groff): Category:Core => General Summary: warnings and errors reported by "cppcheck" => "cppcheck" reports errors, warnings, and notes ___ Foll

[bug #65052] [troff] `cf` behavioral anomalies

Update of bug #65052 (group groff): Item Group:None => Documentation ___ Follow-up Comment #3: Deri's points in comment #1 are well-taken. This is probably just me misunderstanding things--but t

[bug #42870] [troff] revise hyphenation code management

Follow-up Comment #21, bug #42870 (group groff): So, as I read this, the upshot is that .hw has always (for some value of "always") accepted special character escapes. When using them seemed to have no effect (as in comment #16, clarified in comment #17), it's because the appropriate .hcodes had

[bug #50770] .PSPIC macro at bottom of page causes unwarranted page break

Follow-up Comment #13, bug #50770 (group groff): I understood the purpose of comment #10 as explaining the mechanism of the behavior, which to me was a less interesting question than whether the behavior should be changed, so I didn't pay it much mind in writing comment #11. But as I look at comm

[bug #50770] .PSPIC macro at bottom of page causes unwarranted page break

Follow-up Comment #14, bug #50770 (group groff): [comment #12 comment #12:] > and/or a documentation change cautioning the PSPIC user that the > macro doesn't handle "keeping" the image together with a > subsequent caption for them. I guess I can't raise any objection to such a caution, but in ge

[bug #50770] .PSPIC macro at bottom of page causes unwarranted page break

Follow-up Comment #15, bug #50770 (group groff): [comment #14 comment #14:] > [comment #12 comment #12:] > > and/or a documentation change cautioning the PSPIC user that the > > macro doesn't handle "keeping" the image together with a > > subsequent caption for them. > > I guess I can't raise any