AppImage: text input ignores XCompose rules

• Oct 23, 2019 - 10:05
Reported version
3.x-dev
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
active
Regression
No
Workaround
Yes
Project
MuseScore

System: Linux Mint 19.1

Steps:
1. In any context where text can be input (in the score with, for instance, [Ctrl][t], in a dlg box, etc) either managed by MuseScore or directly by Qt,
2. enter one of the key sequences defined in your XCompose (just as an example, [MultiKey] a ")
3. each key is entered individually in the text (as in a" ), without any composition (=> ä )

Note:

  1. XCompose rules are observed in non-AppImage packages, like an executable locally compiled and run directly

  2. I did observe the same difference (working in installed .deb, not working in AppImage) in ver. 2.x but, having the PPA version fully working, I had no real need for the AppImage. With ver. 3, as far as I know, there is no .deb yet.

  3. Severity set to Major as it affects all text input and messes with a rather basic system feature. There are workarounds (using the F2 palette, which is huge but slow to use or the system Character Map which is even slower), but cumbersome and disruptive of the normal text input flow in Linux.

Comments