Of these, only U+06A9 exists in the Windows CP1256, as can be
demonstrated by using MultiByteToWideChar() API or by reading
ftp://ftp.unicode.org/Public/MAPPINGS/VENDORS/MICSFT/WINDOWS/CP
1256.TXT
Bob Hallissy
[As an interesting aside, the WideCharToMultiByte() API maps
both U+06CC (FARSI YEH) and U+064A (YEH) to Windows character
code 237 (xED). ]
From: <[EMAIL PROTECTED]> AT Internet on 12-07-2000
11:53
To: <[EMAIL PROTECTED]> AT Internet@Ccmail
cc: <[EMAIL PROTECTED]> AT Internet@Ccmail (bcc: Bob
Hallissy/IntlAdmin/WCT)
Subject: Re: Persian developers (was Re: Detecting installed
fonts in
On Wed, 12 Jul 2000, Michael (michka) Kaplan wrote:
> One thing they do is use the LATEST cp 1256, which includes
the Farsi > characters, so the hacks are not needed.... and
then they would not have to > move to Unicode, actually. I ran
across several localizers who were willing > to produce files
in three formats:
Would you please give me a link to the conversion table from
the latest CP1256? The version I saw on the Unicode web site
lacks:
U+066B ARABIC DECIMAL SEPARATOR
U+06A9 ARABIC LETTER KEHEH
U+06C0 ARABIC LETTER HEH WITH YEH ABOVE
U+06CC ARABIC LETTER FARSI YEH
which are needed for Persian.
--roozbeh
