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

[Nick Porcino]

The code I posted earlier converts between UTF-8 and 16. So if you do
the conversion of the strings 8<>16 outside of OpenEXR you are covered
for OpenEXR's internal strings.

Santiago, are you saying that if you convert UTF-16 to UTF-8, then use
the converted string as a filename, that the OS itself displays the
filename as garbage?

-----Original Message-----
From: address@hidden
[mailto:address@hidden On
Behalf Of Paul Miller
Sent: Wednesday, January 25, 2006 6:38 AM
To: address@hidden
Subject: Re: [Openexr-devel] RE: UNICODE support in openexr file I/O

Santiago wrote:
> No, UTF-8 is not at all enough.... I said I want to use Kanji, not 
> karakana or hiragana.... That means I need to use one of the 16-bits 
> "strange" signs.... Can't conver to UTF-8 because I will loose
"bits"... 
> Kanji CAN'T be translated to out latin alphabet, because each sign
means 
> an "object", are NOT letters, so I need to enter the 16/32bits
unicode. 
> And who says Kanji says cyrilic or other signs... YOu , because are 
> almost english talkers, are not at all conscient of the difficulties 
> saving/naming files. For a japanese, is weird to be forced to name a 
> file autoexec.bat and not $%!$"&!W%343.$!&... So no, UTF8 is not
enough, 
> nust be UTF16 or better to use one of the universal signs.

Any UTF-16 string can be encoded as UTF-8. Obviously, you would convert 
your UTF-16 strings to and from UTF-8 when working with the OpenEXR
library.

-- 
Paul Miller | address@hidden | www.fxtech.com | Got Tivo?



_______________________________________________
Openexr-devel mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/openexr-devel