After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 67073 - Multibyte input into cell through XIM
Multibyte input into cell through XIM
Status: RESOLVED DUPLICATE of bug 84062
Product: Gnumeric
Classification: Applications
Component: Sheet Objects
git master
Other other
: Normal normal
: ---
Assigned To: Jody Goldberg
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2001-12-16 22:33 UTC by ynakai
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
includes cursor position fix too (2.02 KB, patch)
2001-12-16 22:36 UTC, ynakai 		none Details | Review

Description ynakai 2001-12-16 22:33:53 UTC 
XIM Over-the-spot style input needs to update
XIM preedit area position to the cursor blinking
position.

(patch is available.)

But I want to update when just focused cell is changed
with a mouse click. It just needs to tell cell's upper
left corner x, y to item_edit_update_im_position() function
but I have no idea about this.
Comment 1 ynakai 2001-12-16 22:36:21 UTC 
Created attachment 6235 [details] [review]
includes cursor position fix too
Comment 2 Jody Goldberg 2001-12-25 22:07:31 UTC 
I am not comfortable with this patch right now.  I'll revisit it for 1.0.1
Comment 3 Jody Goldberg 2002-01-12 21:45:18 UTC 
I did not forget this.  I'll commit after 1.0.2 so it can get some testing.
However, we will need to rework it completely for gnome2.  All input method
support there is disabled.
Comment 4 Havoc Pennington 2002-03-24 15:48:02 UTC 
See also https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=61624
Comment 5 Jody Goldberg 2002-10-02 03:10:13 UTC 
Now that the internals of gnumeric are generally utf8 clean and IM support has
been basicly re-enabled we can revisit support this form of IM.  I can't say I
love the notion of this being in redhat's pacakges of 1.0.x, the patch needed
some work.  Hopefully in the context of 1.1.x this will be alot cleaner.


*** This bug has been marked as a duplicate of 84062 ***