|
From: | 黄建忠 |
Subject: | Re: A patch for enforcing double-width CJK character display |
Date: | Tue, 17 Apr 2012 16:51:49 +0800 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:10.0.2) Gecko/20120327 Thunderbird/10.0.2 |
于 2012年04月17日 15:02, Miles Bader 写道:
黄建忠<address@hidden> writes:Maybe your system have a buggy "Lucida Sans TypeWriter" font, you can try the lucida font released with JDK. Hope the problem can be fixed.No, I think my copy of L-S-T is fine here (you can see from the images I sent in my previous message). Now that I've seen both, it looks like the issue is that the version of "Sazanami minchou" in Debian includes hand-tuned bitmaps. These look much better in many cases, but because there's a limited number of them, and the font-rendering system prefers bitmaps, it chooses a slightly smaller size so it can use a bitmap.
Yes, I disabled embed-bitmap support in fontconfig, and only tested the OUTLINE glyphs of "Sazanami mincho". I also found problems with some old PCF/BDF Chinese fonts, for example, "Song" and "FangSong" shiped with Xorg. If I use such a font, the auto-matched Chinese pixelsize is even bigger than 2 * monospace width.:-(
By the way, some korean PCF fonts also had this problem.At first, I disable pcf/bdf support in this patch, If it is a pcf/bdf font, just keep it unchanged. but this is really not a good idea. for example, "SimSun.ttc"(the default font of Windowz XP CN version) is a very famous font for Chinese, almost everyone use it, it provides 9/10/11pt embedded bitmap "song". A lot of users even can not accept "ClearType" and "YaHei" in Vizta and Win 7. :-D
The result is as you can see, that the size of CJK characters is smaller than you might expect from the size specified. Maybe this is such a rare case that it can be ignored, I dunno, but it does appear that everything is functioning properly...
Yes, I agree, We should try best to keep everything work well. I consider to ignore PCF/BDF font again in this patch.
-miles
-- Huang JianZhong
[Prev in Thread] | Current Thread | [Next in Thread] |