|
Problem of Xft2: msg#00017xfree86.fonts
From: Mike FABIAN <mfabian@xxxxxxx> Subject: [Fonts] Re: After-XTT's extension of the encoding field. Date: Thu, 07 Aug 2003 18:55:26 +0200 > I agree that the old X fonts are broken beyond repair and we should > move on to use fontconfig/Xft as much as possible. The Xft2 seems to have a very important problem in CJK environment. As you know, people in CJK use "FontSet" or "FontList" when using XLFD. However, the Xft2 does not have such a mechanism. Therefore, a toolkit using Xft2 must have it. In fact, Qt has a mechanism of "Font Substitutions". We can set it easily by "qtconfig". This mechanism is excellent. So I always use Konqueror as my browser. But Gtk2 has not complete font-substitution mechanism. Therefore, Gtk2 is insufficient in CJK environment. So I *NEVER* use Gtk2-mozilla. It has no flexibility of a font setting. The right and wrong of a toolkit become clear when using Xft2. For me, Qt is the only choice when using Xft2. So I do not feel charm for Xft2 now. If the Xft2 itself has "Font Substitutions", I may like it. ------------------------------------------------------------ Chisato Yamauchi |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: After-XTT's extension of the encoding field.: 00017, Mike FABIAN |
|---|---|
| Next by Date: | Re: Problem of Xft2: 00017, Pablo Saratxaga |
| Previous by Thread: | Re: Re: After-XTT's extension of the encoding field.i: 00017, Jungshik Shin |
| Next by Thread: | Re: Problem of Xft2: 00017, Pablo Saratxaga |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |