From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/3927 Path: news.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Big5 "mostly" complete Date: Sat, 17 Aug 2013 16:57:57 -0400 Message-ID: <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=us-ascii X-Trace: ger.gmane.org 1376773087 12217 80.91.229.3 (17 Aug 2013 20:58:07 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 17 Aug 2013 20:58:07 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-3931-gllmg-musl=m.gmane.org@lists.openwall.com Sat Aug 17 22:58:11 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 1VAnZa-0002m9-OS for gllmg-musl@plane.gmane.org; Sat, 17 Aug 2013 22:58:10 +0200 Original-Received: (qmail 11643 invoked by uid 550); 17 Aug 2013 20:58:09 -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 11632 invoked from network); 17 Aug 2013 20:58:09 -0000 Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Xref: news.gmane.org gmane.linux.lib.musl.general:3927 Archived-At: 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? Rich