Re: Locale Encoding & Filenames

Ben Hutchings wrote:

> On Fri, 2010-04-09 at 19:36 +1200, Lawrence D'Oliveiro wrote:
>>
>> Previously, filenames would be treated as encoded according to your 
>> locale settings. Now, the behaviour is to treat them as always being in 
>> UTF-8 encoding, unless you build with the --enable-localize-filenames 
>> configure option.
> 
> This is correct for Linux but not for other systems.  I believe other
> Unix systems still follow the convention that filename encoding depends
> on locale.

I doubt that. I understand that previously lots of European Unix and 
Linux users would use ISO-8859-1 and other such regional encodings, 
simply because Unicode support wasn’t that well developed at the time. 
Perhaps even now some of them still do.

But this causes problems when you try to interchange data with other 
people. Consider two different people logging into the same server from 
remote locations in two different parts of the world, each using locale 
settings appropriate to their own region, but being unable to even refer 
to the same files because their filename encodings don’t agree.

For those who have been working the old way for too long, and think it’s 
too difficult to change, this is why convmv was developed.

> The same is true on Windows unless you use Windows-specific
> functions that take wide strings.

Not likely, since NTFS has been using Unicode as its underlying encoding 
for names since about 1993.

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Dvdauthor-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dvdauthor-users