> From: Phillip Vandry <[EMAIL PROTECTED]> > Is it possible to use XFree86's builtin IM (XimLocal) which implements > compose keys and dead accents and the XIM protocol (XimProto) at the > same time? It looks to me like it is not possible.
Do you specifically want to use XimLocal module and XimProto module at the same time? Or you want the local simple composition IM capability and the remote complex IM capability at the same time? If what you want is the latter, you may want to try IIIM Xlib module called xiiimp.so. By modifying the XIM entry of your /usr/X11R6/lib/X11/locale/<current locale>/XI18N_OBJS from XIM common/ximcp _XimOpenIM _XimRegisterIMInstantiateCallback _XimUnRegisterIMInstantiateCallback to something like XIM common/xiiimp _SwitchOpenIM XIM common/xiiimp _XimpLocalOpenIM XIM common/ximp40 _Ximp_OpenIM XIM common/ximcp _XimOpenIM _XimRegisterIMInstantiateCallback _XimUnRegisterIMInstantiateCallback XIM common/ximll _XimpLocalOpenIM XIM common/ximlocal _XimpLocalOpenIM You can use localIM/remoteIM at the same time, and you can go back and forth among them. They are available from openi18n.org. > What would be the correct solution? I'd like both ximlocal and ximcp/ximp40(R6 and R5 XIM protocol modules) and actually all XIM servers to be tapering out, because the combination of them does not really provide multilingual solution, its old design carries many limitations, and not extensible/flexible. Therefore, I'd even like the capability I just explained above to be tapering out as well. What I am aiming for as future IM is to have a multilingual remote IM to delegate dynamically a part of or all of IM functionality to the client side lightweight engine, in addition to switch language engines dynamically, to provide flexible input experience. This mechanism in IIIMF is called EIMIL/PCE(Extensinble IM Interface Language/Primary Composition Engine). We use XML as an IM extention language. > for reimplementing compose keys and dead accents on top of the > additional functionality it provides? Xlib already provides this > functionality, it seems like reinventing the wheel to not be able to > take advantage of it. We distribute the im-sdk, which we position as the successor of IMdkit(XIM server developpers kit) we developed about 10 years ago. The im-sdk also carries such composition engine called UNIT(UNIcode Table based engine), in addition to EIMIL/PCE. It was worth it to reinventing such composition engine to achieve - Full Unicode repertoire coverage - Be integrated seamlessly with other engines - X independent - Native Unicode hard-wired composition engine ;-).. because IIIMF is fully Unicode hard-wired. For more info: http://www.openi18n.org/IIIMF [EMAIL PROTECTED] -- [EMAIL PROTECTED],OpenI18N.org,li18nux.org,unicode.org,sun.com} Chair, OpenI18N.org/The Free Standards Group http://www.OpenI18N.org Architect/Sr. Staff Engineer, Sun Microsystems, Inc, USA eFAX: 509-693-8356 _______________________________________________ I18n mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/i18n