Prior to Fedora Core 5 it was possible to use X.org in a UK environment. Various symbols needed in the UK for real practical use (i + ", a+e, etc) plus those needed for anyone dealing with names or foreign language names (notably western european and eastern european accented symbols) could be typed using the shift-altgr compose sequence. Not all are available without shift-altgr. In FC5 this feature only works outside of X11 and it makes it very unusable for serious work. en_GB (properly en_UK but thats another story) does actually require shift-altgr compose support and it should be restored. This is a revert from FC4 where it all just worked. (Note; Mike Harris asked me to file this upstream so if its Fedora specific ... 8)) Linux 2.6.x, compose working correctly in console modes not X Duplicatable in both xterm and gnome
http://bugzilla.redhat.com/bugzilla/attachment.cgi?id=134203 Is claimed to fix it.
NACK. this stomps RALT level1 regardless of whether it's Alt_R or ISO_Level3_Shift. there was a better fix for this, which is in xkeyboard-config, that has a different compose if you're using ralt as l3.
I'd tend to agree with Daniel and close this one. Feel free to reopen if you think current code is not good enough.
"I'd tend to agree with Daniel and close this one. Feel free to reopen if you think current code is not good enough." Re-opened. This is a regression from X.org 6.8 or so and earlier (back into the mists of time when Xkb first appeared). Please restore the older correct default behavioiur (eg Fedora Core up to FC4) so that the UK keyboard is by default actually usable in the UK and works in the manner that people (particularly non-English users) expect and have documented. I've no idea who decided to break the UK keyboard this way but please revert their changeset.
Alan, the funny thing that level3(ralt_switch) has not been changed for a long time. Well, anyway, I understand that it is not the only component in the system. There is more important question. You want "shift+ralt" work as Compose, don't you? But what about 4th shift level, which is also available using "shift+ralt"? In symbols/gb, I see: key <AE02> { [ 2, quotedbl, twosuperior, oneeighth ] }; key <AE03> { [ 3, sterling, threesuperior, sterling ] }; key <AE04> { [ 4, dollar, EuroSign, onequarter ] }; key <AC11> { [apostrophe, at, dead_circumflex, dead_caron] }; key <TLDE> { [ grave, notsign, bar, bar ] }; key <BKSL> { [numbersign, asciitilde, dead_grave, dead_breve ] }; key <LSGT> { [ backslash, bar, bar, brokenbar ] }; So if we set ralt+shift as Compose, the 4th shift level (oneeighth, sterlin, .. brokenbar) would be inaccessible. What is the correct expected behavior?
As I understand it shift-rightalt [remove paws from keyboard] char1 char2 is not the same as shift-rightalt-key. The version in https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=193922 appears to get us back to where it was prior to Fedora Core 5/Xorg changes and it is now possible to type all the additional characters needed for UK work.
Created attachment 6807 [details] [review] Add lv3:ralt_switch_multikey Here is a patch to add an lv3:ralt_switch_multikey option. IIRC this option did exist at some point in the past but has been dropped.
I am quite happy with this XkbOption. Alan, would it be ok for you just to have this option - or would you insist on inserting it into UK layout by default?
Anyway, the option is added.
With a Red Hat on, if it isn't in by default it's a regression from RHEL4. It's also documented so losing it breaks all the docs.
OK, committed. Seems to be working ok. Should I also change gb(intl)?
Unknown - I don't know what the old behaviour of gb(intl) was.
Ok, for a moment I'll close this one. If people complain, I update gb(intl) as well. (In reply to comment #12) > Unknown - I don't know what the old behaviour of gb(intl) was. >
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.