Bugs item #2789849, was opened at 2009-05-10 23:11
Message generated for change (Comment added) made by courtjester
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=650539&aid=2789849&group_id=108454Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Core: libscim
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: FangQ (fangq)
Assigned to: James Su (suzhe)
Summary: Fontforge menu does not accept scim input
Initial Comment:
This is also a long standing problem with scim. As long as I started scim as my input method (either English or Chinese), fontforge (all versions) will stop accepting key-strokes for any dialog that needs input (for example, menu View\Goto). This is repeatable on CentOS 4.x~5.x and Ubuntu 6.10 ~ 9.04. Only when I started fontforge remotely, and display with a local Xserver, I can type with scim.
My desktop language is English. I used scim normally for typing Chinese. Typically I only enable "English/Keyboard" and "Chinese(simplified) Ziranma" as my input engines.
----------------------------------------------------------------------
Comment By: CourtJester (courtjester)
Date: 2009-05-11 16:44
Message:
I believe this is a problem with fontforge and should be fixed in the
latest version of fontforge. The version in Ubuntu 9.04 is 20080429 which
is rather old and does not contain the fix. I looked at this problem last
December, and this is what I found. Fontforge uses XIM for IM.
In file gdraw/gxdraw.c around lines 3254 (as of last December). FontForge
is discarding ClientMessages generated by the XIM framework. If an input
method does not process a keypress, for example because it is not enabled,
it can requeue the event as a non filtered event by calling IMForwardEvent.
X11 creates a ClientMessage to handle this event. FontForge, for some
reason, only processes messages for windows it owns, and discards the rest.
Unfortunately the window associated with the ClientMessage is not one that
FontForge has any context for so it discards the message. Because it
discards the message, X11 never sees it even though it is expecting it, and
subsequently the no further processing of keyboard input happens. What
should actually happen is that XFilterEvent should be called before any
context processing happens so that X11 can process the ClientMessage before
FontForge discards it.
Try a more recent build for fontforge to see if the problem still exists.
Doug Rintoul.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=650539&aid=2789849&group_id=108454------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled.
http://p.sf.net/sfu/kodak-com_______________________________________________
Scim-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/scim-user
