Arabic diacritics showing not showing in popup keys

REPRODUCIBILITY (% or how often): 99%
BUILD ID = OS VERSION (Settings > About product):
HARDWARE (Jolla1, Tablet, XA2,…): XA2 Plus, X10
REGRESSION: (compared to previous public release: Yes, No, ?): No


The Arabic diacritics do not show at all in the popup of a character key (accents in CharacterKey), in a custom keyboard layout.
However, these diacritics show correctly if they are inserted directly in the Caption or captionShifted of a CharacterKey.


Install an Arabic keyboard layout, such as Multi Keyboard Layouts


  1. Install Multi Keyboard Layouts
  2. Choose Arabic layout
  3. Press and hold the comma symbol


The diacritics should show in popup key


An empty field is shown instead, the diacritics aren’t rendered


(Please ALWAYS attach relevant data such as logs, screenshots, etc…)

Note that the diacritics are actually inserted when the accent key is pressed. They are rendered correctly by Sailfish on documents, bu not on the keyboard.
Note also that these diacritics are shown in the keyboard if written in the caption or captionshifted in the QML file.

Note also that sometimes, very rarely, the diacritics do appear on the popup, but it disappears again on reboot. I failed so far to reproduce the bug or how it appears.

Does anyone with knowledge of the keyboard in QT or Sailfish, or how rendering goes for the keyboard, have any clues or pointers to help me identify and reproduce this bug (and maybe fix if it’s not Sailfish core related) ?

Images to portray the bug :

The bug :

What it should show (very rarely, failed to reproduce) :

What the caption/captionshifted show correctly all the time :

1 Like

Haven’t checked the Multi Keyboard Layouts package but as such this doesn’t sound like a bug in the Sailfish OS. That said, it could still be so that bug gets triggered due to a bug in the Sailfish OS side.

I found another related topic: Dead keys not working

@pherjung Reported that related topic internally as well.

Thanks @rainemak. The Arabic keyboard layout package by aline exhibits in some cases a similar issue.
I might suspect it’s related to fonts, or to how the text is drawn as diacritics are drawn in parts of the button.