suzmccarth wrote:

> > Up to Windows 2000 backspace and delete operated on
> > codepoints [...]
>
> I do like editing a syllable at a time for Indic scripts. It
> feels right.
> I believe that an earlier Uniscribe version allowed editing [...]

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.

"Text" is an invisible, immaterial data structure which is stored in the
memory of the computer. The task of Uniscribe is reading the information in
this data structure and drawing visible glyphs on the screen which
correspond to that information. It does not know (nor need to know) where
that data came from, why it is there, or how long it has been there: the
text could have been copied from a file on disc, generated from a running
program, typed from the keyboard, etc.

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.

The editing modules receives character or function codes from the keyboard
(and commands from the mouse) and uses this information to change the
content of the invisible "Text" data structure. It does not know nor need to
know whether and how changing this data structure will cause a change on the
display.

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.

--
Marco