> Now the question is whether this is appropriate for FreeType to deal
> with UTF-8 filenames on Windows, which does not itself use UTF-8
> filenames, which are, therefore, superfluous.
Exactly. The very issue is that the `pathname' field in
`FT_Open_Args' is of type `FT_String*'. It would have been better to
use a separate `FT_PathString*' type that can be adapted to the
OS with a #define in `ftstdlib.h' or a similar file.
> The user should work with native UTF-16LE filenames on Windows to
> begin with. Then the use might as well open the stream with _wfopen
> by himself and call FT_Open_Face for the stream. Done.
Yes. Perhaps it is sufficient to document this limitation?
Werner
_______________________________________________
Freetype-devel mailing list
Freetype-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/freetype-devel
