On Tue, 2009-01-27 at 00:19 +0100, Martin (OPENGeoMap) wrote: > hummm. > Example: > If we have for example a DWG binary file we have for example 15000 utf16 > strings. If i use glib i need make 15000 translations utf16/utf8 to use > the utf8 glib api. When i need save the file i need make other 15000 > translations. There are thounsand of formats using utf16. I don´t love > utf16, but I "MUST" use utf16 in the real world. I am not the guilty of > existence of utf16 :'( .
If you find that really is a bottleneck, there's nothing stopping you from writing functions _in your app_ which would deal with the strings as UTF-16 throughout the process of loading and saving. Philip > Regards. > > > _______________________________________________ > gtk-devel-list mailing list > [email protected] > http://mail.gnome.org/mailman/listinfo/gtk-devel-list
signature.asc
Description: This is a digitally signed message part
_______________________________________________ gtk-devel-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gtk-devel-list
