|
You don't need any changes in the interface to
support UTF-8. Storing and retrieving UTF-8 strings is done with traditional
8bits string based functions. IMO, something like "character strings are in
UTF-8 format" could be part of the specifications though. Unless you
are thinking about sone API that would translate UTF-8 to Unicode back and forth
automatically.
Yves Poissant
www.hash.com
----- Original Message -----
Sent: Thursday, January 19, 2006 1:42
PM
Subject: Re: [Openexr-devel] UNICODE
support in openexr file I/O
The type wchar_t is compiler implementation
dependant it varies in size from compiler to compiler and should NEVER be
used as a type in files.
That being said, changing the
specification/interface to support UTF-8 would be a good
idea.
Chris
On 1/18/06 7:04 PM, "Santiago" <address@hidden>
wrote:
All the OpenEXR classes ( like TiledRgbaOutputFile )
only accepts old ASCII "const char*" parameter to read/write files....
That's bad because if I wanna name a file using extended characters like Ñç
or even Kanji, I can't .... Please... can you provide too a wchar_t version
so we can use plenty the UNICODE characters? thx
Concursa y llévate
una PS2 two Envía GENIOS al 5959 <http://juegos.ya.com/consolas_y_pc/2005/09/concurso-ps2.html>
.
Ya.com ADSL Navega y habla 24h
ADSL 24h + Llamadas Nacionales
y Locales 24h = 19,95 /mes+IVA. Con Router + Cuota Alta ¡gratis! http://acceso.ya.com/ADSLllamadas/4mb
_______________________________________________
Openexr-devel
mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/openexr-devel
|