ubuntu-translations-coordinators team mailing list archive

[Martin Pitt <martin.pitt@xxxxxxxxxx>]

I still don't understand the problem, sorry.

> I think the best way to configure CJK without language-selector
fontconfig hack is ttf-nanum is apply to fontconfig itselt

Why? It doesn't make a difference, and it even sounds worse because the
config can't be right or at least perfect if the ttf-nanum package is
not installed.

> But it works even without language-selector's Korean fontconfig
hack(69-language-selector-ko-kr.conf)

I was actually hoping that we could get rid of language-selector's
fontconfig hack with the proper fontconfig snippet in the -nanum
package.

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