-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, Jan 30, 2017 at 10:46:26PM +0200, Marko Rauhamaa wrote:
[...] > You are jumping the gun. Linux won't be there for a long time if ever. > Nothing prevents a pathname, or a command-line argument, or an > environment variable, or the standard input from containing illegal > UTF-8. To put more emphasis on this point: as things stand, you won't be able to avoid having paths with illegal UTF-8. Consider mounting a file system with UTF-8 file names over one containing Latin-1 file names. Then even if both are consistent in themselves (a far stretch, because there might be multiple apps under multiple locales creating and naming files), the combined path might be bad UTF-8 As long as the OS keeps out of this business I guess the application will need a "layer" from which to look at paths (and env variables and argv and all that) as mere byte sequences, before any interpretation takes place. > (Also note that even Windows allows pathnames with illegal Unicode in > them if I'm not mistaken.) This is so Microsoft: the file name character set in the file system is Unicode... except when it isn't :-) regards - -- t -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAliQgRgACgkQBcgs9XrR2kaOFwCeLo5oUgkTM9NPWo2aK+1SRObY 3yoAniTL3HgxPqh1mdXMx774fmohmnYb =YuFv -----END PGP SIGNATURE-----
