On 2002-02-20 00:12 Markus Kuhn wrote: > I just spottet in section 1.1.3 of RFC 3030 (NFS version 4 Protocol) > the following requirement: "file and directory names are encoded with > UTF-8".
That’s incredibly good news. At last there is any development in the mess of 8-bit file names. This is a topic which should be adressed actively, the question is on what level translation should be done. Haven’t follwed this dicussion lately, but how is the future of 8-bit filenames under Linux? At the moment I have to enter UTF-8 sequences manually when I want 8-bit filenames. I once avoided using that kind of stuff in file names, but now that UTF-8 has arrived, I’m tired of waiting. I’ll admit it has got me into some trouble. Especially when moving a directory tree over to cfs (cryptfs) on Debian I had some files with Norwegian-specific characters (æøåÆØÅ) in it. The files got moved to the encrypted file system, but I’m not able to read them because of Debian bug #44516. Well. So: Do you think it’s long time until we can enter 8-bits characters in programs when saving files, and it will be stored as UTF-8 in the file system? Or is this a unwanted feature? Thinking about the ability to read file names with invalid UTF-8 sequences. I know this is a topic for endless discussions, but what is the status on this at the moment? Mvh Øyvind +===================================================================+ | OpenPGP: 0xAD19826C 2000-01-24 Øyvind A. Holm <[EMAIL PROTECTED]> | | Fingerprint: EAE5 DCA0 0626 5DAA 72F8 0435 2E2B E476 AD19 826C | +=========== 2 + 2 ≈ 5 for extremely large values of 2. ============+ -- Linux-UTF8: i18n of Linux on all levels Archive: http://mail.nl.linux.org/linux-utf8/
