[LWN Logo]
[LWN.net]
From:	 bugzilla@redhat.com
To:	 redhat-watch-list@redhat.com
Subject: [RHBA-2001:145-04] New Japanese and Korean font packages available
Date:	 Tue, 6 Nov 2001 15:04 -0500

---------------------------------------------------------------------
                   Red Hat, Inc. Red Hat Bug Fix Advisory

Synopsis:          New Japanese and Korean font packages available
Advisory ID:       RHBA-2001:145-04
Issue date:        2001-10-31
Updated on:        2001-11-05
Product:           Red Hat Linux
Keywords:          hanterm charset temporary file alias ISO8859-1
Cross references:  
Obsoletes:         
---------------------------------------------------------------------

1. Topic:

As shipped, the Korean font/character set associations do not work with 
the hanterm.  Additionally, the Japanese font package contains 
sub-optimal aliases for using those fonts in a Western encoding.

2. Relevant releases/architectures:

Red Hat Linux 7.2 - i386, noarch

3. Problem description:

The Korean fonts package for Red Hat Linux 7.2 has an incorrect character 
set mapping.  This results in hanterm not being able to run correctly.

The Japanese TrueType fonts package for Red Hat Linux 7.2 
contains a number of font aliases for Western (ISO8859-1) encodings of 
those fonts.  These aliases can conflict with true ISO8859-1 system 
fonts.  Additionally, the aliases for the bold and italic ISO8859-1 
encodings of these fonts were incorrect.

Additionally, temporary files used during Korean font package 
installation have predictable names, with possible security implications.

4. Solution:

Install the new font package(s).  Additionally, an update to the eel 
(Eazel Extensions Library) package is being made available to enable use 
of the new TrueType fonts package in a Japanese GNOME environment.

Before applying this update, make sure all previously released errata
relevant to your system have been applied.

To update all RPMs for your particular architecture, run:

rpm -Fvh [filenames]

where [filenames] is a list of the RPMs you wish to upgrade.  Only those
RPMs which are currently installed will be updated.  Those RPMs which are
not installed but included in the list will not be updated.  Note that you
can also use wildcards (*.rpm) if your current directory *only* contains
the
desired RPMs.

Please note that this update is also available via Red Hat Network.  Many
people find this an easier way to apply updates.  To use Red Hat Network,
launch the Red Hat Update Agent with the following command:

up2date

This will start an interactive process that will result in the appropriate
RPMs being upgraded on your system.

5. Bug IDs fixed (http://bugzilla.redhat.com/bugzilla for more info):

53798 - Hanterm can't find gulim fonts...
54767 - Can't handling family name for mincho and gothic
43743 - All translations are missing from eel-1.0-1.i386.rpm

6. RPMs required:

Red Hat Linux 7.2:

SRPMS:
ftp://updates.redhat.com/7.2/en/os/SRPMS/ttfonts-ko-1.0-11.src.rpm
ftp://updates.redhat.com/7.2/en/os/SRPMS/ttfonts-ja-1.0-7.src.rpm
ftp://updates.redhat.com/7.2/en/os/SRPMS/eel-1.0.2-2.src.rpm

i386:
ftp://updates.redhat.com/7.2/en/os/i386/eel-1.0.2-2.i386.rpm

noarch:
ftp://updates.redhat.com/7.2/en/os/noarch/ttfonts-ko-1.0-11.noarch.rpm
ftp://updates.redhat.com/7.2/en/os/noarch/ttfonts-ja-1.0-7.noarch.rpm



7. Verification:

MD5 sum                           Package Name
--------------------------------------------------------------------------
951f1967fe041fc9cd33b53c45496979 7.2/en/os/SRPMS/eel-1.0.2-2.src.rpm
61aa2e0d30824db8251782fad60669ba 7.2/en/os/SRPMS/ttfonts-ja-1.0-7.src.rpm
48c0f2918313f705e14748039f458349 7.2/en/os/SRPMS/ttfonts-ko-1.0-11.src.rpm
2229041da89faaf9857ba5e0be1ec6f2 7.2/en/os/i386/eel-1.0.2-2.i386.rpm
554229a000572f0f155c3e6a8981e7e0 7.2/en/os/noarch/ttfonts-ja-1.0-7.noarch.rpm
3486874922f2013553be33631d2827cd 7.2/en/os/noarch/ttfonts-ko-1.0-11.noarch.rpm

These packages are GPG signed by Red Hat, Inc. for security.  Our key
is available at:
    http://www.redhat.com/about/contact/pgpkey.html

You can verify each package with the following command:
    rpm --checksig  <filename>

If you only wish to verify that each package has not been corrupted or
tampered with, examine only the md5sum with the following command:
    rpm --checksig --nogpg <filename>

8. References:




Copyright(c) 2000, 2001 Red Hat, Inc.



_______________________________________________
Redhat-watch-list mailing list
To unsubscribe, visit: https://listman.redhat.com/mailman/listinfo/redhat-watch-list