When I right click on the text or a specific word, I used to get a pop-up window on that word with an option to hear it pronounced in Hebrew or Greek. Now that feature is not showing. How do I get this back?
This will show up in Greek/Hebrew original language bibles (such as NA28) or in bibles with a reverse interlinear (such as the NIV), associating the English word with a Greek/Hebrew original word. In both cases, the context menu that comes up after right-clicking will show the "Pronounce" icon when you selected the "lemma" part of the context menu (the one with the circle icon)
EDIT:
Welcome @Jay Reed
You need to ensure you have the lemma selected on the left side of the context menu
Graham
Available Now
Build your biblical library with a new trusted commentary or resource every month. Yours to keep forever.
Hi, Last year I read through this devotional, For The Love of God Vol. 1. Every day would give a short summary, and the four chapters of the bible to be read that day. If I clicked on the first selection (say Gen 1) it would take me there to that reference in my preferred bible. At the end of that chapter was a link to the…
… when the update involves a fix for Mac OS? I've always wondered about that.
Ok don't laugh… This may be a dumb question. I am no biblical scholar, I am a 30 yr college student who just wants to understand how to read and study her Bible better. So my question is in BDAG it states "extended Definitions are in bold roman" and "English formal equivalents are in bold italic/normal italic." Then goes…
I accidently did something that caused the Bible book titles to disappear from Scripture on my iPad. Does anyone know how to help me get them back? Chapter titles and verse numbers are still there. Titles are still there in my desktop version, but not in my iPad. Thanks!
Is there a reason why the Hebrew keyboard maps used by the keyboard picker are not aligned with the old Logos Biblical Hebrew Keyboard? This morning I tried it out for the first time (I'm used to using the Windows Language Bar), and couldn't figure out why aleph wasn't showing up where it was "supposed" to be. It also…