Eric Blake wrote:
> The correct workaround is indeed to specify a locale with specific charset
> encodings, rather than relying on plain "C"
Yep, I'm testing a patch to that effect.
> (hopefully cygwin will support "C.ASCII", if it does not already).
Yep, it does.
> As far as I know, the hole is intentional. But if others would like me to, I
> am willing to pursue the action of raising a defect against the POSIX
> standard,
> requesting that the next version of POSIX consider including a standardized
> name for a locale with guaranteed single-byte encoding.
I think that would be useful, albeit with the drawback that it would make it
easier for people to carry on putting off dealing with i18n indefinitely.
Surprised that POSIX doesn't specify "C.ASCII" as exactly that already; I
think it would well make sense to put it in the standard.
cheers,
DaveK
