Re: [Openexr-devel] UNICODE support in openexr file I/O

[Drew Hess]

"Santiago " <address@hidden> writes:

> In fact, I NEED to write japanese Kanji comments into an OpenEXR
> file and ALSO name the file in Kanji... so UTF-8 C++ char is not
> enough... I need 16-bits or even 32-bits UNICODE wchar_t
> support. You should add _wfopen()/wsprintf routines to you library
> to do this. thx.


Assuming we provide UTF-8 support for filenames and attribute values,
why can't you convert your application's characters to UTF-8 before
calling OpenEXR APIs?

d