I know the Hebrew vowels have NEVER lined up underneath the consonants, but I keep expecting that to be addressed soon, and it never is. It is very hard to read things with the vowels all messed up.
Wyn, here's an update:
We have been actively researching this issue and we were not having any success finding a problem on our end, so we took our question directly to the top. Google's Android development team hosts a weekly Q & A session for developers via their Google+ Hangout system and we were lucky enough to get to ask two questions of the team.
Our first question described the issue, along with screenshots and specific Hebrew words that did not display correctly. We were told that the team was aware of the issue (it's a problem in the entire Android system, not just the Logos apps) and it has actually already been fixed internally and "will be available in the next release of Android". My personal interpretation of that statement is that the issue will be resolved in Key Lime Pie, whenever this is released.
Later in the session, after some internal discussion amongst the Logos Android team, we asked a second question: "Given that it will be a very long time before the majority of our users have this future release of Android, is there anything we can do right now to fix the issue in our app?" Their answer: a resounding and definitive "No". They told us the fix for the problem involved changes to multiple core components of the Android system (I believe he said four different areas) and they strongly discouraged us from trying to implement our own fix.
Normally these Q & A sessions are posted to Youtube after the session is over, but to our great misfortune there seems to have been an error with our particular video (found here) and it has not been posted to Youtube. We were planning on making a post with this information and links to the relevant sections of the video, but unfortunately that does not seem to be possible.
All that said, the Logos team is always hard at work finding answers to your problems. Unfortunately in this case the solution is out of our hands and will only be resolved with time.
Drew,
Thanks for taking the time to explain. I really appreciate it.
Wyn
Yes, it's good to hear this news and look forward to yet another new version of android.
Hi there,
Even on IPAD platform, the hebrew vowel points do not aligned as well. Do you know why?
Best regards,
Eric
I know that Android has challenges for displaying characters with complex diacritical marks. What I don't understand is why Olivetree Bible Reader can display the Hebrew with proper vowel points and Greek with proper accents, but Logos cannot.
Here is Genesis 1:1 in Olivetree Bible Reader:
Here is Logos 2.11 for Android on the same passage:
There are similar discrepancies in the display of Greek with accents. Although the Greek text is fine when reading the NA27, pop-ups windows, searches and Bible word studies do not display accented characters in Logos. But Bible Window has no trouble with this font.
I am using Logos with Android ICS 4.03 on an Acer A100 tablet and ICS 4.04 on a Samsung Galaxy S3.
I hope Logos is able to find a way to resolve this. If we have to wait for Google to solve it, most existing phones and tablets will never display Greek or Hebrew correctly. I know Logos has much more complex multilingual documents to display, so the task is more difficult. But it is a shame, because these limitations reduce the utility of many of the wonderful Bibles and reference books in Logos.
Yes, even while I do not challenge what Google says about the inherent problem with the current version of Android, it is true that several softwares seemed to have found a way around the problem. In addition to olivetree, there is Perpetua, a flashcards app.
I encountered the same Greek & Hebrew problem.
From a software engineer's perspective, I believe Logos needs to improve.
Pray that our Lord help Logos to resolve this problem ASAP.
Hello Harry,
As I posted in another forum, Olive Tree and others most likely resolve this by resorting to using non-unicode fonts. You might be aware that Bibleworks does this on Windows as well. However, what this means is that what you see in the bibleworks font will be gibberish in another font. This has caused some frustration for some of my students who wonder why their Hebrew or Greek didn't turn out when then emailed an assignment. At any rate, using non-unicode fonts may give the appearance of a fix, but it is a step back in some ways. Furthermore, it would be extremely tedious to reset the type for a temporary fix like this.
That said, I share your frustration with this issue. I just upgraded my tablet to Jelly Bean in hopes the Hebrew would be sorted out, but no luck for now. Soon I hope.
