-
-
Notifications
You must be signed in to change notification settings - Fork 28
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
sutra numbering mismatch #20
Comments
This is a known problem in 1.1. |
I see. Then, we should combine the commentaries of such commentators and store them in a single file - and then change numbering of subsequent sutras to match numbering of other commentators. Will you take this up? |
Sure. Will do so. Can you check up programmatically where the sutra for same number are different programmatically. I know of this one case. There may be others. |
You might want to pay special attention to |
Also check these - 1.1.19, 1.4.58, 2.1.12, 4.2.8, 4.2.32, 4.4.104, 5.1.36, 5.2.53, 6.2.108, 6.3.8, 7.3.119,8.4.20 The ashtdhyayi.com curation had all these speed bumps. |
#25 (comment) is relevant as well. |
Just added code to compare vritti file sutra-s to the "canonical" sutras . The bAlamanorama dump from ashtadhyayi.com shows the following mismatches,
These should be fixed PS: @drdhaval2785 you can use https://pypi.org/project/python-frontmatter/ for writing frontmatter as well. |
The comparison code flops with kAshika because of sandhi splitting ( |
Having switched to a sequence matching algorithm, I get the below for kAshikA:
|
लघुकौमुद्याम् एतानि परीक्ष्याणि -
|
तत्त्वबोधिन्याम् असमञ्जसानि -
|
(cc @neeleshb)
http://ashtadhyayi.com/sutraani/1/1/55 इत्य् "अनेकाल् शित् सर्वस्य" +इति दर्शयति।
किञ्च, अस्मज्जालक्षेत्रे न्यासटीकायां समस्या - https://ashtadhyayi.github.io/ui/?sutra=1.1.55 इति "स्थानिवदादेशोऽनल्विधौ" इत्यस्य टीकां दर्शयति। अन्यास् सर्वा अपि टीकास् सम्यग् भान्ति। असामञ्जस्यमिदम् परिहरणीयम्।
कामं @neeleshb अस्य श्रमः प्रयुज्यताम् पुनश्शोधनस्यापेक्षया।
(#2 इत्यत्र धवलकृत्यम् परीक्षता मयेदं दृष्टम्।)
The text was updated successfully, but these errors were encountered: