[bug #65710] [preconv] require disambiguation of U+00A0 on input

Follow-up Comment #1, bug #65710 (group groff): [comment #0 original submission:] > an input U+00A0...: is it a fixed-width non-breakable space, or a > variable-width non-breakable space? Unicode does not distinguish. Unicode intentionally provides some latitude to rendering engines to make the

[bug #64155] [troff] specifying -fZD on command line generates warnings

Follow-up Comment #39, bug #64155 (group groff): Self-followup: [comment #37 comment #37:] > in a way back compatible to almost any older troff. Obviously, this specific example is not AT&T-portable due to the long names, but the logic can be written portably. _

[bug #65716] We don't seem to be using the "latest" glyphlist.txt to generate the tables for afmtodit.

URL: Summary: We don't seem to be using the "latest" glyphlist.txt to generate the tables for afmtodit. Group: GNU roff Submitter: deri Submitted: Wed 08 May 2024 11:47:44 PM UTC

[bug #65693] exceptions to NBSP statement in groff_char(7) should be documented

Follow-up Comment #2, bug #65693 (group groff): Given the arguments in favor of the U+00A0 to \~ mapping presented in bug #58962 and bug #65710, I now wonder if groff might be better off doing something heretical like ignoring the u00A0 glyph in a font and applying its own mapping to that characte