Follow-up Comment #17, bug #58206 (project groff):
[comment #15 comment #15:]
> I misread the output--the problem file from the original submission indeed
contains UTF-16LE, not surprising at all given all the Windows systems in the
world.
Embarrassingly, I had it right the first time. A null (zero) byte followed by
a byte at a higher address with its eighth bit clear, representing a Unicode
basic Latin character, is definitely big-endian.
I'll have to send some of whatever I was munching on to Michael Pollan.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?58206>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
