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: Status of Big5 and extensions
Date: Thu, 8 Aug 2013 01:31:07 -0400	[thread overview]
Message-ID: <20130808053107.GL221@brightrain.aerifal.cx> (raw)
In-Reply-To: <20130808045057.GO25714@port70.net>

On Thu, Aug 08, 2013 at 06:50:57AM +0200, Szabolcs Nagy wrote:
> * Rich Felker <dalias@aerifal.cx> [2013-08-08 00:30:35 -0400]:
> > On Thu, Aug 08, 2013 at 05:53:21AM +0200, Szabolcs Nagy wrote:
> > > note that
> > > C87A, C87C, C8A4 are mapped to 2xxxx in hkscs
> > > (old hkscs pua codes agree with uao)
> > 
> > OK, so is this non-conflicting?
> > 
> 
> i just wanted to note that these are the only codes
> in the 89x157 table that map to non-16bit unicode
> codepoints
> 
> there is no conflict

OK, great. I think rather than using any fancy tables for the 89x157
grid and HKSCS, we can just special-case these two in the code.

It also looks to me like HKSCS and UAO are essentially non-conflicting
in the 89x157 grid once you remove PUA junk; the only real conflict is
the half-width kana UAO mapped over part of HKSCS. So it may make
sense to just add all the extended mappings in this range except the
kana to the base Big5 table. This would definitely simplify HKSCS
support. If we later want UAO support, this range could just be
special-cased algorithmically since it seems to be direct range
mappings to Unicode.

Rich


  reply	other threads:[~2013-08-08  5:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-07 16:50 Rich Felker
2013-08-08  0:18 ` Roy
2013-08-08  2:11   ` Rich Felker
2013-08-08  3:48     ` Roy
2013-08-08  3:53     ` Szabolcs Nagy
2013-08-08  4:30       ` Rich Felker
2013-08-08  4:50         ` Szabolcs Nagy
2013-08-08  5:31           ` Rich Felker [this message]
2013-08-08  7:19             ` Rich Felker

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=20130808053107.GL221@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).