Incorrect headwords in Lewis and Short's Latin Dictionary
The headwords in the new Lewis and Short Latin Dictionary seem to be a little messed up, in a similar way to the problems I pointed out in the Autenrieth Homeric dictionary.
Take the word "liber" for example. Right-clicking on the dictionary entry shows that the headword is "libeo", the entry just before it, which is a mistake. This means that clicking on a form of "liber" in a given Latin text won't pull up the Lewis & Short, because the entry for "book" is linked to "libeo" instead of "liber".
I'm not sure what's causing this, however. It would appear that it only happens for entries that begin with a numeral. For instance: "1. germānus, a, um" has the incorrect headword "germānĭtus". In the same way, "gero" points to "gerimo", etc.
This means that the L&S won't show up in the right-click menu for more polyvalent words, greatly reducing the value of the electronic dictionary.
Comments
-
I'm not sure what's causing this, however. It would appear that it only happens for entries that begin with a numeral. For instance: "1. germānus, a, um" has the incorrect headword "germānĭtus". In the same way, "gero" points to "gerimo", etc.
You are right. I just checked servus to find the same.
Have joy in the Lord!
0 -
Many headwords also have hyphens in them, e.g., prae-dūco, which prevents the word from being looked up if the hyphen isn't included. It also prevents syncing between L&S and other Latin dictionaries:
I had to manually align these two entries in these two dictionaries. Syncing only works sporadically.
If the hyphen needs to be in the headword (I'm not sure it should be), then a second headword without the hyphen should also be added for each of those entries. There's a lot of them.
MacBook Pro (2019), ThinkPad E540
0 -
[:(]
0 -
It seems that computers would be very good at scanning through the headwords of Lewis and Short and removing the hyphens. Do you suppose that Logos might want to do something like that in order to really let this dictionary become the useful tool that it might be?
0 -
If the hyphen needs to be in the headword (I'm not sure it should be), then a second headword without the hyphen should also be added for each of those entries.
The surface text needs to match the printed text but the headword tagging does not. This appears to be a simple case of QA missing the obvious.
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0 -
If the hyphen needs to be in the headword (I'm not sure it should be), then a second headword without the hyphen should also be added for each of those entries.
The surface text needs to match the printed text but the headword tagging does not. This appears to be a simple case of QA missing the obvious.
Before I got BAG and then BDAG I had the Middle Liddell. I seem to recall a similar problem there though I just checked and it seems to be fixed now.
george
gfsomselיְמֵי־שְׁנוֹתֵינוּ בָהֶם שִׁבְעִים שָׁנָה וְאִם בִּגְבוּרֹת שְׁמוֹנִים שָׁנָה וְרָהְבָּם עָמָל וָאָוֶן
0 -
Thanks for bringing this to our attention. The text production department is aware of this issue and will release an update as soon as possible.
0 -
Thanks for bringing this to our attention. The text production department is aware of this issue and will release an update as soon as possible.
Thanks Mike. However, you say "this issue" when there are two issues reported:
- Entries beginning with numbers don't have headwords and therefore get associated with the previous entry's headword.
- Headwords shouldn't have hyphens, even if the entry does.
I'm hoping that both of these issues get fixed when the resource gets updated.
MacBook Pro (2019), ThinkPad E540
0 -
Yes, both will be fixed in the update. [:)]
0 -
you say "this issue" when there are two issues reported:
Three, actually. There is also Lewis and Short Latin Dictionary ready but Harpers' downloads ? A resource should have the same name on logos.com, in blog posts and the like, and in Logos itself.
Mac Pro (late 2013) OS 12.6.2
0 -
you say "this issue" when there are two issues reported:
Three, actually. There is also Lewis and Short Latin Dictionary ready but Harpers' downloads ? A resource should have the same name on logos.com, in blog posts and the like, and in Logos itself.
It's not any different than Louw-Nida:
https://www.logos.com/product/199/greek-english-lexicon-of-the-new-testament-based-on-semantic-domainsOn the other hand, BDAG does include the common name as part of the title:
https://www.logos.com/product/3878/a-greek-english-lexicon-of-the-new-testament-and-other-early-christian-literature-3rd-edMacBook Pro (2019), ThinkPad E540
0 -
It's not any different than Louw-Nida:
https://www.logos.com/product/199/greek-english-lexicon-of-the-new-testament-based-on-semantic-domainsHow is it not different? Looks to me like that one has exactly the same name on the product page and in the library.
BDAG also has the same name, except that the abbreviation is added after the title on the web, while it's in the abbreviated title column in Library.
Mac Pro (late 2013) OS 12.6.2
0 -
It's not any different than Louw-Nida:
https://www.logos.com/product/199/greek-english-lexicon-of-the-new-testament-based-on-semantic-domainsHow is it not different? Looks to me like that one has exactly the same name on the product page and in the library.
Ah, I misunderstood your point. I was pointing out that the common name isn't used in the product name. I agree with your concern, but I think that fixing it is not necessarily a resource issue, since the resource has the correct title, but the product page does not.
MacBook Pro (2019), ThinkPad E540
0 -
True, but this is the Noet forum. I don't think we necessarily have to separate things here, the way we do between the L5 and the Website forum.
Besides, this thread seemed to be monitored, while the other one seems overlooked.
Mac Pro (late 2013) OS 12.6.2
0 -
It's really a shame that the arrival of this dictionary, which should be a cause for celebration, is instead marred by poor quality control at Logos. I suppose I'll be happy when it gets fixed in a few weeks.
But why not just wait a little and put it out when it works?
0 -
Yes, both will be fixed in the update.
confirm: fixed! Thanks!
Have joy in the Lord!
0 -
Thank you, Logos!0
-
Thank you for fixing this!
I can't seem to download this resouce to my mobile device, however, has it been released for download?
0
