> From: Juliusz Chroboczek <[EMAIL PROTECTED]> > [2] Sun's recent beast (whatever its name) doesn't seem like it fits > the bill -- its complexity is most certainly beyond my capablities to > understand.
Why? Hope it is not because it originally came from Sun nor it is currently maintained by openi18n.org ;-P The IIIM project now has libiiimcf, the library which provides simple but powerful API set for clients using C/C++. This API is way simpler than XIM. For example, your favorite four only remotely related protocols (``styles'') do no longer exist, all complexity due to the X specific performance hack is completely out of scope in IIIM. IIIM is, from-top-to-bottom, natively (tagged)Unicode hardwired including protocol regardless of locale, and single server supports multiple language engines simultaneously. Multiengine/Multilingual/multiplatform(such as X, Java, emacs, console, Windows) nature of IIIM introduced some complexity but it also reduced another architectural X and locale specific complexities significantly compared to XIM. -- [EMAIL PROTECTED],OpenI18N.org,li18nux.org,unicode.org,sun.com} Chair, OpenI18N/Open Internationalization Initiative, http://www.OpenI18N.org Architect/Sr. Staff Engineer, Sun Microsystems, Inc, USA eFAX: 509-693-8356 -- Linux-UTF8: i18n of Linux on all levels Archive: http://mail.nl.linux.org/linux-utf8/
