I would also add that, while this is the most damaging Devanagari (Hindi) script rendering problem, there are many aspects of it that Logos doesn't render well. Many of the vowel markings are poorly placed (many of the " े" and the " ि ") and no "combined consonants" are rendered well (they merely include the " ् " symbol under them, instead of making changes to the consonant itself). These all cause Devanagari-based works to be poorly displayed in Logos.
BUG: Incorrect Rendering of Hindi Font
Derrick Pemberton
Member Posts: 79 ✭✭
I have been formatting a new Urdu Devanagari (Hindi script) translation of the Bible for Logos. I have tried several Hindi fonts. All of them look fine in Logos, except for one element. A certain Hindi vowel marking isn't rendering correctly in Logos. This only happens when the vowel comes at the end of a word. It happens in all fonts. For example, कि is a common word. In Logos it always appears more like क ि (only with the horizontal line connecting them) when the resource is open. However, it appears correctly when copied into the Logos search bar. It also appears correctly in the search results. I have attached a screenshot to demonstrate this. Compare the blue highlighted text on the right with the text in the search bar. Any solutions?
0
Comments
-
I would also add that, while this is the most damaging Devanagari (Hindi) script rendering problem, there are many aspects of it that Logos doesn't render well. Many of the vowel markings are poorly placed (many of the " े" and the " ि ") and no "combined consonants" are rendered well (they merely include the " ् " symbol under them, instead of making changes to the consonant itself). These all cause Devanagari-based works to be poorly displayed in Logos.
0 -
Thanks for the bug report. I will investigate the rendering issues.
0 -
Just an additional note. Both the "combined consonants" and the vowel markings are displayed correctly when viewed in the Power Lookup tab, in the search bar and results, and when the text is copied to a word processor. It is only when viewing the Bible itself that it renders improperly.
While this may not be a major problem (it could be), search results are displayed for only the consonants in the word. Any combination of vowel markings may be included, meaning that you actually could see many words that you don't want to see.
0 -
For searching, you can use the [match marks] syntax before the word to match vowel marks. See http://wiki.logos.com/Search_Matching_Commands
0 -
Awesome! There is so much that Logos can do!
Let me know of any progress on the other font issues.
Thanks!
0 -
You may have already figured this out, but the vowel marking problem seems to be related to the order that some letters are types being different than the order in which they must be displayed.
For example: क = ka; कि = ki. So you can see that "ki" requires the vowel marking to be swung around before the consonant, though it is typed--and spoken--after it.
If there is anything I can do to help, please let me know!
Thanks!
0 -
Not to rush you or anything [:)] but has any progress been made on the font rendering issue? It is fatal for any devanagari work in Logos. I would like to get this translation into Logos as soon as possible.
Thanks for the help!
0 -
You expect a fix in a week? In my experience it takes on average a year to get bugs fixed. You're lucky to even get it noticed in the first week. I've often had to wait months.
Mac Pro (late 2013) OS 12.6.2
0 -
Doesn't mean I can't ask. It is very important for me, so I will give a nudge every now and then. I'm grateful that it is being worked on at all.
0 -
Of course you can. I wish you luck. I just don't have very good experiences myself.
Mac Pro (late 2013) OS 12.6.2
0 -
Hello again! Any progress or projections?
0 -
It's still on my list; I haven't gotten to it yet.
0 -
How does this look? This is on Windows.
Let me know if you have more specific cases that you'd like me to check.
0 -
Sorry! For some reason I wasn't being notified of new posts! Actually, I just decided to look at it again in Logos after crossgrading to version 6. As far as I can tell, the issues are resolved! Thanks! This is a huge help for me. I will let you know if I see any other problems, but it looks good right now.
0
