Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: X taking _long_ time to render fonts
- To: tlug@example.com
- Subject: Re: X taking _long_ time to render fonts
- From: Mike Fabian <mfabian@example.com>
- Date: 13 Aug 2001 22:39:18 +0200
- Content-Type: text/plain; charset=iso-2022-jp
- Delivered-To: tlug@example.com
- In-Reply-To: Tobias Diedrich's message of "Fri, 3 Aug 2001 01:32:52 +0200"
- List-Help: <mailto:tlug-request@example.comsubject=help>
- List-Post: <mailto:tlug@example.com>
- List-Subscribe: <mailto:tlug-request@example.comsubject=subscribe>
- List-Unsubscribe: <mailto:tlug-request@example.comsubject=unsubscribe>
- Old-Return-Path: <mfabian@example.com>
- References: <Pine.LNX.4.21.0108021652190.17077-100000@example.com><20010803013252.B1469@example.com>
- Reply-To: mfabian@example.com
- Resent-From: tlug@example.com
- Resent-Message-ID: <tERukC.A.XmH.irDe7@example.com>
- Resent-Sender: tlug-request@example.com
- Sender: mfabian@example.com
- User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Artificial Intelligence)
Tobias Diedrich <ranma@example.com> writes: > Marc Christensen wrote: > > [slow freetype] > > Sadly, that is normal behaviour. The font server has to tell something > about the font's properties and will render all characters to gather that > information (IIRC it was average width or something like that). Only for proportional fonts, for example: -bitstream-bitstream cyberbit-medium-r-normal--0-0-0-0-p-0-iso10646-1 For charcell fonts, i.e. fonts which have a "-c-" instead a "-m-" like -bitstream-bitstream cyberbit-medium-r-normal--0-0-0-0-c-0-jisx0208.1983-0 it is fast, because it is not necessary to render all characters if the metrics is the same for all of them. If you change the "-p-" in the first example into "-c-" in fonts.scale (and rerun mkfontdir), the font will open fast, but the spacing for the latin part will be completely fucked up. > I don't know if someone is working on that problem though. > Maybe some kind of caching would be a good idea ? There is some caching. Only the first application opening the font will start slow, subsequent applications share the font. I.e. ~$ xfd -fn "-bitstream-bitstream cyberbit-medium-r-normal--0-0-0-0-p-0-iso10646-1"& will be slow, but if you don't close the window and start another "xfd" process, the second one will be fast. If you close all applications using this font, the first application opening it again will start slow again. > I would imagine that not being too difficult, but instead I guess most > people don't notice the problem because they use only fonts with not > that much characters in it, so the server will not block that long. Using the font server "xfs" helps a little bit. With the font server, only the application requesting the font waits. Without the font server, the whole X11 session freezes until the font is opened. > For something related I don't understand why Anti-aliasing won't work > with big (asian) Truetype fonts (or did they fix that, did not try that > lately ?). It does work. And it doesn't have the above mentioned performance problem for large fonts. -- Mike Fabian <mfabian@example.com> http://www.suse.de/~mfabian 睡眠不足はいい仕事の敵だ。
- References:
- X taking _long_ time to render fonts
- From: Marc Christensen <marc@example.com>
- Re: X taking _long_ time to render fonts
- From: Tobias Diedrich <ranma@example.com>
Home | Main Index | Thread Index
- Prev by Date: Re: kinput2 Auxiliary Control
- Next by Date: RE: [reminder] 8/17 TLUG Nomikai
- Prev by thread: Re: X taking _long_ time to render fonts
- Next by thread: Boot Floppy on Sparc
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links