At 09:20 02/02/2001 +0000, Edmund GRIMLEY EVANS wrote: >Inconsistent encoding of file names is a problem. There seem to be two >solutions: > >1. Introduce an as yet undesigned but probably complex and insecure >system by which file names are automatically converted to the >appropriate encoding. note: this is ALREADY IMPLEMENTED IN LINUX for the FAT filesystem. see kernel docs - Documentation/Configure.help, under "NLS". If it has to be done - it has to be done in the kernel, at filesystem level. -- Harald Tveit Alvestrand, [EMAIL PROTECTED] +47 41 44 29 94 Personal email: [EMAIL PROTECTED] - Linux-UTF8: i18n of Linux on all levels Archive: http://mail.nl.linux.org/lists/
- Re: filename encoding (was: ISO-2022) Edmund GRIMLEY EVANS
- Re: filename encoding (was: ISO-2022) Tomohiro KUBOTA
- Re: filename encoding (was: ISO-2022) Marcin 'Qrczak' Kowalczyk
- Re: filename encoding (was: ISO-2022) Tomohiro KUBOTA
- Re: filename encoding (was: ISO-2022) Ulrich Drepper
- Re: filename encoding (was: ISO-2022) David Starner
- Re: filename encoding (was: ISO-2022) Tomohiro KUBOTA
- Re: filename encoding (was: ISO-2022) David Starner
- Re: filename encoding (was: ISO-2022) Henry Spencer
- Re: filename encoding (was: ISO-2022) Edmund GRIMLEY EVANS
- Re: filename encoding (was: ISO-2022) Harald Alvestrand
- Re: filename encoding (was: ISO-2022) Edmund GRIMLEY EVANS
- Re: filename encoding (was: ISO-2022) David Starner
- ISO-2022 (Re: filename encoding (was: ISO-2022)) Tomohiro KUBOTA
- Re: ISO-2022 Markus Kuhn
- Re: ISO-2022 Tomohiro KUBOTA
- Re: ISO-2022 Bruno Haible
- XTerm and ISO-2022 Tomohiro KUBOTA
- Re: XTerm and ISO-2022 Robert Brady
- Re: XTerm and ISO-2022 Tomohiro KUBOTA
- Re: XTerm and ISO-2022 Robert Brady
