Re: [Indic-computing-devel] Re: NCST Indix Examined

[<jk...@Fr...>]

ks> I can definately think about redesigning of IndiX once it
ks> will be proved that it really breaks protocol. 

I'm happy to hear that.  I've only heard good reports of the Indic
(Devanagari) rendering aspects of IndiX.

ks> have also decided to keep quiet on the issues like
ks> XUtf8DrawString and XmbDrawString which we believe sends

I didn't think this list is the place to clear the basic
misconceptions about X programming.

Since you seem unable (unwilling?) to do your own homework, I'll do it
for you (this once).

Please start with:

      "i18n mechanism"
      http://www.xfree86.org/pipermail/i18n/2002-February/003074.html

and follow the thread, in particular the replies from Tomohiro KUBOTA

      http://www.xfree86.org/pipermail/i18n/2002-February/003077.html

and Keith Packard.

      http://www.xfree86.org/pipermail/i18n/2002-February/003078.html

OR the answers to my question here:
   
   "Complex text layout and mapping screen coordinates"
   http://www.xfree86.org/pipermail/fonts/2002-February/001331.html

OR Arun Sharma's continuation of this argument on those lists:

   http://www.xfree86.org/pipermail/fonts/2002-February/001341.html

OR this discussion here:

   "Another approach to text in X"
   http://www.xfree86.org/pipermail/fonts/2002-February/001339.html

These links should help to clarify matters in a more efficent manner
than any discussion on <indic-computing-devel> could hope to achieve.

Could you please take further discussion of basic X concepts and X
programming to the XFree86 lists?  They are a better place for such
discussions.

We can discuss IndiX being part of the Bootable CD once it is
re-designed to be protocol compliant.

Regards,
Koshy
<jk...@fr...>