Sync FAQ docs re: FontCache slowness
This commit is contained in:
parent
2196d6dc72
commit
82ad88bad4
15 changed files with 295 additions and 15 deletions
|
|
@ -96,7 +96,7 @@
|
|||
</p>
|
||||
|
||||
<p>
|
||||
14 maj 2024 </p>
|
||||
4 qershor 2024 </p>
|
||||
</center>
|
||||
|
||||
<table border="2"
|
||||
|
|
@ -678,6 +678,23 @@
|
|||
To disable the lockfile, add the "<code>--nolockfile</code>" argument to Tux Paint's command-line, or "<code>nolockfile=yes</code>" to the configuration file. </p>
|
||||
</dd>
|
||||
|
||||
<dt>
|
||||
Tux Paint launches very slowly </dt>
|
||||
|
||||
<dd>
|
||||
<p>
|
||||
The first time Tux Paint is launched (for a particular user), it may take a minute or more to respond. The font system used by Tux Paint (FontConfig, via Pango) is creating a 'cache' of information about the fonts on your system. Subsequent launches of Tux Paint should be fast. </p>
|
||||
|
||||
<p>
|
||||
While the font cache is generated behind the scenes, Tux Paint should remain interactive (showing an animated 'please wait' animation) as this process runs. </p>
|
||||
|
||||
<p>
|
||||
If this delay persists or reoccurs, it could be that the cache is being deleted — for example, in an environment (such as a school computer lab) where a system is returned into a default state when a user finishes using the program. Some versions of Tux Paint ship with a file, <nobr>"<code style='background: #EEE;'>fonts.conf</code>"</nobr> (<a href="https://fontconfig.pages.freedesktop.org/fontconfig/fontconfig-user.html">documented at freedesktop.org</a>), which can be modified to have FontConfig store the file elsewhere, e.g.: <blockquote>
|
||||
<code><cachedir>C:\Documents and Settings\All Users\Application Data\fontconfig\cache</cachedir></code>
|
||||
</blockquote>
|
||||
</p>
|
||||
</dd>
|
||||
|
||||
<dt>
|
||||
S’mbyll dot Tux Paint-in </dt>
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue