Comment 20 for bug 890438

Revision history for this message
In , Gannet (ken20001) wrote :

(In reply to comment #14)

> Ok, if we agree that it must be fixed in GNOME - would that close the subtopic
> about mainstream DEs
Please read commentary 11. DE subtopic is not about fix some DE-related bug, it's about current availability of this feature for target audience. Availability of this feature for target audience (in Gnome Shell - probably doesn't work because of bug, in Unity - not implemented yet, in KDE - enabled and available by default) suggests that not many peoples may notice problems with current situation around keyboard layout switch order in xkb.

> > Well, I was asking because I know some ppl whou use >2 layouts.
> I realize it is not always possible, but at least some effort should be made.
I just accidentally noticed in news about KDE releases there is at least one more man who think current keyboard layout switching order is "strange": http://kubuntu.ru/node/8488#comment-92734

> That is really odd. I guess it must be a bug, please file it.
This bug is not solved yet so I don't see any sense to report more bugs related to keyboard layouts in Linux until this bug will be resolved. (Bugs on KDE side is resolved in 4.7.4 so now only this bug is stumbling block).

> And you see James admitted there is some good use to it.
Yes, BUT James also noticed:
> I would not, however, object to having to change my config

> I do not consider Unity as such
You know, thanks for reminding me! I filled feature request for Unity developers here: https://bugs.launchpad.net/unity/+bug/907298

> Unfortunately logic does not have immediately higher priority over status quo.
> I may support your logic - but that is not enough to break existing things.
> Well, there are so many more serious issues with the XKB design;)
Since feature request for Unity developers is filled, many more peoples (than just Gnome Shell and KDE audience) may notice problems with keyboard layouts switching order in xkb in near future. So now it's time to fix this problem in XKB design. Don't you think so?