|
From: | Kazunobu Kuriyama |
Subject: | Re: Text drawing bug - gaps after 16th character in scaled view |
Date: | Wed, 02 Jul 2003 08:20:46 +0900 |
User-agent: | Mozilla/5.0 (X11; U; Linux i686; ja-JP; rv:1.0.0) Gecko/20020614 |
Fred Kiefer wrote:
It seems that I should had put the following sentence before the second paragraph:Kazunobu Kuriyama wrote:In short, the art backend works fine. At first I forgot to set GSFontAntiAlias to YES and, naturally, got the same result as that of the xlib backend. After setting the environmental variable correctly, the trouble has disappeared! One thing to note: Depending on the value of GSFontAntiAlias, I saw different kind of fonts. So I'm not sure if I conclude the cause of the bug really lies in the xlib backend. I'll test other programs to see what happens, and if I find something, I'll send you a supplement to this note.Are you sure that you are using the Art backend? GSFontAntiAlias is used there as well, but should be YES by default, as opposed to the xlib backend where we have a default of NO. The difference in the available fonts suggest that you are still using xlib as there the fonts either come from the font_cache or from font_config, which gives different results. The art backend still has a lot of extra features, which may make it a worthwhile replacemetn for xlib, so you may give it another try.Fred
"I had set GSFontAntiAlias to NO before trying the Art backend." Hopefully, this makes sense.I understand the Art backend is a "worthwhile replacement" for the xlib one and hence began studying it. Why? Because I have to get some .nfonts for Asian characters somewhere or to make ones by myself somehow, though I have no idea on it yet. That's the biggest obstacle I'm
now faced with in the transition from the xlib backend to the art one.Having said so, I'd like you to be reminded of the fact that the bug in the xlib backend still
remains unfixed. - KK
[Prev in Thread] | Current Thread | [Next in Thread] |