To: unicode(at)unicode.org
From: Rick Cameron Rick.Cameron(at)crystaldecisions.com
Received: (qmail 19825 invoked by uid 0); 11 Jul 2003 16:13:23 -0000

from unicode.org (209.235.17.55) by ns.need.bg with SMTP; 11 Jul
 2003 16:13:23 -0000

from sarasvati.unicode.org (localhost.localdomain [127.0.0.1]) by
 unicode.org (8.11.6/8.11.6) with ESMTP id h6BG9Hs01032; Fri, 11 Jul 2003
 12:09:17 -0400

with ECARTIS (v1.0.0; list unicode); Fri, 11 Jul 2003 12:09:17 -0400
 (EDT)

from VANEXCH01.crystald.net (user.seagatesoftware.com [204.50.113.28]) 
by unicode.org (8.11.6/8.11.6) with ESMTP id h6BG9Gs01026 for ; Fri,
 11 Jul 2003 12:09:16 -0400

by vanexch01.crystald.net with Internet Mail Service (5.5.2656.59) id ;
 Fri, 11 Jul 2003 09:09:09 -0700
Date: Fri, 11 Jul 2003 09:09:08 -0700
XMailer: Internet Mail Service (5.5.2656.59)
MIMEVersion: 1.0
ContentType: text/plain
Subject: RE: Combining diacriticals and Cyrillic
Body: Ah, but what you don't realise [and it's not surprising, because MSDN
doesn't make it clear] is that when ScriptTextOut calls ExtTextOut, it
passes glyph indices, and uses the ETO_GLYPH_INDEX option. 

Thus, the two statements are perfectly consistent. For once, Philippe's
bold statement of fact is right. ;^)

(BTW, the authority for my bold statement of fact above is a conversation
with David Brown, the architect of Uniscribe)

Cheers

- rick cameron

-----Original Message-----
From: Andrew C. West [mailto:andrewcwest(at)alumni.princeton.edu] 
Sent: Friday, 11 July 2003 8:53
To: unicode(at)unicode.org
Subject: Re: Combining diacriticals and Cyrillic


On Fri, 11 Jul 2003 13:15:14 +0200, Philippe Verdy wrote:

> The Win32 Text APIs (such as TextOut) actually DO support UniScribe 
> transparently on Windows XP... In most applications, this means that 
> the UniScribe support works without requiring explicit calls to the 
> Uniscribe API.

Surely some mistake here.


Starting with Microsoft Windows 2000, these functions [TextOut, ExtTextOut,
TabbedTextOut, DrawText, and GetTextExtentExPoint] have been extended to
support complex scripts. In general, this support is transparent to the
application. 


The [Uniscribe] ScriptTextOut function takes the output of both ScriptShape
and ScriptPlace calls and calls the operating system ExtTextOut function
appropriately. 

Now if Uniscribe's ScriptTextOut function calls ExtTextOut, and according to
Philippe ExtTextOut utilises Uniscribe to output text ...

No, I don't think so. There is a big difference between support complex
scripts (MSDN) and support UniScribe (Philippe). I don't know what the
exact implementation of complex script support is for ExtTextOut etc., but
I'm pretty sure that it is independant of Uniscribe. Maybe I'm wrong, but at
least I'm not going to dress up a wild guess as a statement of certain fact
as Philippe so likes to do (and it is disingenuous of him to pretend that we
are all picking on him because his English is not good enough - there's
nothing ambiguous about his misleading statements, and if he wants to repeat
them in French they'll still be misleading or just plain wrong).

Andrew