Re: g_malloc overhead

[Maciej Piechotka <uzytkownik2 gmail com>]

Martín Vales <martin opengeomap org> writes:

> Colin Walters escribió:
>> On Mon, Jan 26, 2009 at 9:12 AM, Behdad Esfahbod <behdad behdad org> wrote:
>>   
>>> Lets just say that
>>> UTF-16 is at best implementation details of Firefox.
>>>     
>>
>> Well, JavaScript is notably UTF-16.  Given that the Web, Java and
>> .NET

To be honest - aren't web currently XML-based (XHTML & co.)? And isn't
UTF-8 default encoding, and acidentally the most widly used, for XML?

>
>> But yeah, there's no way POSIX/GNOME etc. could switch even if it made
>> sense to do so (which it clearly doesn't).
>>   
> Yes, i only talked about the overhead with utf8 outside of glib, only that.
> Perhaps the only solution is add more suport to utf16 in glib with
> more methods.
>

Well - what do you mean? Having 2 functions - one reciving utf-16 and
one utf-8? To be honest - it doesn't make any sense to me (it would
create much mess, double the code, make programming errors easier...).

Converting? What's wrong with g_utf16_to_utf8?

Regards
-- 
I've probably left my head... somewhere. Please wait untill I find it.
Homepage (pl_PL): http://uzytkownik.jogger.pl/
(GNU/)Linux User: #425935 (see http://counter.li.org/)