hi Bahdad<br><br><br><div class="gmail_quote">On Nov 30, 2007 3:04 PM, Behdad Esfahbod <<a href="mailto:behdad@behdad.org">behdad@behdad.org</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>---------- Forwarded message ----------<br>From: Behdad Esfahbod <<a href="mailto:besfahbo@redhat.com">besfahbo@redhat.com</a>><br>To: Qianqian Fang <<a href="mailto:fangqq@gmail.com">fangqq@gmail.com</a>>
<br>Date: Fri, 30 Nov 2007 12:40:04 -0500<br>Subject: Re: Request for review and advice on wqy-bitmap-fonts fontconfig settings<br>On Thu, 2007-11-29 at 19:08 -0500, Qianqian Fang wrote:<br>><br>> For zh locales, in addition to the above problem, under monospace
<br>> (gnome-terminal),<br>> the Latin glyphs were rendered by the wqy bitmap glyphs. I expect<br>> those are rendered by Dejavu Sans Mono or Bitstream Sans Mono.<br><br>That's because gnome-terminal, unlike Pango, doesn't refine language
<br>tags passed to fontconfig based on the input text. That is, it always<br>asks fontconfig for fonts to render Chinese, even if the text is Latin.<br>Can be fixed in g-t for sure, but not a high prio. It's impossible to
<br>fix this with a fontconfig config. That's what you pay when you put<br>multiple scripts in a single font.</blockquote><div> </div><div>In 0.9.9-1, the following fontconfig config does work for gnome-terminal <br>
(for both zh or non-zh locales), could you give some explanations? <br><pre> <match target="pattern"><br> <test equal="any" compare="eq" name="family"><br> <string>WenQuanYi Bitmap Song</string>
<br> </test><br> <test equal="any" compare="eq" name="family"><br> <string>monospace</string><br> </test><br> <edit name="family" mode="prepend">
<br> <string>Bitstream Vera Sans Mono</string><br> </edit><br> <edit name="family" mode="prepend" binding="strong"><br> <string>DejaVu LGC Sans Mono</string>
<br> </edit><br> </match></pre><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>> in either case, the output of
<br>> FC_DEBUG=4 fc-match "monospace:lang=zh-cn:pixelsize=10px"<br>> always put wqy as the first one, this is not consistent with what<br>> Firefox actually displayed under en locales.<br><br>What do you mean "always"? It's just one query. Of course it prefers
<br>wqy: you are asking for a Chinese font and your config files make it<br>prefer wqy for Chinese.<br></blockquote><div><br>I found a problem in my original file, I meant to put DejaVu in front<br>of WQY bitmap Song in the "monospace" block. However, even after fixing
<br>this, wqy-bitmap song is still listed as the first one in my fc-match output (for<br>all sizes under zh-cn locale). Doesn't the first one in the <prefer> list<br>get higher priority to be used?<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>> Can any of you help me to find out how to get around these problems?<br><br><br>Got a question for you: You said wqy is a fork of bitmaps from a<br>TrueType font. Why not just contribute the bitmaps back to the original
<br>font?<br></blockquote><div><br>this bitmap fonts starts from Firefly bitmap font, which is licensed under GPL. <br><a href="http://www.study-area.org/apt/firefly-font/Changelog">http://www.study-area.org/apt/firefly-font/Changelog
</a><br>Firefly font was integrated into Uming with some verbal permission from Firefly.<br>Uming is licensed under Arphic Public License (APL), which is not compatible with<br>GPL. This font was significantly expanded and improved by wqy's contributors,
<br>and our Copyright committee decided to stay with GPL. Therefore, merging to <br>Uming is not permitted by license. We also developed our own vector fonts, <br>one of the first release is wqy-zenhei-fonts (currently in Fedora). Zenhei
<br>embedded the bitmap glyphs for about 20400 characters out of 27842 characters <br>in wqy-bitmap-fonts (those missing are due to the lack of outline data).<br>Comparing to uming, it only has ~16000 char containing bitmap glyphs.
<br></div></div><br>I did not find in your reply: do you have any thought on why the <br>last two match blocks (replacing wqy bitmap font by Uming for large/small sizes) <br>does not work?<br><br>thanks<br><br>Qianqian<br>
<br>