Comment # 5 on bug 954723 from Stefan Hundhammer

Not sure if we can do very much about this - I guess that's deep inside Qt in
the text rendering engine. I could imagine (but I am not sure) that the
ampersand '&' character that denotes the keyboard shortcut is removed one step
too late in the text rendering process, so a lone character (which would
otherwise use the standalone version of that character) is not alone yet at
this stage: It's still "&a", not "a". And then the text renderer would pick the
wrong glyph.

Background information for those not familiar with Arabic font rendering:

Since Arabic is normally written with a pencil or a brush, it's a "written"
script, i.e. characters in a word are normally connected with each other - the
way the pencil writes on paper. This means that there are normally four
versions of each character (glyph):

- One when it's the first character in a word
- One when it's in the middle of a word
- One when it's the last character in a word
- One when it's standalone.

This bug is about the last version; the text rendering engine seems to pick the
wrong version with a connecting line to one side. It should pick the standalone
one.

Hanny, I hope this description is correct - please correct me if I am wrong.