sanskrit_parser
sanskrit_parser copied to clipboard
kmadathil
Parsers for Sanskrit / संस्कृतम्
Just to let you know that now the recently launched APIs for verb related information. This may be integrated with the information regarding the verb form (currently it comes from...
Eg: "ity api" doesn't work as of now. We have two options 1. add spaces (optional) into adeSa rules as in 7be2be230c9a08526e64cd9079c4d63e576ed7f5 2. find a better way. I think 2....
Namaste! I Am Sebastian, an indologist/buddhologist from Germany who is mainly working with Sanskrit and Tibetan bilingual texts (translation of Buddhist material). I am currently thinking about ways to automatize...
Need to add tests to ensure normalization behaves as expected. Should test the base normalization module as well as the higher level API of sandhi, lexical and morphological analyzers.
Quoth @vvasuki in #9 " Taking the flexibility preference to a slightly higher level - it is a good idea not to be "married" to any database technology. Access it...
Discussion in #60 reminds one of the need for flask API tests (From experience, they're quite simple to write and useful).
Akin to https://github.com/kmadathil/sanskrit_parser/issues/61, I think it's a good idea to adapt and contribute to a common datacontainer/ json schema definition - https://github.com/vedavaapi/sanskrit_data/tree/master/sanskrit_data/schema . Folks wouldn't then misspend time converting from...
* Add descriptions to the API-s using appropriate flask restful annotations. See examples in https://api.vedavaapi.org/py/ullekhanam/docs#/ * Good to add links to report issues as well in each API description.
Opening a separate issue to talk about this, since it was being lost in the overgeneration discussion: घटकानां मध्ये व्यवस्था एवं भवेत् इति मम मतम् L0: Given an input string,...
SanskritLexicalAnalyzer currently reports no splits for praNamati, vizIdati etc, because of the Natva, Shatva, etc. whereas it can correctly handle pranamati (even though this is not the correct form). Need...