get unicode character OEMTextOut

Hello all,

Someone could help me on how to get the unicode character in the
OEMTextOut implementation when (pstro->flAccel & SO_GLYPHINDEX_TEXTOUT)
is true.

Thanks in advance

bobbym
Wed Jun 01 13:49:00 CDT 2005

------=_NextPart_0001_D78E3EB9
Content-Type: text/plain
Content-Transfer-Encoding: 7bit


--------------------
From: "news.edisontel.com" <software@ditron.net>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
Newsgroups: microsoft.public.development.device.drivers
Subject: get unicode character OEMTextOut
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Hello all,

Someone could help me on how to get the unicode character in the
OEMTextOut implementation when (pstro->flAccel & SO_GLYPHINDEX_TEXTOUT)
is true.

Thanks in advance

There is not always a 1:1 mapping between glyph indices and character codes
and vice versa.
This is expecially true with international character sets like Hebrew,
Arabic etc.

So once you get this as SO_GLYPHINDEX_TEXTOUT, your driver should handle
the glyph itself instead of trying to convert it back to Unicode.


Thank you,
Bobby Mattappally
Microsoft

This posting is provided "AS IS" with no warranties, and confers no rights.

------=_NextPart_0001_D78E3EB9
Content-Type: text/x-rtf
Content-Transfer-Encoding: 7bit

{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fnil\fprq2\fcharset0 MS Sans Serif;}}
\viewkind4\uc1\pard\f0\fs20
\par \pard\li720 --------------------
\par From: "news.edisontel.com" <software@ditron.net>
\par User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
\par X-Accept-Language: en-us, en
\par MIME-Version: 1.0
\par Newsgroups: microsoft.public.development.device.drivers
\par Subject: get unicode character OEMTextOut
\par Content-Type: text/plain; charset=ISO-8859-1; format=flowed
\par
\par Hello all,
\par
\par Someone could help me on how to get the unicode character in the
\par OEMTextOut implementation when (pstro->flAccel & SO_GLYPHINDEX_TEXTOUT)
\par is true.
\par
\par Thanks in advance
\par \pard
\par There is not always a 1:1 mapping between glyph indices and character codes
\par and vice versa.
\par This is expecially true with international character sets like Hebrew,
\par Arabic etc.
\par
\par So once you get this as SO_GLYPHINDEX_TEXTOUT, your driver should handle the glyph itself instead of trying to convert it back to Unicode.
\par
\par
\par Thank you,
\par Bobby Mattappally
\par Microsoft
\par
\par This posting is provided "AS IS" with no warranties, and confers no rights.
\par
\par
\par }
------=_NextPart_0001_D78E3EB9--

jack
Thu Jun 02 00:52:43 CDT 2005

Since I am writing a postscript printer driver that must to capture all
the text present in the document in order to save the original document
and a file that has only the text part of the original one.
I thought to do this catching all the call to the OEMTextOut function
but seems that this is not always possible.
Is there any other way to do this?

Thanks
Jack