From: Rob Pike <robpike@gmail.com>
To: erik quanstrom <quanstro@speakeasy.net>,
Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] runetype.c
Date: Fri, 2 Sep 2005 15:47:11 +1000 [thread overview]
Message-ID: <7359f049050901224752b6a2a5@mail.gmail.com> (raw)
In-Reply-To: <20050902043503.A768BB3C4D@dexter-peak.quanstro.net>
in UnicodeData-3.0.0.txt, these are as predicted, e.g. 24d0 is a lowercase form.
-rob
On 9/2/05, erik quanstrom <quanstro@quanstro.net> wrote:
> 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?
>
next prev parent reply other threads:[~2005-09-02 5:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-02 4:35 erik quanstrom
2005-09-02 5:47 ` Rob Pike [this message]
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=7359f049050901224752b6a2a5@mail.gmail.com \
--to=robpike@gmail.com \
--cc=9fans@cse.psu.edu \
--cc=quanstro@speakeasy.net \
/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).