← Back to team overview

ubuntu-translations-coordinators team mailing list archive

[Bug 835304] Re: contained fontconfig setting files force to make it default font

 

Martin Pitt,

I think the best way to configure CJK without language-selector fontconfig hack is ttf-nanum is apply to fontconfig itselt, not using setting file in font package.
Korean sans-serif font "UnDotum" is good example.
Package "ttf-unfonts-core" provide it without any setting files.
But it works even without language-selector's Korean fontconfig hack(69-language-selector-ko-kr.conf) because one of fontconfig's default config file(65-nonlatin.conf) specifies to use "Undotum" as sans-serif font.
Also, "ttf-nanum"'s fontconfig file name is starting with "90-~" so it can overwrite fontconfig(+language-selector)'s settings.

In debian/90-ttf-nanum.conf line 49, there is comment...
 "TODO: it will be moved to fontconfig default configs -->"
It means this is just workaround, and for now I think it is problem to Ubuntu.

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