[cairo] [PATCH] script: More compatible with C89 and VC++.

Bill Spitzak spitzak at gmail.com
Fri Jun 25 17:57:23 PDT 2010

That sucks. That may explain why in a previous library the solution
was to add complete replacement functions for all the File I/O that
did UTF-8 to UTF-16 translation (actually it did whatever the system
did but it was assumed to be UTF-8) and then used the wide character
api for all this.

Obviously another bad decision by Microsoft...

2010/6/25 Krzysztof Kosiński <tweenk.pl at gmail.com>:
> 2010/6/25 Bill Spitzak <spitzak at gmail.com>:
>> Isn't there a way to force the "system code page" to be UTF-8?
> No. MSDN docs say there is an UTF-8 codepage, but in practice you can
> only use it in encoding conversion functions. It doesn't work when you
> try to use it set it the console codepage or as the locale codepage.
>> UTF-8 is involved if the system encoding is UTF-8.
> See above, it's not possible.
> The only way to handle all files is to use the "wide" versions of
> Windows API functions. The C library on Windows cannot handle Unicode
> in any form.
> Regards, Krzysztof Kosiński

More information about the cairo mailing list