From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/3928 Path: news.gmane.org!not-for-mail From: Roy Newsgroups: gmane.linux.lib.musl.general Subject: Re: Big5 "mostly" complete Date: Sun, 18 Aug 2013 12:20:47 +0800 Message-ID: References: <20130817205757.GA32462@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes Content-Transfer-Encoding: Quoted-Printable X-Trace: ger.gmane.org 1376799659 6930 80.91.229.3 (18 Aug 2013 04:20:59 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 18 Aug 2013 04:20:59 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-3932-gllmg-musl=m.gmane.org@lists.openwall.com Sun Aug 18 06:21:03 2013 Return-path: Envelope-to: gllmg-musl@plane.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1VAuUB-0000fD-Bt for gllmg-musl@plane.gmane.org; Sun, 18 Aug 2013 06:21:03 +0200 Original-Received: (qmail 1761 invoked by uid 550); 18 Aug 2013 04:21:02 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 1751 invoked from network); 18 Aug 2013 04:21:02 -0000 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 54 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 203186096008.static.ctinets.com User-Agent: Opera Mail/11.64 (Win32) Xref: news.gmane.org gmane.linux.lib.musl.general:3928 Archived-At: On Sun, 18 Aug 2013 04:57:57 +0800, Rich Felker wrot= e: > Hi all, > > I just committed a revision to iconv Big5 support, adding current > standardized extensions up to nearly the maximum possible level. The > whatwg definition of Big5 is still a bit bigger, so maybe we should > research whether its additions make sense to support. There would be > no size or performance cost to supporting them, since they just fill > in holes in the table without extending the table size. > > I'm still unclear on what, if any, action needs to be taken for > extended Taiwan variants of Big5. In theory UAO could be added (minus > the PUA mappings) but it's quite large and I still don't feel like I > have a good understanding of whether there are users who need it. > Whatwg has no mention of it with encoding standards > (http://encoding.spec.whatwg.org/) and only Mozilla seems to support > it. If it's needed in Taiwant for representing native-language text in= > a Big5-based encoding, that's a strong argument for supporting it > anyway, but if it's just for representing mixed-language text (as a > poor substitute for Unicode) I feel like it would be hard to justify > including it, and maybe we could think about later supporting it as a > local nonstandard encoding via charmap files... > > Comments? Both Big5-UAO and Big5-HKSCS are needed for those Taiwan people and Hong= = Kong people. For Big5-UAO, there is some commonly used dingbats(for example "=E2=99=A1= " mark) = and numeric representations(for example "=E2=91=A0") are in Big5-UAO but= not in = CP950. and Big5-UAO is still being used not only in ptt.cc telnet BBS, but also= = in text data files(file lists/cue sheets) because of not-supporting UTF= -8 = in applications(for example, Perl File-system I/O in windows, CD-Rippers= ). for Big5-HKSCS, it use used for storing commonly used Cantonese ideograp= hs = (for example, "=F0=A8=8B=A2" means "lift" in Cantonese) in Hong Kong. > > Rich