-
Notifications
You must be signed in to change notification settings - Fork 0
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
Explanation of LS numbers in BOP #7
Comments
Does this answer your query, @drdhaval2785 ? One may note the large space between 19. and 2) The BOP has marked the separate meanings/genders in x) style; and there is no third numeric element in Ragh. (it has just xx.yy numbers) that could go as a citation! And finally, I did all these corrections mostly with regex itself. |
My request would be for the regexes used by you and order of application thereof, so that I can apply the same to bop.txt and arrive at roughly the same configuration as your file. That would enable me to see substantive changes made by you in Meld. Currently, too many false positives to navigate. |
I looked at the BOP file now, and seen that it needs much more work than what I did (mostly filling the blanks) those initial days. So, i would suggest that a complete overhaul might be preferred from the present cdsl text. |
What is the import of the above sentence for me? Should I wait till you complete the overhauling? |
I do not know, if and when I might take up the CDSL works again. I just meant that there is not much use with this L2 version that I had posted earlier, as it did not touch many aspects in the digital text. So far as the (filled up) lang. strings are concerned, Jim seems to have incorporated them (with later corrections from Anna and myself) in to the CDSL file already. |
Ok. I keep it in waiting mode till any further update. |
As Jim has worked on my file at #6 now, probably you could close this issue. |
Headword - kumudvat
Current digitization in csl-devanagari
AB version
Questions:
4.19. 2
with a space instead of4.19.2
?The text was updated successfully, but these errors were encountered: