Follow-up Comment #4, bug #67735 (group groff): At 2025-11-25T16:44:55-0500, Collin Funk wrote: > Follow-up Comment #3, bug #67735 (group groff): > > +1, unsigned char or uint8_t is best if you just want to represent > bytes of data.
That's not what we want. We want to read input bytes and encode them into a much more semantically rich data type. https://cgit.git.savannah.gnu.org/cgit/groff.git/tree/src/roff/troff/input.h?h=1.23.0 https://cgit.git.savannah.gnu.org/cgit/groff.git/tree/src/roff/troff/token.h?h=1.23.0 A factor that clarifies some things and obfuscates others is that sometimes (but less often than people suppose; see _groff_char_(7)) these token represent Unicode Basic Latin characters that happen to have identical code point assignments in ISO 10646 and ISO 646. _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?67735> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
signature.asc
Description: PGP signature
