Sync EXTENDING re: FontConfig

This commit is contained in:
Bill Kendrick 2025-06-08 11:02:09 -07:00
parent f33cb19c7f
commit 7f01203ffa
9 changed files with 489 additions and 26 deletions

View file

@ -620,7 +620,7 @@ option is set). The locations vary, depending on operating system.
+ B_USER_FONTS_DIRECTORY
+ B_USER_NONPACKAGED_FONTS_DIRECTORY
* Linux
* Linux/etc.
+ /usr/share/feh/fonts
+ /usr/share/fonts
+ /usr/X11R6/lib/X11/fonts
@ -633,7 +633,46 @@ option is set). The locations vary, depending on operating system.
### FontConfig ###
...
Tux Paint utilizes FontConfig to find additional system-wide and user-specific
fonts that the 'Text' and 'Label' tools might be able to use (unless the
"--nosysfonts" option is set). It does this by looking for FontConfig
configuration files ("fonts.conf") in various locations.
* Windows
+ The "etc/fonts/fonts.conf" file included with Tux Paint.
* macOS
+ The path specified by the "FONTCONFIG_PATH" environment variable, if
set.
* Haiku
+ /boot/system/settings/fonts/fonts.conf
* Linux/etc.
+ The path specified by the "FONTCONFIG_PATH" environment variable, if
set.
+ If the above fails, then "/etc/fonts/fonts.conf".
+ The path specified by the "XDG_CONFIG_HOME" environment variable, if
set. There, it looks for the file "fontconfig/fonts.conf".
+ If the above fails, then "$HOME/.config/fontconfig/fonts.conf".
Each FontConfig configuration file ("fonts.conf") is examined for "<dir>" tags
that specify directory (folder) paths where fonts might be found, and Tux Paint
scans them and loads the fonts. If a "prefix" attribute is included in the tag,
Tux Paint prefixes the path accordingly.
→ xdg ←
The directory path specified is considered to be relative to the user's
local data path, specified by the "XDG_DATA_HOME" environment variable. If
not set, then ".local/share" under the path specified by the "HOME"
environment variable will be used, if it exists.
→ relative ←
The directory path specified is considered to be relative to the
configuration file itself.
→ default, cwd, or no "prefix" attribute specified ←
The directory path specified is considered to be relative to the current
working directory (where Tux Paint is running), unless a root path is
included at the start (e.g., "/", "C:\\", etc.)
'Starters'

View file

@ -710,7 +710,7 @@
<li>
The location specified by the "<code>Fonts</code>" option of the "<code>Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders</code>" Windows Registry key. </li>
<li>
If the above fails, then "C:\WINDOWS\FONTS". </li>
If the above fails, then "<code>C:\WINDOWS\FONTS</code>". </li>
<li>
The location specified by the "<code>Local AppData</code>" option of the "<code>Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders</code>" Windows Registry key. The path "<code>\Microsoft\Windows\Fonts</code>" is appended to that location. </li>
</ul>
@ -743,7 +743,7 @@
</p>
</li>
<li>
<strong>Linux</strong>
<strong>Linux/etc.</strong>
<ul>
<li><code>/usr/share/feh/fonts</code></li>
<li><code>/usr/share/fonts</code></li>
@ -768,7 +768,60 @@
</h2>
</header>
<p>...</p>
<p>
Tux Paint utilizes <cite>FontConfig</cite> to find additional system-wide and user-specific fonts that the 'Text' and 'Label' tools might be able to use (unless the "<code>--nosysfonts</code>" option is set). It does this by looking for <cite>FontConfig</cite> configuration files ("<code>fonts.conf</code>") in various locations. </p>
<ul>
<li>
<strong>Windows</strong>
<ul>
<li>
The "<code>etc/fonts/fonts.conf</code>" file included with Tux Paint. </li>
</ul>
</li>
<li>
<strong>macOS</strong>
<ul>
<li>
The path specified by the "<code>FONTCONFIG_PATH</code>" environment variable, if set. </li>
</ul>
</li>
<li>
<strong>Haiku</strong>
<ul>
<li><code>/boot/system/settings/fonts/fonts.conf</code></li>
</ul>
</li>
<li>
<strong>Linux/etc.</strong>
<ul>
<li>
The path specified by the "<code>FONTCONFIG_PATH</code>" environment variable, if set. </li>
<li>
If the above fails, then "<code>/etc/fonts/fonts.conf</code>". </li>
<li>
The path specified by the "<code>XDG_CONFIG_HOME</code>" environment variable, if set. There, it looks for the file "<code>fontconfig/fonts.conf</code>". </li>
<li>
If the above fails, then "<code>$HOME/.config/fontconfig/fonts.conf</code>". </li>
</ul>
</li>
</ul>
<p>
Each FontConfig configuration file ("<code>fonts.conf</code>") is examined for "<code>&lt;dir&gt;</code>" tags that specify directory (folder) paths where fonts might be found, and Tux Paint scans them and loads the fonts. If a "<code>prefix</code>" attribute is included in the tag, Tux Paint prefixes the path accordingly. <dl>
<dt><code>xdg</code></dt>
<dd>
The directory path specified is considered to be relative to the user's local data path, specified by the "<code>XDG_DATA_HOME</code>" environment variable. If not set, then "<code>.local/share</code>" under the path specified by the "<code>HOME</code>" environment variable will be used, if it exists. </dd>
<dt><code>relative</code></dt>
<dd>
The directory path specified is considered to be relative to the configuration file itself. </dd>
<dt>
<code>default</code>, <code>cwd</code>, or no "<code>prefix</code>" attribute specified </dt>
<dd>
The directory path specified is considered to be relative to the current working directory (where Tux Paint is running), unless a root path is included at the start (e.g., "/", "C:\\", etc.) </dd>
</ul>
</p>
</section><!-- H2: FontConfig -->
</section><!-- H1: Fonts -->

View file

@ -710,7 +710,7 @@
<li>
The location specified by the "<code>Fonts</code>" option of the "<code>Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders</code>" Windows Registry key. </li>
<li>
If the above fails, then "C:\WINDOWS\FONTS". </li>
If the above fails, then "<code>C:\WINDOWS\FONTS</code>". </li>
<li>
The location specified by the "<code>Local AppData</code>" option of the "<code>Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders</code>" Windows Registry key. The path "<code>\Microsoft\Windows\Fonts</code>" is appended to that location. </li>
</ul>
@ -743,7 +743,7 @@
</p>
</li>
<li>
<strong>Linux</strong>
<strong>Linux/etc.</strong>
<ul>
<li><code>/usr/share/feh/fonts</code></li>
<li><code>/usr/share/fonts</code></li>
@ -768,7 +768,60 @@
</h2>
</header>
<p>...</p>
<p>
Tux Paint utilizes <cite>FontConfig</cite> to find additional system-wide and user-specific fonts that the 'Text' and 'Label' tools might be able to use (unless the "<code>--nosysfonts</code>" option is set). It does this by looking for <cite>FontConfig</cite> configuration files ("<code>fonts.conf</code>") in various locations. </p>
<ul>
<li>
<strong>Windows</strong>
<ul>
<li>
The "<code>etc/fonts/fonts.conf</code>" file included with Tux Paint. </li>
</ul>
</li>
<li>
<strong>macOS</strong>
<ul>
<li>
The path specified by the "<code>FONTCONFIG_PATH</code>" environment variable, if set. </li>
</ul>
</li>
<li>
<strong>Haiku</strong>
<ul>
<li><code>/boot/system/settings/fonts/fonts.conf</code></li>
</ul>
</li>
<li>
<strong>Linux/etc.</strong>
<ul>
<li>
The path specified by the "<code>FONTCONFIG_PATH</code>" environment variable, if set. </li>
<li>
If the above fails, then "<code>/etc/fonts/fonts.conf</code>". </li>
<li>
The path specified by the "<code>XDG_CONFIG_HOME</code>" environment variable, if set. There, it looks for the file "<code>fontconfig/fonts.conf</code>". </li>
<li>
If the above fails, then "<code>$HOME/.config/fontconfig/fonts.conf</code>". </li>
</ul>
</li>
</ul>
<p>
Each FontConfig configuration file ("<code>fonts.conf</code>") is examined for "<code>&lt;dir&gt;</code>" tags that specify directory (folder) paths where fonts might be found, and Tux Paint scans them and loads the fonts. If a "<code>prefix</code>" attribute is included in the tag, Tux Paint prefixes the path accordingly. <dl>
<dt><code>xdg</code></dt>
<dd>
The directory path specified is considered to be relative to the user's local data path, specified by the "<code>XDG_DATA_HOME</code>" environment variable. If not set, then "<code>.local/share</code>" under the path specified by the "<code>HOME</code>" environment variable will be used, if it exists. </dd>
<dt><code>relative</code></dt>
<dd>
The directory path specified is considered to be relative to the configuration file itself. </dd>
<dt>
<code>default</code>, <code>cwd</code>, or no "<code>prefix</code>" attribute specified </dt>
<dd>
The directory path specified is considered to be relative to the current working directory (where Tux Paint is running), unless a root path is included at the start (e.g., "/", "C:\\", etc.) </dd>
</ul>
</p>
</section><!-- H2: FontConfig -->
</section><!-- H1: Fonts -->

View file

@ -710,7 +710,7 @@
<li>
The location specified by the "<code>Fonts</code>" option of the "<code>Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders</code>" Windows Registry key. </li>
<li>
If the above fails, then "C:\WINDOWS\FONTS". </li>
If the above fails, then "<code>C:\WINDOWS\FONTS</code>". </li>
<li>
The location specified by the "<code>Local AppData</code>" option of the "<code>Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders</code>" Windows Registry key. The path "<code>\Microsoft\Windows\Fonts</code>" is appended to that location. </li>
</ul>
@ -743,7 +743,7 @@
</p>
</li>
<li>
<strong>Linux</strong>
<strong>Linux/etc.</strong>
<ul>
<li><code>/usr/share/feh/fonts</code></li>
<li><code>/usr/share/fonts</code></li>
@ -768,7 +768,60 @@
</h2>
</header>
<p>...</p>
<p>
Tux Paint utilizes <cite>FontConfig</cite> to find additional system-wide and user-specific fonts that the 'Text' and 'Label' tools might be able to use (unless the "<code>--nosysfonts</code>" option is set). It does this by looking for <cite>FontConfig</cite> configuration files ("<code>fonts.conf</code>") in various locations. </p>
<ul>
<li>
<strong>Windows</strong>
<ul>
<li>
The "<code>etc/fonts/fonts.conf</code>" file included with Tux Paint. </li>
</ul>
</li>
<li>
<strong>macOS</strong>
<ul>
<li>
The path specified by the "<code>FONTCONFIG_PATH</code>" environment variable, if set. </li>
</ul>
</li>
<li>
<strong>Haiku</strong>
<ul>
<li><code>/boot/system/settings/fonts/fonts.conf</code></li>
</ul>
</li>
<li>
<strong>Linux/etc.</strong>
<ul>
<li>
The path specified by the "<code>FONTCONFIG_PATH</code>" environment variable, if set. </li>
<li>
If the above fails, then "<code>/etc/fonts/fonts.conf</code>". </li>
<li>
The path specified by the "<code>XDG_CONFIG_HOME</code>" environment variable, if set. There, it looks for the file "<code>fontconfig/fonts.conf</code>". </li>
<li>
If the above fails, then "<code>$HOME/.config/fontconfig/fonts.conf</code>". </li>
</ul>
</li>
</ul>
<p>
Each FontConfig configuration file ("<code>fonts.conf</code>") is examined for "<code>&lt;dir&gt;</code>" tags that specify directory (folder) paths where fonts might be found, and Tux Paint scans them and loads the fonts. If a "<code>prefix</code>" attribute is included in the tag, Tux Paint prefixes the path accordingly. <dl>
<dt><code>xdg</code></dt>
<dd>
The directory path specified is considered to be relative to the user's local data path, specified by the "<code>XDG_DATA_HOME</code>" environment variable. If not set, then "<code>.local/share</code>" under the path specified by the "<code>HOME</code>" environment variable will be used, if it exists. </dd>
<dt><code>relative</code></dt>
<dd>
The directory path specified is considered to be relative to the configuration file itself. </dd>
<dt>
<code>default</code>, <code>cwd</code>, or no "<code>prefix</code>" attribute specified </dt>
<dd>
The directory path specified is considered to be relative to the current working directory (where Tux Paint is running), unless a root path is included at the start (e.g., "/", "C:\\", etc.) </dd>
</ul>
</p>
</section><!-- H2: FontConfig -->
</section><!-- H1: Fonts -->

View file

@ -710,7 +710,7 @@
<li>
The location specified by the "<code>Fonts</code>" option of the "<code>Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders</code>" Windows Registry key. </li>
<li>
If the above fails, then "C:\WINDOWS\FONTS". </li>
If the above fails, then "<code>C:\WINDOWS\FONTS</code>". </li>
<li>
The location specified by the "<code>Local AppData</code>" option of the "<code>Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders</code>" Windows Registry key. The path "<code>\Microsoft\Windows\Fonts</code>" is appended to that location. </li>
</ul>
@ -743,7 +743,7 @@
</p>
</li>
<li>
<strong>Linux</strong>
<strong>Linux/etc.</strong>
<ul>
<li><code>/usr/share/feh/fonts</code></li>
<li><code>/usr/share/fonts</code></li>
@ -768,7 +768,60 @@
</h2>
</header>
<p>...</p>
<p>
Tux Paint utilizes <cite>FontConfig</cite> to find additional system-wide and user-specific fonts that the 'Text' and 'Label' tools might be able to use (unless the "<code>--nosysfonts</code>" option is set). It does this by looking for <cite>FontConfig</cite> configuration files ("<code>fonts.conf</code>") in various locations. </p>
<ul>
<li>
<strong>Windows</strong>
<ul>
<li>
The "<code>etc/fonts/fonts.conf</code>" file included with Tux Paint. </li>
</ul>
</li>
<li>
<strong>macOS</strong>
<ul>
<li>
The path specified by the "<code>FONTCONFIG_PATH</code>" environment variable, if set. </li>
</ul>
</li>
<li>
<strong>Haiku</strong>
<ul>
<li><code>/boot/system/settings/fonts/fonts.conf</code></li>
</ul>
</li>
<li>
<strong>Linux/etc.</strong>
<ul>
<li>
The path specified by the "<code>FONTCONFIG_PATH</code>" environment variable, if set. </li>
<li>
If the above fails, then "<code>/etc/fonts/fonts.conf</code>". </li>
<li>
The path specified by the "<code>XDG_CONFIG_HOME</code>" environment variable, if set. There, it looks for the file "<code>fontconfig/fonts.conf</code>". </li>
<li>
If the above fails, then "<code>$HOME/.config/fontconfig/fonts.conf</code>". </li>
</ul>
</li>
</ul>
<p>
Each FontConfig configuration file ("<code>fonts.conf</code>") is examined for "<code>&lt;dir&gt;</code>" tags that specify directory (folder) paths where fonts might be found, and Tux Paint scans them and loads the fonts. If a "<code>prefix</code>" attribute is included in the tag, Tux Paint prefixes the path accordingly. <dl>
<dt><code>xdg</code></dt>
<dd>
The directory path specified is considered to be relative to the user's local data path, specified by the "<code>XDG_DATA_HOME</code>" environment variable. If not set, then "<code>.local/share</code>" under the path specified by the "<code>HOME</code>" environment variable will be used, if it exists. </dd>
<dt><code>relative</code></dt>
<dd>
The directory path specified is considered to be relative to the configuration file itself. </dd>
<dt>
<code>default</code>, <code>cwd</code>, or no "<code>prefix</code>" attribute specified </dt>
<dd>
The directory path specified is considered to be relative to the current working directory (where Tux Paint is running), unless a root path is included at the start (e.g., "/", "C:\\", etc.) </dd>
</ul>
</p>
</section><!-- H2: FontConfig -->
</section><!-- H1: Fonts -->

View file

@ -710,7 +710,7 @@
<li>
The location specified by the "<code>Fonts</code>" option of the "<code>Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders</code>" Windows Registry key. </li>
<li>
If the above fails, then "C:\WINDOWS\FONTS". </li>
If the above fails, then "<code>C:\WINDOWS\FONTS</code>". </li>
<li>
The location specified by the "<code>Local AppData</code>" option of the "<code>Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders</code>" Windows Registry key. The path "<code>\Microsoft\Windows\Fonts</code>" is appended to that location. </li>
</ul>
@ -743,7 +743,7 @@
</p>
</li>
<li>
<strong>Linux</strong>
<strong>Linux/etc.</strong>
<ul>
<li><code>/usr/share/feh/fonts</code></li>
<li><code>/usr/share/fonts</code></li>
@ -768,7 +768,60 @@
</h2>
</header>
<p>...</p>
<p>
Tux Paint utilizes <cite>FontConfig</cite> to find additional system-wide and user-specific fonts that the 'Text' and 'Label' tools might be able to use (unless the "<code>--nosysfonts</code>" option is set). It does this by looking for <cite>FontConfig</cite> configuration files ("<code>fonts.conf</code>") in various locations. </p>
<ul>
<li>
<strong>Windows</strong>
<ul>
<li>
The "<code>etc/fonts/fonts.conf</code>" file included with Tux Paint. </li>
</ul>
</li>
<li>
<strong>macOS</strong>
<ul>
<li>
The path specified by the "<code>FONTCONFIG_PATH</code>" environment variable, if set. </li>
</ul>
</li>
<li>
<strong>Haiku</strong>
<ul>
<li><code>/boot/system/settings/fonts/fonts.conf</code></li>
</ul>
</li>
<li>
<strong>Linux/etc.</strong>
<ul>
<li>
The path specified by the "<code>FONTCONFIG_PATH</code>" environment variable, if set. </li>
<li>
If the above fails, then "<code>/etc/fonts/fonts.conf</code>". </li>
<li>
The path specified by the "<code>XDG_CONFIG_HOME</code>" environment variable, if set. There, it looks for the file "<code>fontconfig/fonts.conf</code>". </li>
<li>
If the above fails, then "<code>$HOME/.config/fontconfig/fonts.conf</code>". </li>
</ul>
</li>
</ul>
<p>
Each FontConfig configuration file ("<code>fonts.conf</code>") is examined for "<code>&lt;dir&gt;</code>" tags that specify directory (folder) paths where fonts might be found, and Tux Paint scans them and loads the fonts. If a "<code>prefix</code>" attribute is included in the tag, Tux Paint prefixes the path accordingly. <dl>
<dt><code>xdg</code></dt>
<dd>
The directory path specified is considered to be relative to the user's local data path, specified by the "<code>XDG_DATA_HOME</code>" environment variable. If not set, then "<code>.local/share</code>" under the path specified by the "<code>HOME</code>" environment variable will be used, if it exists. </dd>
<dt><code>relative</code></dt>
<dd>
The directory path specified is considered to be relative to the configuration file itself. </dd>
<dt>
<code>default</code>, <code>cwd</code>, or no "<code>prefix</code>" attribute specified </dt>
<dd>
The directory path specified is considered to be relative to the current working directory (where Tux Paint is running), unless a root path is included at the start (e.g., "/", "C:\\", etc.) </dd>
</ul>
</p>
</section><!-- H2: FontConfig -->
</section><!-- H1: Fonts -->

View file

@ -710,7 +710,7 @@
<li>
The location specified by the "<code>Fonts</code>" option of the "<code>Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders</code>" Windows Registry key. </li>
<li>
If the above fails, then "C:\WINDOWS\FONTS". </li>
If the above fails, then "<code>C:\WINDOWS\FONTS</code>". </li>
<li>
The location specified by the "<code>Local AppData</code>" option of the "<code>Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders</code>" Windows Registry key. The path "<code>\Microsoft\Windows\Fonts</code>" is appended to that location. </li>
</ul>
@ -743,7 +743,7 @@
</p>
</li>
<li>
<strong>Linux</strong>
<strong>Linux/etc.</strong>
<ul>
<li><code>/usr/share/feh/fonts</code></li>
<li><code>/usr/share/fonts</code></li>
@ -768,7 +768,60 @@
</h2>
</header>
<p>...</p>
<p>
Tux Paint utilizes <cite>FontConfig</cite> to find additional system-wide and user-specific fonts that the 'Text' and 'Label' tools might be able to use (unless the "<code>--nosysfonts</code>" option is set). It does this by looking for <cite>FontConfig</cite> configuration files ("<code>fonts.conf</code>") in various locations. </p>
<ul>
<li>
<strong>Windows</strong>
<ul>
<li>
The "<code>etc/fonts/fonts.conf</code>" file included with Tux Paint. </li>
</ul>
</li>
<li>
<strong>macOS</strong>
<ul>
<li>
The path specified by the "<code>FONTCONFIG_PATH</code>" environment variable, if set. </li>
</ul>
</li>
<li>
<strong>Haiku</strong>
<ul>
<li><code>/boot/system/settings/fonts/fonts.conf</code></li>
</ul>
</li>
<li>
<strong>Linux/etc.</strong>
<ul>
<li>
The path specified by the "<code>FONTCONFIG_PATH</code>" environment variable, if set. </li>
<li>
If the above fails, then "<code>/etc/fonts/fonts.conf</code>". </li>
<li>
The path specified by the "<code>XDG_CONFIG_HOME</code>" environment variable, if set. There, it looks for the file "<code>fontconfig/fonts.conf</code>". </li>
<li>
If the above fails, then "<code>$HOME/.config/fontconfig/fonts.conf</code>". </li>
</ul>
</li>
</ul>
<p>
Each FontConfig configuration file ("<code>fonts.conf</code>") is examined for "<code>&lt;dir&gt;</code>" tags that specify directory (folder) paths where fonts might be found, and Tux Paint scans them and loads the fonts. If a "<code>prefix</code>" attribute is included in the tag, Tux Paint prefixes the path accordingly. <dl>
<dt><code>xdg</code></dt>
<dd>
The directory path specified is considered to be relative to the user's local data path, specified by the "<code>XDG_DATA_HOME</code>" environment variable. If not set, then "<code>.local/share</code>" under the path specified by the "<code>HOME</code>" environment variable will be used, if it exists. </dd>
<dt><code>relative</code></dt>
<dd>
The directory path specified is considered to be relative to the configuration file itself. </dd>
<dt>
<code>default</code>, <code>cwd</code>, or no "<code>prefix</code>" attribute specified </dt>
<dd>
The directory path specified is considered to be relative to the current working directory (where Tux Paint is running), unless a root path is included at the start (e.g., "/", "C:\\", etc.) </dd>
</ul>
</p>
</section><!-- H2: FontConfig -->
</section><!-- H1: Fonts -->

View file

@ -710,7 +710,7 @@
<li>
The location specified by the "<code>Fonts</code>" option of the "<code>Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders</code>" Windows Registry key. </li>
<li>
If the above fails, then "C:\WINDOWS\FONTS". </li>
If the above fails, then "<code>C:\WINDOWS\FONTS</code>". </li>
<li>
The location specified by the "<code>Local AppData</code>" option of the "<code>Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders</code>" Windows Registry key. The path "<code>\Microsoft\Windows\Fonts</code>" is appended to that location. </li>
</ul>
@ -743,7 +743,7 @@
</p>
</li>
<li>
<strong>Linux</strong>
<strong>Linux/etc.</strong>
<ul>
<li><code>/usr/share/feh/fonts</code></li>
<li><code>/usr/share/fonts</code></li>
@ -768,7 +768,60 @@
</h2>
</header>
<p>...</p>
<p>
Tux Paint utilizes <cite>FontConfig</cite> to find additional system-wide and user-specific fonts that the 'Text' and 'Label' tools might be able to use (unless the "<code>--nosysfonts</code>" option is set). It does this by looking for <cite>FontConfig</cite> configuration files ("<code>fonts.conf</code>") in various locations. </p>
<ul>
<li>
<strong>Windows</strong>
<ul>
<li>
The "<code>etc/fonts/fonts.conf</code>" file included with Tux Paint. </li>
</ul>
</li>
<li>
<strong>macOS</strong>
<ul>
<li>
The path specified by the "<code>FONTCONFIG_PATH</code>" environment variable, if set. </li>
</ul>
</li>
<li>
<strong>Haiku</strong>
<ul>
<li><code>/boot/system/settings/fonts/fonts.conf</code></li>
</ul>
</li>
<li>
<strong>Linux/etc.</strong>
<ul>
<li>
The path specified by the "<code>FONTCONFIG_PATH</code>" environment variable, if set. </li>
<li>
If the above fails, then "<code>/etc/fonts/fonts.conf</code>". </li>
<li>
The path specified by the "<code>XDG_CONFIG_HOME</code>" environment variable, if set. There, it looks for the file "<code>fontconfig/fonts.conf</code>". </li>
<li>
If the above fails, then "<code>$HOME/.config/fontconfig/fonts.conf</code>". </li>
</ul>
</li>
</ul>
<p>
Each FontConfig configuration file ("<code>fonts.conf</code>") is examined for "<code>&lt;dir&gt;</code>" tags that specify directory (folder) paths where fonts might be found, and Tux Paint scans them and loads the fonts. If a "<code>prefix</code>" attribute is included in the tag, Tux Paint prefixes the path accordingly. <dl>
<dt><code>xdg</code></dt>
<dd>
The directory path specified is considered to be relative to the user's local data path, specified by the "<code>XDG_DATA_HOME</code>" environment variable. If not set, then "<code>.local/share</code>" under the path specified by the "<code>HOME</code>" environment variable will be used, if it exists. </dd>
<dt><code>relative</code></dt>
<dd>
The directory path specified is considered to be relative to the configuration file itself. </dd>
<dt>
<code>default</code>, <code>cwd</code>, or no "<code>prefix</code>" attribute specified </dt>
<dd>
The directory path specified is considered to be relative to the current working directory (where Tux Paint is running), unless a root path is included at the start (e.g., "/", "C:\\", etc.) </dd>
</ul>
</p>
</section><!-- H2: FontConfig -->
</section><!-- H1: Fonts -->

View file

@ -710,7 +710,7 @@
<li>
The location specified by the "<code>Fonts</code>" option of the "<code>Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders</code>" Windows Registry key. </li>
<li>
If the above fails, then "C:\WINDOWS\FONTS". </li>
If the above fails, then "<code>C:\WINDOWS\FONTS</code>". </li>
<li>
The location specified by the "<code>Local AppData</code>" option of the "<code>Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders</code>" Windows Registry key. The path "<code>\Microsoft\Windows\Fonts</code>" is appended to that location. </li>
</ul>
@ -743,7 +743,7 @@
</p>
</li>
<li>
<strong>Linux</strong>
<strong>Linux/etc.</strong>
<ul>
<li><code>/usr/share/feh/fonts</code></li>
<li><code>/usr/share/fonts</code></li>
@ -768,7 +768,60 @@
</h2>
</header>
<p>...</p>
<p>
Tux Paint utilizes <cite>FontConfig</cite> to find additional system-wide and user-specific fonts that the 'Text' and 'Label' tools might be able to use (unless the "<code>--nosysfonts</code>" option is set). It does this by looking for <cite>FontConfig</cite> configuration files ("<code>fonts.conf</code>") in various locations. </p>
<ul>
<li>
<strong>Windows</strong>
<ul>
<li>
The "<code>etc/fonts/fonts.conf</code>" file included with Tux Paint. </li>
</ul>
</li>
<li>
<strong>macOS</strong>
<ul>
<li>
The path specified by the "<code>FONTCONFIG_PATH</code>" environment variable, if set. </li>
</ul>
</li>
<li>
<strong>Haiku</strong>
<ul>
<li><code>/boot/system/settings/fonts/fonts.conf</code></li>
</ul>
</li>
<li>
<strong>Linux/etc.</strong>
<ul>
<li>
The path specified by the "<code>FONTCONFIG_PATH</code>" environment variable, if set. </li>
<li>
If the above fails, then "<code>/etc/fonts/fonts.conf</code>". </li>
<li>
The path specified by the "<code>XDG_CONFIG_HOME</code>" environment variable, if set. There, it looks for the file "<code>fontconfig/fonts.conf</code>". </li>
<li>
If the above fails, then "<code>$HOME/.config/fontconfig/fonts.conf</code>". </li>
</ul>
</li>
</ul>
<p>
Each FontConfig configuration file ("<code>fonts.conf</code>") is examined for "<code>&lt;dir&gt;</code>" tags that specify directory (folder) paths where fonts might be found, and Tux Paint scans them and loads the fonts. If a "<code>prefix</code>" attribute is included in the tag, Tux Paint prefixes the path accordingly. <dl>
<dt><code>xdg</code></dt>
<dd>
The directory path specified is considered to be relative to the user's local data path, specified by the "<code>XDG_DATA_HOME</code>" environment variable. If not set, then "<code>.local/share</code>" under the path specified by the "<code>HOME</code>" environment variable will be used, if it exists. </dd>
<dt><code>relative</code></dt>
<dd>
The directory path specified is considered to be relative to the configuration file itself. </dd>
<dt>
<code>default</code>, <code>cwd</code>, or no "<code>prefix</code>" attribute specified </dt>
<dd>
The directory path specified is considered to be relative to the current working directory (where Tux Paint is running), unless a root path is included at the start (e.g., "/", "C:\\", etc.) </dd>
</ul>
</p>
</section><!-- H2: FontConfig -->
</section><!-- H1: Fonts -->