Filed the following, thanks Richard. CLDR-13445 <https://unicode-org.atlassian.net/browse/CLDR-13445>
Release link for "latest" goes to zip file <https://unicode-org.atlassian.net/browse/CLDR-13445> <https://unicode-org.atlassian.net/browse/CLDR-13445> On Tue, Dec 3, 2019 at 2:31 AM Richard Wordingham via Unicode < unicode@unicode.org> wrote: > On Mon, 2 Dec 2019 09:09:02 -0800 > Markus Scherer via Unicode <unicode@unicode.org> wrote: > > > On Mon, Dec 2, 2019 at 8:42 AM Roozbeh Pournader via Unicode < > > unicode@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'. >