URL: <https://savannah.gnu.org/bugs/?68721>
Summary: doc/groff.texi.in: reëncode in UTF-8
Group: GNU roff
Submitter: gbranden
Submitted: Mon 28 Sep 2026 01:53:52 AM UTC
Category: Core
Severity: 3 - Normal
Item Group: Documentation
Status: Confirmed
Privacy: Public
Assigned to: gbranden
Open/Closed: Open
Discussion Lock: Unlocked
Planned Release: None
_______________________________________________________
Follow-up Comments:
-------------------------------------------------------
Date: Mon 28 Sep 2026 01:53:52 AM UTC By: G. Branden Robinson <gbranden>
...from ISO 8859-1.
Reportedly, this will give _makeinfo_(1) the nudge it needs to write UTF-8
encoded Info files, which should solve a horrendous readability problem.
To that end, not all input lines are text lines containing words to
be formatted. Control lines start with a dot ('.') or an apostrophe
(''') as the first character, and are followed by a request or macro
name that tells a macro package (or GNU 'troff' directly) how to format
the text.
...
All of these requests cause a break, starting a new line. If you
invoke them with the apostrophe ''', the no-break control character, the
(initial) break they normally perform is suppressed. ''br' does
nothing.
...
-- Register: \n[TC-MARGIN]
Defines the width of the field in which page numbers are set in a
table of contents entry; the right margin thus moves inboard by
this amount. This is a GNU extension.
Effective: next 'PX' call.
Default: '\w'000''
Other occurrences are merely annoying, but they are **numerous**.
AT&T 'troff''s 'yr' register has a Y2K bug; GNU 'troff' simulates the
bug for consistency due to its widespread usage, but provides an
alternative register implementing AT&T's _documented_ semantics; recall
*note Host System Service Access::.
...
It's time to remove, if we can, this source of endless amusement for
*roff-haters, facilitated by Texinfo's sabotage of our manual's
comprehensibility.
("If you didn't want it to look like that, why did you mark it up with the
semantically correct `@` tag?")
Try it and see if it works.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?68721>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
