From: "Roozbeh Pournader" <[EMAIL PROTECTED]> > CP1256 has never supported FARSI YEH.
> No it's not. Persian locale is only avaiable on Windows 2000 and XP, which > are Unicode based. Unfortunately, it is a bit more complicated then that. GetLocaleInfo/LOCALE_IDEFAULTANSICODEPAGE for Farsi does indeed return 1256. Because of this, CP_ACP when you select a Farsi default system locale is also 1256. My original post that showed the mapping on Win2000/WinXP to 0xED was mistaken; this is a "best fit" mapping, which if you try to round trip you will see ends up back at U+064A. There are several of these "best fit" mappings -- at least eight of them , perhaps even an infinite number. :-) In retrospect, it would have been better to treat Farsi as a Unicode-only locale, but even back in NT4 this was done. Perhaps a LOCALE_IACTUALANSICODEPAGE needs to be added to help "fix up" these things? <g> MichKa Michael Kaplan Trigeminal Software, Inc. http://www.trigeminal.com/
