Regen DOCs after clean up (removal of "as of..." notes)

This commit is contained in:
Bill Kendrick 2025-01-12 10:40:45 -08:00
parent 277d902235
commit b88145b924
77 changed files with 753 additions and 1032 deletions

View file

@ -95,12 +95,12 @@
version 0.9.35 </h1>
<p>
Copyright &copy; 2002-2024 by various contributors; see <a href="../../AUTHORS.txt">AUTHORS.txt</a>.<br>
Copyright &copy; 2002-2025 by various contributors; see <a href="../../AUTHORS.txt">AUTHORS.txt</a>.<br>
<a href="https://tuxpaint.org/">https://tuxpaint.org/</a>
</p>
<p>
desember 25, 2024 </p>
janúar 12, 2025 </p>
</center>
</header>
@ -231,7 +231,7 @@
<p>
Your personal Tux Paint folder is stored in your personal "Application Data". For example, on newer Windows:
<blockquote>
<nobr><code style='background: #EEE;'>C:\Users\username\AppData\Roaming\TuxPaint\</code></nobr> </blockquote>
<nobr><code style='background: #EEE;'>C:\Users\<i>username</i>\AppData\Roaming\TuxPaint\</code></nobr> </blockquote>
</p>
</dd>
@ -246,7 +246,7 @@
<dt><strong>Linux and Unix</strong></dt>
<dd>
<p>
Your personal Tux Paint files go into a 'hidden directory' found in your account's home directory: <nobr>"<code style='background: #EEE;'>/home/username/.tuxpaint/</code>"</nobr>. </p>
Your personal Tux Paint files go into a 'hidden directory' found in your account's home directory: <nobr>"<code style='background: #EEE;'>/home/<i>username</i>/.tuxpaint/</code>"</nobr>. </p>
<p>
Don't forget the period ("<code>.</code>") before the "<code>tuxpaint</code>"! </p>
</dd>
@ -256,7 +256,7 @@
To add your own brushes, stamps, 'starters,' templates, and fonts, create subdirectories under your personal Tux Paint directory named "<code><b>brushes</b></code>", "<code><b>stamps</b></code>", "<code><b>starters</b></code>", "<code><b>templates</b></code>", "<code><b>fonts</b></code>", respectively. </p>
<p>
(For example, if you created a brush named <nobr>"<code style='background: #EEE;'>flower.png</code>"</nobr>, you would put it in <nobr>"<code style='background: #EEE;'>/home/username/.tuxpaint/brushes/</code>"</nobr> under Linux or Unix.) </p>
(For example, if you created a brush named <nobr>"<code style='background: #EEE;'>flower.png</code>"</nobr>, you would put it in <nobr>"<code style='background: #EEE;'>/home/<i>username</i>/.tuxpaint/brushes/</code>"</nobr> under Linux or Unix.) </p>
</section><!-- H2: Personal Files -->
</section><!-- H1: Where Files Go -->
@ -337,7 +337,7 @@
<dt><strong>Brush Spacing</strong></dt>
<dd>
<p>
As of Tux Paint version 0.9.16, you can now specify the spacing for brushes (that is, how often they are drawn). By default, the spacing will be the brush's height, divided by 4. </p>
You may specify the spacing for brushes &mdash; that is, how frequently they are drawn across the length of a line or stroke. By default, the spacing will be the brush's height, divided by 4. </p>
<p>
Add a line containing the line "<code><b>spacing=<i>N</i></b></code>" to the brush's data file, where "<i>N</i>" is the spacing you want for the brush. (The lower the number, the more often the brush is drawn.) </p>
</dd>
@ -345,9 +345,9 @@
<dt><strong>Animated Brushes</strong></dt>
<dd>
<p>
As of Tux Paint version 0.9.16, you may now create animated brushes. As the brush is used, each frame of the animation is drawn. </p>
Brushes may be animated. As the brush is used, each frame of the animation is drawn in sequence. </p>
<p>
Lay each frame out across a wide PNG image. For example, if your brush is 30x30 and you have 5 frames, the image should be 150x30. </p>
Lay each frame out across a wide PNG image. For example, if the brush is 30x30 and there are 5 frames, the image should be 150x30. </p>
<p>
Add a line containing the line "<code><b>frames=<i>N</i></b></code>" to the brush's data file, where "<i>N</i>" is the number of frames in the brush. </p>
<p class="note">
@ -357,9 +357,9 @@
<dt><strong>Directional Brushes</strong></dt>
<dd>
<p>
As of Tux Paint version 0.9.16, you may now create directional brushes. As the brush is used, different shapes are drawn, depending on the direction the brush is going. </p>
Brushes may be configured to draw a different shape based on the direction of the line or brush stroke. Different shapes will be drawn depending on which of the eight compass directions the brush is moving &mdash; up (aka North), up/right (aka Northeast), right (aka East), down/right (aka Southeast), etc.). A ninth "center" shape is used when there's no motion (e.g., simply clicking/tapping and releasing the "Paint" tool, without dragging). </p>
<p>
The directional shapes are divided into a 3x3 square in a PNG image. For example, if your brush is 30x30, the image should be 90x90, and each of the direction's shapes placed in a 3x3 grid. The center region is used for no motion. The top right is used for motion that's both up, and to the right. And so on. </p>
The directional shapes are divided into a 3x3 square in a PNG image. For example, if your brush is 30x30, the image should be 90x90, and each of the direction's shapes placed in a 3x3 grid. </p>
<p>
Add a line containing the word "<code><b>directional</b></code>" to the brush's data file. </p>
</dd>
@ -367,7 +367,7 @@
<dt><strong>Rotating Brushes</strong></dt>
<dd>
<p>
As of Tux Paint version 0.9.27, you may now create rotating brushes. As the brush is used, it is rotated 360 degrees, depending on the direction the brush is going. </p>
Brushes may be configured to rotate based on the angle of the line or brush stroke. (Unlike Directional Brushes, described above, only a single brush shape may be provided. </p>
<p>
Add a line containing the word "<code><b>rotate</b></code>" to the brush's data file. </p>
</dd>
@ -375,7 +375,7 @@
<dt><strong>Chaotic Brushes</strong></dt>
<dd>
<p>
As of Tux Paint version 0.9.34, brushes can be configured to continuously pick random directions as you draw with them. </p>
Brushes may be configured to continuously choose a random direction as you draw with them. </p>
<p>
Add a line containing the word "<code><b>chaotic</b></code>" to the brush's data file. </p>
</dd>
@ -424,7 +424,7 @@
alt=""
align="right">
<p>
As of Tux Paint version 0.9.17, Stamps may be either PNG bitmap images or SVG vector images. They can be full-color or greyscale. The alpha (transparency) channel of PNGs is used to determine the actual shape of the picture (otherwise you'll stamp a large rectangle on your drawings). </p>
Stamps may be either PNG bitmap images or SVG vector images. They can be full-color or greyscale. The alpha (transparency) channel of PNGs is used to determine the actual shape of the picture (otherwise you'll stamp a large rectangle on your drawings). </p>
<p>
PNGs can be any size, and Tux Paint (by default) provides a set of sizing buttons to let the user scale the stamp up (larger) and down (smaller). </p>
@ -662,7 +662,7 @@
For example, for the stamp "<code>stamp.png</code>" you would create another file named "<code>stamp_mirror.png</code>", which will be used when the stamp is mirrored (rather than using a backwards version of "<code>stamp.png</code>"). </p>
<p>
As of Tux Paint 0.9.18, you may similarly provide a pre-flipped image with "<code><b>_flip</b></code>" in the name, and/or an image that is both mirrored and flipped, by naming it "<code><b>_mirror_flip</b></code>". </p>
You may also provide a pre-flipped image with "<code><b>_flip</b></code>" in the name, and/or an image that is both mirrored <em>and</em> flipped, by naming it "<code><b>_mirror_flip</b></code>". </p>
<p class="note">
<span title="Information">&#128161;</span> <strong>Note:</strong> If the user flips and mirrors an image, and a pre-drawn "<code>_mirror_flip</code>" doesn't exist, but either "<code>_flip</code>" or "<code>_mirror</code>" does, it will be used, and mirrored or flipped, respectively. </p>
@ -720,7 +720,7 @@
The most basic kind of 'starter' is similar to a picture in a coloring book. It's an outline of a shape which you can then color in and add details to. In Tux Paint, as you draw, type text, or stamp stamps, the outline remains 'above' what you draw. You can erase the parts of the drawing you made, but you can't erase the outline. </p>
<p>
To create this kind of 'starter' image, simply create an outlined black and white picture in a paint program, and save it as a raster PNG file, or vector SVG. If saving as a PNG, you may optionally render the image as black-and-transparent, rather than black-and-white, but (as of Tux Paint 0.9.21) this is not required. </p>
To create this kind of 'starter' image, simply create an outlined black and white picture in a paint program, and save it as a raster PNG file, or vector SVG. If saving as a PNG, you may optionally render the image as black-and-transparent, rather than black-and-white, although this is not required. </p>
</section><!-- H2: Coloring-Book Style Starters -->
<section><!-- H2: Scene-Style Starters -->
@ -957,7 +957,7 @@
alt=""
align="right">
<p>
'Template' images also appear in the 'New' dialog, along with solid color background choices and 'Starters'. (Note: Tux Paint prior to version 0.9.22 did not have the 'Template' feature.) </p>
'Template' images also appear in the 'New' dialog, along with solid color background choices and 'Starters'. </p>
<p>
Unlike pictures drawn in Tux Paint by users and then opened later, opening a 'template' creates a new drawing. When you save, the 'template' image is not overwritten. Unlike 'starters', there is no immutable 'layer' above the canvas. You may draw over any part of it. </p>
@ -1118,7 +1118,7 @@
</header>
<p>
As of version 0.9.22, Tux Paint's 'Text' and 'Label' tools can present an on-screen keyboard that allows the pointer (via a mouse, touch screen, eye-tracking systems, etc.) to be used to input characters. Files that describe the layout and available keys are stored in Tux Paint "<code>osk</code>" directory. Each keyboard layout is defined by a number of files (some of which may be shared by different layouts). </p>
Tux Paint's 'Text' and 'Label' tools can present an on-screen keyboard that allows the pointer (via a mouse, touch screen, eye-tracking systems, etc.) to be used to input characters. Files that describe the layout and available keys are stored in Tux Paint "<code>osk</code>" directory. Each keyboard layout is defined by a number of files (some of which may be shared by different layouts). </p>
<p>
We'll use the QWERTY keyboard as an example: </p>

View file

@ -96,7 +96,7 @@
</p>
<p>
janúar 9, 2025 </p>
janúar 12, 2025 </p>
</center>
<table border="2"
@ -141,7 +141,7 @@
This means that Tux Paint either couldn't find any stamp images, or was asked not to load them. </p>
<p>
If you installed Tux Paint, but did not install the separate, optional "Stamps" collection, quit Tux Paint and install it now. It should be available from the same place you got the main Tux Paint program. <i>(Note: As of version 0.9.14, Tux Paint comes with a small collection of example stamps.)</i> </p>
If you installed Tux Paint, but did not install the separate, optional "Stamps" collection, quit Tux Paint and install it now. It should be available from the same place you got the main Tux Paint program. <i>(Note: Tux Paint ships with a very small collection of example stamps.)</i> </p>
<p>
If you don't want to install the default collection of stamps, you can just create your own. See the "Extending Tux Paint" documentation for more on creating PNG and SVG image files, TXT text description files, Ogg Vorbis, MP3 or WAV sound files, and DAT text data files that make up stamps. </p>
@ -286,12 +286,6 @@
<p>
If that program is not available (for example, you're using CUPS, the Common Unix Printing System, and do not have "<code>cups-lpr</code>" installed), you will need to specify an appropriate command using the "<code>printcommand</code>" option in Tux Paint's configuration file. (See the "Options Documentation".) </p>
<p>
<i>Note:</i> Versions of Tux Paint prior to 0.9.15 used a different default command for printing, "<code>pngtopnm | pnmtops | lpr</code>", as Tux Paint output PNG format, rather than PostScript. </p>
<p>
If you had changed your "printcommand" option prior to Tux Paint 0.9.15, you will need to go back and alter it to accept PostScript. </p>
</dd>
<dt>
@ -363,7 +357,7 @@
</dt>
<dd>
In the user's "AppData" folder:<br> e.g., <nobr>"<code style='background: #EEE;'>C:\Users\username\AppData\Roaming\TuxPaint\saved\</code>"</nobr> <br/>
In the user's "AppData" folder:<br> e.g., <nobr>"<code style='background: #EEE;'>C:\Users\<i>username</i>\AppData\Roaming\TuxPaint\saved\</code>"</nobr> <br/>
<br/>
(Note: The "<nobr><code style='background: #EEE;'>AppData</code></nobr>" folder is hidden (not visible) by default. You can enter the path manually in the location bar of your file browser (e.g., <cite>File Explorer</cite>).) <br/>
<br/>
@ -383,7 +377,7 @@
</dt>
<dd>
In the user's "home directory" folder:<br> e.g., <nobr>"<code style='background: #EEE;'>/home/username/.tuxpaint/saved/</code>"</nobr> <br/>
In the user's "home directory" folder:<br> e.g., <nobr>"<code style='background: #EEE;'>/home/<i>username</i>/.tuxpaint/saved/</code>"</nobr> <br/>
<br/>
(Note: The ".tuxpaint" folder is hidden (not visible) by default. You can enter the path manually in the location bar of your file browser (e.g., <cite>GNOME Files</cite> or <cite>Dolphin</cite>).) <br/>
<br/>
@ -676,7 +670,7 @@
If Tux Paint aborts with the message: "You're already running a copy of Tux Paint!", this means it has been launched in the last 30 seconds. (On Unix/Linux, this message would appear in a terminal console if you ran Tux Paint from a command-line. On Windows, this message would appear in a file named "<code>stdout.txt</code>" in the same folder where <code>TuxPaint.exe</code> resides (e.g., in <nobr>"<code style='background: #EEE;'>C:\Program Files\TuxPaint\</code>"</nobr>). </p>
<p>
A lockfile (e.g., <nobr>"<code style='background: #EEE;'>/home/username/.tuxpaint/lockfile.dat</code>"</nobr> on Linux and Unix, <nobr>"<code style='background: #EEE;'>userdata\lockfile.dat</code>"</nobr> on Windows) is used to make sure Tux Paint isn't run too many times at once (e.g., due to a child impatiently clicking its icon more than once). </p>
A lockfile (e.g., <nobr>"<code style='background: #EEE;'>/home/<i>username</i>/.tuxpaint/lockfile.dat</code>"</nobr> on Linux and Unix, <nobr>"<code style='background: #EEE;'>userdata\lockfile.dat</code>"</nobr> on Windows) is used to make sure Tux Paint isn't run too many times at once (e.g., due to a child impatiently clicking its icon more than once). </p>
<p>
Even if the lockfile exists, it contains the 'time' Tux Paint was last run. If it's been more than 30 seconds, Tux Paint should run fine, and simply update the lockfile with the current time. </p>
@ -786,7 +780,7 @@
<blockquote>
<p>
<nobr><code style='background: #EEE;'>C:\Users\username\AppData\Roaming\TuxPaint\tuxpaint.cfg</code></nobr> </p>
<nobr><code style='background: #EEE;'>C:\Users\<i>username</i>\AppData\Roaming\TuxPaint\tuxpaint.cfg</code></nobr> </p>
</blockquote>
<p>
@ -830,7 +824,7 @@
<blockquote>
<p>
<nobr><code style='background: #EEE;'>/home/username/.tuxpaintrc</code></nobr> </p>
<nobr><code style='background: #EEE;'>/home/<i>username</i>/.tuxpaintrc</code></nobr> </p>
</blockquote>
<p>
@ -865,7 +859,7 @@
</blockquote>
<p>
...then you can reenable sound by either adding this option to your own <nobr>"<code style='background: #EEE;'>/home/username/.tuxpaintrc</code>"</nobr> file: </p>
...then you can reenable sound by either adding this option to your own <nobr>"<code style='background: #EEE;'>/home/<i>username</i>/.tuxpaintrc</code>"</nobr> file: </p>
<blockquote>
<p>

View file

@ -93,12 +93,12 @@
Installation Documentation </h1>
<p>
Copyright &copy; 2002-2024 by various contributors; see <a href="../../AUTHORS.txt">AUTHORS.txt</a>.<br>
Copyright &copy; 2002-2025 by various contributors; see <a href="../../AUTHORS.txt">AUTHORS.txt</a>.<br>
<a href="https://tuxpaint.org/">https://tuxpaint.org/</a>
</p>
<p>
apríl 29, 2024 </p>
janúar 12, 2025 </p>
</center>
</header>
@ -206,7 +206,7 @@
<dt><strong>libpaper (Linux/Unix only)</strong></dt>
<dd>
<p>
As of Tux Paint 0.9.17, Tux Paint can determine your system's default paper size (e.g., A4 or Letter), or can be told to use a particular paper size, thanks to "libpaper". </p>
Tux Paint can determine your system's default paper size (e.g., A4 or Letter), or can be told to use a particular paper size, thanks to "libpaper". </p>
<p>
<a href="https://github.com/naota/libpaper">https://github.com/naota/libpaper</a>
@ -226,7 +226,7 @@
<dt><strong>SVG graphics support</strong></dt>
<dd>
<p>
As of Tux Paint 0.9.17, Tux Paint can load SVG (Scalable Vector Graphics) images as stamps. Two sets of libraries are supported, and SVG support can be completely disabled (via "<code style="white-space: nowrap;">make SVG_LIB:=</code>") </p>
Tux Paint can load SVG (Scalable Vector Graphics) images as stamps. Two sets of libraries are supported, and SVG support can be completely disabled (via "<code style="white-space: nowrap;">make SVG_LIB:=</code>") </p>
<dl>
<dt>librsvg-2 &amp; libCairo2 (newer libraries)</dt>
@ -311,7 +311,7 @@
</header>
<p>
As of February 2005 (starting with Tux Paint 0.9.15), the "<code>Makefile</code>" includes support for building on a Windows system using MinGW/MSYS (<a href="https://sourceforge.net/projects/msys2/">https://sourceforge.net/projects/msys2/</a>). </p>
The "<code>Makefile</code>" includes support for building on a Windows system using MinGW/MSYS (<a href="https://sourceforge.net/projects/msys2/">https://sourceforge.net/projects/msys2/</a>). </p>
<p>
Many tools and libraries are required to build Tux Paint. The package management system "<code>pacman</code>" helps you install them automatically solving complicated dependencies. </p>
@ -751,7 +751,7 @@
</header>
<p>
If, when you double-click on the shortcut to run Tux Paint, nothing happens, it is probably because some of these command-line options are wrong. Open an Explorer, and look for a file called "<code>stderr.txt</code>" in your personal saving folder for TuxPaint which is normaly <nobr>"<code style='background: #EEE;'>C:\Users\username\AppData\Roaming\TuxPaint\</code>"</nobr>. </p>
If, when you double-click on the shortcut to run Tux Paint, nothing happens, it is probably because some of these command-line options are wrong. Open an Explorer, and look for a file called "<code>stderr.txt</code>" in your personal saving folder for TuxPaint which is normaly <nobr>"<code style='background: #EEE;'>C:\Users\<i>username</i>\AppData\Roaming\TuxPaint\</code>"</nobr>. </p>
<p>
It will contain a description of what was wrong. Usually it will just be due to incorrect character-case (capital 'Z' instead of lowercase 'z') or a missing (or extra) '-' (dash). </p>

View file

@ -97,12 +97,12 @@
Magic Tool Plugin API Documentation </h2>
<p>
Höfundarréttur &copy; 2007-2024 eftir various contributors; sjá <a href="../../AUTHORS.txt">AUTHORS-skrá</a>.<br>
Höfundarréttur &copy; 2007-2025 eftir various contributors; sjá <a href="../../AUTHORS.txt">AUTHORS-skrá</a>.<br>
<a href="https://tuxpaint.org/">https://tuxpaint.org/</a>
</p>
<p>
17. september 2024 </p>
12. janúar 2025 </p>
</center>
</header>
@ -153,7 +153,7 @@
</header>
<p>
Beginning with version 0.9.18, Tux Paint's 'Magic' tools were converted from routines that lived within the application itself, to a set of 'plugins' that are loaded when Tux Paint starts up. </p>
Tux Paint's 'Magic' tools come as a set of 'plugins' which are loaded when Tux Paint starts up. </p>
<p>
This division allows more rapid development of 'Magic' tools, and allows programmers to create and test new tools without needing to integrate them within the main Tux Paint source code. (Users of more professional graphics tools, such as GIMP, should be familiar with this plugin concept.) </div>

View file

@ -97,12 +97,12 @@
Options Documentation </h2>
<p>
Copyright &copy; 2002-2024 by various contributors; see <a href="../../AUTHORS.txt">AUTHORS.txt</a>.<br>
Copyright &copy; 2002-2025 by various contributors; see <a href="../../AUTHORS.txt">AUTHORS.txt</a>.<br>
<a href="https://tuxpaint.org/">https://tuxpaint.org/</a>
</p>
<p>
apríl 29, 2024 </p>
janúar 12, 2025 </p>
</center>
</header>
@ -169,7 +169,7 @@
</header>
<p>
<nobr><code style='background: #EEE;'>/home/username/.tuxpaintrc</code></nobr> </p>
<nobr><code style='background: #EEE;'>/home/<i>username</i>/.tuxpaintrc</code></nobr> </p>
</div>
<section class="indent"><!-- H3: System-Wide Configuration File -->
@ -216,7 +216,7 @@
</header>
<p>
<nobr><code style='background: #EEE;'>C:\Users\username\AppData\Roaming\TuxPaint\tuxpaint.cfg</code></nobr> </p>
<nobr><code style='background: #EEE;'>C:\Users\<i>username</i>\AppData\Roaming\TuxPaint\tuxpaint.cfg</code></nobr> </p>
<p>
You can use NotePad or WordPad to create this file. Be sure to save it as Plain Text, and make sure the filename doesn't have ".txt" at the end... </p>
@ -519,10 +519,7 @@
<dd>
<p>
Prior to Tux Paint 0.9.15, the middle and right buttons on a mouse could also be used for clicking. In version 0.9.15, it was changed so that <i>only</i> the left mouse button worked, so as to not train children to use the wrong button. </p>
<p>
However, for children who have trouble with the mouse, this distinction between the two or three buttons on a mouse can be disabled (returning Tux Paint to its old behavior) by using this option. </p>
For children who have trouble with the mouse, this distinction between the two or three buttons on a mouse may be disabled by using this option. </p>
<p class="note">
<span title="Configuration option">&#9881;</span> <strong>Note:</strong> If used in a system-wide configuration file, may be overridden by the user's configuration file using "<code>nobuttondistinction=no</code>" or "<code>buttondistinction=yes</code>". In both cases, may be overridden by the command-line option "<code>--buttondistinction</code>". </p>
</dd>
@ -1637,12 +1634,6 @@
<blockquote>
<code>lpr</code>
</blockquote>
<p class="note">
<span title="Version variation">&#128220;</span> <b>Note:</b> Versions of Tux Paint prior to 0.9.15 sent PNG format data to the print command (which defaulted to "<code>pngtopnm | pnmtops | lpr</code>"). </p>
<p>
If you set an alternative <code><b>printcommand</b></code> in the configuration file prior to version 0.9.15, you will need to change it. </p>
</dd>
<dt>
@ -1785,11 +1776,11 @@
<dt>Linux / Unix</dt>
<dd>
Under a hidden directory in your home directory:<br/>
<nobr><code style='background: #EEE;'>/home/username/.tuxpaint/saved/</code></nobr> </dd>
<nobr><code style='background: #EEE;'>/home/<i>username</i>/.tuxpaint/saved/</code></nobr> </dd>
<dt>Windows</dt>
<dd>
<nobr><code style='background: #EEE;'>C:\Users\username\AppData\Roaming\TuxPaint\saved\</code></nobr> </dd>
<nobr><code style='background: #EEE;'>C:\Users\<i>username</i>\AppData\Roaming\TuxPaint\saved\</code></nobr> </dd>
<dt>macOS</dt>
<dd>
@ -1823,7 +1814,7 @@
<ul>
<li>Linux &amp; Unix — If available, wherever your desktop environment is configured for pictures to be stored, based on your XDG (X Desktop Group) configuration. (Try running the command-line "<code style="white-space: nowrap;">xdg-user-dir PICTURES</code>" to find out.)<br>
Typically (in an English locale), this will be a "<code>Pictures</code>" subdirectory in your home directory (i.e., <nobr>"<code style='background: #EEE;'>/home/username/Pictures</code>"</nobr>).<br>
Typically (in an English locale), this will be a "<code>Pictures</code>" subdirectory in your home directory (i.e., <nobr>"<code style='background: #EEE;'>/home/<i>username</i>/Pictures</code>"</nobr>).<br>
Tux Paint will fall back to using that typical directory, if no XDG configuration can be read, or nothing is set for "<code>XDG_PICTURES_DIR</code>". </li>
<li>Windows - <nobr>"<code style='background: #EEE;'>My Pictures</code>"</nobr> directory for each user (normaly <nobr>"<code style='background: #EEE;'>C:\Users\username\My Pictures</code>"</nobr>)<br>You can directly open the folder as follows: <ul>
<li>Press "[Windows]+[R]" key to open "Run ..." dialogue.</li>
@ -1836,11 +1827,11 @@
</ul>
<p class="note">
<span title="Information">&#128161;</span> <strong>Note:</strong> When the defaults are used, a new "<code>TuxPaint</code>" subdirectory will be created and used. (e.g., <nobr>"<code style='background: #EEE;'>/home/username/Pictures/TuxPaint</code>"</nobr>) When the "<code>--exportdir</code>" option is used, the exact path specified will be used (no "<code>TuxPaint</code>" subdirectory is created). </p>
<span title="Information">&#128161;</span> <strong>Note:</strong> When the defaults are used, a new "<code>TuxPaint</code>" subdirectory will be created and used. (e.g., <nobr>"<code style='background: #EEE;'>/home/<i>username</i>/Pictures/TuxPaint</code>"</nobr>) When the "<code>--exportdir</code>" option is used, the exact path specified will be used (no "<code>TuxPaint</code>" subdirectory is created). </p>
<p>
The directory itself (e.g., <nobr>"<code style='background: #EEE;'>/home/username/Pictures/TuxPaint</code>"</nobr>) will be created, if it doesn't exist. </p>
The directory itself (e.g., <nobr>"<code style='background: #EEE;'>/home/<i>username</i>/Pictures/TuxPaint</code>"</nobr>) will be created, if it doesn't exist. </p>
<p>
If the <em>parent</em> directory (e.g., <nobr>"<code style='background: #EEE;'>/home/username/Pictures</code>"</nobr>) also does not exist, Tux Paint will attempt to create it as well (but not any directories higher than that). </p>
If the <em>parent</em> directory (e.g., <nobr>"<code style='background: #EEE;'>/home/<i>username</i>/Pictures</code>"</nobr>) also does not exist, Tux Paint will attempt to create it as well (but not any directories higher than that). </p>
<p>
Example: <code>exportdir=/home/penguin/TuxPaintExports</code> </p>
@ -1944,10 +1935,10 @@
<dl>
<dt>Linux / Unix</dt>
<dd><nobr><code style='background: #EEE;'>/home/username/.tuxpaint/</code></nobr></dd>
<dd><nobr><code style='background: #EEE;'>/home/<i>username</i>/.tuxpaint/</code></nobr></dd>
<dt>Windows</dt>
<dd><nobr><code style='background: #EEE;'>C:\Users\username\AppData\Roaming\TuxPaint\</code></nobr></dd>
<dd><nobr><code style='background: #EEE;'>C:\Users\<i>username</i>\AppData\Roaming\TuxPaint\</code></nobr></dd>
<dt>macoS</dt>
<dd><nobr><code style='background: #EEE;'>/Users/<i>username</i>/Library/Application Support/TuxPaint/</code></nobr></dd>
@ -2373,7 +2364,7 @@
</header>
<p>
If any of the above options are set in a system-wide configuration file (e.g. <nobr>"<code style='background: #EEE;'>/etc/tuxpaint/tuxpaint.conf</code>"</nobr> on Linux), you may override them in your own personal configuration file (e.g. <nobr>"<code style='background: #EEE;'>/home/username/.tuxpaintrc</code>"</nobr>) </p>
If any of the above options are set in a system-wide configuration file (e.g. <nobr>"<code style='background: #EEE;'>/etc/tuxpaint/tuxpaint.conf</code>"</nobr> on Linux), you may override them in your own personal configuration file (e.g. <nobr>"<code style='background: #EEE;'>/home/<i>username</i>/.tuxpaintrc</code>"</nobr>) </p>
<p>
For true/false options, like "<code>noprint</code>" and "<code>grab</code>", you can simply say they equal 'no' in your personal configuration file: </p>
@ -2550,7 +2541,7 @@
This prevents the system-wide configuration file (e.g. <nobr>"<code style='background: #EEE;'>/etc/tuxpaint/tuxpaint.conf</code>"</nobr> on Linux), from being read. </p>
<p>
Only your own configuration file (e.g. <nobr>"<code style='background: #EEE;'>/home/username/.tuxpaintrc</code>"</nobr> on Linux) &mdash; if it exists &mdash; will be used. </p>
Only your own configuration file (e.g. <nobr>"<code style='background: #EEE;'>/home/<i>username</i>/.tuxpaintrc</code>"</nobr> on Linux) &mdash; if it exists &mdash; will be used. </p>
</dd>
</dl>

View file

@ -1706,7 +1706,7 @@
</dt>
<dd>
In the user's "AppData" folder:<br> e.g., <nobr>"<code style='background: #EEE;'>C:\Users\username\AppData\Roaming\TuxPaint\saved\</code>"</nobr> <br/>
In the user's "AppData" folder:<br> e.g., <nobr>"<code style='background: #EEE;'>C:\Users\<i>username</i>\AppData\Roaming\TuxPaint\saved\</code>"</nobr> <br/>
<br/>
(Note: The "<nobr><code style='background: #EEE;'>AppData</code></nobr>" folder is hidden (not visible) by default. You can enter the path manually in the location bar of your file browser (e.g., <cite>File Explorer</cite>).) <br/>
<br/>
@ -1726,7 +1726,7 @@
</dt>
<dd>
In the user's "home directory" folder:<br> e.g., <nobr>"<code style='background: #EEE;'>/home/username/.tuxpaint/saved/</code>"</nobr> <br/>
In the user's "home directory" folder:<br> e.g., <nobr>"<code style='background: #EEE;'>/home/<i>username</i>/.tuxpaint/saved/</code>"</nobr> <br/>
<br/>
(Note: The ".tuxpaint" folder is hidden (not visible) by default. You can enter the path manually in the location bar of your file browser (e.g., <cite>GNOME Files</cite> or <cite>Dolphin</cite>).) <br/>
<br/>