Syncing docs again, after wrapping up path nonsense

This commit is contained in:
Bill Kendrick 2024-04-27 13:45:41 -07:00
parent e268b598ff
commit a655146677
69 changed files with 830 additions and 992 deletions

View file

@ -317,28 +317,28 @@
</dt>
<dd>
In the user's "AppData" folder:<br> e.g., <nobr>"<code>C:\Users\nome de usuario\AppData\Roaming\TuxPaint\saved\</code>"</nobr> </dd>
In the user's "AppData" folder:<br> e.g., <nobr>"<code style='background: #EEE;'>C:\Users\nome de usuario\AppData\Roaming\TuxPaint\saved\</code>"</nobr> </dd>
<dt>
<cite>macOS</cite>
</dt>
<dd>
In the user's "Application Support" folder:<br> e.g., <nobr>"<code>/Users/nome de usuario/Library/Application Support/TuxPaint/saved/</code>"</nobr> </dd>
In the user's "Application Support" folder:<br> e.g., <nobr>"<code style='background: #EEE;'>/Users/nome de usuario/Library/Application Support/TuxPaint/saved/</code>"</nobr> </dd>
<dt>
<cite>Linux / Unix</cite>
</dt>
<dd>
In the user's "home directory" folder:<br> e.g., <nobr>"<code>/home/nome de usuario/.tuxpaint/saved/</code>"</nobr> </dd>
In the user's "home directory" folder:<br> e.g., <nobr>"<code style='background: #EEE;'>/home/nome de usuario/.tuxpaint/saved/</code>"</nobr> </dd>
<dt>
<cite>Haiku</cite>
</dt>
<dd>
In the user's "settings" folder:<br> e.g., <nobr>"<code>/boot/home/config/settings/TuxPaint/saved/</code>"</nobr> </dd>
In the user's "settings" folder:<br> e.g., <nobr>"<code style='background: #EEE;'>/boot/home/config/settings/TuxPaint/saved/</code>"</nobr> </dd>
</dl>
<p>
@ -617,10 +617,10 @@
<dd>
<p>
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>C:\Program Files\TuxPaint\</code>"</nobr>). </p>
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>/home/nome de usuario/.tuxpaint/lockfile.dat</code>"</nobr> on Linux and Unix, <nobr>"<code>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/nome de usuario/.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>
Mesmo se o ficheiro de bloqueo existe, contén a «hora» na que se executou Tux Paint por última vez. Se pasaron máis de 30 segundos, Tux Paint debería funcionar ben e simplemente actualiza o ficheiro de bloqueo coa hora actual. </p>
@ -705,7 +705,7 @@
<blockquote>
<p>
<nobr><code>C:\Program Files\TuxPaint\tuxpaint.cfg</code></nobr> </p>
<nobr><code style='background: #EEE;'>C:\Program Files\TuxPaint\tuxpaint.cfg</code></nobr> </p>
</blockquote>
<p>
@ -713,7 +713,7 @@
<blockquote>
<p>
<nobr><code>C:\Users\nome de usuario\AppData\Roaming\TuxPaint\tuxpaint.cfg</code></nobr> </p>
<nobr><code style='background: #EEE;'>C:\Users\nome de usuario\AppData\Roaming\TuxPaint\tuxpaint.cfg</code></nobr> </p>
</blockquote>
<p>
@ -727,7 +727,7 @@
<blockquote>
<p>
<nobr><code>/Library/Application Support/TuxPaint/tuxpaint.cfg</code></nobr> </p>
<nobr><code style='background: #EEE;'>/Library/Application Support/TuxPaint/tuxpaint.cfg</code></nobr> </p>
</blockquote>
<p>
@ -735,7 +735,7 @@
<blockquote>
<p>
<nobr><code>/Users/nome de usuario/Library/Application Support/TuxPaint/tuxpaint.cfg</code></nobr> </p>
<nobr><code style='background: #EEE;'>/Users/nome de usuario/Library/Application Support/TuxPaint/tuxpaint.cfg</code></nobr> </p>
</blockquote>
<p>
@ -749,7 +749,7 @@
<blockquote>
<p>
<nobr><code>/etc/tuxpaint/tuxpaint.conf</code></nobr> </p>
<nobr><code style='background: #EEE;'>/etc/tuxpaint/tuxpaint.conf</code></nobr> </p>
</blockquote>
<p>
@ -757,7 +757,7 @@
<blockquote>
<p>
<nobr><code>/home/nome de usuario/.tuxpaintrc</code></nobr> </p>
<nobr><code style='background: #EEE;'>/home/nome de usuario/.tuxpaintrc</code></nobr> </p>
</blockquote>
<p>
@ -771,7 +771,7 @@
<blockquote>
<p>
<nobr><code>/boot/home/config/settings/TuxPaint/tuxpaint.conf</code></nobr> </p>
<nobr><code style='background: #EEE;'>/boot/home/config/settings/TuxPaint/tuxpaint.conf</code></nobr> </p>
</blockquote>
<p>
@ -783,7 +783,7 @@
Isto significa que se estabelece algo nun ficheiro de configuración que non quere estabelecer, terá que cambiar o ficheiro de configuración (se pode) ou anular a opción na liña de ordes. </p>
<p>
For example, on Linux and Unix, if <nobr>"<code>/etc/tuxpaint/tuxpaint.conf</code>"</nobr> includes this option to disable sound... </p>
For example, on Linux and Unix, if <nobr>"<code style='background: #EEE;'>/etc/tuxpaint/tuxpaint.conf</code>"</nobr> includes this option to disable sound... </p>
<blockquote>
<p>
@ -792,7 +792,7 @@
</blockquote>
<p>
...then you can reenable sound by either adding this option to your own <nobr>"<code>/home/nome de usuario/.tuxpaintrc</code>"</nobr> file: </p>
...then you can reenable sound by either adding this option to your own <nobr>"<code style='background: #EEE;'>/home/nome de usuario/.tuxpaintrc</code>"</nobr> file: </p>
<blockquote>
<p>