Closed funderburkjim closed 9 years ago
case = 51 headword= jyO page = 2279-2 linenum = 89784
<H1>100{jyotsneSa}1{*jyotsneSa}¦ •m. {%der Mond.%} PW43616
<H1>100{jyO}1{jyO}¦ (•Nom. #{jyOs}) •m. |
<g>Ζεύς</g>
, {%der Planet Jupiter.%} PW43617
<H1>100{jyOtiza}1{jyOtiza}¦ •n. ²1) = #{jyotiza} ‹4).› ²2) {%eine best.
gegen die Finsterniss geschleuderte leuchtende Waffe †Arg4una's%} ¯MBH.7
,30,24. ‹v.l.› #{jyotizka}. ²3) ‹Name zweier †Sa7man› ¯A7RSH.BR. PW43618
case = 52 headword= takzaSila page = 3002-1 linenum = 90774
<H1>100{takzavant}1{takzavant}¦ •Adj. ¯MBH.2,23,18 ‹vielleicht fehlerhaf
t für› #{kzatavant} {%verwundet habend.%} ¯NI7LAK.: #{takzastanUkaraRa g
AtrasaMkoca ityarTaH tadvAn}. PW44070
<H1>100{takzaSila}1{takzaSila}¦ ²1) •m. •Pl. {%die Bewohner von%} ‹2).›
²2) •f. #{A} |
<g>Τάξιλα</g>
, ‹N.pr. einer Hauptstadt der †Gandha7ra.› #{°tas} ¯45,24. PW44071
<H1>100{takzaSilAvatI}1{*takzaSilAvatI}¦ •f. ‹N.pr. einer Oertlichkeit.›
PW44072
case = 53 headword= tAmraparRi page = 3022-3 linenum = 93461
<H1>100{tAmraparRa}1{tAmraparRa}¦ ²1) •n. ‹N.pr. eines Theiles von †Bha7
rata †Varsha› ¯GOLA7DHJ.BHUV.41. ²2) •f. #{I} ³a) {%®*Rubia_Munjista.%}
³b) {%*eine Art Teich.%} ³c) ‹N.pr.› ¹a) ‹einer Tochter †Kr2shn2a's› ¯HA
RIV.2,103,8. #{tAmrapakzA} ‹v.l.› ¹b) ‹eines Flusses› ¯VARA7H.BR2H.S.14,
16. ¹g) ‹*einer Stadt auf Ceylon.› PW45320
<H1>100{tAmraparRi}1{tAmraparRi}¦ ‹(metrisch)› •f. = #{tAmraparRa} ‹2)c)
<g>β</g>
)› ¯VARA7H.BR2H.S.81,1. PW45321
<H1>000{tAmraparRItawAka}1{tAmraparRItawAka}¦ ‹N.pr. einer Oertlichkeit.
› PW45322
case = 54 headword= tAlajaNGa page = 3025-2 linenum = 93871
<H1>100{tAlaja}1{tAlaja}¦ ²1) •Adj. {%von der Weinpalme kommend%} ¯SUC2R
.1,213,1.¯BHA7VAPR.1,242. ²2) •*n. {%Palmwein.%} PW45524
<H1>001{tAlajaNGa}1{tAlajaNGa}¦ ²1) ³a) {%Weinpalmen gleiche ~ , d.i. se
hr lange Beine habend%} ¯R.5,12,35. ³b) {%zum Stamme der †Ta7lagan5ga ge
hörig.%} ²2) •m. ³a) {%ein †Rakshas%} ¯VARA7H.JOGAJ.3,21. ³b) ‹N.pr.› ¹a
) •Pl. ‹eines Kriegerstammes› ¯105,23. ¹b) ‹des angeblichen Ahnherrn von
2)b)
<g>α</g>
).› ¹g) ‹eines †Raksha.› ¹d) ‹eines †Daitja› ¯HARIV.3,47,11. ¹e) ‹eines
Fürsten der Kobolde.› ³c) {%ein Fürst der †Ta7lag4an5gha%} ‹2)b)
<g>α</g>
).› PW45525
<H1>100{tAlajawA}1{*tAlajawA}¦ •f. {%die unter der äusseren Rinde liegen
den Fibern der Weinpalme.%} PW45526
case = 57 headword= trika page = 3048-2 linenum = 97576
<H1>100{triHplakzA}1{triHplakzA}¦ •f. ‹v.l. für› #{triplakza}. PW47336
end%} ¯C2ULBAS.1,49. ³b) {%*zum dritten Mal erfolgend.%} ³c) ‹in Verbind
ung mit oder mit Ergänzung von› #{Sata} {%drei vom hundert , drei Procen
t.%} ²2) •m. (•*n.) {%ein dreieckiger Platz , ~ Hof%} ¯HARIV.6501. ²3) •
*m. ³a) {%®Asteracantha_longifolia.%} ³b) {%Trapa bispinosa.%} ²4) •*f.
#{A} {%eine best. Vorrichtung am Brunnen.%} ²5) •n. ³a) {%Dreizahl%} , |
<g>τριάς</g>
¯227,1. ³b) {%regio sacra , Kreuzbein%} ; ‹auch› {%die Hüften.%} ‹In› ¯
SUC2R. ‹auch› {%die Gegend zwischen den Schulterblättern.%} PW47337
<H1>100{trikakud}1{trikaku/d}¦ ²1) •Adj. {%dreigipfelig , dreispitzig ,
mit drei Hörnern versehen.%} #{trikaku/deva/ samAnA/nAm} ‹so v.a.› {%dre
ifach Seinesgleichen überragend.%} ²2) •m. ³a) ‹Bein.› ¹a) ‹†Vishn2u's o
der †Kr2shn2a's› ¯MBH.12,342,93. ¹b) ‹†Brahman's.› ³b) {%ein best. †Dac2
a7ha%} ¯VAITA7N. ³c) ‹N.pr.› ¹a) ‹eines Berges im †Himavant.› ¹b) ‹eines
case = 59 headword= dakzakanyA page = 3061-3 linenum = 99724
C2iva's Stier.%} ³l) ‹N.pr.› ¹a) ‹eines †A7ditja , der auch mit †Prag4a7
pati identificirt wird› , ¹b) ‹eines best. †Prag4a7pati , dessen Opfer v
on †C2iva zu Nichte gemacht wird. Hierher wohl› #{dakzasyAyanam} ‹als Be
s.› {%eines best. Opfers%} ¯M.6,10 ‹(Hdschr.).› ¹g) ‹eines Sohnes des †G
arud2a.› ¹d) ‹verschiedener Männer.› ²3) •*f. #{A} {%die Erde.%} PW48397
<H1>100{dakzakanyA}1{dakzakanyA}¦ •f. ²1) {%eine Tochter von †Daksha%} ‹
2)l)
<g>β</g>
).› ²2) ‹*Patron. der †Du7rga7.› PW48398
<H1>100{dakzakratu}1{dakzakratu/}^1¦ •m. •Du. {%Wille und Verstand%} ¯TB
R.1,5,4,2.¯A7C2B, ¯GR2HJ.3,6,7. PW48399
case = 60 headword= daSArhaka page = 3076-3 linenum = 101911
<H1>100{daSArha}1{daSArha}¦ ²1) •m. ³a) ‹N.pr.› ¹a) •Pl. ‹eines Volkes.›
¹b) ‹des Ahnen dieses Volkes.› ³b) ‹Bein.› ¹a) ‹†Kr2shna's.v.l.› #{dASA
rha}. ¹b) ‹*jedes †Buddha.› ²2) •*f. #{I} {%eine Prinzessin der †Dac2a7r
ha.%} PW49444
<H1>100{daSArhaka}1{daSArhaka}¦ •m. •Pl. = #{daSArha} ‹1)a)
<g>α</g>
).› PW49445
<H1>100{daSAlaMkAramaYjarI}1{daSAlaMkAramaYjarI}¦ •f. ‹Titel eines Werke
s.› PW49446
@jmigliori All the cases for PW are ready for you.
@funderburkjim would be interesting to see a video how you prepared the list. Documenting every with a text file can take the whole day. The video is better because in it you can make mistakes and still we will be able to reproduce it one day, if needed. At least we can try. Although I'm not sure - you can not do something middle class, you always want it perfect. That's a problem.
It looks like there’s a mistake with Case 6. The Greek word in question appears under that headword, but on 1098-1, not 1097-3. Additionally, Greek letters are used to mark sub-definitions in the entry but aren’t marked for change. How should I go about this?
on 1098-1, not 1097-3
is possible, rarely the page numbers do not match.
Regarding 1097-3 or 1098-1:
a) First, a detail about the displays of scan pages - you've probably already discovered this, but it won't hurt
to mention the detail here. The little < and > appearing at top left of the scanned image allow you to
click to the previous or next page, respectively.
b) The page number (like 1097-3) is probably the location where the headword begins. If this turns out to be a difficulty for your work, I can examine the program involved and try to make it more precise in terms of the location of the Greek text.
Regarding the Greek letters marking sub-definitions: You don't need to mark these. Here's why, by example under case 6 , occurring at top of page 1098-1
Part of the digitization is ¹a) ‹der Mutter des †Pari7kshit.› ¹b) ‹einer Schwester †Amr2todana's.›
.
The alpha)
section header of the scan is represented in the digitization by ¹a)
and the
beta)
section header by ¹b)
.
If you look at the display of this headword (click the amfta headword link in case 6), you'll see that the display represents the Greek.
Why Thomas chose this way to represent the Greek section headers is unclear. But, at least you don't have to be concerned with coding these Greek section headers.
@gasyoun I'll put the video request in TODO list.
Got it!
On Apr 18, 2015, at 3:04 PM, funderburkjim notifications@github.com wrote:
Regarding the Greek letters marking sub-definitions: You don't need to mark these. Here's why, by example under case 6 , occurring at top of page 1098-1
Part of the digitization is ¹a) ‹der Mutter des †Pari7kshit.› ¹b) ‹einer Schwester †Amr2todana's.›.
The alpha) section header of the scan is represented in the digitization by ¹a) and the beta) section header by ¹b).
If you look at the display of this headword (click the amfta headword link in case 6), you'll see that the display represents the Greek.
Why Thomas chose this way to represent the Greek section headers is unclear. But, at least you don't have to be concerned with coding these Greek section headers.
— Reply to this email directly or view it on GitHub.
Why Thomas chose this way to represent the Greek section headers
- maybe it's time to have them as in the book?
It would be possible to programmatically change pw.txt to do this. There are many such changes that might improve pw.txt to make it more useable. Some of these are present in the construction of pw.xml, and in the programs that display pw.xml. I don't want to tackle reorganizing pw.txt, pw.xml and the displays any time soon.
As you say. It's good to at least know and document - I was not aware of it before.
Ι found some more Greek that isn’t marked here. It’s the same headword as Case 35 under section 12: http://www.sanskrit-lexicon.uni-koeln.de/scans/PWScan/2014/web/webtc/indexcaller.php?input=slp1&output=deva&key=ca (It should be θ). There’s also something marked as Greek that isn’t.
There’s also another unmarked Greek letter under the last headword on 2254-1, where it continues on to the next column, after e). (It should be γ)
These are now also otherwise all set.
@jmigliori |(greek) te , , que -> θ, que
would be easier to understand than It should be θ
, thanks.
Sorry about that, @gasyoun, I’m new to GitHub and should be more clear :
•The τε part is fine.
•The “d” I highlighted in code above is marked as Greek, but there is no Greek there in the dictionary scan.
•As for the θ I mentioned, it’s also under that headword, but farther down in the entry. I noticed it in the scan. I don’t have access to the code to show you where it is. I can show you where it is in the online dictionary (under header 12): http://www.sanskrit-lexicon.uni-koeln.de/scans/PWScan/2014/web/webtc/indexcaller.php?input=slp1&output=deva&key=ca
Regarding Case 35. I can see why this is confusing - the reason is that somewhere along the line (in one of the programs that generated these GitHub issue comments) data vanished !
Here's the corrected data:
78366 old <H1>001{ca}1{ca}^1¦ ‹Conj.› ²1) {%und , auch , |
<g>te</g>
, , que.%} ‹Steht hinter beiden zu verbindenden Theilen (oft durch› {%s
owohl - als auch%} ‹wiederzugeben) , nur nach dem letzten oder nur nach
dem ersten. Bei drei und mehr zu verbindenden Theilen überall , nur nach
dem letzten oder hier und da. In gebundener Rede steht› #{ca} {%bisweil
en an unrichtiger Stelle%} ‹(› #{vEcitryaM nItividyAM dadAti ca} ‹st.› #
[ALL OF THIS IS MISSING FROM ORIGINAL case 35]
{ca da°}) ‹und auch müssig. Werden zwei Sätze durch wiederholtes› #{ca}
‹verbunden , so hat das erste Verbum finitum den Ton.› #{ca} ‹--› #{ca}
‹in einem negativen Satze› {%weder -noch%} ; #{na Kalu ca - nEva} ‹dass.
Grammatiker , Lexicographen und Erklärer gebrauchen› #{ca} ‹oft elliptisch›
{%(auch ‹so v.a.› dieses und noch Anderes)%}. ‹In Verbindung mit andern
Partikeln› ; #{cEva , cEva - cEva , cEva - ca , ca - cEva , cEva hi}
‹(am Ende eines Halbverses)› , #{cApi , ca - cApi , cApi - ca , api ca ,
na - na - api ca} ‹(mit fehlender Negation)› , #{na - na cApi , api cEva ,
cEvApi , ca taTA , taTA ca , taTEva ca}. ²2) #{ca - tu} = #{ca - ca}
{%sowohl - als auch%} ¯110,13. ²3) {%oder%} , ‹mit› #{vA}
‹wechselnd oder dessen Stelle vertretend (nach› #{utAho}). ²4)
{%auch , selbst , sogar.%} ²5) {%und zwar.%} ²6) {%gerade , eben%}
‹(ausnahmsweise).› ²7) {%aber , dagegen%} ¯43,18. ‹Insbes. nach›
#{yadi , aTa} ƒPage2.203-1ƒ ‹(hier v.l.› #{tu}) , #{aTa vA}.#{ na cEva}
‹--› #{tu} {%nicht aber%} ¯193,28. ²8) {%dennoch.%} ²9) #{ca}
‹--› #{ca} {%kaum.%} ‹--› ‹so ein› #{ca} ‹an zweiter Stelle ohne ein
vorangehendes› #{ca} {%alsbald , sogleich.%} ²10) #{ca} ‹--› #{ca}
{%obgleich - dennoch%} ¯VIKROR.28. #{ca-na tu} ‹und› #{ca-na ca}
{%obgleich-dennoch nicht.%} #{na ca-ca} {%obgleich nicht - so doch.%}
²11) {%wenn%} ‹(mit betontem Verbum fin.)› ¯VIKROR.39. ²12)
‹über die Bed. von› #{ca} ‹nach einem Interrogativum› •»s.u. ‹1.›
#{ka} ‹2)a) , 1.› #{kaTA} ‹1)› , #{kim} ‹2)d)
[END OF MISSING DATA FROM ORIGINAL case 35
<g>d</g>)›
, #{kutra} ‹7) und› #{kva} ‹5)b).› PW38182
As you see, that <g>d</g>
occurs in a different place and is fact that Theta that you noticed!!
I've put the θ at location of the 'd'.
Regarding 'There’s also another unmarked Greek letter under the last headword on 2254-1, where it continues on to the next column, after e). (It should be γ)'
I don't think this is a problem in the digitization.
This is under headword jamBaka
on page = 2254-2
That γ does appear in the display for jamBaka Here is the digitization: linenum = 85910
<H1>100{jamBaka}1{ja/mBaka}¦ ²1) •Adj. ‹am Ende eines Comp.› {%zermalmend , verschlingend.%}
²2) •m. ³a) ‹etwa› {%Zauber%} ¯MBH.5,64,16. ³b) {%Unhold oder ein best. Unhold%} ¯VS.30,16. ³c)
‹Bein. †Gan2ec2a's.› ³d) ‹N.pr.› ¹a) ‹eines Unholds , eines Krankheitsdämons› ¯HARIV.9557.
ƒPage2.254-2ƒ ¯AGNI-P.40,19. ¹b) ‹eines von †Kr2shn2a besiegten Dämons.›
¹g) ‹verschiedener in mythischen Waffen hausender Geister.› ¹d) ‹*eines Wesens im Gefolge †C2iva's.› ³e) {%ein an%}
‹2)d)› ¹g) {%gerichteter Spruch.%} [ This is the gamma
³f) {%*Citronenbaum.%} ²3)
•*f. #{jamBakA} {%das Aufsperren des Mundes.%} ²4) •f. #{jambikA} ‹N.pr. einer buddh. Gottheit.› PW41748
In this coding that gamma is coded as ¹g)
, that superscript '1' indicates that is the coding of a Greek subsection number, and that's the way the display shows it:
So, unless that gamma is not supposed to be a subsection identifier, the digitization looks right to me.
Does this make sense?
I didn't think that’s a subsection header because it’s out of alphabetical order (γ comes before δ) with the other headers and formatted differently in the facsimile. Most of what’s been set aside for me to code has been letters like this, appearing in parentheses right after a number and a Roman letter.
@gasyoun Can you understand the German ? How should we understand 2)d)γ
?
@jmigliori I see your point, that there are many cases with Greek letters appearing in parentheses right after a number and a Roman letter.
This does seem similar -- At the moment I don't know which coding is right:
``
2)d)
My German is pretty subpar. I’m not sure what they meant by that.
I've posted all these corrections.
You should probably do some spot checking to convince yourself that your corrections are properly installed (e.g. by clicking on the headword links - The Greek text is temporarily shown with a yellow background color).
I'm going to post the first page of next dictionary cases (PWG) now.
I did some random checks throughout: they all looked great!
So the 2)d)γ)
or 2)d)¹g)
question remains open, right?
@gasyoun - yes, that's still an open question, restated in issue#8.
Since @jmigliori confirms that the installation of corrections looks ok, this issue can be closed.
There are 166 cases of Greek text in the PW dictionary, Böhtlingk Sanskrit-Wörterbuch in kürzerer Fassung.
This first part has cases 1-60.
The page-column will be useful in locating the text in the scanned image of the page. For instance, 1012-3 (for case=2) indicates that the text is on 3rd column of that page.
These cases are ready to go. I'll go ahead and post cases 61-110 on issue 5, and cases 111-166 on issue 6.
The reason for splitting cases into different issues is just so the web pages aren't too big.