[bug #58718] font file should allow kern pairs with space as first element

Follow-up Comment #1, bug #58718 (project groff): Bug #64519 observes that a hyphen likewise cannot be the first element of a kern pair. Arguably these are two examples of the same limitation. (There may be others; I did not test every character.) But I feel #64519 is the easier to solve becaus

[bug #64018] [man, mdoc] decide on a common base paragraph indentation

Follow-up Comment #21, bug #64018 (project groff): Regarding editing manual page source code in such a way as to avoid particularly ugly line breaks in standard-width 80 column terminal windows: [comment #12 comment #12:] > Possibly, _mdoc_(7) page authors knew this and carefully edited the ones

[bug #58718] font file should allow kern pairs with space as first element

Follow-up Comment #2, bug #58718 (project groff): Further, the width of ordinary spaces is under the control of the user (via .ss), and spaces are stretchable in fully justified text. Thus, kerning them raises an additional question that other kerned characters need not address: is the amount of

[bug #64018] [man, mdoc] decide on a common base paragraph indentation

Follow-up Comment #22, bug #64018 (project groff): [comment #15 comment #15:] > > > > We cannot, obviously, have three-letter requests. > > > Nope. Like I said, there's room for `Cq`, `Co`, and `Cc`. > > > > Indeed, I see only Co used grepping through all tmacs: > > tmac.doc.old has it as macro

[bug #64526] Retool example of using newlines as escape delimiters

URL: Summary: Retool example of using newlines as escape delimiters Group: GNU roff Submitter: barx Submitted: Mon 07 Aug 2023 01:34:40 PM CDT Category: Core S

[bug #63028] document nroff \o limitations in modern terminal emulators

Follow-up Comment #4, bug #63028 (project groff): The comment #3 side issue is now bug #64526. ___ Reply to this item at: ___ Message sent via Savannah

[bug #64018] [man, mdoc] decide on a common base paragraph indentation

Follow-up Comment #23, bug #64018 (project groff): Thanks for the history! I also don’t see it used anywhere really. >By the way, do we still have that ancient README file in the groff git tree? >I think that OpenBSD still has it lying around in the source tree in >/usr/src/share/tmac/mdoc/README

[bug #64509] [bjarnigroff] new tests are not reproducible, e.g. tmac/tests/an_MR-works.sh

Update of bug #64509 (project groff): Status: Need Info => Invalid Open/Closed:Open => Closed ___ Follow-up Comment #2: [https://lists.gnu.or