Different base fonts for Russian clients #6


  • Defect
  • Fixed
Closed
Assigned to elkano
  • Phanx created this issue Sep 5, 2012

    In WoW 5.x, Blizzard added a number of new font files to accomodate non-Latin languages. LibSharedMedia-3.0 doesn't recognize these (at least for Russian), so Russian users are unable to use Friz Quadrata, Morpheus, or Skurri, as selecting one of those fonts will simply show ??? since the files used don't support Cyrillic characters.

    Solution:

    LibSharedMedia-3.0 should detect the user's locale as ruRU and register the following fonts with the appropriate path to their Cyrillic version instead of their Latin version:

    • Friz Quadrata: Latin FRIZQT__.ttf (2 underscores) ==> Cyrillic FRIZQT___CYR.TTF (3 underscores)
    • Morpheus: Latin MORPHEUS.TTF ==> Cyrillic MORPHEUS_CYR.TTF
    • Skurri: Latin SKURRI.TTF ==> Cyrillic SKURRI_CYR.TTF

    There are also new font files supporting Korean and Chinese characters, but I'm not sure offhand which ones are used as equvalent to Friz Quadrata etc.

  • Phanx added the tags New Defect Sep 5, 2012
  • Elkano posted a comment Sep 6, 2012

    LSM-3.0 already does locale based font registration, though not having installed non-latin clients it's hard to notice changes in the fonts used. Do you know if they also have a special version for Arial Narrow and if they still use Nimrod MT?

  • Phanx posted a comment Sep 6, 2012

    I actually just committed a fix; after actually looking at the code it was trivial. Arial Narrow already supports Cyrillic, and Nimrod MT does too.

    FYI if you have a beta account, you can log into the beta servers in any language except zhCN. ;)

    I also added the Blizzard compact unit frame bar texture, since it seemed to fit with the standard unit frame bar texture and character skills bar texture, but feel free to remove it if you don't think it should be in there.

  • Elkano posted a comment Sep 6, 2012

    it seems like all fonts are now distributed with the client, so I don't understand why they didn't just replace the old ones... :/

    also, currently looking at the characters supported by these fonts so I can enable them on other locales, too.

    /€dit: Now I know why... they also placed Cyrillic characters in positions where they aren't supposed to be... ...and then mapped them to the position where they should be...


    Edited Sep 6, 2012
  • Elkano removed a tag New Sep 8, 2012
  • Elkano added a tag Fixed Sep 8, 2012
  • Elkano closed issue Sep 8, 2012

To post a comment, please login or register a new account.