Follow-up Comment #5, bug #65654 (group groff):
Correcting my earlier statement:
[comment #2 comment #2:]
> 0xA0 appears to refer to the Latin-1 character NO-BREAK SPACE
> (Unicode U+00A0)--but there is no reason to run preconv if the
> file is in Latin-1 encoding,
My Latin-1 (ISO 8859-1) blinders were on: the byte 0xA0 is also the no-break
space in encodings ISO 8859-2, ISO 8859-3, ISO 8859-4, etc., any of which
would require preconv.
> Nonetheless, his point remains:
This makes the preceding (mis)statement mostly moot, but I wanted to correct
the record.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?65654>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
