Dmitry Timoshkov wrote:
snippage AdH
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
Alexandre Julliard [EMAIL PROTECTED] wrote:
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
I check original windows 98(Japanese edition; CP_ACP=cp932).
There are some system fonts that have codepage CP_ACP
(at least in my environments):
- System, FixedSys, Terminal
Probablly, these three 'reserved' fonts should be treated
as special font names and should have CP_ACP.
And all stock
And all stock font objects should have codepage CP_ACP, too.
Sorry,
"all stock font objects" - "all 'non-ANSI and non-OEM' stock font objects".
charset of stock objects seem to be:
ANSI_FIXED_FONT - ANSI_CHARSET (fixed)
ANSI_VAR_FONT - ANSI_CHARSET
DEFAULT_GUI_FONT - the charset of CP_ACP
TAKESHIMA Hidenori [EMAIL PROTECTED] wrote:
I check original windows 98(Japanese edition; CP_ACP=cp932).
There are some system fonts that have codepage CP_ACP
(at least in my environments):
- System, FixedSys, Terminal
Probablly, these three 'reserved' fonts should be treated
as special font
"Dmitry Timoshkov" [EMAIL PROTECTED] writes:
Note 1: Until the last changes, ALL my fonts with ALL different encodings
worked in Wine just fine. I already noted in my previous mail, code page of
currently selected font is the problem of a dc driver (display, printer, etc.) ONLY.
Well, on my
Hello.
This patch broke correct displaying of cyrillic characters:
revision 1.28
date: 2000/08/20 20:08:35; author: julliard; state: Exp; lines: +20 -14
Hidenori Takeshima [EMAIL PROTECTED]
Handle the codepage of fonts if supported by the graphics driver.
because of:
1. My app loads
Hello.
Unquestionably, this patch should be improved.
(special handling of ANSI_CHARSET should be added.)
2. Then app displays the text using ExtTextOutA. Here the problems begin.
Now ExtTextOutA assumes, that ANSI code page and code page of currently
selected font is the same. It is wrong
Alexandre Julliard [EMAIL PROTECTED] wrote:
2. Then app displays the text using ExtTextOutA. Here the problems begin.
Now ExtTextOutA assumes, that ANSI code page and code page of currently
selected font is the same. It is wrong assumption. As it was many times
pointed out (at least by me).
