Great Circle Associates

XCIN Mail-list
(December 2000)


Indexed By Date: [Previous] [Next] Indexed By Thread: [Previous] [Next]

Subject: [hiura@unicode.org: Re: [I18n] API for XIM server side]
From: Tung-Han Hsieh <thhsieh@twcpro.phys.ntu.edu.tw>
Date: Thu, 21 Dec 2000 08:04:07 +0800
To: xcin@linux.org.tw
Reply-To: xcin@linux.org.tw
User-Agent: Mutt/1.0.1i

(遙頭苦笑 ....)

這個間諜真不好當,每天都要很用功才行 ....

這一篇是與 XIM server 有關的,我猜可能可以做為 IMdkit 的後繼人
選。但因為我們已在 IMdkit 中做了一些特殊修改 (就是防止 rxvt crash
的修改),故不曉得下文所提的 IIIM 適不適用。但我想值得花時間去看
看 :-))

T.H.Hsieh

----- Forwarded message from hiura@unicode.org -----

From: hiura@unicode.org
Date: Tue, 19 Dec 2000 23:21:54 -0800 (PST)
To: i18n@XFree86.Org, thhsieh@linux.org.tw
Subject: Re: [I18n] API for XIM server side
In-Reply-To: <20001220151025.A14830@tlug.sinica.edu.tw>
X-Mailer: Mew version 1.95b43 on Emacs 20.7 / Mule 4.1 (AOI)

Thanks for introducing IMdkit.

I have small information to add.

The IMdkit you referred is almost identical with the original, the
first release of IMdkit by XI18N team of X Consortium. The newer,
improved and clearner version of IMdkit done by the original author of
IMdkit is available as a part of IIIMF/XI18N distribution(as a part of
IIIM server framework) from the www.li18nux.org CVS tree. 

Actually, the entire IIIM server framework and the leif (Language Engine
InterFace) are the successor of original IMdkit as a whole.
So you do not have to write a lot of duplicating code to add your
languege engine. 

The special remarks here, for whom do not see why not current Xutf8*
APIs ;-) is that IMdkit/IIIM server framework uses Unicode
normalization approach for its I18N framework; The major difference
from Xutf8* is that it uses with annotation(as known as higher level
protocol in Unicode terminology) with multi-locale concept.

--
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,      FAX 650-786-9553


> From: thhsieh@linux.org.tw
> Greetings,
> 
> We all know that Xlib has standard API for XIM client side, e.g.,
> XOpenIM(), XCreateIC(), XSetIMValues(), XmbLookupString() .... etc.
> But in my knowledge, there is no standard API for XIM server part.
> Therefore, to write a XIM server, we usually have to explore some
> un-documented function calls inside Xlib. For example, a library
> named "IMdkit"
> 
> 	ftp://xcin.linux.org.tw/pub/xcin/misc/IMdkit.tar.gz
> 
> which could make life easy to write a XIM server, but in the library
> it calls _XRegisterFilterByType(), _XRegisterFilterByType(),
> _XimXTransRead() .... function to accomplish its goals. These are
> not the APIs documented in the Xlib programming manual.
> 
> So, is there any plan to add such API into Xlib?
> 
> Thanks very much for your explaination.
> 
> 
> T.H.Hsieh
> _______________________________________________
> I18n mailing list
> I18n@XFree86.Org
> http://XFree86.Org/mailman/listinfo/i18n

----- End forwarded message -----
To Unsubscribe: send mail to majordomo@linux.org.tw
with "unsubscribe xcin" in the body of the message

Indexed By Date Previous: [FWD] [I18n] Proposal for withdrawing Xutf8*() APIs
From: Edward Lee <edward.@kimo.com>
Next: Re: [FWD] Re: [I18n] On the Xutf8* funtions and the future of UTF-8 l
From: Platin.bbs@openbazaar.net (小虫)
Indexed By Thread Previous: [FWD] [I18n] Proposal for withdrawing Xutf8*() APIs
From: Edward Lee <edward.@kimo.com>
Next: [填補注音] 12001-13000
From: Tung-Han Hsieh <thhsieh@twcpro.phys.ntu.edu.tw>