trunks-social / trunks-public

Issue tracker project
44 stars 3 forks source link

Some Unicode (?) characters not showing correctly in Android client #286

Closed MrThistle closed 6 months ago

MrThistle commented 11 months ago

Some accounts use special characters and they don't render correctly. Also, when I try to enter "rational numbers like 1/5" they are not showing correctly. See two attached screenshots.

Phone: Asus Zenfone 8 with offical Android 13 and all latest updates. Trunks: The latest version 1.2.12:217

Phone primary language is English, secondary Czech, sometimes I change the primary language to Czech (but usually only for a while). I have seen it also some time ago, so it is not a new bug. In the message editor, I am trying to write 1 (top index), 1/2, 1/3, ... as available on "1" key in the keyboard when numbers are visible (long press the "1" key).

Trunsk - Special characters (wrong, small) Trunsk - Account name (wrong, small)

amayasnep commented 8 months ago

I’m having the same issue with the iOS client. Trunks will display everything correctly upon initial sign in, but shortly thereafter any text that isn’t plain English throws errors. My user profile on Mastodon includes French, Spanish, Greek, Traditional Mandarin Chinese, and some emojis.

Phone: iPhone 12 Pro OS: iOS 17.3.1 (latest) Trunks: The latest version 1.2.17

IMG_0611

Decad3nce commented 8 months ago

This happens on iOS as well.

I just made a beta build for 1.2.18 that should address this.

It was a combination of encoding issues along with font issues. :(

MrThistle commented 8 months ago

Hi, I am sorry but the issue is not resolved yet in 1.2.18:259 (Android, font Roboto). I tried to write all "shifted" characters in numeric keyboard starting with 1, 1/2 up to 1/10 Screenshot_20240318-200940857_1 FYI @Decad3nce - if you prepare some beta version with extra logging or so, I will gladly help in investigation.

amayasnep commented 8 months ago

The same issue I showed before persists even now.

Decad3nce commented 8 months ago

Seems to be https://github.com/flutter/flutter/issues/115517

Decad3nce commented 7 months ago

I may have finally resolved this in the 1.2.21 beta