Syncing docs again, after wrapping up path nonsense
This commit is contained in:
parent
e268b598ff
commit
a655146677
69 changed files with 830 additions and 992 deletions
|
|
@ -317,28 +317,28 @@
|
|||
</dt>
|
||||
|
||||
<dd>
|
||||
In the user's "AppData" folder:<br> e.g., <nobr>"<code>C:\Users\nom d'utilisateur\AppData\Roaming\TuxPaint\saved\</code>"</nobr> </dd>
|
||||
In the user's "AppData" folder:<br> e.g., <nobr>"<code style='background: #EEE;'>C:\Users\nom d'utilisateur\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/nom d'utilisateur/Library/Application Support/TuxPaint/saved/</code>"</nobr> </dd>
|
||||
In the user's "Application Support" folder:<br> e.g., <nobr>"<code style='background: #EEE;'>/Users/nom d'utilisateur/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/nom d'utilisateur/.tuxpaint/saved/</code>"</nobr> </dd>
|
||||
In the user's "home directory" folder:<br> e.g., <nobr>"<code style='background: #EEE;'>/home/nom d'utilisateur/.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>
|
||||
|
|
@ -618,10 +618,10 @@ cible "nosound". (c'est-à-dire, ne lancez pas "<code>make nosound</code>") Assu
|
|||
|
||||
<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/nom d'utilisateur/.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/nom d'utilisateur/.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>
|
||||
Même si le fichier de verrouillage existe, il contient l'heure de la dernière exécution de Tux Paint. Si cela fait plus de 30 secondes, Tux Paint devrait fonctionner correctement et simplement mettre à jour le fichier de verrouillage avec l'heure courante. </p>
|
||||
|
|
@ -706,7 +706,7 @@ cible "nosound". (c'est-à-dire, ne lancez pas "<code>make nosound</code>") Assu
|
|||
|
||||
<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>
|
||||
|
|
@ -714,7 +714,7 @@ cible "nosound". (c'est-à-dire, ne lancez pas "<code>make nosound</code>") Assu
|
|||
|
||||
<blockquote>
|
||||
<p>
|
||||
<nobr><code>C:\Users\nom d'utilisateur\AppData\Roaming\TuxPaint\tuxpaint.cfg</code></nobr> </p>
|
||||
<nobr><code style='background: #EEE;'>C:\Users\nom d'utilisateur\AppData\Roaming\TuxPaint\tuxpaint.cfg</code></nobr> </p>
|
||||
</blockquote>
|
||||
|
||||
<p>
|
||||
|
|
@ -728,7 +728,7 @@ cible "nosound". (c'est-à-dire, ne lancez pas "<code>make nosound</code>") Assu
|
|||
|
||||
<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>
|
||||
|
|
@ -736,7 +736,7 @@ cible "nosound". (c'est-à-dire, ne lancez pas "<code>make nosound</code>") Assu
|
|||
|
||||
<blockquote>
|
||||
<p>
|
||||
<nobr><code>/Users/nom d'utilisateur/Library/Application Support/TuxPaint/tuxpaint.cfg</code></nobr> </p>
|
||||
<nobr><code style='background: #EEE;'>/Users/nom d'utilisateur/Library/Application Support/TuxPaint/tuxpaint.cfg</code></nobr> </p>
|
||||
</blockquote>
|
||||
|
||||
<p>
|
||||
|
|
@ -750,7 +750,7 @@ cible "nosound". (c'est-à-dire, ne lancez pas "<code>make nosound</code>") Assu
|
|||
|
||||
<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>
|
||||
|
|
@ -758,7 +758,7 @@ cible "nosound". (c'est-à-dire, ne lancez pas "<code>make nosound</code>") Assu
|
|||
|
||||
<blockquote>
|
||||
<p>
|
||||
<nobr><code>/home/nom d'utilisateur/.tuxpaintrc</code></nobr> </p>
|
||||
<nobr><code style='background: #EEE;'>/home/nom d'utilisateur/.tuxpaintrc</code></nobr> </p>
|
||||
</blockquote>
|
||||
|
||||
<p>
|
||||
|
|
@ -772,7 +772,7 @@ cible "nosound". (c'est-à-dire, ne lancez pas "<code>make nosound</code>") Assu
|
|||
|
||||
<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>
|
||||
|
|
@ -784,7 +784,7 @@ cible "nosound". (c'est-à-dire, ne lancez pas "<code>make nosound</code>") Assu
|
|||
Cela signifie que si quelque chose est défini dans un fichier de configuration que vous ne souhaitez pas activer, vous devrez soit modifier le fichier config. fichier (si vous le pouvez), ou changer l'option par le biais de la ligne de commande. </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>
|
||||
|
|
@ -793,7 +793,7 @@ cible "nosound". (c'est-à-dire, ne lancez pas "<code>make nosound</code>") Assu
|
|||
</blockquote>
|
||||
|
||||
<p>
|
||||
...then you can reenable sound by either adding this option to your own <nobr>"<code>/home/nom d'utilisateur/.tuxpaintrc</code>"</nobr> file: </p>
|
||||
...then you can reenable sound by either adding this option to your own <nobr>"<code style='background: #EEE;'>/home/nom d'utilisateur/.tuxpaintrc</code>"</nobr> file: </p>
|
||||
|
||||
<blockquote>
|
||||
<p>
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue