GNOME Bugzilla – Bug 75814
Compose key not working.
Last modified: 2004-12-22 21:47:04 UTC
The Compose key doesn't seem to work on the new GNOME Terminal. To reproduce, try this: xmodmap -e "remove mod1 = Meta_R" -e "keysym Meta_R = Multi_key" which will re-map the right alt key to be compose. Then start emacs -nw in a GNOME terminal and in a buffer type "RightAlt ~ n". It will insert "~n" instead of "ñ".
more libzvt fun
Is any one working on this ?
aruna: for what it is worth, if no one from wipro is working on a zvt bug at the moment, it is very unlikely anyone is looking at it :)
I have the same problem but with dead keys. By looking at the code I think it's because the terminal widget doesn't have an input context (that code is commented out since the API it was using is deprecated). The new way to do this is with GtkIMContext, right? Would a GtkIMSimpleContext suffice?
I worked out a patch to add a GtkIMContextSimple to the ZvtTerm widget. I wasn't sure about when to reset the context, so I mimicked GtkTextView. There are two things yet to be done (I don't know exactly how to do them): retrieve_surrounding signal handling and setting the cursor location on the context.
Created attachment 8572 [details] [review] Add GtkIMContextSimple to terminal widget
I think using GtkMultiContextIM is a right thing. I modified the patch above and attached it to #78007.
Hmmm... does this really make sense? I mean there's currently no way to change to input context, except via the menu items you have to merge into some popup (which currently we don't have :-) Internationalization is pretty broken anyways, so... (I shouldn't need to call g_locale_from_utf8 for example ;-)
Ah -yes, I assumed a way to switch input methods should be also added as gtktextview/gtkentry do in popup-menu(or in any better way)!
If libzvt uses pango for text display instead of using Xlib calls and XFontSet/XFontStruct directly, then there is no need to call g_locale_from_utf8 here.
Hidetoshi, Gustavo: can I mark this a duplicate of bug 78007 then?
How about saying this depends on 78007?
I think it should be marked as duplicate. Bug 78007 raises the issue of input method AND double width characters. So you could say this bug is included in 78007. Besides the patch is also there, and even improved by Hidetoshi. My only concern is that the other bug's title is not general enough (i.e. mentions only Korean characters). i18n is really broken anyway, and there are a lot more bugs reported about it though (75487, 79415, 77135... just to name a few :-) Will libzvt be supported in the future, or it will be replaced by vte? I would be willing to help fixing it, though certainly not for 2.0.0.
The short summary of #78007 starts with "CJK" right now, but can be changed to "I18N" to be more generic if we like. I also agree to close this as a duplicated to #78007.
Gustavo: thanks for working on this one; because of the more comprehensive nature of the patch on bug 78007 I'm going to mark this a dup of that. If you have further comments or patches, please add them to that bug. Thanks! *** This bug has been marked as a duplicate of 78007 ***