by scott967 » Tue Sep 04, 2012 6:50 pm
Don't have an answer to your problem, but I haven't had any problem with displaying east Asian glyphs (characters) in MM4 on Win 7 (through 4.06).
Was curious about font issues in Windows in general, so did some digging. Still don't really have a grip o it, but it seems like:
1. The fonts used in MM4 are controlled by the skin in use. The skin I am currently on (Vitreous) seems to use Tahoma for most text. Note: My language setting is en (default) in MediaMonkey.ini.
2. In Windows since Win98 there is a system to allow for font substitution when the selected font doesn't provide the necessary glyph. How this substitution gets done depends on a couple of factors, which determine how text is drawn and displayed on your system (most common is that a program uses GDI though I guess now MS is promoting DirectWrite as an alternative). There is something called "Uniscribe" which has to be turned on in Win XP (along with many non-latin fonts) but is on automatically in I guess Vista and up. Uniscribe is designed to work with "complex fonts" (for example, right-to-left ordering, etc) but I guess may help with "normal" font rendering (I believe the fonts used must be of the "open-type" variety). Uniscribe has the concept of "fallback fonts" which are used when the required character\glyph isn't in the selected font. I couldn't find a description of the actual fallbacks.
An alternative method is to use GDI font linking to accomplish the same thing (finding an appropriate font for a character/glyph that isn't in the selected font). Font linking is set up in the registry under a key
HKLM/SOFTWARE/Microsoft/Windows NT/CurrentVersion/FontLink/SystemLink
For example for Tahoma it shows:
MSGOTHIC.TTC,MS UI Gothic
MINGLIU.TTC,PMingLiU
SIMSUN.TTC,SimSun
GULIM.TTC,Gulim
which should allow display for most Unicode glyphs.
3. MediaMonkey AFAICT is using Unicode / UTF-16 to represent all text data (character/strings) as does windows. So there shouldn't be any issue with the internal storage, library database, etc. Just a display issue.
So, based on what I can find out I would suggest first trying a different skin and seeing if that works. If that doesn't work my guess would be some sort of problem with the font linking. But if that was the case I would think you would see a problem in other programs in addition to MM.
scott s.
.
Don't have an answer to your problem, but I haven't had any problem with displaying east Asian glyphs (characters) in MM4 on Win 7 (through 4.06).
Was curious about font issues in Windows in general, so did some digging. Still don't really have a grip o it, but it seems like:
1. The fonts used in MM4 are controlled by the skin in use. The skin I am currently on (Vitreous) seems to use Tahoma for most text. Note: My language setting is en (default) in MediaMonkey.ini.
2. In Windows since Win98 there is a system to allow for font substitution when the selected font doesn't provide the necessary glyph. How this substitution gets done depends on a couple of factors, which determine how text is drawn and displayed on your system (most common is that a program uses GDI though I guess now MS is promoting DirectWrite as an alternative). There is something called "Uniscribe" which has to be turned on in Win XP (along with many non-latin fonts) but is on automatically in I guess Vista and up. Uniscribe is designed to work with "complex fonts" (for example, right-to-left ordering, etc) but I guess may help with "normal" font rendering (I believe the fonts used must be of the "open-type" variety). Uniscribe has the concept of "fallback fonts" which are used when the required character\glyph isn't in the selected font. I couldn't find a description of the actual fallbacks.
An alternative method is to use GDI font linking to accomplish the same thing (finding an appropriate font for a character/glyph that isn't in the selected font). Font linking is set up in the registry under a key
HKLM/SOFTWARE/Microsoft/Windows NT/CurrentVersion/FontLink/SystemLink
For example for Tahoma it shows:
MSGOTHIC.TTC,MS UI Gothic
MINGLIU.TTC,PMingLiU
SIMSUN.TTC,SimSun
GULIM.TTC,Gulim
which should allow display for most Unicode glyphs.
3. MediaMonkey AFAICT is using Unicode / UTF-16 to represent all text data (character/strings) as does windows. So there shouldn't be any issue with the internal storage, library database, etc. Just a display issue.
So, based on what I can find out I would suggest first trying a different skin and seeing if that works. If that doesn't work my guess would be some sort of problem with the font linking. But if that was the case I would think you would see a problem in other programs in addition to MM.
scott s.
.