Open funderburkjim opened 7 years ago
such instances of headword errors in MW are now rare
Yes, it's a pleasure indeed. This case
SayanEkadaSI:MW
SayanEkAdaSI:PW,PWG,SHS,SKD,VCP,WIL,YAT
Which is like 1 authority dictionary versus more than 2 different (including authority) dictionaries, where the only difference is a single letter (not even a letter, but let's say quantity of a sound), which is not a difference in the nasals (including anusvara orthographic convenience) and not doubling of consonants (old SKD and VCP style). Seems (I have suspected it) that the o vs O is not yet over. If @funderburkjim has no easy way to provide me with such lists of suspected words, I'll have to ask @juhnowski to dive with him into it. He would be good in some more technical aspects ( @drdhaval2785 what's your opinion?) of Cologne, but as headwords cleanness is number one aspect for me personally, this is how I see it.
Sounds like a worthy investigation. Probably could be done by analysis of hwnorm1c.txt.
If @juhnowski can help, that seems like a good choice now. At least for my part, I need to focus on the AS to IAST conversion, and on the meta-line project, as well as your simple-sanskrit project. So best not depend on me for this investigation.
So best not depend on me for this investigation.
Understood.
Good morning! I'm ready to go to work, but I need detailed comments.
There is no need to reinvent the wheel. The same work was done in o_vs_O method as we used to call it. https://github.com/sanskrit-lexicon/CORRECTIONS/issues/151
The correction submission based on that pattern is still pending. Time for Marcis to actually find out a correction submitter.
I thought o_vs_O things are over, but it turns out that there are still cases around.
While working with IAST conversion for Yates, the Yates headword
SayanEkAdaSI
came to attention for Asháṛha spelling.
When looking to MW, found headword spelling
SayanEkadaSI
Since
ekAdaSa
is 'eleven', and since several dictionaries (:PW,PWG,SHS,SKD,VCP,WIL,YAT) have the Yates spelling, it is clear that this is an instance of MW headword spelling error, and is a print error.We can congratulate ourselves that such instances of headword errors in MW are now rare. 😃