Forums

Non-latin characters are not displayed in POL prefixes

Is there an equivalent to winetricks' font packages?

Auteur Réponses
carlos.mason Mercredi 30 Janvier 2013 à 22:42
carlos.masonAnonymous

Perhaps I'm just dense.  But I can't seem to figure out how to get non-Latin characters to be properly displayed in any applications of any POL prefixes.  Instead I just see a white rectangle, "▯", in place of the Unicode character meant to represent the 'foreign' character.  However, this isn't the case when using winetricks to install fonts in
non-POL prefixes (e.g. ~/.wine).  When the correct font packages are
installed, non-Latin character appear as expected.

I thought perhaps installing the Microsoft Core Fonts component might remedy the problem, unfortunately it did not.  I've tried manually installing font's in the prefixes themselves
(copying fonts to
~/.PlayOnLinux/wineprefix/<$PREFIX>/drive_c/windows/Fonts/), but that too, seems to have no effect.  I even tried to use winetricks to install the requisite fonts in my POL prefixes.  But it appears that POL and winetricks are incompatible.

Is there some other component I need to install or configuration option to be tweaked in order to display Unicode characters?


FYI, I'm presently using POL 4.1.9 with Wine 1.4.1 (System) or 1.5.21.  I'm not receiving any warning or error output either.




petch Mercredi 30 Janvier 2013 à 23:57
petch

Hi, I don't understand what could be wrong, but if you want to run winetricks in a virtual drive (we don't officially support it, but that can still be useful for testing, for example), that can be done:
- open a terminal in the virtual drive (Configure button > (select the virtual drive) > Miscellaneous tab > "Open a shell" button)
at that point there's enough environment initialized for POL statements, but not to run plain wine statements (and programs using them, like winetricks), so
- type "POL_Wine_AutoSetVersionEnv"
and from there on you should have a full environment to start winetricks...

Not sure it will help, but could you paste the result of the "locale" command in that environment?
carlos.mason Jeudi 31 Janvier 2013 à 4:07
carlos.masonAnonymous

Hi, I don't understand what could be wrong, but if you want to run winetricks in a virtual drive (we don't officially support it, but that can still be useful for testing, for example), that can be done:
- open a terminal in the virtual drive (Configure button > (select the virtual drive) > Miscellaneous tab > "Open a shell" button)
at that point there's enough environment initialized for POL statements, but not to run plain wine statements (and programs using them, like winetricks), so
- type "POL_Wine_AutoSetVersionEnv"
and from there on you should have a full environment to start winetricks...

Quote from petch


Following your instructions, I was able to achieve partial success and I think ascertain the cause.  In winetricks you can install the cjkfonts package or, oddly enough, the fakekorean package to enable the rendering of most Chinese, Japanese, and Korean characters.  These packages create aliases to to the fonts they install.  Otherwise, you have to use a font that explicitly supports a given alphabet (e.g. IPAex Mincho).  As it turns out, fakechinese and fakejapanese don't seem to work for Chinese or Japanese characters, but that's probably a bug in winetricks.  Unfortunately though, other characters (from Arabic, Greek, Hebrew, etc. alphabets) still don't render correctly, regardless of which prefixes are used.

For those it may concern, I was playing around in notepad, selecting random Hiragana and Katakana characters in Gnome's Character Map app. I found at least one character that rendered when using IPAex Mincho that dosen't render using System/Baekmuk (Baekmuk having been installed by the fakekorean package).  So if you do choose to use winetricks to create font aliases for CJK characters, you may find some still aren't rendered correctly.

Not sure it will help, but could you paste the result of the "locale" command in that environment?

Citer


LANG=en_US.UTF-8
LANGUAGE=
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=


I don't see anything wrong here, but then I'm not sure how these variables would affect POL or Wine.


If you have any tips on getting other alphabets to render correctly, I'd appreciate it.

Edité par carlos.mason