Follow-up Comment #14, bug #67252 (group groff): [comment #13 comment #13:] > Separate issue #3: _groff_char_(7) should be revised to present > glyph tables that don't overset when semantic fallbacks are used.
Yes, that summarizes 3 of the 4 possible solutions presented in comment #9.
> If that's all that remains of this ticket, I am inclined to
> close it as "Rejected".
And that's the 4th.
The "best" of the 4 solutions seems to be "The problem characters could be
always omitted from output encodings that don't support them." This is not
something I'd recommend in general, but groff_char(7) in particular loses no
information by omitting the characters: semantic fallbacks in this table
merely repeat information that appears in another column of the table.
But the reason "best" is in quotes above is that there's no existing mechanism
to implement this: nroff unconditionally loads tty-char.tmac, which defines
the semantic fallbacks for the ascii and latin1 devices.
Even supposing that bug #62814, against Ingo's counsel, is resolved in a way
that lets the user easily opt in to or out of semantic fallbacks, that may not
address the groff_char(7) situation, where it is the document author who's in
the best position to determine that missing characters are better than
semantic fallbacks for this page.
A ham-fisted but effective way to make this work would be to have
groff_char.7.man unconditionally .rchar the semantic fallbacks, or redefine
them all to something (like "-") that gives the user an indication of a
missing character while not being any wider than a single character.
> Is the foregoing a fair redrawing of the multifarious issues
> arising from comment #0?
I believe so, but I'm not the author of comment #0.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?67252>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
