"Dmitry Timoshkov" <[EMAIL PROTECTED]> writes:
> Of course, I can :-). ExtTextOutA at wine/objects/text.c takes non-unicode
> text and translates it to unicode using wrong code page. That's all.
> The used code page will be always wrong, if currently selected font will have
> another code page rather then current ANSI code page. Theoretically, the system
> could have fonts with three different code pages: ANSI, OEM, MAC. I have even more
> in addition to the mentioned ones: iso8859-1, iso8859-5, koi8-r, symbol. In my case
> ANSI = 1251, OEM = 866, MAC = 10007. So, the question: Can the fonts with the
> different code pages easy break everything?!
I don't have any Russian fonts on my Windows machine to test this, but
if I select an OEM font TextOut definitely uses the OEM codepage, not
the CP_ACP one. So we cannot assume that all strings passed to TextOut
are in current ANSI codepage; we have to take into account the font
codepage somehow.
--
Alexandre Julliard
[EMAIL PROTECTED]
