-
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
PWG ls markup #51
Comments
first phase done.Notes describing the changes is present in pwg_ls2/mbh1 folder. The changes were done in six steps, with the detailed changes of each step in change_01.txt through change_06.txt. In addition, a summary of the current frequency count of ls markup was prepared |
Hurray, that was top 3 of my whishlist and now it's become real. Thanks, its was badly wanted, an update.
@funderburkjim what would be the way to link to a book we allready have? What help would be required from my volunteers?
Done in MW, so can be redone easily?
Have no idea about it. How about @Andhrabharati ? @SergeA ?
@drdhaval2785 where is your Hemacandra?
Long live Kate
I'm working on publishing the Russian traslation once again, but it is a different edition.
I have the book, it's a gem. Guess it does not differ in the Sanskrit part from the later editions @drdhaval2785 ?
Waiting for @drdhaval2785
Nothing to be done here?
I believe we will have to leave it for later. 10598 ŚAT. BR. The ŚATAPATHABRĀHMAṆA in the Mādhyandina |
When followed by a number, it denoted the Burnouf's edition, which got published in 3 vol.s (Vol-1: Skandhas 1-3; Vol-2: Skandhas 4-6; Vol-3: Skandhas 7-9), containing both Sanskrit verses and French translation. |
Kathasaritsagara of Brockhaus was published in 3 parts (Part-1: lambakas 1-5, Part-2: lambakas 6-8 & Part-3: lambakas 9-18) in 1839. |
Laws of Manu by Deslongchamps was published in 1830, and it is a widely cited work. Why leave it? |
I had given the link to this widely cited work sometime back, and indeed it could be indexed for linking now.
The Śatapatha Brāhmaṇa by A. Weber is a major work after the Vedas, is too popular a work to be left out. This covers the works with 10k+ citations in PWG. |
The second phase could cover the following works (5k-10k):
|
Yes, please.
(Ind.) Spr. is already uploaded, but not linked to?
@Andhrabharati if you would give the PDFs for @KateRusse I would ask her to go for |
Just look for "katha sarit sagara Brockhaus" in Google books; two books with years 1839 (vol.1) and 1862 (vol.2: 1862 & vol.3: 1866) can be downloaded from there. You can get these from archive.org as well. |
I just recalled that @funderburkjim has recently posted the pwk ls lists [summary & detail] (in November last); but probably he could update the same now, which might just change the MBh. & Hariv. numbers. |
https://www.google.ru/books/edition/Katha_Sarit_Sagara_Die_M%C3%A4hrchensammlung/MLpUAAAAcAAJ?hl=ru&gbpv=1&dq=katha+sarit+sagara+Brockhaus&printsec=frontcover @KateRusse - do you understand the next step? |
MBH additional markupThis work described in pwg_ls2/mbh2 directory. The change_01.txt shows the sequence of changes. It is large. A typical change would be of form: This determinationis made by seeing if the previous non-number ls is an explicit MBH. For example, under L=41, aMsay pwg.txt has
so it is appropriate to change the markup But in a case such as
it is not appropriate to add MBH markup Of course, there are several other variations to this basic example. The summary of the markup changes can be seen in this comparison:
|
A 10k increase, amazing work as usual. |
Additional RV1 markupAnother additional 1000+ Rigveda links marked for link target. There is a rather large (500) number of RV references with 2 numbers. At least some of these are references to a particular hymn, rather than to a particular verse of a particular hymn. |
Additional AV markupThese changes in markup expose additional active links to the Atharva Veda verses. Some examples:
The markup work was done in folder pwg_ls2/av. The revised count of AV links rose from 9283 to 16149. |
11, 17, 2 not foundIn the above example, under aMSa, the AV link to 11, 17, 2 is not found! We get a 404 error from Don't know the cause of this. |
Not only this AV. 11,17,2; but the AV. 6,2,5 also is NOT at the current link given.
The reason is very plain and simple-- the VN text is to be read and applied appropriately to the main pages' text. In the above case, Thus the citations become avś_06.004.02. avś_11.006.02. There are very many such link targets that need corrections from the VN pages. Does this sound a good reason to the CDSL team, for "applying" the VN text to the main text (i.e. integrating appropriately; not just appending somewhere beneath, as is being done now), atleast the 'lies ... ... st. ... ...' portions? |
Sounds like a big piece of work. |
There are just about 360 of 'lies' followed by a number in a line (and 40 spanning two lines) in the whole of PWG text. Not a big thing at all, if decided to be 'done'. |
Thanks for the research on |
Additional P markupThese changes in markup expose additional active links to Panini; the work An example
The markup work was done in folder pwg_ls2/p. The revised count of P links rose from 19829 to 24914 |
Big fish. |
Just like to bring to your notice that not all "P. xxx" citations refer to Pāṇini's work as is. Many a times they are to its associated works [commentaries (or improvements) on it] like Kātyāyana’s Vārttika, Patanjali’s Mahābhāṣya, Jayāditya’s Kāśikā (referred mostly as Sch. in this PWG, and hence in MW), or Bhattoji's Siddhānta Kaumudi (SK). See for e.g. This "P. xxx" is presently in two ls parts in CDSL text-- It is the associated Kāśikā that has the अंशहरः word-- In summary, we should not split these as separate parts but have them as single entity (as done in my version); and link directly to the resp. work as far as possible. |
In the example (P. 3,2,9) The link https://ashtadhyayi.com/sutraani/3/2/9 also shows the Kāśikā . So in this example at least, the link target is relevant -- I see no problem here. |
@Andhrabharati your say? |
I chose P. just as an example for the point 'of clubbing commentary with the actual main source'. It is just incidental here that astadhyayi.com is used as the link target, which has almost all the associated works together at a single place; and as such @funderburkjim 'felt' no 'relevance' of my point. When other works are linked, the significance would be known. The works list is quite vast, starting from SAY on Vedas &c., KULL on Manu, MIT on Yaj~n, NILAK on MBH, MALL on various kAvyas. ... ...; If only the main work is linked in these cases, the actual intended commentary text would not be there. So the proper link text/source is to be used in all such cases. This is what I said above, as "In summary, we should not split these as separate parts but have them as single entity (as done in my version); and link directly to the resp. work as far as possible." Also the point could be extended to another variety, "citations within another work"; these could mostly be taken as "xxx im (or in) SKDR", being the cited reference as in SKDR. Seen that other editions of those actual works sometimes have a different text than that is in SKDR. |
And my actual point has another aspect, to combine both ls parts together. As can be seen even in this example, the Sch. part (separately marked) does not go anywhere (which actually is the intended matter); though the link to the first P. xxx part nevertheless contained the Sch. text somewhere underneath. |
Additional R. markupThis work described in #57. |
@Andhrabharati In re-reading your comments above, First, the 'P.' example is certainly a special case, in that the link target includes access to the commentaries. As you described, an interested and informed reader can get to the desiderata from the link given to the sutra. This seems satisfactory to me. While it might be possible to devise a link to a particular commentary for a given verse, I'm not sure that this added specificity would be of great use. As an exemplar for the other references, let's take sAyaRa commentary on Rg veda.
The ṚV. reference is linked to the verse, and the aKKala word does occur. So this link has at least some Thus, it seems to me that in this case, the current markup is both satisfactory for the current state of our link targets, and upgradeable. Practically, there would be several steps involved to upgrade the markup for such a commentary:
@Andhrabharati Do you see flaws in this suggested approach? In terms of priorities, I might prefer to develop link targets for some of the other more common ls references of pwg. But a 'complete' markup of pwg would include links to commentaries. |
There are no flaws in your approach, @funderburkjim ; you're quite practical in dealing with any matter (when you take it up!). What I was saying is to get/show the actual 'quoted text' as far as possible, not to just give an indication of the 'entry word'. Here is the screenshot for the above RV citation with actual wording used in PWG-- As you had pointed it, it is just the matter of finding the 'right' (PDF) source to link-up the citation. |
Whether a link is provided or not, this is TRUE in every sense. |
Technically doable? |
Jim has already stated the steps above; undoubtedly 'do-able', if the sources are identified/traced. |
Agree
Guess even @Andhrabharati agrees it would be too much for now |
I am a kind of 'a perfectionist'!! |
@Andhrabharati seen the scan? |
You mean scans of the parts done by others? The reason behind my above statement is not that the data is bad, but that it is not what PWG or pwk has seen. |
Here are some snippets from the Bomb. ed. of Bhag. P.-- Transcripted text: |
As I had mentioned before, this Bh. P. also came with the Śrīdhara's comm. (Bhāvārthadīpikā); just like the way the other big works R. (with Tilaka comm.) and MBh. (with Nīlakaṇṭha’s comm.). |
I am aiming to resolve all the literary source links in PWG for which there is a link target.
Currently this includes RV, AV, MBH, HARIV (and probably soon) R(amayana).
This note documents the current skirmishes in this battle.
The first intermediate objectives:
<ls>AV. 1, 2, 3. HARIV. 12345.</ls>
-><ls>AV. 1, 2, 3.</ls> <ls>HARIV. 12345.</ls>
(<ls>nach</ls> <ls>HAUGHTON).</ls>
->(nach <ls>HAUGHTON).</ls>
<ls>R.</ls> <ls>GORR.
-><ls>R. GORR.
Also, a few changes were made unrelated to 'ls'. e.g.
{#(X)#}
->({#X#})
(7000).The text was updated successfully, but these errors were encountered: