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 80120 - gnome-terminal not displaying Japanese characters at all
gnome-terminal not displaying Japanese characters at all
Product: Red Hat Raw Hide
Classification: Retired
Component: vte (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Nalin Dahyabhai
Depends On:
Blocks: 79578
  Show dependency treegraph
Reported: 2002-12-20 02:59 EST by Jens Petersen
Modified: 2008-05-01 11:38 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-01-20 21:21:29 EST
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 Jens Petersen 2002-12-20 02:59:31 EST
Description of problem:
The current gnome-terminal is displaying Japanese characters at all
in a Japanese locale.  Whitespace appears instead.

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

How reproducible:
Every time.

Steps to Reproduce:
Start a new gnome-terminal session in ja locale
  % killall -9 gnome-terminal
  % LANG=ja_JP gnome-terminal
  % date
Actual results:
2002   12   20          16:55:13 JST

Expected results:
2002<nen> 12<gatu> 20<nichi> <kinyoubi> 16:55:13 JST
where the words in <>'s represent kanji

Additional info:
Has been working until quite recently.
Korean and Chinese seem to be ok.
Comment 1 Havoc Pennington 2002-12-20 09:49:49 EST
Please, file all terminal emulation/behavior bugs against vte, 
gnome-terminal is just the menus and dialogs and command line options.
Comment 2 Akira TAGOH 2002-12-24 02:28:56 EST
It works for me. I've installed it with freshly Everything install from
Comment 3 Leon Ho 2002-12-26 21:24:34 EST
A bit strange. I got a desktop install and it couldn't display. FC_DEBUG=1 
shows that it uses Luxi Mono. Actually look like fontconfig font matching has 
changed. Has the latest update changes anything on that?
Comment 4 Jens Petersen 2003-01-20 21:21:29 EST
I think this was actually due to fontconfig problems that
got fixed in Phoebe beta2.

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