search for: _wmain

Take a look at how the Opus Tools package handles it. So far as I remember, it requires minimal changes to the file(s) containing references to the main entry point and to fopen. It imports the command line arguments as wchar_t and converts them to UTF-8, and has replacement functions for fopen and some text output that accept UTF-8 instead of ANSI. I think it automatically kicks in on definition

On 3/18/2013 14:55, Erik de Castro Lopo wrote: > Brian Willoughby wrote: > >> I believe that shell does handle wildcards on all Unix variants, >> including OSX. > > Yes. > >> Since Windows does not handle them, I suggest that the >> main flac code not be littered with code that's not necessary on the >> primary platforms. > > No, the

..."If you provide a code page like UTF-7 or UTF-8, setlocale will fail, returning NULL."). There is a good chance that the behavior will still be correct with UTF-8 strings even when in the "C" locale, but I'm not entirely sure. If so, you might be correct, we could just add _wmain(), have it convert the commandline parameters to UTF-8 and call the existing main() function. We also have to be sure to open the FLAC objects with either callback-functions for I/O or with the version where you pass a FILE * object. Having proper display from the commandline is another issue ent...