BUG: Command Box Won't I Look Up Spanish words in my Spanish Dictionary

I have a Spanish-English dictionary in my library. However, when I typed "look up bosquejo" in the Command Box, it didn't execute the Look Up feature.

However, the Look Up feature in the Context Menu does work.

If Look Up works for Spanish words in the Context Menu, shouldn't they also work in the Command Box? Isn't this the same functionality?

Find more posts tagged with

Desktop App

Comments

MJ. Smith

I don't have time at the moment to test this but I suspect the context menu passes a language code and that in the command box you did not enter a language code.

NB.Mick

I have a Spanish-English dictionary in my library. However, when I typed "look up bosquejo" in the Command Box, it didn't execute the Look Up feature.

From my tests, it seems the command box understands look up as well as lookup without a space in between.

It also seems that look up accepts headwords in

English
Latin
Greek (presumably Hebrew as well)
the current UI language (I tested by switching between German and Spanish)

so look up bosquejo will work if you are in the Spanish UI (for those readers who wondered, MWSED just taught me that bosquejo is a noun that means outline, sketch or draft). The command uilang es is your friend.

Kiyah

https://community.logos.com/discussion/comment/1274000#Comment_1274000

I don't have time at the moment to test this but I suspect the context menu passes a language code and that in the command box you did not enter a language code.

How do I include the language code? Can I combine a language code with the Look Up command so that it looks up a Spanish word without having to change my UI?

Dave Hooton

https://community.logos.com/discussion/comment/1274065#Comment_1274065

Can I combine a language code with the Look Up command so that it looks up a Spanish word without having to change my UI?

You should be able to specify lookup bosquejo in {Spanish-resource}, so I created a bug report. So you might try

open {Spanish-resource} to bosquejo

There is no language code with lookup, as lookup bosquejo should work.

Kiyah

https://community.logos.com/discussion/comment/1274120#Comment_1274120

You should be able to specify lookup bosquejo in {Spanish-resource}, so I created a bug report. So you might try

open {Spanish-resource} to bosquejo

There is no language code with lookup, as lookup bosquejo should work.

Thanks Dave.

Andrew Batishko

I have a Spanish-English dictionary in my library. However, when I typed "look up bosquejo" in the Command Box, it didn't execute the Look Up feature.

However, the Look Up feature in the Context Menu does work.

If Look Up works for Spanish words in the Context Menu, shouldn't they also work in the Command Box? Isn't this the same functionality?

Looking up the word requires that the application know the language of the word. The resource tags the words with their language, allowing the context menu to work as desired. However, when you use the command box, it can only assume that you are typing using the current application language (English in your case), and that prevents it from being able to find the headword in any resources (which prevents it from suggesting the look up command). If you were running the application in Spanish, then it would be able to do the lookup from the command box.

I recommend creating a suggestion at https://feedback.faithlife.com/boards/logos-desktop-app/ to support look ups from the command box in languages other than the current setting.

Kiyah

https://community.logos.com/discussion/comment/1274253#Comment_1274253

The resource tags the words with their language, allowing the context menu to work as desired.

So does this explain why the context menu look-up for 'bosquejo' works for these two Spanish resources:

Merriam-Webster's Spanish-English Dictionary

Nueva Biblia de Las Américas (NBLA)

...but does not work for these two English resources?:

The Catholic Encyclopedia (15 vols.)

Encyclopedia of Ancient Christianity (3 vols.)

Since the resources are in English it's signaling to the program to look for English words and so doesn't recognize the Spanish words these resources contain?

Andrew Batishko

https://community.logos.com/discussion/comment/1274260#Comment_1274260

...but does not work for these two English resources?:

The Catholic Encyclopedia (15 vols.)

Encyclopedia of Ancient Christianity (3 vols.)

Since the resources are in English it's signaling to the program to look for English words and so doesn't recognize the Spanish words these resources contain?

Pretty much, yes. Foreign language words can get tagged correctly in resources that are primarily a different language, but in these cases it is not. I think that's pretty much never done for bibliographic citations, but you might see it in other places, particularly if a resource has a lot of text from a secondary language.

MJ. Smith

https://community.logos.com/discussion/comment/1274260#Comment_1274260

This is how I check if a word has the right language tag - note the two English language resources I expanded one with and one without the Spanish language tag.

Kiyah

https://community.logos.com/discussion/comment/1274265#Comment_1274265

This is how I check if a word has the right language tag - note the two English language resources I expanded one with and one without the Spanish language tag.

Thanks MJ. Helpful.

NB.Mick

https://community.logos.com/discussion/comment/1274253#Comment_1274253

when you use the command box, it can only assume that you are typing using the current application language (English in your case), and that prevents it from being able to find the headword in any resources (which prevents it from suggesting the look up command).

Not to doubt your expertise, but my tests seem to indicate that

look up accepts headwords in

English
Latin
Greek (presumably Hebrew as well)
the current UI language (I tested by switching between German and Spanish)

and therefore it seems not to work with the assumption you stated, but with some kind of prioritization across headwords in five or more languages (Aramaic and the pseudo-language "Translit" may also be among the headwords that are understood). I'm glad that so much is working as it should. On the other hand, the accepted headwords will be in large indexes drawn from dozens of resources for the biblical languages as well as English - presumably there is only a very small number of resources with headword indexes for non-English resources, thus it's probably even easier to not cut them off (will an index of command-lookable headwords be built everytime at application start? Or is it a restricted search against a full index?)

Andrew Batishko

https://community.logos.com/discussion/comment/1274272#Comment_1274272

look up accepts headwords in

English

Latin

Greek (presumably Hebrew as well)

the current UI language (I tested by switching between German and Spanish)

Yes. I simplified for the purposes of the report on this thread and left out talking about Greek/Hebrew/Aramaic/Latin lemmas (I don't think transliterated lemmas are supported). Original language terms are all only lemmas, and are handled a bit differently than modern language terms are handled.

I hadn't checked to see if we fall back to searching English headwords when running in a non-English UI, but it appears that you are correct. It's not uncommon for us to fall back to English in a variety of places.

Unfortunately, due to the way that things are set up, it's not a simple task to check all languages for matching headwords.

NB.Mick

https://community.logos.com/discussion/comment/1274276#Comment_1274276

Unfortunately, due to the way that things are set up, it's not a simple task to check all languages for matching headwords.

Thanks for looking into this and all the info!

Dave Hooton

https://community.logos.com/discussion/comment/1274262#Comment_1274262

Foreign language words can get tagged correctly in resources that are primarily a different language, but in these cases it is not. I think that's pretty much never done for bibliographic citations, but you might see it in other places, particularly if a resource has a lot of text from a secondary language.

english:biblia yielded many results but no Lookup in the Context menu

spanish:biblia yielded some results but with Lookup in CGRT (Continuum Glossary of Religious Terms) and DPF (Dictionary of Phrase and Fable). Both link to the article on Bible. DPF has an article on Bib′lia Pau′perum (headword:"Biblia Pauperum"), and an english:Biblia, otherwise they don't have a headword:Biblia. So, is this LCV at work?

Andrew Batishko

https://community.logos.com/discussion/comment/1274305#Comment_1274305

So, is this LCV at work?

No. That's the result of some fuzzy matching in the headword lookup. So, for example, english:bibles can have a context menu lookup for the same Bible article in CGRT, even though the headword is just Bible.

Dave Hooton

https://community.logos.com/discussion/comment/1274379#Comment_1274379

for example, english:bibles can have a context menu lookup for the same Bible article in CGRT, even though the headword is just Bible.

Sorry, Andrew but I'm not following.

If you meant english:bible (as "bibles" has no match in CGRT), I'm still none the wiser.

Andrew Batishko

https://community.logos.com/discussion/comment/1274459#Comment_1274459

for example, english:bibles can have a context menu lookup for the same Bible article in CGRT, even though the headword is just Bible.

Sorry, Andrew but I'm not following.

If you meant english:bible (as "bibles" has no match in CGRT), I'm still none the wiser.

Well... apparently you can ignore that comment. At the time I wrote it, I thought I could recreate that behavior. Now I have no idea what I was seeing... I know that there is some fuzzy matching of headwords that can happen, but I don't know exactly how it behaves.