Doesn't work for me in Qt

[drydenp]

It's not working in Kubuntu 16.04, KDE.

When I restart SDDM and log in, my .XCompose is not even getting accessed.

Using or not using uim makes no difference.

Strangely at this point there is a difference in what appears to be GTK applications, including apostrophe turning into special accent ¨don´t¨ which is not what I want, but the same thing doesn't happen in QT applications.

And I don´t even have anything installed at this point.

The keyboard is set to ¨US International with dead keys¨.

So currently using the default fcitx and I don´t know how to get it to work for Qt nor how to get back the original ¨ ;-) " except by changing to US variant.

[raelgc]

Hi @drydenp, thanks for reporting this issue.

Indeed, I just tested and it's not working on KDE 5.

I'll search for a fix.

[raelgc]

@drydenp It works if I follow the manual setup (install uim and download the .XCompose file into my home). Of course, restart X is required.

[drydenp]

I tried that, doesn´t work for me. As you can (see) in Gnome applications it works and I get special type ´ when I type instead of '.

It doesn´t work in Konsole or Dolphin.

I don´t know what this depends on.

It´s doable because most applications are actually GTK applications.

My .XCompose is getting read by Konsole, it is just not acted upon it seems.

[raelgc]

Weird, KDE5 kind of mixes the way it works.

No more accent on consonants, but ` still not properly working.

By example, if I type "i'll", in GTK, I can type: i +` + l + l.

In KDE, if I type i +` + l + l, the first L will be not displayed, it's used to display the apostrophe.

Wondering if it requires a special rule in the .XCompose.

Or if any tweak on System Settings > Input devices > Keyboard > Advanced can fix it.

[drydenp]

And now even though I didn't have an .XCompose AND uim was not installed, my keyboard stopped having dead keys in Gnome, while the dead keys work in Qt, and the Compose key also works in Qt, but not in GTK.

I mean GTK.

I don't know what the hell happened, I guess I need to reset my keyboard configuration or something.

Very strange all.