Re: GLib String support

Am Montag, den 11.08.2008, 09:13 +0200 schrieb Colin Leroy:
> On Mon, 11 Aug 2008 09:10:10 +0200, Mathias Hasselmann wrote:
> Hi,
> >  They needlessly limit the range of
> > characters a application can process, and even more important: They
> > add a vast amount of complexity to your program. Programmers really
> > should not have to think about locale issues.
> Email client developers know that, but unfortunately have no way to
> avoid them. Even with this, I don't think this should go into GLib :)

Yes, and that's why GLib offers the g_convert family of functions:
GLib's suggestion for dealing with charsets is to convert to UTF-8 on
input and to the specific locale on output. Java and .NET use the same
approach. AFAIR also the Python guys decided to choose that route for
3.0. IMHO convert-on-io is the least painless way.

Mathias Hasselmann <mathias hasselmann gmx de>
Openismus GmbH:
Personal Site:

Attachment: signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]