After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 540467 - in ko_KR.UTF-8, monospace has Korean font glyph on gnome-terminal.
in ko_KR.UTF-8, monospace has Korean font glyph on gnome-terminal.
Status: RESOLVED NOTGNOME
Product: vte
Classification: Core
Component: general
0.16.x
Other All
: Normal normal
: ---
Assigned To: VTE Maintainers
VTE Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-06-27 11:28 UTC by sangu
Modified: 2012-10-10 13:04 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24

Attachments
en_US.UTF-8 vs ko_KR.UTF-8 (154.55 KB, image/png)
2012-10-10 05:32 UTC, sangu 		Details

Description sangu 2008-06-27 11:28:39 UTC 
Please describe the problem:
$ LANG=en_US.UTF-8 fc-match monospace
DejaVuLGCSansMono.ttf: "DejaVu LGC Sans Mono" "Book"
$ LANG=ko_KR.UTF-8 fc-match monospace
malgun.ttf: "Malgun Gothic" "Regular" <- Korean default font.

Select monospace on gnome-terminal Profile Preference-> monospace has Korean font glyph on gnome-terminal.

Steps to reproduce:
1.  Select monospace on gnome-terminal.
2. 
3. 


Actual results:


Expected results:


Does this happen every time?
yes, always.

Other information:
See Also : https://bugzilla.redhat.com/show_bug.cgi?id=428389

fontconfig-2.6.0-2.fc10.i386
libXft-2.1.12-5.fc9.i386
vte-0.16.14-1.fc10.i386
gnome-terminal-2.23.4.2-1.fc10.i386
Comment 1 Behdad Esfahbod 2008-06-27 13:27:47 UTC 
Can you confirm that running with VTE_BACKEND=pango "fixes" it?
Comment 2 sangu 2008-06-27 16:14:06 UTC 
(In reply to comment #1)
> Can you confirm that running with VTE_BACKEND=pango "fixes" it?
> 

No. Running  with VTE_BACKEND=pango has the same problem. Scroll is only big slow.
Comment 3 Christian Persch 2009-01-20 19:04:48 UTC 
Is this still reproducible using vte 0.19.4 ?
Comment 4 Akira TAGOH 2010-11-19 08:40:01 UTC 
I can reproduce this with vte 0.26.1. I'm not sure if VTE_BACKEND is still effective, but I don't see any difference in the behaviour. though I type ASCII characters in gedit, it's rendering with the different fonts for "@" and "@a" say, no changes in vte with even VTE_BACKEND=pango for example.
Comment 5 sangu 2012-10-10 05:32:46 UTC 
Created attachment 226153 [details]
en_US.UTF-8 vs ko_KR.UTF-8

$ date --help in $ LANG=en_US.UTF-8 vte2_90
$ date --help in $ LANG=ko_KR.UTF-8 vte2_90

This bug still happens in vte3-0.34.0.
Comment 6 Christian Persch 2012-10-10 09:14:39 UTC 
Please add an explanation for why you resolved it NOTGNOME?
Comment 7 sangu 2012-10-10 13:04:30 UTC 
(In reply to comment #6)
> Please add an explanation for why you resolved it NOTGNOME?

 After updating to fixed font package ( wrong family name in fontconfig config, See Also https://bugzilla.redhat.com/show_bug.cgi?id=864778 ), this issue was fixed.