[bug #55154] .tr has undocumented and inconsistent space-character restrictions

Follow-up Comment #8, bug #55154 (project groff): Everything else I wanted to say (here and in bug #64337) I ended up talking myself out of. All I have left are two minor comments on the documentation update. [comment #6 comment #6:] > > This feature replaces the odd-parity tr mapping trick "r

[bug #55799] -a output does not heed .char definitions

Follow-up Comment #1, bug #55799 (project groff): Heirloom troff has also implemented the .char request (recognized when using -x2 or higher), and its -a output works as expected. $ printf ".char a z\nplan\n" | heirloom-troff -a -x2 plzn $ printf ".char a z\nplan\n" | groff -a plan

[bug #64342] [afmtodit] Preserve AFM file's ItalicAngle value in font description file

URL: Summary: [afmtodit] Preserve AFM file's ItalicAngle value in font description file Group: GNU roff Submitter: barx Submitted: Sat 24 Jun 2023 02:45:53 PM CDT Category: Ut

[bug #64342] [afmtodit] Preserve AFM file's ItalicAngle value in font description file

Follow-up Comment #1, bug #64342 (project groff): [comment #0 original submission:] > the AFM file's ItalicAngle value should still be placed in the file, > either in a comment or as a parameter to a new optional directive. The intro of the Font Description File Format section of the Texinfo manu

[bug #57506] Suspicious "slant" values in devps/TI, devlbp/HI, devlbp/HBI

Follow-up Comment #9, bug #57506 (project groff): [comment #7 comment #7:] > I think it's safe to say any font description file that has > more than one "slant" line is in error. ...unless it isn't. [http://savannah.gnu.org/bugs/?64342#comment1 Comment #1 of bug #64342] suggests a possible inten

[bug #55060] [me] behavior of .ll does not match documentation

Follow-up Comment #13, bug #55060 (project groff): For the archaeologists, this bug was first reported in http://lists.gnu.org/r/bug-groff/2011-05/msg3.html ___ Reply to this item at: