Ralph Corderoy <ralph(_at_)inputplus(_dot_)co(_dot_)uk> writes:
Hi Ken,
So ... what would that mean, exactly? Ignore the locale setting
and always output UTF-8?
Well, yes, the code would be writing UTF-8, with the knowledge of
how many cells have been occupied, e.g. one for the combining `a⃞',
but it could complain about the non-UTF-8 locale setting, or try and
set up `fire and forget' converter on open and opening files if it
was easy enough to be worth the bother.
Help me out here, because I'm trying to translate your concepts into
actual code and I'm having some problems seeing how it would work.
Geez, how much hand-waving do you want a guy to do? :-)
Assuming we don't bring in a library like ICU,
GNU's libunistring might be an alternative to ICU.
http://www.gnu.org/software/libunistring/
This small lib could be useful as well, expat-licensed and could even
be vendored:
https://github.com/JuliaLang/utf8proc
--
Christian Neukirchen <chneukirchen(_at_)gmail(_dot_)com>
http://chneukirchen.org
_______________________________________________
Nmh-workers mailing list
Nmh-workers(_at_)nongnu(_dot_)org
https://lists.nongnu.org/mailman/listinfo/nmh-workers