GNOME Bugzilla – Bug 696632
dead key mapping - dead circumflex is not printed as ^
Last modified: 2018-04-15 00:31:01 UTC
Created attachment 239858 [details] [review] proposed patch using xev , dead circumflex is seen as "^" . With gtk based application "^" , the key is mapped to the one left of the '1' key is shown as "dead circumflex" - http://de.wikipedia.org/wiki/Zirkumflex - http://de.wikipedia.org/wiki/Datei:Laptop_Tastatur.jpg
Created attachment 239860 [details] screenshot of the issue
I'm not convince that the patch is right. Concerns: a) This might break dead_circumflex functioning as a dead key (needs testing, at least) b) What about all the other dead keys ?
Hi @Matthias > a) This might break dead_circumflex functioning as a dead key (needs testing, at least) This patch does not any break dead key functionality on my system as far as I could test, with Hindi/Portuguese/ German keyboard atleast. > b) What about all the other dead keys ? Few of these were never mapped to being with, and no one has raised any bz for these. -- ritz
(In reply to comment #3) > Hi @Matthias > > > a) This might break dead_circumflex functioning as a dead key (needs testing, > at least) > > This patch does not any break dead key functionality on my system as far as I > could test, with Hindi/Portuguese/ German keyboard atleast. > Thanks for testing, that is good to know. > > b) What about all the other dead keys ? > Few of these were never mapped to being with, and no one has raised any bz for > these. Well, that's still no good reason to treat them differently.
Hi @Matthias <snip/> > > > b) What about all the other dead keys ? > > Few of these were never mapped to being with, and no one has raised any bz for > > these. > > Well, that's still no good reason to treat them differently. Agreed, but most of the frequently used dead keys are mapped. It would be hard to know, what is missing until a bz is filled for the same. Cheers ritz
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.
As announced a while ago, we are migrating to gitlab, and bugs that haven't seen activity in the last year or so will be not be migrated, but closed out in bugzilla. If this bug is still relevant to you, you can open a new issue describing the symptoms and how to reproduce it with gtk 3.22.x or master in gitlab: https://gitlab.gnome.org/GNOME/gtk/issues/new