Re: Locale Encoding & Filenames

David Huang wrote:

> The distro-wide policy should be to use the locale...

That’s fine. That’s why I provided the option to build the code that way,
if you want it.

Previously you wrote:

> Sure, *NTFS* uses Unicode, but the Windows API has two versions of every
> function that takes a string: the "ANSI" version, which uses the system's
> locale setting, and the "Wide" version, which uses UTF-16 (not UTF-8). I
> believe Windows dvdauthor binaries are usually built with mingw32, which
> I'm not too familiar with, but I get the impression that as with MS Visual
> C++, the standard library functions, such as open(), take strings encoded
> with the system's locale.

Since that’s inconsistent with the behaviour on POSIX systems, I’m pretty sure
that would be wrong.

------------------------------------------------------------------------------
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