Hi Rich ! >My statement was imprecise; of course to support users still >stuck on legacy locales, nl_langinfo(CODESET) should be >consulted.
How do you determine the correct code set of a foreign file system on an external drive? How can you tell if all systems which accessed this drive has handled translations in the correct way? >> .... and not only unzip may produce such results. Think of >> using an USB stick at an Windows machine, then carry that over >> to an Linux machine. > >The filenames are stored in UCS-2. No problem. UCS-2 with different code page translations from an 8 bit charset. Translations which leave name mapping in inconsistent state when further translations occur. >If you mount it incorrectly, then this is user error. Correct, all those trouble arrives due to anybody having an incorrect setup. This will ripple trough and may produce trouble on other ends. >All programs are not affected. Only programs which read >filenames as byte strings from foreign sources (such as the >directory table of a zip file) are affected. ... but how do you know the code page the zip archive uses. How do you know you need to do translations? I'm unsure if the archiv contains this information, so it needs to be provided by a much more error prone user. -- Harald _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
