Red Hat Bugzilla – Bug 119240
xinput should only turn on IIIMF for Asian locale
Last modified: 2007-11-30 17:10:39 EST
Description of problem:
As reported in bug 118588 by lxo, for an everything
install iiimf gets turned on even for European languages
where it is not useful.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install iiimf-*
2. Start en_US gnome session
3. Start gtk2 or XIM application
XIM and iiimf IM turned on
No input method being used.
Why is this marked as "fixed in xinitrc-3.38-0"? I have not checked
any new changes into CVS for this, nor built a xinitrc-3.38-0
package. No package exists in dist-fc2, dist-fc2-scratch,
dist-fc2-HEAD, dist-fc2-hold. Was this closed by mistake?
Jens built this package and handed it to me for testing. I thought it
was going to be in rawhide soon.
lxo: Ah, just a bit of confusion. ;o)
Ok, I've made some cleanups to the xinput script both for this issue,
the missing ']' issue, another issue of using || instead of -o that
was present and changed to using -n instead of tests for != "".
This will be in the next build. I don't know what happened to jens
patch though, I think I lost it in email.
Jens, can you attach your patches to bugzilla?
Ugh, my patch did all that too pretty much I think. :-(
Created attachment 98954 [details]
patch to avoid htt for European langs and lots of other cleanup
The patch I mailed on Saturday night to Mike.
Thanks Jens, I've added a few more of your fixes, as well as a host
full of my own fixes to the various scripts also. The complete
details are in the xinitrc-3.38 specfile changelog. Please review
a diff of the changes between 3.37 and 3.38 for glaring goofups if
you have the time to have a peek, as a second set of eyes passing over
my changes would be a good idea. I studied a diff between the two
for problems and didn't spot anything obvious, but it doesn't hurt.
Closing as fixed in 3.38-1 in rawhide. (dist-fc2-hold currently)
*** Bug 119083 has been marked as a duplicate of this bug. ***
*** Bug 119917 has been marked as a duplicate of this bug. ***