'Starter' images appear in the 'New' dialog, along with
solid color background choices. (Note: In earlier versions
- of Tux Paint, they appeared in the 'Open' dialog,
- together with saved drawings.)
+ of Tux Paint,
+ they appeared in the 'Open' dialog, together with saved
+ drawings.)
The most basic kind of 'starter' is similar to a picture
in a coloring book. It's an outline of a shape which you
- can then color in and add details to. In Tux Paint,
- as you draw, type text, or stamp stamps, the outline
- remains 'above' what you draw. You can erase the parts of
- the drawing you made, but you can't erase the outline.
+ can then color in and add details to. In Tux Paint, as you draw,
+ type text, or stamp stamps, the outline remains 'above'
+ what you draw. You can erase the parts of the drawing you
+ made, but you can't erase the outline.
To create this kind of 'starter' image, simply draw an
outlined picture in a paint program, make the rest of the
graphic transparent (that will come out as white in
- Tux Paint), and save it as a PNG format file.
+ Tux Paint), and
+ save it as a PNG format file.
@@ -1186,9 +1239,8 @@
@@ -1231,29 +1283,31 @@
The 'starter' images should be the same size as
- Tux Paint's canvas.
- (See the "Loading Other Pictures into
- Tux Paint" section of
- README for details on sizing.) If they
- are not, they will be stretched, without affecting the
+ Tux Paint's
+ canvas. (See the "Loading Other Pictures into Tux Paint" section of
+ README for details on sizing.) If
+ they are not, they will be stretched, without affecting the
shape ("aspect ratio"); however some smudging may be
applied to the edges.
Place them in the "starters" 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.
+ 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.
Note: 'Starters' can't be saved over from within
- Tux Paint, since loading a 'starter' is really like
- creating a new image. (Instead of being blank, though
- there's already something there to work with.) The 'Save'
- command simply creates a new picture, like it would if the
- 'New' command had been used.
+ Tux Paint, since
+ loading a 'starter' is really like creating a new image.
+ (Instead of being blank, though there's already something
+ there to work with.) The 'Save' command simply creates a
+ new picture, like it would if the 'New' command had been
+ used.
@@ -1261,9 +1315,10 @@
via a small text file that has the same name as the saved
file, but with ".dat" as the extension. This
allows the overlay and background, if any, to continue to
- affect the drawing even after Tux Paint has been quit,
- or another picture loaded or started. (In other words, if
- you base a drawing on a 'starter' image, it will always be
+ affect the drawing even after Tux Paint has been quit, or
+ another picture loaded or started. (In other words, if you
+ base a drawing on a 'starter' image, it will always be
affected by it.)
@@ -1273,9 +1328,8 @@
noshade>
@@ -1287,12 +1341,13 @@
'Template' images also appear in the 'New' dialog, along
with solid color background choices and 'Starters'. (Note:
- Tux Paint prior to version 0.9.22 did not have the
- 'Template' feature.)
+ Tux Paint prior
+ to version 0.9.22 did not have the 'Template' feature.)
- Unlike pictures drawn in Tux Paint by users and then
+ Unlike pictures drawn in Tux Paint by users and then
opened later, opening a 'template' creates a new drawing.
When you save, the 'template' image is not overwritten.
Unlike 'starters', there is no immutable 'layer' above the
@@ -1313,10 +1368,11 @@
The 'template' images should be the same size as
- Tux Paint's canvas.
- (See the "Loading Other Pictures into Tux Paint"
- section of README for details on sizing.) If they
- are not, they will be stretched, without affecting the
+ Tux Paint's
+ canvas. (See the "Loading Other Pictures into Tux Paint" section of
+ README for details on sizing.) If
+ they are not, they will be stretched, without affecting the
shape ("aspect ratio"); however some smudging may be
applied to the edges.
@@ -1324,18 +1380,19 @@
Place them in the "templates"
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
- and 'starters'.
+ Tux Paint, the
+ 'template' images will appear in the screen that appears,
+ after the various solid color choices and 'starters'.
Note: 'Templates' can't be saved over from within
- Tux Paint, since loading a 'template' is really like
- creating a new image. (Instead of being blank, though
- there's already something there to work with.) The 'Save'
- command simply creates a new picture, like it would if the
- 'New' command had been used.
+ Tux Paint, since
+ loading a 'template' is really like creating a new image.
+ (Instead of being blank, though there's already something
+ there to work with.) The 'Save' command simply creates a
+ new picture, like it would if the 'New' command had been
+ used.
@@ -1344,9 +1401,10 @@
file, but with ".dat" as the extension. This
allows the background to continue to be available to the
drawing (e.g., when using the 'Eraser' tool) even after
- Tux Paint has been quit, or another picture loaded or
- started. (In other words, if you base a drawing on a
- 'template' image, it will always be affected by it.)
+ Tux Paint has
+ been quit, or another picture loaded or started. (In other
+ words, if you base a drawing on a 'template' image, it will
+ always be affected by it.)
@@ -1355,39 +1413,42 @@
noshade>
- Tux Paint supports numerous languages, thanks to use of the
- "gettext" localization library. (See OPTIONS
- for how to change locales in
+ Tux Paint
+ supports numerous languages, thanks to use of the "gettext"
+ localization library. (See OPTIONS for how to change locales in
Tux Paint.)
- To translate Tux Paint to a new language, copy the
- translation template file, "tuxpaint.pot"
- (found in Tux Paint's source code, in the folder
- "src/po/"). Rename the copy as a
- ".po" file, with an appropriate name for the
- locale you're translating to (e.g., "es.po"
- for Spanish; or "pt_BR.po" for
- Brazilian Portuguese,
- versus "pt.po" or
- "pt_PT.po" for Portuguese spoken in Portugal.)
+ To translate Tux
+ Paint to a new language, copy the translation
+ template file, "tuxpaint.pot" (found in
+ Tux Paint's
+ source code, in the folder "src/po/"). Rename
+ the copy as a ".po" file, with an appropriate
+ name for the locale you're translating to (e.g.,
+ "es.po" for Spanish; or
+ "pt_BR.po" for Brazilian Portuguese, versus
+ "pt.po" or "pt_PT.po" for
+ Portuguese spoken in Portugal.)
Open the newly-created ".po" file — you can
edit in a plain text edtior, such as Emacs, Pico or
VI on Linux, or NotePad on Windows. The original English
- text used in Tux Paint is listed in lines starting
- with "msgid". Enter your translations of each
- of these pieces of text in the empty "msgstr"
+ text used in Tux
+ Paint is listed in lines starting with
+ "msgid". Enter your translations of each of
+ these pieces of text in the empty "msgstr"
lines directly below the corresponding "msgid"
lines. (Note: Do not remove the quotes.)
@@ -1398,30 +1459,34 @@
-
- msgid "Smudge"
+ msgid "Smudge"
msgstr "Manchar"
msgid "Click and drag to draw large bricks."
- msgstr "Haz clic y arrastra para dibujar ladrillos grandes."
+ msgstr "Haz clic y arrastra para dibujar ladrillos
+ grandes."
A graphical tool, called poEdit (http://www.poedit.net/), is
- available for Linux, Windows and Mac OS X.
+ available for Linux, Windows and macOS.
Note: It is best to always work off of the
- latest Tux Paint text catalog template
+ 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: Tux Paint can be found in
+ Tux Paint's Git
+ repository (see: http://www.tuxpaint.org/download/source/git/),
- and on the Tux Paint website at Tux
+ Paint website at http://www.tuxpaint.org/help/po/.
@@ -1434,8 +1499,8 @@
You may send new or edited translation files to
Bill Kendrick,
- lead developer of Tux Paint, at:
- Tux
+ Paint, at: bill@newbreedsoftware.com,
or post them to the "tuxpaint-i18n" mailing list (see:
Note: Additional locale support also requires
- additions to Tux Paint's source code
- (/src/i18n.h and /src/i18n.c),
- and requires updates to the Makefile, to have
- the ".po" gettext catalog source files
- compiled into ".mo" files, and installed, for
- use at runtime.
+ additions to Tux
+ Paint's source code (/src/i18n.h and
+ /src/i18n.c), and requires updates to the
+ Makefile, to have the ".po"
+ gettext catalog source files compiled into
+ ".mo" files, and installed, for use at
+ runtime.
-
+
- As of version 0.9.17, Tux Paint's "Text" tool can
+ As of version 0.9.17, Tux Paint's "Text" tool can
provide alternative input methods for some languages. For
- example, when Tux Paint is running with a Japanese
- locale, the right [Alt] key can be pressed to
- cycle between Latin, Romanized Hiragana and Romanized
- Katakana modes. This allows native characters and words to
- be entered into the "Text" tool by typing one or more keys
- on a keyboard with Latin characters (e.g., a
+ example, when Tux
+ Paint is running with a Japanese locale, the
+ right [Alt] key can be
+ pressed to cycle between Latin, Romanized Hiragana and
+ Romanized Katakana modes. This allows native characters and
+ words to be entered into the "Text" tool by typing one or
+ more keys on a keyboard with Latin characters (e.g., a
US QWERTY
keyboard).
@@ -1493,11 +1561,11 @@
The ".im" file can have multiple character
mapping sections for different character mapping modes. For
- example, on a Japanese typing system, typing
- [K] [A]
- in Hiragana mode generates a
- different Unicode character than typing
- [K] [A] in Katakana mode.
+ example, on a Japanese typing system, typing [K] [A] in
+ Hiragana mode generates a different Unicode character than
+ typing [K]
+ [A] in Katakana mode.
@@ -1537,7 +1605,7 @@
304E gi -
304D:3083 kya -
3063:305F tta -
-
+
# Katakana
section
30AB ka -
@@ -1564,225 +1632,273 @@
Note: Additional input method support also requires
- additions to Tux Paint's source code
- (/src/im.c), and requires updates to the
- Makefile, to have the ".im" files
- installed, for use at runtime.
+ additions to Tux
+ Paint's source code (/src/im.c), and
+ requires updates to the Makefile, to have the
+ ".im" files installed, for use at runtime.
-
- As of version 0.9.22, Tux Paint's
- "Text" and "Label" tools can present an on-screen keyboard that allows
- the pointer (via a mouse, eye-tracking systems, etc.) to be used to
- input characters. Files that describe the layout and available keys
- are stored in
- Tux Paint's
- "osk" directory. Each keyboard layout is defined by a number
- of files (some of which may be shared by different layouts). We'll use
- the QWERTY keyboard as an example:
+ As of version 0.9.22, Tux Paint's "Text" and
+ "Label" tools can present an on-screen keyboard that allows
+ the pointer (via a mouse, eye-tracking systems, etc.) to be
+ used to input characters. Files that describe the layout
+ and available keys are stored in Tux Paint's
+ "osk" directory. Each keyboard layout is
+ defined by a number of files (some of which may be shared
+ by different layouts). We'll use the QWERTY keyboard as an
+ example:
- Layout overview file ("qwerty.layout")
+
+ Layout overview file ("qwerty.layout")
+
+
- This is a text file that specifies the other files used to describe the
- layout and key mappings.
+ This is a text file that specifies the other files used
+ to describe the layout and key mappings.
+
-
- layout qwerty.h_layout
- keymap us-intl-altgr-dead-keys.keymap
-
- composemap en_US.UTF-8_Compose
- keysymdefs keysymdef.h
- keyboardlist qwerty.layout default.layout
-
+ layout qwerty.h_layout
+ keymap us-intl-altgr-dead-keys.keymap
+
+ composemap en_US.UTF-8_Compose
+ keysymdefs keysymdef.h
+ keyboardlist qwerty.layout default.layout
+
- 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.
+ 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.
+
The "keyboardlist" line describes which
- layouts to switch to, when the user clicks the
- left and right buttons on the keyboard.
- (See below.)
+ layouts to switch to, when the user clicks the left and
+ right buttons on the keyboard. (See below.)
- Keyboard layout file ("qwerty.h_layout")
+
+ Keyboard layout file ("qwerty.h_layout")
+
+
- This describes how big the keyboard is (as a W×H grid),
- and lists each key with its numeric keycode (see the "keymap"
- file, below), the width it should be drawn at (typically
- "1.0", to take one space on the keyboard,
- but in the example below, notice the "TAB" and
- "SPACE" keys are much wider), the character or
- text to display on the key, depending on which modifier
- keys have been pressed (one each for: no modifiers,
- [Shift], [AltGr], and [Shift]+[AltGr]),
- and finally whether or not the key is affected by the
- [CapsLock] key (use "1") or
- [AltGr] (alternate graphics) key (use "2"),
- or not at all (use "0").
+ This describes how big the keyboard is (as a W×H grid),
+ and lists each key with its numeric keycode (see the
+ "keymap" file, below), the width it should be drawn at
+ (typically "1.0", to take one space on the
+ keyboard, but in the example below, notice the
+ "TAB" and "SPACE" keys are much
+ wider), the character or text to display on the key,
+ depending on which modifier keys have been pressed (one
+ each for: no modifiers, [Shift], [AltGr],
+ and [Shift]+[AltGr]), and finally whether or not
+ the key is affected by the [CapsLock] key (use
+ "1") or [AltGr] (alternate graphics)
+ key (use "2"), or not at all (use
+ "0").
+
-
- WIDTH 15
- HEIGHT 5
-
- KEY 49 1.0 ` ~ ` ~ 0
- KEY 10 1.0 1 ! ¡ ¹ 0
- KEY 11 1.0 2 @ ² ˝ 0
- KEY 12 1.0 3 # · ³ 0
- KEY 13 1.0 4 $ ¤ £ 0
- KEY 14 1.0 5 % € ¸ 0
- KEY 15 1.0 6 ^ ¼ ^ 0
- ...
- KEY 21 1.0 = + × ÷ 0
- KEY 22 2.0 DELETE DELETE DELETE DELETE 0
-
- NEWLINE
-
- KEY 23 1.5 TAB TAB TAB TAB 0
- KEY 24 1.0 q Q ä Ä 1
- KEY 25 1.0 w W å Å 1
- KEY 26 1.0 e E é É 1
- KEY 27 1.0 r R ® ® 1
- ...
-
- NEWLINE
-
- # Arrow to left will change to the previous keyboard
- KEY 2 1.0 <- <- <- <- 0
-
- KEY 133 2.0 Cmp Cmp Cmp Cmp 0
-
- # The ALT or ALTGR keys are used in im to switch the input mode.
- KEY 64 2.0 Alt Alt Alt Alt 0
-
- # Space
- KEY 65 7.0 SPACE SPACE SPACE SPACE 0
-
- KEY 108 2.0 AltGr AltGr AltGr AltGr 0
-
- # Arrow to right will change to the next keyboard
- KEY 1 1.0 -> -> -> -> 0
-
+ WIDTH 15
+ HEIGHT 5
+
+ KEY 49 1.0 ` ~ ` ~ 0
+ KEY 10 1.0 1 ! ¡ ¹ 0
+ KEY 11 1.0 2 @ ² ˝ 0
+ KEY 12 1.0 3 # · ³ 0
+ KEY 13 1.0 4 $ ¤ £ 0
+ KEY 14 1.0 5 % € ¸ 0
+ KEY 15 1.0 6 ^ ¼ ^ 0
+ ...
+ KEY 21 1.0 = + × ÷ 0
+ KEY 22 2.0 DELETE DELETE DELETE DELETE 0
+
+ NEWLINE
+
+ KEY 23 1.5 TAB TAB TAB TAB 0
+ KEY 24 1.0 q Q ä Ä 1
+ KEY 25 1.0 w W å Å 1
+ KEY 26 1.0 e E é É 1
+ KEY 27 1.0 r R ® ® 1
+ ...
+
+ NEWLINE
+
+ # Arrow to left will change to the previous
+ keyboard
+ KEY 2 1.0 <- <- <- <- 0
+
+ KEY 133 2.0 Cmp Cmp Cmp Cmp 0
+
+ # The ALT or ALTGR keys are used in im to switch the
+ input mode.
+ KEY 64 2.0 Alt Alt Alt Alt 0
+
+ # Space
+ KEY 65 7.0 SPACE SPACE SPACE SPACE 0
+
+ KEY 108 2.0 AltGr AltGr AltGr AltGr 0
+
+ # Arrow to right will change to the next keyboard
+ KEY 1 1.0 -> -> -> -> 0
+
- Notice here that alphabetic keys ([Q], [W], etc.)
- will be affected by [CapsLock], while numeric keys
- ([1], [2], etc.), [Space], and so on,
- will not.
+ Notice here that alphabetic keys ([Q], [W],
+ etc.) will be affected by [CapsLock], while
+ numeric keys ([1], [2], etc.),
+ [Space], and so on, will not.
+
- Keycodes up to "8" are reserved for internal use.
- The ones currently used are described below.
+ Keycodes up to "8" are reserved for internal
+ use. The ones currently used are described below.
+
-
-
0 — empty button
+ 0 — empty button
+
-
-
1 — next layout
- (per the layout file's "keyboardlist" setting)
+ 1 — next layout (per the layout file's
+ "keyboardlist" setting)
+
-
-
2 — previous layout
- (per the layout file's "keyboardlist" setting)
+ 2 — previous layout (per the layout file's
+ "keyboardlist" setting)
- Keymap file ("us-intl-altgr-dead-keys.keymap")
+
+ Keymap file ("us-intl-altgr-dead-keys.keymap")
+
+
This file defines which numeric keycodes (seen in the
- keyboard layout files, such as "qwerty.h_layout"
- described above) should be mapped to which actual characters
- that an application such as
- Tux Paint
- expects to receive when keys (e.g., on a real keyboard)
- are pressed.
+ keyboard layout files, such as
+ "qwerty.h_layout" described above) should be
+ mapped to which actual characters that an application
+ such as Tux
+ Paint expects to receive when keys (e.g., on a
+ real keyboard) are pressed.
+
- If you're using an operating system such as Linux,
- which runs X-Window and has the
- "xmodmap" command-line tool available, you can run
- it with the ("print keymap expressions"
+ If you're using an operating system such as
+ Linux, which runs X-Window and
+ has the "xmodmap" command-line tool
+ available, you can run it with the ("print keymap expressions"
option, "-pke", to generate a keymap file.
+
-
- keycode 9 = Escape NoSymbol Escape Escape
- keycode 10 = 1 exclam exclamdown onesuperior 1 exclam 1 exclam NoSymbol onesuperior
- keycode 11 = 2 at twosuperior dead_doubleacute 2 at 2 at onehalf twosuperior
- keycode 12 = 3 numbersign periodcentered threesuperior dead_macron periodcentered
- ...
- keycode 52 = z Z ae AE Arabic_hamzaonyeh asciitilde guillemotright NoSymbol Greek_zeta Greek_ZETA U037D U03FF
- keycode 53 = x X x X Arabic_hamza Arabic_sukun guillemotleft NoSymbol Greek_chi Greek_CHI rightarrow leftarrow
- keycode 54 = c C copyright cent Arabic_hamzaonwaw braceright Greek_psi Greek_PSI copyright
- keycode 55 = v V v V Arabic_ra braceleft Greek_omega Greek_OMEGA U03D6
- keycode 56 = b B b B UFEFB UFEF5 Greek_beta Greek_BETA U03D0
- keycode 57 = n N ntilde Ntilde Arabic_alefmaksura Arabic_maddaonalef Greek_nu Greek_NU U0374 U0375
- keycode 58 = m M mu mu Arabic_tehmarbuta apostrophe Greek_mu Greek_MU U03FB U03FA
- keycode 59 = comma less ccedilla Ccedilla Arabic_waw comma comma less guillemotleft
- keycode 60 = period greater dead_abovedot dead_caron Arabic_zain period period greater guillemotright periodcentered
- keycode 61 = slash question questiondown dead_hook Arabic_zah Arabic_question_mark slash question
- keycode 62 = Shift_R NoSymbol Shift_R Shift_R
- ...
-
+ keycode 9 = Escape NoSymbol Escape Escape
+ keycode 10 = 1 exclam exclamdown onesuperior 1 exclam 1
+ exclam NoSymbol onesuperior
+ keycode 11 = 2 at twosuperior dead_doubleacute 2 at 2
+ at onehalf twosuperior
+ keycode 12 = 3 numbersign periodcentered threesuperior
+ dead_macron periodcentered
+ ...
+ keycode 52 = z Z ae AE Arabic_hamzaonyeh asciitilde
+ guillemotright NoSymbol Greek_zeta Greek_ZETA U037D
+ U03FF
+ keycode 53 = x X x X Arabic_hamza Arabic_sukun
+ guillemotleft NoSymbol Greek_chi Greek_CHI rightarrow
+ leftarrow
+ keycode 54 = c C copyright cent Arabic_hamzaonwaw
+ braceright Greek_psi Greek_PSI copyright
+ keycode 55 = v V v V Arabic_ra braceleft Greek_omega
+ Greek_OMEGA U03D6
+ keycode 56 = b B b B UFEFB UFEF5 Greek_beta Greek_BETA
+ U03D0
+ keycode 57 = n N ntilde Ntilde Arabic_alefmaksura
+ Arabic_maddaonalef Greek_nu Greek_NU U0374 U0375
+ keycode 58 = m M mu mu Arabic_tehmarbuta apostrophe
+ Greek_mu Greek_MU U03FB U03FA
+ keycode 59 = comma less ccedilla Ccedilla Arabic_waw
+ comma comma less guillemotleft
+ keycode 60 = period greater dead_abovedot dead_caron
+ Arabic_zain period period greater guillemotright
+ periodcentered
+ keycode 61 = slash question questiondown dead_hook
+ Arabic_zah Arabic_question_mark slash question
+ keycode 62 = Shift_R NoSymbol Shift_R Shift_R
+ ...
- Composemap file ("en_US.UTF-8_Compose")
+
+ Composemap file ("en_US.UTF-8_Compose")
+
+
- This file describes characters that can be composed by multiple
- inputs. For example, "[Compose]" followed by "[A]" and
- "[E]" can be used to create the "æ" character.
+ This file describes characters that can be composed by
+ multiple inputs. For example, "[Compose]" followed
+ by "[A]" and "[E]" can be used to create
+ the "æ" character.
+
- The file that comes with Tux Paint
- is based on the US English UTF-8 (Unicode) composemap that
- comes with X.Org's X Window system.
- The current version from the Xlib library as a web page at
- https://www.x.org/releases/current/doc/libX11/i18n/compose/en_US.UTF-8.html).
+ The file that comes with Tux Paint is based on the
+ US English UTF-8 (Unicode) composemap that comes with
+ X.Org's X Window
+ system. The current version from the
+ Xlib library as a web page at
+ https://www.x.org/releases/current/doc/libX11/i18n/compose/en_US.UTF-8.html).
+
- Keysym definitions file ("keysymdef.h")
+
+ Keysym definitions file ("keysymdef.h")
+
+
This file (which is a C programming language
- header file) is also from the
- X Window System.
- It defines the Unicode values of each keycap
- (e.g., "XK_equal" corresponds to
+ header file) is also from the X Window System. It defines
+ the Unicode values of each keycap (e.g.,
+ "XK_equal" corresponds to
"U+003D", for the character "="
- ("EQUALS SIGN").
+ ("EQUALS
+ SIGN").
+
It is unlikely that any modification will be required of
this file.
@@ -1790,7 +1906,7 @@
-
-
+
Greyscale pixels in the brush PNG will be drawn using the
- currently-selected color in Tux Paint. Color pixels
- will be tinted.
+ currently-selected color in Tux Paint. Color pixels will
+ be tinted.
