Sync EXTENDING docs after note styling
This commit is contained in:
parent
09756c3d51
commit
5fe0850827
18 changed files with 388 additions and 394 deletions
|
|
@ -36,7 +36,7 @@
|
|||
and other content used by Tux Paint, you can do so fairly easily by simply
|
||||
adding, changing, or removing files where Tux Paint looks for them.
|
||||
|
||||
Note: You'll need to re-launch Tux Paint for the changes to take effect.
|
||||
💡 Note: You'll need to re-launch Tux Paint for the changes to take effect.
|
||||
|
||||
Where Files Go
|
||||
|
||||
|
|
@ -87,7 +87,7 @@ Standard Files
|
|||
will make the content available to any user that launches
|
||||
this copy (icon) of Tux Paint.
|
||||
|
||||
Note: If you install a newer version of Tux Paint and replace or
|
||||
💡 Note: If you install a newer version of Tux Paint and replace or
|
||||
discard the old version, you will lose changes made by following
|
||||
the instructions above, so keep backups of your new content
|
||||
(stamps, brushes, etc.).
|
||||
|
|
@ -185,7 +185,7 @@ Brush Options
|
|||
Add a line containing the line "frames=N" to the brush's data
|
||||
file, where "N" is the number of frames in the brush.
|
||||
|
||||
Note: If you'd rather the frames be flipped through randomly,
|
||||
⚙ Note: If you'd rather the frames be flipped through randomly,
|
||||
rather than sequentially, also add a line containing "random" to
|
||||
the brush's data file.
|
||||
|
||||
|
|
@ -228,7 +228,7 @@ Brush Options
|
|||
Place the brush image PNGs (and any data text files) in the "brushes"
|
||||
directory.
|
||||
|
||||
Note: If your new brushes all come out as solid squares or rectangles,
|
||||
💡 Note: If your new brushes all come out as solid squares or rectangles,
|
||||
it's because you forgot to use alpha transparency! See the 'PNG
|
||||
documentation' in Tux Paint for more information and tips.
|
||||
|
||||
|
|
@ -255,17 +255,17 @@ Stamp Images
|
|||
SVGs are vector-based, and will be scaled appropriately for the canvas
|
||||
size being used in Tux Paint.
|
||||
|
||||
Note: If your new PNG-based stamps all come out as solid squares or
|
||||
💡 Note: If your new PNG-based stamps all come out as solid squares or
|
||||
rectangles, it's because you forgot to use alpha transparency! See the
|
||||
'PNG documentation' in Tux Paint for more information and tips.
|
||||
|
||||
Note: If your new SVG stamps seem to have a lot of whitespace, make sure
|
||||
💡 Note: If your new SVG stamps seem to have a lot of whitespace, make sure
|
||||
the SVG 'document' is no larger than the shape(s) within. If they are
|
||||
being clipped, make sure the 'document' is large enough to contain the
|
||||
shape(s). See the 'SVG documentation' in Tux Paint for more information
|
||||
and tips.
|
||||
|
||||
Advanced Users: The 'Advanced Stamps How-To' document describes, in
|
||||
⚙ Advanced Users: The 'Advanced Stamps How-To' document describes, in
|
||||
detail, how to make PNG images which will scale perfectly when used as
|
||||
stamps in Tux Paint.
|
||||
|
||||
|
|
@ -329,7 +329,7 @@ Stamp Sound Effects
|
|||
If no localized sound effect can be loaded, Tux Paint will attempt
|
||||
to load the 'default' sound file. (e.g., "stamp.wav")
|
||||
|
||||
Note: Also consider using descriptive sounds; see 'Stamp Descriptive
|
||||
💡 Note: Also consider using descriptive sounds; see 'Stamp Descriptive
|
||||
Sound', below.
|
||||
|
||||
Stamp Descriptive Sound
|
||||
|
|
@ -507,7 +507,7 @@ Pre-Mirrored and Flipped Stamps
|
|||
"_flip" in the name, and/or an image that is both mirrored and flipped, by
|
||||
naming it "_mirror_flip".
|
||||
|
||||
Note: If the user flips and mirrors an image, and a pre-drawn
|
||||
💡 Note: If the user flips and mirrors an image, and a pre-drawn
|
||||
"_mirror_flip" doesn't exist, but either "_flip" or "_mirror" does, it
|
||||
will be used, and mirrored or flipped, respectively.
|
||||
|
||||
|
|
@ -578,7 +578,7 @@ Scene-Style Starters
|
|||
in Tux Paint, the 'starter' images will appear in the screen that appears,
|
||||
after the various solid color choices.
|
||||
|
||||
Note: 'Starters' are 'attached' to saved pictures, via a small text file
|
||||
💡 Note: 'Starters' are 'attached' to saved pictures, via a small text file
|
||||
that has the same name as the saved file, but with ".dat" as the
|
||||
extension. This allows it to continue to affect the drawing even after Tux
|
||||
Paint has been quit, or another picture is loaded or a new image is
|
||||
|
|
@ -615,8 +615,8 @@ Scene-Style Starters
|
|||
in Tux Paint, the 'template' images will appear in the screen that
|
||||
appears, after the various solid color choices.
|
||||
|
||||
Note: 'Templates' are 'attached' to saved pictures, via a small text file
|
||||
that has the same name as the saved file, but with ".dat" as the
|
||||
💡 Note: 'Templates' are 'attached' to saved pictures, via a small text
|
||||
file that has the same name as the saved file, but with ".dat" as the
|
||||
extension. This allows it to continue to affect the drawing even after Tux
|
||||
Paint has been quit, or another picture is loaded or a new image is
|
||||
created. (In other words, if you base a drawing on a 'template' image, it
|
||||
|
|
@ -657,7 +657,7 @@ Scene-Style Starters
|
|||
* Virtraal
|
||||
* Lokalize
|
||||
|
||||
Note: It is best to always work off of the latest Tux Paint text catalog
|
||||
💡 Note: It is best to always work off of the latest Tux Paint text catalog
|
||||
template ("tuxpaint.pot"), since new text is added, and old text is
|
||||
occasionally changed. The text catalog for the upcoming, unreleased
|
||||
version of Tux Paint can be found in Tux Paint's Git repository (see:
|
||||
|
|
@ -676,7 +676,7 @@ Scene-Style Starters
|
|||
the Git source code repository so that you may commit your changes
|
||||
directly.
|
||||
|
||||
Note: Support for new locales requires making additions to Tux Paint's
|
||||
💡 Note: Support for new locales requires making additions to Tux Paint's
|
||||
source code ("/src/i18n.h" and "/src/i18n.c"), and requires updates to the
|
||||
Makefile, to ensure the ".po" files are compiled into ".mo" files, and
|
||||
available for use at runtime.
|
||||
|
|
@ -730,15 +730,15 @@ Scene-Style Starters
|
|||
30AD ki -
|
||||
30AE gi -
|
||||
|
||||
Note: Blank lines within the ".im" file will be ignored, as will any text
|
||||
following a "#" (pound/hash) character — it can be used to denote
|
||||
⚙ Note: Blank lines within the ".im" file will be ignored, as will any
|
||||
text following a "#" (pound/hash) character — it can be used to denote
|
||||
comments, as seen in the example above.
|
||||
|
||||
Note: Meanings of the flags are locale-specific, and are processed by the
|
||||
language-specific source code in "src/im.c". For example, "b" is used in
|
||||
Korean to handle Batchim, which may carry over to the next character.
|
||||
💡 Note: Meanings of the flags are locale-specific, and are processed by
|
||||
the language-specific source code in "src/im.c". For example, "b" is used
|
||||
in Korean to handle Batchim, which may carry over to the next character.
|
||||
|
||||
Note: Support for new input methods requires making additions to Tux
|
||||
💡 Note: Support for new input methods requires making additions to Tux
|
||||
Paint's source code ("/src/im.c"), and requires updates to the Makefile,
|
||||
to ensure the ".im" files are available for use at runtime.
|
||||
|
||||
|
|
@ -764,7 +764,7 @@ Layout overview file ("qwerty.layout")
|
|||
keysymdefs keysymdef.h
|
||||
keyboardlist qwerty.layout default.layout
|
||||
|
||||
Note: Blank lines within the ".layout" file will be ignored, as will any
|
||||
⚙ Note: Blank lines within the ".layout" file will be ignored, as will any
|
||||
text following a "#" (pound/hash) character — it can be used to denote
|
||||
comments, as seen in the example above.
|
||||
|
||||
|
|
@ -892,7 +892,7 @@ Keysym definitions file ("keysymdef.h")
|
|||
X Window System. It defines the Unicode values of each keycap (e.g.,
|
||||
"XK_equal" corresponds to "U+003D", for the character "=" ("EQUALS SIGN").
|
||||
|
||||
Note: This file is not compiled into Tux Paint, but is read and parsed at
|
||||
runtime.
|
||||
💡 Note: This file is not compiled into Tux Paint, but is read and parsed
|
||||
at runtime.
|
||||
|
||||
It is unlikely that any modification will be required of this file.
|
||||
|
|
|
|||
|
|
@ -128,12 +128,12 @@
|
|||
</table>
|
||||
</section>
|
||||
|
||||
<section>
|
||||
<section class="outer">
|
||||
<p>
|
||||
If you wish to add or change things like Brushes, Starters, Rubber Stamps, and other content used by Tux Paint, you can do so fairly easily by simply adding, changing, or removing files where Tux Paint looks for them. </p>
|
||||
|
||||
<p>
|
||||
Note: You'll need to re-launch Tux Paint for the changes to take effect. </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> You'll need to re-launch Tux Paint for the changes to take effect. </p>
|
||||
</section>
|
||||
|
||||
<section class="indent outer"><!-- H1: Where Files Go -->
|
||||
|
|
@ -195,8 +195,8 @@
|
|||
<li>
|
||||
There, you will find various sub-folders, such as "starters", "stamps", "brushes", etc. Adding new content to these folders will make the content available to any user that launches this copy (icon) of Tux Paint. </li>
|
||||
</ol>
|
||||
<p>
|
||||
<em>Note:</em> If you install a newer version of Tux Paint and replace or discard the old version, you will lose changes made by following the instructions above, so keep backups of your new content (stamps, brushes, etc.). </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <em>Note:</em> If you install a newer version of Tux Paint and replace or discard the old version, you will lose changes made by following the instructions above, so keep backups of your new content (stamps, brushes, etc.). </p>
|
||||
<p>
|
||||
Tux Paint also looks for files in a "TuxPaint" folder that you can place in your system's "Application Support" folder (found under "Library" at the root of your filesystem): <blockquote>
|
||||
<code style="white-space: nowrap;">/Library/Application Support/TuxPaint/</code>
|
||||
|
|
@ -313,8 +313,8 @@
|
|||
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>
|
||||
<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>
|
||||
<b>Note:</b> If you'd rather the frames be flipped through randomly, rather than sequentially, also add a line containing "<code><b>random</b></code>" to the brush's data file. </p>
|
||||
<p class="note">
|
||||
<span title="Configuration option">⚙</span> <strong>Note:</strong> If you'd rather the frames be flipped through randomly, rather than sequentially, also add a line containing "<code><b>random</b></code>" to the brush's data file. </p>
|
||||
</dd>
|
||||
|
||||
<dt><strong>Directional Brushes</strong></dt>
|
||||
|
|
@ -348,8 +348,8 @@
|
|||
<p>
|
||||
Place the brush image PNGs (and any data text files) in the "<code><b>brushes</b></code>" directory. </p>
|
||||
|
||||
<p>
|
||||
Note: If your new brushes all come out as solid squares or rectangles, it's because you forgot to use alpha transparency! See the 'PNG documentation' in Tux Paint for more information and tips. </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> If your new brushes all come out as solid squares or rectangles, it's because you forgot to use alpha transparency! See the 'PNG documentation' in Tux Paint for more information and tips. </p>
|
||||
</section><!-- H1: Brushes -->
|
||||
|
||||
<section class="indent outer"><!-- H1: Stamps -->
|
||||
|
|
@ -387,14 +387,14 @@
|
|||
<p>
|
||||
SVGs are vector-based, and will be scaled appropriately for the canvas size being used in Tux Paint. </p>
|
||||
|
||||
<p>
|
||||
Note: If your new PNG-based stamps all come out as solid squares or rectangles, it's because you forgot to use alpha transparency! See the 'PNG documentation' in Tux Paint for more information and tips. </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> If your new PNG-based stamps all come out as solid squares or rectangles, it's because you forgot to use alpha transparency! See the 'PNG documentation' in Tux Paint for more information and tips. </p>
|
||||
|
||||
<p>
|
||||
Note: If your new SVG stamps seem to have a lot of whitespace, make sure the SVG 'document' is no larger than the shape(s) within. If they are being clipped, make sure the 'document' is large enough to contain the shape(s). See the 'SVG documentation' in Tux Paint for more information and tips. </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> If your new SVG stamps seem to have a lot of whitespace, make sure the SVG 'document' is no larger than the shape(s) within. If they are being clipped, make sure the 'document' is large enough to contain the shape(s). See the 'SVG documentation' in Tux Paint for more information and tips. </p>
|
||||
|
||||
<p>
|
||||
<b>Advanced Users:</b> The 'Advanced Stamps How-To' document describes, in detail, how to make PNG images which will scale perfectly when used as stamps in Tux Paint. </p>
|
||||
<p class="note">
|
||||
<span title="Configuration option">⚙</span> <b>Advanced Users:</b> The 'Advanced Stamps How-To' document describes, in detail, how to make PNG images which will scale perfectly when used as stamps in Tux Paint. </p>
|
||||
</section><!-- H2: Stamp Images -->
|
||||
|
||||
<section><!-- H2: Stamp Descriptive Text -->
|
||||
|
|
@ -455,8 +455,8 @@
|
|||
</dd>
|
||||
</dl>
|
||||
|
||||
<p>
|
||||
Note: Also consider using descriptive sounds; see 'Stamp Descriptive Sound', below. </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> Also consider using descriptive sounds; see 'Stamp Descriptive Sound', below. </p>
|
||||
</section><!-- H2: Stamp Sound Effects -->
|
||||
|
||||
<section><!-- H2: Stamp Descriptive Sound -->
|
||||
|
|
@ -619,8 +619,8 @@
|
|||
<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>
|
||||
|
||||
<p>
|
||||
<b>Note:</b> 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>
|
||||
<p class="note">
|
||||
<span title="Information">💡</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>
|
||||
</section><!-- H2: Pre-Mirrored and Flipped Stamps -->
|
||||
</section><!-- H1: Stamps -->
|
||||
|
||||
|
|
@ -705,8 +705,8 @@
|
|||
<p>
|
||||
Place them in the "<code><b>starters</b></code>" directory. When the 'New' dialog is accessed in Tux Paint, the 'starter' images will appear in the screen that appears, after the various solid color choices. </p>
|
||||
|
||||
<p>
|
||||
<b>Note:</b> 'Starters' are 'attached' to saved pictures, via a small text file that has the same name as the saved file, but with "<code>.dat</code>" as the extension. This allows it to continue to affect the drawing even after Tux Paint has been quit, or another picture is loaded or a new image is created. (In other words, if you base a drawing on a 'starter' image, it will always be affected by it.) </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> 'Starters' are 'attached' to saved pictures, via a small text file that has the same name as the saved file, but with "<code>.dat</code>" as the extension. This allows it to continue to affect the drawing even after Tux Paint has been quit, or another picture is loaded or a new image is created. (In other words, if you base a drawing on a 'starter' image, it will always be affected by it.) </p>
|
||||
</section><!-- H1: Starters -->
|
||||
|
||||
<section class="indent outer"><!-- H1: 'Templates' -->
|
||||
|
|
@ -740,8 +740,8 @@
|
|||
<p>
|
||||
Place them in the "<code><b>templates</b></code>" directory. When the 'New' dialog is accessed in Tux Paint, the 'template' images will appear in the screen that appears, after the various solid color choices. </p>
|
||||
|
||||
<p>
|
||||
<b>Note:</b> 'Templates' are 'attached' to saved pictures, via a small text file that has the same name as the saved file, but with "<code>.dat</code>" as the extension. This allows it to continue to affect the drawing even after Tux Paint has been quit, or another picture is loaded or a new image is created. (In other words, if you base a drawing on a 'template' image, it will always be affected by it.) </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> 'Templates' are 'attached' to saved pictures, via a small text file that has the same name as the saved file, but with "<code>.dat</code>" as the extension. This allows it to continue to affect the drawing even after Tux Paint has been quit, or another picture is loaded or a new image is created. (In other words, if you base a drawing on a 'template' image, it will always be affected by it.) </p>
|
||||
<br clear="all">
|
||||
</section><!-- H1: 'Templates' -->
|
||||
|
||||
|
|
@ -782,8 +782,8 @@
|
|||
</ul>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
<i>Note:</i> It is best to always work off of the <i>latest</i> Tux Paint text catalog template ("<code>tuxpaint.pot</code>"), since new text is added, and old text is occasionally changed. The text catalog for the upcoming, unreleased version of Tux Paint can be found in Tux Paint's Git repository (see: <a href="https://tuxpaint.org/download/source/git/">https://tuxpaint.org/download/source/git/</a>), and on the Tux Paint website at <a href="https://tuxpaint.org/help/po/">https://tuxpaint.org/help/po/</a>. </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> It is best to always work off of the <i>latest</i> Tux Paint text catalog template ("<code>tuxpaint.pot</code>"), since new text is added, and old text is occasionally changed. The text catalog for the upcoming, unreleased version of Tux Paint can be found in Tux Paint's Git repository (see: <a href="https://tuxpaint.org/download/source/git/">https://tuxpaint.org/download/source/git/</a>), and on the Tux Paint website at <a href="https://tuxpaint.org/help/po/">https://tuxpaint.org/help/po/</a>. </p>
|
||||
|
||||
<p>
|
||||
To edit an existing translation, download the latest "<code>.po</code>" file for that language, and edit it as described above. </p>
|
||||
|
|
@ -794,8 +794,8 @@
|
|||
<p>
|
||||
Alternatively, if you have an account with <a href="http://www.sourceforge.net/">SourceForge.net</a>, you can request to be added to the "<code>tuxpaint</code>" project and receive write-access to the Git source code repository so that you may commit your changes directly. </p>
|
||||
|
||||
<p>
|
||||
<i>Note:</i> Support for new locales requires making additions to Tux Paint's source code ("<code>/src/i18n.h</code>" and "<code>/src/i18n.c</code>"), and requires updates to the <code>Makefile</code>, to ensure the "<code>.po</code>" files are compiled into "<code>.mo</code>" files, and available for use at runtime. </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> Support for new locales requires making additions to Tux Paint's source code ("<code>/src/i18n.h</code>" and "<code>/src/i18n.c</code>"), and requires updates to the <code>Makefile</code>, to ensure the "<code>.po</code>" files are compiled into "<code>.mo</code>" files, and available for use at runtime. </p>
|
||||
</section><!-- H1: Translations -->
|
||||
|
||||
<section class="indent outer"><!-- H1: Alternative Input Methods -->
|
||||
|
|
@ -849,14 +849,14 @@
|
|||
</blockquote>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
<i>Note:</i> Blank lines within the "<code>.im</code>" file will be ignored, as will any text following a "<code>#</code>" (pound/hash) character — it can be used to denote comments, as seen in the example above. </p>
|
||||
<p class="note">
|
||||
<span title="Configuration option">⚙</span> <strong>Note:</strong> Blank lines within the "<code>.im</code>" file will be ignored, as will any text following a "<code>#</code>" (pound/hash) character — it can be used to denote comments, as seen in the example above. </p>
|
||||
|
||||
<p>
|
||||
<i>Note:</i> Meanings of the flags are locale-specific, and are processed by the language-specific source code in "<code>src/im.c</code>". For example, "<code>b</code>" is used in Korean to handle Batchim, which may carry over to the next character. </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> Meanings of the flags are locale-specific, and are processed by the language-specific source code in "<code>src/im.c</code>". For example, "<code>b</code>" is used in Korean to handle Batchim, which may carry over to the next character. </p>
|
||||
|
||||
<p>
|
||||
<i>Note:</i> Support for new input methods requires making additions to Tux Paint's source code ("<code>/src/im.c</code>"), and requires updates to the <code>Makefile</code>, to ensure the "<code>.im</code>" files are available for use at runtime. </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> Support for new input methods requires making additions to Tux Paint's source code ("<code>/src/im.c</code>"), and requires updates to the <code>Makefile</code>, to ensure the "<code>.im</code>" files are available for use at runtime. </p>
|
||||
</section><!-- H1: Alternative Input Methods -->
|
||||
|
||||
<section class="indent outer"><!-- H1: On-screen Keyboard -->
|
||||
|
|
@ -891,8 +891,8 @@
|
|||
</p>
|
||||
</blockquote>
|
||||
|
||||
<p>
|
||||
<i>Note:</i> Blank lines within the "<code>.layout</code>" file will be ignored, as will any text following a "<code>#</code>" (pound/hash) character — it can be used to denote comments, as seen in the example above. </p>
|
||||
<p class="note">
|
||||
<span title="Configuration option">⚙</span> <strong>Note:</strong> Blank lines within the "<code>.layout</code>" file will be ignored, as will any text following a "<code>#</code>" (pound/hash) character — it can be used to denote comments, as seen in the example above. </p>
|
||||
|
||||
<p>
|
||||
The "<code>keyboardlist</code>" line describes which layouts to switch to, when the user clicks the left and right buttons on the keyboard. (See below.) </p>
|
||||
|
|
@ -1046,8 +1046,8 @@
|
|||
<p>
|
||||
This file (which is a <cite>C</cite> programming language header file) is also from the <cite>X Window System</cite>. It defines the Unicode values of each keycap (e.g., "<code>XK_equal</code>" corresponds to "<code>U+003D</code>", for the character "<code>=</code>" ("<code>EQUALS SIGN</code>"). </p>
|
||||
|
||||
<p>
|
||||
<b>Note:</b> This file is not compiled into Tux Paint, but is read and parsed at runtime. </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> This file is not compiled into Tux Paint, but is read and parsed at runtime. </p>
|
||||
|
||||
<p>
|
||||
It is unlikely that any modification will be required of this file. </p>
|
||||
|
|
|
|||
|
|
@ -36,7 +36,7 @@
|
|||
and other content used by Tux Paint, you can do so fairly easily by simply
|
||||
adding, changing, or removing files where Tux Paint looks for them.
|
||||
|
||||
Note: You'll need to re-launch Tux Paint for the changes to take effect.
|
||||
💡 Note: You'll need to re-launch Tux Paint for the changes to take effect.
|
||||
|
||||
Where Files Go
|
||||
|
||||
|
|
@ -87,7 +87,7 @@ Standard Files
|
|||
will make the content available to any user that launches
|
||||
this copy (icon) of Tux Paint.
|
||||
|
||||
Note: If you install a newer version of Tux Paint and replace or
|
||||
💡 Note: If you install a newer version of Tux Paint and replace or
|
||||
discard the old version, you will lose changes made by following
|
||||
the instructions above, so keep backups of your new content
|
||||
(stamps, brushes, etc.).
|
||||
|
|
@ -185,7 +185,7 @@ Brush Options
|
|||
Add a line containing the line "frames=N" to the brush's data
|
||||
file, where "N" is the number of frames in the brush.
|
||||
|
||||
Note: If you'd rather the frames be flipped through randomly,
|
||||
⚙ Note: If you'd rather the frames be flipped through randomly,
|
||||
rather than sequentially, also add a line containing "random" to
|
||||
the brush's data file.
|
||||
|
||||
|
|
@ -228,7 +228,7 @@ Brush Options
|
|||
Place the brush image PNGs (and any data text files) in the "brushes"
|
||||
directory.
|
||||
|
||||
Note: If your new brushes all come out as solid squares or rectangles,
|
||||
💡 Note: If your new brushes all come out as solid squares or rectangles,
|
||||
it's because you forgot to use alpha transparency! See the 'PNG
|
||||
documentation' in Tux Paint for more information and tips.
|
||||
|
||||
|
|
@ -255,17 +255,17 @@ Stamp Images
|
|||
SVGs are vector-based, and will be scaled appropriately for the canvas
|
||||
size being used in Tux Paint.
|
||||
|
||||
Note: If your new PNG-based stamps all come out as solid squares or
|
||||
💡 Note: If your new PNG-based stamps all come out as solid squares or
|
||||
rectangles, it's because you forgot to use alpha transparency! See the
|
||||
'PNG documentation' in Tux Paint for more information and tips.
|
||||
|
||||
Note: If your new SVG stamps seem to have a lot of whitespace, make sure
|
||||
💡 Note: If your new SVG stamps seem to have a lot of whitespace, make sure
|
||||
the SVG 'document' is no larger than the shape(s) within. If they are
|
||||
being clipped, make sure the 'document' is large enough to contain the
|
||||
shape(s). See the 'SVG documentation' in Tux Paint for more information
|
||||
and tips.
|
||||
|
||||
Advanced Users: The 'Advanced Stamps How-To' document describes, in
|
||||
⚙ Advanced Users: The 'Advanced Stamps How-To' document describes, in
|
||||
detail, how to make PNG images which will scale perfectly when used as
|
||||
stamps in Tux Paint.
|
||||
|
||||
|
|
@ -329,7 +329,7 @@ Stamp Sound Effects
|
|||
If no localized sound effect can be loaded, Tux Paint will attempt
|
||||
to load the 'default' sound file. (e.g., "stamp.wav")
|
||||
|
||||
Note: Also consider using descriptive sounds; see 'Stamp Descriptive
|
||||
💡 Note: Also consider using descriptive sounds; see 'Stamp Descriptive
|
||||
Sound', below.
|
||||
|
||||
Stamp Descriptive Sound
|
||||
|
|
@ -507,7 +507,7 @@ Pre-Mirrored and Flipped Stamps
|
|||
"_flip" in the name, and/or an image that is both mirrored and flipped, by
|
||||
naming it "_mirror_flip".
|
||||
|
||||
Note: If the user flips and mirrors an image, and a pre-drawn
|
||||
💡 Note: If the user flips and mirrors an image, and a pre-drawn
|
||||
"_mirror_flip" doesn't exist, but either "_flip" or "_mirror" does, it
|
||||
will be used, and mirrored or flipped, respectively.
|
||||
|
||||
|
|
@ -578,7 +578,7 @@ Scene-Style Starters
|
|||
in Tux Paint, the 'starter' images will appear in the screen that appears,
|
||||
after the various solid color choices.
|
||||
|
||||
Note: 'Starters' are 'attached' to saved pictures, via a small text file
|
||||
💡 Note: 'Starters' are 'attached' to saved pictures, via a small text file
|
||||
that has the same name as the saved file, but with ".dat" as the
|
||||
extension. This allows it to continue to affect the drawing even after Tux
|
||||
Paint has been quit, or another picture is loaded or a new image is
|
||||
|
|
@ -615,8 +615,8 @@ Scene-Style Starters
|
|||
in Tux Paint, the 'template' images will appear in the screen that
|
||||
appears, after the various solid color choices.
|
||||
|
||||
Note: 'Templates' are 'attached' to saved pictures, via a small text file
|
||||
that has the same name as the saved file, but with ".dat" as the
|
||||
💡 Note: 'Templates' are 'attached' to saved pictures, via a small text
|
||||
file that has the same name as the saved file, but with ".dat" as the
|
||||
extension. This allows it to continue to affect the drawing even after Tux
|
||||
Paint has been quit, or another picture is loaded or a new image is
|
||||
created. (In other words, if you base a drawing on a 'template' image, it
|
||||
|
|
@ -657,7 +657,7 @@ Scene-Style Starters
|
|||
* Virtraal
|
||||
* Lokalize
|
||||
|
||||
Note: It is best to always work off of the latest Tux Paint text catalog
|
||||
💡 Note: It is best to always work off of the latest Tux Paint text catalog
|
||||
template ("tuxpaint.pot"), since new text is added, and old text is
|
||||
occasionally changed. The text catalog for the upcoming, unreleased
|
||||
version of Tux Paint can be found in Tux Paint's Git repository (see:
|
||||
|
|
@ -676,7 +676,7 @@ Scene-Style Starters
|
|||
the Git source code repository so that you may commit your changes
|
||||
directly.
|
||||
|
||||
Note: Support for new locales requires making additions to Tux Paint's
|
||||
💡 Note: Support for new locales requires making additions to Tux Paint's
|
||||
source code ("/src/i18n.h" and "/src/i18n.c"), and requires updates to the
|
||||
Makefile, to ensure the ".po" files are compiled into ".mo" files, and
|
||||
available for use at runtime.
|
||||
|
|
@ -730,15 +730,15 @@ Scene-Style Starters
|
|||
30AD ki -
|
||||
30AE gi -
|
||||
|
||||
Note: Blank lines within the ".im" file will be ignored, as will any text
|
||||
following a "#" (pound/hash) character — it can be used to denote
|
||||
⚙ Note: Blank lines within the ".im" file will be ignored, as will any
|
||||
text following a "#" (pound/hash) character — it can be used to denote
|
||||
comments, as seen in the example above.
|
||||
|
||||
Note: Meanings of the flags are locale-specific, and are processed by the
|
||||
language-specific source code in "src/im.c". For example, "b" is used in
|
||||
Korean to handle Batchim, which may carry over to the next character.
|
||||
💡 Note: Meanings of the flags are locale-specific, and are processed by
|
||||
the language-specific source code in "src/im.c". For example, "b" is used
|
||||
in Korean to handle Batchim, which may carry over to the next character.
|
||||
|
||||
Note: Support for new input methods requires making additions to Tux
|
||||
💡 Note: Support for new input methods requires making additions to Tux
|
||||
Paint's source code ("/src/im.c"), and requires updates to the Makefile,
|
||||
to ensure the ".im" files are available for use at runtime.
|
||||
|
||||
|
|
@ -764,7 +764,7 @@ Layout overview file ("qwerty.layout")
|
|||
keysymdefs keysymdef.h
|
||||
keyboardlist qwerty.layout default.layout
|
||||
|
||||
Note: Blank lines within the ".layout" file will be ignored, as will any
|
||||
⚙ Note: Blank lines within the ".layout" file will be ignored, as will any
|
||||
text following a "#" (pound/hash) character — it can be used to denote
|
||||
comments, as seen in the example above.
|
||||
|
||||
|
|
@ -892,7 +892,7 @@ Keysym definitions file ("keysymdef.h")
|
|||
X Window System. It defines the Unicode values of each keycap (e.g.,
|
||||
"XK_equal" corresponds to "U+003D", for the character "=" ("EQUALS SIGN").
|
||||
|
||||
Note: This file is not compiled into Tux Paint, but is read and parsed at
|
||||
runtime.
|
||||
💡 Note: This file is not compiled into Tux Paint, but is read and parsed
|
||||
at runtime.
|
||||
|
||||
It is unlikely that any modification will be required of this file.
|
||||
|
|
|
|||
|
|
@ -54,7 +54,7 @@
|
|||
padding-bottom: 1em;
|
||||
border-bottom: 2px solid #000;
|
||||
}
|
||||
section.indent p,dl {
|
||||
section.indent p,dl,ul {
|
||||
margin-left: 2em;
|
||||
}
|
||||
section.indent dl p {
|
||||
|
|
@ -128,12 +128,12 @@
|
|||
</table>
|
||||
</section>
|
||||
|
||||
<section>
|
||||
<section class="outer">
|
||||
<p>
|
||||
If you wish to add or change things like Brushes, Starters, Rubber Stamps, and other content used by Tux Paint, you can do so fairly easily by simply adding, changing, or removing files where Tux Paint looks for them. </p>
|
||||
|
||||
<p>
|
||||
Note: You'll need to re-launch Tux Paint for the changes to take effect. </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> You'll need to re-launch Tux Paint for the changes to take effect. </p>
|
||||
</section>
|
||||
|
||||
<section class="indent outer"><!-- H1: Where Files Go -->
|
||||
|
|
@ -195,8 +195,8 @@
|
|||
<li>
|
||||
There, you will find various sub-folders, such as "starters", "stamps", "brushes", etc. Adding new content to these folders will make the content available to any user that launches this copy (icon) of Tux Paint. </li>
|
||||
</ol>
|
||||
<p>
|
||||
<em>Note:</em> If you install a newer version of Tux Paint and replace or discard the old version, you will lose changes made by following the instructions above, so keep backups of your new content (stamps, brushes, etc.). </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <em>Note:</em> If you install a newer version of Tux Paint and replace or discard the old version, you will lose changes made by following the instructions above, so keep backups of your new content (stamps, brushes, etc.). </p>
|
||||
<p>
|
||||
Tux Paint also looks for files in a "TuxPaint" folder that you can place in your system's "Application Support" folder (found under "Library" at the root of your filesystem): <blockquote>
|
||||
<code style="white-space: nowrap;">/Library/Application Support/TuxPaint/</code>
|
||||
|
|
@ -313,8 +313,8 @@
|
|||
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>
|
||||
<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>
|
||||
<b>Note:</b> If you'd rather the frames be flipped through randomly, rather than sequentially, also add a line containing "<code><b>random</b></code>" to the brush's data file. </p>
|
||||
<p class="note">
|
||||
<span title="Configuration option">⚙</span> <strong>Note:</strong> If you'd rather the frames be flipped through randomly, rather than sequentially, also add a line containing "<code><b>random</b></code>" to the brush's data file. </p>
|
||||
</dd>
|
||||
|
||||
<dt><strong>Directional Brushes</strong></dt>
|
||||
|
|
@ -348,8 +348,8 @@
|
|||
<p>
|
||||
Place the brush image PNGs (and any data text files) in the "<code><b>brushes</b></code>" directory. </p>
|
||||
|
||||
<p>
|
||||
Note: If your new brushes all come out as solid squares or rectangles, it's because you forgot to use alpha transparency! See the 'PNG documentation' in Tux Paint for more information and tips. </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> If your new brushes all come out as solid squares or rectangles, it's because you forgot to use alpha transparency! See the 'PNG documentation' in Tux Paint for more information and tips. </p>
|
||||
</section><!-- H1: Brushes -->
|
||||
|
||||
<section class="indent outer"><!-- H1: Stamps -->
|
||||
|
|
@ -387,14 +387,14 @@
|
|||
<p>
|
||||
SVGs are vector-based, and will be scaled appropriately for the canvas size being used in Tux Paint. </p>
|
||||
|
||||
<p>
|
||||
Note: If your new PNG-based stamps all come out as solid squares or rectangles, it's because you forgot to use alpha transparency! See the 'PNG documentation' in Tux Paint for more information and tips. </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> If your new PNG-based stamps all come out as solid squares or rectangles, it's because you forgot to use alpha transparency! See the 'PNG documentation' in Tux Paint for more information and tips. </p>
|
||||
|
||||
<p>
|
||||
Note: If your new SVG stamps seem to have a lot of whitespace, make sure the SVG 'document' is no larger than the shape(s) within. If they are being clipped, make sure the 'document' is large enough to contain the shape(s). See the 'SVG documentation' in Tux Paint for more information and tips. </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> If your new SVG stamps seem to have a lot of whitespace, make sure the SVG 'document' is no larger than the shape(s) within. If they are being clipped, make sure the 'document' is large enough to contain the shape(s). See the 'SVG documentation' in Tux Paint for more information and tips. </p>
|
||||
|
||||
<p>
|
||||
<b>Advanced Users:</b> The 'Advanced Stamps How-To' document describes, in detail, how to make PNG images which will scale perfectly when used as stamps in Tux Paint. </p>
|
||||
<p class="note">
|
||||
<span title="Configuration option">⚙</span> <b>Advanced Users:</b> The 'Advanced Stamps How-To' document describes, in detail, how to make PNG images which will scale perfectly when used as stamps in Tux Paint. </p>
|
||||
</section><!-- H2: Stamp Images -->
|
||||
|
||||
<section><!-- H2: Stamp Descriptive Text -->
|
||||
|
|
@ -455,8 +455,8 @@
|
|||
</dd>
|
||||
</dl>
|
||||
|
||||
<p>
|
||||
Note: Also consider using descriptive sounds; see 'Stamp Descriptive Sound', below. </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> Also consider using descriptive sounds; see 'Stamp Descriptive Sound', below. </p>
|
||||
</section><!-- H2: Stamp Sound Effects -->
|
||||
|
||||
<section><!-- H2: Stamp Descriptive Sound -->
|
||||
|
|
@ -619,8 +619,8 @@
|
|||
<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>
|
||||
|
||||
<p>
|
||||
<b>Note:</b> 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>
|
||||
<p class="note">
|
||||
<span title="Information">💡</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>
|
||||
</section><!-- H2: Pre-Mirrored and Flipped Stamps -->
|
||||
</section><!-- H1: Stamps -->
|
||||
|
||||
|
|
@ -705,8 +705,8 @@
|
|||
<p>
|
||||
Place them in the "<code><b>starters</b></code>" directory. When the 'New' dialog is accessed in Tux Paint, the 'starter' images will appear in the screen that appears, after the various solid color choices. </p>
|
||||
|
||||
<p>
|
||||
<b>Note:</b> 'Starters' are 'attached' to saved pictures, via a small text file that has the same name as the saved file, but with "<code>.dat</code>" as the extension. This allows it to continue to affect the drawing even after Tux Paint has been quit, or another picture is loaded or a new image is created. (In other words, if you base a drawing on a 'starter' image, it will always be affected by it.) </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> 'Starters' are 'attached' to saved pictures, via a small text file that has the same name as the saved file, but with "<code>.dat</code>" as the extension. This allows it to continue to affect the drawing even after Tux Paint has been quit, or another picture is loaded or a new image is created. (In other words, if you base a drawing on a 'starter' image, it will always be affected by it.) </p>
|
||||
</section><!-- H1: Starters -->
|
||||
|
||||
<section class="indent outer"><!-- H1: 'Templates' -->
|
||||
|
|
@ -740,8 +740,8 @@
|
|||
<p>
|
||||
Place them in the "<code><b>templates</b></code>" directory. When the 'New' dialog is accessed in Tux Paint, the 'template' images will appear in the screen that appears, after the various solid color choices. </p>
|
||||
|
||||
<p>
|
||||
<b>Note:</b> 'Templates' are 'attached' to saved pictures, via a small text file that has the same name as the saved file, but with "<code>.dat</code>" as the extension. This allows it to continue to affect the drawing even after Tux Paint has been quit, or another picture is loaded or a new image is created. (In other words, if you base a drawing on a 'template' image, it will always be affected by it.) </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> 'Templates' are 'attached' to saved pictures, via a small text file that has the same name as the saved file, but with "<code>.dat</code>" as the extension. This allows it to continue to affect the drawing even after Tux Paint has been quit, or another picture is loaded or a new image is created. (In other words, if you base a drawing on a 'template' image, it will always be affected by it.) </p>
|
||||
<br clear="all">
|
||||
</section><!-- H1: 'Templates' -->
|
||||
|
||||
|
|
@ -782,8 +782,8 @@
|
|||
</ul>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
<i>Note:</i> It is best to always work off of the <i>latest</i> Tux Paint text catalog template ("<code>tuxpaint.pot</code>"), since new text is added, and old text is occasionally changed. The text catalog for the upcoming, unreleased version of Tux Paint can be found in Tux Paint's Git repository (see: <a href="https://tuxpaint.org/download/source/git/">https://tuxpaint.org/download/source/git/</a>), and on the Tux Paint website at <a href="https://tuxpaint.org/help/po/">https://tuxpaint.org/help/po/</a>. </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> It is best to always work off of the <i>latest</i> Tux Paint text catalog template ("<code>tuxpaint.pot</code>"), since new text is added, and old text is occasionally changed. The text catalog for the upcoming, unreleased version of Tux Paint can be found in Tux Paint's Git repository (see: <a href="https://tuxpaint.org/download/source/git/">https://tuxpaint.org/download/source/git/</a>), and on the Tux Paint website at <a href="https://tuxpaint.org/help/po/">https://tuxpaint.org/help/po/</a>. </p>
|
||||
|
||||
<p>
|
||||
To edit an existing translation, download the latest "<code>.po</code>" file for that language, and edit it as described above. </p>
|
||||
|
|
@ -794,8 +794,8 @@
|
|||
<p>
|
||||
Alternatively, if you have an account with <a href="http://www.sourceforge.net/">SourceForge.net</a>, you can request to be added to the "<code>tuxpaint</code>" project and receive write-access to the Git source code repository so that you may commit your changes directly. </p>
|
||||
|
||||
<p>
|
||||
<i>Note:</i> Support for new locales requires making additions to Tux Paint's source code ("<code>/src/i18n.h</code>" and "<code>/src/i18n.c</code>"), and requires updates to the <code>Makefile</code>, to ensure the "<code>.po</code>" files are compiled into "<code>.mo</code>" files, and available for use at runtime. </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> Support for new locales requires making additions to Tux Paint's source code ("<code>/src/i18n.h</code>" and "<code>/src/i18n.c</code>"), and requires updates to the <code>Makefile</code>, to ensure the "<code>.po</code>" files are compiled into "<code>.mo</code>" files, and available for use at runtime. </p>
|
||||
</section><!-- H1: Translations -->
|
||||
|
||||
<section class="indent outer"><!-- H1: Alternative Input Methods -->
|
||||
|
|
@ -849,14 +849,14 @@
|
|||
</blockquote>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
<i>Note:</i> Blank lines within the "<code>.im</code>" file will be ignored, as will any text following a "<code>#</code>" (pound/hash) character — it can be used to denote comments, as seen in the example above. </p>
|
||||
<p class="note">
|
||||
<span title="Configuration option">⚙</span> <strong>Note:</strong> Blank lines within the "<code>.im</code>" file will be ignored, as will any text following a "<code>#</code>" (pound/hash) character — it can be used to denote comments, as seen in the example above. </p>
|
||||
|
||||
<p>
|
||||
<i>Note:</i> Meanings of the flags are locale-specific, and are processed by the language-specific source code in "<code>src/im.c</code>". For example, "<code>b</code>" is used in Korean to handle Batchim, which may carry over to the next character. </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> Meanings of the flags are locale-specific, and are processed by the language-specific source code in "<code>src/im.c</code>". For example, "<code>b</code>" is used in Korean to handle Batchim, which may carry over to the next character. </p>
|
||||
|
||||
<p>
|
||||
<i>Note:</i> Support for new input methods requires making additions to Tux Paint's source code ("<code>/src/im.c</code>"), and requires updates to the <code>Makefile</code>, to ensure the "<code>.im</code>" files are available for use at runtime. </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> Support for new input methods requires making additions to Tux Paint's source code ("<code>/src/im.c</code>"), and requires updates to the <code>Makefile</code>, to ensure the "<code>.im</code>" files are available for use at runtime. </p>
|
||||
</section><!-- H1: Alternative Input Methods -->
|
||||
|
||||
<section class="indent outer"><!-- H1: On-screen Keyboard -->
|
||||
|
|
@ -891,8 +891,8 @@
|
|||
</p>
|
||||
</blockquote>
|
||||
|
||||
<p>
|
||||
<i>Note:</i> Blank lines within the "<code>.layout</code>" file will be ignored, as will any text following a "<code>#</code>" (pound/hash) character — it can be used to denote comments, as seen in the example above. </p>
|
||||
<p class="note">
|
||||
<span title="Configuration option">⚙</span> <strong>Note:</strong> Blank lines within the "<code>.layout</code>" file will be ignored, as will any text following a "<code>#</code>" (pound/hash) character — it can be used to denote comments, as seen in the example above. </p>
|
||||
|
||||
<p>
|
||||
The "<code>keyboardlist</code>" line describes which layouts to switch to, when the user clicks the left and right buttons on the keyboard. (See below.) </p>
|
||||
|
|
@ -1046,8 +1046,8 @@
|
|||
<p>
|
||||
This file (which is a <cite>C</cite> programming language header file) is also from the <cite>X Window System</cite>. It defines the Unicode values of each keycap (e.g., "<code>XK_equal</code>" corresponds to "<code>U+003D</code>", for the character "<code>=</code>" ("<code>EQUALS SIGN</code>"). </p>
|
||||
|
||||
<p>
|
||||
<b>Note:</b> This file is not compiled into Tux Paint, but is read and parsed at runtime. </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> This file is not compiled into Tux Paint, but is read and parsed at runtime. </p>
|
||||
|
||||
<p>
|
||||
It is unlikely that any modification will be required of this file. </p>
|
||||
|
|
|
|||
|
|
@ -54,7 +54,7 @@
|
|||
padding-bottom: 1em;
|
||||
border-bottom: 2px solid #000;
|
||||
}
|
||||
section.indent p,dl {
|
||||
section.indent p,dl,ul {
|
||||
margin-left: 2em;
|
||||
}
|
||||
section.indent dl p {
|
||||
|
|
|
|||
|
|
@ -54,7 +54,7 @@
|
|||
padding-bottom: 1em;
|
||||
border-bottom: 2px solid #000;
|
||||
}
|
||||
section.indent p,dl {
|
||||
section.indent p,dl,ul {
|
||||
margin-left: 2em;
|
||||
}
|
||||
section.indent dl p {
|
||||
|
|
|
|||
|
|
@ -38,8 +38,7 @@
|
|||
ajoutant, modifiant ou supprimant simplement des fichiers là où Tux Paint
|
||||
les recherche.
|
||||
|
||||
Remarque: vous devrez redémarrer Tux Paint pour que les modifications
|
||||
prennent effet.
|
||||
💡 Note: You'll need to re-launch Tux Paint for the changes to take effect.
|
||||
|
||||
Où vont les fichiers
|
||||
|
||||
|
|
@ -93,11 +92,11 @@ Fichiers standards
|
|||
dossiers rendra celui-ci disponible pour tout utilisateur qui
|
||||
lance cette copie (icône) de Tux Paint .
|
||||
|
||||
Remarque : Si vous installez une version plus récente de Tux Paint
|
||||
et remplacez ou supprimez l'ancienne version, vous perdrez les
|
||||
modifications apportées avec les instructions ci-dessus, faites
|
||||
donc des sauvegardes de votre nouveau contenu (tampons,pinceaux,
|
||||
etc.).
|
||||
💡 Remarque : Si vous installez une version plus récente de Tux
|
||||
Paint et remplacez ou supprimez l'ancienne version, vous perdrez
|
||||
les modifications apportées avec les instructions ci-dessus,
|
||||
faites donc des sauvegardes de votre nouveau contenu
|
||||
(tampons,pinceaux, etc.).
|
||||
|
||||
Tux Paint recherche également les fichiers dans un dossier "Tux
|
||||
Paint" que vous pouvez placer dans votre dossier système
|
||||
|
|
@ -201,9 +200,9 @@ Options de pinceau
|
|||
Ajoutez une ligne contenant la ligne "frames=N" au fichier de
|
||||
données du pinceau, où"N" est le nombre d'images dans le pinceau.
|
||||
|
||||
Remarque : si vous préférez que les images apparaissent de manière
|
||||
aléatoire plutôt que séquentielle, ajoutez en plus une ligne
|
||||
contenant "random" au fichier de données du pinceau.
|
||||
⚙ Note: If you'd rather the frames be flipped through randomly,
|
||||
rather than sequentially, also add a line containing "random" to
|
||||
the brush's data file.
|
||||
|
||||
Pinceaux directionnels
|
||||
|
||||
|
|
@ -249,10 +248,9 @@ Options de pinceau
|
|||
Placez les PNG de l'image du pinceau (et tous les fichiers texte de
|
||||
données) dans le répertoire "brushes".
|
||||
|
||||
Remarque: si vos nouveaux pinceaux se présentent tous sous forme de carrés
|
||||
ou de rectangles pleins, c'est que vous avez oublié d'utiliser la
|
||||
transparence alpha ! Consultez le fichier de documentation "PNG" pour plus
|
||||
d'informations et de conseils.
|
||||
💡 Note: If your new pinceaux all come out as solid squares or rectangles,
|
||||
it's because you forgot to use alpha transparency! See the 'PNG
|
||||
documentation' in Tux Paint for more information and tips.
|
||||
|
||||
Tampons
|
||||
|
||||
|
|
@ -281,19 +279,18 @@ Images des tampons
|
|||
Les SVG sont basés sur des vecteurs et seront mis à l'échelle de manière
|
||||
adéquate pour le canevas utilisé.
|
||||
|
||||
Remarque: si vos nouveaux des tampons basés sur PNG se présentent tous
|
||||
sous forme de carrés ou de rectangles pleins, c'est que vous avez oublié
|
||||
d'utiliser la transparence alpha ! Consultez le fichier de documentation
|
||||
"PNG" pour plus d'informations et de conseils.
|
||||
💡 Note: If your new des tampons basés sur PNG all come out as solid
|
||||
squares or rectangles, it's because you forgot to use alpha transparency!
|
||||
See the 'PNG documentation' in Tux Paint for more information and tips.
|
||||
|
||||
Remarque: si vos nouveaux tampons SVG semblent avoir beaucoup de zones
|
||||
vides, assurez-vous que le «document» SVG n'est pas plus grand que la ou
|
||||
les formes qu'il contient. S'ils sont coupés, assurez-vous que le
|
||||
«document» est suffisamment grand pour contenir la ou les formes. Voir le
|
||||
fichier de documentation " SVG" pour plus d'informations et de conseils.
|
||||
💡 Note: If your new SVG stamps seem to have a lot of whitespace, make sure
|
||||
the SVG 'document' is no larger than the shape(s) within. If they are
|
||||
being clipped, make sure the 'document' is large enough to contain the
|
||||
shape(s). See the 'SVG documentation' in Tux Paint for more information
|
||||
and tips.
|
||||
|
||||
Utilisateurs avancés : Le HOWTO Advanced Stamps décrit, en détail, comment
|
||||
créer des images PNG qui seront parfaitement mises à l'échelle
|
||||
⚙ Utilisateurs avancés : Le HOWTO Advanced Stamps décrit, en détail,
|
||||
comment créer des images PNG qui seront parfaitement mises à l'échelle
|
||||
lorsqu'elles seront utilisées comme tampons dans Tux Paint .
|
||||
|
||||
Texte de description des tampons
|
||||
|
|
@ -361,7 +358,7 @@ Effets sonores des tampons
|
|||
tentera de charger le fichier son «par défaut». (par exemple,
|
||||
"stamp.wav")
|
||||
|
||||
Note: Also consider using descriptive sounds; see 'Son descriptif du
|
||||
💡 Note: Also consider using descriptive sounds; see 'Son descriptif du
|
||||
tampon', below.
|
||||
|
||||
Son descriptif du tampon
|
||||
|
|
@ -551,9 +548,9 @@ Mise en miroir et retournement
|
|||
pré-retournée avec "_flip" dans le nom, et / ou une image qui est à la
|
||||
fois en miroir et retournée, en la nommant " _mirror_flip".
|
||||
|
||||
Remarque : Si l'utilisateur retourne et reflète une image, et qu'un
|
||||
"_mirror_flip" pré-dessiné n'existe pas, mais que "_flip" ou "_mirror"
|
||||
existe , il sera utilisé, et reflété ou retourné, selon le cas.
|
||||
💡 Note: If the user flips and mirrors an image, and a pre-drawn
|
||||
"_mirror_flip" doesn't exist, but either "_flip" or "_mirror" does, it
|
||||
will be used, and mirrored or flipped, respectively.
|
||||
|
||||
Polices
|
||||
|
||||
|
|
@ -626,13 +623,12 @@ Images de démarrage avec 'style scénique'
|
|||
apparaîtront avec l'écran qui apparaît, suivant les différents choix de
|
||||
couleurs unies.
|
||||
|
||||
Remarque :'Images de démarrage' sont 'attachés' aux images sauvegardées,
|
||||
via un petit fichier texte qui a le même nom que le fichier sauvegardé,
|
||||
mais avec ".dat" comme extension. Ceci permet de continuer de s'occuper du
|
||||
dessin, mais après avoir quitté Tux Paint, oi bien une autre image a été
|
||||
chargée, ou bien une nouvelle image a été créée (En d'autres termes, si
|
||||
vous basez un dessin sur un image de démarrage, il sera toujours changé
|
||||
par lui).
|
||||
💡 Note: 'Images de démarrage' are 'attached' to saved pictures, via a
|
||||
small text file that has the same name as the saved file, but with ".dat"
|
||||
as the extension. This allows it to continue to affect the drawing even
|
||||
after Tux Paint has been quit, or another picture is loaded or a new image
|
||||
is created. (In other words, if you base a drawing on a image de
|
||||
démarrage, it will always be affected by it.)
|
||||
|
||||
'Modèles'
|
||||
|
||||
|
|
@ -667,12 +663,12 @@ Images de démarrage avec 'style scénique'
|
|||
«Nouveau» est accessible dans Tux Paint , les images 'modèle' apparaîtront
|
||||
avec l'écran qui apparaît, suivant les différents choix de couleurs unies.
|
||||
|
||||
Remarque :'Modèles' sont 'attachés' aux images sauvegardées, via un petit
|
||||
fichier texte qui a le même nom que le fichier sauvegardé, mais avec
|
||||
".dat" comme extension. Ceci permet de continuer de s'occuper du dessin,
|
||||
mais après avoir quitté Tux Paint, oi bien une autre image a été chargée,
|
||||
ou bien une nouvelle image a été créée (En d'autres termes, si vous basez
|
||||
un dessin sur un image 'modèle', il sera toujours changé par lui).
|
||||
💡 Note: 'Modèles' are 'attached' to saved pictures, via a small text file
|
||||
that has the same name as the saved file, but with ".dat" as the
|
||||
extension. This allows it to continue to affect the drawing even after Tux
|
||||
Paint has been quit, or another picture is loaded or a new image is
|
||||
created. (In other words, if you base a drawing on a image 'modèle', it
|
||||
will always be affected by it.)
|
||||
|
||||
Traductions
|
||||
|
||||
|
|
@ -712,12 +708,12 @@ Images de démarrage avec 'style scénique'
|
|||
* Virtraal
|
||||
* Lokalize
|
||||
|
||||
Remarque: Il est préférable de toujours travailler avec le dernier modèle
|
||||
de catalogue de texte Tux Paint ("tuxpaint.pot"), car un nouveau texte est
|
||||
ajouté et l'ancien texte est parfois modifié. Le catalogue de textes de la
|
||||
prochaine version inédite de Tux Paint se trouve dans le référentiel Git
|
||||
de Tux Paint (voir : https://tuxpaint.org/download/source/git/ ), et sur
|
||||
le site Web de Tux Paint à https://tuxpaint.org/help/po/.
|
||||
💡 Note: It is best to always work off of the latest Tux Paint text catalog
|
||||
template ("tuxpaint.pot"), since new text is added, and old text is
|
||||
occasionally changed. The text catalog for the upcoming, unreleased
|
||||
version of Tux Paint can be found in Tux Paint's Git repository (see:
|
||||
https://tuxpaint.org/download/source/git/), and on the Tux Paint website
|
||||
at https://tuxpaint.org/help/po/.
|
||||
|
||||
Pour modifier une traduction existante, téléchargez le dernier fichier
|
||||
".po" pour cette langue et modifiez-le comme décrit ci-dessus.
|
||||
|
|
@ -732,10 +728,10 @@ Images de démarrage avec 'style scénique'
|
|||
écriture au référentiel de code source Git afin que vous puissiez valider
|
||||
vos modifications directement.
|
||||
|
||||
Remarque : la prise en charge de nouveaux locales nécessite des ajouts au
|
||||
code source de Tux Paint ( "/src/i18n.h" et "/src/i18n.c"), et nécessite
|
||||
des mises à jour de Makefile, pour s'assurer que les fichiers ".po" sont
|
||||
compilés en fichiers ".mo", et utilisables pendant l'exécution.
|
||||
💡 Note: Support for new locales requires making additions to Tux Paint's
|
||||
source code ("/src/i18n.h" et "/src/i18n.c"), and requires updates to the
|
||||
Makefile, pour s'assurer que les fichiers ".po" sont compilés en fichiers
|
||||
".mo", et utilisables pendant l'exécution.
|
||||
|
||||
Méthodes alternatives de saisie
|
||||
|
||||
|
|
@ -787,19 +783,18 @@ Images de démarrage avec 'style scénique'
|
|||
30AD ki -
|
||||
30AE gi -
|
||||
|
||||
RemarqueLes lignes vides du fichier ".im" sont ignorées, aussi bien que
|
||||
les lignes commençant par "#" -- ce peut être utilisé pour ajouter des
|
||||
commentaires, comme dans l'exemple ci-dessus.
|
||||
⚙ Note: Blank lines within the ".im" file will be ignored, as will any
|
||||
text following a "#" (pound/hash) character — it can be used to denote
|
||||
comments, as seen in the example above.
|
||||
|
||||
Remarque : Les significations des indicateurs sont spécifiques à la langue
|
||||
et sont traitées par le code source spécifique à la langue dans
|
||||
"src/im.c". Par exemple, "b" est utilisé en coréen pour gérer Batchim, qui
|
||||
peut être reporté au caractère suivant.
|
||||
💡 Note: Meanings of the flags are locale-specific, and are processed by
|
||||
the language-specific source code in "src/im.c". For example, "b" is used
|
||||
in Korean to handle Batchim, which may carry over to the next character.
|
||||
|
||||
Remarque : la prise en charge de nouveaux méthodes de saisie nécessite des
|
||||
ajouts au code source de Tux Paint ( "/src/im.c"), et nécessite des mises
|
||||
à jour de Makefile, pour s'assurer que les fichiers ".im" sont disponibles
|
||||
pour être utilisés lors de l'exécution du programme.
|
||||
💡 Note: Support for new méthodes de saisie requires making additions to
|
||||
Tux Paint's source code ("/src/im.c"), and requires updates to the
|
||||
Makefile, pour s'assurer que les fichiers ".im" sont disponibles pour être
|
||||
utilisés lors de l'exécution du programme.
|
||||
|
||||
Clavier virtuel sur écran
|
||||
|
||||
|
|
@ -824,9 +819,9 @@ Fichier d'aperçu de la disposition ("qwerty.layout")
|
|||
keysymdefs keysymdef.h
|
||||
keyboardlist qwerty.layout default.layout
|
||||
|
||||
RemarqueLes lignes vides du fichier ".layout" sont ignorées, aussi bien
|
||||
que les lignes commençant par "#" -- ce peut être utilisé pour ajouter des
|
||||
commentaires, comme dans l'exemple ci-dessus.
|
||||
⚙ Note: Blank lines within the ".layout" file will be ignored, as will any
|
||||
text following a "#" (pound/hash) character — it can be used to denote
|
||||
comments, as seen in the example above.
|
||||
|
||||
La ligne "keyboardlist" décrit les dispositions vers lesquelles on bascule
|
||||
lorsque l'utilisateur clique sur les boutons gauche et droit du clavier.
|
||||
|
|
@ -962,7 +957,7 @@ Fichier de définitions des Keysim ("keysymdef.h")
|
|||
chaque keycap (par exemple, "XK_equal" correspond à "U+003D", pour le
|
||||
caractère "=" ("EQUALS SIGN").
|
||||
|
||||
Remarque : Ce fichier n'est pas compilé avec Tux Paint, mais il est lu et
|
||||
analysé durant l'exécution de celui-ci.
|
||||
💡 Note: This file is not compiled into Tux Paint, but is read and parsed
|
||||
at runtime.
|
||||
|
||||
Il est peu probable qu'une modification de ce fichier soit requise.
|
||||
|
|
|
|||
|
|
@ -54,7 +54,7 @@
|
|||
padding-bottom: 1em;
|
||||
border-bottom: 2px solid #000;
|
||||
}
|
||||
section.indent p,dl {
|
||||
section.indent p,dl,ul {
|
||||
margin-left: 2em;
|
||||
}
|
||||
section.indent dl p {
|
||||
|
|
@ -128,12 +128,12 @@
|
|||
</table>
|
||||
</section>
|
||||
|
||||
<section>
|
||||
<section class="outer">
|
||||
<p>
|
||||
Si vous souhaitez ajouter ou modifier des éléments tels que des pinceaux, des images de démarrage, des tampons en caoutchouc et d'autres contenus utilisés par Tux Paint , vous pouvez le faire assez facilement en ajoutant, modifiant ou supprimant simplement des fichiers là où Tux Paint les recherche. </p>
|
||||
|
||||
<p>
|
||||
Remarque: vous devrez redémarrer Tux Paint pour que les modifications prennent effet. </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> You'll need to re-launch Tux Paint for the changes to take effect. </p>
|
||||
</section>
|
||||
|
||||
<section class="indent outer"><!-- H1: Where Files Go -->
|
||||
|
|
@ -195,8 +195,8 @@
|
|||
<li>
|
||||
Vous y trouverez divers sous-dossiers, tels que " starters", "stamps", " brushes", etc. Ajouter du nouveau contenu à ces dossiers rendra celui-ci disponible pour tout utilisateur qui lance cette copie (icône) de Tux Paint . </li>
|
||||
</ol>
|
||||
<p>
|
||||
<em>Remarque :</em> Si vous installez une version plus récente de Tux Paint et remplacez ou supprimez l'ancienne version, vous perdrez les modifications apportées avec les instructions ci-dessus, faites donc des sauvegardes de votre nouveau contenu (tampons,pinceaux, etc.). </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <em>Remarque :</em> Si vous installez une version plus récente de Tux Paint et remplacez ou supprimez l'ancienne version, vous perdrez les modifications apportées avec les instructions ci-dessus, faites donc des sauvegardes de votre nouveau contenu (tampons,pinceaux, etc.). </p>
|
||||
<p>
|
||||
Tux Paint recherche également les fichiers dans un dossier "Tux Paint" que vous pouvez placer dans votre dossier système "Application Support" (situé sous "Library" à la racine de votre système de fichiers) : <blockquote>
|
||||
<code style="white-space: nowrap;">/Library/Application Support/TuxPaint/</code>
|
||||
|
|
@ -313,8 +313,8 @@
|
|||
Disposez chaque trame sur une grande image PNG. Par exemple, si votre pinceau mesure 30x30 et que vous avez 5 trames, l'image doit être 150x30. </p>
|
||||
<p>
|
||||
Ajoutez une ligne contenant la ligne "<code><b>frames=<i>N</i></b></code>" au fichier de données du pinceau, où"<i>N</i>" est le nombre d'images dans le pinceau. </p>
|
||||
<p>
|
||||
<b>Remarque :</b> si vous préférez que les images apparaissent de manière aléatoire plutôt que séquentielle, ajoutez en plus une ligne contenant "<code><b>random</b></code>" au fichier de données du pinceau. </p>
|
||||
<p class="note">
|
||||
<span title="Configuration option">⚙</span> <strong>Note:</strong> If you'd rather the frames be flipped through randomly, rather than sequentially, also add a line containing "<code><b>random</b></code>" to the brush's data file. </p>
|
||||
</dd>
|
||||
|
||||
<dt><strong>Pinceaux directionnels</strong></dt>
|
||||
|
|
@ -348,8 +348,8 @@
|
|||
<p>
|
||||
Placez les PNG de l'image du pinceau (et tous les fichiers texte de données) dans le répertoire "<code><b>brushes</b></code>". </p>
|
||||
|
||||
<p>
|
||||
Remarque: si vos nouveaux pinceaux se présentent tous sous forme de carrés ou de rectangles pleins, c'est que vous avez oublié d'utiliser la transparence alpha ! Consultez le fichier de documentation "PNG" pour plus d'informations et de conseils. </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> If your new pinceaux all come out as solid squares or rectangles, it's because you forgot to use alpha transparency! See the 'PNG documentation' in Tux Paint for more information and tips. </p>
|
||||
</section><!-- H1: Brushes -->
|
||||
|
||||
<section class="indent outer"><!-- H1: Stamps -->
|
||||
|
|
@ -387,14 +387,14 @@
|
|||
<p>
|
||||
Les SVG sont basés sur des vecteurs et seront mis à l'échelle de manière adéquate pour le canevas utilisé. </p>
|
||||
|
||||
<p>
|
||||
Remarque: si vos nouveaux des tampons basés sur PNG se présentent tous sous forme de carrés ou de rectangles pleins, c'est que vous avez oublié d'utiliser la transparence alpha ! Consultez le fichier de documentation "PNG" pour plus d'informations et de conseils. </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> If your new des tampons basés sur PNG all come out as solid squares or rectangles, it's because you forgot to use alpha transparency! See the 'PNG documentation' in Tux Paint for more information and tips. </p>
|
||||
|
||||
<p>
|
||||
Remarque: si vos nouveaux tampons SVG semblent avoir beaucoup de zones vides, assurez-vous que le «document» SVG n'est pas plus grand que la ou les formes qu'il contient. S'ils sont coupés, assurez-vous que le «document» est suffisamment grand pour contenir la ou les formes. Voir le fichier de documentation " SVG" pour plus d'informations et de conseils. </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> If your new SVG stamps seem to have a lot of whitespace, make sure the SVG 'document' is no larger than the shape(s) within. If they are being clipped, make sure the 'document' is large enough to contain the shape(s). See the 'SVG documentation' in Tux Paint for more information and tips. </p>
|
||||
|
||||
<p>
|
||||
<b>Utilisateurs avancés :</b> Le HOWTO Advanced Stamps décrit, en détail, comment créer des images PNG qui seront parfaitement mises à l'échelle lorsqu'elles seront utilisées comme tampons dans Tux Paint . </p>
|
||||
<p class="note">
|
||||
<span title="Configuration option">⚙</span> <b>Utilisateurs avancés :</b> Le HOWTO Advanced Stamps décrit, en détail, comment créer des images PNG qui seront parfaitement mises à l'échelle lorsqu'elles seront utilisées comme tampons dans Tux Paint . </p>
|
||||
</section><!-- H2: Stamp Images -->
|
||||
|
||||
<section><!-- H2: Stamp Descriptive Text -->
|
||||
|
|
@ -455,8 +455,8 @@
|
|||
</dd>
|
||||
</dl>
|
||||
|
||||
<p>
|
||||
Note: Also consider using descriptive sounds; see 'Son descriptif du tampon', below. </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> Also consider using descriptive sounds; see 'Son descriptif du tampon', below. </p>
|
||||
</section><!-- H2: Stamp Sound Effects -->
|
||||
|
||||
<section><!-- H2: Stamp Descriptive Sound -->
|
||||
|
|
@ -619,8 +619,8 @@
|
|||
<p>
|
||||
Depuis Tux Paint 0.9.18, vous pouvez également fournir une image pré-retournée avec "<code><b>_flip</b></code>" dans le nom, et / ou une image qui est à la fois en miroir et retournée, en la nommant " <code><b>_mirror_flip</b></code>". </p>
|
||||
|
||||
<p>
|
||||
<b>Remarque :</b> Si l'utilisateur retourne et reflète une image, et qu'un "<code>_mirror_flip</code>" pré-dessiné n'existe pas, mais que "<code>_flip</code>" ou "<code>_mirror</code>" existe , il sera utilisé, et reflété ou retourné, selon le cas. </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</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>
|
||||
</section><!-- H2: Pre-Mirrored and Flipped Stamps -->
|
||||
</section><!-- H1: Stamps -->
|
||||
|
||||
|
|
@ -705,8 +705,8 @@
|
|||
<p>
|
||||
Placez-les dans le répertoire "<code><b>starters</b></code>". Lorsque la boîte de dialogue «Nouveau» est accessible dans Tux Paint , les images de démarrage apparaîtront avec l'écran qui apparaît, suivant les différents choix de couleurs unies. </p>
|
||||
|
||||
<p>
|
||||
<b>Remarque :</b>'Images de démarrage' sont 'attachés' aux images sauvegardées, via un petit fichier texte qui a le même nom que le fichier sauvegardé, mais avec "<code>.dat</code>" comme extension. Ceci permet de continuer de s'occuper du dessin, mais après avoir quitté Tux Paint, oi bien une autre image a été chargée, ou bien une nouvelle image a été créée (En d'autres termes, si vous basez un dessin sur un image de démarrage, il sera toujours changé par lui). </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> 'Images de démarrage' are 'attached' to saved pictures, via a small text file that has the same name as the saved file, but with "<code>.dat</code>" as the extension. This allows it to continue to affect the drawing even after Tux Paint has been quit, or another picture is loaded or a new image is created. (In other words, if you base a drawing on a image de démarrage, it will always be affected by it.) </p>
|
||||
</section><!-- H1: Starters -->
|
||||
|
||||
<section class="indent outer"><!-- H1: 'Templates' -->
|
||||
|
|
@ -740,8 +740,8 @@
|
|||
<p>
|
||||
Placez-les dans le répertoire "<code><b>templates</b></code>". Lorsque la boîte de dialogue «Nouveau» est accessible dans Tux Paint , les images 'modèle' apparaîtront avec l'écran qui apparaît, suivant les différents choix de couleurs unies. </p>
|
||||
|
||||
<p>
|
||||
<b>Remarque :</b>'Modèles' sont 'attachés' aux images sauvegardées, via un petit fichier texte qui a le même nom que le fichier sauvegardé, mais avec "<code>.dat</code>" comme extension. Ceci permet de continuer de s'occuper du dessin, mais après avoir quitté Tux Paint, oi bien une autre image a été chargée, ou bien une nouvelle image a été créée (En d'autres termes, si vous basez un dessin sur un image 'modèle', il sera toujours changé par lui). </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> 'Modèles' are 'attached' to saved pictures, via a small text file that has the same name as the saved file, but with "<code>.dat</code>" as the extension. This allows it to continue to affect the drawing even after Tux Paint has been quit, or another picture is loaded or a new image is created. (In other words, if you base a drawing on a image 'modèle', it will always be affected by it.) </p>
|
||||
<br clear="all">
|
||||
</section><!-- H1: 'Templates' -->
|
||||
|
||||
|
|
@ -782,8 +782,8 @@
|
|||
</ul>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
Remarque: Il est préférable de toujours travailler avec le <i>dernier</i> modèle de catalogue de texte Tux Paint ("<code>tuxpaint.pot</code>"), car un nouveau texte est ajouté et l'ancien texte est parfois modifié. Le catalogue de textes de la prochaine version inédite de Tux Paint se trouve dans le référentiel Git de Tux Paint (voir : <a href="https://tuxpaint.org/download/source/git/">https://tuxpaint.org/download/source/git/</a> ), et sur le site Web de Tux Paint à <a href="https://tuxpaint.org/help/po/">https://tuxpaint.org/help/po/</a>. </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> It is best to always work off of the <i>latest</i> Tux Paint text catalog template ("<code>tuxpaint.pot</code>"), since new text is added, and old text is occasionally changed. The text catalog for the upcoming, unreleased version of Tux Paint can be found in Tux Paint's Git repository (see: <a href="https://tuxpaint.org/download/source/git/">https://tuxpaint.org/download/source/git/</a>), and on the Tux Paint website at <a href="https://tuxpaint.org/help/po/">https://tuxpaint.org/help/po/</a>. </p>
|
||||
|
||||
<p>
|
||||
Pour modifier une traduction existante, téléchargez le dernier fichier "<code>.po</code>" pour cette langue et modifiez-le comme décrit ci-dessus. </p>
|
||||
|
|
@ -794,8 +794,8 @@
|
|||
<p>
|
||||
Autrement, si vous avez un compte chez <a href="http://www.sourceforge.net/">SourceForge.net</a> , vous pouvez demander à être ajouté au projet "<code>tuxpaint</code>" et obtenir un accès en écriture au référentiel de code source Git afin que vous puissiez valider vos modifications directement. </p>
|
||||
|
||||
<p>
|
||||
<i>Remarque :</i> la prise en charge de nouveaux locales nécessite des ajouts au code source de Tux Paint ( "<code>/src/i18n.h</code>" et "<code>/src/i18n.c</code>"), et nécessite des mises à jour de <code>Makefile</code>, pour s'assurer que les fichiers "<code>.po</code>" sont compilés en fichiers "<code>.mo</code>", et utilisables pendant l'exécution. </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> Support for new locales requires making additions to Tux Paint's source code ("<code>/src/i18n.h</code>" et "<code>/src/i18n.c</code>"), and requires updates to the <code>Makefile</code>, pour s'assurer que les fichiers "<code>.po</code>" sont compilés en fichiers "<code>.mo</code>", et utilisables pendant l'exécution. </p>
|
||||
</section><!-- H1: Translations -->
|
||||
|
||||
<section class="indent outer"><!-- H1: Alternative Input Methods -->
|
||||
|
|
@ -849,14 +849,14 @@
|
|||
</blockquote>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
<i>Remarque</i>Les lignes vides du fichier "<code>.im</code>" sont ignorées, aussi bien que les lignes commençant par "<code>#</code>" -- ce peut être utilisé pour ajouter des commentaires, comme dans l'exemple ci-dessus. </p>
|
||||
<p class="note">
|
||||
<span title="Configuration option">⚙</span> <strong>Note:</strong> Blank lines within the "<code>.im</code>" file will be ignored, as will any text following a "<code>#</code>" (pound/hash) character — it can be used to denote comments, as seen in the example above. </p>
|
||||
|
||||
<p>
|
||||
<i>Remarque :</i> Les significations des indicateurs sont spécifiques à la langue et sont traitées par le code source spécifique à la langue dans "<code>src/im.c</code>". Par exemple, "<code>b</code>" est utilisé en coréen pour gérer Batchim, qui peut être reporté au caractère suivant. </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> Meanings of the flags are locale-specific, and are processed by the language-specific source code in "<code>src/im.c</code>". For example, "<code>b</code>" is used in Korean to handle Batchim, which may carry over to the next character. </p>
|
||||
|
||||
<p>
|
||||
<i>Remarque :</i> la prise en charge de nouveaux méthodes de saisie nécessite des ajouts au code source de Tux Paint ( "<code>/src/im.c</code>"), et nécessite des mises à jour de <code>Makefile</code>, pour s'assurer que les fichiers "<code>.im</code>" sont disponibles pour être utilisés lors de l'exécution du programme. </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> Support for new méthodes de saisie requires making additions to Tux Paint's source code ("<code>/src/im.c</code>"), and requires updates to the <code>Makefile</code>, pour s'assurer que les fichiers "<code>.im</code>" sont disponibles pour être utilisés lors de l'exécution du programme. </p>
|
||||
</section><!-- H1: Alternative Input Methods -->
|
||||
|
||||
<section class="indent outer"><!-- H1: On-screen Keyboard -->
|
||||
|
|
@ -891,8 +891,8 @@
|
|||
</p>
|
||||
</blockquote>
|
||||
|
||||
<p>
|
||||
<i>Remarque</i>Les lignes vides du fichier "<code>.layout</code>" sont ignorées, aussi bien que les lignes commençant par "<code>#</code>" -- ce peut être utilisé pour ajouter des commentaires, comme dans l'exemple ci-dessus. </p>
|
||||
<p class="note">
|
||||
<span title="Configuration option">⚙</span> <strong>Note:</strong> Blank lines within the "<code>.layout</code>" file will be ignored, as will any text following a "<code>#</code>" (pound/hash) character — it can be used to denote comments, as seen in the example above. </p>
|
||||
|
||||
<p>
|
||||
La ligne "<code>keyboardlist</code>" décrit les dispositions vers lesquelles on bascule lorsque l'utilisateur clique sur les boutons gauche et droit du clavier. (Voir ci-dessous.) </p>
|
||||
|
|
@ -1046,8 +1046,8 @@
|
|||
<p>
|
||||
Ce fichier (qui est un fichier d'en-tête du langage de programmation <cite>C</cite> ) provient également du <cite>système X Window</cite> . Il définit les valeurs Unicode de chaque keycap (par exemple, "<code>XK_equal</code>" correspond à "<code>U+003D</code>", pour le caractère "<code>=</code>" ("<code>EQUALS SIGN</code>"). </p>
|
||||
|
||||
<p>
|
||||
<b>Remarque :</b> Ce fichier n'est pas compilé avec Tux Paint, mais il est lu et analysé durant l'exécution de celui-ci. </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> This file is not compiled into Tux Paint, but is read and parsed at runtime. </p>
|
||||
|
||||
<p>
|
||||
Il est peu probable qu'une modification de ce fichier soit requise. </p>
|
||||
|
|
|
|||
|
|
@ -54,7 +54,7 @@
|
|||
padding-bottom: 1em;
|
||||
border-bottom: 2px solid #000;
|
||||
}
|
||||
section.indent p,dl {
|
||||
section.indent p,dl,ul {
|
||||
margin-left: 2em;
|
||||
}
|
||||
section.indent dl p {
|
||||
|
|
|
|||
|
|
@ -54,7 +54,7 @@
|
|||
padding-bottom: 1em;
|
||||
border-bottom: 2px solid #000;
|
||||
}
|
||||
section.indent p,dl {
|
||||
section.indent p,dl,ul {
|
||||
margin-left: 2em;
|
||||
}
|
||||
section.indent dl p {
|
||||
|
|
|
|||
|
|
@ -37,7 +37,7 @@
|
|||
bastante facilidade simplemente engadindo, cambiando ou eliminando
|
||||
ficheiros onde os busque Tux Paint.
|
||||
|
||||
Nota: Deberá reiniciar Tux Paint para que os cambios teñan efecto.
|
||||
💡 Note: You'll need to re-launch Tux Paint for the changes to take effect.
|
||||
|
||||
Onde van os ficheiros
|
||||
|
||||
|
|
@ -89,7 +89,7 @@ Ficheiros estándar
|
|||
cartafoles fará que o contido estea dispoñíbel para calquera
|
||||
usuario que inicia copia (icona) de Tux Paint .
|
||||
|
||||
Nota: Se instala unha versión máis recente de Tux Paint e
|
||||
💡 Nota: Se instala unha versión máis recente de Tux Paint e
|
||||
substitúe ou desbota a versión antiga, perderá os cambios feitos
|
||||
seguindo as instrucións anteriores, así que garde as copias de
|
||||
seguridade do seu novo contido (selos, pinceis, etc.) .
|
||||
|
|
@ -192,9 +192,9 @@ Opcións de pinceis
|
|||
Engada unha liña que conteña a liña «frames=N» ao ficheiro de
|
||||
datos do pincel, onde «N» é o número de fotogramas do pincel.
|
||||
|
||||
Nota: Se prefire que os fotogramas se pasen ao chou, no canto de
|
||||
secuencialmente, engada tamén unha liña que conteña «random» ao
|
||||
ficheiro de datos do pincel.
|
||||
⚙ Note: If you'd rather the frames be flipped through randomly,
|
||||
rather than sequentially, also add a line containing "random" to
|
||||
the brush's data file.
|
||||
|
||||
Pinceis direccionais
|
||||
|
||||
|
|
@ -236,9 +236,9 @@ Opcións de pinceis
|
|||
Coloque os ficheiros PNG de pincel (e calquera ficheiro de texto de datos)
|
||||
no directorio «brushes».
|
||||
|
||||
Nota: Se o seu novo brushes sae como cadrados ou rectángulos sólidos, é
|
||||
porque esqueceu usar a transparencia alfa. Vexa a «Documentación PNG» en
|
||||
Tux Paint para obter máis información e consellos.
|
||||
💡 Note: If your new brushes all come out as solid squares or rectangles,
|
||||
it's because you forgot to use alpha transparency! See the 'PNG
|
||||
documentation' in Tux Paint for more information and tips.
|
||||
|
||||
Selos
|
||||
|
||||
|
|
@ -265,17 +265,17 @@ Imaxes de selos
|
|||
Os SVG están baseados en vectores e escalaranse axeitadamente para o
|
||||
tamaño do lenzo que se use en Tux Paint.
|
||||
|
||||
Nota: Se o seu novo PNG-based stamps sae como cadrados ou rectángulos
|
||||
sólidos, é porque esqueceu usar a transparencia alfa. Vexa a
|
||||
«Documentación PNG» en Tux Paint para obter máis información e consellos.
|
||||
💡 Note: If your new PNG-based stamps all come out as solid squares or
|
||||
rectangles, it's because you forgot to use alpha transparency! See the
|
||||
'PNG documentation' in Tux Paint for more information and tips.
|
||||
|
||||
Nota: Se os seus novos selos SVG parecen ter moito espazo en branco,
|
||||
asegúrese de que o «documento» SVG non sexa maior que a(s) forma(s) que
|
||||
contén. Se se están recortando, asegúrese de que o «documento» é grande de
|
||||
abondo como para conter a(s) forma(s). Vexa a «Documentación SVG» en Tux
|
||||
Paint para obter máis información e consellos.
|
||||
💡 Note: If your new SVG stamps seem to have a lot of whitespace, make sure
|
||||
the SVG 'document' is no larger than the shape(s) within. If they are
|
||||
being clipped, make sure the 'document' is large enough to contain the
|
||||
shape(s). See the 'SVG documentation' in Tux Paint for more information
|
||||
and tips.
|
||||
|
||||
Usuarios avanzados: O documento «Como facer os selos avanzados» describe
|
||||
⚙ Usuarios avanzados: O documento «Como facer os selos avanzados» describe
|
||||
detalladamente como facer imaxes PNG que se adaptarán perfectamente cando
|
||||
se usen como selos en Tux Paint.
|
||||
|
||||
|
|
@ -342,7 +342,7 @@ Efectos de son dos selos
|
|||
cargar o ficheiro de son «predeterminado». (por exemplo,
|
||||
«selo.wav»)
|
||||
|
||||
Note: Also consider using descriptive sounds; see 'Son descritivo do
|
||||
💡 Note: Also consider using descriptive sounds; see 'Son descritivo do
|
||||
selo', below.
|
||||
|
||||
Son descritivo do selo
|
||||
|
|
@ -524,9 +524,9 @@ Selos prereflectidos e invertidos
|
|||
previamente invertida con «_flip» no nome e/ou unha imaxe que se reflicta
|
||||
e inverta, denominándoa «_mirror_flip».
|
||||
|
||||
Nota: Se o usuario inverte e reflicte unha imaxe e non existe un
|
||||
«_mirror_flip» deseñado previamente, mais si un «_flip» ou un «_mirror» ,
|
||||
usarase e reflectirase ou inverterase, respectivamente.
|
||||
💡 Note: If the user flips and mirrors an image, and a pre-drawn
|
||||
"_mirror_flip" doesn't exist, but either "_flip" or "_mirror" does, it
|
||||
will be used, and mirrored or flipped, respectively.
|
||||
|
||||
Tipos de letra
|
||||
|
||||
|
|
@ -594,12 +594,12 @@ Imaxes «de comezo» ao estilo dunha escena
|
|||
en Tux Paint, as imaxes «de comezo» veranse na pantalla que aparece, após
|
||||
as distintas opcións de cor sólida.
|
||||
|
||||
Nota: As «Imaxes de comezo» están «anexadas» ás imaxes gardadas, a través
|
||||
dun pequeno ficheiro de texto que leva o mesmo nome que o ficheiro
|
||||
gardado, pero con «.dat» como extensión. Isto permítelle seguir afectando
|
||||
ao debuxo incluso após saír de Tux Paint, ou se cargue outra imaxe ou se
|
||||
cree unha nova imaxe. (Noutras palabras, se un debuxo se basea nun imaxe
|
||||
«de comezo», sempre se verá afectado por el.)
|
||||
💡 Note: «Imaxes de comezo» are 'attached' to saved pictures, via a small
|
||||
text file that has the same name as the saved file, but with ".dat" as the
|
||||
extension. This allows it to continue to affect the drawing even after Tux
|
||||
Paint has been quit, or another picture is loaded or a new image is
|
||||
created. (In other words, if you base a drawing on a imaxe «de comezo», it
|
||||
will always be affected by it.)
|
||||
|
||||
«Modelos»
|
||||
|
||||
|
|
@ -633,12 +633,12 @@ Imaxes «de comezo» ao estilo dunha escena
|
|||
en Tux Paint, as imaxes «modelo» veranse na pantalla que aparece, após as
|
||||
distintas opcións de cor sólida.
|
||||
|
||||
Nota: As «Modelos» están «anexadas» ás imaxes gardadas, a través dun
|
||||
pequeno ficheiro de texto que leva o mesmo nome que o ficheiro gardado,
|
||||
pero con «.dat» como extensión. Isto permítelle seguir afectando ao debuxo
|
||||
incluso após saír de Tux Paint, ou se cargue outra imaxe ou se cree unha
|
||||
nova imaxe. (Noutras palabras, se un debuxo se basea nun imaxe «modelo»,
|
||||
sempre se verá afectado por el.)
|
||||
💡 Note: «Modelos» are 'attached' to saved pictures, via a small text file
|
||||
that has the same name as the saved file, but with ".dat" as the
|
||||
extension. This allows it to continue to affect the drawing even after Tux
|
||||
Paint has been quit, or another picture is loaded or a new image is
|
||||
created. (In other words, if you base a drawing on a imaxe «modelo», it
|
||||
will always be affected by it.)
|
||||
|
||||
Traducións
|
||||
|
||||
|
|
@ -676,12 +676,12 @@ Imaxes «de comezo» ao estilo dunha escena
|
|||
* Virtraal
|
||||
* Lokalize
|
||||
|
||||
Nota: É mellor traballar sempre co último modelo de catálogo de texto Tux
|
||||
Paint («tuxpaint.pot»), xa que se engade n novos textos e o texto antigo
|
||||
cambia ocasionalmente. O catálogo de texto para a próxima versión inédita
|
||||
de Tux Paint pódese atopar no repositorio Git de Tux Paint (ver:
|
||||
https://tuxpaint.org/download/source/git/) e no sitio web de Tux Paint en
|
||||
https://tuxpaint.org/help/po/.
|
||||
💡 Note: It is best to always work off of the latest Tux Paint text catalog
|
||||
template ("tuxpaint.pot"), since new text is added, and old text is
|
||||
occasionally changed. The text catalog for the upcoming, unreleased
|
||||
version of Tux Paint can be found in Tux Paint's Git repository (see:
|
||||
https://tuxpaint.org/download/source/git/), and on the Tux Paint website
|
||||
at https://tuxpaint.org/help/po/.
|
||||
|
||||
Para editar unha tradución existente, descargue o último ficheiro «.po»
|
||||
para ese idioma e edíteo como se describe anteriormente.
|
||||
|
|
@ -696,11 +696,11 @@ Imaxes «de comezo» ao estilo dunha escena
|
|||
repositorio de código fonte de Git para que poida enviar os seus cambios
|
||||
directamente.
|
||||
|
||||
Nota: A compatibilidade cos novo configuracións locais require facer
|
||||
adicións ao código fonte de Tux Paint («/src/i18n.h» e «/src/i18n.c»), e
|
||||
require actualizacións dos Makefile, para asegurarse de que os ficheiros
|
||||
«.po» están compilados en ficheiros «.mo» e están dispoñíbeis para o seu
|
||||
uso en tempo de execución.
|
||||
💡 Note: Support for new configuracións locais requires making additions to
|
||||
Tux Paint's source code («/src/i18n.h» e «/src/i18n.c»), and requires
|
||||
updates to the Makefile, para asegurarse de que os ficheiros «.po» están
|
||||
compilados en ficheiros «.mo» e están dispoñíbeis para o seu uso en tempo
|
||||
de execución.
|
||||
|
||||
Métodos de entrada alternativos
|
||||
|
||||
|
|
@ -751,19 +751,18 @@ Imaxes «de comezo» ao estilo dunha escena
|
|||
30AD ki -
|
||||
30AE gi -
|
||||
|
||||
Nota: Ignoraranse as liñas en branco dentro do ficheiro «.im», así como
|
||||
calquera texto que teña un carácter «#» (grella). Isto pódese usar para
|
||||
denotar comentarios , como se ve no exemplo anterior.
|
||||
⚙ Note: Blank lines within the ".im" file will be ignored, as will any
|
||||
text following a "#" (pound/hash) character — it can be used to denote
|
||||
comments, as seen in the example above.
|
||||
|
||||
Nota: Os significados dos sinaladores son específicos da configuración
|
||||
local e son procesados polo código fonte específico do idioma en
|
||||
«src/im.c». Por exemplo, «b» úsase en coreano para tratar Batchim, que
|
||||
pode pasar ao seguinte carácter.
|
||||
💡 Note: Meanings of the flags are locale-specific, and are processed by
|
||||
the language-specific source code in "src/im.c". For example, "b" is used
|
||||
in Korean to handle Batchim, which may carry over to the next character.
|
||||
|
||||
Nota: A compatibilidade cos novo input methods require facer adicións ao
|
||||
código fonte de Tux Paint ("/src/im.c"), e require actualizacións dos
|
||||
Makefile, para asegurarse de que os ficheiros «.im» están dispoñíbeis para
|
||||
o seu uso en tempo de execución.
|
||||
💡 Note: Support for new input methods requires making additions to Tux
|
||||
Paint's source code ("/src/im.c"), and requires updates to the Makefile,
|
||||
para asegurarse de que os ficheiros «.im» están dispoñíbeis para o seu uso
|
||||
en tempo de execución.
|
||||
|
||||
Teclado en pantalla
|
||||
|
||||
|
|
@ -788,9 +787,9 @@ Ficheiro de visión xeral da disposición («qwerty.layout»)
|
|||
keysymdefs keysymdef.h
|
||||
keyboardlist qwerty.layout default.layout
|
||||
|
||||
Nota: Ignoraranse as liñas en branco dentro do ficheiro «.layout», así
|
||||
como calquera texto que teña un carácter «#» (grella). Isto pódese usar
|
||||
para denotar comentarios , como se ve no exemplo anterior.
|
||||
⚙ Note: Blank lines within the ".layout" file will be ignored, as will any
|
||||
text following a "#" (pound/hash) character — it can be used to denote
|
||||
comments, as seen in the example above.
|
||||
|
||||
A liña «keyboardlist» describe a que esquemas cambiar, cando o usuario
|
||||
preme nos botóns esquerdo e dereito do teclado. (Ver máis abaixo.)
|
||||
|
|
@ -923,7 +922,7 @@ Ficheiro de definición Keysym («keysymdef.h»)
|
|||
(p. ex.: «XK_equal» corresponde a «U+003D», para o carácter «=» («EQUALS
|
||||
SIGN»).
|
||||
|
||||
Nota: este ficheiro non se compila en Tux Paint, senón que se le e analiza
|
||||
no tempo de execución.
|
||||
💡 Note: This file is not compiled into Tux Paint, but is read and parsed
|
||||
at runtime.
|
||||
|
||||
É pouco probábel que se precise algunha modificación neste ficheiro.
|
||||
|
|
|
|||
|
|
@ -54,7 +54,7 @@
|
|||
padding-bottom: 1em;
|
||||
border-bottom: 2px solid #000;
|
||||
}
|
||||
section.indent p,dl {
|
||||
section.indent p,dl,ul {
|
||||
margin-left: 2em;
|
||||
}
|
||||
section.indent dl p {
|
||||
|
|
@ -128,12 +128,12 @@
|
|||
</table>
|
||||
</section>
|
||||
|
||||
<section>
|
||||
<section class="outer">
|
||||
<p>
|
||||
Se quere engadir ou cambiar cousas como pinceis, imaxes de comezo, selos de goma e outros contidos empregados por Tux Paint, pode facelo con bastante facilidade simplemente engadindo, cambiando ou eliminando ficheiros onde os busque Tux Paint. </p>
|
||||
|
||||
<p>
|
||||
Nota: Deberá reiniciar Tux Paint para que os cambios teñan efecto. </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> You'll need to re-launch Tux Paint for the changes to take effect. </p>
|
||||
</section>
|
||||
|
||||
<section class="indent outer"><!-- H1: Where Files Go -->
|
||||
|
|
@ -195,8 +195,8 @@
|
|||
<li>
|
||||
Alí atoparás varios subcartafoles, como «imaxes de comezo», «selos», «pinceis», etc. Engadindo novo contido a estes cartafoles fará que o contido estea dispoñíbel para calquera usuario que inicia copia (icona) de Tux Paint . </li>
|
||||
</ol>
|
||||
<p>
|
||||
<em>Nota:</em> Se instala unha versión máis recente de Tux Paint e substitúe ou desbota a versión antiga, perderá os cambios feitos seguindo as instrucións anteriores, así que garde as copias de seguridade do seu novo contido (selos, pinceis, etc.) . </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <em>Nota:</em> Se instala unha versión máis recente de Tux Paint e substitúe ou desbota a versión antiga, perderá os cambios feitos seguindo as instrucións anteriores, así que garde as copias de seguridade do seu novo contido (selos, pinceis, etc.) . </p>
|
||||
<p>
|
||||
Tux Paint tamén busca ficheiros nun cartafol «TuxPaint» que pode colocar no seu sistema no cartafol «Application Support» (atópase en «Library» na raíz do seu sistema de ficheiros): <blockquote>
|
||||
<code style="white-space: nowrap;">/Library/Application Support/TuxPaint/</code>
|
||||
|
|
@ -313,8 +313,8 @@
|
|||
Coloca cada cadro nunha ampla imaxe PNG. Por exemplo, se o pincel ten 30x30 e ten 5 fotogramas, a imaxe debería ser 150x30. </p>
|
||||
<p>
|
||||
Engada unha liña que conteña a liña «<code><b>frames=<i>N</i></b></code>» ao ficheiro de datos do pincel, onde «<i>N</i>» é o número de fotogramas do pincel. </p>
|
||||
<p>
|
||||
<b>Nota:</b> Se prefire que os fotogramas se pasen ao chou, no canto de secuencialmente, engada tamén unha liña que conteña «<code><b>random</b></code>» ao ficheiro de datos do pincel. </p>
|
||||
<p class="note">
|
||||
<span title="Configuration option">⚙</span> <strong>Note:</strong> If you'd rather the frames be flipped through randomly, rather than sequentially, also add a line containing "<code><b>random</b></code>" to the brush's data file. </p>
|
||||
</dd>
|
||||
|
||||
<dt><strong>Pinceis direccionais</strong></dt>
|
||||
|
|
@ -348,8 +348,8 @@
|
|||
<p>
|
||||
Coloque os ficheiros PNG de pincel (e calquera ficheiro de texto de datos) no directorio «<code><b>brushes</b></code>». </p>
|
||||
|
||||
<p>
|
||||
Nota: Se o seu novo brushes sae como cadrados ou rectángulos sólidos, é porque esqueceu usar a transparencia alfa. Vexa a «Documentación PNG» en Tux Paint para obter máis información e consellos. </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> If your new brushes all come out as solid squares or rectangles, it's because you forgot to use alpha transparency! See the 'PNG documentation' in Tux Paint for more information and tips. </p>
|
||||
</section><!-- H1: Brushes -->
|
||||
|
||||
<section class="indent outer"><!-- H1: Stamps -->
|
||||
|
|
@ -387,14 +387,14 @@
|
|||
<p>
|
||||
Os SVG están baseados en vectores e escalaranse axeitadamente para o tamaño do lenzo que se use en Tux Paint. </p>
|
||||
|
||||
<p>
|
||||
Nota: Se o seu novo PNG-based stamps sae como cadrados ou rectángulos sólidos, é porque esqueceu usar a transparencia alfa. Vexa a «Documentación PNG» en Tux Paint para obter máis información e consellos. </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> If your new PNG-based stamps all come out as solid squares or rectangles, it's because you forgot to use alpha transparency! See the 'PNG documentation' in Tux Paint for more information and tips. </p>
|
||||
|
||||
<p>
|
||||
Nota: Se os seus novos selos SVG parecen ter moito espazo en branco, asegúrese de que o «documento» SVG non sexa maior que a(s) forma(s) que contén. Se se están recortando, asegúrese de que o «documento» é grande de abondo como para conter a(s) forma(s). Vexa a «Documentación SVG» en Tux Paint para obter máis información e consellos. </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> If your new SVG stamps seem to have a lot of whitespace, make sure the SVG 'document' is no larger than the shape(s) within. If they are being clipped, make sure the 'document' is large enough to contain the shape(s). See the 'SVG documentation' in Tux Paint for more information and tips. </p>
|
||||
|
||||
<p>
|
||||
<b>Usuarios avanzados:</b> O documento «Como facer os selos avanzados» describe detalladamente como facer imaxes PNG que se adaptarán perfectamente cando se usen como selos en Tux Paint. </p>
|
||||
<p class="note">
|
||||
<span title="Configuration option">⚙</span> <b>Usuarios avanzados:</b> O documento «Como facer os selos avanzados» describe detalladamente como facer imaxes PNG que se adaptarán perfectamente cando se usen como selos en Tux Paint. </p>
|
||||
</section><!-- H2: Stamp Images -->
|
||||
|
||||
<section><!-- H2: Stamp Descriptive Text -->
|
||||
|
|
@ -455,8 +455,8 @@
|
|||
</dd>
|
||||
</dl>
|
||||
|
||||
<p>
|
||||
Note: Also consider using descriptive sounds; see 'Son descritivo do selo', below. </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> Also consider using descriptive sounds; see 'Son descritivo do selo', below. </p>
|
||||
</section><!-- H2: Stamp Sound Effects -->
|
||||
|
||||
<section><!-- H2: Stamp Descriptive Sound -->
|
||||
|
|
@ -619,8 +619,8 @@
|
|||
<p>
|
||||
A partir de Tux Paint 0.9.18, de xeito similar pode fornecer unha imaxe previamente invertida con «<code><b>_flip</b></code>» no nome e/ou unha imaxe que se reflicta e inverta, denominándoa «<code><b>_mirror_flip</b></code>». </p>
|
||||
|
||||
<p>
|
||||
<b>Nota:</b> Se o usuario inverte e reflicte unha imaxe e non existe un «<code>_mirror_flip</code>» deseñado previamente, mais si un «<code>_flip</code>» ou un «<code>_mirror</code>» , usarase e reflectirase ou inverterase, respectivamente. </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</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>
|
||||
</section><!-- H2: Pre-Mirrored and Flipped Stamps -->
|
||||
</section><!-- H1: Stamps -->
|
||||
|
||||
|
|
@ -705,8 +705,8 @@
|
|||
<p>
|
||||
Colóqueas no directorio de «<code><b>starters</b></code>». Cando se accede ao diálogo «Novo» en Tux Paint, as imaxes «de comezo» veranse na pantalla que aparece, após as distintas opcións de cor sólida. </p>
|
||||
|
||||
<p>
|
||||
<b>Nota:</b> As «Imaxes de comezo» están «anexadas» ás imaxes gardadas, a través dun pequeno ficheiro de texto que leva o mesmo nome que o ficheiro gardado, pero con «<code>.dat</code>» como extensión. Isto permítelle seguir afectando ao debuxo incluso após saír de Tux Paint, ou se cargue outra imaxe ou se cree unha nova imaxe. (Noutras palabras, se un debuxo se basea nun imaxe «de comezo», sempre se verá afectado por el.) </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> «Imaxes de comezo» are 'attached' to saved pictures, via a small text file that has the same name as the saved file, but with "<code>.dat</code>" as the extension. This allows it to continue to affect the drawing even after Tux Paint has been quit, or another picture is loaded or a new image is created. (In other words, if you base a drawing on a imaxe «de comezo», it will always be affected by it.) </p>
|
||||
</section><!-- H1: Starters -->
|
||||
|
||||
<section class="indent outer"><!-- H1: 'Templates' -->
|
||||
|
|
@ -740,8 +740,8 @@
|
|||
<p>
|
||||
Colóqueas no directorio de «<code><b>templates</b></code>». Cando se accede ao diálogo «Novo» en Tux Paint, as imaxes «modelo» veranse na pantalla que aparece, após as distintas opcións de cor sólida. </p>
|
||||
|
||||
<p>
|
||||
<b>Nota:</b> As «Modelos» están «anexadas» ás imaxes gardadas, a través dun pequeno ficheiro de texto que leva o mesmo nome que o ficheiro gardado, pero con «<code>.dat</code>» como extensión. Isto permítelle seguir afectando ao debuxo incluso após saír de Tux Paint, ou se cargue outra imaxe ou se cree unha nova imaxe. (Noutras palabras, se un debuxo se basea nun imaxe «modelo», sempre se verá afectado por el.) </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> «Modelos» are 'attached' to saved pictures, via a small text file that has the same name as the saved file, but with "<code>.dat</code>" as the extension. This allows it to continue to affect the drawing even after Tux Paint has been quit, or another picture is loaded or a new image is created. (In other words, if you base a drawing on a imaxe «modelo», it will always be affected by it.) </p>
|
||||
<br clear="all">
|
||||
</section><!-- H1: 'Templates' -->
|
||||
|
||||
|
|
@ -782,8 +782,8 @@
|
|||
</ul>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
<i>Nota:</i> É mellor traballar sempre co <i>último</i> modelo de catálogo de texto Tux Paint («<code>tuxpaint.pot</code>»), xa que se engade n novos textos e o texto antigo cambia ocasionalmente. O catálogo de texto para a próxima versión inédita de Tux Paint pódese atopar no repositorio Git de Tux Paint (ver: <a href="https://tuxpaint.org/download/source/git/">https://tuxpaint.org/download/source/git/</a>) e no sitio web de Tux Paint en <a href="https://tuxpaint.org/help/po/">https://tuxpaint.org/help/po/</a>. </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> It is best to always work off of the <i>latest</i> Tux Paint text catalog template ("<code>tuxpaint.pot</code>"), since new text is added, and old text is occasionally changed. The text catalog for the upcoming, unreleased version of Tux Paint can be found in Tux Paint's Git repository (see: <a href="https://tuxpaint.org/download/source/git/">https://tuxpaint.org/download/source/git/</a>), and on the Tux Paint website at <a href="https://tuxpaint.org/help/po/">https://tuxpaint.org/help/po/</a>. </p>
|
||||
|
||||
<p>
|
||||
Para editar unha tradución existente, descargue o último ficheiro «<code>.po</code>» para ese idioma e edíteo como se describe anteriormente. </p>
|
||||
|
|
@ -794,8 +794,8 @@
|
|||
<p>
|
||||
Como alternativa, se te unha conta con <a href="http://www.sourceforge.net/">SourceForge.net</a>, pode solicitar que o engadan ao proxecto «<code>tuxpaint</code>» e recibir acceso de escritura ao repositorio de código fonte de Git para que poida enviar os seus cambios directamente. </p>
|
||||
|
||||
<p>
|
||||
<i>Nota:</i> A compatibilidade cos novo configuracións locais require facer adicións ao código fonte de Tux Paint («<code>/src/i18n.h</code>» e «<code>/src/i18n.c</code>»), e require actualizacións dos <code>Makefile</code>, para asegurarse de que os ficheiros «<code>.po</code>» están compilados en ficheiros «<code>.mo</code>» e están dispoñíbeis para o seu uso en tempo de execución. </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> Support for new configuracións locais requires making additions to Tux Paint's source code («<code>/src/i18n.h</code>» e «<code>/src/i18n.c</code>»), and requires updates to the <code>Makefile</code>, para asegurarse de que os ficheiros «<code>.po</code>» están compilados en ficheiros «<code>.mo</code>» e están dispoñíbeis para o seu uso en tempo de execución. </p>
|
||||
</section><!-- H1: Translations -->
|
||||
|
||||
<section class="indent outer"><!-- H1: Alternative Input Methods -->
|
||||
|
|
@ -849,14 +849,14 @@
|
|||
</blockquote>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
<i>Nota:</i> Ignoraranse as liñas en branco dentro do ficheiro «<code>.im</code>», así como calquera texto que teña un carácter «<code>#</code>» (grella). Isto pódese usar para denotar comentarios , como se ve no exemplo anterior. </p>
|
||||
<p class="note">
|
||||
<span title="Configuration option">⚙</span> <strong>Note:</strong> Blank lines within the "<code>.im</code>" file will be ignored, as will any text following a "<code>#</code>" (pound/hash) character — it can be used to denote comments, as seen in the example above. </p>
|
||||
|
||||
<p>
|
||||
<i>Nota:</i> Os significados dos sinaladores son específicos da configuración local e son procesados polo código fonte específico do idioma en «<code>src/im.c</code>». Por exemplo, «<code>b</code>» úsase en coreano para tratar Batchim, que pode pasar ao seguinte carácter. </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> Meanings of the flags are locale-specific, and are processed by the language-specific source code in "<code>src/im.c</code>". For example, "<code>b</code>" is used in Korean to handle Batchim, which may carry over to the next character. </p>
|
||||
|
||||
<p>
|
||||
<i>Nota:</i> A compatibilidade cos novo input methods require facer adicións ao código fonte de Tux Paint ("<code>/src/im.c</code>"), e require actualizacións dos <code>Makefile</code>, para asegurarse de que os ficheiros «<code>.im</code>» están dispoñíbeis para o seu uso en tempo de execución. </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> Support for new input methods requires making additions to Tux Paint's source code ("<code>/src/im.c</code>"), and requires updates to the <code>Makefile</code>, para asegurarse de que os ficheiros «<code>.im</code>» están dispoñíbeis para o seu uso en tempo de execución. </p>
|
||||
</section><!-- H1: Alternative Input Methods -->
|
||||
|
||||
<section class="indent outer"><!-- H1: On-screen Keyboard -->
|
||||
|
|
@ -891,8 +891,8 @@
|
|||
</p>
|
||||
</blockquote>
|
||||
|
||||
<p>
|
||||
<i>Nota:</i> Ignoraranse as liñas en branco dentro do ficheiro «<code>.layout</code>», así como calquera texto que teña un carácter «<code>#</code>» (grella). Isto pódese usar para denotar comentarios , como se ve no exemplo anterior. </p>
|
||||
<p class="note">
|
||||
<span title="Configuration option">⚙</span> <strong>Note:</strong> Blank lines within the "<code>.layout</code>" file will be ignored, as will any text following a "<code>#</code>" (pound/hash) character — it can be used to denote comments, as seen in the example above. </p>
|
||||
|
||||
<p>
|
||||
A liña «<code>keyboardlist</code>» describe a que esquemas cambiar, cando o usuario preme nos botóns esquerdo e dereito do teclado. (Ver máis abaixo.) </p>
|
||||
|
|
@ -1046,8 +1046,8 @@
|
|||
<p>
|
||||
Este ficheiro (que é un ficheiro de cabeceira da linguaxe de programación <cite>C</cite>) tamén é do <cite>Sistema X Window</cite>. Define os valores Unicode de cada tecla (p. ex.: «<code>XK_equal</code>» corresponde a «<code>U+003D</code>», para o carácter «<code>=</code>» («<code>EQUALS SIGN</code>»). </p>
|
||||
|
||||
<p>
|
||||
<b>Nota:</b> este ficheiro non se compila en Tux Paint, senón que se le e analiza no tempo de execución. </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> This file is not compiled into Tux Paint, but is read and parsed at runtime. </p>
|
||||
|
||||
<p>
|
||||
É pouco probábel que se precise algunha modificación neste ficheiro. </p>
|
||||
|
|
|
|||
|
|
@ -54,7 +54,7 @@
|
|||
padding-bottom: 1em;
|
||||
border-bottom: 2px solid #000;
|
||||
}
|
||||
section.indent p,dl {
|
||||
section.indent p,dl,ul {
|
||||
margin-left: 2em;
|
||||
}
|
||||
section.indent dl p {
|
||||
|
|
|
|||
|
|
@ -54,7 +54,7 @@
|
|||
padding-bottom: 1em;
|
||||
border-bottom: 2px solid #000;
|
||||
}
|
||||
section.indent p,dl {
|
||||
section.indent p,dl,ul {
|
||||
margin-left: 2em;
|
||||
}
|
||||
section.indent dl p {
|
||||
|
|
|
|||
|
|
@ -36,7 +36,7 @@
|
|||
and other content used by Tux Paint, you can do so fairly easily by simply
|
||||
adding, changing, or removing files where Tux Paint looks for them.
|
||||
|
||||
Note: You'll need to re-launch Tux Paint for the changes to take effect.
|
||||
💡 Note: You'll need to re-launch Tux Paint for the changes to take effect.
|
||||
|
||||
Where Files Go
|
||||
|
||||
|
|
@ -87,7 +87,7 @@ Standard Files
|
|||
will make the content available to any user that launches
|
||||
this copy (icon) of Tux Paint.
|
||||
|
||||
Note: If you install a newer version of Tux Paint and replace or
|
||||
💡 Note: If you install a newer version of Tux Paint and replace or
|
||||
discard the old version, you will lose changes made by following
|
||||
the instructions above, so keep backups of your new content
|
||||
(stamps, brushes, etc.).
|
||||
|
|
@ -185,7 +185,7 @@ Brush Options
|
|||
Add a line containing the line "frames=N" to the brush's data
|
||||
file, where "N" is the number of frames in the brush.
|
||||
|
||||
Note: If you'd rather the frames be flipped through randomly,
|
||||
⚙ Note: If you'd rather the frames be flipped through randomly,
|
||||
rather than sequentially, also add a line containing "random" to
|
||||
the brush's data file.
|
||||
|
||||
|
|
@ -228,7 +228,7 @@ Brush Options
|
|||
Place the brush image PNGs (and any data text files) in the "brushes"
|
||||
directory.
|
||||
|
||||
Note: If your new brushes all come out as solid squares or rectangles,
|
||||
💡 Note: If your new brushes all come out as solid squares or rectangles,
|
||||
it's because you forgot to use alpha transparency! See the 'PNG
|
||||
documentation' in Tux Paint for more information and tips.
|
||||
|
||||
|
|
@ -255,17 +255,17 @@ Stamp Images
|
|||
SVGs are vector-based, and will be scaled appropriately for the canvas
|
||||
size being used in Tux Paint.
|
||||
|
||||
Note: If your new PNG-based stamps all come out as solid squares or
|
||||
💡 Note: If your new PNG-based stamps all come out as solid squares or
|
||||
rectangles, it's because you forgot to use alpha transparency! See the
|
||||
'PNG documentation' in Tux Paint for more information and tips.
|
||||
|
||||
Note: If your new SVG stamps seem to have a lot of whitespace, make sure
|
||||
💡 Note: If your new SVG stamps seem to have a lot of whitespace, make sure
|
||||
the SVG 'document' is no larger than the shape(s) within. If they are
|
||||
being clipped, make sure the 'document' is large enough to contain the
|
||||
shape(s). See the 'SVG documentation' in Tux Paint for more information
|
||||
and tips.
|
||||
|
||||
Advanced Users: The 'Advanced Stamps How-To' document describes, in
|
||||
⚙ Advanced Users: The 'Advanced Stamps How-To' document describes, in
|
||||
detail, how to make PNG images which will scale perfectly when used as
|
||||
stamps in Tux Paint.
|
||||
|
||||
|
|
@ -329,7 +329,7 @@ Stamp Sound Effects
|
|||
If no localized sound effect can be loaded, Tux Paint will attempt
|
||||
to load the 'default' sound file. (e.g., "stamp.wav")
|
||||
|
||||
Note: Also consider using descriptive sounds; see 'Stamp Descriptive
|
||||
💡 Note: Also consider using descriptive sounds; see 'Stamp Descriptive
|
||||
Sound', below.
|
||||
|
||||
Stamp Descriptive Sound
|
||||
|
|
@ -507,7 +507,7 @@ Pre-Mirrored and Flipped Stamps
|
|||
"_flip" in the name, and/or an image that is both mirrored and flipped, by
|
||||
naming it "_mirror_flip".
|
||||
|
||||
Note: If the user flips and mirrors an image, and a pre-drawn
|
||||
💡 Note: If the user flips and mirrors an image, and a pre-drawn
|
||||
"_mirror_flip" doesn't exist, but either "_flip" or "_mirror" does, it
|
||||
will be used, and mirrored or flipped, respectively.
|
||||
|
||||
|
|
@ -578,7 +578,7 @@ Scene-Style Starters
|
|||
in Tux Paint, the 'starter' images will appear in the screen that appears,
|
||||
after the various solid color choices.
|
||||
|
||||
Note: 'Starters' are 'attached' to saved pictures, via a small text file
|
||||
💡 Note: 'Starters' are 'attached' to saved pictures, via a small text file
|
||||
that has the same name as the saved file, but with ".dat" as the
|
||||
extension. This allows it to continue to affect the drawing even after Tux
|
||||
Paint has been quit, or another picture is loaded or a new image is
|
||||
|
|
@ -615,8 +615,8 @@ Scene-Style Starters
|
|||
in Tux Paint, the 'template' images will appear in the screen that
|
||||
appears, after the various solid color choices.
|
||||
|
||||
Note: 'Templates' are 'attached' to saved pictures, via a small text file
|
||||
that has the same name as the saved file, but with ".dat" as the
|
||||
💡 Note: 'Templates' are 'attached' to saved pictures, via a small text
|
||||
file that has the same name as the saved file, but with ".dat" as the
|
||||
extension. This allows it to continue to affect the drawing even after Tux
|
||||
Paint has been quit, or another picture is loaded or a new image is
|
||||
created. (In other words, if you base a drawing on a 'template' image, it
|
||||
|
|
@ -657,7 +657,7 @@ Scene-Style Starters
|
|||
* Virtraal
|
||||
* Lokalize
|
||||
|
||||
Note: It is best to always work off of the latest Tux Paint text catalog
|
||||
💡 Note: It is best to always work off of the latest Tux Paint text catalog
|
||||
template ("tuxpaint.pot"), since new text is added, and old text is
|
||||
occasionally changed. The text catalog for the upcoming, unreleased
|
||||
version of Tux Paint can be found in Tux Paint's Git repository (see:
|
||||
|
|
@ -676,7 +676,7 @@ Scene-Style Starters
|
|||
the Git source code repository so that you may commit your changes
|
||||
directly.
|
||||
|
||||
Note: Support for new locales requires making additions to Tux Paint's
|
||||
💡 Note: Support for new locales requires making additions to Tux Paint's
|
||||
source code ("/src/i18n.h" and "/src/i18n.c"), and requires updates to the
|
||||
Makefile, to ensure the ".po" files are compiled into ".mo" files, and
|
||||
available for use at runtime.
|
||||
|
|
@ -730,15 +730,15 @@ Scene-Style Starters
|
|||
30AD ki -
|
||||
30AE gi -
|
||||
|
||||
Note: Blank lines within the ".im" file will be ignored, as will any text
|
||||
following a "#" (pound/hash) character — it can be used to denote
|
||||
⚙ Note: Blank lines within the ".im" file will be ignored, as will any
|
||||
text following a "#" (pound/hash) character — it can be used to denote
|
||||
comments, as seen in the example above.
|
||||
|
||||
Note: Meanings of the flags are locale-specific, and are processed by the
|
||||
language-specific source code in "src/im.c". For example, "b" is used in
|
||||
Korean to handle Batchim, which may carry over to the next character.
|
||||
💡 Note: Meanings of the flags are locale-specific, and are processed by
|
||||
the language-specific source code in "src/im.c". For example, "b" is used
|
||||
in Korean to handle Batchim, which may carry over to the next character.
|
||||
|
||||
Note: Support for new input methods requires making additions to Tux
|
||||
💡 Note: Support for new input methods requires making additions to Tux
|
||||
Paint's source code ("/src/im.c"), and requires updates to the Makefile,
|
||||
to ensure the ".im" files are available for use at runtime.
|
||||
|
||||
|
|
@ -764,7 +764,7 @@ Layout overview file ("qwerty.layout")
|
|||
keysymdefs keysymdef.h
|
||||
keyboardlist qwerty.layout default.layout
|
||||
|
||||
Note: Blank lines within the ".layout" file will be ignored, as will any
|
||||
⚙ Note: Blank lines within the ".layout" file will be ignored, as will any
|
||||
text following a "#" (pound/hash) character — it can be used to denote
|
||||
comments, as seen in the example above.
|
||||
|
||||
|
|
@ -892,7 +892,7 @@ Keysym definitions file ("keysymdef.h")
|
|||
X Window System. It defines the Unicode values of each keycap (e.g.,
|
||||
"XK_equal" corresponds to "U+003D", for the character "=" ("EQUALS SIGN").
|
||||
|
||||
Note: This file is not compiled into Tux Paint, but is read and parsed at
|
||||
runtime.
|
||||
💡 Note: This file is not compiled into Tux Paint, but is read and parsed
|
||||
at runtime.
|
||||
|
||||
It is unlikely that any modification will be required of this file.
|
||||
|
|
|
|||
|
|
@ -54,7 +54,7 @@
|
|||
padding-bottom: 1em;
|
||||
border-bottom: 2px solid #000;
|
||||
}
|
||||
section.indent p,dl {
|
||||
section.indent p,dl,ul {
|
||||
margin-left: 2em;
|
||||
}
|
||||
section.indent dl p {
|
||||
|
|
@ -128,12 +128,12 @@
|
|||
</table>
|
||||
</section>
|
||||
|
||||
<section>
|
||||
<section class="outer">
|
||||
<p>
|
||||
If you wish to add or change things like Brushes, Starters, Rubber Stamps, and other content used by Tux Paint, you can do so fairly easily by simply adding, changing, or removing files where Tux Paint looks for them. </p>
|
||||
|
||||
<p>
|
||||
Note: You'll need to re-launch Tux Paint for the changes to take effect. </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> You'll need to re-launch Tux Paint for the changes to take effect. </p>
|
||||
</section>
|
||||
|
||||
<section class="indent outer"><!-- H1: Where Files Go -->
|
||||
|
|
@ -195,8 +195,8 @@
|
|||
<li>
|
||||
There, you will find various sub-folders, such as "starters", "stamps", "brushes", etc. Adding new content to these folders will make the content available to any user that launches this copy (icon) of Tux Paint. </li>
|
||||
</ol>
|
||||
<p>
|
||||
<em>Note:</em> If you install a newer version of Tux Paint and replace or discard the old version, you will lose changes made by following the instructions above, so keep backups of your new content (stamps, brushes, etc.). </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <em>Note:</em> If you install a newer version of Tux Paint and replace or discard the old version, you will lose changes made by following the instructions above, so keep backups of your new content (stamps, brushes, etc.). </p>
|
||||
<p>
|
||||
Tux Paint also looks for files in a "TuxPaint" folder that you can place in your system's "Application Support" folder (found under "Library" at the root of your filesystem): <blockquote>
|
||||
<code style="white-space: nowrap;">/Library/Application Support/TuxPaint/</code>
|
||||
|
|
@ -313,8 +313,8 @@
|
|||
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>
|
||||
<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>
|
||||
<b>Note:</b> If you'd rather the frames be flipped through randomly, rather than sequentially, also add a line containing "<code><b>random</b></code>" to the brush's data file. </p>
|
||||
<p class="note">
|
||||
<span title="Configuration option">⚙</span> <strong>Note:</strong> If you'd rather the frames be flipped through randomly, rather than sequentially, also add a line containing "<code><b>random</b></code>" to the brush's data file. </p>
|
||||
</dd>
|
||||
|
||||
<dt><strong>Directional Brushes</strong></dt>
|
||||
|
|
@ -348,8 +348,8 @@
|
|||
<p>
|
||||
Place the brush image PNGs (and any data text files) in the "<code><b>brushes</b></code>" directory. </p>
|
||||
|
||||
<p>
|
||||
Note: If your new brushes all come out as solid squares or rectangles, it's because you forgot to use alpha transparency! See the 'PNG documentation' in Tux Paint for more information and tips. </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> If your new brushes all come out as solid squares or rectangles, it's because you forgot to use alpha transparency! See the 'PNG documentation' in Tux Paint for more information and tips. </p>
|
||||
</section><!-- H1: Brushes -->
|
||||
|
||||
<section class="indent outer"><!-- H1: Stamps -->
|
||||
|
|
@ -387,14 +387,14 @@
|
|||
<p>
|
||||
SVGs are vector-based, and will be scaled appropriately for the canvas size being used in Tux Paint. </p>
|
||||
|
||||
<p>
|
||||
Note: If your new PNG-based stamps all come out as solid squares or rectangles, it's because you forgot to use alpha transparency! See the 'PNG documentation' in Tux Paint for more information and tips. </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> If your new PNG-based stamps all come out as solid squares or rectangles, it's because you forgot to use alpha transparency! See the 'PNG documentation' in Tux Paint for more information and tips. </p>
|
||||
|
||||
<p>
|
||||
Note: If your new SVG stamps seem to have a lot of whitespace, make sure the SVG 'document' is no larger than the shape(s) within. If they are being clipped, make sure the 'document' is large enough to contain the shape(s). See the 'SVG documentation' in Tux Paint for more information and tips. </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> If your new SVG stamps seem to have a lot of whitespace, make sure the SVG 'document' is no larger than the shape(s) within. If they are being clipped, make sure the 'document' is large enough to contain the shape(s). See the 'SVG documentation' in Tux Paint for more information and tips. </p>
|
||||
|
||||
<p>
|
||||
<b>Advanced Users:</b> The 'Advanced Stamps How-To' document describes, in detail, how to make PNG images which will scale perfectly when used as stamps in Tux Paint. </p>
|
||||
<p class="note">
|
||||
<span title="Configuration option">⚙</span> <b>Advanced Users:</b> The 'Advanced Stamps How-To' document describes, in detail, how to make PNG images which will scale perfectly when used as stamps in Tux Paint. </p>
|
||||
</section><!-- H2: Stamp Images -->
|
||||
|
||||
<section><!-- H2: Stamp Descriptive Text -->
|
||||
|
|
@ -455,8 +455,8 @@
|
|||
</dd>
|
||||
</dl>
|
||||
|
||||
<p>
|
||||
Note: Also consider using descriptive sounds; see 'Stamp Descriptive Sound', below. </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> Also consider using descriptive sounds; see 'Stamp Descriptive Sound', below. </p>
|
||||
</section><!-- H2: Stamp Sound Effects -->
|
||||
|
||||
<section><!-- H2: Stamp Descriptive Sound -->
|
||||
|
|
@ -619,8 +619,8 @@
|
|||
<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>
|
||||
|
||||
<p>
|
||||
<b>Note:</b> 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>
|
||||
<p class="note">
|
||||
<span title="Information">💡</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>
|
||||
</section><!-- H2: Pre-Mirrored and Flipped Stamps -->
|
||||
</section><!-- H1: Stamps -->
|
||||
|
||||
|
|
@ -705,8 +705,8 @@
|
|||
<p>
|
||||
Place them in the "<code><b>starters</b></code>" directory. When the 'New' dialog is accessed in Tux Paint, the 'starter' images will appear in the screen that appears, after the various solid color choices. </p>
|
||||
|
||||
<p>
|
||||
<b>Note:</b> 'Starters' are 'attached' to saved pictures, via a small text file that has the same name as the saved file, but with "<code>.dat</code>" as the extension. This allows it to continue to affect the drawing even after Tux Paint has been quit, or another picture is loaded or a new image is created. (In other words, if you base a drawing on a 'starter' image, it will always be affected by it.) </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> 'Starters' are 'attached' to saved pictures, via a small text file that has the same name as the saved file, but with "<code>.dat</code>" as the extension. This allows it to continue to affect the drawing even after Tux Paint has been quit, or another picture is loaded or a new image is created. (In other words, if you base a drawing on a 'starter' image, it will always be affected by it.) </p>
|
||||
</section><!-- H1: Starters -->
|
||||
|
||||
<section class="indent outer"><!-- H1: 'Templates' -->
|
||||
|
|
@ -740,8 +740,8 @@
|
|||
<p>
|
||||
Place them in the "<code><b>templates</b></code>" directory. When the 'New' dialog is accessed in Tux Paint, the 'template' images will appear in the screen that appears, after the various solid color choices. </p>
|
||||
|
||||
<p>
|
||||
<b>Note:</b> 'Templates' are 'attached' to saved pictures, via a small text file that has the same name as the saved file, but with "<code>.dat</code>" as the extension. This allows it to continue to affect the drawing even after Tux Paint has been quit, or another picture is loaded or a new image is created. (In other words, if you base a drawing on a 'template' image, it will always be affected by it.) </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> 'Templates' are 'attached' to saved pictures, via a small text file that has the same name as the saved file, but with "<code>.dat</code>" as the extension. This allows it to continue to affect the drawing even after Tux Paint has been quit, or another picture is loaded or a new image is created. (In other words, if you base a drawing on a 'template' image, it will always be affected by it.) </p>
|
||||
<br clear="all">
|
||||
</section><!-- H1: 'Templates' -->
|
||||
|
||||
|
|
@ -782,8 +782,8 @@
|
|||
</ul>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
<i>Note:</i> It is best to always work off of the <i>latest</i> Tux Paint text catalog template ("<code>tuxpaint.pot</code>"), since new text is added, and old text is occasionally changed. The text catalog for the upcoming, unreleased version of Tux Paint can be found in Tux Paint's Git repository (see: <a href="https://tuxpaint.org/download/source/git/">https://tuxpaint.org/download/source/git/</a>), and on the Tux Paint website at <a href="https://tuxpaint.org/help/po/">https://tuxpaint.org/help/po/</a>. </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> It is best to always work off of the <i>latest</i> Tux Paint text catalog template ("<code>tuxpaint.pot</code>"), since new text is added, and old text is occasionally changed. The text catalog for the upcoming, unreleased version of Tux Paint can be found in Tux Paint's Git repository (see: <a href="https://tuxpaint.org/download/source/git/">https://tuxpaint.org/download/source/git/</a>), and on the Tux Paint website at <a href="https://tuxpaint.org/help/po/">https://tuxpaint.org/help/po/</a>. </p>
|
||||
|
||||
<p>
|
||||
To edit an existing translation, download the latest "<code>.po</code>" file for that language, and edit it as described above. </p>
|
||||
|
|
@ -794,8 +794,8 @@
|
|||
<p>
|
||||
Alternatively, if you have an account with <a href="http://www.sourceforge.net/">SourceForge.net</a>, you can request to be added to the "<code>tuxpaint</code>" project and receive write-access to the Git source code repository so that you may commit your changes directly. </p>
|
||||
|
||||
<p>
|
||||
<i>Note:</i> Support for new locales requires making additions to Tux Paint's source code ("<code>/src/i18n.h</code>" and "<code>/src/i18n.c</code>"), and requires updates to the <code>Makefile</code>, to ensure the "<code>.po</code>" files are compiled into "<code>.mo</code>" files, and available for use at runtime. </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> Support for new locales requires making additions to Tux Paint's source code ("<code>/src/i18n.h</code>" and "<code>/src/i18n.c</code>"), and requires updates to the <code>Makefile</code>, to ensure the "<code>.po</code>" files are compiled into "<code>.mo</code>" files, and available for use at runtime. </p>
|
||||
</section><!-- H1: Translations -->
|
||||
|
||||
<section class="indent outer"><!-- H1: Alternative Input Methods -->
|
||||
|
|
@ -849,14 +849,14 @@
|
|||
</blockquote>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
<i>Note:</i> Blank lines within the "<code>.im</code>" file will be ignored, as will any text following a "<code>#</code>" (pound/hash) character — it can be used to denote comments, as seen in the example above. </p>
|
||||
<p class="note">
|
||||
<span title="Configuration option">⚙</span> <strong>Note:</strong> Blank lines within the "<code>.im</code>" file will be ignored, as will any text following a "<code>#</code>" (pound/hash) character — it can be used to denote comments, as seen in the example above. </p>
|
||||
|
||||
<p>
|
||||
<i>Note:</i> Meanings of the flags are locale-specific, and are processed by the language-specific source code in "<code>src/im.c</code>". For example, "<code>b</code>" is used in Korean to handle Batchim, which may carry over to the next character. </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> Meanings of the flags are locale-specific, and are processed by the language-specific source code in "<code>src/im.c</code>". For example, "<code>b</code>" is used in Korean to handle Batchim, which may carry over to the next character. </p>
|
||||
|
||||
<p>
|
||||
<i>Note:</i> Support for new input methods requires making additions to Tux Paint's source code ("<code>/src/im.c</code>"), and requires updates to the <code>Makefile</code>, to ensure the "<code>.im</code>" files are available for use at runtime. </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> Support for new input methods requires making additions to Tux Paint's source code ("<code>/src/im.c</code>"), and requires updates to the <code>Makefile</code>, to ensure the "<code>.im</code>" files are available for use at runtime. </p>
|
||||
</section><!-- H1: Alternative Input Methods -->
|
||||
|
||||
<section class="indent outer"><!-- H1: On-screen Keyboard -->
|
||||
|
|
@ -891,8 +891,8 @@
|
|||
</p>
|
||||
</blockquote>
|
||||
|
||||
<p>
|
||||
<i>Note:</i> Blank lines within the "<code>.layout</code>" file will be ignored, as will any text following a "<code>#</code>" (pound/hash) character — it can be used to denote comments, as seen in the example above. </p>
|
||||
<p class="note">
|
||||
<span title="Configuration option">⚙</span> <strong>Note:</strong> Blank lines within the "<code>.layout</code>" file will be ignored, as will any text following a "<code>#</code>" (pound/hash) character — it can be used to denote comments, as seen in the example above. </p>
|
||||
|
||||
<p>
|
||||
The "<code>keyboardlist</code>" line describes which layouts to switch to, when the user clicks the left and right buttons on the keyboard. (See below.) </p>
|
||||
|
|
@ -1046,8 +1046,8 @@
|
|||
<p>
|
||||
This file (which is a <cite>C</cite> programming language header file) is also from the <cite>X Window System</cite>. It defines the Unicode values of each keycap (e.g., "<code>XK_equal</code>" corresponds to "<code>U+003D</code>", for the character "<code>=</code>" ("<code>EQUALS SIGN</code>"). </p>
|
||||
|
||||
<p>
|
||||
<b>Note:</b> This file is not compiled into Tux Paint, but is read and parsed at runtime. </p>
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> This file is not compiled into Tux Paint, but is read and parsed at runtime. </p>
|
||||
|
||||
<p>
|
||||
It is unlikely that any modification will be required of this file. </p>
|
||||
|
|
|
|||
|
|
@ -54,7 +54,7 @@
|
|||
padding-bottom: 1em;
|
||||
border-bottom: 2px solid #000;
|
||||
}
|
||||
section.indent p,dl {
|
||||
section.indent p,dl,ul {
|
||||
margin-left: 2em;
|
||||
}
|
||||
section.indent dl p {
|
||||
|
|
|
|||
|
|
@ -54,7 +54,7 @@
|
|||
padding-bottom: 1em;
|
||||
border-bottom: 2px solid #000;
|
||||
}
|
||||
section.indent p,dl {
|
||||
section.indent p,dl,ul {
|
||||
margin-left: 2em;
|
||||
}
|
||||
section.indent dl p {
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue