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

@ -96,7 +96,7 @@
</p>
<p>
enero 9, 2025 </p>
enero 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>