Closed deepestblue closed 10 months ago
Thanks. I want vidyut-lipi to support languages beyond Sanskrit, as long as that support doesn't conflict with support for Sanskrit. So this is a legitimate bug, and I'll prepare a fix.
@deepestblue Is there a Devanagari equivalent for the aytam? Our current transliteration code assumes that all text can be mapped to a Devanagari equivalent. If that's not the case for the aytam, a fix here will be more challenging.
To my knowledge, there isn't. There are other characters that also don't have Devanagari equivalents, like the saṁvr̥tōkāram of Malayalam (again unique to Dravidian). Devanagari is an adequate "base" for Sanskrit but no one to my knowledge uses it for Dravidian languages.
For now, I've worked around this by using Devanagari conventionally as the internal join key but using strings from other scripts as needed. I've confirmed that my local setup works and will push this out (& close this issue) in the next round of updates.
Pushed and deployed to our online demo.
./lipi -f tamil -t iso19519 "ஃ"
Expected:
ḳ
Actual:ḥ
Source: https://web.archive.org/web/20160418005419/http://homepage.ntlworld.com/stone-catend/trimain1.htm
As for resolving the issue, one option is to remove support for
ஃ
altogether, as this character is specific to Dravidian languages. Or if vidyut-lipi aims to support languages beyond Sanskrit, the mapping could be fixed instead.