9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: [9fans] runetype.c
Date: Thu,  1 Sep 2005 23:35:03 -0500	[thread overview]
Message-ID: <20050902043503.A768BB3C4D@dexter-peak.quanstro.net> (raw)

unicode sure gets wierd if you start looking too closely.

i'm curious about a few lines in __alpharune2[] and __toupper2[] for example

	0x3260,	0x327b,	/* ㉠ - ㉻ */

and (from __toupper2[])

	0x24d0,	0x24e9, 474,	/* ⓐ-ⓩ Ⓐ-Ⓩ */

and

	0x3371,	0x3376,	/* ㍱ - ㍶ */

however, from UnicodeData.txt (version 4.1), all of these are classified as symbols.

so, as far as i can tell, we either:

(a) declare anything with an upper/lower case a letter, never mind the unicode classification.
this makes 1 == isalpharune(ⓐ)  while 0 == isalpharune(㉻), however.

(b) go with the flow. anything that unicode says is a symbol is not a letter, even if some
symbols have an uppercase.

(c) (this appears to be what the current table is doing) anything that either is a letter
or is composed as "<operator> L+" where L+ are 1..N letter symbols is considered to be a letter.


any thoughts?


             reply	other threads:[~2005-09-02  4:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-02  4:35 erik quanstrom [this message]
2005-09-02  5:47 ` Rob Pike
2005-09-02  6:24 erik quanstrom

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=20050902043503.A768BB3C4D@dexter-peak.quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@cse.psu.edu \
    /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. 
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).