Qksms: Arabic characters clipped in message view

Created on 17 Jul 2018  ยท  9Comments  ยท  Source: moezbhatti/qksms

Arabic characters at the start side of the message bubble seem to be clipping early, resulting in part of the message not being visible.

I suspect the culprit to be TightTextView

bug

Most helpful comment

Hey @yarons, sorry for all the confusion. I just realized that while I did indeed fix the issue, I hadn't released the fix yet. And so this is why you're still experiencing the issue in 3.6.3

I just tested using your text and I can confirm that the issue has been resolved, and will be pushed out in 3.6.4, hopefully later this week :)

All 9 comments

I can confirm it still persists if we used system fonts.

why it closed? is it fixed? I wait just for that fix to reuse the application

yep, it's fixed

well I am using Hebrew and it shown better but still cutting the first letters

@schapira can you give me some sample text to test with? And can you let me know what version you currently have installed?

There you go:
Screenshot_2019-03-12-16-28-37-425_com moez QKSMS

It starts with ืคืš ืžื“ื™ื ื™, but it should actually start with ืžื”ืคืš ืžื“ื™ื ื™.
I'll also add Arabic transliteration for reference:
Appears as ูพุฎ ู…ุฏูŠู†ูŠ
Instead of ู…ู‡ูพุฎ ู…ุฏูŠู†ูŠ

Same goes to all the following lines after.

@yarons can you please copy and paste the original text onto github? I'd like to test it with this exact same text on my own device

And can you confirm which version of the app you're using?

@moezbhatti
This is the full message:
ืžื”ืคืš ืžื“ื™ื ื™, ืžื”ืคืš ื—ื‘ืจืชื™, ืžื”ืคืš ื‘ื”ืคืจื“ืช ื”ื“ืช ืžื”ืžื“ื™ื ื”. ืื™ืŸ ืžื”ืคืš ื‘ืœื™ ืžืจืฆ ืฆืคื• ื‘ืงืžืคื™ื™ืŸ ื”ื—ื“ืฉ http://bit.ly/MRZvideo ืœืชืžื™ื›ื” ื”ืฉื™ื‘ื• 1 ืœื”ืกืจื” ื”ืฉื™ื‘ื• 0

With line breaks as displayed in the app:
ืžื”ืคืš ืžื“ื™ื ื™, ืžื”ืคืš ื—ื‘ืจืชื™, ืžื”ืคืš
ื‘ื”ืคืจื“ืช ื”ื“ืช ืžื”ืžื“ื™ื ื”. ืื™ืŸ ืžื”ืคืš ื‘ืœื™
ืžืจืฆ ืฆืคื• ื‘ืงืžืคื™ื™ืŸ ื”ื—ื“ืฉ http://bit.ly
/MRZvideo ืœืชืžื™ื›ื” ื”ืฉื™ื‘ื• 1 ืœื”ืกืจื”
ื”ืฉื™ื‘ื• 0

My version:
Screenshot_2019-03-12-17-17-14-463_com moez QKSMS

Thanks!

Hey @yarons, sorry for all the confusion. I just realized that while I did indeed fix the issue, I hadn't released the fix yet. And so this is why you're still experiencing the issue in 3.6.3

I just tested using your text and I can confirm that the issue has been resolved, and will be pushed out in 3.6.4, hopefully later this week :)

Was this page helpful?
0 / 5 - 0 ratings