Follow-up Comment #8, bug #40720 (group groff): [comment #7 comment #7:] > Unless I'm misunderstanding you and Ingo,
Possibly, because the point made in this paragraph seems to have little
bearing on our proposal.
> at the level GNU _troff_ needs to work on characters, I think
> it expects singleton items
GNU troff can already, and has been able to for years, handle text full of
"characters" spelled like \[u1F913]. Whatever internal storage it uses is
already up to this task.
What it can't do is read UTF-8 input containing the character 🤓. It needs
preconv to convert this into \[u1F913].
But that's only an _input_ problem. Once troff is past the input stage, if it
continues to store the character the same way it has stored \[u1F913] for
years, much of the code base can remain untouched. Only the part of troff
that reads input needs to change.
> to prevent the Savannah web UI from mistaking my asterisks for
> emphasis markup
It's clunky, but savannah's +nomarkup+ tag lets you char * char * char * all
day long.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?40720>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
