You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Use e.g. the following text "Šutr". It previews OK on android, but when the text is sent to the badge everything after the "Š" is garbled. It seems there is some overflow, because the "utr" is wrongly vertically aligned and unreadable.
To Reproduce
Use e.g. the text "Šutr".
Expected behavior
Text "Šutr" is correctly rendered on both android preview and on the badge.
Logs
Not applicable.
Screenshots
Smartphone Info:
Device
Xperia XZ2C
Android Version
9
Additional context
Would you like to work on the issue?
I can try to fix it.
The text was updated successfully, but these errors were encountered:
Hey @yarda! Thanks for raising this issue. I was testing some German characters and found similar alignment problems. Have you managed to find some clues on how to solve this? I hope I can find some time to look into the code as well.
I've added some characters to the font on my end but I've only tested the USB version from upstream, not the Android app yet. I think that's the way forward, adding new characters - it may be intractable in the long run but as long as we're not planning to support ALL unicode characters I think ad-hoc additions might suffice.
Maybe a script to convert unicode glyphs into 8x11 bitmaps?
Describe the bug
Use e.g. the following text "Šutr". It previews OK on android, but when the text is sent to the badge everything after the "Š" is garbled. It seems there is some overflow, because the "utr" is wrongly vertically aligned and unreadable.
To Reproduce
Use e.g. the text "Šutr".
Expected behavior
Text "Šutr" is correctly rendered on both android preview and on the badge.
Logs
Not applicable.
Screenshots
Smartphone Info:
Additional context
Would you like to work on the issue?
I can try to fix it.
The text was updated successfully, but these errors were encountered: