mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Re: Re: Big5 "mostly" complete
Date: Sun, 18 Aug 2013 03:32:29 -0400	[thread overview]
Message-ID: <20130818073229.GE20515@brightrain.aerifal.cx> (raw)
In-Reply-To: <op.w1zvoxfcdyj81a@monster.itedn32a.localdomain>

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


  reply	other threads:[~2013-08-18  7:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-17 20:57 Rich Felker
2013-08-18  4:20 ` Roy
2013-08-18  7:32   ` Rich Felker [this message]
2013-08-18 11:19     ` Roy
2013-08-27  1:53       ` Rich Felker
2013-08-28  0:57         ` Roy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130818073229.GE20515@brightrain.aerifal.cx \
    --to=dalias@aerifal.cx \
    --cc=musl@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).