Re: utf-16 and glib

2009-01-31 Thread Behdad Esfahbod
No one's converting the GTK+ stack away from UTF-8. Don't let all the talk intimidate you. behdad Thomas Stover wrote: > Please, please, please don't switch to UTF-16. To me gtk is about > getting to use technologies that are "solid", "real", "fun", and > "effective". Principally, that means C a

Re: utf-16 and glib

2009-01-30 Thread Thomas Stover
Please, please, please don't switch to UTF-16. To me gtk is about getting to use technologies that are "solid", "real", "fun", and "effective". Principally, that means C and *nix. UTF-8 is the greatest thing for one reason that kills all the others: solid compatibility with both of the above. I

Re: utf-16 and glib

2009-01-29 Thread Dominic Lachowicz
> Glib/gtk is full of macros. I believe que a C compiler is the right place to > this kind of unsafe code. If i want create safe code i have c#,c++, JAVA, D > or VALA. > Using macros is the only way to ensure intermediate APIs don´t have any > overhead. Besides modern GUIs have support to understan

Re: utf-16 and glib

2009-01-29 Thread Maciej Piechotka
On Mon, 2009-01-26 at 23:48 +0100, Martin (OPENGeoMap) wrote: > Dominic Lachowicz escribió: > What is wrong with: > gchar* g_utf8_strncpy (gchar *dest,const gchar *src,gsize n); > > > >>> That's one not needed as strncpy should work. > >>> > >>> > >> hehe i kno

Re: utf-16 and glib

2009-01-29 Thread Maciej Piechotka
On Mon, 2009-01-26 at 23:01 +0100, Martin (OPENGeoMap) wrote: > Maciej Piechotka escribió: > > On Mon, 2009-01-26 at 22:49 +0100, Martin (OPENGeoMap) wrote: > > > >> Maciej Piechotka escribió: > >> > >>> On Mon, 2009-01-26 at 22:30 +0100, Martin (OPENGeoMap) wrote: > >>> > >>> > >

Re: utf-16 and glib (was: g_malloc overhead)

2009-01-29 Thread Maciej Piechotka
On Mon, 2009-01-26 at 22:49 +0100, Martin (OPENGeoMap) wrote: > Maciej Piechotka escribió: > > On Mon, 2009-01-26 at 22:30 +0100, Martin (OPENGeoMap) wrote: > > > >> hi: > >> > > > >>> Well - what do you mean? Having 2 functions - one reciving utf-16 and > >>> one ut

Re: utf-16 and glib

2009-01-29 Thread Dominic Lachowicz
>>> What is wrong with: >>> gchar* g_utf8_strncpy (gchar *dest,const gchar *src,gsize n); >>> >> >> That's one not needed as strncpy should work. >> > > hehe i know but that function it really exist: > http://library.gnome.org/devel/glib/unstable/glib-Unicode-Manipulation.html#g-utf8-strncpy It

Re: utf-16 and glib

2009-01-26 Thread Behdad Esfahbod
Martin (OPENGeoMap) wrote: > Dominic Lachowicz escribió: > What is wrong with: > gchar* g_utf8_strncpy (gchar *dest,const gchar *src,gsize n); > > That's one not needed as strncpy should work. >>> hehe i know but that function it really exist: >>> ht

Re: utf-16 and glib

2009-01-26 Thread Martin (OPENGeoMap)
Dominic Lachowicz escribió: What is wrong with: gchar* g_utf8_strncpy (gchar *dest,const gchar *src,gsize n); That's one not needed as strncpy should work. hehe i know but that function it really exist: http://library.gnome.org/devel/glib/unstable/glib-Unicode-Manipulation.h

Re: utf-16 and glib

2009-01-26 Thread Martin (OPENGeoMap)
Maciej Piechotka escribió: On Mon, 2009-01-26 at 22:49 +0100, Martin (OPENGeoMap) wrote: Maciej Piechotka escribió: On Mon, 2009-01-26 at 22:30 +0100, Martin (OPENGeoMap) wrote: hi: Well - what do you mean? Having 2 functions - one re