> From: Bharathi S <[EMAIL PROTECTED]>
> I want to write a Encoding based XIM, XIM should
> be independent of language and font.
You mean you just want to use the language switing mechanism in ISCII,
or something-else?
> Input
> |
> \|/
> XIM <-- ASCII to FIE Rule file.
> | ISCII is NOT a permentent. User can able
> | to use any kind of Encoding ( to Unicode, to TSCII,
> | etc ), So it will become Encoding Free XIM (?)
What XIM produces is the string consists of coded
character set, not a font index array by
definitin/design, it will meet with what
you mean by FIE anyway if things are properly done.
ASCII -> ISCII transliteration should be quite simple,
and can be done with the Xlib's local Compose mechanism,
which I am actually working on replacing with the more
flexible/extensible EIMIL/PCE mechanism in the future.
Also you can use IIIMF which has several Indic language
engines come with as a part of language engine
repartoire.
> \|/
> File / Memory - FIE (Font Independent Encoding)
Granted. It should be in either ISCII or Unicode or some
other coded character set, rather than the array of font
index anyway.
> \|/
> XOM <-- FIE to Glyph Rule file for every Language.
> | @ Runtime depending upon the user Lang setting
> | correct rule file is selected.
The mechanism/framework to render CTL(Complex Text layout
language) for XOM is called XomCTL.
XomCTL is not yet integrated into XFree86 4.2.0,
but the code of XomCTL enabled version of Xlib is
already available from cvs.li8nux.org as a part of
Xlib-I18N. You also need to checkout liblayout,
which implements PLS(Portable Layout Service).
cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot login
(no passwd needed)
cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot co Xlib-I18N
cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot co liblayout
Under Xlib-I18N directory, there is a ordinally xc/lib/X11
structure which you can copy onto XFree86.4.2.0 source
tree to build XomCTL enabled XFree86 4.2.0. (Build
liblayout first, because XomCTL enabled Xlib requires it)
BTW, the indic layout logic itself does not come with
these packages, and actually I do not have the ISCII
version handy, so you need to define it, according
to your font encodings including the shape charset
indexes.
Enjoy!
--
hiura@{{li18nux,freestandards,unicode}.org,sun.com} http://www.li18nux.org
Chair, Li18nux/Linux Internationalization Initiative, Free Standards Group
Architect/Sr. Staff Engineer, Sun Microsystems, Inc, USA FAX 650-786-9553
_______________________________________________
I18n mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/i18n
