-
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
Ṛv. 10, 16, 4. 1. Vs. 21, 9. pwgauth.html #23
Comments
Is this issue still remaining? With a similar approach I used in AP90 (marking all the LS entries separated consistently by semicolon), this PWG can also be resolved. Easy task for me, if I get the Devanagari text. And then this issue can be closed. |
@funderburkjim any quick way? |
For all Devanagari needs, there exists a repository of Devanagari version of csl-orig at https://github.com/sanskrit-lexicon/csl-devanagari/tree/main/v02 . Anyone who needs Devanagari version may regenerate and use. |
https://github.com/sanskrit-lexicon/csl-devanagari/blob/main/scripts/redo_all.sh is the script to regenerate |
I had finished the pwg work 5 months before Dhaval came in to make all Devanagari files. (just for info.) |
And how does it help us? |
|
This is a 'global' issue. See my post at sanskrit-lexicon/MWS#130 (comment) |
pwgauth.html opens ok in Firefox and not at all in Chrome Version 58.0.3029.81 on Win 7. That's documented before.
But "trains" like
Ṛv. 10, 16, 4. 1, 162, 2. 4. Vs. 21, 9. Av. 9, 5, 1. Çat. Br. 2, 1, 4, 3. Ḱhând. Up. 2, 6, 1. M. 3, 6. 260. 8, 298. 11, 136. 12, 55.
do not get split. That means onlyṚv.
will be recognized in such list. So just marking references is not worth much. We want to split them, I guess, @funderburkjim , sure you're aware of the issue.The text was updated successfully, but these errors were encountered: