http://bugs.winehq.org/show_bug.cgi?id=13600
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID
--- Comment #33 from Dmitry Timoshkov dmitry@codeweavers.com 2008-06-09 07:46:43 --- (In reply to comment #32)
However, this whole bug is about emulating the existence of a font, not about behaviour of Wine when a font is missing.
Wine *does not* emulate an existence of a certain font. If a font is missing it should be added, that was the case for Tahoma, that's the case for Times New Roman (bug 9623).
This is a minimal regedit file that fixes my application: REGEDIT4 [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\FontSubstitutes] "System"="MS Shell Dlg" [HKEY_USERS\S-1-5-4\Software\Wine\Fonts\Replacements] "MS UI Gothic"="Sazanami Gothic"
That's exactly which I was talking about - a missing Windows font. This clearly makes this bug invalid.
Not really. First a system font that is expected to exist on Windows should not be missing for Wine to create a usable runtime emulation layer. Secondly looking at the trace it looks like the font in fact exists but is deficient. When running Notepad I get a font that is called 'System', looks as ugly as the one used in my test application when the fonts are not substituted (uppercase letters are shown using line width different from lowercase), and does not work for Japanese. From the trace it looks like the font is jvgasys.fon. It claims to support Japanese (the only script the font selection dialog offers for it is Japanese) but does not have the Japanes glyphs - at least for the Kana characters I tried.
jvgasys.fon does not contain japanese glyphs, a Windows one doesn't either.
Please stop re-opening this bug, it is invalid.