crefminusbib, part 3

[drdhaval2785]

https://github.com/sanskrit-lexicon/PWK/issues/23 continued 41 to 44

¯LILA&V@savarRana@savarRana@122491:¯LILA7V:t:
¯VIKR.S@caturaSra@caturaSra@38606:¯VIKR. S:t:
¯KR2K4K4H@liKana@liKana@96181:¯MR2K4K4H:t:
¯KA7D.I@kIlita@kIlita@28102:¯KA7D. I:t:

[drdhaval2785]

45

¯KUMA7RILA@aBihotavE@aBihotavE@7769:¯KUMA7RILA:n:Not sure

Needs examination. Seems like a name rather than a work.

3 occurrences

    Line 15622: <H1>100{aBihotavE}1{aBihotavE}¦ •Dat. ‹Inf.› {%zu opfern%} ‹Cit. bei› ¯KUMA7RILA. ‹nach› ¯GOLD. PW7769
    Line 15624: <H1>100{aBihoma}1{aBihoma}¦ •m. = #{aBihava} ¯KUMA7RILA. ‹bei› ¯GOLD. PW7770
    Line 15802: <H1>100{aByaDika}1{aByaDika}¦ ²1) •Adj. (•f. #{A}) ³a) {%überschüssig , hinzukommend , mehr seiend.%} ³b) {%das gewöhnliche Maass überschreitend , vorzüglich , ausserordentlich%} ¯51,25. ³c) {%überlegen , vorangehend , mehr geltend , höher stehend , mehr , grösser , stärker , heftiger , vorzüglicher.%} ‹Ein› •Abl. , •Instr. ‹oder ein in Comp. vorangehendes Wort bezeichnet entweder den Ueberschuss (› #{SatamaByaDikaM zazwitaH}) {%hundertundsechzig%} ¯221,2. #{atipayatfREraByaDikaM muzwim} ¯KUMA7RILA. ‹bei› ¯GOLD.). ‹oder das Uebertroffene› #{SarIrABya°} {%lieber als die eigene Person%} ¯112,12). ‹In Congruenz mit einem› •Adj. ‹so v.a. das› •Adj. ‹im Compar.› ¯SPR.3277. ²2) #{°m} •Adv. {%in hohem Grade , ausserordentlich , sehr.%} PW7859

[drdhaval2785]

46 to 50

¯LI7LA7V.S95@dIpaka@dIpaka@50514:¯LI7LA7V. S.95:t:Somewhere Marcis said 'S' stands for page. Not sure.
¯NR2S¯TA7P. ¯UP.@sasaptadvIpa@sasaptadvIpa@122706:¯NR2S.TA7P.UP.:t:Single reference
¯SIDDH.K. ‹ed.› ¯TA7R.@tasTI@*tasTI@45086:¯SIDDH.K.‹ed.›TA7R.:t:New resource. siddhAntakumudI edited by tArAnAtha.
¯GAN2IT.BHAGAN2.33.¯MADHJAM.@deva@deva/@52136:¯GAN2IT.BHAGAN2.33.MADHJAM.:t:It refers to maDyamADyAya of gaRit...
¯AMR2T. ‹Up.› ¯7.@parvataDAtu@parvataDAtu@64878:¯AMR2T.UP. 7.:t:

[drdhaval2785]

51 to 55

¯Beitr.z.K.d.ig.¯SPR@unmAdayantI@unmAdayantI@19337:¯Beitr.z.K.d.ig.SPR:t:
¯KAN2D2AK@BUruh@BUruh@80683:¯K4AN2D2AK:t:
¯KA7D.II,70,11@amBomuc@amBomuc@8636:¯KA7D. II,70,11:t:Space
¯K4AMPAVA@mahardDika@mahardDika@84096:¯K4AMPAKA:t:
‹N.pr. einer› ¯Zofe.@nipuRikA@nipuRikA@58662:‹N.pr. einer Zofe›.:t:Not a reference

[drdhaval2785]

56 to 60

¯R2SHIMAN2D2ALASTOTRA105@smar@smar@131651:¯R2SHIMAN2D2ALASTOTRA 105:t:space
¯WHITNEY,@SI@SI@112857:¯WHITNEY,:n:Not sure
(¯BHüLER, ‹Rep. No. 322)›@SizyahitA@SizyahitA@112852:(¯BÜHLER,Rep.No.322):t:
¯Z4@vitatI@vitatI@102394:¯Z.d.d.m.G.:t:
¯BHA7APR@AmapAcin@AmapAcin@15151:¯BHA7VAPR:t:

[drdhaval2785]

@funderburkjim Cumulative corrections stored in https://github.com/sanskrit-lexicon/PWK/blob/master/pw_ls/pwbib/diffstudy/correctionsubmission/crefminusbibsubmission.txt

Please use this standard submission file till case 60.

[gasyoun]

Page 60 or first 60 cases?

[drdhaval2785]

case

[drdhaval2785]

Ready to install.

[funderburkjim]

@drdhaval2785 Ho, Ho, Ho.

I'm way behind your crefminusbib work, and plan to start catching up tomorrow.

Should I proceed to take these issues in order, starting here at #27?

[drdhaval2785]

@funderburkjim Yes. Treat them in order. Best luck.

[funderburkjim]

Here are the way I'm handling these cases.

1. These cases will be treated as typos. These changes have not yet been installed.

   ; PW typos
   ¯LILA&V@savarRana@savarRana@122491:¯LI7LA7V:t: two errors
   ¯KR2K4K4H@liKana@liKana@96181:¯MR2K4K4H:t:
   ¯NR2S¯TA7P. ¯UP.@sasaptadvIpa@sasaptadvIpa@122706:¯NR2S.TA7P.UP.:t:Single reference
   ¯SIDDH.K. ‹ed.› ¯TA7R.@tasTI@*tasTI@45086:¯SIDDH.K.ed.TA7R.:t:New resource. siddhAntakumudI edited by tArAnAtha.
   ¯GAN2IT.BHAGAN2.33.¯MADHJAM.@deva@deva/@52136:¯GAN2IT.BHAGAN2.33.MADHJAM.:t:It refers to maDyamADyAya of gaRit...
   ¯AMR2T. ‹Up.› ¯7.@parvataDAtu@parvataDAtu@64878:¯AMR2T.UP.7.:t:
   ¯Beitr.z.K.d.ig.¯SPR@unmAdayantI@unmAdayantI@19337:¯Beitr.z.K.d.ig.Spr:t:
   ¯KAN2D2AK@BUruh@BUruh@80683:¯K4AN2D2AK:t:
   ¯K4AMPAVA@mahardDika@mahardDika@84096:¯K4AMPAKA:t:
   ‹N.pr. einer› ¯Zofe.@nipuRikA@nipuRikA@58662:‹N.pr. einer Zofe›.:t:Not a reference
   (¯BHüLER, ‹Rep. No. 322)›@SizyahitA@SizyahitA@112852:(¯BÜHLER,Rep.No.322):t:
   ¯Z4. ‹d.d.m.› ¯G.36,531.@vitatI@vitatI@102394:¯Z4.d.d.m.G.36,531.:t:
   ¯BHA7APR@AmapAcin@AmapAcin@15151:¯BHA7VAPR:t:
   

2. These are additions to pwbib_new (some overlap with above):

   ; ¯KUMA7RILA@aBihotavE@aBihotavE@7769:¯KUMA7RILA:n:Not sure  ejf: add to pwbib_new
   ; SIDDH.K.ed.TA7R. added 
   ; WHITNEY,@SI@SI@112857:¯WHITNEY,:n:Not sure

3. These cases are handled as non-typos. The problem with these cases is that it is hard to recognize the end of the abbreviation. The solution you suggested above involves inserting a space. This would be fine if we were making corrections directly to pw.xml, since it is ok to have a space within an xml tag: <ls>blah blah</ls>. However, inserting a space does not work in the coding of pw.txt; for instance in ¯KA7D. II,70,11 the space would be interpreted as the end of the ls element, and the 'II,70,11' would be left dangling unattached to KA7D.
   The way I'm handling this situation is to leave pw.txt unchanged in such cases, but to add logic to the clean_special function in abbrv.py so that the Roman numeral 'II' will not be considered part of the abbreviation. And, similarly for the other cases. This is somewhat awkward, but serves the present purposes of finding matches with pwbib. Note the last case (BÜHLER) doesn't involve a space, but is similarly handled.

   ; ¯VIKR.S@caturaSra@caturaSra@38606:¯VIKR. S:t: 
   ; ¯KA7D.I@kIlita@kIlita@28102:¯KA7D. I:t: 
   ; 46-50
   ;¯LI7LA7V.S95@dIpaka@dIpaka@50514:¯LI7LA7V. S.95:t: 
   ;¯KA7D.II,70,11@amBomuc@amBomuc@8636:¯KA7D. II,70,11:t:Space
   ;¯R2SHIMAN2D2ALASTOTRA105@smar@smar@131651:¯R2SHIMAN2D2ALASTOTRA 105:t:space
   ; BÜHLER,Rep.No. => BÜHLER,Rep.

[funderburkjim]

Corrections now installed.

[gasyoun]

I would not care much about the txt files. I would make the XML the default and main file for changes. With spaces included.

[funderburkjim]

I would make the XML the default and main file for changes

From a managerial point of view, there is much to like about this suggestion.

However, from the operational point of view, this presents numerous difficulties.

I have viewed as of paramount importance the 'chain of custody' notion. That is, the whole system derives from one source, pw_orig.txt, by a sequence of reproducible steps.

I feel sure that at some point in the process of improvements to the dictionaries, an xml form will be considered the primary form.

But this may occur after my time of involvement with the dictionaries.

[drdhaval2785]

'chain of custody' notion.

Absolutely agree. Actually manipulating text files is far more easier and faster than XMLs in most cases. When we are sure that not many mechanical errors remain in the texts, XMLs can be made the default. Noted at https://github.com/sanskrit-lexicon/CORRECTIONS/issues/228 so that it is not lost as a sub discussion of a correction issue.

[gasyoun]

But this may occur after my time of involvement with the dictionaries. - the last day of Pompeii, let it not come soon. Let .txt live for now.