[Bug 55132] New: Shoujo-tachi wa Kouya o Mezasu: (Japanese) text does not display in settings utility
https://bugs.winehq.org/show_bug.cgi?id=55132
Bug ID: 55132 Summary: Shoujo-tachi wa Kouya o Mezasu: (Japanese) text does not display in settings utility Product: Wine Version: 8.10 Hardware: x86-64 URL: http://minatosoft.com/koya/download/ OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: pernegger@gmail.com Distribution: ---
Created attachment 74685 --> https://bugs.winehq.org/attachment.cgi?id=74685 wine 8.10 terminal output
Note: The trial version is free to download, see URL. Any of the mirrors / DOWNLOAD links will do. No need to install, just run from the lower-level directory.
The settings utility--run Launcher.exe, select the middle option in the top row--is missing most of the Japanese text in the UI. All the elements that look a bit like tabs should be labelled. It seems to work if the label is in Latin letters, but Japanese is broken. See screenshots.
The tooltips that appear at the bottom work fine as well.
Setting LANG/LC_ALL to ja_JP.UTF-8 doesn't help.
Terminal output is attached but unhelpful. Since it's so quick and easy to reproduce it's probably quicker if someone who knows what they're doing gives it a quick whirl anyway.
https://bugs.winehq.org/show_bug.cgi?id=55132
--- Comment #1 from pernegger@gmail.com --- Created attachment 74686 --> https://bugs.winehq.org/attachment.cgi?id=74686 screenshot 1
https://bugs.winehq.org/show_bug.cgi?id=55132
--- Comment #2 from pernegger@gmail.com --- Created attachment 74687 --> https://bugs.winehq.org/attachment.cgi?id=74687 screenshot 2
https://bugs.winehq.org/show_bug.cgi?id=55132
pernegger@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download
https://bugs.winehq.org/show_bug.cgi?id=55132
--- Comment #3 from Rafał Mużyło galtgendo@o2.pl --- As long as it's run in the Japanese locale, the full text shows up sort of correctly for me (the 'sort of' part is that the antialiasing looks broken).
So you either need Fonts/Replacements keys set up or this is a variant of bug 42606.
https://bugs.winehq.org/show_bug.cgi?id=55132
--- Comment #4 from pernegger@gmail.com --- So much for "easy to reproduce" ...
Japanese locale is set.
There's a full set of (Japanese) Windows TrueType fonts in the fontconfig search path, though I suppose this kind of dialogue might still use bitmap fonts?
Is there any way to find out what exactly it's missing?
Anyway, thanks for looking into this.
https://bugs.winehq.org/show_bug.cgi?id=55132
--- Comment #5 from Rafał Mużyło galtgendo@o2.pl --- The only (relevant here) font replacements I have set up are for MS default fontsets (3 Gothic and 2 Mincho) including their Japanese names (I'm not sure if that part is still necessary as over the years there have been a few commits that might have addressed it, but I see no harm in keeping those).
Bug 42606 has a workaround patch and could be tested for by creating a *clean* prefix in the Japanese locale (WINEPREFIX=<whatever>) - that way the cached values will be the Japanese ones.
https://bugs.winehq.org/show_bug.cgi?id=55132
--- Comment #6 from pernegger@gmail.com --- Would you mind sharing your relevant font replacements? Maybe the HOWTO you used, if any? I've never needed any before, and I'm not getting anywhere just using Google, I'm afraid.
FWIW, WINE regedit also shows weird behaviour. Japanese text shows up fine--except while editing Japanese names/data, i.e. when the text changes into a textbox in place, then Japanese characters show up as boxes. Confirm the edit, and all is fine again.
https://bugs.winehq.org/show_bug.cgi?id=55132
--- Comment #7 from Rafał Mużyło galtgendo@o2.pl --- Created attachment 74696 --> https://bugs.winehq.org/attachment.cgi?id=74696 my font replacements
Change the fonts to ones that are on your system.
(pity there's no *good* replacement for the UI variant - MS in their unending wisdom decided to make wide space non-wide and all fonts that I know, that claim to be metric substitutes fail to account for that)
https://bugs.winehq.org/show_bug.cgi?id=55132
--- Comment #8 from pernegger@gmail.com --- Created attachment 74700 --> https://bugs.winehq.org/attachment.cgi?id=74700 screenshot 1, working version
https://bugs.winehq.org/show_bug.cgi?id=55132
--- Comment #9 from pernegger@gmail.com --- Created attachment 74701 --> https://bugs.winehq.org/attachment.cgi?id=74701 screenshot 2, working version
https://bugs.winehq.org/show_bug.cgi?id=55132
--- Comment #10 from pernegger@gmail.com --- (In reply to Rafał Mużyło from comment #7)
my font replacements
Change the fonts to ones that are on your system.
The funny thing is, I *have* all these fonts. Nevertheless, it works. Thank you!
The only entry that is actually required in this case is
[HKEY_CURRENT_USER\Software\Wine\Fonts\Replacements] "ＭＳ ゴシック"="MS Gothic"
In other words, even though the original MS Gothic is available, and WINE uses it in other contexts just fine (including the in-game text for this very game), something about the way it's accessed here via its Japanese name prevents it from being found.
I get the rationale that actual font replacements (for missing fonts) are system-dependent and thus out of scope for WINE, but this still feels like a bug. Windows will find the font using either name, after all.
Is there an elegant way to have such registry entries added to all new prefixes, ideally regardless of WINE version?
(I also attached working versions of the two screenshots, to document how the "missing" font affects the layout and style of the dialogue; it's not just missing text.)
https://bugs.winehq.org/show_bug.cgi?id=55132
--- Comment #11 from Rafał Mużyło galtgendo@o2.pl --- ...well, font matching in wine...
It works pretty well...as long as you only need a single font.
If the match doesn't have the glyphs you actually need, you're likely pretty screwed. This is just one example of it.
But doing this properly would likely require something like pango and despite some of its shortcomings, that's a pretty complex beast.
https://bugs.winehq.org/show_bug.cgi?id=55132
--- Comment #12 from Rafał Mużyło galtgendo@o2.pl --- ...though there's an idea: perhaps lfCharSet could be used as a sort-of hint and be translated to 'lang=<foo>' tag in the fontconfig string ? That should get better matches from fontconfig...
https://bugs.winehq.org/show_bug.cgi?id=55132
--- Comment #13 from Rafał Mużyło galtgendo@o2.pl --- ...never mind, while that seems like it should work, local fontconfig setup may easily prevent that from working *well*...
-
WineHQ Bugzilla