--- In qalam@yahoogroups.com, Marco Cimarosti <marco.cimarosti@...>
wrote:

> suzmccarth wrote:

> Hmmm... There's a bit of misunderstanding here.

> Uniscribe has nothing to do with editing or typing. It is the

module which

> handles the *display* of text.

<Snip>

> On the other hand, the keyboard driver is a module which interprets
> keystrokes on the keyboard, convert them into character codes

(e.g., "a") or

> in function codes (e.g., DELETE) and sends them to the editing

module. It

> does not know nor need to know what the editing module will do

with this

> information.

<Snip>

> As Uniscribe module and the editing module run at the same time,

the net

> effect is that typing on the keyboard you see text changing on the

screen.

> But, actually, there is no interaction between the two modules

apart the

> fact that they access the same text data in memory.

This is not quite true. You're forgetting the mouse! Uniscribe
will convert pixel positions to character positions (see
http://msdn.microsoft.com/library/en-us/intl/uniscrib_4ka8.asp ),
and if this documentation is correct, it may, seemingly at its own
discretion, refuse to return a character position within
a 'cluster', e.g. an 'akshara'. Semites seem more privileged than
Indians - the former are allowed to click on vowel points in their
native scripts.

Richard.