Re: Just curious: who is using Pike for what?

Chris Angelico <[email protected]>
Newsgroups gmane.comp.lang.pike.user
Message-ID <CAPTjJmoo_GXUCcfdb=wTX-OEmYM1eOjqCxv=ZWLDQ=xT-raRHQ@mail.gmail.com>
On Tue, Dec 13, 2016 at 4:21 AM, Henrik Grubbström <[email protected]> wrote:
> That must be some Python-specific stuff; UnicodeData.txt from Unicode 8.0.0
> contains just the following entry:
>
>   00DF;LATIN SMALL LETTER SHARP S;Ll;0;L;;;;;N;;;;;
>
> ie no indication of an upper case variant. cf
>
>   00E0;LATIN SMALL LETTER A WITH GRAVE;Ll;0;L;0061 0300;;;;N;LATIN SMALL
> LETTER A GRAVE;;00C0;;00C0
>
> where the upper case variant is listed as 00C0.

I think that answers the question. It's not Python-specific; it's that
there are two separate tables:

http://unicode.org/faq/casemap_charprop.html
ftp://ftp.unicode.org/Public/UCD/latest/ucd/SpecialCasing.txt

# The German es-zed is special--the normal mapping is to SS.
# Note: the titlecase should never occur in practice. It is equal to
titlecase(uppercase(<es-zed>))

00DF; 00DF; 0053 0073; 0053 0053; # LATIN SMALL LETTER SHARP S

So I was wrong about exactly what Pike and Python differ on, but there
is definitely a valid definition in the Unicode specs. Anyway, it's
still really minor :)

If I find myself a tuit, I might put together an importer from the
Unicode files into some sort of bidirectional lookup table for names
and codepoints (or characters). If I do, would an appropriate place be
String.uniname["FULL STOP"]=="." and String.uniname["."] == "FULL
STOP"?

ChrisA
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.