> From: [EMAIL PROTECTED] > So, is there any comment or good ideas to resolve this problem? :-))
The solution I took was to move to IIIMF completely, including IIIMXCF enabled Xlib. No more XIM protocol or traditional XIM server involved, so the problem you encountered no longer exists. Since IIIMXCF features XIM compatibility, an X Client can use XIM API. Underneath the XIM API, all the way through IIIMSF and dynamic loadable engine interface, including IIIM protocol, are all new implementation based on different architecture, but it is invisible to X Client using XIM API. Also, XBackend provides XIM Protocol emulation for non-IIIMXCF enabled Xlib(of course the problem of XIM protocol remains here) so it covers transition/heterogeneous environment painlessly. Moving to IIIMF means to the IM Server developpers that they are to separate their core language engine part to port to IIIMSF pluggable engine interface, and to separate specific GUI components if any as a dynamic loadable GUI object to be loaded onto IIIMXCF dynamically. This is how Solaris implemented Multilingual Input Method Service. For source and documentation, http://www.li18nux.org/subgroups/im/IIIMF/ -- hiura@{sun.com,li18nux.org,kondara.org,unicode.org} http://www.li18nux.org Chair, Li18nux/Linux Internationalization Initiative, Free Standards Group Architect/Sr. Staff Engineer, Sun Microsystems, Inc, USA FAX 650-786-9553 _______________________________________________ I18n mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/i18n
