Re: [Groff] mom : unicode in .INCLUDE'd files

[Ralph Corderoy]

Hi Keith,

> The simple reality is that, if we wish to preserve groff's current
> utility on MS-Windows, insistence on UTF-8 only as an input encoding
> is not a viable option.

I understand the Windows API has moved to UTF-16, but does that mean
text file on disk are stored in that format?  I wouldn't have thought so
else we'd hear of more problems with these files being unreadable by
many programs that expect one byte per rune, or UTF-8.

If groff read its input a byte at a time from a "binary" file, parsing
the multi-byte sequences that can occur in UTF-8, would that not work on
Windows for its plain text files?

-- 
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy