Re: Proposal to add Roman transliteration schemes to ISO 15924.

From: Richard Wordingham via Unicode <unicode_at_unicode.org>
Date: Tue, 3 Dec 2019 02:05:35 +0000

On Tue, 3 Dec 2019 01:27:39 +0000
Richard Wordingham <richard.wordingham_at_ntlworld.com> wrote:

> On Mon, 2 Dec 2019 09:09:02 -0800
> Markus Scherer via Unicode <unicode_at_unicode.org> wrote:
>
> > On Mon, Dec 2, 2019 at 8:42 AM Roozbeh Pournader via Unicode <
> > unicode_at_unicode.org> wrote:
> >
> > > You don't need an ISO 15924 script code. You need to think in
> > > terms of BCP 47. Sanskrit in Latin would be sa-Latn.
> > >
> >
> > Right!
> >
> > Now, if you want to distinguish the different transcription systems
> > for
> > > writing Sanskrit in Latin, you can apply to registry a BCP 47
> > > variant. There are also BCP 47 extension T, which may also be
> > > useful to you:
> > >
> > > https://tools.ietf.org/html/rfc6497
> > >
> >
> > And that extension is administered by Unicode, with documentation
> > and data here:
> > http://www.unicode.org/reports/tr35/tr35.html#t_Extension
>
> But that says that the definitions are at
> https://github.com/unicode-org/cldr/releases/tag/latest/common/bcp47/transform.xml ,
> but all one currently gets from that is an error message 'XML Parsing
> Error: no element found'.

A working URI is
https://github.com/unicode-org/cldr/blob/master/common/bcp47/transform.xml .

I'm still trying to work out what to do for IAST. Is it just:

sa-t-m0-iast

if one finds that

sa-Latn

allows too much latitude?

How does one choose between anusvara and specific consonants
for homorganic nasals? Is it sa-150-t-m0-iast v. sa-IN-t-m0-iast?

Richard.
Received on Mon Dec 02 2019 - 20:05:55 CST

This archive was generated by hypermail 2.2.0 : Mon Dec 02 2019 - 20:05:55 CST