AppImage doesn't accept accented characters from keyboard using "dead keys"
Priority
P1 - High
Type
Graphical (UI)
Frequency
Many
Severity
S2 - Critical
Reproducibility
Always
Status
active
Regression
No
Workaround
Yes
Project
Hi,
I have just installed 2.0.3 version. It's nice but not accepts accented characters in creating any kind of text. (i.e. á à ã ó) very common in Portuguese.
GIT commit: 3c7a69d
Comments
That would be a major regression (assuming you had it working in 2.0.2, had you?), I can't reproduce it though, á, à and ó work just fine (and I don't know how to enter that ã).
What OS are you using?
Also, how are you entering the characters, and wha font are you using? The Special Characters palette that appears when you press F2 while editing text works just fine for me with the default FreeSerif font.
It would help if you attached the score you are havig problems with and precise steps to reproduce the problem.
No accented characters here, too. I'm entering lyrics with STRG+L
MuseScore 2.0.2 is fine,
Standard-Textfont: FreeSerif
I'm on Kubuntu 15.04
Linux 3.19.0-56-generic
Lyric_characters.mscz
The lyrics are (should be) : é, è, ê
As said, this works just fine for me (and yes, I tested lyrics), albeit on Windows 7
Are you using an AppImage Version? Self build? What else?
I tried with the default font (Freeserif) and many others. None works.
I tried with the default font (Freeserif) and many others. None works.
I am using Appimage on Xubuntu 15.10.
Yes, i use the Portable AppImage
3c7a69d.
Downloaded and clicked for run.
Mysterious! When i open your attached file, Jojo, it shows the correct characters!
Can someone please attach a specific score they are having problems with and precise step by step instructions to reproduce the problem? Here is is what works for me:
1) My First Score
2) Double click title to enter text edit mode
3) Press F2 to display Special Characters palette
4) Double click any accented character - say, ç
5) Press F2 again to close Special Characters palette
Result: as expect, the character appears in the text
Is this exactly what you those of you seeing problems are doing, or are you perhaps doing something different? What precisely goes wrong? Does the palette not appear at step 3? Does it appear but is empty? Does the character not appear in the text when you double click the palette? Does an empty box show instead?
FWIW, I see the same (correct) results if I enter notes then use Ctrl+L to enter lyrics: the F2 palette works flawlessly.
BTW, when I open the file attached to #3, I see three regular e's, and opening the actual MSCX file within the archive using a text editor shows me the same thing. This suggsts to me that the F2 palette was not used and perhaps you tried some other unsupported method of entering the characters? Because I can't think of any way the F2 palette could just happen to replace an accented "e" with a regular one - they are completely different character codes.
I too am using the AppImage, on Ubuntu 14.04.
I've entered then the 'normal' way: Select a note, start lyrics entry Ctrl+L, enter Accent (it is a dead key here) followed by the letter `e
I've just inputted every available special character my (belgian azerty) keyboard has on 2.0.3 Win7, they all work flawlessly.
Perhaps an AppImage specific problem?
I'm using AppImage as well, and again the F2 palette works flawlessly. I'm not familiar with an "Accent" key - perhaps some sort of OS-dependent key present on some non-US keyboards? I could believe that the AppImage doesn't necessarily support such system-dependent methods of character entry. But the F2 palette should work fine.
I'm talking about hat (accent circonflexe), back tick (accent grave) and tick (accent aigu) (and tilde, which I can't get to work, it is not a dead key here), those are available on US keyboards too I think.
For those where it falis, esp Pentatonus: what about German umlauts ä,ö,ü?
Please share your keyboard layout name if possible - https://en.wikipedia.org/wiki/Keyboard_layout
I can confirm this problem for Kubuntu 14.04.
Running my self-compiled v2.0.3 everything works.
Running the AppImage version, one cannot enter characters, that are created by pressing two keys after another (using "dead keys") . While F2 palette works, this seems to be no feasible way of entering these characters if they are needed frequently.
From viewing images of the French keyboard layout I'd also expect ê to be impossible to enter using the AppImage and a French keyboard.
Jojo-Schmitz:
German Umlauts are fine, because they sit on their own key. Dead keys is the problem.
If I input the accented characters by using F2 everything is OK. Typing special characters in other software (text editors, browsers, etc.) and copying and pasting also works. However that's unproductive. It seems that 2.0.3 not recognizes my portuguese keyboard layout.
My keyboard is QWERTY (Brazilian)
Mine's a QWERTZ, and I'using dead keys to enter accented caracters.
Jojo, just to be sure, you're running the AppImage on Linux?
No, Windows and the official 2.0.3 from the download page.
But maybe this is related to #104846: AppImage does not use translations on buttons in dialog windows
I use QWERTZ (german) layout. German umlauts ä,ö,ü are ok.
I use the dead keys for ` ^ etc. - dont work with a, e , i, o, u.
Yes, F2 works for me, but the combination with dead keys is much more common and faster.
Ok, so if I'm understanding correctly, the issue occurs only when using "dead keys" as a method of entering these characters? I guess that is some sort of keyboard / OS-specific entry method (I'm not familiar with it). so like I said, not terribly surprising it might not work. That kind of stuff is generally handled by Qt, and the AppImage comes with its own version of Qt, I believe.
The F2 palette should still work. What about Alt + numeric keypad, for keyboard that support that entry method?
I remember back in the days you'd need to do some special config in Linix or the X-Server to get dead keys working.
But if it works for 2.0.2 and not for 2.0.3, this won't be the issue, right?
> But if it works for 2.0.2 and not for 2.0.3, this won't be the issue, right?
What do you mean? I don't think there was an AppImage for version 2.0.2.
See New features section in MuseScore 2.0.3 is released:
Right, JoJo. Must be the Qt-version in the AppImage !?.
When 2.0.3 comes in the Linux repositories etc. , all may be ok !?
@heuchi: not related to AppImages, just to general Linux/ X-Server config reg. dead keys.
@Pentatonus: I doubt it is the Qt version, but rather something missing in the package.
@Jojo-Schmitz: Why do you think it's not related to AppImage?
Two quotes:
#7: I am using Appimage on Xubuntu 15.10.
and #8: Yes, i use the Portable AppImage
The two users experiencing the problem both say they use the AppImage version. And I myself have confirmed, that on my system the AppImage version shows this problem, while the self-compiled v2.0.3 does not. (#17)
About the Qt version:
MuseScore-2.0.3-x86_64.AppImage says it's using Qt5.5.1.
I just created a self-compiled v2.0.3 using Qt5.5.1 and it doesn't show the problem.
I don't think it is not related to AppImage (actually I'm quite sure it is reated to that), I just believe it is not related to a Linux/X-Server setup messup, but want to verify that.
However, using Qt-5.5.1 for AppImage, while Windows and Mac use 5.4.2 looks plain wrong to me.
Well, I'm completely confused now.
In #30 you wrote:
@heuchi: not related to AppImages, just to general Linux/ X-Server config reg. dead keys.
And now you write:
I don't think it is not related to AppImage...
?? or am I just getting tired...
the latter ;-)
currrent thinking is that the AppImage somehow inherits some settings from the build system rather than taking those from the system it runs on. Could explain the keyboard and the translation issue?
I just downloaded an AppImage version of Scribus for a test.
Entering é,è,ê characters was possible. It also uses Qt5.5.1.
The "Recipe" used to create this AppImage seems to be accessible here.
Came up again in https://musescore.org/en/node/196071, there for a 2.1 AppImage
Came up again in https://musescore.org/en/node/228136
I would like to add that the snap version is also affected by this problem. I'm on KDE Neon, based on Ubuntu 16.04.
Workaround is to use the special characters palette. And it is not really random, all appimages are affected
In reply to Workaround is to use the… by Jojo-Schmitz
I am experiencing this with Appimage 2.3.2 on Linux mint 18 cinnamon 3.0.7.
I am using the Canadian French keyboard and it only has trouble with dead keys, the é works fine since it is on its own key.
It works fine on the one from the repository so I will use that one now.
Came up again: https://musescore.org/en/node/283462
It's affected by all versions of the AppImage (with a distribution package it works). As mentioned: via cross-referencing deadkeys work with an AppImage of Scribus as expected, but don't with any MuseScore Appimages.