[9fans] runetype.c

[9fans] runetype.c

[erik quanstrom]

true, but since isalpharune() returns 1 when isupperrune() returns 1,
isalpharune(Ⓐ) returns 1, although the unicode guys say it's a symbol.

also, 3371 (<square> h P a) is listed in _alpha2[] though the unicode
guys say it's a symbol. it also has not upper/lower case.

sorry for being dense, i'm just trying to figure out what the rules are
and why they are the way they are.

erik

-----

> in UnicodeData-3.0.0.txt, these are as predicted, e.g. 24d0 is a lowercase form.

Re: [9fans] runetype.c

[Rob Pike]

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?
>

[9fans] runetype.c

[erik quanstrom]

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?