LXX in Exegetical Guide Instead of Hebrew in iOS9
Hi, Friends.
I continue to have an unusual problem with the Exegetical Guide when working with Logos Bible app on my iPad (iOS 9). The Guide works acceptably when I'm working in the NT (I don't know why I can't choose the lexicons I want, but the app gets a couple of them right); but when I'm working with the OT, under the Word for Word section, all I ever get is the LXX and Greek lexicons, not BHS and Hebrew lexicons.
Anyone else having the same problem? I can find no information on how to change this. I need to work with my Hebrew lexicons, not the Greek.
Any suggestions would be greatly appreciated. The EG is useless to me until I can get the Hebrew lexicons to appear.
Thanks,
Jeff
Comments
-
To my knowledge the Exegetical Guide's lexicons are currently not user selectable in the mobile apps. We are looking into a possible rewrite of the back-end server code that serves up this information, but that's about all I know.
0 -
Hi, Kevin.
Thanks for your reply.
Exegetical Guide is a crucial reason that I use Logos, and at the moment, it is useless for OT studies. It would be great if Logos could find a resolution to this problem.
Thank you for your labors for the Master and for us.
Jeff
0 -
I see Hebrew lexicons as below
What at version of the app do you have? Which app are you using?
0 -
Hi, Graham.
Thanks for your reply.
I know that's what mine is supposed to look like. But where you have the Hebrew and Hebrew lexicons, mine only shows the LXX and Greek lexicons.
I am using version 5.0.2 (5.020894) of the Logos Bible app on an iPad Air 2.
0 -
Very strange
What lexicons are shown in the Definition section when you run a BWS against an OT word?
0 -
When I run a BWS, Hebrew lexicons appear. So I cannot understand why they do not appear in the EG.
EG has obviously defaulted to the LXX for some reason, and that appears to be the problem. Setting it to default to the Hebrew--if someone knew how to do that--would seem to be the solution.
just a guess...might be something more involved.
0 -
Can you post a screenshot of how the Word by Word section appears on the iPad - and also showing what prioritisation you have in the Logos 6 Library, particularly around lexicons?
0 -
I'm sorry, Graham, but I cannot figure out how to insert the screenshot. The insert/edit image wants a URL. The screenshot is on my computer. Can you please tell me how to do this?
thank you.
0 -
-
Jeff, taking a screenshot on your iPad and attaching it are easy. To take a screenshot on your iPad (of what you are looking at on your screen), hit the home button and power on/off button at the same time. You should hear the shutter click sound.
To attach a screenshot, select the paperclip icon in the format bar you see as you are typing your post. Then, "choose file" and select Photo Library or Camera roll (on the iPad). Find your photo in your iPad photo library and select it. Hope this all makes sense.
0 -
alabama24: thank you.
Juanita: knew how to do the screenshot, but was obviously using the wrong icon to attach it! Thank you very much.
Update: I changed the prioritization of the LXX and the BHS and I have now got Hebrew and Hebrew lexicons. The only remaining problem that remains is that in neither the Greek nor the Hebrew lexicons do I have the ones I want. This doesn't appear on the surface to be a prioritization problem because the ones EG chooses are not in my prioritization order.
Thanks Graham, alabama 24, and Juanita!
0 -
Update: I changed the prioritization of the LXX and the BHS and I have now got Hebrew and Hebrew lexicons
That is good news
The only remaining problem that remains is that in neither the Greek nor the Hebrew lexicons do I have the ones I want. This doesn't appear on the surface to be a prioritization problem because the ones EG chooses are not in my prioritization order.
And this goes back to the point that Kevin made above about limitations in the controls over which lexicons are used on the mobile apps. For that, we would need to wait for the possible rewrite he mentioned.
0 -
Thanks, Graham. Understood.
The reason I raised the lexicon issue is that yesterday, I spoke to a tech support rep who said that the power users on the forum would probably have a fix. While I understood Kevin's original note, I didn't know whether he was aware of all the info in all the discussions on the site, and I was just hoping that perhaps someone else had found a solution that hadn't made its way into the posts yet.
Short of that hope, I'll be awaiting the possible rewrite.
0 -
While I understood Kevin's original note, I didn't know whether he was aware of all the info in all the discussions on the site
From what I've seen Kevin is aware of most / all of the issues in the mobile apps[:)]
and I was just hoping that perhaps someone else had found a solution that hadn't made its way into the posts yet.
always worth asking the question....
0 -
and I was just hoping that perhaps someone else had found a solution that hadn't made its way into the posts yet.
always worth asking the question....
Yes, I learned that from my wife [;)]
0 -
Thanks, Graham. Understood.
The reason I raised the lexicon issue is that yesterday, I spoke to a tech support rep who said that the power users on the forum would probably have a fix. While I understood Kevin's original note, I didn't know whether he was aware of all the info in all the discussions on the site, and I was just hoping that perhaps someone else had found a solution that hadn't made its way into the posts yet.
Short of that hope, I'll be awaiting the possible rewrite.
Selecting which of my lexicons show up in Guides would ease the frustrations in using the Bible app. As it is now, Building NT Greek vocabulary shows up and TDNT doesn't show up which to me is a huge waste. See this thread: https://community.logos.com/forums/t/118576.aspx
Occasionally, you can get to a lexicon that is not in the list of results by finding a link to it in a lexicon that does show up. For example, DBL Greek shows up with results in the EG and when you look at the entry, usually there is a reference to TDNT with an active link. Hover over the TDNT number and usually there is a popup from the TDNT. That is great when it works. Results are not as good when trying this tip in Hebrew word studies. Links do not take you to the references resource but loop back to the DBL.
I have asked but still do not know why NIDOTTE does not show up in the Guides with results and NIDNTT does. And asked who or what makes the decision as to what lexicons do show up? I am told they are aware of inequities and are working on it. No specific answers. And now with TDOT becoming available it would be great if we could get results from it when doing Bible Word Studies in the OT as there are so few Hebrew lexicons that do show up. Giving the user access to all their lexicons in the Guides would greatly improve the useability of the app. I would be happy to pay for the app if that would ensure a better user experience. To contrast user experiences, I paid $5 for the e-sword app and it provides an excellent user experience. Well worth the price as I have over 55 free commentaries on my iPad, can use and select all the lexicons and it runs everything off line also. My opinions and my experiences.
0 -
I have asked but still do not know why NIDOTTE does not show up in the Guides with results and NIDNTT does. And asked who or what makes the decision as to what lexicons do show up? I am told they are aware of inequities and are working on it. No specific answers.
Juanita,
If I didn't give a specific enough answer here I apologize. Here's a more direct answer: it's broken. It doesn't work because there are bugs in the implementation. We know about it, are aware of it, and are working on it.
0 -
I have asked but still do not know why NIDOTTE does not show up in the Guides with results and NIDNTT does. And asked who or what makes the decision as to what lexicons do show up? I am told they are aware of inequities and are working on it. No specific answers.
Juanita,
If I didn't give a specific enough answer here I apologize. Here's a more direct answer: it's broken. It doesn't work because there are bugs in the implementation. We know about it, are aware of it, and are working on it.
Thanks for your responsiveness, Kevin. Given the Bible app is a free app, I guess I really can't say that it should work without being broken. I can just choose not to use it or accept it as is, hope for better and use the features that aren't buggy. But, IMO, I don't understand releasing an app for customers to use that is broken unless the philosophy of IT folks is to just have the majority of it work. I know the app is not intended to be a substitute for the software itself however just wanting access to all my lexicons in the Guides, I don't think, raises to that level. I would most gladly pay $25 to buy a Logos app that provides me with this access and an easy way to search in a resource provided it was not broken in part as my other paid ios apps all work. Thank you for putting up with my questions and musings.
0 -
Juanita,
Given the Bible app is a free app, I guess I really can't say that it should work without being broken.
We don't knowingly ship broken apps, free or otherwise.
To bring the context back, you said "I have asked but still do not know why NIDOTTE does not show up in the Guides with results and NIDNTT does." My response was "Here's a more direct answer: it's broken. It doesn't work because there are bugs in the implementation. We know about it, are aware of it, and are working on it."So, to say it again (just to be crystal clear), here's what is broken: "The NIDOTTE does not show up in the Guides with results and NIDNTT does."
I didn't say "the app" is broken but that the specific instance that you are experiencing in the Guide results is broken, because there's a bug. Almost all of the time, resource prioritization on the Desktop will solve the issue at hand (Guide results in the mobile apps) as it did previously in this thread for another customer.
I can just choose not to use it or accept it as is, hope for better and use the features that aren't buggy.Please report any other bugs you may find since we are already aware of this very specific bug.
By the way, Guide results are not included in the mobile apps, are not built into the mobile apps, and are not coded into the mobile apps. Guide results come from the web and are served up from Faithlife servers (as I mentioned here when I said "We know that the mobile (web-based) results don't match the Desktop results and we are fully aware of this issue, but it's not just a simple flip of a switch to solve."). This is why Guides don't work offline.
You can access the exact same Guide results from a web page if you know the exact URL and are signed in. In fact, you can completely delete all Faithlife mobile apps from any/all of your devices and you can still access the same guide information through a web browser (if you know the URL and are signed in).
But, IMO, I don't understand releasing an app for customers to use that is broken unless the philosophy of IT folks is to just have the majority of it work.
You know, whenever this happens I find it quite curious. I don't understand how statement(s) acknowledging a specific bug in Guide results experienced by a customer can morph into a blanket generalization that Faithlife's philosophy is to knowingly ship broken mobile apps, just as long as 51% or more of the features still work. Juanita, is that what you meant, or...? I wouldn't want to put words in your mouth (since I know how frustrating that can be).
Other than this particular case of web-based Guide results not matching Desktop results (which, again, is a known issue that we are working to fix on the server-side since it can't be fixed in the mobile app itself), please let us know of anything else that you find is broken in the mobile apps. I am aware of some issues (and they will be fixed in either 5.0.3 or the upcoming 5.1 release), but if there is anything else that you find that is broken please report it.BTW, I apologize for repeatedly saying the same thing over and over again but it's exasperating when something I say gets twisted into a pretzel. it kinda feels that happened here, probably completely unintended though. I just wanted to make my post pretzel-proof (I love pretzels, though).
I know the app is not intended to be a substitute for the software itself however just wanting access to all my lexicons in the Guides, I don't think, raises to that level. I would most gladly pay $25 to buy a Logos app that provides me with this access
To my knowledge our mobile apps will continue to be free. When the Guide results issue is fixed it won't cost you anything.
and an easy way to search in a resource provided it was not broken in part as my other paid ios apps all work.
Please create a new thread with a bit more detail; searching in a resource is not related to the topic of Guide results, and I am unaware of any problems with searching in a resource.
0 -
Kevin,
Thanks for your detailed response. Clearly, I misunderstood what you meant by "broken". I wrongly interpreted broken to apply to my entire issue with all my lexicons not being accessible to me in the guides of which the NIDOTTE not showing up was the example I stated. I thought broken to be a far worse situation than a bug and not equivalent expressions at all
As far as prioritizing lexicons solving my problem, it doesn't. TDNT and Vine's are all prioritized higher than BDAG and the EDNT and they do not show up in results. Prioritizing NIDOTTE all the way to the top doesn't change anything.
You said;
Almost all of the time, resource prioritization on the Desktop will solve the issue at hand (Guide results in the mobile apps) as it did previously in this thread for another customer.
However, Jeff Pollard made a distinction regarding resources and how prioritizations affect them:
Update: I changed the prioritization of the LXX and the BHS and I have now got Hebrew and Hebrew lexicons. The only remaining problem that remains is that in neither the Greek nor the Hebrew lexicons do I have the ones I want. This doesn't appear on the surface to be a prioritization problem because the ones EG chooses are not in my prioritization order.
IOW, lexicon prioritization doesn't help me get the lexicons I want in the Guides.
Let me respond to the following so that you better understand me:
But, IMO, I don't understand releasing an app for customers to use that is broken unless the philosophy of IT folks is to just have the majority of it work.
You know, whenever this happens I find it quite curious. I don't understand how statement(s) acknowledging a specific bug in Guide results experienced by a customer can morph into a blanket generalization that Faithlife's philosophy is to knowingly ship broken mobile apps, just as long as 51% or more of the features still work. Juanita, is that what you meant, or...? I wouldn't want to put words in your mouth (since I know how frustrating that can be).
Kevin, my saying that FL ships a broken app made sense to me given I understood broken to mean not that I cannot get the NIDOTTE, but also cannot get the TDNT, Vines and let me add TWOT and there are probably others. IOW, my main issue is I cannot get all the lexicons in results. Only repeating myself to be clear. I don't know if these are bugs to report or limitations in the app. At this point, I am guessing they are not bugs based on this:
Other than this particular case of web-based Guide results not matching Desktop results (which, again, is a known issue that we are working to fix on the server-side since it can't be fixed in the mobile app itself), please let us know of anything else that you find is broken in the mobile apps. I am aware of some issues (and they will be fixed in either 5.0.3 or the upcoming 5.1 release), but if there is anything else that you find that is broken please report it.
That is indeed the good news that FL is working on the server side to fix the issue. Thank you for giving me the benefit of the doubt in interpreting what I said. E-communications leave a lot to be desired.
0
