[openi18n-im:01422] Re: patch to export information of input method engine

Kasha,

As part of external interface, absolutely we should keep the spec file
up-to-date, Thanks.
I will do it once the code got committed.

-federic


> Hi Federic,
> 
> Date: Mon, 20 Jun 2005 12:05:05 +0800
> From: Federic Zhang <[email protected]>:
> > 
> > Please get the lastest patch through attachment, which i verified is ok.
> > several modifications have been made: 
> > 
> >    - exclude 'reserved1' and 'reserved2' from the IMEInfo struct
> >    - correct the name of iiimcf_get_input_method_imeinfos in
> > libiiimcf.sym
> >    - attach the missing comp-imeinfos.c
> > 
> > Please review. If it is no problem, i will commit in this two days.
> 
> Would you also update doc/protocol/spec.html to include the data
> definition?  Your code is very clear, but the data definition
> with some explanation will greatly help us to understand
> meanings of each field.
> 
> Thanks,
> -- 
> kasha
> 
> > 
> > BTW, Ervin suggests to export also the identification (id) of input
> > method engine (in ASCII)
> > to distinguish different input method engines in client, it is one good
> > suggestion.
> > 
> > -federic