ubuntu-translations-coordinators team mailing list archive

[Gunnar Hjalmarsson <835304@xxxxxxxxxxxxxxxxxx>]

Jinkyu Yi (jincreator) wrote on 2011-11-30:
> 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).

What is the "lang" option in fontconfig? Is it possibly something that
makes the LANG env. variable control the fontconfig settings, and can
this have something to do with the fact that language-selector's
fontconfig hack basically has been controlled by the LANGUAGE env.
variable (i.e. not LANG)?

-- 
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