From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/3929 Path: news.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: Re: Big5 "mostly" complete Date: Sun, 18 Aug 2013 03:32:29 -0400 Message-ID: <20130818073229.GE20515@brightrain.aerifal.cx> 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 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1376811164 32058 80.91.229.3 (18 Aug 2013 07:32:44 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 18 Aug 2013 07:32:44 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-3933-gllmg-musl=m.gmane.org@lists.openwall.com Sun Aug 18 09:32:48 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 1VAxTk-0005GM-7Z for gllmg-musl@plane.gmane.org; Sun, 18 Aug 2013 09:32:48 +0200 Original-Received: (qmail 29920 invoked by uid 550); 18 Aug 2013 07:32:44 -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 29906 invoked from network); 18 Aug 2013 07:32:43 -0000 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Xref: news.gmane.org gmane.linux.lib.musl.general:3929 Archived-At: On Sun, Aug 18, 2013 at 12:20:47PM +0800, Roy wrote: > 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 "♡" > mark) and numeric representations(for example "①") 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 > ideographs (for example, "𨋢" means "lift" in Cantonese) in Hong > Kong. HKSCS is supported as of yesterday's commit. I'm aware that it's needed for representing Cantonese language in Big5, and that it's widely used on the web. What I'm not clear on is the necessity of UAO. Keep in mind that iconv is an API for information interchange: things like interpreting web content, email, old text files, etc. The fact that UAO exists is not alone reason to support it; it has to actually have usefulness in situations where the iconv interface should be used. If you want to see it included, this is what you need to convince us of: - That it's in widespread use in large volumes of existing data (on the web, text files, etc.) or data that is being newly generated (e.g. as a default encoding of popular mail software). - That it's necessary to represent linguistic content in languages used in Taiwan, not just as a substitute for Unicode to represent foreign languages. - That failure to support it would put musl's iconv in a worse position of compatibility than other iconv implementations or software-specific (e.g. in-browser) character set conversions. The fact that UAO does not even have a MIME type, and that, per web standards (http://encoding.spec.whatwg.org/), a MIME type of "Big5" is to be interpreted as essentially Big5-2003+HKSCS, leaves me doubting that UAO is in widespread use for information interchange. Mozilla seems to be the only browser that support it. I previously cited a thread on the whatwg mailing list in which research was being conducted to determine what should constitute Big5, i.e. roughly what characters outside the old CP950 were needed for real websites, and UAO did not come up. If I'm wrong and just missing its importance, please fill me in. I'm not trying to be difficult, but if UAO is important, I want to see the reasons why. Rich