Date: Wed, 6 May 2009 14:28:51 +0400 From: Alexander Churanov <alexanderchuranov@gmail.com> To: Gabor Kovesdan <gabor@freebsd.org> Cc: freebsd-hackers@freebsd.org Subject: Re: SoC 2009: BSD-licensed libiconv in base system Message-ID: <3cb459ed0905060328n4ad05d98xb5ba0c2e01d356e2@mail.gmail.com> In-Reply-To: <4A00B897.809@FreeBSD.org> References: <aa9f273a8313c6436e76fa9f5d587ef4.squirrel@webmail.kovesdan.org> <20090427183836.GA10793@zim.MIT.EDU> <49F5FE45.2090101@freebsd.org> <20090427193326.GA7654@britannica.bec.de> <20090427194904.GA11137@zim.MIT.EDU> <49F6C7A1.6070708@FreeBSD.org> <20090428122225.GA2862@britannica.bec.de> <24e9a86bf5995ba551db8f27aa204191.squirrel@webmail.kovesdan.org> <20090428180624.GA2223@britannica.bec.de> <4A00B897.809@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Gabor, Joerg, I am currently working on UTF-8 support in syscons and highly interested in making FreeBSD using UTF-8 out of box. There is my $0.02: 1) Why discuss UCS-4 at all? UTF-32 is alreay in place. SImple, standardized, fixed-width and stateless. 2) I'm against using wchar_t internally, because C language standard does not require that a wchar_t variable can hold an UTF-32 code point. 3) Please, give an example of character that does not fit into UCS-4. I'll check whether it fits into UTF-32. I expect that any character fits into a single UTF-32 code point. Sincerely, Alexander Churanov
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3cb459ed0905060328n4ad05d98xb5ba0c2e01d356e2>