-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
On transliteration of Jihvamuliya & Upadhmaniya #267
Comments
For Ranjana- there are two cases, |
Just like other Indic script, in combination with the next consonants, in Tibetan script- Subscripts are to be used. |
Thanks a lot for this! The bug in Tibetan is now fixed. I'll have a look at the others. V |
Now I think for major scripts in the output you can use Ardhavisarga, for the remaining scripts you can just approximate to Visarga. |
Ardhavisarga can be supported in Tamil ( Extended ) as well |
Jihvamuliya and Upadhmaniya are represented using following
Distinct signs for both sounds are seen and in
Brahmi, Kannada, Tibetan, Devanagari, Bengali ( Vedic Extns code points), Soyombo, Newa, Sharada, Mongolian ( please add if some scripts are left out)
Ardhavisarga-
Ardhavisarga is seen and is added in the Script Extns for following scripts based on evidence by us
Script_Extensions=Beng Deva Gran Knda Mlym Nand Orya Sinh Telu Tirh
This covers all Major Indic scripts ( including Sri Lanka) used for Sanskrit.
In Gujarat only Devanagari is commonly used for Sanskrit even in the Gujarati language, script books, thus did not find any evidence.
Same with the Buddhist countries of SE Asia where I don’t know if there are any signs ( maybe one has to check in Sanskrit Vyakarana manuscripts if they exist)
Not sure of usages in Extended Tamil as the texts where these signs are generally seen ( like Vedic , Vyakarana) are all Grantha.
But the ardhavisarga glyph is generic, I guess can be used even where they were not seen traditionally.
While converting from scripts where Ardhavisarga is used needs to be based whether the next chars are ka/ kha and pa/pha ( any joiners / space needs or ignored )
But when the sign entered and used standalone in texts, then in target script it can be approximated to just visarga. Thus there are additional complexities.
In Devanagari, Bengali and Kannada an option use Ardhavisarga instead distinct signs needs to added.
The text was updated successfully, but these errors were encountered: