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

2019-12-03 Thread Vishvas Vasuki
On Tue, Dec 3, 2019 at 5:07 PM Richard Wordingham via Unicode <
unicode@unicode.org> wrote:

>
> However, as a locale for generated text, I feel it is inadequate.
> Wouldn't the expansion rules generate saṃti from संति rather than santi
> from सन्ति for 'they are'?


True. I suppose that someone wanting to replicate the "anusvAra instead of
nasal" shorthand in IAST would use a dravidian source script or a
non-sanskrit source language - or ask for inclusion of a modifier after
"iast" - like t-sa-m0-iast-anusavrashorthand

-- 
--
Vishvas /विश्वासः


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

2019-12-03 Thread Vishvas Vasuki
On Tue, Dec 3, 2019 at 3:48 PM Richard Wordingham via Unicode <
unicode@unicode.org> wrote:

> On Tue, 3 Dec 2019 02:05:35 +
> Richard Wordingham via Unicode  wrote:

The text in IAST that I encounter seems not to have ansuvara before
> stop consonants.

That's typical.
Whatever the source script (if there is one), IAST tends to be used by
people who follow the sanskrit devanAgarI conventions pretty strictly (so
ends up being transcription rather than transliteration.)



> I believe 'sa' would naturally expand (are there
> non-void prescribed rules on this?) as sa-Deva-IN, so perhaps the
> sa-Latn I usually see is unusual as sa-t-m0-iast and the description
> should be expanded to at least sa-t-m0-sa-150-iast if sa-Latn is not
> precise enough.
>

Not sure what 150 is doing there..

-- 
--
Vishvas /विश्वासः


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

2019-12-02 Thread Vishvas Vasuki
On Tue, Dec 3, 2019 at 7:28 AM Markus Scherer  wrote:

>
> The subtag I would use for IAST seems to be:
>> sa-Latn-t-sa-m0-iast (https://r12a.github.io/app-subtags/ is unable to
>> confirm that the extension
>> 
>> t-sa-m0-iast  is all right though.. Could someone confirm?)
>>
>
> I assume that the second "sa" is unnecessary, but I am not very familiar
> with the -t- extension.
>

The example und-Cyrl-t-und-latn-m0-ungegn-2007 in
https://tools.ietf.org/rfc/rfc6497.txt led me to use:
sa-Latn-t-sa-Zyyy-m0-iast for my case.


>
> Then, the next step seems to be to propose to add the below to
>> https://github.com/unicode-org/cldr/blob/master/common/bcp47/transform.xml
>> :
>> ISO 15919, Kyoto-Harvard, ITRANS, Velthuis, SLP1, WX, National Library at
>> Kolkata romanisation
>> How to proceed with that?
>>
>
> I would start with filing a CLDR ticket:
> http://cldr.unicode.org/index/bug-reports
>

Thanks! I've filed https://unicode-org.atlassian.net/browse/CLDR-13444 .



>
> Best regards,
> markus
>


-- 
--
Vishvas /विश्वासः


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

2019-12-02 Thread Vishvas Vasuki
On Tue, Dec 3, 2019 at 6:59 AM Richard Wordingham 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
>
> Thanks for the pointers!



> 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'.
>

Yes - that needs to be fixed (+markda...@google.com - could you please? )

https://github.com/unicode-org/cldr/blob/master/common/bcp47/transform.xml
shows iast!

The subtag I would use for IAST seems to be:
sa-Latn-t-sa-m0-iast (https://r12a.github.io/app-subtags/ is unable to
confirm that the extension

t-sa-m0-iast  is all right though.. Could someone confirm?)

Then, the next step seems to be to propose to add the below to
https://github.com/unicode-org/cldr/blob/master/common/bcp47/transform.xml :
ISO 15919, Kyoto-Harvard, ITRANS, Velthuis, SLP1, WX, National Library at
Kolkata romanisation
How to proceed with that?


-- 
--
Vishvas /विश्वासः


Proposal to add Roman transliteration schemes to ISO 15924.

2019-12-02 Thread Vishvas Vasuki
bcc:   as an FYI - plz respond on
the unicode mailing list as needed.

namaste!

Sanskrit has traditionally been written in a variety of scripts ranging
from Sharada to Grantha. In the past two centuries, it has been written in
Latin based scripts as well (please see
https://en.wikipedia.org/wiki/Devanagari_transliteration
). We
would like these Latin based scripts (IAST, ISO 15919, Kyoto-Harvard,
ITRANS, Velthuis, SLP1, WX, National Library at Kolkata romanisation) to be
included in the https://unicode.org/iso15924/iso15924-codes.html list.

The reason is that we would like to be able to present sanskrit text in a
variety of scripts and representations (see related thread
)
- and search engines like Google
recommend using  ISO
15924 to specify the script. Please guide us as to how to proceed.

-- 
--
Vishvas /विश्वासः