ubuntu-translations-coordinators team mailing list archive

[Jinkyu Yi <835304@xxxxxxxxxxxxxxxxxx>]

Martin pitt,

The difference is, fonts-nanum/fonts-nanum-coding depends on "lang" option, but language-selector/fontconfig-config does not.
And, "lang" option is not working at Ubuntu(in my test).
But fontconfig-config doesn't have information about Nanum fonts.
As a result, Un fonts become default Korean fonts because it has higher priority than Nanum fonts.

So I suggest patch fontconfig-config to have information about fonts-nanum and make it high priority in Korean fonts list.
If fonts-nanum is missing, another fonts(i.e unfonts-core) will wokr beside it.
And maybe we can remove 69-language-selector-ko-kr.conf then.

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
https://bugs.launchpad.net/bugs/835304

Title:
  contained fontconfig setting files force to make it default font

Status in Ubuntu Translations:
  Triaged
Status in “fonts-nanum” package in Ubuntu:
  New
Status in “fonts-nanum-coding” package in Ubuntu:
  New
Status in “ttf-nanum” package in Ubuntu:
  Incomplete
Status in “ttf-nanum” package in Debian:
  New

Bug description:
  This packages has 90-ttf-nanum.conf file and it contains some code to make it default Korean font by itself.
  But, default Korean font settings are at 69-language-support-ko-kr.conf by using language-selector.
  Also, it specifies fallback of the MS fonts, but these settings are provide from setting files in package "fontpackage"
  And, there's even "TODO" for remove settings later!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/835304/+subscriptions