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 103641 - Monospaced font render in Pango
Monospaced font render in Pango
Status: RESOLVED NOTGNOME
Product: pango
Classification: Platform
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Owen Taylor
Owen Taylor
Depends on:
Blocks:
 
 
Reported: 2003-01-16 07:55 UTC by Young-Ho Cha
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
screenshot (37.64 KB, image/png)
2003-01-16 07:55 UTC, Young-Ho Cha
Details
qt 3.1 is equal problem. pango is not bad. (23.86 KB, image/png)
2003-01-17 16:14 UTC, sangu
Details

Description Young-Ho Cha 2003-01-16 07:55:05 UTC
look at follow screenshot.

there are two font preview. one is fontilus(use Xft), and other is
gedit(use pango).

they use same font (GungsuhChe, fixed-width, 18 point).

In this font, Hangul glyph (and other CJK glyphs) had double width of
english glyph, on purpose.

fontilus render glyphs correctly. 

gedit render all glyphs with same width.

but this is not correct. because default glyph width in each other language
are different.
Comment 1 Young-Ho Cha 2003-01-16 07:55:54 UTC
Created attachment 13610 [details]
screenshot
Comment 2 Owen Taylor 2003-01-16 22:53:11 UTC
This is going to be a font specific problem of some sort,
probably in FreeType. Pango doesn't even know that fixed
width fonts exist.

You'll have to find someone with the same font to debug it.
Comment 3 kz 2003-01-17 14:56:54 UTC
gulim.ttc and batang.ttc are only sample that I know for monospaced ttf;
installed on MS Windows and used by default.
so I believe that ttc are not guilty.

and as ganadist said, pure Xft routine in fontilus is ok.
so Pango the higher layer is guilty, suspective.

btw, this issue is really important for gnome-terminal users;
vte does not support layered fontname of Xft: bug 100594
so gnome-termianl with vte has a little bit funny shape for font.
Comment 4 kz 2003-01-17 15:35:20 UTC
http://mail.nl.linux.org/linux-utf8/2002-06/msg00036.html is for this
matter, right?
Comment 5 Owen Taylor 2003-01-17 16:01:51 UTC
It may be that Xft (or FreeType) finds the width of characters
incorrectly but still draws correctly. Pango trusts Xft
for the character widths and treats every font the same
way.

I don't understand what you mean "layered font names". 
vte does not use Pango to draw text.
Comment 6 sangu 2003-01-17 16:14:06 UTC
Created attachment 13652 [details]
qt 3.1 is equal problem. pango is not bad.
Comment 7 Owen Taylor 2003-01-28 23:08:48 UTC
The screenshot looks like a different font, but I'm going to
resolve this NOTGNOME because I am pretty sure it's a 
Xft or FreeType bug, that's going to have to be debugged
by someone with access to the font.

Comment 8 kz 2003-02-25 02:46:18 UTC
http://www.mail-archive.com/fonts%40xfree86.org/msg01376.html
seems to have a patch. let's see the upcoming Xft! :)
Comment 9 Young-Ho Cha 2003-02-27 08:21:53 UTC
keith package fixed fontconfig. and resolve this problem.

thanx ;)
Comment 10 Young-Ho Cha 2003-02-27 08:23:39 UTC
sorry. I confused. 

sorry! keith packard but you have done great job!
Comment 11 Bugzilla Maintainers 2004-04-01 23:44:57 UTC
The URL field has been removed from bugzilla.gnome.org. This URL was in the old URL field, and is being added as a comment so that the data is not lost. Please email bugmaster@gnome.org if you have any questions.

URL: 
http://bugs.kde.org/show_bug.cgi?id=52538