freetype-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ftview segfault on ArefRuqaaInk-Regular.ttf (one of google web fonts


From: Werner LEMBERG
Subject: Re: ftview segfault on ArefRuqaaInk-Regular.ttf (one of google web fonts)
Date: Mon, 15 May 2023 03:53:50 +0000 (UTC)

>> Hmm.  Then `ftview`'s default cache size should probably be
>> increased to cover both the number of characters/glyphs in Arabic
>> and Indic scripts, including (most of) the necessary ligatures.  If
>> I call `ftview ArefRuqaaInk-Regular.ttf`, a bit more than 200
>> glyphs are shown; IMHO this *must* fit into the cache.
>>
>> Am I missing something?
> 
> The default cache size is 200,000.  Just to cover a small screen of
> 640x480 with gray glyphs, we might need 300,000.  If we go LCD or
> BGRA on a larger screen... Uh-oh. basically we have never had enough
> cache for ftview, even if it works.
> 
> Anyway, until recently I was happy to create some rendering load in
> ftview for profiling and FTC was never showing up.

So how shall we proceed?  What can we do to make `ftview` respond with
less delay if pressing the Fx keys?


    Werner



reply via email to

[Prev in Thread] Current Thread [Next in Thread]