Sync docs: macOS build info & French translation
h/t Mark & Jacques
This commit is contained in:
Bill Kendrick
parent
89a8cc5efe
commit
d570f12f0b
133 changed files with 1094 additions and 1400 deletions
|
|
@ -93,7 +93,7 @@
|
|||
Documentation sur l'installation </h1>
|
||||
|
||||
<p>
|
||||
Copyright © 2002-2023 by divers contributeurs; see <a href="../../AUTHORS.txt">AUTHORS.txt</a>.<br>
|
||||
Copyright © 2002-2023 by divers contributeurs; voir <a href="../../AUTHORS.txt">AUTHORS.txt</a>.<br>
|
||||
<a href="https://tuxpaint.org/">https://tuxpaint.org/</a>
|
||||
</p>
|
||||
|
||||
|
|
@ -151,7 +151,7 @@
|
|||
Tux Paint nécessite la bibliothèque de couches DirectMedia simple (libSDL), une bibliothèque de programmation multimédia Open Source disponible sous la Licence publique générale limitée GNU (LGPL). </p>
|
||||
|
||||
<p>
|
||||
Along with libSDL, Tux Paint depends on a number of other SDL 'helper' libraries: SDL_Image (for graphics files), SDL_gfx (for some graphical functions, like rotation), SDL_TTF and SDL2_Pango (for True Type Font support) and, optionally, SDL_Mixer (for sound effects). </p>
|
||||
Avec libSDL, Tux Paint dépend d'un certain nombre d'autres bibliothèques 'd'aide' SDL : SDL_Image (pour les fichiers graphiques), SDL_gfx (pour certaines fonctions graphiques, comme la rotation), SDL_TTF et SDL_Pango (pour la prise en charge des polices True Type) et, éventuellement, SDL_Mixer (pour les effets sonores). </p>
|
||||
|
||||
<p>
|
||||
Les bibliothèques SDL sont disponibles en tant que code source, ou en tant que paquets RPM ou Debian pour diverses distributions de Linux. Ils peuvent être téléchargés à partir de : </p>
|
||||
|
|
@ -168,7 +168,7 @@
|
|||
Elles sont aussi parmi les paquets inclus dans votre distribution (par ex. sur le media d'installation, ou via la maintenance de vos logiciels comme la commande <code>apt</code> de Debian). </p>
|
||||
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> When installing libraries from packages, be sure to ALSO install the development versions of the packages. (For example, install both "<code>SDL2-2.24.0.rpm</code>" <em>and</em> "<code>SDL2-devel-2.24.0.rpm</code>".) </p>
|
||||
<span title="Information">💡</span> <strong>Remarque :</strong>Lors de l'installation à partir de paquets, assurez-vous d'installer AUSSI les versions de développement des paquets (Par ex. installez les deux "<code>SDL2-2.24.0.rpm</code>" <em>et</em> "<code>SDL2-2.24.0-devel.rpm</code>".) </p>
|
||||
</section><!-- H2: Simple DirectMedia Layer library (libSDL) -->
|
||||
|
||||
<section class="indent"><!-- H2: Other Libraries -->
|
||||
|
|
@ -265,7 +265,7 @@
|
|||
</p>
|
||||
</dd>
|
||||
|
||||
<dt><strong>Outils NetPBM (optionnel) ne sont plus utilisés par défaut</strong></dt>
|
||||
<dt><strong>Outils NetPBM (optionnel) Ne sont plus utilisés par défaut</strong></dt>
|
||||
<dd>
|
||||
<p class="note">
|
||||
<span title="Version variation">📜</span> Sous Linux et Unix, les anciennes versions de Tux Paint utilisaient les outils NetPBM comme aide à l'impression. (Un PNG est généré par TuxPaint et converti en PostScript en utilisant en ligne de commande les outils NetPBM <code>pngtopnm</code> et <code>pnmtops</code>.) </p>
|
||||
|
|
@ -324,7 +324,7 @@
|
|||
<p>
|
||||
Téléchargez le dernier environnement MSYS2 à partir de <a href="https://www.msys2.org/">https://www.msys2.org/</a> et installez-le où vous voulez (par défaut "<code>C:\msys64</code>") </p>
|
||||
<p>
|
||||
Open the MSYS2 shell from the "Start Menu" → "MSYS2 64bit" → "MSYS2 MSYS" and execute following command: <blockquote>
|
||||
Ouvrez le shell MSYS2 via le "Menu de Démarrage" →;"MSYS2 64bit" -→ "MSTS2 MSYS" et exécutez la commande suivante : <blockquote>
|
||||
<code>
|
||||
$ <strong>yes</strong> "" | <strong>pacman</strong> -Syu
|
||||
</code>
|
||||
|
|
@ -332,7 +332,7 @@
|
|||
</p>
|
||||
|
||||
<p>
|
||||
This will update core system and the window will close automatically. Open the msys2 shell again and execute following command to finish remaining updating process. <blockquote>
|
||||
Ceci mettra à jour tout le système et la fenêtre se fermera automatiquement. Ouvrez le shell msys2 de nouveau et exécutez la commande suivante pour finaliser le process restant de mise à jour. <blockquote>
|
||||
<code>
|
||||
$ <strong>yes</strong> "" | <strong>pacman</strong> -Syu
|
||||
</code>
|
||||
|
|
@ -358,12 +358,12 @@
|
|||
<header>
|
||||
<h4>
|
||||
<a name="64bit" id="64bit">
|
||||
MinGW 64bit (x86_64) compiler and tools </a>
|
||||
Compilateur MinGW 64bit (x86_64) et outils </a>
|
||||
</h4>
|
||||
</header>
|
||||
|
||||
<p>
|
||||
Sous le shell MSYS2, exécutez la commande suivante pour installer 64bit compiler and basic development tools : <blockquote>
|
||||
Sous le shell MSYS2, exécutez la commande suivante pour installer compilateur 64bit et outils basiques de développement : <blockquote>
|
||||
<code>
|
||||
$ <strong>yes</strong> "" | <strong>pacman</strong> -S mingw-w64-x86_64-{gcc,pkgconf,ntldd-git}
|
||||
</code>
|
||||
|
|
@ -376,7 +376,7 @@
|
|||
<section class="indent"><!-- H4: ...dependency libraries for Tux Paint -->
|
||||
<header>
|
||||
<h4>
|
||||
64bit (x86_64) dependency libraries for Tux Paint and Tux Paint Config </h4>
|
||||
bibliothèques de dépendance 64bit (x86_64) pour Tux Paint et Tux Paint Config </h4>
|
||||
</header>
|
||||
|
||||
<p>
|
||||
|
|
@ -452,12 +452,12 @@
|
|||
<header>
|
||||
<h4>
|
||||
<a name="32bit" id="32bit">
|
||||
MinGW 32bit (i686) compiler and tools </a>
|
||||
Compilateur MinGW 32bit (i686) et outils </a>
|
||||
</h4>
|
||||
</header>
|
||||
|
||||
<p>
|
||||
Sous le shell MSYS2, exécutez la commande suivante pour installer 32bit compiler and basic development tools : <blockquote>
|
||||
Sous le shell MSYS2, exécutez la commande suivante pour installer compilateur 32bit et outils basiques de développement : <blockquote>
|
||||
<code>
|
||||
$ <strong>yes</strong> "" | <strong>pacman</strong> -S mingw-w64-i686-{gcc,pkgconf,ntldd-git}
|
||||
</code>
|
||||
|
|
@ -470,7 +470,7 @@
|
|||
<section class="indent"><!-- H4: ...dependency libraries for Tux Paint -->
|
||||
<header>
|
||||
<h4>
|
||||
32bit (i686) dependency libraries for Tux Paint and Tux Paint Config </h4>
|
||||
bibliothèques de dépendance 32bit (i686) pour Tux Paint et Tux Paint Config </h4>
|
||||
</header>
|
||||
|
||||
<p>
|
||||
|
|
@ -586,9 +586,9 @@
|
|||
<p>
|
||||
You can use either (a) a stable tar-ball release, or (b) the developing source tree. <ol type="a">
|
||||
<li>
|
||||
Using stable tar-ball release: <ul>
|
||||
Utiliser une version tar-ball stable : <ul>
|
||||
<li>
|
||||
<a href="https://sourceforge.net/projects/tuxpaint/files/tuxpaint-config/">Download a source tar-ball</a>
|
||||
<a href="https://sourceforge.net/projects/tuxpaint/files/tuxpaint-config/">Télécharger l'ensemble des fichiers sources</a>
|
||||
</li>
|
||||
<li>
|
||||
Expand the tar-ball and change the directory name so that the final packaging process can find related files. <blockquote>
|
||||
|
|
@ -601,9 +601,9 @@
|
|||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
Using the developing source tree: <ul>
|
||||
Utiliser l'arborescence source en développement : <ul>
|
||||
<li>
|
||||
Fetch the developing source tree from git repository: <blockquote>
|
||||
Aller chercher l'arborescence source en développement via le dépôt git : <blockquote>
|
||||
<code>
|
||||
$ <strong>git</strong> clone https://git.code.sf.net/p/tuxpaint/tuxpaint-config tuxpaint-config
|
||||
</code>
|
||||
|
|
@ -614,7 +614,7 @@
|
|||
</ol>
|
||||
</p>
|
||||
<p>
|
||||
Now you can build Tux Paint Config. as follows: <blockquote>
|
||||
Maintenant vous pouvez faire Tux Paint Config. comme suit : <blockquote>
|
||||
<code>
|
||||
$ <strong>cd</strong> tuxpaint-config<br/>
|
||||
$ <strong>make</strong> win32<br/>
|
||||
|
|
@ -631,9 +631,9 @@
|
|||
<p>
|
||||
You can use either (a) a stable tar-ball release, or (b) the developing source tree. <ol type="a">
|
||||
<li>
|
||||
Using stable tar-ball release: <ul>
|
||||
Utiliser une version tar-ball stable : <ul>
|
||||
<li>
|
||||
<a href="https://sourceforge.net/projects/tuxpaint/files/tuxpaint/">Download a source tar-ball</a>
|
||||
<a href="https://sourceforge.net/projects/tuxpaint/files/tuxpaint/">Télécharger l'ensemble des fichiers sources</a>
|
||||
</li>
|
||||
<li>
|
||||
Expand the tar-ball and change the directory name so that the final packaging process can find related files. <blockquote>
|
||||
|
|
@ -646,9 +646,9 @@
|
|||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
Using the developing source tree: <ul>
|
||||
Utiliser l'arborescence source en développement : <ul>
|
||||
<li>
|
||||
Fetch the developing source tree from git repository: <blockquote>
|
||||
Aller chercher l'arborescence source en développement via le dépôt git : <blockquote>
|
||||
<code>
|
||||
$ <strong>git</strong> clone https://git.code.sf.net/p/tuxpaint/tuxpaint tuxpaint
|
||||
</code>
|
||||
|
|
@ -659,7 +659,7 @@
|
|||
</ol>
|
||||
</p>
|
||||
<p>
|
||||
Now you can build Tux Paint as follows: <blockquote>
|
||||
Maintenant vous pouvez faire Tux Paint comme suit : <blockquote>
|
||||
<code>
|
||||
$ <strong>cd</strong> tuxpaint<br/>
|
||||
$ <strong>make</strong> bdist-win32<br/>
|
||||
|
|
@ -675,7 +675,7 @@
|
|||
<section class="indent"><!-- H3: Building the Tux Paint Windows Installer -->
|
||||
<header>
|
||||
<h3>
|
||||
Building the Tux Paint Windows Installer </h3>
|
||||
Construire l'installateur de Tux Paint sous Windows </h3>
|
||||
</header>
|
||||
|
||||
<p>
|
||||
|
|
@ -683,7 +683,7 @@
|
|||
<p>
|
||||
Officiellement Inno Setup prend en compte des traductions dans environ 20 langues. Cependant, un des points majeurs de Tux Paint est qu'il supporte beaucoup de langues. Aussi, le script de mise au point "<code>tuxpaint.iss</code>" qui sert pour construire le programme d'installation est écrit en beaucoup plus de langues, y compris des non-officielles qui sont disponibles sur "<a href="https://jrsoftware.org/files/istrans/">Inno Setup Translations</a>". Vous devez télécharger les fichiers de traduction (<code>.isl</code>) qui sont requis et les mettre dans le répertoire "Languages" sous le répertoire dans lequel Inno Setup est installé. </p>
|
||||
<p>
|
||||
Before building an installer, edit the "<code>tuxpaint.iss</code>" file and enable one of the lines starting with "<code>#define BuildTarget=</code>", depending on the architecture of the installer you want to create. </p>
|
||||
Avant de construire un programme d'installation, éditez le fichier "<code>tuxpaint.iss</code>" et activez l'une des lignes commençant par "<code>#define BuildTarget=</code>", en fonction de l'architecture du programme que vous voulez créer. </p>
|
||||
<p>
|
||||
Alors, vous pouvez facilement construire un installateur exécutable en cliquant-droit sur l'icône "<code>tuxpaint.iss</code>" du répertoires "<code>win32</code>" et sélectionner "Compile" dans la liste. Cela prendra un certain temps, et éventuellement vous obtiendrez un fichier "<code>tuxpaint-<i>X.Y.Z</i>-windows-<arch>-installer.exe</code>" dans le même répertoire. </p>
|
||||
</section><!-- H3: Building the Tux Paint Windows Installer -->
|
||||
|
|
@ -691,7 +691,7 @@
|
|||
<section class="indent"><!-- H3: Running the Tux Paint Windows Installer -->
|
||||
<header>
|
||||
<h3>
|
||||
Running the Tux Paint Windows Installer </h3>
|
||||
Utiliser l'installateur de Tux Paint sous Windows </h3>
|
||||
</header>
|
||||
|
||||
<p>
|
||||
|
|
@ -713,7 +713,7 @@
|
|||
<section class="indent"><!-- H3: Changing the Settings Using the Shortcut -->
|
||||
<header>
|
||||
<h3>
|
||||
Changing the Settings Using the Shortcut </h3>
|
||||
Modification des paramètres à l'aide du raccourci </h3>
|
||||
</header>
|
||||
|
||||
<p>
|
||||
|
|
@ -753,7 +753,7 @@
|
|||
<section class="indent"><!-- H3: If Something Goes Wrong -->
|
||||
<header>
|
||||
<h3>
|
||||
If Something Goes Wrong </h3>
|
||||
Si quelque chose ne va pas </h3>
|
||||
</header>
|
||||
|
||||
<p>
|
||||
|
|
@ -811,7 +811,7 @@
|
|||
<section class="indent"><!-- H3: Disabling Sound at Compile-time -->
|
||||
<header>
|
||||
<h3>
|
||||
Disabling Sound at Compile-time </h3>
|
||||
Désactiver le son lors de la compilation </h3>
|
||||
</header>
|
||||
|
||||
<p>
|
||||
|
|
@ -826,7 +826,7 @@
|
|||
<section class="indent"><!-- H3: Other options -->
|
||||
<header>
|
||||
<h3>
|
||||
Other options </h3>
|
||||
Autres options </h3>
|
||||
</header>
|
||||
|
||||
<p>
|
||||
|
|
@ -836,7 +836,7 @@
|
|||
<section class="indent"><!-- H3: If you get errors -->
|
||||
<header>
|
||||
<h3>
|
||||
If you get errors </h3>
|
||||
Si vous obtenez des erreurs </h3>
|
||||
</header>
|
||||
|
||||
<p>
|
||||
|
|
@ -846,7 +846,7 @@
|
|||
<section class="indent"><!-- H3: Installing -->
|
||||
<header>
|
||||
<h3>
|
||||
Installng </h3>
|
||||
Installation </h3>
|
||||
</header>
|
||||
|
||||
<p>
|
||||
|
|
@ -1044,10 +1044,10 @@
|
|||
% <strong>make</strong> install
|
||||
</code>
|
||||
</blockquote>
|
||||
... to create the <code>TuxPaint.app</code> application bundle that can be run in-place or copied to <code>/Applications</code>. To create the DMG file for distribution, use 'make TuxPaint.dmg'. </p>
|
||||
... to create the <code>TuxPaint.app</code> application bundle that can be run in-place or copied to <code>/Applications</code>. Pour créer le fichier DMG pour la distribution, faites 'make TuxPaint.dmg'. </p>
|
||||
|
||||
<p>
|
||||
Additional steps may be required when building for the Apple Silicon. See "Building for Apple Silicon" below. </p>
|
||||
Additional steps are required when building a Unviersal Binary. See "Building a Universal Binary" below. </p>
|
||||
</section><!-- H3: How to Build -->
|
||||
|
||||
<section class="indent"><!-- H3: Known Issues -->
|
||||
|
|
@ -1100,7 +1100,7 @@
|
|||
<section class="indent"><!-- H3: Recompiling MacPorts -->
|
||||
<header>
|
||||
<h3>
|
||||
Recompiling MacPorts </h3>
|
||||
Recompiler MacPorts </h3>
|
||||
</header>
|
||||
|
||||
<p>
|
||||
|
|
@ -1113,7 +1113,7 @@
|
|||
</p>
|
||||
|
||||
<p>
|
||||
Then uninstall all MacPorts packages: <blockquote>
|
||||
Ensuite désinstaller tous les paquets MacPorts : <blockquote>
|
||||
<code>
|
||||
$ <strong>sudo port</strong> -fp uninstall installed
|
||||
</code>
|
||||
|
|
@ -1127,39 +1127,16 @@
|
|||
As of this writing, all libraries Tux Paint requires from MacPorts can be recompiled in this manner to run on macOS 10.10 Yosemite and later on Intel CPUs, and macOS 11.0 Big Sur and later on Apple Silicon. Unfortunately, although MacPorts has the option to enable the building of universal libraries, several libraries Tux Paint require cannot be built as universal libraries so they can only be built to run natively on the hardware on which they were built. See "Building a Universal Binary" below for instructions on how to build Tux Paint as a Universal Binary. </p>
|
||||
</section><!-- H3: Recompiling MacPorts -->
|
||||
|
||||
<section class="indent"><!-- H3: Building for Apple Silicon -->
|
||||
<header>
|
||||
<h3>
|
||||
Building for Apple Silicon </h3>
|
||||
</header>
|
||||
|
||||
<p>macOS for Apple Silicon requires all native Apple Silicon applications be signed, even if it is signed "ad-hoc" (anonymously). Because of this, compilers that produce native Apple Silicon applications sign all produced binaries and libraries as a part of the compilation process.<sup>*</sup> However, the Tux Paint compilation process modifies the libraries to be modular (using <code>install_name_tool</code>) so they can be added into the application bundle, which has the unfortunate side effect of breaking the signature. This can be addressed by signing the application bundle ad-hoc (example below) or using your own Apple Developer Identity if you have one. The DMG file, if needed, must be created after signing the App Bundle so the DMG file is created with signed App Bundle: <blockquote>
|
||||
<code>
|
||||
$ <strong>codesign</strong> -s - TuxPaint.app<br/>
|
||||
$ <strong>make</strong> TuxPaint.dmg
|
||||
</code>
|
||||
</blockquote>
|
||||
<sup>*</sup> For more information on the code signing requirements on the Apple Silicon, see <a href="https://developer.apple.com/documentation/macos-release-notes/macos-big-sur-11_0_1-universal-apps-release-notes#:~:text=New%20in%20macOS,pass%20through%20Gatekeeper">https://developer.apple.com/documentation/macos-release-notes/macos-big-sur-11_0_1-universal-apps-release-notes#:~:text=New%20in%20macOS,pass%20through%20Gatekeeper</a>. </p>
|
||||
<p>If you get an error that the application bundle is already signed, remove it before signing: <blockquote>
|
||||
<code>
|
||||
$ <strong>codesign</strong> --remove-signature TuxPaint.app
|
||||
</code>
|
||||
</blockquote>
|
||||
</p>
|
||||
<p>If you plan to combine the Apple Silicon bundle with the Intel CPU bundle to produce the Universal bundle, the code signing must be done after they are combined. See "Building a Universal Binary" below. </p>
|
||||
</section><!-- H3: Building for Apple Silicon -->
|
||||
|
||||
<section class="indent"><!-- H3: Building a Universal Binary -->
|
||||
<header>
|
||||
<h3>
|
||||
Building a Universal Binary </h3>
|
||||
Créer un Binaire Universel </h3>
|
||||
</header>
|
||||
|
||||
<p>
|
||||
To build Tux Paint as a Universal Binary, compile Tux Paint for the Intel CPU and the Apple Silicon separately first. Then rename the app bundle for the Intel CPU to TuxPaint-x86_64.app, and the bundle for the Apple Silicon to TuxPaint-arm64.app, copy the app bundle from the Intel machine to the Apple Silicon machine, then use the provided <code>build-universal.sh</code> script to combine the two application bundles as below. The produced bundle must be signed (see "Building for Apple Silicon" above for more details). The DMG file, if required, must be built after the signing: <blockquote>
|
||||
To build Tux Paint as a Universal Binary, compile Tux Paint for the Intel CPU and the Apple Silicon separately first. Then rename the app bundle for the Intel CPU to TuxPaint-x86_64.app, and the bundle for the Apple Silicon to TuxPaint-arm64.app, copy the app bundle from the Intel machine to the Apple Silicon machine, then use the provided <code>build-universal.sh</code> script to combine the two application bundles as below. The DMG file can be built afterwards: <blockquote>
|
||||
<code>
|
||||
$ <strong>macos/build-universal.sh</strong><br/>
|
||||
$ <strong>codesign</strong> -s - TuxPaint.app <br/>
|
||||
$ <strong>make</strong> TuxPaint.dmg
|
||||
</code>
|
||||
</blockquote>
|
||||
|
|
@ -1193,7 +1170,7 @@
|
|||
Prérequis </h3>
|
||||
</header>
|
||||
|
||||
<p>You will need recent versions of: <ul>
|
||||
<p>Vous avez besoin des versions récentes de : <ul>
|
||||
<li>
|
||||
<a href="https://gradle.org/">Gradle</a> — build automation tool </li>
|
||||
<li>
|
||||
|
|
@ -1216,7 +1193,7 @@
|
|||
<section class="indent"><!-- H3: Building -->
|
||||
<header>
|
||||
<h3>
|
||||
Building </h3>
|
||||
Construire </h3>
|
||||
</header>
|
||||
|
||||
<p>
|
||||
|
|
@ -1259,7 +1236,7 @@
|
|||
|
||||
<p>
|
||||
Install the required develop packages in Terminal: <dl>
|
||||
<dt>32-bit:</dt>
|
||||
<dt>32-bit :</dt>
|
||||
<dd>
|
||||
<code>
|
||||
<strong>pkgman</strong> install
|
||||
|
|
@ -1282,7 +1259,7 @@
|
|||
zlib_x86_devel
|
||||
</code>
|
||||
</dd>
|
||||
<dt>64-bit:</dt>
|
||||
<dt>64-bit :</dt>
|
||||
<dd>
|
||||
<code>
|
||||
<strong>pkgman</strong> install
|
||||
|
|
@ -1316,7 +1293,7 @@
|
|||
<section class="indent"><!-- H3: Building -->
|
||||
<header>
|
||||
<h3>
|
||||
Building </h3>
|
||||
Construire </h3>
|
||||
</header>
|
||||
<p>
|
||||
<code><strong>make</strong> PREFIX=/boot/home/config/non-packaged</code>
|
||||
|
|
@ -1326,7 +1303,7 @@
|
|||
<section class="indent"><!-- H3: Tux Paint Stamps -->
|
||||
<header>
|
||||
<h3>
|
||||
Tux Paint Stamps </h3>
|
||||
Tampons pour Tux Paint </h3>
|
||||
</header>
|
||||
<p>
|
||||
<code><strong>make</strong> install-all DATA_PREFIX=/boot/home/config/non-packaged/share/tuxpaint/</code>
|
||||
|
|
@ -1398,7 +1375,7 @@
|
|||
</header>
|
||||
|
||||
<p>
|
||||
Enlevez "<code>TuxPaint.app</code>" du dossier "Applications". Les fichiers de données les fichiers de configuration, les tampons et les images sauvegardées peuvent être trouvées dans "<code style="white-space: nowrap;">/Library/Application Support/TuxPaint</code>" (pour tous les utilisateurs) et "<code style="white-space: nowrap;">/Users/<i>USERNAME</i>/Library/Application Support/TuxPaint</code>" pour les utilisateurs individuels. </p>
|
||||
Enlevez "<code>TuxPaint.app</code>" du dossier "Applications". Les fichiers de données les fichiers de configuration, les tampons et les images sauvegardées peuvent être trouvées dans "<code style="white-space: nowrap;">/Bibliothèque/Support d'Application/Tux Paint</code>" (pour tous les utilisateurs) et "<code style="white-space: nowrap;">/Users/<i>USERNAME</i>/Library/Application Support/TuxPaint</code>" pour les utilisateurs individuels. </p>
|
||||
</section><!-- H2: macOS -->
|
||||
|
||||
<section class="indent"><!-- H2: Linux -->
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue