© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
67d34a1
(Get the code!)
I also posted this in a different bug report (https:/
I got a "stupid" way to "solve" the deadkeys problem in Gutsy for KDE apps...
What I did:
0.- I reinstalled Gutsy, all from scratch, and using an Ubuntu Studio version instead the original version. *
1.- I added the Ubuntu DVD as a repository source and then added the other repositories. I'm not using gutsy-updates nor gutsy-security. **
2.- I opened language settings and installed Chinese and Japanese support. ***
3.- Restarted the System.
4.- I opened language settings and activated complex characters input, then applied. I unchecked this option, applied again. I enabled again this setting, applied and closed the window. Reopened the window and checked the option is active. ****
5.- Restarted the system.
6.- Opened Gedit. As expected you cannot trigger SCIM with ctrl+space, but you can right click and select it to input text. With or without SCIM there's no deadkeys problem.
7.- Opened Konversation and Opera to check input. Cannot choose input but there's no dead key problem.
8.- Installed scim-qtimm. *****
9.- Installed scim-bridge-
10.- Installed scim-bridge and scim-bridge-
11.- Restarted.
12.- sudo gedit /etc/X11/
13.- Restarted. #
14.- Opened Gedit and triggered SCIM. It works as expected, and there's no problem with deadkeys.
15.- Opened Konversation and Opera. Deadkeys problem started. But you can trigger SCIM. ##
16.- Started to think KDE it's no good for my computer, and decided to use just gnome apps. Then did a little modification: sudo gedit /etc/X11/
17.- Then I just opened SCIM to configure it for Gnome. In global settings (under interface) you found a rollover to select keyboard distribution. It said Unknown, I changed it to Spanish (Spain) the keyb I use. Closed it and rememebered I just need a pinyin input (chinese) and an anthy input (japanese). Reopened and selected them. There's an additional option, others, with spanish/european and raw input. I leave spanish/european marked.
18.- Opened Opera and triggered the SCIM. then selected spanish/european, and wow! It works! Then, disabled the SCIM, deadkeys problem is back.
19.- Opened Konversation ad did the same, I can write spanish throug SCIM too. ####
20.- Remember the step number 16? Then i opened Konversation and tried to input the ~ accent modified in this keyb to write ã... And it also works! Then SCIM is using my main tables for input, and deadkeys works through SCIM.
Two more things
a.- I think this is not a "solution" or at least a clean solution cause you don't need to use an IME to write spanish. But cause it works...
b.- The downside. Before reinstalled my system I was able to input chinese in aMSN, I don't know how! And I think if I discovered I can write spanish through SCIM I was still able to write in aMSN using spanish, english and chinese... I have to look what I did before but I'm deeply afraid to render SCIM useless again... A little suggestion, I though it's something related to an option in KDE input settings scim-panel-kde... but I'm not sure. Does anybody want to try it to enable input on aMSN, skype and related??
* This is not really an step, just a way to say I used a fresh install and the problem is not related to standard installation.
** I think you could use them if you want, but I write it to clarify you don't need updates or security packages to "solve" the problem
*** I found a problem in meta-package, but that's for a different issue
**** Dunno why, but everywhere I look in the net says you must enable-
***** I didin't used it, but... (umm I got out of asterisks...)
# OK, it seems to be a lil bit paranoid, but I prefer to sin being paranoid rather than sin being to confident....
## It feels to strange to be able to write english and chinese but no spanish.
### That seems to be out of scope but just wait few steps...
#### Of course you feel weird enough using a complex IME to write spanish in your system.