"Lars Kristan" writes: > > A system administrator (because he has access to all files). > My my, you are assuming all files are in the same encoding. And what about > all the references to the files in scripts? In configuration files? Soft > links? If you want to break things, this is definitely the way to do it.
Was it ever really wise to use non-ASCII file names in scripts and configuration files? It's not very hard to convert soft links at the same time. Nor, really should it be too hard to figure out the encodings; /home/foo/.bashrc probably tells you, as well as simple logic. Even if you can't do a system-wide change, it's easy enough to change the system files, and post a message about switching to UTF-8, and offering to assist any users with the change. -- ___________________________________________________________ Sign-up for Ads Free at Mail.com http://promo.mail.com/adsfreejump.htm
