openjdk team mailing list archive

[Keechang Kim <keechang@xxxxxxxxxxx>]

90-fonts-nanum.conf and 30-cjk-aliases.conf, for example, have somewhat
different instructions. One can, of course, remove altogether the lines
concerning Korean fonts from 30-cjk-aliases.conf and then it would be ok
with 90-fonts-nanum.conf alone. With the current instructions contained
in 30-cjk-aliases.conf, however, ttf-unfont will be regarded as the
preferred font for certain missing fonts.

-- 
You received this bug notification because you are a member of OpenJDK,
which is subscribed to openjdk-6 in Ubuntu.
https://bugs.launchpad.net/bugs/792471

Title:
  Change default Korean font to ttf-nanum

Status in Fontconfig - Font Configuration Library:
  Confirmed
Status in “fontconfig” package in Ubuntu:
  In Progress
Status in “language-selector” package in Ubuntu:
  Fix Released
Status in “openjdk-6” package in Ubuntu:
  Confirmed
Status in “ubuntu-meta” package in Ubuntu:
  Fix Released

Bug description:
  This report affects ubuntu-desktop, language-support-fonts-ko and language-selector-common.
  Since Sep. 2007, ttf-unfonts-core has been a suggested package of ubuntu-desktop. In a default install, Unfonts are set as the default Korean font.
  A superior quality Korean font (ttf-nanum) became available as from late 2010 under OFL. In May 2011, Google ChromeOS adopted ttf-nanum as the default Korean font. After an extensive discussion in the Ubuntu Korean LoCo Mailing list since last year, a consensus has now been reached that it is time to migrate to ttf-nanum as the default Korean font in Ubuntu. 
  To achieve this, (1) ttf-unfonts-core (7.4Mb package size) must be replaced with ttf-nanum (7.5Mb package size) as the suggested package of ubuntu-desktop (2) language-support-fonts-ko should now include ttf-unfonts-core and ttf-nanum-coding (3) appropriate changes need to be made in some of the configurations files shipped with language-selector-common and fontconfig-config (proposed patches are attached herewith).

To manage notifications about this bug go to:
https://bugs.launchpad.net/fontconfig/+bug/792471/+subscriptions