-
Notifications
You must be signed in to change notification settings - Fork 5
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
o
vs O
Corrections in MW, Part 2
#129
Comments
@gasyoun |
|
ह् (h) and ः (ḥ, Visarga) are different phonetic phenomena. ह् does not change to ः at the end of a word. ह् is a voiced fricative glottal (v. Wikipedia). Visarga is a voiceless “allophone of /r/ and /s/ in pausa (at the end of an utterance)” (Wikipedia). स्वरुह् is formed with the verbal root रुह्. As to the declension of such words, v. Whitney 391.f. |
sIrRa and SIrRa are alternative forms: |
330 false positive, different meanings |
1.079.08b satrāsā́haṃ váreṇiyam http://www.utexas.edu/cola/centers/lrc/RV/RV01.html#H079 |
satyaratA may be a valid word- indulging in truth.. original reference may
have to be checked
|
@drdhaval2785 satyaraTA f. N. of the wife of tri-śaṅku Hariv. in MW is close to meaning in PE. |
It is perhaps worth observing that satyaratA in PUI is given as derived from satyavrata (MW: सत्य-व्रत [p= 1136] : n. a vow of truthfulness Hariv. Kāv. [L=230057]; mf(आ)n. devoted to a vow of truth, strictly truthful ṠāṅkhṠr. MBh. Hariv. &c [L=230058]; m. N. of an ancient king Pañcat. …). Observe also that the cited passages are different in satyaraTA MW (Hariv.) and satyaratA in PE,PUI (Br. III. 63. 115: Vā. 88. 117), which may point to different forms (and different etymological interpretations) of the same word in those different passages. |
@gasyoun I agree with your observation. A print error. The word comes clearly from SAva + a-SOca (MW: अशौच n. impurity, contamination, defilement). |
@zaaf2 what's your opinion about the other cases? Your way of dealing with possible errors makes my screenshots valuable. |
I have remained silent where I though my opinion would not add anything valuable, either because your arguments and the evidence you provided were already decisive and sometimes self-evident (especially in the case of OCR errors) or because I myself remained in doubt and was waiting for somebody else’s more informed opinion. Here are some of the cases not yet commented which I think are certain:
Here are some cases I am still in doubt:
|
|
@zaaf2 what do you think about taking one dictionary for yourself? Or some smaller list like http://drdhaval2785.github.io/o_vs_O/output1/INM.html - just 80 cases in the first, most important table. |
@gasyoun I wish I had time! But I will take a look into the PWG file to see how it works and how long it would take to go through it, and then I will let you know if I can help. |
Regarding:
Why not preserve both readings (with u and ū) since they are both correct, especially in the case of viBUkratu / viBukratu, where the RV is the source? |
both readings is not a bad idea, when RV is the source, otherwise would not makes sense, I guess. Too many artificial words are not good as well. Please do consider PWK, PWG, SCH - they are the most important ones. |
I will try the PWG. Should I open a new issue as |
Yes, new. And as PWG is big, make several topics, not all in 1. Label "bug". Assignee is not that important, but let it be Jim. He's the judge. |
Done. |
296 vidUragamana vidurAgamana - false positive |
293 vikAsaBft ― vikASaBft MW: PWG: SHS: WIL: As regards the other issues (296 - 291) I think you are right. |
Now I see this is not an orthography issue. It is a false positive. These are different words (h is not equivalent to H!). Dictionaries such as AP90 give the nominative form of a word (e.g. with -uH at the end in the case of m. words ending in u, instead of -u as MW). MW: AP90: PWG @gasyoun I think it is better when you give the reasons and (when needed) reproduce the evidences upon which your conclusions are based (as in the majority of cases you do!). Otherwise a reviewer is forced do the same amount of work to confirm those conclusions. |
@gasyoun Please forget what I said above. I was referring to cases 296, 295, 294. They are almost self-evident. As to case 295: it is perhaps indifferent how one labels it. It is enough that a correction here is not justified. As I see now, the facts you provide are enough to reach a conclusion, and perhaps it is better to be succinct than to lose time adding further elements which a knowledgeable person could supply without much trouble. |
I'm finally catching up with all the good work done here. I've been busy making some old grammar work useable . Since there are a few differences of opinion, I've made notes for the changes (and non-changes) that seem right when weighing the evidence. Here are the notes. @gasyoun and @zaaf2 might take a look at the notes. Unless you have objections, I'll install these changes as indicated, probably on Tuesday. @gasyoun I suggest you put further items in a new issue, as this seems a good break point for this batch. Then I'll close the issue after installation. Note: the items marked in the notes file with 'print error' will be mentioned in the corrections_factual file for MW. |
@zaaf2 I must excuse myself when the logic behind my screenshots is not self evident. I very much like the way you document, but I understand that in most cases it's an overkill. I choose to submit more words than to document them fully. Must be wrong, still not much choice left. |
@gasyoun Re |
@funderburkjim I have read your notes and I agree with them. |
I think I got an answer: e-mail blocker. I will fix it. |
A factual error in MW śāmbhara [p= 1065,3] [L=215618: |
Note moved above (śāmbhara ) to #131. Corrections installed. |
#127 continued. I continue to explore chaotically http://drdhaval2785.github.io/o_vs_O/output1/MW.html, 1 st table, Highest probability (One dictionary in first word and more dictionaries in second word).
1.
hemakUWya -> hemakUwya (MW print error)kUwa
means horn,kUWya
means nothing, and= -kuqya
makes only sense with kUwyaThe text was updated successfully, but these errors were encountered: