![]() | ||||||||||
Messages in this thread |
#include <hallo.h> * John Bradford [Thu, Feb 12 2004, 07:08:06PM]: > Well, as long as every userspace implementation gets it correct, we'll > be OK. Personally, I doubt they all will, especially those that > convert from legacy encodings to Unicode, although quite possibly the > above scenario with combining characters is not likely to happen for > filenames. Or is it? What about copying a file from a filesystem > with a UTF-8 encoding to a filesystem with a legacy encoding, and then > back again? I always wondered why there is no "iocharset" option for unixoid filesystems. IMO there could be an easy migration path for existing installations to UTF-8: - convert all filenames to UTF-8 (or any other Unicode encoding) - mount the FS with "iocharset=UTF-8,charset=latin1" (for current Latin1 users). Users can continue to use their latin1 names while they are stored in Unicode on the disk (this is what currently happens with VFAT, a very nice solution IMHO) - when enough applications are ready for multibyte encodings, remove the charset/iocharset workaround and make people use .UTF-8 locales Though, the ultimate solution for the steps 2. and 3. would be the Microsoft-like way: - convert the filenames in libc (from $locale to UTF-8), depending on which locale the user has set This sounds like cheating but would allow to be most flexible and most compatible to encoding-ignoring applications. Eduard. -- Wir sind nichts; was wir suchen ist alles. -- Johann Christian Friedrich Hölderlin - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | |||||||||
| Last update: 2005-03-22 13:00 [from the cache] ©2003-2008 | ||||||||||