http://bugs.winehq.org/show_bug.cgi?id=16325
Aric Stewart aric@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |aric@codeweavers.com
--- Comment #98 from Aric Stewart aric@codeweavers.com 2009-11-08 04:06:01 --- I believe this is a System default fallback issue.
Windows in CJK locales have the ability to fall back to a default fonts to find missing glyphs. Windows in other locales do NOT do this. so in wine we have only activated this logic for CJK locales.
The registry key that is looked for is:
HKLM\Software\Microsoft\Windows NT\CurrentVersion\FontLink\SystemLink "Microsoft Sans Serif"
It is a REG_SZ_MULTI string that sepecifies font files,font name.
for example on my Japaense windows machine i see
MSGOTHIC.TTC,MS UI Gothic","gulim.ttc,gulim","SimSun.TTC,SimSun","mingliu.ttc,PMingLiU
The tricky issue is that it uses font file names, and redirects inside wine does not work to follow them.
So a distribution packager would need to make sure that fonts that exist on the system are what are listed.
Then when wine is run in the CJK locale it should properly fall back to finding glyphs in these fonts.
Now again I would need Chinese and Korean users to confirm that this entry is correct. It may order differently based on locale of the windows install. I am unsure if it was because I was looking at a Japanese machine that MSGOTHIC.TTC was first (the Japanese Font) of it the Microsoft fonts are just such that Japanese is listed first then Korean, then Chinese Simplified and then Chinese Traditional.
-aric