I don't think that's a problem for a fresh install. Are there any tools for converting existing file systems from one encoding to another? That's a non-trivial problem. Assuming that all of the characters in the source encoding map to distinct characters in the target encoding (let's assume for the moment that we're talking about ISO 8859-1 to UTF-8), then all of the file names can be converted. But here's the list of things that must happen:
1) All of the file names must be converted from the source encoding to the target encoding. 2) Any symbolic links must be converted such that they point to the renamed file or directory. 3) Files that contain file or directory names will have to be converted. A couple of very obvious examples are /etc/passwd (for home directories) and /etc/fstab for mount points). It's step 3 that's going to be the problem. While you can make a more or less complete list of system files that would have to be converted, each case wound have to be considered for whether it was safe to convert the entire file or it was necessary to just convert file names. There is no way of identifying all of the scripts that might require conversion. And I don't want to think about going through each user's .bashrc, .profile and .emacs looking for all of the other files they load or run. ----- Original Message ----- From: Danilo Segan <[EMAIL PROTECTED]> Date: Wednesday, February 1, 2006 1:58 pm Subject: Re: question on Linux UTF8 support > Basically, you want to "ask" of all your users to use UTF-8 as > filesystem encoding. -- Linux-UTF8: i18n of Linux on all levels Archive: http://mail.nl.linux.org/linux-utf8/
