> From: "Maiorana, Jason" <[EMAIL PROTECTED]>
> Dees anyone know what/how iterm would use iiimf?
The libiiimcf(iiim client framework) and the iterm
glue code are in development, are not yet released,
so current release(0.1) does not use iiimf.
We initially planned to develop single library "libiiimf" for
both server and client, but later, we decided to separate it
into two; The lower layer libiiimp which implements protocol handling
and can be used for both server and client, and the higher layer libiiimcf
which implements easy-to-use simple IM API for client only.
The libiiimp is already released and used as a part of new server
code base, replacing old IMdkit for protocol handling.
The releasing schedule we are looking at right now is about within a
month or so.
# Note: the entire IIIMF is hardwired to UTF-16, including
# server, language engines, all client side libraries/shared objects,
# and IIIM protocol. Whenever other encodings are required, it uses
# codeset converter, as seen in some client side code, such as in
# xiiimp.so in Xlib or XBackend.
#
# BTW, "locale", "language" and "codeset" are three distinctive
# things. Those terms are not interchangable.
# I have said "hardwired to specific codeset", or "CSD - CodeSet
# Dependent" vs "CSI - CodeSet Independent", as different approaches
# for I18N, but I have not said as Kai summarized.
--
hiura@{freestandards.org,li18nux.org,unicode.org,sun.com}
Chair, Li18nux/Linux Internationalization Initiative, http://www.li18nux.org
Board of Directors, Free Standards Group, http://www.freestandards.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/
