Closed Andhrabharati closed 1 year ago
@Andhrabharati Will get to this eventually.
was thinking of proofing the HWs portions
@Andhrabharati please, please, please.
Any update @Andhrabharati ?
Any update @Andhrabharati ?
???
Just posting AB version of the (basic) corrected pw file, for the perusal of others. pw_AB_L0.zip
[Except for saying that the quality of digitisation is quite poor as compared with other files seen here so far, I do not want to go further with any comments/observations (too many encountered; and only a very few handled), lest it would hurt the feelings of others.]
metaline comparisons:
OLD : {#खादितंर्#}¦ <ab>Nom. ag.</ab> {%Esser, Verzehrer, Verspeiser%} <174,19.>
NEW : {#खादितर्#}¦ <ab>Nom. ag.</ab> {%Esser, Verzehrer, Verspeiser%} <174,19.>
Otherwise, the metalines are identical in pw.txt and pw_AB_L0.txt.
Otherwise, the metalines are identical in pw.txt and pw_AB_L0.txt.
Oh, so most changes seem to be inside.
Made the corrections to pw.txt posted in first comment above. See commit 66fa46b.
One slight adjustment made : 367928 <ls>SUŚR.1,368,18</ls> fügen
.
Also a few changes of 'eine best ' to 'eine best. ' 'best.' found to be a German abbreviation for 'bestimmte' = 'a certain (kind of)'. translation provided by Thomas.
* Suggest change in L=33744 in pw_AB_L0.txt KAditaMr -> KAditar (M not needed) and similarly remove anusvAra in body:
I've noticed too many typos, and was thinking of correcting atleast the front portion (HW entry and the continuation) next.
Had just spent 3 days for arriving at the above basic version.
The ultimate goal is to bring this pw also to the format of my PWG (did about 90% of rearrangement and stalled).
Here are some sample screens of this PWG-
Ultimately vLex and Lex fields would be combined; and the entry & contd. fields would be with the grouped HWs to be appropriately split as separate entries as done in MW.
Just posting AB version of the (basic) corrected pw file, for the perusal of others. pw_AB_L0.zip
[Except for saying that the quality of digitisation is quite poor as compared with other files seen here so far, I do not want to go further with any comments/observations (too many encountered; and only a very few handled), lest it would hurt the feelings of others.]
@Andhrabharati Your restraint is appreciated and even more so if you were also not to allude to (potentially hurtful) comments you have suppressed.
Had just spent 3 days for arriving at the above basic version.
Hard working you are.
Have been working to harvest corrections to 'ls' tags from pw_AB_L0.
An example is <116,17.> <ls>Spr.</ls> <2121. 7756.>
Here the 'ls' tag indicates the name of the literary source.
and the specifics of the reference are put in a 'naked' <>
markup.
Usually this 'naked' tag starts with a digit, as in the examples above.
But occasionally the 'naked' tag starts with some other character, as in <ls>HANUM. UP.</ls> <S. 392.>
, where the 'S.' is abbreviation for 'Seite' = 'Page'.
It is somewhat difficult to devise logic to distinguish such a non-numeric tag from some unrelated xml markup such as <bot>
, <ab>
, etc.
Thus, in future work suggest some more easily identifiable markup.
Some suggestions <ln>116,17.</ln>
, <_116,17.>
It is somewhat difficult to devise logic to distinguish such a non-numeric tag from some unrelated xml markup
When a novice like me could "frame" a logic, wonder why such an expert as @funderburkjim cannot "devise" one!
It is somewhat difficult to devise logic to distinguish such a non-numeric tag from some unrelated xml markup
When a novice like me could "frame" a logic, wonder why such an expert as @funderburkjim cannot "devise" one!
@Andhrabharati
Jim (being a Ph.D. in mathematics) might have referred to mathematical logic (and not "a" logic), for all I know,
so just presenting your solution would be sufficient.
A sarcastic reference to a senior colleague, as "such an expert as", is rude.
@Andhrabharati we can do more together, than on our own. Be softer, thanks.
@Andhrabharati ... so just presenting your solution would be sufficient.
Sorry to be back on this, @thomasincambodia!
I was just responding to the below suggestion by @funderburkjim -
Thus, in future work suggest some more easily identifiable markup.
And I guess, he has understood me well enough over the past few monhts, to "filter" my comments to get only what he needs out of my posts.
I think, this issue is closeable now.
[As I have never left a work (to the planned level) unfinished, this is just an indication that my PWG session is over; was thinking of proofing the HWs portions as some errors were noticed during my work. May be sometime very soon.]
It is but natural that one would see PWK after PWG (when seriously interested).
I have the PWK text converted into Devanagari, and the very first corrections list is being posted here.
[This is with a check for "small letter followed by Cap. letter". Similar correction was done in PWG in my working.]