Date: Mon, 03 Nov 2003 19:23:40 +0800 From: David Xu <davidxu@freebsd.org> To: Tim Robbins <tjr@freebsd.org> Cc: cvs-src@freebsd.org Subject: Re: cvs commit: src/lib/libc/locale big5.c euc.c mskanji.c utf8.c Message-ID: <3FA63ABC.1080907@freebsd.org> In-Reply-To: <3FA582F6.1020605@freebsd.org> References: <200311021009.hA2A9XTU063850@repoman.freebsd.org> <20031102134326.GA7255@nagual.pp.ru> <3FA582F6.1020605@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Tim Robbins wrote: > Andrey Chernov wrote: > >> On Sun, Nov 02, 2003 at 02:09:33AM -0800, Tim J. Robbins wrote: >> >> >>> unconverted; GB18030 will be done eventually, but GBK and UTF2 may >>> just >>> be removed, as they are subsets of GB18030 and UTF-8 respectively. >>> >> >> >> They can't be removed just because they are subsets. From this >> position ASCII can be removed too. They can be removed only if they >> are not used (encoded documents amount should be considered). >> >> > I was considering just making them aliases for GB18030 and UTF-8. I > don't see how this could break anything, but maybe I'll do a little > research into how other systems handle GBK/GB18030; UTF2 doesn't > really matter, since it's slated for removal in 6.0. > > Some printers can not support GB18030 and GBK, for example Epson LQ1600, It only supports GB2312, but LQ1600 is widely using in China, if I want to verify if a text file can be printed on LQ1600, I must have GB2312 locale to verify it, so I am even thinking about import GB2312 locale into FreeBSD, but not removing already existing locale, they are all needed in special cases, and in fact, GBK locale is still not fully working, although it is already in FreeBSD, it might only work for LC_CTYPE, but not LC_ALL. > Tim > David Xu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3FA63ABC.1080907>