Date: Mon, 27 Apr 2009 15:49:04 -0400 From: David Schultz <das@FreeBSD.ORG> To: freebsd-hackers@FreeBSD.ORG Subject: Re: SoC 2009: BSD-licensed libiconv in base system Message-ID: <20090427194904.GA11137@zim.MIT.EDU> In-Reply-To: <20090427193326.GA7654@britannica.bec.de> References: <aa9f273a8313c6436e76fa9f5d587ef4.squirrel@webmail.kovesdan.org> <20090427183836.GA10793@zim.MIT.EDU> <49F5FE45.2090101@freebsd.org> <20090427193326.GA7654@britannica.bec.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Apr 27, 2009, Joerg Sonnenberger wrote: > On Mon, Apr 27, 2009 at 11:49:41AM -0700, Tim Kientzle wrote: > > David Schultz wrote: > >> ... whether it would make more sense to standardize on something like > >> UCS-4 for the internal representation. > > > > YES. Without this, wchar_t is useless. > > I strongly disagree. Everything can be represented as UCS-4 is a bad > assumption, but something Americans and Europeans naturally don't have > to care about. ...but isn't this moot at present because there are no widely-accepted encodings that include characters that aren't supported by UCS-4? Citrus doesn't seem to support any such encodings in any case. If this ever really becomes an issue, we could always stuff locale-dependent encodings into unused UCS-4 code pages. However, it doesn't seem worthwhile to deliberately burden programmers over concerns that are presently, and for the foreseeable future, hypothetical.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090427194904.GA11137>