-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
According to wollman+austin-group@lcs.mit.edu on 10/30/2009 3:02 PM:
> <<On Fri, 30 Oct 2009 14:58:32 -0600, Eric Blake <ebb9@byu.net> said:
>
>> That's a restriction that I think we should be very reluctant to make. In
>> other words, there has to be a good reason why we are willing to require
>> the POSIX locale to require a unibyte charset. And I don't think we have
>> come up with one yet.
>
> Turn it around: of what value is the POSIX locale without such a
> requirement?
The POSIX locale is already specified to be portable in character contexts
only when you use just the portable characters. Both unibyte and UTF-8
meet the following criteria: 1. all portable characters are single bytes,
2. no characters outside the portable characters can be confused in whole
or in part (well, the in part only applies to multi-byte charsets) with
portable characters. So for all intents and purposes, you should not need
to care whether the POSIX locale is single- or multi-byte encoded - a
portable app can't use characters outside the portable set in the first
place. In fact, an EBCDIC charset should be just as compliant as the
underlying charset of the POSIX locale as the more traditional ASCII or UTF-8.
- --
Don't work too hard, make some time for fun as well!
Eric Blake ebb9@byu.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkrrYTMACgkQ84KuGfSFAYBCfQCcDXpipFotHMR5YelDQyQsV2rJ
OEwAn3lr/ujqx5Gfnk1zBEz0G3vVyWWK
=674u
-----END PGP SIGNATURE-----
|