Bug 70995
| Summary: | Can't enter " easily with us_intl keyboard | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] Red Hat Public Beta | Reporter: | Alexandre Oliva <aoliva> | ||||||
| Component: | gtk2 | Assignee: | Owen Taylor <otaylor> | ||||||
| Status: | CLOSED RAWHIDE | QA Contact: | Jay Turner <jturner> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | limbo | CC: | srevivo | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | i386 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2002-08-14 03:17:46 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Bug Depends On: | 71014 | ||||||||
| Bug Blocks: | 67218 | ||||||||
| Attachments: |
|
||||||||
|
Description
Alexandre Oliva
2002-08-07 17:34:46 UTC
FWIW, konsole and other KDE applications I've tested exhibit the correct behavior. Also, contrary to my initial description of the problem, it's not about displaying characters incorrectly, it's about getting the meaning of keystrokes incorrectly. In en_US/.UTF-8Compose, I see:
<dead_diaeresis> <space> : "\"" quotedbl
<dead_diaeresis> <dead_diaeresis> : "(" diaeresis
Which looks backwards from what you have above for the xterm/emacs
case...
The GTK+ universal compose table got these mappings from the iso-8859-1
Compose sequences ... so it does the same thing as the keys would
have done in previous releases. The Xlib en_US.UTF-8 table disagrees
with the iso-8859-1 table.
BTW - You can make GTK+ use the Xlib compose tables if you set
GTK_IM_MODULE=xim (gnome-terminal doesn't currently offer a
way to select that interactively, most apps have a right click
menu.)
Oops. Sorry. Steps to Reproduce.3 should have read like 5. The iso-8859-1 compose tables were wrong (IMO) in earlier releases, an opinion shared by a number of other users of international keyboards I know. I still haven't checked whether they've been corrected, but a patch for XFree86 to fix them was sent a while ago. FWIW, iso8859-15 had got the diaeresis compose rules right, but iso8859-1 still had them wrong. I've just submitted a patch for XFree86 (internal and upstream) that fixes this and a few other oddities in the iso8859-1 compose tables. Bug 71014. Where is it that the gtk2 encoding tables are stored in the gtk2 source tree? I can try to fix them myself, and some pointers would surely help me get to it :-) Thanks, gtk+/gtk/gtkimcontextsimple.c Ignore the comment about the Perl scripts ... if I have them any more, I don't know where they are. (And there was quite a bit of hand editing involved as well in getting to the current form.) The following patch adjusts the behavior of quotedbl space and introduces double-dead-accent sequences for the grave and circumflex accents, that would formerly generate nothing. It also rearranges the similar sequences for acute accent and tilde, so that they're all in the beginning. With these changes, the behavior matches that of XFree86, at least as far as these sequences are concerned. Created attachment 70464 [details]
Patch for gtk+ to fix dead key sequences.
I failed to mention I haven't tested this patch, cause I'm missing glib2-2.0.6 in my laptop. I'll try it out tomorrow, and probably find out I shouldn't have reordered the entries :-( Created attachment 70485 [details]
Patch as applied
Tests out fine in 2.0.6-3 |