Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 71618 - Japanese GDM has some font errors
Japanese GDM has some font errors
Product: Red Hat Public Beta
Classification: Retired
Component: pango (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Owen Taylor
Mike McLean
Depends On:
Blocks: 67217
  Show dependency treegraph
Reported: 2002-08-15 16:02 EDT by Jay Turner
Modified: 2015-01-07 18:59 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-08-21 19:21:29 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jay Turner 2002-08-15 16:02:17 EDT
Description of Problem:
If you run GDM with LANG=ja_JP.eucJP, then you will get a display which is
mostly correct, except for the characters in the lower-left corner, where the
language, session and system icons appear.  This is with gdm-

Version-Release number of selected component (if applicable):

How Reproducible:

Steps to Reproduce:

Actual Results:

Expected Results:

Additional Information:
Comment 1 Owen Taylor 2002-08-15 18:17:20 EDT
Think this is a Pango problem ... Pango doesn't do the right
fallbacks for the FT2 backend.
Comment 2 Havoc Pennington 2002-08-21 13:05:03 EDT
This should be fixed in redhat-artwork 0.38, I would expect it to be anyway.
Comment 3 Owen Taylor 2002-08-21 19:21:23 EDT
Actaully, I took this bug because there were pango issues with
the exact fonts that should be used, but that should be fixed
as of pango-1.1.1-1
Comment 4 Jay Turner 2002-08-28 09:48:33 EDT
OK, fix confirmed with redhat-artwork-0.39-1 and pango-1.1.1-1.  Someone please
reopen if there are still font issues, but the ones that were pointed out to me
by Owen and Adrian appeared fixed.

Note You need to log in before you can comment on or make changes to this bug.