From: Uncle George <gatgul@voicenet.com>
To: tromey@cygnus.com,
"mauve-discuss@sourceware.cygnus.com"
<mauve-discuss@sourceware.cygnus.com>
Subject: Re: Unicode character \u2102
Date: Tue, 30 Mar 1999 12:13:00 -0000 [thread overview]
Message-ID: <3700BECD.A75BF59C@voicenet.com> (raw)
In-Reply-To: <87pv5srw8z.fsf@cygnus.com>
The 1.2 specification for Character.isLowerCase() appears to have 2
specifications. Also one might also read that all the "L1" characters are
"considered to be lowercase"
1) is the "L1" in the unicode 2.0 character set.
2) The other soecification that specifically excludes the \u2000 <=>
\u2fff range.
The Character.isUpperCase() does not have any Unicode character
'category" specification at all.
It is not yet, to me, what is/isnot really true/false for any of the
Character methods. Searching......
gat
Tom Tromey wrote:
> >>>>> ">" == Uncle George <gatgul@voicenet.com> writes:
>
> >> From the JAVA documentaion, the unicode char 2102, is just not a
> >> capital letter ( 1'st test - must NOT be between \u2000 - \u2fff ).
> >> ergo can never be a java uppercase letter!
>
> >> Is there something going on with the presumption of the
> >> CharacterTest ?
>
> I don't recall -- does CharacterTest say that \u2102 is upper case or
> not?
>
> If you read the online JDK 1.2 docs, you'll notice that isLowercase
> has two possible definitions. One is `Ll'. The other is a long
> sequence of conditions.
>
> Sun told me that `Ll' is the correct answer. I'm not sure I believe
> them. So it's still possible that this bug could lie anywhere: in
> Sun's doc, Sun's implementation, or our test.
>
> Anyway, by analogy I'd assume their uppercase documentation is
> similarly incorrect (or not).
>
> Opinions, preferably with supporting documentation, solicited.
>
> Tom
WARNING: multiple messages have this Message-ID
From: Uncle George <gatgul@voicenet.com>
To: tromey@cygnus.com,
"mauve-discuss@sourceware.cygnus.com"
<mauve-discuss@sourceware.cygnus.com>
Subject: Re: Unicode character \u2102
Date: Thu, 01 Apr 1999 00:00:00 -0000 [thread overview]
Message-ID: <3700BECD.A75BF59C@voicenet.com> (raw)
Message-ID: <19990401000000.yO47yRvNqnKTTcl6wowbb9nCwMsha-dz-bxb-PbDyME@z> (raw)
In-Reply-To: <87pv5srw8z.fsf@cygnus.com>
The 1.2 specification for Character.isLowerCase() appears to have 2
specifications. Also one might also read that all the "L1" characters are
"considered to be lowercase"
1) is the "L1" in the unicode 2.0 character set.
2) The other soecification that specifically excludes the \u2000 <=>
\u2fff range.
The Character.isUpperCase() does not have any Unicode character
'category" specification at all.
It is not yet, to me, what is/isnot really true/false for any of the
Character methods. Searching......
gat
Tom Tromey wrote:
> >>>>> ">" == Uncle George <gatgul@voicenet.com> writes:
>
> >> From the JAVA documentaion, the unicode char 2102, is just not a
> >> capital letter ( 1'st test - must NOT be between \u2000 - \u2fff ).
> >> ergo can never be a java uppercase letter!
>
> >> Is there something going on with the presumption of the
> >> CharacterTest ?
>
> I don't recall -- does CharacterTest say that \u2102 is upper case or
> not?
>
> If you read the online JDK 1.2 docs, you'll notice that isLowercase
> has two possible definitions. One is `Ll'. The other is a long
> sequence of conditions.
>
> Sun told me that `Ll' is the correct answer. I'm not sure I believe
> them. So it's still possible that this bug could lie anywhere: in
> Sun's doc, Sun's implementation, or our test.
>
> Anyway, by analogy I'd assume their uppercase documentation is
> similarly incorrect (or not).
>
> Opinions, preferably with supporting documentation, solicited.
>
> Tom
next prev parent reply other threads:[~1999-03-30 12:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-28 17:18 Uncle George
1999-03-29 9:05 ` Uncle George
1999-03-29 10:23 ` Tom Tromey
1999-03-30 12:13 ` Uncle George [this message]
1999-04-01 0:00 ` Uncle George
1999-04-01 0:00 ` Tom Tromey
1999-04-01 0:00 ` Uncle George
1999-04-01 0:00 ` Uncle George
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=3700BECD.A75BF59C@voicenet.com \
--to=gatgul@voicenet.com \
--cc=mauve-discuss@sourceware.cygnus.com \
--cc=tromey@cygnus.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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).