sanskrit-lexicon / CORRECTIONS

Correction history for Cologne Sanskrit Lexicon
8 stars 5 forks source link

aFem Manual Processing, Part 2 (PWK, SCH, AP90) #166

Closed gasyoun closed 8 years ago

gasyoun commented 8 years ago

https://github.com/sanskrit-lexicon/CORRECTIONS/issues/160 continued.

PWK

agrahyanamaka Lexicographer error?

kalapakayja Lexicographer error?

kikvisa

telaspanda

digdevata

denuzyita

sacisutra

sarangahara

gasyoun commented 8 years ago
gasyoun commented 8 years ago
gasyoun commented 8 years ago

laganiya

gasyoun commented 8 years ago
gasyoun commented 8 years ago
gasyoun commented 8 years ago

samikriya

gasyoun commented 8 years ago

This why we need to test not only -a. There seems to be many cases, some of which are legal. (!) f. = legal f., @drdhaval2785

interesting-f

gasyoun commented 8 years ago

PWK says to compare [=Vgl.] it with -lāsikā, not with -lāsika, so suralāsika with hrasva is a lexicographer or print error. *suralāsika [L=127533] [p= 7162-2] f. Föte. Vgl. svaralāsikā.

suralasika

gasyoun commented 8 years ago

svarapaycasata

gasyoun commented 8 years ago

hayasala

This ends PWK cases.

gasyoun commented 8 years ago

SCH

kubj

adho

gasyoun commented 8 years ago

AP90

gasyoun commented 8 years ago

Ready for @zaaf2 validation.

zaaf2 commented 8 years ago

Re. agrAhyanAmaka f. → agrAhyanAmaka Adj. Lexicographer / Print error MW:

zaaf2 commented 8 years ago

kalApaKaYja f. → kalApaKaYja m. Print error.

MW:

PWK:


kikviSa f. → kikviSa m. Print error

MW:

PWK:


tElaspanda f. → tElaspandA f. Print error.

MW:

PWG:


digdEvata f. → digdEvata n. Print error

PWG:

MW:


Denuzyita f. → Denuzyita Adj. Print error.

PWG:

MW:


paricintaka f. → paricintaka Adj. Print error

PWG:

MW:


bAhyatva f. → bAhyatva n. Print error.

PWG:

MW:


sAcIsUtra f. → sAcIsUtra n. Print error

MW:


sāraṅgahāra f. → sāraṅgahāra m. Print error

MW:


Re. suralAsika -> suralAsikaA (print error)

You mean: suralAsika -> suralAsikA (print error)

Confirmation: MW:


This ends the PWK review.

zaaf2 commented 8 years ago

I reviewed the other cases. Nothing to add.

gasyoun commented 8 years ago

@zaaf2 thanks, @funderburkjim your turn.

funderburkjim commented 8 years ago

Re sch aDoguqA:

I am uncertain about why this is in the aFem list. Here is the sch.txt record:

.{#aDoguqA#}100{#adhogud2a1#}¦ f. Argyreia speciosa , Caraka 1 , 1. [Schµ1867] €2

and here is the sch.xml record:

<H1><h><key1>aDoguqA</key1><key2>adhogud2a1</key2></h><body>f. Argyreia speciosa , 
Caraka 1 , 1. [Schµ1867] €2</body><tail><L>1841</L><pc>025-2</pc></tail></H1>

and here is the html display

adhoguḍā [L=1841] [p= 025-2] f. Argyreia speciosa , Caraka 1 , 1. 2

Everything looks right to me.

It is odd that in sch.txt and sch.xml the 'key2' field is present AND is in the AS coding. But, that coding is proper (the ending 'a1' means dIrGa 'a' or slp1 'A').

I will mark this as a no-change,

funderburkjim commented 8 years ago

pw corrections installed. Normalized form:

pw:agrAhyanAmaka:agrAhyanAmaka:p:l  f.->Adj.
pw:kalApaKaYja:kalApaKaYja:p:l  f.->m.
pw:kikviSa:kikviSa:p:l  f.->m.
pw:tElaspanda:tElaspandA:p: 
pw:digdEvata:digdEvata:p:l f.->n.
pw:Denuzyita:Denuzyita:p: f.->Adj.
pw:paricintaka:paricintaka:p:l f.->Adj.
pw:bAhyatva:bAhyatva:p: f.->n.
pw:sAcIsUtra:sAcIsUtra:p: f.->n.
pw:sAraNgahAra:sAraNgahAra:p: f.->m.
pw:SarkAra:SarkAra:n: good to generate SarkArI for search purposes
pw:garBopanizAwa:garBopanizad:t:
pw:jIvapura:jIvapurA:t:
pw:bfhatkaTa:bfhatkaTA:t:
pw:maNgalagIta:maNgalagIta:t: f.->n.
pw:raktADAra:raktADAra:t: f. -> m. 
pw:laganIya:laganIya:t: f.  ein best. Metrum. ->n. <impers.> {%sich anzuh&auml;ngen an%} (<Loc.>)
pw:vfkzamArjAra:vfkzamArjAra:t: f. -> m.
pw:vedavidya:vedavidyA:t:
pw:samIkriya:samIkriyA:t:
pw:suralAsika:suralAsikA:p:
pw:svarapaYcASata:svarapaYcASat:t:
pw:hayaSAla:hayaSAlA:t:
funderburkjim commented 8 years ago

SCH corrections installed.

sch:kubjottarA:kubjottarA:t: key2 Kubjottara -> kubjottara1
sch:aDoguqA:aDoguqA:n:
funderburkjim commented 8 years ago

Re ap90 SuBa -> SuB There are two forms of this, one a root and one a noun. In both cases the text is written without the 'a', and the digitization is wrong in having that 'a'. So both corrected as typos.

funderburkjim commented 8 years ago

ap90 corrections installed:

ap90:aBisaMpada:aBisaMpad:t:
ap90:tarada:tarad:t:
ap90:parizada:parizad:t:
ap90:SuBa:SuB:t:  two headwords
funderburkjim commented 8 years ago

All corrections installed.

funderburkjim commented 8 years ago

I'm using a 'playbook' ('cheat sheet', whatever) to do the various update steps. For your reading enjoyment, here is that instruction sheet for ap90:


;Corrections to AP90
; Ref https://github.com/sanskrit-lexicon/CORRECTIONS/issues/166
This is in directory pywork/correctionwork/issue-166/.

Input file is change.txt
step 1. Generate ap90upd.txt, ap90upd.tsv, and ap90nochange.txt
sh prepareupd.sh ap90 gasyoun 166

step 1a. Make manual adjustments to ap90upd.txt:
 cp ap90upd.txt ap90upd_edit.txt  # corrections in a copy
  NOTE SuBa had two forms, so had to modify by 
  hand from ap90.txt

step 2. Install corrections using ap90upd_edit.txt
 - By examination of pywork/update.sh, the last line is
python updateByLine.py ../orig/ap902.txt manualByLine02.txt ../orig/ap90.txt 

 - So, we append ap90upd_edit.txt to the end of file manualByLine02.txt
   in pywork,
   cp manualByLine02.txt prev_manualByLine02.txt
   cat prev_manualByLine02.txt correctionwork/issue-166/ap90upd_edit.txt > manualByLine02.txt
 - Then, in pywork directory, issue that last command of update.sh, as shown
   above

 - Then, create the headwords file, ap90hw2.txt
sh redo_hw.sh
 - Then, recreate (a) ap90.xml, (b) ../web/sqlite/ap90.sqlite
sh redo_xml.sh

The rest of the steps update downloads and documentation
step3.  
  web/webtc directory:
  edit web/webtc/download.html, and change as-of-date at bottom of file
  remake downloads:
    cd to downloads directory
    sh redo_all.sh

step4a: copy ap90upd.tsv to php/correction_response/
 cd ../pywork
 From pywork directory:
cp correctionwork/issue-166/ap90upd.tsv ../../../../php/correction_response/

step4b: cd ../../../../php/correction_response/
step4c: append ap90upd.tsv to end of cfr.tsv
 cp cfr.tsv cfr-prev.tsv
 cat cfr-prev.tsv ap90upd.tsv > cfr.tsv

step5a.  On local machine, open Github application, then open local
 CORRECTIONS repository in Explorer
step5b. Open GitBash terminal,
 cd Documents/GitHub/CORRECTIONS/
 sh redo_cfr.sh
step5c. rm ap90upd.tsv # in php/correction_response/ directory at Cologne.

step6a. edit history.txt, and write note of the changes
step6b. update dictionaries/AP90/ap90_printchange.txt using cfr.tsv
    This done by reformatting the 'print error' records of ap90upd.txt
    NOTE: Not required this step, no print errors.

step6c. update corrections_nochange.txt from ap90nochange.txt
   NOTE: Not required for this step, no nochange cases

step7.  prepare new sanhw1.txt and sanhw2.txt
step7a. On Cologne server, change to scans/awork/sanhw1
  (Assuming still in php/correction_response):
  cd ../../scans/awork/sanhw1/
  sh redo_update.sh
step7b. In local CORRECTIONS repository,
  sh redo_sanhw12.sh

step8. sync with GitHub
step8a. Create commit
step8b. 'Sync'

step9. Make 'installation complete' note in #166.

Note that sanhw1 recreation is now part of the process.