I compared the results of CT_CTYPE1 GetStringTypeW() between Windows 2000 and Wine and found a lot of differences (about 12000 of them). Nothing really spectacular, e.g. codepoint 0x00b5 (MICRO SIGN) is classified C1_PUNCT in Win2k and (C1_ALPHA | C1_LOWER) in Wine. I noticed that the Wine table is generated from information on ftp.unicode.org, so I'm wondering if the table generation is correct or if Microsoft made some strange choices?
Gé van Geldorp.
"Ge van Geldorp" gvg@reactos.com wrote:
I compared the results of CT_CTYPE1 GetStringTypeW() between Windows 2000 and Wine and found a lot of differences (about 12000 of them). Nothing really spectacular, e.g. codepoint 0x00b5 (MICRO SIGN) is classified C1_PUNCT in Win2k and (C1_ALPHA | C1_LOWER) in Wine. I noticed that the Wine table is generated from information on ftp.unicode.org, so I'm wondering if the table generation is correct or if Microsoft made some strange choices?
That's a known incompatibility. Another one is sort weight tables. We can do nothing to fix it, unicode.org and Microsoft have very different unicode tables.
Do you have an app which depends on GetStringTypeW return values?
From: Dmitry Timoshkov
"Ge van Geldorp" gvg@reactos.com wrote:
I compared the results of CT_CTYPE1 GetStringTypeW() between Windows 2000 and Wine and found a lot of differences
That's a known incompatibility. Another one is sort weight tables. We can do nothing to fix it, unicode.org and Microsoft have very different unicode tables.
Ok, I remember a discussion about sort weight tables some time ago.
Do you have an app which depends on GetStringTypeW return values?
No, I was just porting some Wine routines to ReactOS and was a little bit surprised when I tested the result and found the difference with Windows. I guess we'll have to live with it just like you guys do.
Ge van Geldorp.
-
Dmitry Timoshkov -
Ge van Geldorp