[Ltru] Re: Non-Latin-1 Description fields in RFC 4645bis

Doug Ewell wrote:

> Here are the Description fields in the proposed RFC 4645bis Registry 
> that contain non-Latin-1 characters.

Thanks.  Unsurprisingly the hex. NCRs "work for me", i.e. it's clear
which Unicode point they refer to, for the experiment I jump to your
second block (UTF-8):

> * Basic Latin
> * Latin-1 Supplement

Oddly TUS 5.0 doesn't mention "English"  in chapter 7, or I missed it.

> * Latin Extended-A

Note to myeelf, need to find out why Sorbian and Frisian are listed
here (in TUS 5.0), and not earlier.

> * Spacing Modifier Letters
> * Latin Extended Additional

No extended B, C, D, or IPA so far, interesting.  

> Type: language
> Subtag: gwi
> Description: Gwichʼin

FAIL after ch.  Is that just my W2K font, or a more general issue
with the glottal stop &x2BC; ?

> Type: language
> Subtag: nqo
> Description: N’Ko

PASS.  

> Type: language
> Subtag: pmh
> Description: Māhārāṣṭri Prākrit
> Description: Prākrit, Māhārāṣṭri

FAIL (twice before ri), can't do "Latin extended additional" here.

> Type: script
> Subtag: Ethi
> Description: Geʻez

FAIL, my copy of TUS claims that &x2BB; is Hawaian, not Ethiopian.

Anything else "works for me" (at the moment I can't double check
it easily with other platforms)

 Frank

_______________________________________________
Ltru mailing list
Ltru@ietf.org
https://www1.ietf.org/mailman/listinfo/ltru