BUG: Search Results for the Thai Bible do not wrap properly
I recently purchased the Thai Holy Bible which became available on Logos.com. Although I am glad to finally have a Thai Bible in Logos, I have noticed a number of problems with it especially in Logos 4. For instance, verses do not wrap properly in the search results as you can see below.
I imagine that this is due to the fact that the Thai language does not use spaces between each word but only between larger units of thought. The algorithm used in the search results panel seems to be wrapping the results based on the spaces between words. Since Thai does not use a space between individual words, extra long lines do not wrap properly. When you open the resource itself in a panel, the lines wrap correctly as you would expect which you can also see above. The lines also wrap correctly in the search results window of Libronix 3.
This same line breaking problem is also present when viewing the Thai Bible on an iPod or iPhone. Extra long lines do not wrap properly but instead are simply cut off which is a much greater problem on these devices because it means there is no way to read the end of many verses. I imagine that these problems were simply overlooked due to a lack of Logos employees that can read Thai.
The default text size and font used is also very large. Even at the lowest setting, the text size is still fairly large. This is true both in Logos 4 on the computer and in the app on an iPhone. In the iPhone app, this is an even greater hassle because lowering the font size so you can read the Thai Bible comfortably means that all other resources will display using too small of a font. Also, on the desktop, changing the default font does not change the font used to display this resource. Perhaps there needs to be an option in the program settings for changing the fonts used for foreign languages other than Greek, Hebrew, etc....
Finally, I believe that the meta information concerning the date this version was produced is incorrect. Both in the software and on your website, you state that this is the 1973 version. Unless I am mistaken, no such version was ever produced in Thailand. The text in this resource seems to be identical to the 1971 version put out by the Thai Bible Society which I have in print.
Thank you for all your hard work in producing Logos 4 and in making a Thai version of the Bible available. I look forward to seeing these problems resolved and to using the Thai Bible in Logos for many years to come.
Brad Beckett
Comments
-
Brad Beckett said:
Extra long lines do not wrap properly but instead are simply cut off which is a much greater problem on these devices because it means there is no way to read the end of many verses.
I have reported this non-wrapping for long lines before. At that time, Logos had said that it was operating correctly and as they intended. On reflection, I think that answer is wrong, and your examples show that this is something that must be changed and fixed to work as we expect.
Thanks for reporting this bug. I hope it gets the attention it requires.
0 -
Brad ~ I'll submit your report to development. Thanks.
0 -
Thanks Melissa
0 -
See also: http://community.logos.com/forums/p/22829/170241.aspx#170241
Simon
0 -
Thai script formatting on iP-hone/od/ad devices now seems to be working with the release of the iPhone app version 1.5 update.
See: http://community.logos.com/forums/p/22829/170241.aspx#170241
0 -
Yes, Thai script now wraps properly on the iPhone app and on the latest beta release (4.2a Beta 2) of the desktop software. Thank you Logos for all your hard work.
The only problem I am still having is that the font size is abnormally large by default. You can adjust this in the program settings, but doing so makes the English font sizes of all other resources too small especially on the iPhone app. Also, there doesn't seem to be a way of selecting the font used for rendering Thai script in Logos 4. Changing the default font does not change the font used to render the Thai script.
0 -
Brad Beckett said:
The only problem I am still having is that the font size is abnormally large by default. You can adjust this in the program settings, but doing so makes the English font sizes of all other resources too small especially on the iPhone app. Also, there doesn't seem to be a way of selecting the font used for rendering Thai script in Logos 4. Changing the default font does not change the font used to render the Thai script.
You can also change the font size per resource by using the text size slider at the top of the resource panel menu. This setting is remembered the next time you open that resource. That way you can leave the default font size where you want it for English resources and set the Thai Bible to a smaller size.
0 -
Yes, in Logos 4 you can change the font size on a resource by resource basis. However, this cannot currently be done in the iPhone app as far as I know. For me, this is not that big of an issue. Not being a native Thai reader, I tend to prefer a larger font size in order to make out the details of the intricate script. Native Thais however like my wife generally use much smaller font sizes which of course would enable many more verses to be displayed on the screen at one time.
Also, when you reduce the font size of the Thai script in Logos 4, the Thai characters become quite fuzzy. This is likely due to either the particular anti-aliasing function that is used on fonts in Logos or the particular font that is used to display Thai script. Having the ability to change the font used to render Thai script would likely solve this problem. The iPhone app seems to use a different font to display the Thai script, and it is much clearer at smaller font sizes. However, the smallest font size available for Thai script on the iPhone app is still quite large.
Thanks for all your help.
0 -
Logos 4 Thai font rendering is much improved. However, the iphone app is off now. It was working acceptably before.
0 -
Nathaniel Heng said:
Logos 4 Thai font rendering is much improved. However, the iphone app is off now. It was working acceptably before.
The issues you are seeing have been fixed in an upcoming release. Be on the lookout for that when we update the app.
Thanks,
0
