Date: Mon, 27 Apr 2009 14:38:36 -0400 From: David Schultz <das@FreeBSD.ORG> To: =?iso-8859-1?Q?G=E1bor_K=F6vesd=E1n?= <gabor@kovesdan.org> Cc: hackers@FreeBSD.ORG Subject: Re: SoC 2009: BSD-licensed libiconv in base system Message-ID: <20090427183836.GA10793@zim.MIT.EDU> In-Reply-To: <aa9f273a8313c6436e76fa9f5d587ef4.squirrel@webmail.kovesdan.org> References: <aa9f273a8313c6436e76fa9f5d587ef4.squirrel@webmail.kovesdan.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Apr 23, 2009, Gábor Kövesdán wrote: > Hello all, > > my name is Gábor Kövesdán. I'm a Hungarian student and I'll be working on > a BSD-licensed libiconv implementation for FreeBSD during this year's > Summer of Code program. It'll be based on NetBSD's Citrus iconv but there > is a lot to do besides porting. My mentor is Xin Li. Nice. I'm sure many people will thank you for this. One complaint I've heard about both our wide character implementation and Citrus iconv is that the internal (wchar_t) encoding depends on the current locale. (Basically it uses a packed binary version of whatever the external representation is.) The relevant standards allow this, but it can be a pain for application and library writers. One thing to think about is whether it would make more sense to standardize on something like UCS-4 for the internal representation.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090427183836.GA10793>