I love the verse-on-image feature! It could really earn the app great exposure. But for RTL text, we have two weird things that happen:
If there are quote marks involved in the verse (as is not uncommon on the verses one wants to put on an image), we’ll end up with a weird pair of quote marks hanging at the end, like this:
If the verse begins with “މާތްﷲ” (as several verses in GEN 1 do), the “ﷲ” incorrectly gets put first (on the right), like this:
No amount of inserting RLM characters seems to help.
Does the same problem occur in Word for example? Try pasting it into Word and experimenting with different fonts.
We had a different problem with للە in our Kurdish app. The translators did not use that word but it would magically appear in words that contained the letters ل ل ە. Words like قوللو (qulle, means tower) or کوللە (kulle, means locust). (yes, JtB would eat Allah and honey).
With experimenting I discovered that it was simply a matter of font. Some fonts turn that 3 letter combination into the name Allah, some fonts don’t. In the same way that different fonts handle the lam-alif (لا) combination differently. Even in the above sentence with the 2 examples, at least on my browser, 1 of the words does it and one doesn’t.
So my suggestion is to try a different font.
I hope that helps.
I’ve tested it, and with all fonts the behaviour is the same.
Note that this is not للە (U+0644 U+0644 U+06d5) but ﷲ (U+fdf2). It works fine in all other contexts. Only the verse-on-image feature has this problem. If a space is inserted between the Thaana letters and U+fdf2, even verse-on-text will render in the proper order (but of course, then there’s a space there).
For bug #1 with the quote marks, how about I add you to the GitHub project, so you always have access to the current form of this RTL project? What’s your GitHub username?
You can test it out in any verse involving quote marks, such as PRO 4:24 above.
(Note: The project has added a space before Allah, as a workaround to bug #2.)
@mcquayi, I see that bug #2 has been fixed. Thank you guys!
We’re still very eager to see a fix for bug #1, as this is a rather glaring, high-frequency problem. It seems that SAB is trying to be helpful, trying to patch things up for verses that contain an open quote without a close quote, by suffixing a close quote at the end of the verse, and likewise for verses that contain a close quote without an open quote, by prefixing the verse with an open quote. That makes sense, and indeed, it would be helpful if it worked as intended. As it is, it’s much worse than doing nothing.
The problem is that in RTL text, quotes are opened with right quotes (U+201D or U+2019) and closed with left quotes (U+201C or U+2018). So before deciding which end of the verse to append the missing quote mark to, SAB needs to check if the project is RTL, and if so, append to the opposite end.
Handy places to test this in the project I shared with you are LUK 4:18 (open without close), LUK 4:19 (close without open) and LUK 4:23 (mid-verse open without close).
Really looking forward to a fix for this soon!! Thanks so much!
There is a separate bug that is unique to iOS, and I’ve just emailed @david_moore1 about this. Here’s what I wrote:
Quote marks should always be “glued” to the adjacent text, never separated by wrapping the line. The scripture text in the Android app obeys this rule, but in the iOS app, it does not. Here’s an example of a closing (that is, left) quote that got wrapped to the next line:
I’m wondering if there’s some LTR logic in there that assumes it’s OK to wrap after a right quote and before a left quote. Of course, that’s backwards for RTL projects.
I investigated the final issue mentioned in the text about the hanging quotation marks and found that the left/right quotation marks that were being used don’t seem to be being handled properly by the browser when using an RTL language. Using single quotation marks works ok. But the type used here appears to cause issues because the browser is pairing them up and finding the left quotation mark appearing before the right. Even marking the direction as RTL in the HTML would not correct the problem. Dan had found some other characters that he said seemed to work ok to get around his issue I believe, but I don’t have a solution for the original issue. I did make changes related to the original issue with the verse on image that will be part of the next release.
@david_moore1, I just saw that SAB 8.6.4 has been uploaded, so I eagerly installed it, but the same problem with quote marks in verse-on-image is still present, as pictured in the top-most image in this post. Is that the issue you are referring to as supposed to be changed in this release? (Sorry I’ve jumbled so many issues into the same thread.)
I have noticed this issue several times recently as I share the verse of the day using the verse-on-image feature on social media.
The verse looks like this in the app, it is only the start of the quote so has the beginning quote, but not the end quote (which is in a following verse):
I can of course fix this by double tapping on the text and editing it, but then it does that odd thing of making the reference the same font as the text, easily seen in this screenshot compared with the above one:
And this process removes the option of adjusting the reference size, before this button is the left-most:
