notgne2/tuxpaint-pencil-sharpener
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

September 8th

Browse source 
Merge branch 'master' into sdl2.0
Many changes and improvements by Bill
This commit is contained in:
Pere Pujal i Carabantes 2021-09-08 00:10:35 +02:00
commit 10baa371dd
272 changed files with 54699 additions and 34028 deletions
Download patch file Download diff file Expand all files Collapse all files

93
Makefile
View file

@ -4,12 +4,12 @@
# Various contributors (see AUTHORS.txt)
# http://www.tuxpaint.org/
# June 14, 2002 - June 28, 2021
# June 14, 2002 - September 6, 2021
# The version number, for release:
VER_VERSION:=0.9.26
VER_VERSION:=0.9.27
ifdef SOURCE_DATE_EPOCH
VER_DATE=$(shell date -u -d "@$(SOURCE_DATE_EPOCH)" "+%Y-%m-%d" 2>/dev/null || date -u -r "$(SOURCE_DATE_EPOCH)" "+%Y-%m-%d" 2>/dev/null || date -u "+%Y-%m-%d")
else
@ -80,37 +80,36 @@ endif
# <HOSTROOT>/lib/pkgconfig *.pc files.
#
ifdef HOST
ifndef HOSTROOT
$(error Must set HOSTROOT to cross compile)
endif
ifeq ($(wildcard $(HOSTROOT)/.),)
$(error Invalid HOSTROOT: $(HOSTROOT))
endif
ifdef HOSTROOT
ifeq ($(wildcard $(HOSTROOT)/.),)
$(error Invalid HOSTROOT: $(HOSTROOT))
endif
ifeq ($(HOST),iphoneos)
OS:=ios
CC:=$(shell xcrun --sdk iphoneos -f clang)
SDK:=iphoneos
ARCHS:=arm64 armv7s armv7
MINVER:=9.0
MINVEROPT:=-miphoneos-version-min=$(MINVER)
SDKROOT:=$(shell xcrun --sdk iphoneos --show-sdk-path)
else ifeq ($(HOST),iphonesimulator)
OS:=ios
CC:=$(shell xcrun --sdk iphonesimulator -f clang)
SDK:=iphonesimulator
ARCHS:=$(shell uname -m)
MINVER:=9.0
MINVEROPT:=-mios-simulator-version-min=$(MINVER)
SDKROOT:=$(shell xcrun --sdk iphonesimulator --show-sdk-path)
else
$(error Invalid HOST: $(HOST))
endif
ifeq ($(HOST),iphoneos)
OS:=ios
CC:=$(shell xcrun --sdk iphoneos -f clang)
SDK:=iphoneos
ARCHS:=arm64 armv7s armv7
MINVER:=9.0
MINVEROPT:=-miphoneos-version-min=$(MINVER)
SDKROOT:=$(shell xcrun --sdk iphoneos --show-sdk-path)
else ifeq ($(HOST),iphonesimulator)
OS:=ios
CC:=$(shell xcrun --sdk iphonesimulator -f clang)
SDK:=iphonesimulator
ARCHS:=$(shell uname -m)
MINVER:=9.0
MINVEROPT:=-mios-simulator-version-min=$(MINVER)
SDKROOT:=$(shell xcrun --sdk iphonesimulator --show-sdk-path)
else
$(error Invalid HOST for cross compilation: $(HOST))
endif
# We set PKG_CONFIG_LIBDIR instead of PKG_CONFIG_PATH because we want to
# *change* where pkg-config looks for .pc files instead of adding to the
# default path which may have libraries that aren't for HOST.
export PKG_CONFIG_LIBDIR:=$(HOSTROOT)/lib/pkgconfig
# We set PKG_CONFIG_LIBDIR instead of PKG_CONFIG_PATH because we want to
# *change* where pkg-config looks for .pc files instead of adding to the
# default path which may have libraries that aren't for HOST.
export PKG_CONFIG_LIBDIR:=$(HOSTROOT)/lib/pkgconfig
endif
endif
# change to sdl-console to build a console version on Windows
@ -286,6 +285,7 @@ CURSOR_SHAPES:=LARGE
SDL_LIBS:=$(shell $(PKG_CONFIG) $(SDL_PCNAME) --libs)
SDL_LIBS+=$(call linktest,SDL2_image,-lSDL2_image,$(SDL_LIBS))
SDL_LIBS+=$(call linktest,SDL2_ttf,-lSDL2_ttf,$(SDL_LIBS))
SDL_LIBS+=$(call linktest,SDL2_gfx,-lSDL2_gfx,$(SDL_LIBS))
SDL_LIBS+=$(call linktest,zlib,-lz,)
SDL_LIBS+=$(call linktest,libpng,$(PNG),)
@ -699,9 +699,11 @@ uninstall: uninstall-i18n
-rm -r $(DATA_PREFIX)
-rm -r $(DOC_PREFIX)
-rm $(MAN_PREFIX)/man1/tuxpaint.1.gz
-rm $(MAN_PREFIX)/pl/man1/tuxpaint.1.gz
-rm $(MAN_PREFIX)/*/man1/tuxpaint.1.gz
-rm $(MAN_PREFIX)/man1/tuxpaint-import.1.gz
-rm $(MAN_PREFIX)/*/man1/tuxpaint-import.1.gz
-rm $(MAN_PREFIX)/man1/tp-magic-config.1.gz
-rm $(MAN_PREFIX)/*/man1/tp-magic-config.1.gz
-rm -f -r $(CONFDIR)
-rm $(COMPLETIONDIR)/tuxpaint-completion.bash
-rm -r $(MAGIC_PREFIX)
@ -964,6 +966,7 @@ install-dlls:
cp $(MINGW_DIR)/bin/libpng12.dll $(BIN_PREFIX); \
cp $(MINGW_DIR)/bin/SDL.dll $(BIN_PREFIX); \
cp $(MINGW_DIR)/bin/SDL_image.dll $(BIN_PREFIX); \
cp $(MINGW_DIR)/bin/SDL_gfx.dll $(BIN_PREFIX); \
cp $(MINGW_DIR)/bin/SDL_mixer.dll $(BIN_PREFIX); \
cp $(MINGW_DIR)/bin/SDL_ttf.dll $(BIN_PREFIX); \
cp $(MINGW_DIR)/bin/libfreetype-6.dll $(BIN_PREFIX); \
@ -1070,28 +1073,31 @@ install-doc:
.PHONY: install-man
install-man:
@echo
@echo "...Installing man pages..."
@echo "...Installing English man pages..."
@# man1 directory...
@install -d $(MAN_PREFIX)/man1
@# tuxpaint.1
@cp src/manpage/tuxpaint.1 $(MAN_PREFIX)/man1
@cp man/en/tuxpaint.1 $(MAN_PREFIX)/man1/
@gzip -f $(MAN_PREFIX)/man1/tuxpaint.1
@chmod a+rx,g-w,o-w $(MAN_PREFIX)/man1/tuxpaint.1.gz
@# pl/man1 directory...
@install -d $(MAN_PREFIX)/pl/man1/
@# tuxpaint-pl.1
@cp src/manpage/tuxpaint-pl.1 $(MAN_PREFIX)/pl/man1/tuxpaint.1
@gzip -f $(MAN_PREFIX)/pl/man1/tuxpaint.1
@chmod a+rx,g-w,o-w $(MAN_PREFIX)/pl/man1/tuxpaint.1.gz
@# tuxpaint-import.1
@cp src/manpage/tuxpaint-import.1 $(MAN_PREFIX)/man1/
@cp man/en/tuxpaint-import.1 $(MAN_PREFIX)/man1/
@gzip -f $(MAN_PREFIX)/man1/tuxpaint-import.1
@chmod a+rx,g-w,o-w $(MAN_PREFIX)/man1/tuxpaint-import.1.gz
@# tp-magic-config.1
@cp src/manpage/tp-magic-config.1 $(MAN_PREFIX)/man1/
@cp man/en/tp-magic-config.1 $(MAN_PREFIX)/man1/
@gzip -f $(MAN_PREFIX)/man1/tp-magic-config.1
@chmod a+rx,g-w,o-w $(MAN_PREFIX)/man1/tp-magic-config.1.gz
@echo
for l in `ls -d man/*.UTF-8 | cut -d '/' -f 2`; do \
DEST=$(MAN_PREFIX)/$$l/man1 ; \
echo "...Installing $$l man pages into $$DEST..." ; \
install -d $$DEST ; \
cp man/$$l/tuxpaint.1 $$DEST ; \
gzip -f $$DEST/tuxpaint.1 ; \
chmod a+rx,g-w,o-w $$DEST/tuxpaint.1.gz ; \
done
@# FIXME: The other man pages aren't localizable yet -bjk 2021.08.14
# Install the support files for macOS application bundle
.PHONY: install-macbundle
@ -1348,6 +1354,7 @@ obj:
MAGIC_SDL_CPPFLAGS:=$(shell $(PKG_CONFIG) $(SDL_PCNAME) --cflags)
# FIXME: Expose SDL_rotozoom to Magic API? -bjk 2021.09.06
windows_MAGIC_SDL_LIBS:=-L/usr/local/lib $(LIBMINGW) $(shell $(PKG_CONFIG) $(SDL_PCNAME) --libs) -lSDL_image -lSDL_ttf $(SDL_MIXER_LIB)
macos_MAGIC_SDL_LIBS:=-L/usr/local/lib $(shell $(PKG_CONFIG) $(SDL_PCNAME) --libs) -lSDL_image -lSDL_ttf $(SDL_MIXER_LIB)
ios_MAGIC_SDL_LIBS:=$(shell $(PKG_CONFIG) $(SDL_PCNAME) --libs) -lSDL_image -lSDL_ttf $(SDL_MIXER_LIB)

2
data/brushes/arrow.dat Normal file
View file

@ -0,0 +1,2 @@
rotate
spacing=60

BIN
data/brushes/arrow.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 6.7 KiB

2
data/brushes/arrow_compass_points.dat
View file

@ -1,2 +0,0 @@
directional
spacing=80

BIN
data/brushes/arrow_compass_points.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 2.1 KiB

BIN
data/images/ui/brush_anim.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 9 KiB

BIN
data/images/ui/brush_dir.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 1 KiB

113
docs/CHANGES.txt
View file

@ -8,6 +8,119 @@ http://www.tuxpaint.org/
$Id$
2021.September.6 (0.9.27)
* New Magic Tools:
----------------
* "Opposite" -- Change parts of the picture to their complementary
colors. (Similar to "Negative", but instead of inverting the
Red, Green, and Blue components, it rotates the Hue 180 degrees
while leaving Saturation and Lightness alone.)
(Closes https://sourceforge.net/p/tuxpaint/feature-requests/136/)
* "Panels" - Convert your picture to 4-panel-comic-style
2x2 image, repeating the original. (Repeat for "compound eye"
style effects!)
(Closes https://sourceforge.net/p/tuxpaint/feature-requests/204/)
* Magic Tool Improvements:
------------------------
* "Halftone" works much better, drawing large overlapping circles
of Cyan, Magenta, Yellow, and Black, based on the average
color of the area of the picture being replaced, to give a
"newsprint" effect.
* "Halftone" can now affect the entire image at once.
* Other Improvements:
-------------------
* WIP Rotational brushes now supported. Unlike "directional"
brushes, in which a 3x3 grid representing the 8 cardinal
directions (45 degree steps) is used, only a single brush image
is required, and Tux Paint will rotate it between 0 and 360 degrees,
depending on the direction the mouse is going. The brush's ".dat"
file should contain a line consisting of the word "rotate".
* FIXME: WIP -- Doesn't handle animated brushes correctly!
* Note: This adds a dependency on "SDL_gfx" library
(Homepage: https://www.ferzkopp.net/wordpress/2016/01/02/sdl_gfx-sdl2_gfx/
SourceForge project page: https://sourceforge.net/projects/sdlgfx/)
as this feature use it's "rotozoom" functionality.
(Closes https://sourceforge.net/p/tuxpaint/feature-requests/122/)
* Replaced the "arrow_compass_points" brush with a single
arrow which can rotate at any angle, using the new
"rotational" brush feature.
* Small icons appear on brush selection buttons denoting
when the brush is animated and/or directional.
(Closes https://sourceforge.net/p/tuxpaint/bugs/183/)
* Always show the appropriate instructions at the bottom when the
"Fill" (depends on which sub-tool chosen) and "Shapes" (depends
on whether "simpleshapes" option is set) tools are selected
(e.g., when returning from the "Open" dialog).
(Closes https://sourceforge.net/p/tuxpaint/feature-requests/186/)
* Documentation updates:
---------------------
* Ensured Tux Paint's built-in help ("tuxpaint --help"),
Unix manual ("man page"), and command-line option
tab-completion list, and "OPTIONS" documentation all cover
the full set of Tux Paint options.
* Reorganized the "Available Options" section of "OPTIONS"
documentation (to match the organization found in the UI
of "Tux Paint Config.")
* Reorganized the options listed in Tux Paint's man page,
to more closely (but not precisely) match the organization
noted above.
* tuxpaint(1) manpage is now managed & translatable via the
'tuxpaint-docs' project, just like the HTML & plaintext
documentation files (since 0.9.26).
* Added table of contents to some documentation
("Options Documentation", "FAQ", "Installation Documentation",
and "Advanced Stamps 'How-To'").
* Moved Windows and macOS compilation instructions into main
"Installation Documentation" (docs/.../INSTALL...).
* Documentation translation updates:
+ French translation
Jacques Chion <jacques.chion@orange.fr>
* Translation Updates:
--------------------
* Ensure some locales have hints to find the best fonts
for the Text and Label tools:
* Greek
* Scottish Gaelic
* French
Jacques Chion <jacques.chion@orange.fr>
* Icelandic
Sveinn í Felli <sv1@fellsnet.is>
* Bug Fixes:
----------
* "Negative" magic tool did not play its sound when using
fullscreen (vs painting) mode. Fixed.
* "Zoom" magic tool icon had weird artifacting. Mended.
* "Halftone" magic tool had the "Zoom" tool's icon.
* Ports & Building
----------------
* Fix compilation error on Linux with HOST environment variable set.
Modifies the Makefile so it attempts to cross compile only when both
HOST and HOSTROOT environment variable (which are both required for
cross compilation) are set; avoid confusion when an unrelated
$HOST env. var. is set.
Mark K. Kim <markuskimius@gmail.com>
2021.June.28 (0.9.26)
* New Features
------------

30
docs/en/ADVANCED-STAMPS-HOWTO.txt
View file

@ -1,9 +1,27 @@
Tux Paint
version 0.9.26 Advanced Stamps 'How-To'
version 0.9.27 Advanced Stamps 'How-To'
Copyright © 2006-2021 by Albert Cahalan and others; see AUTHORS.
http://www.tuxpaint.org/
August 29, 2021
----------------------------------------------------------------------
+----------------------------------------+
|Table of Contents |
|----------------------------------------|
| * About this 'How-To' |
| * Image choice is crucial |
| * Prepare the mask |
| * Replace the fringe and junk pixels |
| * Save the image for Tux Paint |
+----------------------------------------+
----------------------------------------------------------------------
----------------------------------------------------------------------
About this 'How-To'
This 'How-To' assumes that you want to make an excellent Tux Paint
@ -18,6 +36,8 @@ About this 'How-To'
also best done with custom software, but are not troublesome to do as
follows.
----------------------------------------------------------------------
Image choice is crucial
License
@ -66,6 +86,8 @@ Image choice is crucial
will need to draw new ones. If only one is buried, you might be able
to copy the other one as a replacement.
----------------------------------------------------------------------
Prepare the image
First of all, be sure to avoid re-saving the image as a JPEG. This
@ -101,6 +123,8 @@ Prepare the image
normally. This would cause data loss. You will be given special scaling
instructions later.
----------------------------------------------------------------------
Prepare the mask
Get used to doing [Ctrl]-click and [Alt]-click on the thumbnail images
@ -161,6 +185,8 @@ Prepare the mask
expected color. Invert the selection, then paint these away using the
pencil tool. Do this operation for both white and black.
----------------------------------------------------------------------
Replace the fringe and junk pixels
Still viewing the mask, select by color. Choose black. Shrink the
@ -222,6 +248,8 @@ Replace the fringe and junk pixels
edge, you should use the pencil tool (or sloppy select with
drag-and-drop color) to ensure that the result will compress well.
----------------------------------------------------------------------
Save the image for Tux Paint
It is very easy to ruin your hard work. Image editors can silently

4
docs/en/ENVVARS.txt
View file

@ -1,11 +1,11 @@
Tux Paint
version 0.9.26
version 0.9.27
Environment Variables Documentation
Copyright © 2021-2021 by various contributors; see AUTHORS.
http://www.tuxpaint.org/
May 11, 2021
August 8, 2021
----------------------------------------------------------------------

31
docs/en/EXTENDING.txt
View file

@ -1,11 +1,11 @@
Extending
Tux Paint
version 0.9.26
version 0.9.27
Copyright © 2002-2021 by various contributors; see AUTHORS.
http://www.tuxpaint.org/
May 31, 2021
September 6, 2021
----------------------------------------------------------------------
@ -212,17 +212,26 @@ Brushes
Add a line containing the word "directional" to the brush's data
file.
Animated Directional Brushes
Rotating Brushes
You may mix both animated and directional features into one brush.
Use both options ("frames=N" and "directional"), in separate lines
in the brush's ".dat" file.
As of Tux Paint version 0.9.27, you may now create rotating brushes.
As the brush is used, it is rotated 360 degrees, depending on the
direction the brush is going.
Lay the brush out so that each 3x3 set of directional shapes are
laid out across a wide PNG image. For example, if the brush is 30x30
and there are 5 frames, it would be 450x90. (The leftmost 150x90
pixels of the image represent the 9 direction shapes for the first
frame, for example.)
Add a line containing the word "rotate" to the brush's data file.
Animated Directional or Rotating Brushes
You may mix both animated and either directional or rotating
features into one brush. Use both options desired ("frames=N" and
"directional" or "rotate"), in separate lines in the brush's ".dat"
file.
For directional brushes, lay the brush out so that each 3x3 set of
directional shapes are laid out across a wide PNG image. For
example, if the brush is 30x30 and there are 5 frames, it would be
450x90. (The leftmost 150x90 pixels of the image represent the 9
direction shapes for the first frame, for example.)
Place the brush image PNGs (and any data text files) in the "brushes"
directory.

19
docs/en/FAQ.txt
View file

@ -1,10 +1,25 @@
Tux Paint
version 0.9.26 Frequently Asked Questions
version 0.9.27 Frequently Asked Questions
Copyright © 2002-2021 by various contributors; see AUTHORS.
http://www.tuxpaint.org/
June 2, 2021
August 29, 2021
----------------------------------------------------------------------
+------------------------------+
|Table of Contents |
|------------------------------|
| * Drawing-related |
| * Interface Problems |
| * Printing |
| * Saving |
| * Audio Problems |
| * Fullscreen Mode Problems |
| * Other Probelms |
| * Help / Contact |
+------------------------------+
----------------------------------------------------------------------

474
docs/en/INSTALL.txt
View file

@ -1,26 +1,46 @@
Tux Paint
version 0.9.26
version 0.9.27
Installation Documentation
Copyright © 2002-2021 by various contributors; see AUTHORS.
http://www.tuxpaint.org/
March 9, 2021
September 5, 2021
----------------------------------------------------------------------
Requirements:
+----------------------------------------------------+
|Table of Contents |
|----------------------------------------------------|
| * Requirements |
| * Simple DirectMedia Layer library (libSDL) |
| * Other Libraries |
| * Compiling and Installation |
| * Windows Users |
| * Linux/Unix Users |
| * macOS Users |
| * Debugging |
| * Uninstalling Tux Paint |
| * Windows |
| * macOS |
| * Linux |
+----------------------------------------------------+
libSDL
----------------------------------------------------------------------
Requirements
Simple DirectMedia Layer library (libSDL)
Tux Paint requires the Simple DirectMedia Layer Library (libSDL), an
Open Source multimedia programming library available under the GNU
Lesser General Public License (LGPL).
Along with libSDL, Tux Paint depends on a number of other SDL 'helper'
libraries: SDL_Image (for graphics files), SDL_TTF and (optionally)
SDL_Pango (for True Type Font support) and, optionally, SDL_Mixer (for
sound effects).
libraries: SDL_Image (for graphics files), SDL_gfx (for some graphical
functions, like rotation), SDL_TTF and (optionally) SDL_Pango (for
True Type Font support) and, optionally, SDL_Mixer (for sound
effects).
Linux/Unix Users:
@ -30,6 +50,9 @@ Requirements:
* libSDL: http://www.libsdl.org/
* SDL_Image: http://www.libsdl.org/projects/SDL_image/
* SDL_gfx:
https://www.ferzkopp.net/wordpress/2016/01/02/sdl_gfx-sdl2_gfx/
(https://sourceforge.net/projects/sdlgfx/)
* SDL_TTF: http://www.libsdl.org/projects/SDL_ttf/
* SDL_Pango: http://sourceforge.net/projects/sdlpango/ (optional)
* SDL_Mixer: http://www.libsdl.org/projects/SDL_mixer/ (optional)
@ -116,55 +139,261 @@ Requirements:
http://netpbm.sourceforge.net/
Compiling and Installation:
----------------------------------------------------------------------
Compiling and Installation
Tux Paint is released under the GNU General Public License (GPL) (see
"COPYING.txt" for details), and therefore the 'source code' to the
program is available freely.
Windows Users:
Windows Users
Compiling:
October 25, 2020 Shin-ichi TOYAMA shin1@wmail.plala.or.jp
<shin1@wmail.plala.or.jp>
Compiling Set-Up
As of February 2005 (starting with Tux Paint 0.9.15), the "Makefile"
includes support for building on a Windows system using MinGW/MSYS
(http://www.mingw.org/).
(https://sourceforge.net/projects/msys2/).
After configuring the environment and building and installing all
the dependencies, use these commands, in MSYS, to build, install and
run:
Many tools and libraries are required to build Tux Paint. The
package management system "pacman" helps you install them
automatically solving complicated dependencies.
Prior to version 0.9.20:
Download the latest MSYS2 environment from
https://sourceforge.net/projects/msys2/files/Base/ and install it
where you'd like (the default is "C:\msys64")
$ make win32
$ make install-win32
$ tuxpaint
Open the MSYS2 shell from the "Start Menu" -> "MSYS2 64bit" ->
"MSYS2 MSYS" and execute following command (press [Enter] or
[Return] to accept the defaults for all questions):
Version 0.9.20 and beyond:
pacman -Syu
$ make
$ make install
$ tuxpaint
This will update core system and the window will close
automatically. Repeat the steps above one more time to finish the
remaining update process.
Use the following command to build a version suitable for
redistribution with the installer or in a zip-file:
Within the MSYS2 shell, run the following command to install basic
development tools:
pacman -S base-devel msys2-devel git
Proceed to the next "MinGW 64bit (x86_64) toolchains" section, or skip
to the "MinGW 32bit (i686) toolchains" section if you need only a
32bit build environment.
-------------------------------------------------------
MinGW 64bit (x86_64) toolchains
Within the MSYS2 shell, run the following command to install basic
64bit development tools:
pacman -S mingw-w64-x86_64-toolchain
64bit (x86_64) dependency libraries for Tux Paint
You can install tools and libraries required for compiling Tux Paint
on MSYS2/MINGW using "pacman" except for SDL_Pango.
"ntldd" is a small tool which examine windows executable files to
list Dynamic Link Library (.dll) files they depends on. Tux Paint's
packaging process for binary distribution uses it to find required
.dll files.
FLTK is a cross-platform GUI toolkit used by "Tux Paint Config.".
You can skip installing it if you are only building "Tux Paint".
$ pacman -S mingw-w64-x86_64-SDL_{image,mixer,ttf}
$ pacman -S mingw-w64-x86_64-librsvg
$ pacman -S mingw-w64-x86_64-fribidi
$ pacman -S mingw-w64-x86_64-libimagequant
$ pacman -S mingw-w64-x86_64-fltk
$ pacman -S mingw64/mingw-w64-x86_64-ntldd-git
Note: Close the shell before proceeding to the remaining process.
Install SDL_Pango and re-install SDL on the 64bit environment
SDL_Pango should be installed manually. In addition, you have to
re-install SDL from the source code or you will see unnecessary
blank window opens when starting Tux Paint.
This time, use the MinGW "64bit" shell. Open the shell from the
"Start Menu" -> "MSYS2 64bit" -> "MSYS2 MinGW 64-bit"
SDL_Pango
At first, you have to prepare source tar-ball and a required patch
in the same directory.
* Download source tar-ball of SDL_Pango-0.1.2 from SDL_Pango's
page on Sourceforge.net.
* Download a patch file from John Popplewell's "Tux Paint -
MinGW/MSYS build instructions" webpage. (This adds some extra
(required) functionality to SDL_Pango.)
Build and install SDL_Pango as follows.
$ tar zxvf SDL_Pango-0.1.2.tar.gz
$ cd SDL_Pango-0.1.2/
$ patch -p0 < ../SDL_Pango-configure-extra-api.patch
$ ./configure --prefix=/mingw64 && make && make install
SDL
Download source tar-ball of SDL_1.2.15 from libsdl.org.
Re-install SDL as follows.
$ tar zxvf SDL-1.2.15.tar.gz
$ cd SDL-1.2.15
$ ./configure --prefix=/mingw64 && make && make install
Proceed to the next "MinGW 32bit (i686) toolchains" section, or skip
to the "ImageMagick" section if you need only a 64bit build
environment.
-------------------------------------------------------
MinGW 32bit (i686) toolchains
Within the MSYS2 shell, run the following command to install basic
32bit development tools:
pacman -S mingw-w64-i686-toolchain
32bit (i686) dependency libraries for Tux Paint
You can install tools and libraries required for compiling Tux Paint
on MSYS2/MINGW using "pacman" except for SDL_Pango.
"ntldd" is a small tool which examine windows executable files to
list Dynamic Link Library (.dll) files they depends on. Tux Paint's
packaging process for binary distribution uses it to find required
.dll files.
FLTK is a cross-platform GUI toolkit used by "Tux Paint Config.".
You can skip installing it if you are only building "Tux Paint".
$ pacman -S mingw-w64-i686-SDL_{image,mixer,ttf}
$ pacman -S mingw-w64-i686-librsvg
$ pacman -S mingw-w64-i686-fribidi
$ pacman -S mingw-w64-i686-libimagequant
$ pacman -S mingw-w64-i686-fltk
$ pacman -S mingw-w64-i686-ntldd-git
Note: Close the shell before proceeding to the remaining process.
Install SDL_Pango and re-install SDL on the 32bit environment
SDL_Pango should be installed manually. In addition, you have to
re-install SDL from the source code or you will see unnecessary
blank window opens when starting Tux Paint.
This time, use the MinGW "32bit" shell. Open the shell from the
"Start Menu" -> "MSYS2 64bit" -> "MSYS2 MinGW 32-bit"
SDL_Pango
At first, you have to prepare source tar-ball and a required patch
in the same directory.
* Download source tar-ball of SDL_Pango-0.1.2 from SDL_Pango's
page on Sourceforge.net.
* Download a patch file from John Popplewell's "Tux Paint -
MinGW/MSYS build instructions" webpage. (This adds some extra
(required) functionality to SDL_Pango.)
Build and install SDL_Pango as follows.
$ tar zxvf SDL_Pango-0.1.2.tar.gz
$ cd SDL_Pango-0.1.2/
$ patch -p0 < ../SDL_Pango-configure-extra-api.patch
$ ./configure --prefix=/mingw32 && make && make install
SDL
Download source tar-ball of SDL_1.2.15 from libsdl.org.
Re-install SDL as follows.
$ tar zxvf SDL-1.2.15.tar.gz
$ cd SDL-1.2.15
$ ./configure --prefix=/mingw32 && make && make install
-------------------------------------------------------
ImageMagick
ImageMagick is a compilation of command line tools to create, edit,
compose, or convert bitmap images supporting quite a large number of
image formats. Tux Paint uses two functions ("convert" and
"composite") in it to generate thumbnails for startar images and
templates during the build process.
Using official binary release available from "Windows Binary
Release" is recommended, due to the commands installed with "pacman"
on MinGW/MSYS not working as expected!
Do not forget to enable "Install legacy utilities (e.g. convert)"
while installing it, because Tux Paint's build process uses them.
Add the path to the directory in which ImageMagick is installed at
the top of your "PATH" environment variable. For example:
$ export PATH=/c/Program\ Files/ImageMagick-7.0.10-Q16-HDRI:$PATH
You can make this permanent by adding the above to your the BASH
shell configuration file, "~/.bash_profile".
-------------------------------------------------------
Tux Paint
You can compile 64bit binaries using MSYS2 64bit shell, and 32bit
binaries using MSYS2 32bit shell, respectively.
* Select "MSYS2 64bit" -> "MSYS2 MinGW 64-bit" from the "Start
Menu" to open the 64bit shell.
* Select "MSYS2 64bit" -> "MSYS2 MinGW 32-bit" from the "Start
Menu" to open the 32bit shell.
Compile Tux Paint with the following command:
$ make bdist-win32
Or if building for Win9x/ME:
Note: At this point, you will want to build "Tux Paint Config." for
Windows, so it can be included along with "Tux Paint", if you're
making an official (or test) release. The build process will look
for it in a directory named "tuxpaint-config" (with no version
number, e.g., "tuxpaint-config-X.Y.Z"). See "Tux Paint Config."'s
INSTALL.txt documentation for details.
$ BDIST_WIN9X=1 make bdist-win32
All the files needed for starting Tux Paint (and Tux Paint Config.)
are collected in the directory for binary distribution "bdist"
directory under "win32". You can start them by double-clicking their
executable (.exe) files in the "bdist" directory.
Before any of the above will work, you need to configure the
environment and build or install the libraries that Tux Paint
depends upon. John Popplewell put together some instructions for
doing that here:
-------------------------------------------------------
http://www.johnnypops.co.uk/tuxpaint/
Building the Tux Paint Windows Installer:
Read the relevant notes if building for Win9X/ME.
Inno Setup is used to build executable installer for Tux Paint.
Therefore you have to install it in the first place.
Running the Installer:
Then, you can easily build an executable installer by right-clicking
on the "tuxpaint.iss" icon in the "win32" directory and selecting
"Compile" on the list. It will run for a while, and eventually you
will find a "tuxpaint-X.Y.Z-win32-installer.exe" file in the same
directory.
-------------------------------------------------------
Running the Tux Paint Windows Installer:
Double-click the Tux Paint installer executable (.EXE file) and
follow the instructions.
@ -183,6 +412,8 @@ Compiling and Installation:
At this point, you can click 'Install' to install Tux Paint!
-------------------------------------------------------
Changing the Settings Using the Shortcut:
To change program settings, right-click on the TuxPaint shortcut and
@ -211,6 +442,8 @@ Compiling and Installation:
When you have finished, click "OK."
-------------------------------------------------------
If Something Goes Wrong:
If, when you double-click on the shortcut to run Tux Paint, nothing
@ -222,7 +455,9 @@ Compiling and Installation:
just be due to incorrect character-case (capital 'Z' instead of
lowercase 'z') or a missing (or extra) '-' (dash).
Linux/Unix Users:
----------------------------------------------------------------------
Linux/Unix Users
Compiling:
@ -235,6 +470,8 @@ Compiling and Installation:
$ make
-------------------------------------------------------
Disabling SVG support (and hence Cairo, libSVG, and svg-cairo dependencies):
To disable SVG support (e.g., if your system is not currently
@ -244,6 +481,8 @@ Compiling and Installation:
$ make SVG_LIB= SVG_CFLAGS=
-------------------------------------------------------
Disabling Pango support (and hence Pango, Cairo, etc. dependencies):
Prior to version 0.9.18, Tux Paint used the libSDL_ttf library for
@ -254,6 +493,8 @@ Compiling and Installation:
$ make SDL_PANGO_LIB=
-------------------------------------------------------
Disabling Sound at Compile-time:
If you don't have a sound card, or would prefer to build the program
@ -262,11 +503,15 @@ Compiling and Installation:
$ make SDL_MIXER_LIB=
-------------------------------------------------------
Other options:
Various other options (e.g., installation paths) may be overridden;
see them in "Makefile" for further details.
-------------------------------------------------------
If you get errors:
If you receive any errors during compile-time, make sure you have
@ -276,6 +521,8 @@ Compiling and Installation:
packages as well, otherwise you won't be able to compile Tux Paint
(and other programs) from source!
-------------------------------------------------------
Installng:
Assuming no fatal errors occured, you can now install the program so
@ -351,13 +598,150 @@ Compiling and Installation:
Note: This list is out of date. See "Makefile" and "Makefile-i18n"
for a complete list.
Debugging:
----------------------------------------------------------------------
Debugging (to "STDOUT", e.g. to the terminal, or to a "stdout.txt" file,
on Windows) can be enabled by setting "DEBUG" (and, if verbose logging
is wanted, "VERBOSE") #defines in "src/debug.h".
macOS Users
Uninstalling Tux Paint:
September 21, 2021 Mark K. Kim <markuskimius@gmail.com>
Tux Paint 0.9.22 and earlier required building Tux Paint from the
Xcode IDE. Starting with 0.9.23, however, Tux Paint for macOS is built
as though it were a Linux application.
Prerequisites
Although Tux Paint is built without the Xcode IDE, Xcode itself is
still required to build Tux Paint. Download it from the App Store,
and launch it once to accept its license agreements. You may also
need to install the Xcode command line tools using the command:
xcode-select --install
Building Tux Paint also requires various libraries. We install them
from MacPorts where possible, source code otherwise. Install
MacPorts to the default /opt/local path according to the
instructions found on their website: https://www.macports.org/
* ImageMagick
* cairo
* fribidi
* lbzip2
* libimagequant^*
* libpaper
* libpng
* librsvg
* libsdl
* libsdl_image
* libsdl_mixer
* libsdl_pango
* libsdl_ttf
* pkgconfig
* zlib
... but you should install any package that is required by the
latest version of Tux Paint.
^* Not available from MacPorts as of this writing, see below.
libimagequant
libimagequant is not available from MacPorts as of this writing.
It can be installed from the source code as follows. It should be
installed to /opt/local (same as MacPorts) for the library to be
included in TuxPaint.dmg.
$ git clone https://github.com/ImageOptim/libimagequant.git
$ cd libimagequant
$ ./configure --prefix=/opt/local
$ make
$ sudo make install
WARNING: Having any UNIX-like toolset installed on your Mac besides
MacPorts and Xcode, such as Fink or Brew, will prevent your app
bundle from being portable. Be sure Fink and Brew are not accessible
from your build environment.
-------------------------------------------------------
How to Build
Simply, run:
% make
% make install
... to create the TuxPaint.app application bundle that can be run
in-place or copied to /Applications. It also creates TuxPaint.dmg
for distribution.
-------------------------------------------------------
Known Issues
* A macOS binary built on a specific version of macOS only runs on
that version of macOS or later. To ensure Tux Paint can run on
the oldest version of macOS possible, build it on the oldest
version of macOS available. As of this writing we know Tux Paint
cannot be built to run on macOS 10.7 or earlier.
See "Old Versions of macOS" below for best-effort instructions
on how to obtain, install, and build Tux Paint on an old version
of macOS.
-------------------------------------------------------
Old Versions of macOS
Some old versions of macOS can be downloaded from Apple's support
page: https://support.apple.com/en-us/HT211683
macOS does allow dual booting of multiple versions of the OS, but
it's safer and easier to install the old macOS onto a flash drive.
Wherever you're installing it, the target drive's partitioniong
scheme and partition type must match what the old macOS expects, so
use the Disk Utility to partition and format the flash drive
accordingly.
As of this writing, the oldest version of macOS available on Apple's
support site is Yosemite 10.10, which expects "GPT (GUID Partition
Table)" partitioning scheme instead of the older MBR scheme, and
"Mac OS Extended (Journaled)" as the partition type instead of the
newer APFS partition type.
Upon launching the installer, if you get a popup about macOS being
too old or new to be installed, a bootable installer can be created
using the instructions found here:
https://support.apple.com/en-mide/HT201372
It has been found that macOS can be installed onto the bootable
media itself, so you can make the flash drive into a bootable
installer then install the old macOS onto the same flash drive.
Once the old macOS is installed, you may find the Xcode on the App
Store is too new to run on the version of the old macOS. Old
versions of Xcode can be downloaded from Apple's Developer site in
an area accessible with free registration:
https://developer.apple.com/download/more/
The list of macOS versions and the last version of Xcode compatible
with them are laid out nicely on the Wikipedia page on Xcode:
https://en.wikipedia.org/wiki/Xcode#Version_comparison_table
And because Xcode is being installed manually, you can skip the step
to install the Xcode command line tools (do not run "xcode-select
--install") but otherwise build Tux Paint using the same steps
described in the earlier part of this document.
----------------------------------------------------------------------
Debugging
Debugging output — to "STDOUT" on Linux and Unix, to a "stdout.txt" file
on Windows, and to the file "/tmp/tuxpaint.log" on macOS — can be
enabled by setting "DEBUG" (and, if verbose logging is wanted,
"VERBOSE") #defines in "src/debug.h" and (re)compiling Tux Paint.
----------------------------------------------------------------------
Uninstalling Tux Paint
Windows
@ -376,6 +760,18 @@ Uninstalling Tux Paint:
It is also possible to use the entry "TuxPaint (remove only)" in the
Control Panel Add/Remove programs section.
----------------------------------------------------------------------
macOS
Delete "TuxPaint.app" from the "Applications" folder. Data files,
including the configuration files, stamps, and saved pictures, may be
found in "Library/Application Support/TuxPaint" (all users) and
"/Users/USERNAME/Library/Application Support/TuxPaint" (individual
users).
----------------------------------------------------------------------
Linux
Within the Tux Paint source directory (where you compiled Tux Paint),

1929
docs/en/OPTIONS.txt
View file

File diff suppressed because it is too large Load diff

2
docs/en/PNG.txt
View file

@ -1,5 +1,5 @@
Tux Paint
version 0.9.26
version 0.9.27
PNG Documentation
Copyright © 2007-2021 by various contributors; see AUTHORS.

26
docs/en/README.txt
View file

@ -1,12 +1,12 @@
Tux Paint
version 0.9.26
version 0.9.27
A simple drawing program for children
Copyright © 2002-2021 by various contributors; see AUTHORS.
http://www.tuxpaint.org/
June 28, 2021
September 5, 2021
----------------------------------------------------------------------
@ -219,6 +219,22 @@ Available Tools
If you hold the mouse button down, and move the mouse, it
will draw as you move.
Some brushes are animated — they change their shape as you
draw them. A good example of this is the vines brush that
ships with Tux Paint. These brushes will have a small
"filmstrip" icon drawn on their Selector buttons.
Other brushes are directional — they will draw a different
shape depending on what direction you are painting with
them. An example of this is the arrow brush that ships with
Tux Paint. These brushes have a small 8-way arrow icon drawn
on their Selector buttons.
Finally, some brushes can be both direction and animated.
Examples of this are the cat and squirrel brushes that ship
with Tux Paint. These brushes will have both the "filmstrip"
and 8-way arrow icons.
As you draw, a sound is played. The bigger the brush, the
lower the pitch.
@ -278,6 +294,12 @@ Available Tools
Let go of the mouse to complete the line. A "sproing!" sound
will play.
Some brushes are animated, and will show a pattern of shapes
along the line. Others are directional, and will show a
different shape depending on the angle of the brush. And
finally some are both animated and directional. See "Paint",
above, to learn more.
----------------------------------------------------------------------
"Shapes" Tool

2
docs/en/SIGNALS.txt
View file

@ -1,5 +1,5 @@
Tux Paint
version 0.9.26
version 0.9.27
Signals Documentation
Copyright © 2019-2021 by various contributors; see AUTHORS.

2
docs/en/SVG.txt
View file

@ -1,5 +1,5 @@
Tux Paint
version 0.9.26
version 0.9.27
SVG Documentation
Copyright © 2007-2021 by various contributors; see AUTHORS.

81
docs/en/html/ADVANCED-STAMPS-HOWTO.html
View file

@ -17,16 +17,62 @@
width="205"
height="210"
alt="Tux Paint"><br>
version 0.9.26 Advanced Stamps 'How-To' </h1>
version 0.9.27 Advanced Stamps 'How-To' </h1>
<p>
Copyright &copy; 2006-2021 by Albert Cahalan and others; see AUTHORS.<br>
<a href="http://www.tuxpaint.org/">http://www.tuxpaint.org/</a>
</p>
<p>
August 29, 2021 </p>
</center>
<hr size="2"
noshade>
<table border="2"
cellspacing="0"
cellpadding="2"
summary="Table of Contents">
<tr>
<th>
Table of Contents </th>
</tr>
<tr>
<td>
<ul>
<li>
<a href="#about">About this 'How-To'</a>
</li>
<li>
<a href="#choice">Image choice is crucial</a>
</li>
<li>
<a href="#prepare_mask">Prepare the mask</a>
</li>
<li>
<a href="#replace_fringe">Replace the fringe and junk pixels</a>
</li>
<li>
<a href="#save">Save the image for Tux Paint</a>
</li>
</ul>
</td>
</tr>
</table>
<hr size="2"
noshade>
<hr size="2"
noshade>
<h2>
About this 'How-To' </h2>
<a name="about" id="about">
About this 'How-To' </a>
</h2>
<blockquote>
<p>
@ -36,8 +82,13 @@
This 'How-To' assumes you are dealing with normal opaque objects. Dealing with semi-transparent objects (fire, moving fan blade, kid's balloon) or light-giving objects (fire, lightbulb, sun) is best done with custom software. Images with perfect solid-color backgrounds are also best done with custom software, but are not troublesome to do as follows. </p>
</blockquote>
<hr size="2"
noshade>
<h2>
Image choice is crucial </h2>
<a name="choice" id="choice">
Image choice is crucial </a>
</h2>
<blockquote>
<h3>
@ -78,6 +129,9 @@
</blockquote>
</blockquote>
<hr size="2"
noshade>
<h2>
Prepare the image </h2>
@ -116,8 +170,13 @@
<b>Warning:</b> once you have the mask, you may not rotate or scale the image normally. This would cause data loss. You will be given special scaling instructions later. </p>
</blockquote>
<hr size="2"
noshade>
<h2>
Prepare the mask </h2>
<a name="prepare_mask" id="prepare_mask">
Prepare the mask </a>
</h2>
<blockquote>
<p>
@ -151,8 +210,13 @@
View and edit the mask. Select by color, choosing either black or white. Most likely you will see unselected specks that are not quite the expected color. Invert the selection, then paint these away using the pencil tool. Do this operation for both white and black. </p>
</blockquote>
<hr size="2"
noshade>
<h2>
Replace the fringe and junk pixels </h2>
<a name="replace_fringe" id="replace_fringe">
Replace the fringe and junk pixels </a>
</h2>
<blockquote>
<p>
@ -188,8 +252,13 @@
Tux Paint can scale images down by a very large factor, so it is important to extend the edge of your object outward by a great deal. Right at the edge of your object, you should be very accurate about this. As you go outward away from the object, you can get a bit sloppy. It is reasonable to paint outward by a dozen pixels or more. The farther you go, the more Tux Paint can scale down without creating ugly color fringes. For areas that are more than a few pixels away from the object edge, you should use the pencil tool (or sloppy select with drag-and-drop color) to ensure that the result will compress well. </p>
</blockquote>
<hr size="2"
noshade>
<h2>
Save the image for Tux Paint </h2>
<a name="save" id="save">
Save the image for Tux Paint </a>
</h2>
<blockquote>
<p>

4
docs/en/html/ENVVARS.html
View file

@ -17,7 +17,7 @@
width="205"
height="210"
alt="Tux Paint"><br>
version 0.9.26<br/>
version 0.9.27<br/>
Environment Variables Documentation </h1>
<p>
@ -26,7 +26,7 @@
</p>
<p>
May 11, 2021 </p>
August 8, 2021 </p>
</center>
<hr>

21
docs/en/html/EXTENDING.html
View file

@ -18,7 +18,7 @@
width="205"
height="210"
alt="Tux Paint"><br>
version 0.9.26 </h1>
version 0.9.27 </h1>
<p>
Copyright &copy; 2002-2021 by various contributors; see AUTHORS.<br>
@ -26,7 +26,7 @@
</p>
<p>
May 31, 2021 </p>
September 6, 2021 </p>
</center>
<hr size="2"
@ -367,14 +367,25 @@
</blockquote>
<h4>
Animated Directional Brushes </h4>
Rotating Brushes </h4>
<blockquote>
<p>
You may mix both animated and directional features into one brush. Use both options ("<code><b>frames=<i>N</i></b></code>" and "<code><b>directional</b></code>"), in separate lines in the brush's "<code>.dat</code>" file. </p>
As of Tux Paint version 0.9.27, you may now create rotating brushes. As the brush is used, it is rotated 360 degrees, depending on the direction the brush is going. </p>
<p>
Lay the brush out so that each 3x3 set of directional shapes are laid out across a wide PNG image. For example, if the brush is 30x30 and there are 5 frames, it would be 450x90. (The leftmost 150x90 pixels of the image represent the 9 direction shapes for the first frame, for example.) </p>
Add a line containing the word "<code><b>rotate</b></code>" to the brush's data file. </p>
</blockquote>
<h4>
Animated Directional or Rotating Brushes </h4>
<blockquote>
<p>
You may mix both animated and either directional or rotating features into one brush. Use both options desired ("<code><b>frames=<i>N</i></b></code>" and "<code><b>directional</b></code>" or "<code><b>rotate</b></code>"), in separate lines in the brush's "<code>.dat</code>" file. </p>
<p>
For directional brushes, lay the brush out so that each 3x3 set of directional shapes are laid out across a wide PNG image. For example, if the brush is 30x30 and there are 5 frames, it would be 450x90. (The leftmost 150x90 pixels of the image represent the 9 direction shapes for the first frame, for example.) </p>
</blockquote>
</blockquote>

104
docs/en/html/FAQ.html
View file

@ -17,7 +17,7 @@
width="205"
height="210"
alt="Tux Paint"><br>
version 0.9.26 Frequently Asked Questions </h1>
version 0.9.27 Frequently Asked Questions </h1>
<p>
Copyright &copy; 2002-2021 by various contributors; see AUTHORS.<br>
@ -25,13 +25,60 @@
</p>
<p>
June 2, 2021 </p>
August 29, 2021 </p>
</center>
<hr>
<hr size="2"
noshade>
<table border="2"
cellspacing="0"
cellpadding="2"
summary="Table of Contents">
<tr>
<th>
Table of Contents </th>
</tr>
<tr>
<td>
<ul>
<li>
<a href="#drawing">Drawing-related</a>
</li>
<li>
<a href="#interface">Interface Problems</a>
</li>
<li>
<a href="#printing">Printing</a>
</li>
<li>
<a href="#saving">Saving</a>
</li>
<li>
<a href="#audio">Audio Problems</a>
</li>
<li>
<a href="#fullscreen">Fullscreen Mode Problems</a>
</li>
<li>
<a href="#other">Other Probelms</a>
</li>
<li>
<a href="#contact">Help / Contact</a>
</li>
</ul>
</td>
</tr>
</table>
<hr size="2"
noshade>
<h2>
Drawing-related </h2>
<a name="drawing" id="drawing">
Drawing-related </a>
</h2>
<dl>
<dt>
@ -101,10 +148,13 @@
</dd>
</dl>
<hr>
<hr size="2"
noshade>
<h2>
Interface Problems </h2>
<a name="interface" id="interface">
Interface Problems </a>
</h2>
<dl>
<dt>
@ -212,10 +262,13 @@
</dd>
</dl>
<hr>
<hr size="2"
noshade>
<h2>
Printing </h2>
<a name="printing" id="printing">
Printing </a>
</h2>
<dl>
<dt>
@ -282,10 +335,13 @@
</dd>
</dl>
<hr>
<hr size="2"
noshade>
<h2>
Saving </h2>
<a name="saving" id="saving">
Saving </a>
</h2>
<dl>
<dt>
@ -382,10 +438,13 @@
</dd>
</dl>
<hr>
<hr size="2"
noshade>
<h2>
Audio Problems </h2>
<a name="audio" id="audio">
Audio Problems </a>
</h2>
<dl>
<dt>
@ -507,10 +566,13 @@
</dd>
</dl>
<hr>
<hr size="2"
noshade>
<h2>
Fullscreen Mode Problems </h2>
<a name="fullscreen" id="fullscreen">
Fullscreen Mode Problems </a>
</h2>
<dl>
<dt>
@ -569,10 +631,13 @@
</dd>
</dl>
<hr>
<hr size="2"
noshade>
<h2>
Other Probelms </h2>
<a name="other" id="other">
Other Probelms </a>
</h2>
<dl>
<dt>
@ -744,10 +809,13 @@
</dd>
</dl>
<hr>
<hr size="2"
noshade>
<h2>
Help / Contact </h2>
<a name="contact" id="contact">
Help / Contact </a>
</h2>
<p>
Any questions you don't see answered? Please let us know! You can subscribe and post to our "tuxpaint-users" mailing list: </p>

625
docs/en/html/INSTALL.html
View file

@ -17,7 +17,7 @@
width="205"
height="210"
alt="Tux Paint"><br>
version 0.9.26<br/>
version 0.9.27<br/>
Installation Documentation </h1>
<p>
@ -26,21 +26,88 @@
</p>
<p>
March 9, 2021 </p>
September 5, 2021 </p>
</center>
<hr>
<hr size="2" noshade />
<h2>Requirements:</h2>
<table border="2"
cellspacing="0"
cellpadding="2"
summary="Table of Contents">
<tr>
<th>
Table of Contents </th>
</tr>
<tr>
<td>
<ul>
<li>
<a href="#requirements">Requirements</a>
<ul>
<li>
<a href="#req-libsdl">Simple DirectMedia Layer library (libSDL)</a>
</li>
<li>
<a href="#req-other-libs">Other Libraries</a>
</li>
</ul>
</li>
<li>
<a href="#compiling">Compiling and Installation</a>
<ul>
<li>
<a href="#compiling-windows">Windows Users</a>
</li>
<li>
<a href="#compiling-linux">Linux/Unix Users</a>
</li>
<li>
<a href="#compiling-macos">macOS Users</a>
</li>
</ul>
</li>
<li>
<a href="#debugging">Debugging</a>
</li>
<li>
<a href="#uninstalling">Uninstalling Tux Paint</a>
<ul>
<li>
<a href="#uninstalling-windows">Windows</a>
</li>
<li>
<a href="#uninstalling-macOS">macOS</a>
</li>
<li>
<a href="#uninstalling-linux">Linux</a>
</li>
</ul>
</li>
</ul>
</td>
</tr>
</table>
<hr size="2" noshade />
<h2>
<a name="requirements" id="requirements">
Requirements </a>
</h2>
<blockquote>
<h3>libSDL</h3>
<h3>
<a name="req-libsdl" id="req-libsdl">
Simple DirectMedia Layer library (libSDL) </a>
</h3>
<blockquote>
<p>
Tux Paint requires the Simple DirectMedia Layer Library (libSDL), an Open Source multimedia programming library available under the GNU Lesser General Public License (LGPL). </p>
<p>
Along with libSDL, Tux Paint depends on a number of other SDL 'helper' libraries: SDL_Image (for graphics files), SDL_TTF and (optionally) SDL_Pango (for True Type Font support) and, optionally, SDL_Mixer (for sound effects). </p>
Along with libSDL, Tux Paint depends on a number of other SDL 'helper' libraries: SDL_Image (for graphics files), SDL_gfx (for some graphical functions, like rotation), SDL_TTF and (optionally) SDL_Pango (for True Type Font support) and, optionally, SDL_Mixer (for sound effects). </p>
<h4>Linux/Unix Users:</h4>
<blockquote>
@ -49,6 +116,7 @@
<ul>
<li>libSDL: <a href="http://www.libsdl.org/">http://www.libsdl.org/</a></li>
<li>SDL_Image: <a href="http://www.libsdl.org/projects/SDL_image/">http://www.libsdl.org/projects/SDL_image/</a></li>
<li>SDL_gfx: <a href="https://www.ferzkopp.net/wordpress/2016/01/02/sdl_gfx-sdl2_gfx/">https://www.ferzkopp.net/wordpress/2016/01/02/sdl_gfx-sdl2_gfx/</a> (<a href="https://sourceforge.net/projects/sdlgfx/">https://sourceforge.net/projects/sdlgfx/</a>)</li>
<li>SDL_TTF: <a href="http://www.libsdl.org/projects/SDL_ttf/">http://www.libsdl.org/projects/SDL_ttf/</a></li>
<li>SDL_Pango: <a href="http://sourceforge.net/projects/sdlpango/">http://sourceforge.net/projects/sdlpango/</a> (optional)</li>
<li>SDL_Mixer: <a href="http://www.libsdl.org/projects/SDL_mixer/">http://www.libsdl.org/projects/SDL_mixer/</a> (optional)</li>
@ -62,7 +130,10 @@
</blockquote>
</blockquote>
<h3>Other Libraries</h3>
<h3>
<a name="req-other-libs" id="req-other-libs">
Other Libraries </a>
</h3>
<blockquote>
<p>
Tux Paint also takes advantage of a number of other free, LGPL'd libraries. Under Linux, just like SDL, they should either already be installed, or are readily available for installation as part of your Linux distribution. </p>
@ -110,7 +181,7 @@
<h4>SVG graphics support</h4>
<blockquote>
<p>
As of Tux Paint 0.9.17, Tux Paint can load SVG (Scalable Vector Graphics) images as stamps. Two sets of libraries are supported, and SVG support can be completely disabled (via "<code>make SVG_LIB:=</code>") </p>
As of Tux Paint 0.9.17, Tux Paint can load SVG (Scalable Vector Graphics) images as stamps. Two sets of libraries are supported, and SVG support can be completely disabled (via "<code style="white-space: nowrap;">make SVG_LIB:=</code>") </p>
<h5>librsvg-2 &amp; libCairo2 (newer libraries)</h5>
<ul>
@ -155,66 +226,322 @@
</blockquote>
</blockquote>
<h2>Compiling and Installation:</h2>
<hr size="2" noshade />
<h2>
<a name="compiling" id="compiling">
Compiling and Installation </a>
</h2>
<blockquote>
<p>
Tux Paint is released under the GNU General Public License (GPL) (see "COPYING.txt" for details), and therefore the 'source code' to the program is available freely. </p>
<h3>Windows Users:</h3>
<h3>
<a name="compiling-windows" id="compiling-windows">
Windows Users </a>
</h3>
<p style="font-size: small;">
<em>
October 25, 2020 Shin-ichi TOYAMA shin1@wmail.plala.or.jp &lt;<a href="mailto:shin1@wmail.plala.or.jp">shin1@wmail.plala.or.jp</a>&gt;
</em>
</p>
<blockquote>
<h4>Compiling:</h4>
<h4>Compiling Set-Up</h4>
<blockquote>
<p>
As of February 2005 (starting with Tux Paint 0.9.15), the "<code>Makefile</code>" includes support for building on a Windows system using MinGW/MSYS (<a href="http://www.mingw.org/">http://www.mingw.org/</a>). </p>
As of February 2005 (starting with Tux Paint 0.9.15), the "<code>Makefile</code>" includes support for building on a Windows system using MinGW/MSYS (<a href="https://sourceforge.net/projects/msys2/">https://sourceforge.net/projects/msys2/</a>). </p>
<p>
After configuring the environment and building and installing all the dependencies, use these commands, in MSYS, to build, install and run: </p>
<h5>Prior to version 0.9.20:</h5>
<blockquote>
<code>
$ make win32<br/>
$ make install-win32<br/>
$ tuxpaint
</code>
</blockquote>
<h5>Version 0.9.20 and beyond:</h5>
<blockquote>
<code>
$ make<br/>
$ make install<br/>
$ tuxpaint
</code>
</blockquote>
Many tools and libraries are required to build Tux Paint. The package management system "<code>pacman</code>" helps you install them automatically solving complicated dependencies. </p>
<p>
Use the following command to build a version suitable for redistribution with the installer or in a zip-file: </p>
<blockquote>
<code>
$ make bdist-win32
</code>
</blockquote>
Download the latest MSYS2 environment from <a href="https://sourceforge.net/projects/msys2/files/Base/">https://sourceforge.net/projects/msys2/files/Base/</a> and install it where you'd like (the default is "<code>C:\msys64</code>") </p>
<p>
Or if building for Win9x/ME: </p>
<blockquote>
<code>
$ BDIST_WIN9X=1 make bdist-win32
</code>
</blockquote>
<p>
Before any of the above will work, you need to configure the environment and build or install the libraries that Tux Paint depends upon. John Popplewell put together some instructions for doing that here: </p>
<p>
<a href="http://www.johnnypops.co.uk/tuxpaint/">http://www.johnnypops.co.uk/tuxpaint/</a>
Open the MSYS2 shell from the "Start Menu" -&gt; "MSYS2 64bit" -&gt; "MSYS2 MSYS" and execute following command (press <b><code>[Enter]</code></b> or <b><code>[Return]</code></b> to accept the defaults for all questions):
<blockquote>
<code>
pacman -Syu
</code>
</blockquote>
</p>
<p>
Read the relevant notes if building for Win9X/ME. </p>
This will update core system and the window will close automatically. Repeat the steps above one more time to finish the remaining update process. </p>
<p>
Within the MSYS2 shell, run the following command to install basic development tools: <blockquote>
<code>
pacman -S base-devel msys2-devel git
</code>
</blockquote>
</p>
</blockquote>
<h4>Running the Installer:</h4>
<p>
<i>
Proceed to the next "<a href="#64bit">MinGW 64bit (x86_64) toolchains</a>" section, or skip to the "<a href="#32bit">MinGW 32bit (i686) toolchains</a>" section if you need only a 32bit build environment. </i>
</p>
<hr size="1" noshade width="75%" />
<h4>
<a name="64bit" id="64bit">
MinGW 64bit (x86_64) toolchains </a>
</h4>
<blockquote>
<p>
Within the MSYS2 shell, run the following command to install basic 64bit development tools: <blockquote>
<code>
pacman -S mingw-w64-x86_64-toolchain
</code>
</blockquote>
</p>
</blockquote>
<h4>
64bit (x86_64) dependency libraries for Tux Paint </h4>
<blockquote>
<p>
You can install tools and libraries required for compiling Tux Paint on MSYS2/MINGW using "<code>pacman</code>" except for SDL_Pango. </p>
<p>
"<code>ntldd</code>" is a small tool which examine windows executable files to list Dynamic Link Library (<code>.dll</code>) files they depends on. Tux Paint's packaging process for binary distribution uses it to find required <code>.dll</code> files. </p>
<p>
FLTK is a cross-platform GUI toolkit used by "Tux Paint Config.". You can skip installing it if you are <em>only</em> building "Tux Paint". </p>
<p>
<blockquote>
<code>
$ pacman -S mingw-w64-x86_64-SDL_{image,mixer,ttf}<br/>
$ pacman -S mingw-w64-x86_64-librsvg<br/>
$ pacman -S mingw-w64-x86_64-fribidi<br/>
$ pacman -S mingw-w64-x86_64-libimagequant<br/>
$ pacman -S mingw-w64-x86_64-fltk<br/>
$ pacman -S mingw64/mingw-w64-x86_64-ntldd-git
</code>
</blockquote>
</p>
<p>
<strong>Note:</strong> Close the shell before proceeding to the remaining process. </p>
</blockquote>
<h4>
Install SDL_Pango and re-install SDL on the 64bit environment </h4>
<blockquote>
<p>
SDL_Pango should be installed manually. In addition, you have to re-install SDL from the source code or you will see unnecessary blank window opens when starting Tux Paint. </p>
<p>
This time, use the MinGW "64bit" shell. Open the shell from the "Start Menu" -&gt; "MSYS2 64bit" -&gt; "MSYS2 MinGW 64-bit" </p>
<h5>SDL_Pango</h5>
<blockquote>
<p>
At first, you have to prepare source tar-ball and a required patch in the same directory. </p>
<ul>
<li>
Download <a href="https://sourceforge.net/projects/sdlpango/files/SDL_Pango/0.1.2/SDL_Pango-0.1.2.tar.gz/download">source tar-ball of SDL_Pango-0.1.2</a> from <a href="https://sourceforge.net/projects/sdlpango/">SDL_Pango's page on Sourceforge.net</a>. </li>
<li>
Download <a href="http://johnnypops.co.uk/tuxpaint/SDL_Pango-configure-extra-api.patch">a patch file</a> from <a href="http://www.johnnypops.co.uk/tuxpaint/">John Popplewell's "Tux Paint - MinGW/MSYS build instructions" webpage</a>. (This adds some extra (required) functionality to SDL_Pango.) </li>
</ul>
<p>
Build and install SDL_Pango as follows. <blockquote>
<code>
$ tar zxvf SDL_Pango-0.1.2.tar.gz<br/>
$ cd SDL_Pango-0.1.2/<br/>
$ patch -p0 &lt; ../SDL_Pango-configure-extra-api.patch<br/>
$ ./configure --prefix=/mingw64 &amp;&amp; make &amp;&amp; make install
</code>
</blockquote>
</p>
</blockquote>
<h5>SDL</h5>
<blockquote>
<p>
Download <a href="http://www.libsdl.org/release/SDL-1.2.15.tar.gz">source tar-ball of SDL_1.2.15</a> from <a href="http://www.libsdl.org/">libsdl.org</a>. </p>
<p>
Re-install SDL as follows. <blockquote>
<code>
$ tar zxvf SDL-1.2.15.tar.gz<br/>
$ cd SDL-1.2.15<br/>
$ ./configure --prefix=/mingw64 &amp;&amp; make &amp;&amp; make install
</code>
</blockquote>
</p>
</blockquote>
</blockquote>
<p>
<i>
Proceed to the next "<a href="#32bit">MinGW 32bit (i686) toolchains</a>" section, or skip to the "<a href="#imagemagick">ImageMagick</a>" section if you need only a 64bit build environment. </i>
</p>
<hr size="1" noshade width="75%" />
<h4>
<a name="32bit" id="32bit">
MinGW 32bit (i686) toolchains </a>
</h4>
<blockquote>
<p>
Within the MSYS2 shell, run the following command to install basic 32bit development tools: <blockquote>
<code>
pacman -S mingw-w64-i686-toolchain
</code>
</blockquote>
</p>
</blockquote>
<h4>
32bit (i686) dependency libraries for Tux Paint </h4>
<blockquote>
<p>
You can install tools and libraries required for compiling Tux Paint on MSYS2/MINGW using "<code>pacman</code>" except for SDL_Pango. </p>
<p>
"<code>ntldd</code>" is a small tool which examine windows executable files to list Dynamic Link Library (<code>.dll</code>) files they depends on. Tux Paint's packaging process for binary distribution uses it to find required <code>.dll</code> files. </p>
<p>
FLTK is a cross-platform GUI toolkit used by "Tux Paint Config.". You can skip installing it if you are <em>only</em> building "Tux Paint". </p>
<p>
<blockquote>
<code>
$ pacman -S mingw-w64-i686-SDL_{image,mixer,ttf}<br/>
$ pacman -S mingw-w64-i686-librsvg<br/>
$ pacman -S mingw-w64-i686-fribidi<br/>
$ pacman -S mingw-w64-i686-libimagequant<br/>
$ pacman -S mingw-w64-i686-fltk<br/>
$ pacman -S mingw-w64-i686-ntldd-git
</code>
</blockquote>
</p>
<p>
<strong>Note:</strong> Close the shell before proceeding to the remaining process. </p>
</blockquote>
<h4>
Install SDL_Pango and re-install SDL on the 32bit environment </h4>
<blockquote>
<p>
SDL_Pango should be installed manually. In addition, you have to re-install SDL from the source code or you will see unnecessary blank window opens when starting Tux Paint. </p>
<p>
This time, use the MinGW "32bit" shell. Open the shell from the "Start Menu" -&gt; "MSYS2 64bit" -&gt; "MSYS2 MinGW 32-bit" </p>
<h5>SDL_Pango</h5>
<blockquote>
<p>
At first, you have to prepare source tar-ball and a required patch in the same directory. </p>
<ul>
<li>
Download <a href="https://sourceforge.net/projects/sdlpango/files/SDL_Pango/0.1.2/SDL_Pango-0.1.2.tar.gz/download">source tar-ball of SDL_Pango-0.1.2</a> from <a href="https://sourceforge.net/projects/sdlpango/">SDL_Pango's page on Sourceforge.net</a>. </li>
<li>
Download <a href="http://johnnypops.co.uk/tuxpaint/SDL_Pango-configure-extra-api.patch">a patch file</a> from <a href="http://www.johnnypops.co.uk/tuxpaint/">John Popplewell's "Tux Paint - MinGW/MSYS build instructions" webpage</a>. (This adds some extra (required) functionality to SDL_Pango.) </li>
</ul>
<p>
Build and install SDL_Pango as follows. <blockquote>
<code>
$ tar zxvf SDL_Pango-0.1.2.tar.gz<br/>
$ cd SDL_Pango-0.1.2/<br/>
$ patch -p0 &lt; ../SDL_Pango-configure-extra-api.patch<br/>
$ ./configure --prefix=/mingw32 &amp;&amp; make &amp;&amp; make install
</code>
</blockquote>
</p>
</blockquote>
<h5>SDL</h5>
<blockquote>
<p>
Download <a href="http://www.libsdl.org/release/SDL-1.2.15.tar.gz">source tar-ball of SDL_1.2.15</a> from <a href="http://www.libsdl.org/">libsdl.org</a>. </p>
<p>
Re-install SDL as follows. <blockquote>
<code>
$ tar zxvf SDL-1.2.15.tar.gz<br/>
$ cd SDL-1.2.15<br/>
$ ./configure --prefix=/mingw32 &amp;&amp; make &amp;&amp; make install
</code>
</blockquote>
</p>
</blockquote>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>
<a name="imagemagick" id="imagemagick">ImageMagick</a>
</h4>
<blockquote>
<p>
<a href="https://imagemagick.org">ImageMagick</a> is a compilation of command line tools to create, edit, compose, or convert bitmap images supporting quite a large number of image formats. Tux Paint uses two functions ("convert" and "composite") in it to generate thumbnails for startar images and templates during the build process. </p>
<p>
Using official binary release available from "<a href="https://imagemagick.org/script/download.php#windowsand">Windows Binary Release</a>" is recommended, due to the commands installed with "<code>pacman</code>" on MinGW/MSYS not working as expected! </p>
<p>
Do not forget to enable "Install legacy utilities (e.g. convert)" while installing it, because Tux Paint's build process uses them. </p>
<p>
Add the path to the directory in which ImageMagick is installed at the top of your "PATH" environment variable. For example: <blockquote>
<code>
$ export PATH=/c/Program\ Files/ImageMagick-7.0.10-Q16-HDRI:$PATH
</code>
</blockquote>
</p>
<p>
You can make this permanent by adding the above to your the BASH shell configuration file, "<code>~/.bash_profile</code>". </p>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>Tux Paint</h4>
<blockquote>
<p>
You can compile 64bit binaries using MSYS2 64bit shell, and 32bit binaries using MSYS2 32bit shell, respectively. </p>
<ul>
<li>
Select "MSYS2 64bit" -&gt; "MSYS2 MinGW 64-bit" from the "Start Menu" to open the 64bit shell. </li>
<li>
Select "MSYS2 64bit" -&gt; "MSYS2 MinGW 32-bit" from the "Start Menu" to open the 32bit shell. </li>
</ul>
<p>
Compile Tux Paint with the following command: <blockquote>
<code>
$ make bdist-win32
</code>
</blockquote>
</p>
<p>
<strong>Note:</strong> At this point, you will want to build "Tux Paint Config." for Windows, so it can be included along with "Tux Paint", if you're making an official (or test) release. The build process will look for it in a directory named "<code>tuxpaint-config</code>" (with no version number, e.g., "<code>tuxpaint-config-X.Y.Z</code>"). See "Tux Paint Config."'s INSTALL.txt documentation for details. </p>
<p>
All the files needed for starting Tux Paint (and Tux Paint Config.) are collected in the directory for binary distribution "<code>bdist</code>" directory under "<code>win32</code>". You can start them by double-clicking their executable (<code>.exe</code>) files in the "<code>bdist</code>" directory. </p>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>Building the Tux Paint Windows Installer:</h4>
<blockquote>
<p>
<a href="https://jrsoftware.org/isinfo.php">Inno Setup</a> is used to build executable installer for Tux Paint. Therefore you have to install it in the first place. </p>
<p>
</p>
<p>
Then, you can easily build an executable installer by right-clicking on the "<code>tuxpaint.iss</code>" icon in the "<code>win32</code>" directory and selecting "Compile" on the list. It will run for a while, and eventually you will find a "<code>tuxpaint-<i>X.Y.Z</i>-win32-installer.exe</code>" file in the same directory. </p>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>Running the Tux Paint Windows Installer:</h4>
<blockquote>
<p>
Double-click the Tux Paint installer executable (.EXE file) and follow the instructions.
@ -231,6 +558,8 @@
At this point, you can click 'Install' to install Tux Paint! </p>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>Changing the Settings Using the Shortcut:</h4>
<blockquote>
<p>
@ -267,6 +596,8 @@
When you have finished, click "OK." </p>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>If Something Goes Wrong:</h4>
<blockquote>
<p>
@ -277,7 +608,12 @@
</blockquote>
</blockquote>
<h3>Linux/Unix Users:</h3>
<hr size="1" noshade />
<h3>
<a name="compiling-linux" id="compiling-linux">
Linux/Unix Users </a>
</h3>
<blockquote>
<h4>Compiling:</h4>
<blockquote>
@ -294,11 +630,13 @@
</blockquote>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>
Disabling SVG support (and hence Cairo, libSVG, and svg-cairo dependencies): </h4>
<blockquote>
<p>
To disable SVG support (e.g., if your system is not currently supported by the Cairo library or other SVG-related dependencies), you can run "<code>make</code>" with "<code>SVG_LIB= SVG_CFLAGS= NOSVGFLAG=NOSVG</code>" added:
To disable SVG support (e.g., if your system is not currently supported by the Cairo library or other SVG-related dependencies), you can run "<code>make</code>" with "<code style="white-space: nowrap;">SVG_LIB= SVG_CFLAGS= NOSVGFLAG=NOSVG</code>" added:
<blockquote>
<code>
$ make SVG_LIB= SVG_CFLAGS=
@ -306,6 +644,8 @@
</blockquote>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>
Disabling Pango support (and hence Pango, Cairo, etc. dependencies): </h4>
<blockquote>
@ -318,6 +658,8 @@
</blockquote>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>Disabling Sound at Compile-time:</h4>
<blockquote>
If you don't have a sound card, or would prefer to build the program with no sound support (and therefore without a the <code>SDL_mixer</code> dependency), you can run "<code>make</code>" with "<code>SDL_MIXER_LIB=</code>" added: </p>
@ -328,18 +670,24 @@
</blockquote>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>Other options:</h4>
<blockquote>
<p>
Various other options (e.g., installation paths) may be overridden; see them in "<code>Makefile</code>" for further details. </p>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>If you get errors:</h4>
<blockquote>
<p>
If you receive any errors during compile-time, make sure you have the appropriate libraries installed (see above). If using packaged versions of the libraries (e.g., RPMs under RedHat or DEBs under Debian), be sure to get the corresponding "<code>-dev</code>" or "<code>-devel</code>" packages as well, otherwise you won't be able to compile Tux Paint (and other programs) from source! </p>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>Installng:</h4>
<blockquote>
<p>
@ -422,15 +770,155 @@
</blockquote>
</blockquote>
</blockquote>
<hr size="1" noshade />
<h3>
<a name="compiling-macos" id="compiling-macos">
macOS Users </a>
</h3>
<p style="font-size: small;">
<em>
September 21, 2021 Mark K. Kim &lt;<a href="mailto:markuskimius@gmail.com">markuskimius@gmail.com</a>&gt;
</em>
</p>
<blockquote>
<p>
Tux Paint 0.9.22 and earlier required building Tux Paint from the Xcode IDE. Starting with 0.9.23, however, Tux Paint for macOS is built as though it were a Linux application. </p>
<h4>Prerequisites</h4>
<blockquote>
<p>
Although Tux Paint is built without the Xcode IDE, Xcode itself is still required to build Tux Paint. <a href="https://developer.apple.com/xcode/ide/">Download it from the App Store</a>, and launch it once to accept its license agreements. You may also need to install the Xcode command line tools using the command: <blockquote>
<code>
xcode-select --install
</code>
</blockquote>
</p>
<p>
Building Tux Paint also requires various libraries. We install them from MacPorts where possible, source code otherwise. Install MacPorts to the default <code>/opt/local</code> path according to the instructions found on their website: <a href="https://www.macports.org/">https://www.macports.org/</a> <ul>
<li><code>ImageMagick</code></li>
<li><code>cairo</code></li>
<li><code>fribidi</code></li>
<li><code>lbzip2</code></li>
<li><code>libimagequant</code><sup>*</sup></li>
<li><code>libpaper</code></li>
<li><code>libpng</code></li>
<li><code>librsvg</code></li>
<li><code>libsdl</code></li>
<li><code>libsdl_image</code></li>
<li><code>libsdl_mixer</code></li>
<li><code>libsdl_pango</code></li>
<li><code>libsdl_ttf</code></li>
<li><code>pkgconfig</code></li>
<li><code>zlib</code></li>
</ul>
... but you should install any package that is required by the latest version of Tux Paint.<br/>
<br/>
<sup>*</sup> Not available from MacPorts as of this writing, see below. </p>
<h5>libimagequant</h5>
<blockquote>
<p>
<code>libimagequant</code> is not available from MacPorts as of this writing. It can be installed from the source code as follows. It should be installed to <code>/opt/local</code> (same as MacPorts) for the library to be included in <code>TuxPaint.dmg</code>. <blockquote>
<code>
$ git clone https://github.com/ImageOptim/libimagequant.git<br/>
$ cd libimagequant<br/>
$ ./configure --prefix=/opt/local<br/>
$ make<br/>
$ sudo make install
</code>
</blockquote>
</p>
</blockquote>
<p>
<strong>WARNING:</strong> Having any UNIX-like toolset installed on your Mac besides MacPorts and Xcode, such as Fink or Brew, will prevent your app bundle from being portable. Be sure Fink and Brew are not accessible from your build environment. </p>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>How to Build</h4>
<blockquote>
<p>
Simply, run: <blockquote>
<code>
% make<br/>
% make install
</code>
</blockquote>
... to create the <code>TuxPaint.app</code> application bundle that can be run in-place or copied to <code>/Applications</code>. It also creates <code>TuxPaint.dmg</code> for distribution. </p>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>Known Issues</h4>
<blockquote>
<ul>
<li>
A macOS binary built on a specific version of macOS only runs on that version of macOS or later. To ensure Tux Paint can run on the oldest version of macOS possible, build it on the oldest version of macOS available. As of this writing we know Tux Paint cannot be built to run on macOS 10.7 or earlier.<br/>
<br/>
See "Old Versions of macOS" below for best-effort instructions on how to obtain, install, and build Tux Paint on an old version of macOS. </li>
</ul>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>Old Versions of macOS</h4>
<blockquote>
<p>
Some old versions of macOS can be downloaded from Apple's support page: <a href="https://support.apple.com/en-us/HT211683">https://support.apple.com/en-us/HT211683</a> </p>
<p>
macOS does allow dual booting of multiple versions of the OS, but it's safer and easier to install the old macOS onto a flash drive. Wherever you're installing it, the target drive's partitioniong scheme and partition type must match what the old macOS expects, so use the Disk Utility to partition and format the flash drive accordingly. </p>
<p>
As of this writing, the oldest version of macOS available on Apple's support site is Yosemite 10.10, which expects "GPT (GUID Partition Table)" partitioning scheme instead of the older MBR scheme, and "Mac OS Extended (Journaled)" as the partition type instead of the newer APFS partition type. </p>
<p>
Upon launching the installer, if you get a popup about macOS being too old or new to be installed, a bootable installer can be created using the instructions found here: <a href="https://support.apple.com/en-mide/HT201372">https://support.apple.com/en-mide/HT201372</a> </p>
<p>
It has been found that macOS can be installed onto the bootable media itself, so you can make the flash drive into a bootable installer then install the old macOS onto the same flash drive. </p>
<p>
Once the old macOS is installed, you may find the Xcode on the App Store is too new to run on the version of the old macOS. Old versions of Xcode can be downloaded from Apple's Developer site in an area accessible with free registration: <a href="https://developer.apple.com/download/more/">https://developer.apple.com/download/more/</a> </p>
<p>
The list of macOS versions and the last version of Xcode compatible with them are laid out nicely on the Wikipedia page on Xcode: <a href="https://en.wikipedia.org/wiki/Xcode#Version_comparison_table">https://en.wikipedia.org/wiki/Xcode#Version_comparison_table</a> </p>
<p>
And because Xcode is being installed manually, you can skip the step to install the Xcode command line tools (do not run "<code style="white-space: nowrap;">xcode-select --install</code>") but otherwise build Tux Paint using the same steps described in the earlier part of this document. </p>
</blockquote>
</blockquote>
</blockquote>
<h2>Debugging:</h2>
<blockquote>
Debugging (to "STDOUT", e.g. to the terminal, or to a "<code>stdout.txt</code>" file, on Windows) can be enabled by setting "<code>DEBUG</code>" (and, if verbose logging is wanted, "<code>VERBOSE</code>") <code>#define</code>s in "<code>src/debug.h</code>". </blockquote>
<hr size="2" noshade />
<h2>Uninstalling Tux Paint:</h2>
<h2>
<a name="debugging" id="debugging">
Debugging </a>
</h2>
<blockquote>
<h3>Windows</h3>
Debugging output &mdash; to "STDOUT" on Linux and Unix, to a "<code>stdout.txt</code>" file on Windows, and to the file "<code>/tmp/tuxpaint.log</code>" on macOS &mdash; can be enabled by setting "<code>DEBUG</code>" (and, if verbose logging is wanted, "<code>VERBOSE</code>") <code>#define</code>s in "<code>src/debug.h</code>" and (re)compiling Tux Paint. </blockquote>
<hr size="2" noshade />
<h2>
<a name="uninstalling" id="uninstalling">
Uninstalling Tux Paint </h2>
</h2>
<blockquote>
<h3>
<a name="uninstalling-windows" id="uninstalling-windows">
Windows </a>
</h3>
<blockquote>
<h4>Using the Uninstaller</h4>
<blockquote>
@ -448,10 +936,27 @@
</blockquote>
</blockquote>
<h3>Linux</h3>
<hr size="1" noshade />
<h3>
<a name="uninstalling-macos" id="uninstalling-macos">
macOS </a>
</h3>
<blockquote>
<p>
Within the Tux Paint source directory (where you compiled Tux Paint), you can use the "<code>make uninstall</code>" target to uninstall Tux Paint. By default, this must be done by the "root" user ('superuser'), but if you installed Tux Paint somewhere else (e.g., using a "<code>PREFIX=...</code>" setting to "<code>make</code>" and "<code>make install</code>"), you may not, and will want to provide those same settings here. (See the installation instructions above for further information.) </p>
Delete "<code>TuxPaint.app</code>" from the "Applications" folder. Data files, including the configuration files, stamps, and saved pictures, may be found in "<code style="white-space: nowrap;">Library/Application Support/TuxPaint</code>" (all users) and "<code style="white-space: nowrap;">/Users/<i>USERNAME</i>/Library/Application Support/TuxPaint</code>" (individual users). </p>
</blockquote>
<hr size="1" noshade />
<h3>
<a name="uninstalling-linux" id="uninstalling-linux">
Linux </a>
</h3>
<blockquote>
<p>
Within the Tux Paint source directory (where you compiled Tux Paint), you can use the "<code style="white-space: nowrap;">make uninstall</code>" target to uninstall Tux Paint. By default, this must be done by the "root" user ('superuser'), but if you installed Tux Paint somewhere else (e.g., using a "<code>PREFIX=...</code>" setting to "<code>make</code>" and "<code style="white-space: nowrap;">make install</code>"), you may not, and will want to provide those same settings here. (See the <a href="#compiling-linux">installation instructions above</a> for further information.) </p>
</blockquote>
<blockquote>
</body>

5383
docs/en/html/OPTIONS.html
View file

File diff suppressed because it is too large Load diff

2
docs/en/html/PNG.html
View file

@ -17,7 +17,7 @@
width="205"
height="210"
alt="Tux Paint"><br>
version 0.9.26<br/>
version 0.9.27<br/>
PNG Documentation </h1>
<p>

18
docs/en/html/README.html
View file

@ -17,7 +17,7 @@
width="205"
height="210"
alt="Tux Paint"><br>
version 0.9.26 </h1>
version 0.9.27 </h1>
<h3>
A simple drawing program for children </h3>
@ -28,7 +28,7 @@
</p>
<p>
June 28, 2021 </p>
September 5, 2021 </p>
</center>
<hr size="2"
@ -408,6 +408,15 @@
<p>
If you hold the mouse button down, and move the mouse, it will draw as you move. </p>
<p>
Some brushes are animated &mdash; they change their shape as you draw them. A good example of this is the vines brush that ships with Tux Paint. These brushes will have a small "filmstrip" icon drawn on their Selector buttons. </p>
<p>
Other brushes are directional &mdash; they will draw a different shape depending on what direction you are painting with them. An example of this is the arrow brush that ships with Tux Paint. These brushes have a small 8-way arrow icon drawn on their Selector buttons. </p>
<p>
Finally, some brushes can be both direction <em>and</em> animated. Examples of this are the cat and squirrel brushes that ship with Tux Paint. These brushes will have both the "filmstrip" and 8-way arrow icons. </p>
<p>
As you draw, a sound is played. The bigger the brush, the lower the pitch. </p>
<br clear="all">
@ -503,6 +512,9 @@
<p>
Let go of the mouse to complete the line. A "sproing!" sound will play. </p>
<p>
Some brushes are animated, and will show a pattern of shapes along the line. Others are directional, and will show a different shape depending on the angle of the brush. And finally some are both animated and directional. See "Paint", above, to learn more. </p>
<br clear="all">
<p align="center">
@ -605,7 +617,7 @@
Choose a font (from the 'Letters' available on the right) and a color (from the color palette near the bottom). Click on the screen and a cursor will appear. Type text and it will show up on the screen. </p>
<p>
Press <strong><code>[Enter]</code></strong> or <strong><code>[Return]</code></strong> and the text will be drawn onto the picture and the cursor will move down one line. </p>
Press <b><code>[Enter]</code></b> or <b><code>[Return]</code></b> and the text will be drawn onto the picture and the cursor will move down one line. </p>
<p>
Alternatively, press <strong><code>[Tab]</code></strong> and the text will be drawn onto the picture, but the cursor will move to the right of the text, rather than down a line, and to the left. (This can be useful to create a line of text with mixed colors, fonts, styles and sizes.) </p>

2
docs/en/html/SIGNALS.html
View file

@ -17,7 +17,7 @@
width="205"
height="210"
alt="Tux Paint"><br>
version 0.9.26<br/>
version 0.9.27<br/>
Signals Documentation </h1>
<p>

2
docs/en/html/SVG.html
View file

@ -17,7 +17,7 @@
width="205"
height="210"
alt="Tux Paint"><br>
version 0.9.26<br/>
version 0.9.27<br/>
SVG Documentation </h1>
<p>

30
docs/es_ES.UTF-8/ADVANCED-STAMPS-HOWTO.txt
View file

@ -1,9 +1,27 @@
Tux Paint
versión 0.9.26 Advanced Stamps 'How-To'
versión 0.9.27 Advanced Stamps 'How-To'
Copyright © 2006-2021 by Albert Cahalan and others; see AUTHORS.
http://www.tuxpaint.org/
agosto 29, 2021
----------------------------------------------------------------------
+----------------------------------------+
|Table of Contents |
|----------------------------------------|
| * About this 'How-To' |
| * Image choice is crucial |
| * Prepare the mask |
| * Replace the fringe and junk pixels |
| * Save the image for Tux Paint |
+----------------------------------------+
----------------------------------------------------------------------
----------------------------------------------------------------------
About this 'How-To'
This 'How-To' assumes that you want to make an excellent Tux Paint
@ -18,6 +36,8 @@ About this 'How-To'
also best done with custom software, but are not troublesome to do as
follows.
----------------------------------------------------------------------
Image choice is crucial
License
@ -66,6 +86,8 @@ Image choice is crucial
will need to draw new ones. If only one is buried, you might be able
to copy the other one as a replacement.
----------------------------------------------------------------------
Prepare the image
First of all, be sure to avoid re-saving the image as a JPEG. This
@ -101,6 +123,8 @@ Prepare the image
normally. This would cause data loss. You will be given special scaling
instructions later.
----------------------------------------------------------------------
Prepare the mask
Get used to doing [Ctrl]-click and [Alt]-click on the thumbnail images
@ -161,6 +185,8 @@ Prepare the mask
expected color. Invert the selection, then paint these away using the
pencil tool. Do this operation for both white and black.
----------------------------------------------------------------------
Replace the fringe and junk pixels
Still viewing the mask, select by color. Choose black. Shrink the
@ -222,6 +248,8 @@ Replace the fringe and junk pixels
edge, you should use the pencil tool (or sloppy select with
drag-and-drop color) to ensure that the result will compress well.
----------------------------------------------------------------------
Save the image for Tux Paint
It is very easy to ruin your hard work. Image editors can silently

4
docs/es_ES.UTF-8/ENVVARS.txt
View file

@ -1,11 +1,11 @@
Tux Paint
versión 0.9.26
versión 0.9.27
Environment Variables Documentation
Copyright © 2021-2021 by various contributors; see AUTHORS.
http://www.tuxpaint.org/
mayo 11, 2021
agosto 8, 2021
----------------------------------------------------------------------

31
docs/es_ES.UTF-8/EXTENDING.txt
View file

@ -1,11 +1,11 @@
Extending
Tux Paint
versión 0.9.26
versión 0.9.27
Copyright © 2002-2021 by various contributors; see AUTHORS.
http://www.tuxpaint.org/
mayo 31, 2021
septiembre 6, 2021
----------------------------------------------------------------------
@ -212,17 +212,26 @@ Brushes
Add a line containing the word "directional" to the brush's data
file.
Animated Directional Brushes
Rotating Brushes
You may mix both animated and directional features into one brush.
Use both options ("frames=N" and "directional"), in separate lines
in the brush's ".dat" file.
As of Tux Paint version 0.9.27, you may now create rotating brushes.
As the brush is used, it is rotated 360 degrees, depending on the
direction the brush is going.
Lay the brush out so that each 3x3 set of directional shapes are
laid out across a wide PNG image. For example, if the brush is 30x30
and there are 5 frames, it would be 450x90. (The leftmost 150x90
pixels of the image represent the 9 direction shapes for the first
frame, for example.)
Add a line containing the word "rotate" to the brush's data file.
Animated Directional or Rotating Brushes
You may mix both animated and either directional or rotating
features into one brush. Use both options desired ("frames=N" and
"directional" or "rotate"), in separate lines in the brush's ".dat"
file.
For directional brushes, lay the brush out so that each 3x3 set of
directional shapes are laid out across a wide PNG image. For
example, if the brush is 30x30 and there are 5 frames, it would be
450x90. (The leftmost 150x90 pixels of the image represent the 9
direction shapes for the first frame, for example.)
Place the brush image PNGs (and any data text files) in the "brushes"
directory.

19
docs/es_ES.UTF-8/FAQ.txt
View file

@ -1,10 +1,25 @@
Tux Paint
versión 0.9.26 Frequently Asked Questions
versión 0.9.27 Frequently Asked Questions
Copyright © 2002-2021 by various contributors; see AUTHORS.
http://www.tuxpaint.org/
junio 2, 2021
agosto 29, 2021
----------------------------------------------------------------------
+------------------------------+
|Table of Contents |
|------------------------------|
| * Drawing-related |
| * Interface Problems |
| * Printing |
| * Saving |
| * Audio Problems |
| * Fullscreen Mode Problems |
| * Other Probelms |
| * Help / Contact |
+------------------------------+
----------------------------------------------------------------------

474
docs/es_ES.UTF-8/INSTALL.txt
View file

@ -1,26 +1,46 @@
Tux Paint
versión 0.9.26
versión 0.9.27
Installation Documentation
Copyright © 2002-2021 by various contributors; see AUTHORS.
http://www.tuxpaint.org/
marzo 9, 2021
septiembre 5, 2021
----------------------------------------------------------------------
Requirements:
+----------------------------------------------------+
|Table of Contents |
|----------------------------------------------------|
| * Requirements |
| * Simple DirectMedia Layer library (libSDL) |
| * Other Libraries |
| * Compiling and Installation |
| * Windows Users |
| * Linux/Unix Users |
| * macOS Users |
| * Debugging |
| * Uninstalling Tux Paint |
| * Windows |
| * macOS |
| * Linux |
+----------------------------------------------------+
libSDL
----------------------------------------------------------------------
Requirements
Simple DirectMedia Layer library (libSDL)
Tux Paint requires the Simple DirectMedia Layer Library (libSDL), an
Open Source multimedia programming library available under the GNU
Lesser General Public License (LGPL).
Along with libSDL, Tux Paint depends on a number of other SDL 'helper'
libraries: SDL_Image (for graphics files), SDL_TTF and (optionally)
SDL_Pango (for True Type Font support) and, optionally, SDL_Mixer (for
sound effects).
libraries: SDL_Image (for graphics files), SDL_gfx (for some graphical
functions, like rotation), SDL_TTF and (optionally) SDL_Pango (for
True Type Font support) and, optionally, SDL_Mixer (for sound
effects).
Linux/Unix Users:
@ -30,6 +50,9 @@ Requirements:
* libSDL: http://www.libsdl.org/
* SDL_Image: http://www.libsdl.org/projects/SDL_image/
* SDL_gfx:
https://www.ferzkopp.net/wordpress/2016/01/02/sdl_gfx-sdl2_gfx/
(https://sourceforge.net/projects/sdlgfx/)
* SDL_TTF: http://www.libsdl.org/projects/SDL_ttf/
* SDL_Pango: http://sourceforge.net/projects/sdlpango/ (optional)
* SDL_Mixer: http://www.libsdl.org/projects/SDL_mixer/ (optional)
@ -116,55 +139,261 @@ Requirements:
http://netpbm.sourceforge.net/
Compiling and Installation:
----------------------------------------------------------------------
Compiling and Installation
Tux Paint is released under the GNU General Public License (GPL) (see
"COPYING.txt" for details), and therefore the 'source code' to the
program is available freely.
Windows Users:
Windows Users
Compiling:
octubre 25, 2020 Shin-ichi TOYAMA shin1@wmail.plala.or.jp
<shin1@wmail.plala.or.jp>
Compiling Set-Up
As of February 2005 (starting with Tux Paint 0.9.15), the "Makefile"
includes support for building on a Windows system using MinGW/MSYS
(http://www.mingw.org/).
(https://sourceforge.net/projects/msys2/).
After configuring the environment and building and installing all
the dependencies, use these commands, in MSYS, to build, install and
run:
Many tools and libraries are required to build Tux Paint. The
package management system "pacman" helps you install them
automatically solving complicated dependencies.
Prior to version 0.9.20:
Download the latest MSYS2 environment from
https://sourceforge.net/projects/msys2/files/Base/ and install it
where you'd like (the default is "C:\msys64")
$ make win32
$ make install-win32
$ tuxpaint
Open the MSYS2 shell from the "Start Menu" -> "MSYS2 64bit" ->
"MSYS2 MSYS" and execute following command (press [Enter] or
[Return] to accept the defaults for all questions):
Version 0.9.20 and beyond:
pacman -Syu
$ make
$ make install
$ tuxpaint
This will update core system and the window will close
automatically. Repeat the steps above one more time to finish the
remaining update process.
Use the following command to build a version suitable for
redistribution with the installer or in a zip-file:
Within the MSYS2 shell, run the following command to install basic
development tools:
pacman -S base-devel msys2-devel git
Proceed to the next "MinGW 64bit (x86_64) toolchains" section, or skip
to the "MinGW 32bit (i686) toolchains" section if you need only a
32bit build environment.
-------------------------------------------------------
MinGW 64bit (x86_64) toolchains
Within the MSYS2 shell, run the following command to install basic
64bit development tools:
pacman -S mingw-w64-x86_64-toolchain
64bit (x86_64) dependency libraries for Tux Paint
You can install tools and libraries required for compiling Tux Paint
on MSYS2/MINGW using "pacman" except for SDL_Pango.
"ntldd" is a small tool which examine windows executable files to
list Dynamic Link Library (.dll) files they depends on. Tux Paint's
packaging process for binary distribution uses it to find required
.dll files.
FLTK is a cross-platform GUI toolkit used by "Tux Paint Config.".
You can skip installing it if you are only building "Tux Paint".
$ pacman -S mingw-w64-x86_64-SDL_{image,mixer,ttf}
$ pacman -S mingw-w64-x86_64-librsvg
$ pacman -S mingw-w64-x86_64-fribidi
$ pacman -S mingw-w64-x86_64-libimagequant
$ pacman -S mingw-w64-x86_64-fltk
$ pacman -S mingw64/mingw-w64-x86_64-ntldd-git
Note: Close the shell before proceeding to the remaining process.
Install SDL_Pango and re-install SDL on the 64bit environment
SDL_Pango should be installed manually. In addition, you have to
re-install SDL from the source code or you will see unnecessary
blank window opens when starting Tux Paint.
This time, use the MinGW "64bit" shell. Open the shell from the
"Start Menu" -> "MSYS2 64bit" -> "MSYS2 MinGW 64-bit"
SDL_Pango
At first, you have to prepare source tar-ball and a required patch
in the same directory.
* Download source tar-ball of SDL_Pango-0.1.2 from SDL_Pango's
page on Sourceforge.net.
* Download a patch file from John Popplewell's "Tux Paint -
MinGW/MSYS build instructions" webpage. (This adds some extra
(required) functionality to SDL_Pango.)
Build and install SDL_Pango as follows.
$ tar zxvf SDL_Pango-0.1.2.tar.gz
$ cd SDL_Pango-0.1.2/
$ patch -p0 < ../SDL_Pango-configure-extra-api.patch
$ ./configure --prefix=/mingw64 && make && make install
SDL
Download source tar-ball of SDL_1.2.15 from libsdl.org.
Re-install SDL as follows.
$ tar zxvf SDL-1.2.15.tar.gz
$ cd SDL-1.2.15
$ ./configure --prefix=/mingw64 && make && make install
Proceed to the next "MinGW 32bit (i686) toolchains" section, or skip
to the "ImageMagick" section if you need only a 64bit build
environment.
-------------------------------------------------------
MinGW 32bit (i686) toolchains
Within the MSYS2 shell, run the following command to install basic
32bit development tools:
pacman -S mingw-w64-i686-toolchain
32bit (i686) dependency libraries for Tux Paint
You can install tools and libraries required for compiling Tux Paint
on MSYS2/MINGW using "pacman" except for SDL_Pango.
"ntldd" is a small tool which examine windows executable files to
list Dynamic Link Library (.dll) files they depends on. Tux Paint's
packaging process for binary distribution uses it to find required
.dll files.
FLTK is a cross-platform GUI toolkit used by "Tux Paint Config.".
You can skip installing it if you are only building "Tux Paint".
$ pacman -S mingw-w64-i686-SDL_{image,mixer,ttf}
$ pacman -S mingw-w64-i686-librsvg
$ pacman -S mingw-w64-i686-fribidi
$ pacman -S mingw-w64-i686-libimagequant
$ pacman -S mingw-w64-i686-fltk
$ pacman -S mingw-w64-i686-ntldd-git
Note: Close the shell before proceeding to the remaining process.
Install SDL_Pango and re-install SDL on the 32bit environment
SDL_Pango should be installed manually. In addition, you have to
re-install SDL from the source code or you will see unnecessary
blank window opens when starting Tux Paint.
This time, use the MinGW "32bit" shell. Open the shell from the
"Start Menu" -> "MSYS2 64bit" -> "MSYS2 MinGW 32-bit"
SDL_Pango
At first, you have to prepare source tar-ball and a required patch
in the same directory.
* Download source tar-ball of SDL_Pango-0.1.2 from SDL_Pango's
page on Sourceforge.net.
* Download a patch file from John Popplewell's "Tux Paint -
MinGW/MSYS build instructions" webpage. (This adds some extra
(required) functionality to SDL_Pango.)
Build and install SDL_Pango as follows.
$ tar zxvf SDL_Pango-0.1.2.tar.gz
$ cd SDL_Pango-0.1.2/
$ patch -p0 < ../SDL_Pango-configure-extra-api.patch
$ ./configure --prefix=/mingw32 && make && make install
SDL
Download source tar-ball of SDL_1.2.15 from libsdl.org.
Re-install SDL as follows.
$ tar zxvf SDL-1.2.15.tar.gz
$ cd SDL-1.2.15
$ ./configure --prefix=/mingw32 && make && make install
-------------------------------------------------------
ImageMagick
ImageMagick is a compilation of command line tools to create, edit,
compose, or convert bitmap images supporting quite a large number of
image formats. Tux Paint uses two functions ("convert" and
"composite") in it to generate thumbnails for startar images and
templates during the build process.
Using official binary release available from "Windows Binary
Release" is recommended, due to the commands installed with "pacman"
on MinGW/MSYS not working as expected!
Do not forget to enable "Install legacy utilities (e.g. convert)"
while installing it, because Tux Paint's build process uses them.
Add the path to the directory in which ImageMagick is installed at
the top of your "PATH" environment variable. For example:
$ export PATH=/c/Program\ Files/ImageMagick-7.0.10-Q16-HDRI:$PATH
You can make this permanent by adding the above to your the BASH
shell configuration file, "~/.bash_profile".
-------------------------------------------------------
Tux Paint
You can compile 64bit binaries using MSYS2 64bit shell, and 32bit
binaries using MSYS2 32bit shell, respectively.
* Select "MSYS2 64bit" -> "MSYS2 MinGW 64-bit" from the "Start
Menu" to open the 64bit shell.
* Select "MSYS2 64bit" -> "MSYS2 MinGW 32-bit" from the "Start
Menu" to open the 32bit shell.
Compile Tux Paint with the following command:
$ make bdist-win32
Or if building for Win9x/ME:
Note: At this point, you will want to build "Tux Paint Config." for
Windows, so it can be included along with "Tux Paint", if you're
making an official (or test) release. The build process will look
for it in a directory named "tuxpaint-config" (with no version
number, e.g., "tuxpaint-config-X.Y.Z"). See "Tux Paint Config."'s
INSTALL.txt documentation for details.
$ BDIST_WIN9X=1 make bdist-win32
All the files needed for starting Tux Paint (and Tux Paint Config.)
are collected in the directory for binary distribution "bdist"
directory under "win32". You can start them by double-clicking their
executable (.exe) files in the "bdist" directory.
Before any of the above will work, you need to configure the
environment and build or install the libraries that Tux Paint
depends upon. John Popplewell put together some instructions for
doing that here:
-------------------------------------------------------
http://www.johnnypops.co.uk/tuxpaint/
Building the Tux Paint Windows Installer:
Read the relevant notes if building for Win9X/ME.
Inno Setup is used to build executable installer for Tux Paint.
Therefore you have to install it in the first place.
Running the Installer:
Then, you can easily build an executable installer by right-clicking
on the "tuxpaint.iss" icon in the "win32" directory and selecting
"Compile" on the list. It will run for a while, and eventually you
will find a "tuxpaint-X.Y.Z-win32-installer.exe" file in the same
directory.
-------------------------------------------------------
Running the Tux Paint Windows Installer:
Double-click the Tux Paint installer executable (.EXE file) and
follow the instructions.
@ -183,6 +412,8 @@ Compiling and Installation:
At this point, you can click 'Install' to install Tux Paint!
-------------------------------------------------------
Changing the Settings Using the Shortcut:
To change program settings, right-click on the TuxPaint shortcut and
@ -211,6 +442,8 @@ Compiling and Installation:
When you have finished, click "OK."
-------------------------------------------------------
If Something Goes Wrong:
If, when you double-click on the shortcut to run Tux Paint, nothing
@ -222,7 +455,9 @@ Compiling and Installation:
just be due to incorrect character-case (capital 'Z' instead of
lowercase 'z') or a missing (or extra) '-' (dash).
Linux/Unix Users:
----------------------------------------------------------------------
Linux/Unix Users
Compiling:
@ -235,6 +470,8 @@ Compiling and Installation:
$ make
-------------------------------------------------------
Disabling SVG support (and hence Cairo, libSVG, and svg-cairo dependencies):
To disable SVG support (e.g., if your system is not currently
@ -244,6 +481,8 @@ Compiling and Installation:
$ make SVG_LIB= SVG_CFLAGS=
-------------------------------------------------------
Disabling Pango support (and hence Pango, Cairo, etc. dependencies):
Prior to version 0.9.18, Tux Paint used the libSDL_ttf library for
@ -254,6 +493,8 @@ Compiling and Installation:
$ make SDL_PANGO_LIB=
-------------------------------------------------------
Disabling Sound at Compile-time:
If you don't have a sound card, or would prefer to build the program
@ -262,11 +503,15 @@ Compiling and Installation:
$ make SDL_MIXER_LIB=
-------------------------------------------------------
Other options:
Various other options (e.g., installation paths) may be overridden;
see them in "Makefile" for further details.
-------------------------------------------------------
If you get errors:
If you receive any errors during compile-time, make sure you have
@ -276,6 +521,8 @@ Compiling and Installation:
packages as well, otherwise you won't be able to compile Tux Paint
(and other programs) from source!
-------------------------------------------------------
Installng:
Assuming no fatal errors occured, you can now install the program so
@ -351,13 +598,150 @@ Compiling and Installation:
Note: This list is out of date. See "Makefile" and "Makefile-i18n"
for a complete list.
Debugging:
----------------------------------------------------------------------
Debugging (to "STDOUT", e.g. to the terminal, or to a "stdout.txt" file,
on Windows) can be enabled by setting "DEBUG" (and, if verbose logging
is wanted, "VERBOSE") #defines in "src/debug.h".
macOS Users
Uninstalling Tux Paint:
septiembre 21, 2021 Mark K. Kim <markuskimius@gmail.com>
Tux Paint 0.9.22 and earlier required building Tux Paint from the
Xcode IDE. Starting with 0.9.23, however, Tux Paint for macOS is built
as though it were a Linux application.
Prerequisites
Although Tux Paint is built without the Xcode IDE, Xcode itself is
still required to build Tux Paint. Download it from the App Store,
and launch it once to accept its license agreements. You may also
need to install the Xcode command line tools using the command:
xcode-select --install
Building Tux Paint also requires various libraries. We install them
from MacPorts where possible, source code otherwise. Install
MacPorts to the default /opt/local path according to the
instructions found on their website: https://www.macports.org/
* ImageMagick
* cairo
* fribidi
* lbzip2
* libimagequant^*
* libpaper
* libpng
* librsvg
* libsdl
* libsdl_image
* libsdl_mixer
* libsdl_pango
* libsdl_ttf
* pkgconfig
* zlib
... but you should install any package that is required by the
latest version of Tux Paint.
^* Not available from MacPorts as of this writing, see below.
libimagequant
libimagequant is not available from MacPorts as of this writing.
It can be installed from the source code as follows. It should be
installed to /opt/local (same as MacPorts) for the library to be
included in TuxPaint.dmg.
$ git clone https://github.com/ImageOptim/libimagequant.git
$ cd libimagequant
$ ./configure --prefix=/opt/local
$ make
$ sudo make install
WARNING: Having any UNIX-like toolset installed on your Mac besides
MacPorts and Xcode, such as Fink or Brew, will prevent your app
bundle from being portable. Be sure Fink and Brew are not accessible
from your build environment.
-------------------------------------------------------
How to Build
Simply, run:
% make
% make install
... to create the TuxPaint.app application bundle that can be run
in-place or copied to /Applications. It also creates TuxPaint.dmg
for distribution.
-------------------------------------------------------
Known Issues
* A macOS binary built on a specific version of macOS only runs on
that version of macOS or later. To ensure Tux Paint can run on
the oldest version of macOS possible, build it on the oldest
version of macOS available. As of this writing we know Tux Paint
cannot be built to run on macOS 10.7 or earlier.
See "Old Versions of macOS" below for best-effort instructions
on how to obtain, install, and build Tux Paint on an old version
of macOS.
-------------------------------------------------------
Old Versions of macOS
Some old versions of macOS can be downloaded from Apple's support
page: https://support.apple.com/en-us/HT211683
macOS does allow dual booting of multiple versions of the OS, but
it's safer and easier to install the old macOS onto a flash drive.
Wherever you're installing it, the target drive's partitioniong
scheme and partition type must match what the old macOS expects, so
use the Disk Utility to partition and format the flash drive
accordingly.
As of this writing, the oldest version of macOS available on Apple's
support site is Yosemite 10.10, which expects "GPT (GUID Partition
Table)" partitioning scheme instead of the older MBR scheme, and
"Mac OS Extended (Journaled)" as the partition type instead of the
newer APFS partition type.
Upon launching the installer, if you get a popup about macOS being
too old or new to be installed, a bootable installer can be created
using the instructions found here:
https://support.apple.com/en-mide/HT201372
It has been found that macOS can be installed onto the bootable
media itself, so you can make the flash drive into a bootable
installer then install the old macOS onto the same flash drive.
Once the old macOS is installed, you may find the Xcode on the App
Store is too new to run on the version of the old macOS. Old
versions of Xcode can be downloaded from Apple's Developer site in
an area accessible with free registration:
https://developer.apple.com/download/more/
The list of macOS versions and the last version of Xcode compatible
with them are laid out nicely on the Wikipedia page on Xcode:
https://en.wikipedia.org/wiki/Xcode#Version_comparison_table
And because Xcode is being installed manually, you can skip the step
to install the Xcode command line tools (do not run "xcode-select
--install") but otherwise build Tux Paint using the same steps
described in the earlier part of this document.
----------------------------------------------------------------------
Debugging
Debugging output — to "STDOUT" on Linux and Unix, to a "stdout.txt" file
on Windows, and to the file "/tmp/tuxpaint.log" on macOS — can be
enabled by setting "DEBUG" (and, if verbose logging is wanted,
"VERBOSE") #defines in "src/debug.h" and (re)compiling Tux Paint.
----------------------------------------------------------------------
Uninstalling Tux Paint
Windows
@ -376,6 +760,18 @@ Uninstalling Tux Paint:
It is also possible to use the entry "TuxPaint (remove only)" in the
Control Panel Add/Remove programs section.
----------------------------------------------------------------------
macOS
Delete "TuxPaint.app" from the "Applications" folder. Data files,
including the configuration files, stamps, and saved pictures, may be
found in "Library/Application Support/TuxPaint" (all users) and
"/Users/USERNAME/Library/Application Support/TuxPaint" (individual
users).
----------------------------------------------------------------------
Linux
Within the Tux Paint source directory (where you compiled Tux Paint),

1929
docs/es_ES.UTF-8/OPTIONS.txt
View file

File diff suppressed because it is too large Load diff

2
docs/es_ES.UTF-8/PNG.txt
View file

@ -1,5 +1,5 @@
Tux Paint
versión 0.9.26
versión 0.9.27
PNG Documentation
Copyright © 2007-2021 by various contributors; see AUTHORS.

26
docs/es_ES.UTF-8/README.txt
View file

@ -1,12 +1,12 @@
Tux Paint
versión 0.9.26
versión 0.9.27
A simple drawing program for children
Copyright © 2002-2021 by various contributors; see AUTHORS.
http://www.tuxpaint.org/
junio 28, 2021
septiembre 5, 2021
----------------------------------------------------------------------
@ -219,6 +219,22 @@ Available Tools
If you hold the mouse button down, and move the mouse, it
will draw as you move.
Some brushes are animated — they change their shape as you
draw them. A good example of this is the vines brush that
ships with Tux Paint. These brushes will have a small
"filmstrip" icon drawn on their Selector buttons.
Other brushes are directional — they will draw a different
shape depending on what direction you are painting with
them. An example of this is the arrow brush that ships with
Tux Paint. These brushes have a small 8-way arrow icon drawn
on their Selector buttons.
Finally, some brushes can be both direction and animated.
Examples of this are the cat and squirrel brushes that ship
with Tux Paint. These brushes will have both the "filmstrip"
and 8-way arrow icons.
As you draw, a sound is played. The bigger the brush, the
lower the pitch.
@ -278,6 +294,12 @@ Available Tools
Let go of the mouse to complete the line. A "sproing!" sound
will play.
Some brushes are animated, and will show a pattern of shapes
along the line. Others are directional, and will show a
different shape depending on the angle of the brush. And
finally some are both animated and directional. See "Paint",
above, to learn more.
----------------------------------------------------------------------
"Shapes" Tool

2
docs/es_ES.UTF-8/SIGNALS.txt
View file

@ -1,5 +1,5 @@
Tux Paint
versión 0.9.26
versión 0.9.27
Signals Documentation
Copyright © 2019-2021 by various contributors; see AUTHORS.

2
docs/es_ES.UTF-8/SVG.txt
View file

@ -1,5 +1,5 @@
Tux Paint
versión 0.9.26
versión 0.9.27
SVG Documentation
Copyright © 2007-2021 by various contributors; see AUTHORS.

81
docs/es_ES.UTF-8/html/ADVANCED-STAMPS-HOWTO.html
View file

@ -17,16 +17,62 @@
width="205"
height="210"
alt="Tux Paint"><br>
versi&oacute;n 0.9.26 Advanced Stamps 'How-To' </h1>
versi&oacute;n 0.9.27 Advanced Stamps 'How-To' </h1>
<p>
Copyright &copy; 2006-2021 by Albert Cahalan and others; see AUTHORS.<br>
<a href="http://www.tuxpaint.org/">http://www.tuxpaint.org/</a>
</p>
<p>
agosto 29, 2021 </p>
</center>
<hr size="2"
noshade>
<table border="2"
cellspacing="0"
cellpadding="2"
summary="Table of Contents">
<tr>
<th>
Table of Contents </th>
</tr>
<tr>
<td>
<ul>
<li>
<a href="#about">About this 'How-To'</a>
</li>
<li>
<a href="#choice">Image choice is crucial</a>
</li>
<li>
<a href="#prepare_mask">Prepare the mask</a>
</li>
<li>
<a href="#replace_fringe">Replace the fringe and junk pixels</a>
</li>
<li>
<a href="#save">Save the image for Tux Paint</a>
</li>
</ul>
</td>
</tr>
</table>
<hr size="2"
noshade>
<hr size="2"
noshade>
<h2>
About this 'How-To' </h2>
<a name="about" id="about">
About this 'How-To' </a>
</h2>
<blockquote>
<p>
@ -36,8 +82,13 @@
This 'How-To' assumes you are dealing with normal opaque objects. Dealing with semi-transparent objects (fire, moving fan blade, kid's balloon) or light-giving objects (fire, lightbulb, sun) is best done with custom software. Images with perfect solid-color backgrounds are also best done with custom software, but are not troublesome to do as follows. </p>
</blockquote>
<hr size="2"
noshade>
<h2>
Image choice is crucial </h2>
<a name="choice" id="choice">
Image choice is crucial </a>
</h2>
<blockquote>
<h3>
@ -78,6 +129,9 @@
</blockquote>
</blockquote>
<hr size="2"
noshade>
<h2>
Prepare the image </h2>
@ -116,8 +170,13 @@
<b>Warning:</b> once you have the mask, you may not rotate or scale the image normally. This would cause data loss. You will be given special scaling instructions later. </p>
</blockquote>
<hr size="2"
noshade>
<h2>
Prepare the mask </h2>
<a name="prepare_mask" id="prepare_mask">
Prepare the mask </a>
</h2>
<blockquote>
<p>
@ -151,8 +210,13 @@
View and edit the mask. Select by color, choosing either black or white. Most likely you will see unselected specks that are not quite the expected color. Invert the selection, then paint these away using the pencil tool. Do this operation for both white and black. </p>
</blockquote>
<hr size="2"
noshade>
<h2>
Replace the fringe and junk pixels </h2>
<a name="replace_fringe" id="replace_fringe">
Replace the fringe and junk pixels </a>
</h2>
<blockquote>
<p>
@ -188,8 +252,13 @@
Tux Paint can scale images down by a very large factor, so it is important to extend the edge of your object outward by a great deal. Right at the edge of your object, you should be very accurate about this. As you go outward away from the object, you can get a bit sloppy. It is reasonable to paint outward by a dozen pixels or more. The farther you go, the more Tux Paint can scale down without creating ugly color fringes. For areas that are more than a few pixels away from the object edge, you should use the pencil tool (or sloppy select with drag-and-drop color) to ensure that the result will compress well. </p>
</blockquote>
<hr size="2"
noshade>
<h2>
Save the image for Tux Paint </h2>
<a name="save" id="save">
Save the image for Tux Paint </a>
</h2>
<blockquote>
<p>

4
docs/es_ES.UTF-8/html/ENVVARS.html
View file

@ -17,7 +17,7 @@
width="205"
height="210"
alt="Tux Paint"><br>
versi&oacute;n 0.9.26<br/>
versi&oacute;n 0.9.27<br/>
Environment Variables Documentation </h1>
<p>
@ -26,7 +26,7 @@
</p>
<p>
mayo 11, 2021 </p>
agosto 8, 2021 </p>
</center>
<hr>

21
docs/es_ES.UTF-8/html/EXTENDING.html
View file

@ -18,7 +18,7 @@
width="205"
height="210"
alt="Tux Paint"><br>
versi&oacute;n 0.9.26 </h1>
versi&oacute;n 0.9.27 </h1>
<p>
Copyright &copy; 2002-2021 by various contributors; see AUTHORS.<br>
@ -26,7 +26,7 @@
</p>
<p>
mayo 31, 2021 </p>
septiembre 6, 2021 </p>
</center>
<hr size="2"
@ -367,14 +367,25 @@
</blockquote>
<h4>
Animated Directional Brushes </h4>
Rotating Brushes </h4>
<blockquote>
<p>
You may mix both animated and directional features into one brush. Use both options ("<code><b>frames=<i>N</i></b></code>" and "<code><b>directional</b></code>"), in separate lines in the brush's "<code>.dat</code>" file. </p>
As of Tux Paint version 0.9.27, you may now create rotating brushes. As the brush is used, it is rotated 360 degrees, depending on the direction the brush is going. </p>
<p>
Lay the brush out so that each 3x3 set of directional shapes are laid out across a wide PNG image. For example, if the brush is 30x30 and there are 5 frames, it would be 450x90. (The leftmost 150x90 pixels of the image represent the 9 direction shapes for the first frame, for example.) </p>
Add a line containing the word "<code><b>rotate</b></code>" to the brush's data file. </p>
</blockquote>
<h4>
Animated Directional or Rotating Brushes </h4>
<blockquote>
<p>
You may mix both animated and either directional or rotating features into one brush. Use both options desired ("<code><b>frames=<i>N</i></b></code>" and "<code><b>directional</b></code>" or "<code><b>rotate</b></code>"), in separate lines in the brush's "<code>.dat</code>" file. </p>
<p>
For directional brushes, lay the brush out so that each 3x3 set of directional shapes are laid out across a wide PNG image. For example, if the brush is 30x30 and there are 5 frames, it would be 450x90. (The leftmost 150x90 pixels of the image represent the 9 direction shapes for the first frame, for example.) </p>
</blockquote>
</blockquote>

104
docs/es_ES.UTF-8/html/FAQ.html
View file

@ -17,7 +17,7 @@
width="205"
height="210"
alt="Tux Paint"><br>
versi&oacute;n 0.9.26 Frequently Asked Questions </h1>
versi&oacute;n 0.9.27 Frequently Asked Questions </h1>
<p>
Copyright &copy; 2002-2021 by various contributors; see AUTHORS.<br>
@ -25,13 +25,60 @@
</p>
<p>
junio 2, 2021 </p>
agosto 29, 2021 </p>
</center>
<hr>
<hr size="2"
noshade>
<table border="2"
cellspacing="0"
cellpadding="2"
summary="Table of Contents">
<tr>
<th>
Table of Contents </th>
</tr>
<tr>
<td>
<ul>
<li>
<a href="#drawing">Drawing-related</a>
</li>
<li>
<a href="#interface">Interface Problems</a>
</li>
<li>
<a href="#printing">Printing</a>
</li>
<li>
<a href="#saving">Saving</a>
</li>
<li>
<a href="#audio">Audio Problems</a>
</li>
<li>
<a href="#fullscreen">Fullscreen Mode Problems</a>
</li>
<li>
<a href="#other">Other Probelms</a>
</li>
<li>
<a href="#contact">Help / Contact</a>
</li>
</ul>
</td>
</tr>
</table>
<hr size="2"
noshade>
<h2>
Drawing-related </h2>
<a name="drawing" id="drawing">
Drawing-related </a>
</h2>
<dl>
<dt>
@ -101,10 +148,13 @@
</dd>
</dl>
<hr>
<hr size="2"
noshade>
<h2>
Interface Problems </h2>
<a name="interface" id="interface">
Interface Problems </a>
</h2>
<dl>
<dt>
@ -212,10 +262,13 @@
</dd>
</dl>
<hr>
<hr size="2"
noshade>
<h2>
Printing </h2>
<a name="printing" id="printing">
Printing </a>
</h2>
<dl>
<dt>
@ -282,10 +335,13 @@
</dd>
</dl>
<hr>
<hr size="2"
noshade>
<h2>
Saving </h2>
<a name="saving" id="saving">
Saving </a>
</h2>
<dl>
<dt>
@ -382,10 +438,13 @@
</dd>
</dl>
<hr>
<hr size="2"
noshade>
<h2>
Audio Problems </h2>
<a name="audio" id="audio">
Audio Problems </a>
</h2>
<dl>
<dt>
@ -507,10 +566,13 @@
</dd>
</dl>
<hr>
<hr size="2"
noshade>
<h2>
Fullscreen Mode Problems </h2>
<a name="fullscreen" id="fullscreen">
Fullscreen Mode Problems </a>
</h2>
<dl>
<dt>
@ -569,10 +631,13 @@
</dd>
</dl>
<hr>
<hr size="2"
noshade>
<h2>
Other Probelms </h2>
<a name="other" id="other">
Other Probelms </a>
</h2>
<dl>
<dt>
@ -744,10 +809,13 @@
</dd>
</dl>
<hr>
<hr size="2"
noshade>
<h2>
Help / Contact </h2>
<a name="contact" id="contact">
Help / Contact </a>
</h2>
<p>
Any questions you don't see answered? Please let us know! You can subscribe and post to our "tuxpaint-users" mailing list: </p>

625
docs/es_ES.UTF-8/html/INSTALL.html
View file

@ -17,7 +17,7 @@
width="205"
height="210"
alt="Tux Paint"><br>
versi&oacute;n 0.9.26<br/>
versi&oacute;n 0.9.27<br/>
Installation Documentation </h1>
<p>
@ -26,21 +26,88 @@
</p>
<p>
marzo 9, 2021 </p>
septiembre 5, 2021 </p>
</center>
<hr>
<hr size="2" noshade />
<h2>Requirements:</h2>
<table border="2"
cellspacing="0"
cellpadding="2"
summary="Table of Contents">
<tr>
<th>
Table of Contents </th>
</tr>
<tr>
<td>
<ul>
<li>
<a href="#requirements">Requirements</a>
<ul>
<li>
<a href="#req-libsdl">Simple DirectMedia Layer library (libSDL)</a>
</li>
<li>
<a href="#req-other-libs">Other Libraries</a>
</li>
</ul>
</li>
<li>
<a href="#compiling">Compiling and Installation</a>
<ul>
<li>
<a href="#compiling-windows">Windows Users</a>
</li>
<li>
<a href="#compiling-linux">Linux/Unix Users</a>
</li>
<li>
<a href="#compiling-macos">macOS Users</a>
</li>
</ul>
</li>
<li>
<a href="#debugging">Debugging</a>
</li>
<li>
<a href="#uninstalling">Uninstalling Tux Paint</a>
<ul>
<li>
<a href="#uninstalling-windows">Windows</a>
</li>
<li>
<a href="#uninstalling-macOS">macOS</a>
</li>
<li>
<a href="#uninstalling-linux">Linux</a>
</li>
</ul>
</li>
</ul>
</td>
</tr>
</table>
<hr size="2" noshade />
<h2>
<a name="requirements" id="requirements">
Requirements </a>
</h2>
<blockquote>
<h3>libSDL</h3>
<h3>
<a name="req-libsdl" id="req-libsdl">
Simple DirectMedia Layer library (libSDL) </a>
</h3>
<blockquote>
<p>
Tux Paint requires the Simple DirectMedia Layer Library (libSDL), an Open Source multimedia programming library available under the GNU Lesser General Public License (LGPL). </p>
<p>
Along with libSDL, Tux Paint depends on a number of other SDL 'helper' libraries: SDL_Image (for graphics files), SDL_TTF and (optionally) SDL_Pango (for True Type Font support) and, optionally, SDL_Mixer (for sound effects). </p>
Along with libSDL, Tux Paint depends on a number of other SDL 'helper' libraries: SDL_Image (for graphics files), SDL_gfx (for some graphical functions, like rotation), SDL_TTF and (optionally) SDL_Pango (for True Type Font support) and, optionally, SDL_Mixer (for sound effects). </p>
<h4>Linux/Unix Users:</h4>
<blockquote>
@ -49,6 +116,7 @@
<ul>
<li>libSDL: <a href="http://www.libsdl.org/">http://www.libsdl.org/</a></li>
<li>SDL_Image: <a href="http://www.libsdl.org/projects/SDL_image/">http://www.libsdl.org/projects/SDL_image/</a></li>
<li>SDL_gfx: <a href="https://www.ferzkopp.net/wordpress/2016/01/02/sdl_gfx-sdl2_gfx/">https://www.ferzkopp.net/wordpress/2016/01/02/sdl_gfx-sdl2_gfx/</a> (<a href="https://sourceforge.net/projects/sdlgfx/">https://sourceforge.net/projects/sdlgfx/</a>)</li>
<li>SDL_TTF: <a href="http://www.libsdl.org/projects/SDL_ttf/">http://www.libsdl.org/projects/SDL_ttf/</a></li>
<li>SDL_Pango: <a href="http://sourceforge.net/projects/sdlpango/">http://sourceforge.net/projects/sdlpango/</a> (optional)</li>
<li>SDL_Mixer: <a href="http://www.libsdl.org/projects/SDL_mixer/">http://www.libsdl.org/projects/SDL_mixer/</a> (optional)</li>
@ -62,7 +130,10 @@
</blockquote>
</blockquote>
<h3>Other Libraries</h3>
<h3>
<a name="req-other-libs" id="req-other-libs">
Other Libraries </a>
</h3>
<blockquote>
<p>
Tux Paint also takes advantage of a number of other free, LGPL'd libraries. Under Linux, just like SDL, they should either already be installed, or are readily available for installation as part of your Linux distribution. </p>
@ -110,7 +181,7 @@
<h4>SVG graphics support</h4>
<blockquote>
<p>
As of Tux Paint 0.9.17, Tux Paint can load SVG (Scalable Vector Graphics) images as stamps. Two sets of libraries are supported, and SVG support can be completely disabled (via "<code>make SVG_LIB:=</code>") </p>
As of Tux Paint 0.9.17, Tux Paint can load SVG (Scalable Vector Graphics) images as stamps. Two sets of libraries are supported, and SVG support can be completely disabled (via "<code style="white-space: nowrap;">make SVG_LIB:=</code>") </p>
<h5>librsvg-2 &amp; libCairo2 (newer libraries)</h5>
<ul>
@ -155,66 +226,322 @@
</blockquote>
</blockquote>
<h2>Compiling and Installation:</h2>
<hr size="2" noshade />
<h2>
<a name="compiling" id="compiling">
Compiling and Installation </a>
</h2>
<blockquote>
<p>
Tux Paint is released under the GNU General Public License (GPL) (see "COPYING.txt" for details), and therefore the 'source code' to the program is available freely. </p>
<h3>Windows Users:</h3>
<h3>
<a name="compiling-windows" id="compiling-windows">
Windows Users </a>
</h3>
<p style="font-size: small;">
<em>
octubre 25, 2020 Shin-ichi TOYAMA shin1@wmail.plala.or.jp &lt;<a href="mailto:shin1@wmail.plala.or.jp">shin1@wmail.plala.or.jp</a>&gt;
</em>
</p>
<blockquote>
<h4>Compiling:</h4>
<h4>Compiling Set-Up</h4>
<blockquote>
<p>
As of February 2005 (starting with Tux Paint 0.9.15), the "<code>Makefile</code>" includes support for building on a Windows system using MinGW/MSYS (<a href="http://www.mingw.org/">http://www.mingw.org/</a>). </p>
As of February 2005 (starting with Tux Paint 0.9.15), the "<code>Makefile</code>" includes support for building on a Windows system using MinGW/MSYS (<a href="https://sourceforge.net/projects/msys2/">https://sourceforge.net/projects/msys2/</a>). </p>
<p>
After configuring the environment and building and installing all the dependencies, use these commands, in MSYS, to build, install and run: </p>
<h5>Prior to version 0.9.20:</h5>
<blockquote>
<code>
$ make win32<br/>
$ make install-win32<br/>
$ tuxpaint
</code>
</blockquote>
<h5>Version 0.9.20 and beyond:</h5>
<blockquote>
<code>
$ make<br/>
$ make install<br/>
$ tuxpaint
</code>
</blockquote>
Many tools and libraries are required to build Tux Paint. The package management system "<code>pacman</code>" helps you install them automatically solving complicated dependencies. </p>
<p>
Use the following command to build a version suitable for redistribution with the installer or in a zip-file: </p>
<blockquote>
<code>
$ make bdist-win32
</code>
</blockquote>
Download the latest MSYS2 environment from <a href="https://sourceforge.net/projects/msys2/files/Base/">https://sourceforge.net/projects/msys2/files/Base/</a> and install it where you'd like (the default is "<code>C:\msys64</code>") </p>
<p>
Or if building for Win9x/ME: </p>
<blockquote>
<code>
$ BDIST_WIN9X=1 make bdist-win32
</code>
</blockquote>
<p>
Before any of the above will work, you need to configure the environment and build or install the libraries that Tux Paint depends upon. John Popplewell put together some instructions for doing that here: </p>
<p>
<a href="http://www.johnnypops.co.uk/tuxpaint/">http://www.johnnypops.co.uk/tuxpaint/</a>
Open the MSYS2 shell from the "Start Menu" -&gt; "MSYS2 64bit" -&gt; "MSYS2 MSYS" and execute following command (press <b><code>[Enter]</code></b> or <b><code>[Return]</code></b> to accept the defaults for all questions):
<blockquote>
<code>
pacman -Syu
</code>
</blockquote>
</p>
<p>
Read the relevant notes if building for Win9X/ME. </p>
This will update core system and the window will close automatically. Repeat the steps above one more time to finish the remaining update process. </p>
<p>
Within the MSYS2 shell, run the following command to install basic development tools: <blockquote>
<code>
pacman -S base-devel msys2-devel git
</code>
</blockquote>
</p>
</blockquote>
<h4>Running the Installer:</h4>
<p>
<i>
Proceed to the next "<a href="#64bit">MinGW 64bit (x86_64) toolchains</a>" section, or skip to the "<a href="#32bit">MinGW 32bit (i686) toolchains</a>" section if you need only a 32bit build environment. </i>
</p>
<hr size="1" noshade width="75%" />
<h4>
<a name="64bit" id="64bit">
MinGW 64bit (x86_64) toolchains </a>
</h4>
<blockquote>
<p>
Within the MSYS2 shell, run the following command to install basic 64bit development tools: <blockquote>
<code>
pacman -S mingw-w64-x86_64-toolchain
</code>
</blockquote>
</p>
</blockquote>
<h4>
64bit (x86_64) dependency libraries for Tux Paint </h4>
<blockquote>
<p>
You can install tools and libraries required for compiling Tux Paint on MSYS2/MINGW using "<code>pacman</code>" except for SDL_Pango. </p>
<p>
"<code>ntldd</code>" is a small tool which examine windows executable files to list Dynamic Link Library (<code>.dll</code>) files they depends on. Tux Paint's packaging process for binary distribution uses it to find required <code>.dll</code> files. </p>
<p>
FLTK is a cross-platform GUI toolkit used by "Tux Paint Config.". You can skip installing it if you are <em>only</em> building "Tux Paint". </p>
<p>
<blockquote>
<code>
$ pacman -S mingw-w64-x86_64-SDL_{image,mixer,ttf}<br/>
$ pacman -S mingw-w64-x86_64-librsvg<br/>
$ pacman -S mingw-w64-x86_64-fribidi<br/>
$ pacman -S mingw-w64-x86_64-libimagequant<br/>
$ pacman -S mingw-w64-x86_64-fltk<br/>
$ pacman -S mingw64/mingw-w64-x86_64-ntldd-git
</code>
</blockquote>
</p>
<p>
<strong>Note:</strong> Close the shell before proceeding to the remaining process. </p>
</blockquote>
<h4>
Install SDL_Pango and re-install SDL on the 64bit environment </h4>
<blockquote>
<p>
SDL_Pango should be installed manually. In addition, you have to re-install SDL from the source code or you will see unnecessary blank window opens when starting Tux Paint. </p>
<p>
This time, use the MinGW "64bit" shell. Open the shell from the "Start Menu" -&gt; "MSYS2 64bit" -&gt; "MSYS2 MinGW 64-bit" </p>
<h5>SDL_Pango</h5>
<blockquote>
<p>
At first, you have to prepare source tar-ball and a required patch in the same directory. </p>
<ul>
<li>
Download <a href="https://sourceforge.net/projects/sdlpango/files/SDL_Pango/0.1.2/SDL_Pango-0.1.2.tar.gz/download">source tar-ball of SDL_Pango-0.1.2</a> from <a href="https://sourceforge.net/projects/sdlpango/">SDL_Pango's page on Sourceforge.net</a>. </li>
<li>
Download <a href="http://johnnypops.co.uk/tuxpaint/SDL_Pango-configure-extra-api.patch">a patch file</a> from <a href="http://www.johnnypops.co.uk/tuxpaint/">John Popplewell's "Tux Paint - MinGW/MSYS build instructions" webpage</a>. (This adds some extra (required) functionality to SDL_Pango.) </li>
</ul>
<p>
Build and install SDL_Pango as follows. <blockquote>
<code>
$ tar zxvf SDL_Pango-0.1.2.tar.gz<br/>
$ cd SDL_Pango-0.1.2/<br/>
$ patch -p0 &lt; ../SDL_Pango-configure-extra-api.patch<br/>
$ ./configure --prefix=/mingw64 &amp;&amp; make &amp;&amp; make install
</code>
</blockquote>
</p>
</blockquote>
<h5>SDL</h5>
<blockquote>
<p>
Download <a href="http://www.libsdl.org/release/SDL-1.2.15.tar.gz">source tar-ball of SDL_1.2.15</a> from <a href="http://www.libsdl.org/">libsdl.org</a>. </p>
<p>
Re-install SDL as follows. <blockquote>
<code>
$ tar zxvf SDL-1.2.15.tar.gz<br/>
$ cd SDL-1.2.15<br/>
$ ./configure --prefix=/mingw64 &amp;&amp; make &amp;&amp; make install
</code>
</blockquote>
</p>
</blockquote>
</blockquote>
<p>
<i>
Proceed to the next "<a href="#32bit">MinGW 32bit (i686) toolchains</a>" section, or skip to the "<a href="#imagemagick">ImageMagick</a>" section if you need only a 64bit build environment. </i>
</p>
<hr size="1" noshade width="75%" />
<h4>
<a name="32bit" id="32bit">
MinGW 32bit (i686) toolchains </a>
</h4>
<blockquote>
<p>
Within the MSYS2 shell, run the following command to install basic 32bit development tools: <blockquote>
<code>
pacman -S mingw-w64-i686-toolchain
</code>
</blockquote>
</p>
</blockquote>
<h4>
32bit (i686) dependency libraries for Tux Paint </h4>
<blockquote>
<p>
You can install tools and libraries required for compiling Tux Paint on MSYS2/MINGW using "<code>pacman</code>" except for SDL_Pango. </p>
<p>
"<code>ntldd</code>" is a small tool which examine windows executable files to list Dynamic Link Library (<code>.dll</code>) files they depends on. Tux Paint's packaging process for binary distribution uses it to find required <code>.dll</code> files. </p>
<p>
FLTK is a cross-platform GUI toolkit used by "Tux Paint Config.". You can skip installing it if you are <em>only</em> building "Tux Paint". </p>
<p>
<blockquote>
<code>
$ pacman -S mingw-w64-i686-SDL_{image,mixer,ttf}<br/>
$ pacman -S mingw-w64-i686-librsvg<br/>
$ pacman -S mingw-w64-i686-fribidi<br/>
$ pacman -S mingw-w64-i686-libimagequant<br/>
$ pacman -S mingw-w64-i686-fltk<br/>
$ pacman -S mingw-w64-i686-ntldd-git
</code>
</blockquote>
</p>
<p>
<strong>Note:</strong> Close the shell before proceeding to the remaining process. </p>
</blockquote>
<h4>
Install SDL_Pango and re-install SDL on the 32bit environment </h4>
<blockquote>
<p>
SDL_Pango should be installed manually. In addition, you have to re-install SDL from the source code or you will see unnecessary blank window opens when starting Tux Paint. </p>
<p>
This time, use the MinGW "32bit" shell. Open the shell from the "Start Menu" -&gt; "MSYS2 64bit" -&gt; "MSYS2 MinGW 32-bit" </p>
<h5>SDL_Pango</h5>
<blockquote>
<p>
At first, you have to prepare source tar-ball and a required patch in the same directory. </p>
<ul>
<li>
Download <a href="https://sourceforge.net/projects/sdlpango/files/SDL_Pango/0.1.2/SDL_Pango-0.1.2.tar.gz/download">source tar-ball of SDL_Pango-0.1.2</a> from <a href="https://sourceforge.net/projects/sdlpango/">SDL_Pango's page on Sourceforge.net</a>. </li>
<li>
Download <a href="http://johnnypops.co.uk/tuxpaint/SDL_Pango-configure-extra-api.patch">a patch file</a> from <a href="http://www.johnnypops.co.uk/tuxpaint/">John Popplewell's "Tux Paint - MinGW/MSYS build instructions" webpage</a>. (This adds some extra (required) functionality to SDL_Pango.) </li>
</ul>
<p>
Build and install SDL_Pango as follows. <blockquote>
<code>
$ tar zxvf SDL_Pango-0.1.2.tar.gz<br/>
$ cd SDL_Pango-0.1.2/<br/>
$ patch -p0 &lt; ../SDL_Pango-configure-extra-api.patch<br/>
$ ./configure --prefix=/mingw32 &amp;&amp; make &amp;&amp; make install
</code>
</blockquote>
</p>
</blockquote>
<h5>SDL</h5>
<blockquote>
<p>
Download <a href="http://www.libsdl.org/release/SDL-1.2.15.tar.gz">source tar-ball of SDL_1.2.15</a> from <a href="http://www.libsdl.org/">libsdl.org</a>. </p>
<p>
Re-install SDL as follows. <blockquote>
<code>
$ tar zxvf SDL-1.2.15.tar.gz<br/>
$ cd SDL-1.2.15<br/>
$ ./configure --prefix=/mingw32 &amp;&amp; make &amp;&amp; make install
</code>
</blockquote>
</p>
</blockquote>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>
<a name="imagemagick" id="imagemagick">ImageMagick</a>
</h4>
<blockquote>
<p>
<a href="https://imagemagick.org">ImageMagick</a> is a compilation of command line tools to create, edit, compose, or convert bitmap images supporting quite a large number of image formats. Tux Paint uses two functions ("convert" and "composite") in it to generate thumbnails for startar images and templates during the build process. </p>
<p>
Using official binary release available from "<a href="https://imagemagick.org/script/download.php#windowsand">Windows Binary Release</a>" is recommended, due to the commands installed with "<code>pacman</code>" on MinGW/MSYS not working as expected! </p>
<p>
Do not forget to enable "Install legacy utilities (e.g. convert)" while installing it, because Tux Paint's build process uses them. </p>
<p>
Add the path to the directory in which ImageMagick is installed at the top of your "PATH" environment variable. For example: <blockquote>
<code>
$ export PATH=/c/Program\ Files/ImageMagick-7.0.10-Q16-HDRI:$PATH
</code>
</blockquote>
</p>
<p>
You can make this permanent by adding the above to your the BASH shell configuration file, "<code>~/.bash_profile</code>". </p>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>Tux Paint</h4>
<blockquote>
<p>
You can compile 64bit binaries using MSYS2 64bit shell, and 32bit binaries using MSYS2 32bit shell, respectively. </p>
<ul>
<li>
Select "MSYS2 64bit" -&gt; "MSYS2 MinGW 64-bit" from the "Start Menu" to open the 64bit shell. </li>
<li>
Select "MSYS2 64bit" -&gt; "MSYS2 MinGW 32-bit" from the "Start Menu" to open the 32bit shell. </li>
</ul>
<p>
Compile Tux Paint with the following command: <blockquote>
<code>
$ make bdist-win32
</code>
</blockquote>
</p>
<p>
<strong>Note:</strong> At this point, you will want to build "Tux Paint Config." for Windows, so it can be included along with "Tux Paint", if you're making an official (or test) release. The build process will look for it in a directory named "<code>tuxpaint-config</code>" (with no version number, e.g., "<code>tuxpaint-config-X.Y.Z</code>"). See "Tux Paint Config."'s INSTALL.txt documentation for details. </p>
<p>
All the files needed for starting Tux Paint (and Tux Paint Config.) are collected in the directory for binary distribution "<code>bdist</code>" directory under "<code>win32</code>". You can start them by double-clicking their executable (<code>.exe</code>) files in the "<code>bdist</code>" directory. </p>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>Building the Tux Paint Windows Installer:</h4>
<blockquote>
<p>
<a href="https://jrsoftware.org/isinfo.php">Inno Setup</a> is used to build executable installer for Tux Paint. Therefore you have to install it in the first place. </p>
<p>
</p>
<p>
Then, you can easily build an executable installer by right-clicking on the "<code>tuxpaint.iss</code>" icon in the "<code>win32</code>" directory and selecting "Compile" on the list. It will run for a while, and eventually you will find a "<code>tuxpaint-<i>X.Y.Z</i>-win32-installer.exe</code>" file in the same directory. </p>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>Running the Tux Paint Windows Installer:</h4>
<blockquote>
<p>
Double-click the Tux Paint installer executable (.EXE file) and follow the instructions.
@ -231,6 +558,8 @@
At this point, you can click 'Install' to install Tux Paint! </p>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>Changing the Settings Using the Shortcut:</h4>
<blockquote>
<p>
@ -267,6 +596,8 @@
When you have finished, click "OK." </p>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>If Something Goes Wrong:</h4>
<blockquote>
<p>
@ -277,7 +608,12 @@
</blockquote>
</blockquote>
<h3>Linux/Unix Users:</h3>
<hr size="1" noshade />
<h3>
<a name="compiling-linux" id="compiling-linux">
Linux/Unix Users </a>
</h3>
<blockquote>
<h4>Compiling:</h4>
<blockquote>
@ -294,11 +630,13 @@
</blockquote>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>
Disabling SVG support (and hence Cairo, libSVG, and svg-cairo dependencies): </h4>
<blockquote>
<p>
To disable SVG support (e.g., if your system is not currently supported by the Cairo library or other SVG-related dependencies), you can run "<code>make</code>" with "<code>SVG_LIB= SVG_CFLAGS= NOSVGFLAG=NOSVG</code>" added:
To disable SVG support (e.g., if your system is not currently supported by the Cairo library or other SVG-related dependencies), you can run "<code>make</code>" with "<code style="white-space: nowrap;">SVG_LIB= SVG_CFLAGS= NOSVGFLAG=NOSVG</code>" added:
<blockquote>
<code>
$ make SVG_LIB= SVG_CFLAGS=
@ -306,6 +644,8 @@
</blockquote>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>
Disabling Pango support (and hence Pango, Cairo, etc. dependencies): </h4>
<blockquote>
@ -318,6 +658,8 @@
</blockquote>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>Disabling Sound at Compile-time:</h4>
<blockquote>
If you don't have a sound card, or would prefer to build the program with no sound support (and therefore without a the <code>SDL_mixer</code> dependency), you can run "<code>make</code>" with "<code>SDL_MIXER_LIB=</code>" added: </p>
@ -328,18 +670,24 @@
</blockquote>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>Other options:</h4>
<blockquote>
<p>
Various other options (e.g., installation paths) may be overridden; see them in "<code>Makefile</code>" for further details. </p>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>If you get errors:</h4>
<blockquote>
<p>
If you receive any errors during compile-time, make sure you have the appropriate libraries installed (see above). If using packaged versions of the libraries (e.g., RPMs under RedHat or DEBs under Debian), be sure to get the corresponding "<code>-dev</code>" or "<code>-devel</code>" packages as well, otherwise you won't be able to compile Tux Paint (and other programs) from source! </p>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>Installng:</h4>
<blockquote>
<p>
@ -422,15 +770,155 @@
</blockquote>
</blockquote>
</blockquote>
<hr size="1" noshade />
<h3>
<a name="compiling-macos" id="compiling-macos">
macOS Users </a>
</h3>
<p style="font-size: small;">
<em>
septiembre 21, 2021 Mark K. Kim &lt;<a href="mailto:markuskimius@gmail.com">markuskimius@gmail.com</a>&gt;
</em>
</p>
<blockquote>
<p>
Tux Paint 0.9.22 and earlier required building Tux Paint from the Xcode IDE. Starting with 0.9.23, however, Tux Paint for macOS is built as though it were a Linux application. </p>
<h4>Prerequisites</h4>
<blockquote>
<p>
Although Tux Paint is built without the Xcode IDE, Xcode itself is still required to build Tux Paint. <a href="https://developer.apple.com/xcode/ide/">Download it from the App Store</a>, and launch it once to accept its license agreements. You may also need to install the Xcode command line tools using the command: <blockquote>
<code>
xcode-select --install
</code>
</blockquote>
</p>
<p>
Building Tux Paint also requires various libraries. We install them from MacPorts where possible, source code otherwise. Install MacPorts to the default <code>/opt/local</code> path according to the instructions found on their website: <a href="https://www.macports.org/">https://www.macports.org/</a> <ul>
<li><code>ImageMagick</code></li>
<li><code>cairo</code></li>
<li><code>fribidi</code></li>
<li><code>lbzip2</code></li>
<li><code>libimagequant</code><sup>*</sup></li>
<li><code>libpaper</code></li>
<li><code>libpng</code></li>
<li><code>librsvg</code></li>
<li><code>libsdl</code></li>
<li><code>libsdl_image</code></li>
<li><code>libsdl_mixer</code></li>
<li><code>libsdl_pango</code></li>
<li><code>libsdl_ttf</code></li>
<li><code>pkgconfig</code></li>
<li><code>zlib</code></li>
</ul>
... but you should install any package that is required by the latest version of Tux Paint.<br/>
<br/>
<sup>*</sup> Not available from MacPorts as of this writing, see below. </p>
<h5>libimagequant</h5>
<blockquote>
<p>
<code>libimagequant</code> is not available from MacPorts as of this writing. It can be installed from the source code as follows. It should be installed to <code>/opt/local</code> (same as MacPorts) for the library to be included in <code>TuxPaint.dmg</code>. <blockquote>
<code>
$ git clone https://github.com/ImageOptim/libimagequant.git<br/>
$ cd libimagequant<br/>
$ ./configure --prefix=/opt/local<br/>
$ make<br/>
$ sudo make install
</code>
</blockquote>
</p>
</blockquote>
<p>
<strong>WARNING:</strong> Having any UNIX-like toolset installed on your Mac besides MacPorts and Xcode, such as Fink or Brew, will prevent your app bundle from being portable. Be sure Fink and Brew are not accessible from your build environment. </p>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>How to Build</h4>
<blockquote>
<p>
Simply, run: <blockquote>
<code>
% make<br/>
% make install
</code>
</blockquote>
... to create the <code>TuxPaint.app</code> application bundle that can be run in-place or copied to <code>/Applications</code>. It also creates <code>TuxPaint.dmg</code> for distribution. </p>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>Known Issues</h4>
<blockquote>
<ul>
<li>
A macOS binary built on a specific version of macOS only runs on that version of macOS or later. To ensure Tux Paint can run on the oldest version of macOS possible, build it on the oldest version of macOS available. As of this writing we know Tux Paint cannot be built to run on macOS 10.7 or earlier.<br/>
<br/>
See "Old Versions of macOS" below for best-effort instructions on how to obtain, install, and build Tux Paint on an old version of macOS. </li>
</ul>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>Old Versions of macOS</h4>
<blockquote>
<p>
Some old versions of macOS can be downloaded from Apple's support page: <a href="https://support.apple.com/en-us/HT211683">https://support.apple.com/en-us/HT211683</a> </p>
<p>
macOS does allow dual booting of multiple versions of the OS, but it's safer and easier to install the old macOS onto a flash drive. Wherever you're installing it, the target drive's partitioniong scheme and partition type must match what the old macOS expects, so use the Disk Utility to partition and format the flash drive accordingly. </p>
<p>
As of this writing, the oldest version of macOS available on Apple's support site is Yosemite 10.10, which expects "GPT (GUID Partition Table)" partitioning scheme instead of the older MBR scheme, and "Mac OS Extended (Journaled)" as the partition type instead of the newer APFS partition type. </p>
<p>
Upon launching the installer, if you get a popup about macOS being too old or new to be installed, a bootable installer can be created using the instructions found here: <a href="https://support.apple.com/en-mide/HT201372">https://support.apple.com/en-mide/HT201372</a> </p>
<p>
It has been found that macOS can be installed onto the bootable media itself, so you can make the flash drive into a bootable installer then install the old macOS onto the same flash drive. </p>
<p>
Once the old macOS is installed, you may find the Xcode on the App Store is too new to run on the version of the old macOS. Old versions of Xcode can be downloaded from Apple's Developer site in an area accessible with free registration: <a href="https://developer.apple.com/download/more/">https://developer.apple.com/download/more/</a> </p>
<p>
The list of macOS versions and the last version of Xcode compatible with them are laid out nicely on the Wikipedia page on Xcode: <a href="https://en.wikipedia.org/wiki/Xcode#Version_comparison_table">https://en.wikipedia.org/wiki/Xcode#Version_comparison_table</a> </p>
<p>
And because Xcode is being installed manually, you can skip the step to install the Xcode command line tools (do not run "<code style="white-space: nowrap;">xcode-select --install</code>") but otherwise build Tux Paint using the same steps described in the earlier part of this document. </p>
</blockquote>
</blockquote>
</blockquote>
<h2>Debugging:</h2>
<blockquote>
Debugging (to "STDOUT", e.g. to the terminal, or to a "<code>stdout.txt</code>" file, on Windows) can be enabled by setting "<code>DEBUG</code>" (and, if verbose logging is wanted, "<code>VERBOSE</code>") <code>#define</code>s in "<code>src/debug.h</code>". </blockquote>
<hr size="2" noshade />
<h2>Uninstalling Tux Paint:</h2>
<h2>
<a name="debugging" id="debugging">
Debugging </a>
</h2>
<blockquote>
<h3>Windows</h3>
Debugging output &mdash; to "STDOUT" on Linux and Unix, to a "<code>stdout.txt</code>" file on Windows, and to the file "<code>/tmp/tuxpaint.log</code>" on macOS &mdash; can be enabled by setting "<code>DEBUG</code>" (and, if verbose logging is wanted, "<code>VERBOSE</code>") <code>#define</code>s in "<code>src/debug.h</code>" and (re)compiling Tux Paint. </blockquote>
<hr size="2" noshade />
<h2>
<a name="uninstalling" id="uninstalling">
Uninstalling Tux Paint </h2>
</h2>
<blockquote>
<h3>
<a name="uninstalling-windows" id="uninstalling-windows">
Windows </a>
</h3>
<blockquote>
<h4>Using the Uninstaller</h4>
<blockquote>
@ -448,10 +936,27 @@
</blockquote>
</blockquote>
<h3>Linux</h3>
<hr size="1" noshade />
<h3>
<a name="uninstalling-macos" id="uninstalling-macos">
macOS </a>
</h3>
<blockquote>
<p>
Within the Tux Paint source directory (where you compiled Tux Paint), you can use the "<code>make uninstall</code>" target to uninstall Tux Paint. By default, this must be done by the "root" user ('superuser'), but if you installed Tux Paint somewhere else (e.g., using a "<code>PREFIX=...</code>" setting to "<code>make</code>" and "<code>make install</code>"), you may not, and will want to provide those same settings here. (See the installation instructions above for further information.) </p>
Delete "<code>TuxPaint.app</code>" from the "Applications" folder. Data files, including the configuration files, stamps, and saved pictures, may be found in "<code style="white-space: nowrap;">Library/Application Support/TuxPaint</code>" (all users) and "<code style="white-space: nowrap;">/Users/<i>USERNAME</i>/Library/Application Support/TuxPaint</code>" (individual users). </p>
</blockquote>
<hr size="1" noshade />
<h3>
<a name="uninstalling-linux" id="uninstalling-linux">
Linux </a>
</h3>
<blockquote>
<p>
Within the Tux Paint source directory (where you compiled Tux Paint), you can use the "<code style="white-space: nowrap;">make uninstall</code>" target to uninstall Tux Paint. By default, this must be done by the "root" user ('superuser'), but if you installed Tux Paint somewhere else (e.g., using a "<code>PREFIX=...</code>" setting to "<code>make</code>" and "<code style="white-space: nowrap;">make install</code>"), you may not, and will want to provide those same settings here. (See the <a href="#compiling-linux">installation instructions above</a> for further information.) </p>
</blockquote>
<blockquote>
</body>

5373
docs/es_ES.UTF-8/html/OPTIONS.html
View file

File diff suppressed because it is too large Load diff

2
docs/es_ES.UTF-8/html/PNG.html
View file

@ -17,7 +17,7 @@
width="205"
height="210"
alt="Tux Paint"><br>
versi&oacute;n 0.9.26<br/>
versi&oacute;n 0.9.27<br/>
PNG Documentation </h1>
<p>

18
docs/es_ES.UTF-8/html/README.html
View file

@ -17,7 +17,7 @@
width="205"
height="210"
alt="Tux Paint"><br>
versi&oacute;n 0.9.26 </h1>
versi&oacute;n 0.9.27 </h1>
<h3>
A simple drawing program for children </h3>
@ -28,7 +28,7 @@
</p>
<p>
junio 28, 2021 </p>
septiembre 5, 2021 </p>
</center>
<hr size="2"
@ -408,6 +408,15 @@
<p>
If you hold the mouse button down, and move the mouse, it will draw as you move. </p>
<p>
Some brushes are animated &mdash; they change their shape as you draw them. A good example of this is the vines brush that ships with Tux Paint. These brushes will have a small "filmstrip" icon drawn on their Selector buttons. </p>
<p>
Other brushes are directional &mdash; they will draw a different shape depending on what direction you are painting with them. An example of this is the arrow brush that ships with Tux Paint. These brushes have a small 8-way arrow icon drawn on their Selector buttons. </p>
<p>
Finally, some brushes can be both direction <em>and</em> animated. Examples of this are the cat and squirrel brushes that ship with Tux Paint. These brushes will have both the "filmstrip" and 8-way arrow icons. </p>
<p>
As you draw, a sound is played. The bigger the brush, the lower the pitch. </p>
<br clear="all">
@ -503,6 +512,9 @@
<p>
Let go of the mouse to complete the line. A "sproing!" sound will play. </p>
<p>
Some brushes are animated, and will show a pattern of shapes along the line. Others are directional, and will show a different shape depending on the angle of the brush. And finally some are both animated and directional. See "Paint", above, to learn more. </p>
<br clear="all">
<p align="center">
@ -605,7 +617,7 @@
Choose a font (from the 'Letters' available on the right) and a color (from the color palette near the bottom). Click on the screen and a cursor will appear. Type text and it will show up on the screen. </p>
<p>
Press <strong><code>[Enter]</code></strong> or <strong><code>[Return]</code></strong> and the text will be drawn onto the picture and the cursor will move down one line. </p>
Press <b><code>[Enter]</code></b> or <b><code>[Return]</code></b> and the text will be drawn onto the picture and the cursor will move down one line. </p>
<p>
Alternatively, press <strong><code>[Tab]</code></strong> and the text will be drawn onto the picture, but the cursor will move to the right of the text, rather than down a line, and to the left. (This can be useful to create a line of text with mixed colors, fonts, styles and sizes.) </p>

2
docs/es_ES.UTF-8/html/SIGNALS.html
View file

@ -17,7 +17,7 @@
width="205"
height="210"
alt="Tux Paint"><br>
versi&oacute;n 0.9.26<br/>
versi&oacute;n 0.9.27<br/>
Signals Documentation </h1>
<p>

2
docs/es_ES.UTF-8/html/SVG.html
View file

@ -17,7 +17,7 @@
width="205"
height="210"
alt="Tux Paint"><br>
versi&oacute;n 0.9.26<br/>
versi&oacute;n 0.9.27<br/>
SVG Documentation </h1>
<p>

61
docs/fr_FR.UTF-8/ADVANCED-STAMPS-HOWTO.txt
View file

@ -1,9 +1,27 @@
Tux Paint
version 0.9.26 'Guide pratique" pour les tampons de haute qualité
version 0.9.27 'Guide pratique" pour les tampons de haute qualité
Copyright &copie; 2006-2021 par Albert Cahalan et d'autres; voir AUTHORS.
http://www.tuxpaint.org/
août 29, 2021
----------------------------------------------------------------------
+----------------------------------------------------+
|Table des matières |
|----------------------------------------------------|
| * À propos de ce 'guide pratique' |
| * Le choix de l'image est crucial |
| * Préparez le masque |
| * Remplacer la frange et les pixels indésirables |
| * Sauvegarder l'image pour Tux Paint |
+----------------------------------------------------+
----------------------------------------------------------------------
----------------------------------------------------------------------
À propos de ce 'guide pratique'
Ce 'guide pratique' suppose que vous vouliez créer un excellent tampon
@ -18,6 +36,8 @@
de parfaits arrière-plans de couleur unie sont mieux réalisées avec un
logiciel adapté, mais ne posent pas de problèmes avec ce qui suit.
----------------------------------------------------------------------
Le choix de l'image est crucial
Licence
@ -74,6 +94,8 @@ Le choix de l'image est crucial
camouflée, vous devriez pouvoir effectuer un copié-collé pour le
remplacement.
----------------------------------------------------------------------
Préparez l'image
Tout d'abord, ne re-sauvegardez pas une image au format JPEG. Cela
@ -116,6 +138,8 @@ Préparez l'image
de données. On vous donnera plus tard des instructions pour la mise à
l'échelle.
----------------------------------------------------------------------
Préparez le masque
Prenez l'habitude de faire un [Ctrl]-clic et un [Alt]-clic sur les
@ -180,6 +204,8 @@ Préparez le masque
sélection, et coloriez les avec l'outil crayon. Faites ces opérations
pour le blanc et le noir.
----------------------------------------------------------------------
Remplacer la frange et les pixels indésirables
Toujours en regardant le masque, sélectionnez par couleur. Choisissez le
@ -218,12 +244,11 @@ Remplacer la frange et les pixels indésirables
élargir un peu la sélection et / ou masquer la ligne "fourmis rampantes"
qui marque la sélection.
Utilisez l'outil de clonage et l'outil de pinceau. Faites varier
l'opacité selon vos besoins. Utilisez principalement des petites brosses
rondes, peut-être de 3x3 ou 5x5, floues ou non. (Il est généralement
agréable d'associer des pinceaux flous avec une opacité de 100 % et des
pinceaux non flous avec une opacité d'environ 70 %). On peut utiliser
des modes de dessin inhabituels avec des objets semi-transparents.
Use the clone tool and the brush tool. Vary the opacity as needed. Use
small round brushes mostly, perhaps 3x3 or 5x5, fuzzy or not. (It is
generally nice to pair up fuzzy brushes with 100% opacity and non-fuzzy
brushes with about 70% opacity.) Unusual drawing modes can be helpful
with semi-transparent objects.
Le but est de supprimer la frange de bord, à la fois à l'intérieur et à
l'extérieur de l'objet. La frange intérieure, visible lorsque l'objet
@ -250,19 +275,19 @@ Remplacer la frange et les pixels indésirables
l'outil Crayon (ou une vague sélection avec une couleur en
glisser-déposer) pour vous assurer que le résultat se compressera bien.
----------------------------------------------------------------------
Sauvegarder l'image pour Tux Paint
Il est très facile de gâcher votre travail, lui qui vous a demandé
beaucoup d'efforts. Les éditeurs d'images peuvent détruire
silencieusement les pixels dans les zones 0% opaques. Les conditions
dans lesquelles cela se produit peuvent varier d'une version à l'autre.
Si vous êtes très confiant, vous pouvez essayer d'enregistrer votre
image directement au format PNG. Assurez-vous de le relire pour vérifier
que les zones opaques à 0% ne deviennent ni noires ni blanches, ce qui
créerait des franges lorsque Tux Paint réduira l'image. Si vous devez
redimensionner votre image pour gagner de la place (et cacher vos
erreurs), vous êtes presque certain de détruire toutes les zones opaques
à 0%. Alors, voici une meilleure façon...
It is very easy to ruin your hard work. Image editors can silently
destroy pixels in 0% opaque areas. The conditions under which this
happens may vary from version to version. If you are very trusting, you
can try saving your image directly as a PNG. Be sure to read it back in
again to verify that the 0% opaque areas didn't turn black or white,
which would create fringes when Tux Paint scales the image down. If you
need to scale your image to save space (and hide your mistakes), you are
almost certain to destroy all the 0% opaque areas. So here is a better
way...
Une façon sûre pour sauvegarder

4
docs/fr_FR.UTF-8/ENVVARS.txt
View file

@ -1,11 +1,11 @@
Tux Paint
version 0.9.26
version 0.9.27
Documentation sur les variables d'environnement
Copyright &copie; 2021-2021 par divers contributeurs; voir AUTHORS.
http://www.tuxpaint.org/
mai 11, 2021
août 8, 2021
----------------------------------------------------------------------

70
docs/fr_FR.UTF-8/EXTENDING.txt
View file

@ -1,11 +1,11 @@
Extension
Tux Paint
version 0.9.26
version 0.9.27
Copyright &copie; 2002-2021 par divers contributeurs; voir AUTHORS.
http://www.tuxpaint.org/
mai 31, 2021
septembre 6, 2021
----------------------------------------------------------------------
@ -173,9 +173,9 @@ Pinceaux
Options de pinceau
Outre une a graphical shape, les brushes peuvent également recevoir
Outre une une forme graphique, les pinceaux peuvent également recevoir
d'autres attributs. Pour ce faire, vous devez créer un «fichier de
données» pour brush.
données» pour brosse.
Un fichier de données de brush's est simplement un fichier texte ASCII
contenant les options pour le brush.
@ -228,24 +228,34 @@ Pinceaux
...
Ajoute une ligne contenant le mot "directional" au fichier de
données brush's.
données brosse.
Pinceaux animés orientables
Rotating Brushes
Vous pouvez mélanger animation et orientation dans un même pinceau.
Utilisez les deux options ("frames=N" et "directional") en deux
lignes séparées dans le fichier ".dat" qui concerne le pinceau.
As of Tux Paint version 0.9.27, you may now create rotating brushes.
As the brush is used, it is rotated 360 degrees, depending on the
direction the brush is going.
Disposez le pinceau de manière à ce que chaque ensemble 3x3 de
formes orientables soit disposé sur une grande image PNG. Par
exemple, si le pinceau mesure 30x30 et qu'il y a 5 cadres, ce sera
450x90. (Les 150x90 pixels les plus à gauche de l'image représentent
les 9 formes de direction pour la première image, par exemple).
Ajoute une ligne contenant le mot "rotate" au fichier de données
brosse.
Animated Directional or Rotating Brushes
You may mix both animated and either directional or rotating
features into one brush. Use both options desired ("frames=N" and
"directional" or "rotate"), in separate lines in the brush's ".dat"
file.
For directional brushes, lay the brush out so that each 3x3 set of
directional shapes are laid out across a wide PNG image. For
example, if the brush is 30x30 and there are 5 frames, it would be
450x90. (The leftmost 150x90 pixels of the image represent the 9
direction shapes for the first frame, for example.)
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 brushes se présentent tous sous forme de
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.
@ -276,8 +286,8 @@ Tampons
permettre à l'utilisateur d'ajuster le tampon vers le haut (plus
grand) et vers le bas (plus petit).
Les SVG sont basés sur des vecteurs et seront mis à l'échelle de
manière adéquate pour le canevas utilisé.
SVGs are vector-based, and will be scaled appropriately for the canvas
size being used in Tux Paint.
Remarque: si vos nouveaux PNG-based stamps se présentent tous sous
forme de carrés ou de rectangles pleins, c'est que vous avez oublié
@ -399,15 +409,15 @@ Tampons
Options des tampons
Outre une a graphical shape, a textual description, a sound effect,
and a descriptive sound, les stamps peuvent également recevoir
d'autres attributs. Pour ce faire, vous devez créer un «fichier de
données» pour stamp.
Outre une une forme graphique, un texte de description, un effet
sonore et une description orale, les tampons peuvent également
recevoir d'autres attributs. Pour ce faire, vous devez créer un
«fichier de données» pour tampon.
Un fichier de données de stamp's est simplement un fichier texte ASCII
contenant les options pour le stamp.
Un fichier de données de tampon est simplement un fichier texte ASCII
contenant les options pour le tampon.
Le fichier porte le même nom que l'image PNG or SVG , mais une
Le fichier porte le même nom que l'image PNG ou SVG , mais une
extension ".dat". (par exemple, le fichier de données "stamp.png" est
le fichier texte "stamp.dat" qui se trouve dans le même répertoire.)
@ -427,7 +437,7 @@ Tampons
unie.
Ajoute une ligne contenant le mot "colorable" au fichier de
données stamp's.
données tampon.
Teinté
@ -437,7 +447,7 @@ Tampons
est modifiée en fonction de la couleur actuellement sélectionnée.)
Ajoute une ligne contenant le mot "tintable" au fichier de données
stamp's.
tampon.
Options de teinture :
@ -474,11 +484,11 @@ Tampons
Parfois, les tampons sont symétriques, il n'est donc pas utile de
laisser l'utilisateur les retourner ou les refléter.
Pour empêcher un tampon d'être from being flipped vertically,
Pour empêcher un tampon d'être qui a été inversé verticalement,
ajoutez une ligne contenant le mot «noflip» au fichier de données du
tampon.
Pour empêcher un tampon d'être from being mirrored horizontally,
Pour empêcher un tampon d'être qui a été inversé horizontalement,
ajoutez une ligne contenant le mot «nomirror» au fichier de données
du tampon.
@ -795,8 +805,8 @@ Méthodes alternatives de saisie
"src/im.c". Par exemple, "b" est utilisé en coréen pour gérer Batchim,
qui peut être reporté au caractère suivant.
Remarque : la prise en charge de nouveaux input methods nécessite des
ajouts au code source de Tux Paint ( "/src/im.c"), et nécessite des
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.

22
docs/fr_FR.UTF-8/FAQ.txt
View file

@ -1,10 +1,25 @@
Tux Paint
version 0.9.26 Questions fréquemment posées
version 0.9.27 Questions fréquemment posées
Copyright &copie; 2002-2021 par divers contributeurs; voir AUTHORS.
http://www.tuxpaint.org/
juin 2, 2021
août 29, 2021
----------------------------------------------------------------------
+-----------------------------------+
|Table des matières |
|-----------------------------------|
| * Liées au dessin |
| * Problèmes d'interface |
| * Impression |
| * Sauvegarde |
| * Problèmes audio |
| * Problèmes en mode plein écran |
| * Autres problèmes |
| * Aide / Contact |
+-----------------------------------+
----------------------------------------------------------------------
@ -333,7 +348,8 @@ Sauvegarde
Ou utilisez Tux Paint Config. et assurez-vous que "Demander avant
d'écraser" (sous "Sauvegarde") est vérifié.
Also, see "Tux Paint always saves over my old picture!", above.
Également voyez "Tux Paint sauvegarde en écrasant toujours mon
ancienne image !", ci-dessus.
----------------------------------------------------------------------

494
docs/fr_FR.UTF-8/INSTALL.txt
View file

@ -1,26 +1,46 @@
Tux Paint
version 0.9.26
version 0.9.27
Documentation sur l'installation
Copyright &copie; 2002-2021 par divers contributeurs; voir AUTHORS.
http://www.tuxpaint.org/
mars 9, 2021
septembre 5, 2021
----------------------------------------------------------------------
Exigences :
+--------------------------------------------------------+
|Table des matières |
|--------------------------------------------------------|
| * Exigences |
| * Biliothèque Simple DirectMedia Layer (libSDL) |
| * Autres bibliothèques |
| * Compilation et installation |
| * Utilisateurs de Windows |
| * Utilisateurs de Linux/Unix |
| * macOS Users |
| * Débogage |
| * Désinstallation de Tux Paint |
| * Windows |
| * macOS |
| * Linux |
+--------------------------------------------------------+
libSDL
----------------------------------------------------------------------
Exigences
Biliothèque Simple DirectMedia Layer (libSDL)
Tux Paint nécessite la bibliothèque de couches DirectMedia simple
(libSDL), une bibliothèque de programmation multimédia Open Source
disponible sous la Licence publique générale limitée GNU (LGPL).
Avec libSDL, Tux Paint dépend d'un certain nombre d'autres
bibliothèques SDL : SDL_Image (pour les fichiers graphiques), SDL_TTF
et (en option) SDL_Pango (pour la prise en charge des polices True
Type) et, éventuellement, SDL_Mixer (pour les effets sonores).
Along with libSDL, Tux Paint depends on a number of other SDL 'helper'
libraries: SDL_Image (for graphics files), SDL_gfx (for some graphical
functions, like rotation), SDL_TTF and (optionally) SDL_Pango (for
True Type Font support) and, optionally, SDL_Mixer (for sound
effects).
Utilisateurs de Linux/Unix :
@ -30,6 +50,9 @@ Exigences :
* libSDL: http://www.libsdl.org/
* SDL_Image: http://www.libsdl.org/projects/SDL_image/
* SDL_gfx:
https://www.ferzkopp.net/wordpress/2016/01/02/sdl_gfx-sdl2_gfx/
(https://sourceforge.net/projects/sdlgfx/)
* SDL_TTF: http://www.libsdl.org/projects/SDL_ttf/
* SDL_Pango: http://sourceforge.net/projects/sdlpango/ (optionnel)
* SDL_Mixer: http://www.libsdl.org/projects/SDL_mixer/ (optionnel)
@ -119,55 +142,272 @@ Exigences :
http://netpbm.sourceforge.net/
Compilation et installation :
----------------------------------------------------------------------
Compilation et installation
Tux Paint est publié sous la licence publique générale GNU (GPL) (voir
"COPYING.txt" pour plus de détails), et donc le 'code source' du
programme est disponible gratuitement.
Utilisateurs de Windows :
Utilisateurs de Windows
Compilation :
octobre 25, 2020 Shin-ichi TOYAMA shin1@wmail.plala.or.jp
<shin1@wmail.plala.or.jp>
Réglages pour compilation
Depuis février 2005 (à partir de Tux Paint 0.9.15), le "Makefile"
inclut la prise en charge de la construction sur un système Windows
à l'aide de MinGW/MSYS (http://www.mingw.org/).
à l'aide de MinGW/MSYS (https://sourceforge.net/projects/msys2/).
Après avoir configuré l'environnement et construit et installé tous
les dépendances, utilisez ces commandes, dans MSYS, pour créer,
installer et exécuter :
Beaucoup d'outils et de bibliothèques sont nécessaires pour élaborer
Tux Paint. Le système de gestion de paquet "pacman" apporte une aide
pour installer automatiquement, en résolvant les dépendances
nombreuses.
Avant la version 0.9.20 :
Téléchargez le dernier environnement MSYS2 à partir de
https://sourceforge.net/projects/msys2/files/Base/ et installez-le
où vous voulez (par défaut "C:\msys64")
$ make win32
$ make install-win32
$ tuxpaint
Ouvrez le shell MSYS2 via le "Menu de Démarrage" ->"MSYS2 64bit" ->
"MSTS2 MSYS" et exécutez la commande suivante (pressez [Entrée] ou
[Retour] pour accepter par défaut toutes les questions) :
Version 0.9.20 et au-delà :
pacman -Syu
$ make
$ make install
$ tuxpaint
Ceci mettra à jour tout le système et la fenêtre de se fermera
automatiquement. Répétez les étapes précédentes encore une fois pour
finaliser le process restant de mise à jour.
Utilisez la commande suivante pour construire une version adaptée à
la redistribution avec l'installateur ou bien un fichier zip :
Sous le shell MSYS2, exécutez la commande suivante pour installer
outils basiques pour le développement :
pacman -S base-devel msys2-devel git
Allez à la prochaine section "chaînes d'outils MinGW 64bit (x86_64) ",
ou bien à la section "chaînes d'outils MinGW 32bit (i686)" si vous ne
voulez qu'un environnement de travail 32bit.
-------------------------------------------------------
Chaînes d'outils MinGW 64bit (x86_64)
Sous le shell MSYS2, exécutez la commande suivante pour installer
outils basiques pour le développement 64bit :
pacman -S mingw-w64-x86_64-toolchain
bibliothèques de dépendance 64bit (x86_64) pour Tux Paint
Vous pouvez installer les outils et bibliothèques nécessaires pour
la compilation de Tux Paint sur MSYS2 en utilisant "pacman", sauf
pour SDL_Pango.
"ntldd" est un petit outil qui examine les fichiers exécutables de
windows en vue de lister les fichiers DLL (.dll) qui leur sont
nécessaires. Le process de fabrication de Tux Paint pour fournir des
fichiers binaires s'en sert pour trouver les fichiers .dll requis.
FLTK est un ensemble d'outils multiplateforme utilisé par "Tux Paint
Config.". Vous pouvez en pas l'installer si vous compilez seulement
"Tux Paint".
$ pacman -S mingw-w64-x86_64-SDL_{image,mixer,ttf}
$ pacman -S mingw-w64-x86_64-librsvg
$ pacman -S mingw-w64-x86_64-fribidi
$ pacman -S mingw-w64-x86_64-libimagequant
$ pacman -S mingw-w64-x86_64-fltk
$ pacman -S mingw64/mingw-w64-x86_64-ntldd-git
Nota !Fermez l'interpréteur de commandes avant de passer à la suite.
Installe SDL_Pango et réinstalle SDL sur l'environnement 64bit
SDL_Pango doit être installé manuellement. De plus, vous devez
réinstaller SDL à partir du code source, sinon vous verrez s'ouvrir
une fenêtre blanche inutile au démarrage de Tux Paint.
Cette fois-ci, utilisez le shell MinGW "64bit". Ouvrez le shell
depuis le "Menu de Démarrage" -> "MSYS2 64bit" -> "MSYS2 MinGW
64-bit"
SDL_Pango
Tout d'abord, vous devrez préparer l'archive source et un patch
qui est requis, dans le même répertoire.
* Télécharger source tar-ball of SDL_Pango-0.1.2 depuis
SDL_Pango's page on Sourceforge.net.
* Télécharger un fichier patch depuis La page web de John
Popplewell traitant des "instructions pour la compilation de
Tux Paint - MinGW/MSYS". (Ceci ajoute une fonctionnalité
supplémentaire (requise) à SDL_Pango.)
Compiler et installer SDL_Pango comme suit.
$ tar zxvf SDL_Pango-0.1.2.tar.gz
$ cd SDL_Pango-0.1.2/
$ patch -p0 < ../SDL_Pango-configure-extra-api.patch
$ ./configure --prefix=/mingw64 && make && make install
SDL
Télécharger source tar-ball of SDL_1.2.15 depuis libsdl.org.
Réinstallez SDL comme suit.
$ tar zxvf SDL-1.2.15.tar.gz
$ cd SDL-1.2.15
$ ./configure --prefix=/mingw64 && make && make install
Aller à la prochaine section "chaines d'outils MinGW 32bit (i686)", ou
bien aller directement à la section "ImageMagick" si vous n'avez
besoin que d'un environnement de travail 64bit.
-------------------------------------------------------
Chaînes d'outils MinGW 32bit (i686)
Sous le shell MSYS2, exécutez la commande suivante pour installer
outils basiques pour le développement 32bit :
pacman -S mingw-w64-i686-toolchain
bibliothèques de dépendance 32bit (i686) pour Tux Paint
Vous pouvez installer les outils et bibliothèques nécessaires pour
la compilation de Tux Paint sur MSYS2 en utilisant "pacman", sauf
pour SDL_Pango.
"ntldd" est un petit outil qui examine les fichiers exécutables de
windows en vue de lister les fichiers DLL (.dll) qui leur sont
nécessaires. Le process de fabrication de Tux Paint pour fournir des
fichiers binaires s'en sert pour trouver les fichiers .dll requis.
FLTK est un ensemble d'outils multiplateforme utilisé par "Tux Paint
Config.". Vous pouvez en pas l'installer si vous compilez seulement
"Tux Paint".
$ pacman -S mingw-w64-i686-SDL_{image,mixer,ttf}
$ pacman -S mingw-w64-i686-librsvg
$ pacman -S mingw-w64-i686-fribidi
$ pacman -S mingw-w64-i686-libimagequant
$ pacman -S mingw-w64-i686-fltk
$ pacman -S mingw-w64-i686-ntldd-git
Nota !Fermez l'interpréteur de commandes avant de passer à la suite.
Installe SDL_Pango et réinstalle SDL sur l'environnement 32bit
SDL_Pango doit être installé manuellement. De plus, vous devez
réinstaller SDL à partir du code source, sinon vous verrez s'ouvrir
une fenêtre blanche inutile au démarrage de Tux Paint.
Cette fois-ci, utilisez le shell MinGW "32bit". Ouvrez le shell
depuis le "Menu de Démarrage" -> "MSYS2 64bit" -> "MSYS2 MinGW
32-bit"
SDL_Pango
Tout d'abord, vous devrez préparer l'archive source et un patch
qui est requis, dans le même répertoire.
* Télécharger source tar-ball of SDL_Pango-0.1.2 depuis
SDL_Pango's page on Sourceforge.net.
* Télécharger un fichier patch depuis La page web de John
Popplewell traitant des "instructions pour la compilation de
Tux Paint - MinGW/MSYS". (Ceci ajoute une fonctionnalité
supplémentaire (requise) à SDL_Pango.)
Compiler et installer SDL_Pango comme suit.
$ tar zxvf SDL_Pango-0.1.2.tar.gz
$ cd SDL_Pango-0.1.2/
$ patch -p0 < ../SDL_Pango-configure-extra-api.patch
$ ./configure --prefix=/mingw32 && make && make install
SDL
Télécharger source tar-ball of SDL_1.2.15 depuis libsdl.org.
Réinstallez SDL comme suit.
$ tar zxvf SDL-1.2.15.tar.gz
$ cd SDL-1.2.15
$ ./configure --prefix=/mingw32 && make && make install
-------------------------------------------------------
ImageMagick
ImageMagick est un ensemble d'outils en ligne de commande pour
créer, éditer, composer ou convertir des images bitmap, et qui
soupporte un grand nombre de formats d'image.Tux Paint utilise deux
fonctions ("convert" and "composite") pour générer des vignettes
pour les images de démarrage et des modèles durant le process de
compiltaion.
L'utilisation des binaires officiels tirés de "Versions binaires
pour Windows" est recommandée car les commandes installées avec
"pacman" sur MinGW/MSYS ne fonctionnent pas comme elles devraient !
N'oubliez pas de cocher "Installer les utilitaires hérités (par ex.
convert)" pour l'installation, car le processus de compilation de
Tux Paint les utilise.
Ajoutez le chemin où ImageMagick est installé au début de votre
variable d'environnement "PATH". Par exemple :
$ export PATH=/c/Program\ Files/ImageMagick-7.0.10-Q16-HDRI:$PATH
Vous pouvez rendre ceci permanent en ajoutant ce qui précède à votre
fichier de configuration du shell BASH, "~/.bash_profile".
-------------------------------------------------------
Tux Paint
Vous pouvez compiler des binaires 64bit en utilisant le shell MSYS2
64bit, et des binaires 32bit en utilisant le shell MSYS2 32bit.
* Choisissez "MSYS2 64bit" -> "MSYS2 MinGW 64-bit" dans le "Menu
de Démarrage" pour ouvrir le shell 64bit
* Choisissez "MSYS2 64bit" -> "MSYS2 MinGW 32-bit" dans le "Menu
de Démarrage" pour ouvrir le shell 32bit
Compilez Tux Paint avec la commande suivante :
$ make bdist-win32
Ou bien si vous compilez pour Win9x/ME :
Note: At this point, you will want to build "Tux Paint Config." for
Windows, so it can be included along with "Tux Paint", if you're
making an official (or test) release. The build process will look
for it in a directory named "tuxpaint-config" (with no version
number, e.g., "tuxpaint-config-X.Y.Z"). See "Tux Paint Config."'s
INSTALL.txt documentation for details.
$ BDIST_WIN9X=1 make bdist-win32
All the files needed for starting Tux Paint (and Tux Paint Config.)
are collected in the directory for binary distribution "bdist"
directory under "win32". You can start them by double-clicking their
executable (.exe) files in the "bdist" directory.
Avant de mettre en oeuvre les opérations ci-dessus, vous devez
configurer l'environnement et compilez ou installez les
bibliothèques nécessaires pour Tux Paint. John Popplewell a
rassemblé quelques instructions ici pour y parvenir :
-------------------------------------------------------
http://www.johnnypops.co.uk/tuxpaint/
Construire l'installateur de Tux Paint sous Windows :
Lisez les notes pertinentes si vous construisez pour Win9X / ME.
Inno Setup is used to build executable installer for Tux Paint.
Therefore you have to install it in the first place.
Installateur :
Then, you can easily build an executable installer by right-clicking
on the "tuxpaint.iss" icon in the "win32" directory and selecting
"Compile" on the list. It will run for a while, and eventually you
will find a "tuxpaint-X.Y.Z-win32-installer.exe" file in the same
directory.
-------------------------------------------------------
Utliser l'installateur de Tux Paint sous Windows :
Double-cliquez sur l'exécutable du programme d'installation de Tux
Paint (fichier .EXE) et Suivez les instructions.
@ -187,6 +427,8 @@ Compilation et installation :
À ce stade, vous pouvez cliquer sur «Installer» pour installer Tux
Paint !
-------------------------------------------------------
Modification des paramètres à l'aide du raccourci :
Pour modifier les paramètres du programme, cliquez avec le bouton
@ -218,6 +460,8 @@ Compilation et installation :
Quand vous avez fini, appuyez sur "OK".
-------------------------------------------------------
Si quelque chose ne va pas :
Si, lorsque vous double-cliquez sur le raccourci pour lancer le jeu,
@ -231,7 +475,9 @@ Compilation et installation :
incorrecte (majuscule 'Z' à la place de 'z' minuscule) ou un '-'
(tiret) manquant (en trop).
Utilisateurs de Linux/Unix :
----------------------------------------------------------------------
Utilisateurs de Linux/Unix
Compilation :
@ -245,6 +491,8 @@ Compilation et installation :
$ make
-------------------------------------------------------
Désactivation du support SVG (donc des dépendances Cairo, libSVG, et
svg-cairo)
@ -255,6 +503,8 @@ Compilation et installation :
$ make SVG_LIB= SVG_CFLAGS=
-------------------------------------------------------
Désactivation du support Pango (donc des dépendances Pango, Cairo, etc ...)
Avant la version 0.9.18, Tuxpaint utilisait la bibliothèque
@ -266,6 +516,8 @@ Compilation et installation :
$ make SDL_PANGO_LIB=
-------------------------------------------------------
Désactiver le son lors de la compilation :
Si vous n'avez pas de carte son ou si vous préférez créer le
@ -274,11 +526,15 @@ Compilation et installation :
$ make SDL_MIXER_LIB=
-------------------------------------------------------
Autres options :
Diverses autres options (par exemple, les dossiers d'installation)
peuvent être remplacées; voir dans "Makefile" pour plus de détails.
-------------------------------------------------------
Si vous obtenez des erreurs :
Si vous avez des erreurs lors de la compilation, assurez-vous
@ -289,6 +545,8 @@ Compilation et installation :
correspondants, sinon vous ne pourrez pas compiler Tux Paint (et
d'autres programmes) provenant des sources !
-------------------------------------------------------
Installation :
En supposant qu'aucune erreur fatale ne s'est produite, vous pouvez
@ -365,13 +623,151 @@ Compilation et installation :
Remarque : Cette liste est obsolète. Voir "Makefile" et
"Makefile-i18n" pour une liste complète.
Débogage :
----------------------------------------------------------------------
Le débogage (vers "STDOUT", par exemple le terminal, ou vers un fichier
"stdout.txt", sous Windows) peut être activé en définissant "DEBUG" (et,
si un mode verbeux est souhaité, "VERBOSE") # define dans "src/debug.h.
macOS Users
Désinstallation de Tux Paint :
septembre 21, 2021 Mark K. Kim <markuskimius@gmail.com>
Tux Paint 0.9.22 and earlier required building Tux Paint from the
Xcode IDE. Starting with 0.9.23, however, Tux Paint for macOS is built
as though it were a Linux application.
Prérequis
Although Tux Paint is built without the Xcode IDE, Xcode itself is
still required to build Tux Paint. Download it from the App Store,
and launch it once to accept its license agreements. You may also
need to install the Xcode command line tools using the command:
xcode-select --install
Building Tux Paint also requires various libraries. We install them
from MacPorts where possible, source code otherwise. Install
MacPorts to the default /opt/local path according to the
instructions found on their website: https://www.macports.org/
* ImageMagick
* cairo
* fribidi
* lbzip2
* libimagequant^*
* libpaper
* libpng
* librsvg
* libsdl
* libsdl_image
* libsdl_mixer
* libsdl_pango
* libsdl_ttf
* pkgconfig
* zlib
... mais vous devriez installer tout paquet requis par la dernière
version de Tux Paint.
^* Non disponible depuis MacPorts à ce moment, voir ci-dessous.
libimagequant
libimagequant is not available from MacPorts as of this writing.
It can be installed from the source code as follows. It should be
installed to /opt/local (same as MacPorts) for the library to be
included in TuxPaint.dmg.
$ git clone https://github.com/ImageOptim/libimagequant.git
$ cd libimagequant
$ ./configure --prefix=/opt/local
$ make
$ sudo make install
WARNING: Having any UNIX-like toolset installed on your Mac besides
MacPorts and Xcode, such as Fink or Brew, will prevent your app
bundle from being portable. Be sure Fink and Brew are not accessible
from your build environment.
-------------------------------------------------------
Comment construire
Tapez simplement :
% make
% make install
... to create the TuxPaint.app application bundle that can be run
in-place or copied to /Applications. It also creates TuxPaint.dmg
for distribution.
-------------------------------------------------------
Problèmes connus
* A macOS binary built on a specific version of macOS only runs on
that version of macOS or later. To ensure Tux Paint can run on
the oldest version of macOS possible, build it on the oldest
version of macOS available. As of this writing we know Tux Paint
cannot be built to run on macOS 10.7 or earlier.
See "Old Versions of macOS" below for best-effort instructions
on how to obtain, install, and build Tux Paint on an old version
of macOS.
-------------------------------------------------------
Vieilles versions de macOS
Some old versions of macOS can be downloaded from Apple's support
page: https://support.apple.com/en-us/HT211683
macOS does allow dual booting of multiple versions of the OS, but
it's safer and easier to install the old macOS onto a flash drive.
Wherever you're installing it, the target drive's partitioniong
scheme and partition type must match what the old macOS expects, so
use the Disk Utility to partition and format the flash drive
accordingly.
As of this writing, the oldest version of macOS available on Apple's
support site is Yosemite 10.10, which expects "GPT (GUID Partition
Table)" partitioning scheme instead of the older MBR scheme, and
"Mac OS Extended (Journaled)" as the partition type instead of the
newer APFS partition type.
Upon launching the installer, if you get a popup about macOS being
too old or new to be installed, a bootable installer can be created
using the instructions found here:
https://support.apple.com/en-mide/HT201372
It has been found that macOS can be installed onto the bootable
media itself, so you can make the flash drive into a bootable
installer then install the old macOS onto the same flash drive.
Once the old macOS is installed, you may find the Xcode on the App
Store is too new to run on the version of the old macOS. Old
versions of Xcode can be downloaded from Apple's Developer site in
an area accessible with free registration:
https://developer.apple.com/download/more/
The list of macOS versions and the last version of Xcode compatible
with them are laid out nicely on the Wikipedia page on Xcode:
https://en.wikipedia.org/wiki/Xcode#Version_comparison_table
And because Xcode is being installed manually, you can skip the step
to install the Xcode command line tools (do not run "xcode-select
--install") but otherwise build Tux Paint using the same steps
described in the earlier part of this document.
----------------------------------------------------------------------
Débogage
Le débogage — vers "STDOUT", avec Linux et Unix, vers un fichier
"stdout.txt"avec Windows, et vers le fichier "/tmp/tuxpaint.log" avec
macOS — peut être activé en définissant "DEBUG" (et, si un mode verbeux
est souhaité, "VERBOSE") # define dans "src/debug.h, et en (re)compilant
Tux Paint.
----------------------------------------------------------------------
Désinstallation de Tux Paint
Windows
@ -392,6 +788,18 @@ Désinstallation de Tux Paint :
uniquement)" dans la Section Ajout / Suppression de programmes du
Panneau de configuration.
----------------------------------------------------------------------
macOS
Delete "TuxPaint.app" from the "Applications" folder. Data files,
including the configuration files, stamps, and saved pictures, may be
found in "Bibliothèque/Support d'Application/Tux Paint" (all users)
and "/Users/USERNAME/Library/Application Support/TuxPaint" (individual
users).
----------------------------------------------------------------------
Linux
Dans le répertoire source de Tux Paint (où vous avez compilé Tux
@ -399,6 +807,6 @@ Désinstallation de Tux Paint :
désinstaller Tux Paint. Par défaut, cela doit être fait par
l'utilisateur "root" ("superutilisateur"), mais si vous avez installé
Tux Paint à un autre endroit (par ex. en mettant "PREFIX=..." à "make"
et "make install", vous ne pourrez pas, et il faudra fournier les
mêmes réglages ici. (Voir les instructions d'installation ci-dessus
pour plus d'informations.)
et "make install", vous ne pourrez pas, et il faudra fournir les mêmes
réglages ici. (Voir <a href="#compiling-linux>les instructions
d'installation ci-dessus pour plus d'informations.)

2092
docs/fr_FR.UTF-8/OPTIONS.txt
View file

File diff suppressed because it is too large Load diff

2
docs/fr_FR.UTF-8/PNG.txt
View file

@ -1,5 +1,5 @@
Tux Paint
version 0.9.26
version 0.9.27
Documentation sur PNG pour Tux Paint
Copyright &copie; 2007-2021 par divers contributeurs; voir AUTHORS.

33
docs/fr_FR.UTF-8/README.txt
View file

@ -1,12 +1,12 @@
Tux Paint
version 0.9.26
version 0.9.27
Un programme simple pour les enfants
Copyright &copie; 2002-2021 par divers contributeurs; voir AUTHORS.
http://www.tuxpaint.org/
juin 28, 2021
septembre 5, 2021
----------------------------------------------------------------------
@ -136,7 +136,7 @@ Lancement de Tux Paint
----------------------------------------------------------------------
Utilisateurs de macOS
macOS Users
Double-cliquez simplement sur l'icône "Tux Paint".
@ -235,6 +235,22 @@ Outils disponibles
la souris, elle dessine au fur et à mesure que vous vous
déplacez.
Some brushes are animated — they change their shape as you
draw them. A good example of this is the vines brush that
ships with Tux Paint. These brushes will have a small
"filmstrip" icon drawn on their Selector buttons.
Other brushes are directional — they will draw a different
shape depending on what direction you are painting with
them. An example of this is the arrow brush that ships with
Tux Paint. These brushes have a small 8-way arrow icon drawn
on their Selector buttons.
Finally, some brushes can be both direction and animated.
Examples of this are the cat and squirrel brushes that ship
with Tux Paint. These brushes will have both the "filmstrip"
and 8-way arrow icons.
Pendant que vous dessinez, un son est joué. Plus la brosse
est grosse, plus le son est grave.
@ -301,6 +317,12 @@ Outils disponibles
Relâchez la souris pour terminer la ligne. On entend alors
le son "sproing !".
Some brushes are animated, and will show a pattern of shapes
along the line. Others are directional, and will show a
different shape depending on the angle of the brush. And
finally some are both animated and directional. See "Paint",
above, to learn more.
----------------------------------------------------------------------
Outil "Formes"
@ -367,8 +389,9 @@ Outils disponibles
bas). Cliquez sur l'écran et un curseur apparaîtra. Tapez un
texte et il apparaîtra à l'écran.
Appuyez sur [Enter] ou [Return] et le texte sera inclus dans
l'image et le curseur se déplacera d'une ligne vers le bas.
Appuyez sur [Entrée] ou [Retour] et le texte sera inclus
dans l'image et le curseur se déplacera d'une ligne vers le
bas.
Sinon, appuyez sur [Tab] et le texte sera inclus dans
l'image, mais le curseur se déplacera vers la droite du

2
docs/fr_FR.UTF-8/SIGNALS.txt
View file

@ -1,5 +1,5 @@
Tux Paint
version 0.9.26
version 0.9.27
Documentation sur les signaux
Copyright &copie; 2019-2021 par divers contributeurs; voir AUTHORS.

2
docs/fr_FR.UTF-8/SVG.txt
View file

@ -1,5 +1,5 @@
Tux Paint
version 0.9.26
version 0.9.27
Documentation sur SVG
Copyright &copie; 2007-2021 par divers contributeurs; voir AUTHORS.

85
docs/fr_FR.UTF-8/html/ADVANCED-STAMPS-HOWTO.html
View file

@ -17,16 +17,62 @@
width="205"
height="210"
alt="Tux Paint"><br>
version 0.9.26 'Guide pratique" pour les tampons de haute qualité </h1>
version 0.9.27 'Guide pratique" pour les tampons de haute qualité </h1>
<p>
Copyright &copie; 2006-2021 par Albert Cahalan et d'autres; voir AUTHORS.<br>
<a href="http://www.tuxpaint.org/">http://www.tuxpaint.org/</a>
</p>
<p>
août 29, 2021 </p>
</center>
<hr size="2"
noshade>
<table border="2"
cellspacing="0"
cellpadding="2"
summary="Table des matières">
<tr>
<th>
Table des matières </th>
</tr>
<tr>
<td>
<ul>
<li>
<a href="#about">À propos de ce 'guide pratique'</a>
</li>
<li>
<a href="#choice">Le choix de l'image est crucial</a>
</li>
<li>
<a href="#prepare_mask">Préparez le masque</a>
</li>
<li>
<a href="#replace_fringe">Remplacer la frange et les pixels indésirables</a>
</li>
<li>
<a href="#save">Sauvegarder l'image pour Tux Paint</a>
</li>
</ul>
</td>
</tr>
</table>
<hr size="2"
noshade>
<hr size="2"
noshade>
<h2>
À propos de ce 'guide pratique' </h2>
<a name="about" id="about">
À propos de ce 'guide pratique' </a>
</h2>
<blockquote>
<p>
@ -36,8 +82,13 @@
Ce 'guide pratique' suppose que vous travaillez avec des objets normalement opaques. Pour des objets semi-transparents (flamme, hélice de ventilateur en mouvement) ou des objets luminescents (feu, ampoule, soleil) mieux vaut travailler avec un logiciel adapté. Des images avec de parfaits arrière-plans de couleur unie sont mieux réalisées avec un logiciel adapté, mais ne posent pas de problèmes avec ce qui suit. </p>
</blockquote>
<hr size="2"
noshade>
<h2>
Le choix de l'image est crucial </h2>
<a name="choice" id="choice">
Le choix de l'image est crucial </a>
</h2>
<blockquote>
<h3>
@ -78,6 +129,9 @@
</blockquote>
</blockquote>
<hr size="2"
noshade>
<h2>
Préparez l'image </h2>
@ -116,8 +170,13 @@
<b>Attention :</b> une fois que avez le masque, vous ne pourrez plus tourner ou modifier la taille de l'image normalement. Cela entraînerait des pertes de données. On vous donnera plus tard des instructions pour la mise à l'échelle. </p>
</blockquote>
<hr size="2"
noshade>
<h2>
Préparez le masque </h2>
<a name="prepare_mask" id="prepare_mask">
Préparez le masque </a>
</h2>
<blockquote>
<p>
@ -151,8 +210,13 @@
Affichez et modifiez le masque. Sélectionnez par couleur, en choisissant le noir ou le blanc. Vous verrez sûrement des tâches non sélectionnées qui ne sont pas tout à fait à la couleur attendue. Inversez la sélection, et coloriez les avec l'outil crayon. Faites ces opérations pour le blanc et le noir. </p>
</blockquote>
<hr size="2"
noshade>
<h2>
Remplacer la frange et les pixels indésirables </h2>
<a name="replace_fringe" id="replace_fringe">
Remplacer la frange et les pixels indésirables </a>
</h2>
<blockquote>
<p>
@ -180,7 +244,7 @@ déposez cette couleur dans la sélection, supprimant ainsi la plupart des pixel
Pour réduire les accidents, vous souhaiterez peut-être sélectionner uniquement les pixels qui ne sont pas gris dans le masque. (Sélectionnez par couleur dans le masque, choisissez le noir, ajoutez le mode, choisissez le blanc, inversez. Ou bien : sélectionnez tout, sélectionnez par couleur dans le masque, soustrayez le mode, choisissez le noir, choisissez le blanc.) Si vous faites cela, vous voudrez probablement élargir un peu la sélection et / ou masquer la ligne "fourmis rampantes" qui marque la sélection. </p>
<p>
Utilisez l'outil de clonage et l'outil de pinceau. Faites varier l'opacité selon vos besoins. Utilisez principalement des petites brosses rondes, peut-être de 3x3 ou 5x5, floues ou non. (Il est généralement agréable d'associer des pinceaux flous avec une opacité de 100 % et des pinceaux non flous avec une opacité d'environ 70 %). On peut utiliser des modes de dessin inhabituels avec des objets semi-transparents. </p>
Use the clone tool and the brush tool. Vary the opacity as needed. Use small round brushes mostly, perhaps 3x3 or 5x5, fuzzy or not. (It is generally nice to pair up fuzzy brushes with 100% opacity and non-fuzzy brushes with about 70% opacity.) Unusual drawing modes can be helpful with semi-transparent objects. </p>
<p>
Le but est de supprimer la frange de bord, à la fois à l'intérieur et à l'extérieur de l'objet. La frange intérieure, visible lorsque l'objet est composé de magenta ou de vert, doit être supprimée pour des raisons évidentes. La frange extérieure doit également être supprimée car elle deviendra visible lorsque l'image sera réduite. À titre d'exemple, considérons une région avec 2x2 de pixels au bord d'un objet aux arêtes vives. La moitié gauche est noire et opaque à 0%. La moitié droite est blanche et 100% opaque. Autrement dit, nous avons un objet blanc sur fond noir. Lorsque Tux Paint redimensionne cela à 50% (une zone de 1 x 1 pixel), le résultat sera un pixel opaque gris à 50%. Le résultat correct devrait être un pixel blanc opaque à 50%. Pour obtenir ce résultat, nous devrions peindre les pixels noirs. Ils comptent, bien qu'ils soient à 0 % d'opacité. </p>
@ -189,12 +253,17 @@ déposez cette couleur dans la sélection, supprimant ainsi la plupart des pixel
Tux Paint peut réduire considérablement la taille des images, il est donc important d'étendre considérablement le bord de votre objet vers l'extérieur. Juste au bord de votre objet, vous devez être très précis sur ce point. Lorsque vous vous éloignez de l'objet, cela risque de faire négligé. Il est raisonnable de peindre vers l'extérieur sur une douzaine de pixels ou plus. Plus vous irez loin, plus Tux Paint pourra réduire la taille sans créer de franges avec des couleurs moches. Pour les zones situées à plus de quelques pixels du bord, vous devez utiliser l'outil Crayon (ou une vague sélection avec une couleur en glisser-déposer) pour vous assurer que le résultat se compressera bien. </p>
</blockquote>
<hr size="2"
noshade>
<h2>
Sauvegarder l'image pour Tux Paint </h2>
<a name="save" id="save">
Sauvegarder l'image pour Tux Paint </a>
</h2>
<blockquote>
<p>
Il est très facile de gâcher votre travail, lui qui vous a demandé beaucoup d'efforts. Les éditeurs d'images peuvent détruire silencieusement les pixels dans les zones 0% opaques. Les conditions dans lesquelles cela se produit peuvent varier d'une version à l'autre. Si vous êtes très confiant, vous pouvez essayer d'enregistrer votre image directement au format PNG. Assurez-vous de le relire pour vérifier que les zones opaques à 0% ne deviennent ni noires ni blanches, ce qui créerait des franges lorsque Tux Paint réduira l'image. Si vous devez redimensionner votre image pour gagner de la place (et cacher vos erreurs), vous êtes presque certain de détruire toutes les zones opaques à 0%. Alors, voici une meilleure façon... </p>
It is very easy to ruin your hard work. Image editors can silently destroy pixels in 0% opaque areas. The conditions under which this happens may vary from version to version. If you are very trusting, you can try saving your image directly as a PNG. Be sure to read it back in again to verify that the 0% opaque areas didn't turn black or white, which would create fringes when Tux Paint scales the image down. If you need to scale your image to save space (and hide your mistakes), you are almost certain to destroy all the 0% opaque areas. So here is a better way... </p>
<h3>
Une façon sûre pour sauvegarder </h3>

4
docs/fr_FR.UTF-8/html/ENVVARS.html
View file

@ -17,7 +17,7 @@
width="205"
height="210"
alt="Tux Paint"><br>
version 0.9.26<br/>
version 0.9.27<br/>
Documentation sur les variables d'environnement </h1>
<p>
@ -26,7 +26,7 @@
</p>
<p>
mai 11, 2021 </p>
août 8, 2021 </p>
</center>
<hr>

45
docs/fr_FR.UTF-8/html/EXTENDING.html
View file

@ -18,7 +18,7 @@
width="205"
height="210"
alt="Tux Paint"><br>
version 0.9.26 </h1>
version 0.9.27 </h1>
<p>
Copyright &copie; 2002-2021 par divers contributeurs; voir AUTHORS.<br>
@ -26,7 +26,7 @@
</p>
<p>
mai 31, 2021 </p>
septembre 6, 2021 </p>
</center>
<hr size="2"
@ -316,7 +316,7 @@
<blockquote>
<p>
Outre une a graphical shape, les brushes peuvent également recevoir d'autres attributs. Pour ce faire, vous devez créer un «fichier de données» pour brush. </p>
Outre une une forme graphique, les pinceaux peuvent également recevoir d'autres attributs. Pour ce faire, vous devez créer un «fichier de données» pour brosse. </p>
<p>
Un fichier de données de brush's est simplement un fichier texte ASCII contenant les options pour le brush. </p>
@ -363,18 +363,29 @@
Les formes orientables sont divisées en carrés de 3x3 dans une image PNG. Par exemple, si votre pinceau fait 30x30, l'image doit être de 90x90 et chacune des formes orientables est placée dans une grille de 3x3. La région centrale n'est pas orientable. Le haut à droite est utilisé pour le mouvement vers le haut, et vers la droite. Etc ... </p>
<p>
Ajoute une ligne contenant le mot "<code><b>directional</b></code>" au fichier de données brush's. </p>
Ajoute une ligne contenant le mot "<code><b>directional</b></code>" au fichier de données brosse. </p>
</blockquote>
<h4>
Pinceaux animés orientables </h4>
Rotating Brushes </h4>
<blockquote>
<p>
Vous pouvez mélanger animation et orientation dans un même pinceau. Utilisez les deux options ("<code><b>frames=<i>N</i></b></code>" et "<code><b>directional</b></code>") en deux lignes séparées dans le fichier "<code>.dat</code>" qui concerne le pinceau. </p>
As of Tux Paint version 0.9.27, you may now create rotating brushes. As the brush is used, it is rotated 360 degrees, depending on the direction the brush is going. </p>
<p>
Disposez le pinceau de manière à ce que chaque ensemble 3x3 de formes orientables soit disposé sur une grande image PNG. Par exemple, si le pinceau mesure 30x30 et qu'il y a 5 cadres, ce sera 450x90. (Les 150x90 pixels les plus à gauche de l'image représentent les 9 formes de direction pour la première image, par exemple). </p>
Ajoute une ligne contenant le mot "<code><b>rotate</b></code>" au fichier de données brosse. </p>
</blockquote>
<h4>
Animated Directional or Rotating Brushes </h4>
<blockquote>
<p>
You may mix both animated and either directional or rotating features into one brush. Use both options desired ("<code><b>frames=<i>N</i></b></code>" and "<code><b>directional</b></code>" or "<code><b>rotate</b></code>"), in separate lines in the brush's "<code>.dat</code>" file. </p>
<p>
For directional brushes, lay the brush out so that each 3x3 set of directional shapes are laid out across a wide PNG image. For example, if the brush is 30x30 and there are 5 frames, it would be 450x90. (The leftmost 150x90 pixels of the image represent the 9 direction shapes for the first frame, for example.) </p>
</blockquote>
</blockquote>
@ -382,7 +393,7 @@
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 brushes 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>
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>
<br clear="all">
</blockquote>
@ -418,7 +429,7 @@
Les fichiers PNG peuvent être de n'importe quelle taille, et Tux Paint (par défaut) fournit un ensemble de boutons de redimensionnement pour permettre à l'utilisateur d'ajuster le tampon vers le haut (plus grand) et vers le bas (plus petit). </p>
<p>
Les SVG sont basés sur des vecteurs et seront mis à l'échelle de manière adéquate pour le canevas utilisé. </p>
SVGs are vector-based, and will be scaled appropriately for the canvas size being used in Tux Paint. </p>
<p>
Remarque: si vos nouveaux PNG-based stamps 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>
@ -536,13 +547,13 @@
<blockquote>
<p>
Outre une a graphical shape, a textual description, a sound effect, and a descriptive sound, les stamps peuvent également recevoir d'autres attributs. Pour ce faire, vous devez créer un «fichier de données» pour stamp. </p>
Outre une une forme graphique, un texte de description, un effet sonore et une description orale, les tampons peuvent également recevoir d'autres attributs. Pour ce faire, vous devez créer un «fichier de données» pour tampon. </p>
<p>
Un fichier de données de stamp's est simplement un fichier texte ASCII contenant les options pour le stamp. </p>
Un fichier de données de tampon est simplement un fichier texte ASCII contenant les options pour le tampon. </p>
<p>
Le fichier porte le même nom que l'image PNG or SVG , mais une extension "<code>.dat</code>". (par exemple, le fichier de données "<code>stamp.png</code>" est le fichier texte "<code>stamp.dat</code>" qui se trouve dans le même répertoire.) </p>
Le fichier porte le même nom que l'image PNG ou SVG , mais une extension "<code>.dat</code>". (par exemple, le fichier de données "<code>stamp.png</code>" est le fichier texte "<code>stamp.dat</code>" qui se trouve dans le même répertoire.) </p>
<h4>
Tampons colorés </h4>
@ -569,7 +580,7 @@
</center>
<p>
Ajoute une ligne contenant le mot "<code><b>colorable</b></code>" au fichier de données stamp's. </p>
Ajoute une ligne contenant le mot "<code><b>colorable</b></code>" au fichier de données tampon. </p>
</blockquote>
<h5>
@ -587,7 +598,7 @@
</center>
<p>
Ajoute une ligne contenant le mot "<code><b>tintable</b></code>" au fichier de données stamp's. </p>
Ajoute une ligne contenant le mot "<code><b>tintable</b></code>" au fichier de données tampon. </p>
<h6>
Options de teinture : </h6>
@ -639,10 +650,10 @@
Parfois, cela n'a pas de sens pour un timbre d'être retourné ou reflété; par exemple, des timbres de lettres ou de chiffres. Parfois, les tampons sont symétriques, il n'est donc pas utile de laisser l'utilisateur les retourner ou les refléter. </p>
<p>
Pour empêcher un tampon d'être from being flipped vertically, ajoutez une ligne contenant le mot «<code><b>noflip</b></code>» au fichier de données du tampon. </p>
Pour empêcher un tampon d'être qui a été inversé verticalement, ajoutez une ligne contenant le mot «<code><b>noflip</b></code>» au fichier de données du tampon. </p>
<p>
Pour empêcher un tampon d'être from being mirrored horizontally, ajoutez une ligne contenant le mot «<code><b>nomirror</b></code>» au fichier de données du tampon. </p>
Pour empêcher un tampon d'être qui a été inversé horizontalement, ajoutez une ligne contenant le mot «<code><b>nomirror</b></code>» au fichier de données du tampon. </p>
</blockquote>
<h4>
@ -932,7 +943,7 @@
<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>
<i>Remarque :</i> la prise en charge de nouveaux input methods 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>
<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>
</blockquote>
<hr size="1"

106
docs/fr_FR.UTF-8/html/FAQ.html
View file

@ -17,7 +17,7 @@
width="205"
height="210"
alt="Tux Paint"><br>
version 0.9.26 Questions fréquemment posées </h1>
version 0.9.27 Questions fréquemment posées </h1>
<p>
Copyright &copie; 2002-2021 par divers contributeurs; voir AUTHORS.<br>
@ -25,13 +25,60 @@
</p>
<p>
juin 2, 2021 </p>
août 29, 2021 </p>
</center>
<hr>
<hr size="2"
noshade>
<table border="2"
cellspacing="0"
cellpadding="2"
summary="Table des matières">
<tr>
<th>
Table des matières </th>
</tr>
<tr>
<td>
<ul>
<li>
<a href="#drawing">Liées au dessin</a>
</li>
<li>
<a href="#interface">Problèmes d'interface</a>
</li>
<li>
<a href="#printing">Impression</a>
</li>
<li>
<a href="#saving">Sauvegarde</a>
</li>
<li>
<a href="#audio">Problèmes audio</a>
</li>
<li>
<a href="#fullscreen">Problèmes en mode plein écran</a>
</li>
<li>
<a href="#other">Autres problèmes</a>
</li>
<li>
<a href="#contact">Aide / Contact</a>
</li>
</ul>
</td>
</tr>
</table>
<hr size="2"
noshade>
<h2>
Liées au dessin </h2>
<a name="drawing" id="drawing">
Liées au dessin </a>
</h2>
<dl>
<dt>
@ -101,10 +148,13 @@
</dd>
</dl>
<hr>
<hr size="2"
noshade>
<h2>
Problèmes d'interface </h2>
<a name="interface" id="interface">
Problèmes d'interface </a>
</h2>
<dl>
<dt>
@ -212,10 +262,13 @@
</dd>
</dl>
<hr>
<hr size="2"
noshade>
<h2>
Impression </h2>
<a name="printing" id="printing">
Impression </a>
</h2>
<dl>
<dt>
@ -282,10 +335,13 @@
</dd>
</dl>
<hr>
<hr size="2"
noshade>
<h2>
Sauvegarde </h2>
<a name="saving" id="saving">
Sauvegarde </a>
</h2>
<dl>
<dt>
@ -378,14 +434,17 @@
Ou utilisez Tux Paint Config. et assurez-vous que "Demander avant d'écraser" (sous "Sauvegarde") est vérifié. </p>
<p>
Also, see "Tux Paint always saves over my old picture!", above. </p>
Également voyez "Tux Paint sauvegarde en écrasant toujours mon ancienne image !", ci-dessus. </p>
</dd>
</dl>
<hr>
<hr size="2"
noshade>
<h2>
Problèmes audio </h2>
<a name="audio" id="audio">
Problèmes audio </a>
</h2>
<dl>
<dt>
@ -508,10 +567,13 @@ cible "nosound". (c'est-à-dire, ne lancez pas "<code>make nosound</code>") Assu
</dd>
</dl>
<hr>
<hr size="2"
noshade>
<h2>
Problèmes en mode plein écran </h2>
<a name="fullscreen" id="fullscreen">
Problèmes en mode plein écran </a>
</h2>
<dl>
<dt>
@ -570,10 +632,13 @@ cible "nosound". (c'est-à-dire, ne lancez pas "<code>make nosound</code>") Assu
</dd>
</dl>
<hr>
<hr size="2"
noshade>
<h2>
Autres problèmes </h2>
<a name="other" id="other">
Autres problèmes </a>
</h2>
<dl>
<dt>
@ -745,10 +810,13 @@ cible "nosound". (c'est-à-dire, ne lancez pas "<code>make nosound</code>") Assu
</dd>
</dl>
<hr>
<hr size="2"
noshade>
<h2>
Aide / Contact </h2>
<a name="contact" id="contact">
Aide / Contact </a>
</h2>
<p>
Des questions auxquelles vous ne trouvez pas de réponse ? Merci de nous le faire savoir ! Vous pouvez vous abonner et écrire sur notre liste de diffusion "tuxpaint-users" : </p>

625
docs/fr_FR.UTF-8/html/INSTALL.html
View file

@ -17,7 +17,7 @@
width="205"
height="210"
alt="Tux Paint"><br>
version 0.9.26<br/>
version 0.9.27<br/>
Documentation sur l'installation </h1>
<p>
@ -26,21 +26,88 @@
</p>
<p>
mars 9, 2021 </p>
septembre 5, 2021 </p>
</center>
<hr>
<hr size="2" noshade />
<h2>Exigences :</h2>
<table border="2"
cellspacing="0"
cellpadding="2"
summary="Table des matières">
<tr>
<th>
Table des matières </th>
</tr>
<tr>
<td>
<ul>
<li>
<a href="#requirements">Exigences</a>
<ul>
<li>
<a href="#req-libsdl">Biliothèque Simple DirectMedia Layer (libSDL)</a>
</li>
<li>
<a href="#req-other-libs">Autres bibliothèques</a>
</li>
</ul>
</li>
<li>
<a href="#compiling">Compilation et installation</a>
<ul>
<li>
<a href="#compiling-windows">Utilisateurs de Windows</a>
</li>
<li>
<a href="#compiling-linux">Utilisateurs de Linux/Unix</a>
</li>
<li>
<a href="#compiling-macos">macOS Users</a>
</li>
</ul>
</li>
<li>
<a href="#debugging">Débogage</a>
</li>
<li>
<a href="#uninstalling">Désinstallation de Tux Paint</a>
<ul>
<li>
<a href="#uninstalling-windows">Windows</a>
</li>
<li>
<a href="#uninstalling-macOS">macOS</a>
</li>
<li>
<a href="#uninstalling-linux">Linux</a>
</li>
</ul>
</li>
</ul>
</td>
</tr>
</table>
<hr size="2" noshade />
<h2>
<a name="requirements" id="requirements">
Exigences </a>
</h2>
<blockquote>
<h3>libSDL</h3>
<h3>
<a name="req-libsdl" id="req-libsdl">
Biliothèque Simple DirectMedia Layer (libSDL) </a>
</h3>
<blockquote>
<p>
Tux Paint nécessite la bibliothèque de couches DirectMedia simple (libSDL), une bibliothèque de programmation multimédia Open Source disponible sous la Licence publique générale limitée GNU (LGPL). </p>
<p>
Avec libSDL, Tux Paint dépend d'un certain nombre d'autres bibliothèques SDL : SDL_Image (pour les fichiers graphiques), SDL_TTF et (en option) SDL_Pango (pour la prise en charge des polices True Type) et, éventuellement, SDL_Mixer (pour les effets sonores). </p>
Along with libSDL, Tux Paint depends on a number of other SDL 'helper' libraries: SDL_Image (for graphics files), SDL_gfx (for some graphical functions, like rotation), SDL_TTF and (optionally) SDL_Pango (for True Type Font support) and, optionally, SDL_Mixer (for sound effects). </p>
<h4>Utilisateurs de Linux/Unix :</h4>
<blockquote>
@ -49,6 +116,7 @@
<ul>
<li>libSDL: <a href="http://www.libsdl.org/">http://www.libsdl.org/</a></li>
<li>SDL_Image: <a href="http://www.libsdl.org/projects/SDL_image/">http://www.libsdl.org/projects/SDL_image/</a></li>
<li>SDL_gfx: <a href="https://www.ferzkopp.net/wordpress/2016/01/02/sdl_gfx-sdl2_gfx/">https://www.ferzkopp.net/wordpress/2016/01/02/sdl_gfx-sdl2_gfx/</a> (<a href="https://sourceforge.net/projects/sdlgfx/">https://sourceforge.net/projects/sdlgfx/</a>)</li>
<li>SDL_TTF: <a href="http://www.libsdl.org/projects/SDL_ttf/">http://www.libsdl.org/projects/SDL_ttf/</a></li>
<li>SDL_Pango: <a href="http://sourceforge.net/projects/sdlpango/">http://sourceforge.net/projects/sdlpango/</a> (optionnel)</li>
<li>SDL_Mixer: <a href="http://www.libsdl.org/projects/SDL_mixer/">http://www.libsdl.org/projects/SDL_mixer/</a> (optionnel)</li>
@ -62,7 +130,10 @@
</blockquote>
</blockquote>
<h3>Autres bibliothèques</h3>
<h3>
<a name="req-other-libs" id="req-other-libs">
Autres bibliothèques </a>
</h3>
<blockquote>
<p>
Tux Paint profite également d'un certain nombre d'autres bibliothèques gratuites LGPL. Sous Linux, tout comme SDL, ils devraient être soit déjà installées, soit facilement disponibles avec votre distribution Linux. </p>
@ -110,7 +181,7 @@
<h4>Support des graphismes SVG</h4>
<blockquote>
<p>
À partir de Tux Paint 0.9.17, Tux Paint peut prendre en charge les images SVG (Scalable Vector Graphics) pour les tampons. Deux ensembles de bibliothèques sont pris en charge et le support SVG peut être complètement désactivé (via "<code>make SVG_LIB:=</code>=") </p>
À partir de Tux Paint 0.9.17, Tux Paint peut prendre en charge les images SVG (Scalable Vector Graphics) pour les tampons. Deux ensembles de bibliothèques sont pris en charge et le support SVG peut être complètement désactivé (via "<code style="white-space: nowrap;">make SVG_LIB:=</code>=") </p>
<h5>librsvg-2 &amp; libCairo2 (nouvelles bibliothèques)</h5>
<ul>
@ -155,66 +226,322 @@
</blockquote>
</blockquote>
<h2>Compilation et installation :</h2>
<hr size="2" noshade />
<h2>
<a name="compiling" id="compiling">
Compilation et installation </a>
</h2>
<blockquote>
<p>
Tux Paint est publié sous la licence publique générale GNU (GPL) (voir "COPYING.txt" pour plus de détails), et donc le 'code source' du programme est disponible gratuitement. </p>
<h3>Utilisateurs de Windows :</h3>
<h3>
<a name="compiling-windows" id="compiling-windows">
Utilisateurs de Windows </a>
</h3>
<p style="font-size: small;">
<em>
octobre 25, 2020 Shin-ichi TOYAMA shin1@wmail.plala.or.jp &lt;<a href="mailto:shin1@wmail.plala.or.jp">shin1@wmail.plala.or.jp</a>&gt;
</em>
</p>
<blockquote>
<h4>Compilation :</h4>
<h4>Réglages pour compilation</h4>
<blockquote>
<p>
Depuis février 2005 (à partir de Tux Paint 0.9.15), le "<code>Makefile</code>" inclut la prise en charge de la construction sur un système Windows à l'aide de MinGW/MSYS (<a href="http://www.mingw.org/">http://www.mingw.org/</a>). </p>
Depuis février 2005 (à partir de Tux Paint 0.9.15), le "<code>Makefile</code>" inclut la prise en charge de la construction sur un système Windows à l'aide de MinGW/MSYS (<a href="https://sourceforge.net/projects/msys2/">https://sourceforge.net/projects/msys2/</a>). </p>
<p>
Après avoir configuré l'environnement et construit et installé tous les dépendances, utilisez ces commandes, dans MSYS, pour créer, installer et exécuter : </p>
<h5>Avant la version 0.9.20 :</h5>
<blockquote>
<code>
$ make win32<br/>
$ make install-win32<br/>
$ tuxpaint
</code>
</blockquote>
<h5>Version 0.9.20 et au-delà :</h5>
<blockquote>
<code>
$ make<br/>
$ make install<br/>
$ tuxpaint
</code>
</blockquote>
Beaucoup d'outils et de bibliothèques sont nécessaires pour élaborer Tux Paint. Le système de gestion de paquet "<code>pacman</code>" apporte une aide pour installer automatiquement, en résolvant les dépendances nombreuses. </p>
<p>
Utilisez la commande suivante pour construire une version adaptée à la redistribution avec l'installateur ou bien un fichier zip : </p>
<blockquote>
<code>
$ make bdist-win32
</code>
</blockquote>
Téléchargez le dernier environnement MSYS2 à partir de <a href="https://sourceforge.net/projects/msys2/files/Base/">https://sourceforge.net/projects/msys2/files/Base/</a> et installez-le où vous voulez (par défaut "<code>C:\msys64</code>") </p>
<p>
Ou bien si vous compilez pour Win9x/ME : </p>
<blockquote>
<code>
$ BDIST_WIN9X=1 make bdist-win32
</code>
</blockquote>
<p>
Avant de mettre en oeuvre les opérations ci-dessus, vous devez configurer l'environnement et compilez ou installez les bibliothèques nécessaires pour Tux Paint. John Popplewell a rassemblé quelques instructions ici pour y parvenir : </p>
<p>
<a href="http://www.johnnypops.co.uk/tuxpaint/">http://www.johnnypops.co.uk/tuxpaint/</a>
Ouvrez le shell MSYS2 via le "Menu de Démarrage" -&gt;"MSYS2 64bit" -&gt; "MSTS2 MSYS" et exécutez la commande suivante (pressez <b><code>[Entrée]</code></b> ou <b><code>[Retour]</code></b> pour accepter par défaut toutes les questions) :
<blockquote>
<code>
pacman -Syu
</code>
</blockquote>
</p>
<p>
Lisez les notes pertinentes si vous construisez pour Win9X / ME. </p>
Ceci mettra à jour tout le système et la fenêtre de se fermera automatiquement. Répétez les étapes précédentes encore une fois pour finaliser le process restant de mise à jour. </p>
<p>
Sous le shell MSYS2, exécutez la commande suivante pour installer outils basiques pour le développement : <blockquote>
<code>
pacman -S base-devel msys2-devel git
</code>
</blockquote>
</p>
</blockquote>
<h4>Installateur :</h4>
<p>
<i>
Allez à la prochaine section "<a href="#64bit">chaînes d'outils MinGW 64bit (x86_64) </a>", ou bien à la section "<a href="#32bit">chaînes d'outils MinGW 32bit (i686)</a>" si vous ne voulez qu'un environnement de travail 32bit. </i>
</p>
<hr size="1" noshade width="75%" />
<h4>
<a name="64bit" id="64bit">
Chaînes d'outils MinGW 64bit (x86_64) </a>
</h4>
<blockquote>
<p>
Sous le shell MSYS2, exécutez la commande suivante pour installer outils basiques pour le développement 64bit : <blockquote>
<code>
pacman -S mingw-w64-x86_64-toolchain
</code>
</blockquote>
</p>
</blockquote>
<h4>
bibliothèques de dépendance 64bit (x86_64) pour Tux Paint </h4>
<blockquote>
<p>
Vous pouvez installer les outils et bibliothèques nécessaires pour la compilation de Tux Paint sur MSYS2 en utilisant "<code>pacman</code>", sauf pour SDL_Pango. </p>
<p>
"<code>ntldd</code>" est un petit outil qui examine les fichiers exécutables de windows en vue de lister les fichiers DLL (<code>.dll</code>) qui leur sont nécessaires. Le process de fabrication de Tux Paint pour fournir des fichiers binaires s'en sert pour trouver les fichiers <code>.dll</code> requis. </p>
<p>
FLTK est un ensemble d'outils multiplateforme utilisé par "Tux Paint Config.". Vous pouvez en pas l'installer si vous compilez <em>seulement</em> "Tux Paint". </p>
<p>
<blockquote>
<code>
$ pacman -S mingw-w64-x86_64-SDL_{image,mixer,ttf}<br/>
$ pacman -S mingw-w64-x86_64-librsvg<br/>
$ pacman -S mingw-w64-x86_64-fribidi<br/>
$ pacman -S mingw-w64-x86_64-libimagequant<br/>
$ pacman -S mingw-w64-x86_64-fltk<br/>
$ pacman -S mingw64/mingw-w64-x86_64-ntldd-git
</code>
</blockquote>
</p>
<p>
<strong>Nota !</strong>Fermez l'interpréteur de commandes avant de passer à la suite. </p>
</blockquote>
<h4>
Installe SDL_Pango et réinstalle SDL sur l'environnement 64bit </h4>
<blockquote>
<p>
SDL_Pango doit être installé manuellement. De plus, vous devez réinstaller SDL à partir du code source, sinon vous verrez s'ouvrir une fenêtre blanche inutile au démarrage de Tux Paint. </p>
<p>
Cette fois-ci, utilisez le shell MinGW "64bit". Ouvrez le shell depuis le "Menu de Démarrage" -&gt; "MSYS2 64bit" -&gt; "MSYS2 MinGW 64-bit" </p>
<h5>SDL_Pango</h5>
<blockquote>
<p>
Tout d'abord, vous devrez préparer l'archive source et un patch qui est requis, dans le même répertoire. </p>
<ul>
<li>
Télécharger <a href="https://sourceforge.net/projects/sdlpango/files/SDL_Pango/0.1.2/SDL_Pango-0.1.2.tar.gz/download">source tar-ball of SDL_Pango-0.1.2</a> depuis <a href="https://sourceforge.net/projects/sdlpango/">SDL_Pango's page on Sourceforge.net</a>. </li>
<li>
Télécharger <a href="http://johnnypops.co.uk/tuxpaint/SDL_Pango-configure-extra-api.patch">un fichier patch</a> depuis <a href="http://www.johnnypops.co.uk/tuxpaint/">La page web de John Popplewell traitant des "instructions pour la compilation de Tux Paint - MinGW/MSYS"</a>. (Ceci ajoute une fonctionnalité supplémentaire (requise) à SDL_Pango.) </li>
</ul>
<p>
Compiler et installer SDL_Pango comme suit. <blockquote>
<code>
$ tar zxvf SDL_Pango-0.1.2.tar.gz<br/>
$ cd SDL_Pango-0.1.2/<br/>
$ patch -p0 &lt; ../SDL_Pango-configure-extra-api.patch<br/>
$ ./configure --prefix=/mingw64 &amp;&amp; make &amp;&amp; make install
</code>
</blockquote>
</p>
</blockquote>
<h5>SDL</h5>
<blockquote>
<p>
Télécharger <a href="http://www.libsdl.org/release/SDL-1.2.15.tar.gz">source tar-ball of SDL_1.2.15</a> depuis <a href="http://www.libsdl.org/">libsdl.org</a>. </p>
<p>
Réinstallez SDL comme suit. <blockquote>
<code>
$ tar zxvf SDL-1.2.15.tar.gz<br/>
$ cd SDL-1.2.15<br/>
$ ./configure --prefix=/mingw64 &amp;&amp; make &amp;&amp; make install
</code>
</blockquote>
</p>
</blockquote>
</blockquote>
<p>
<i>
Aller à la prochaine section "<a href="#32bit">chaines d'outils MinGW 32bit (i686)</a>", ou bien aller directement à la section "<a href="#imagemagick">ImageMagick</a>" si vous n'avez besoin que d'un environnement de travail 64bit. </i>
</p>
<hr size="1" noshade width="75%" />
<h4>
<a name="32bit" id="32bit">
Chaînes d'outils MinGW 32bit (i686) </a>
</h4>
<blockquote>
<p>
Sous le shell MSYS2, exécutez la commande suivante pour installer outils basiques pour le développement 32bit : <blockquote>
<code>
pacman -S mingw-w64-i686-toolchain
</code>
</blockquote>
</p>
</blockquote>
<h4>
bibliothèques de dépendance 32bit (i686) pour Tux Paint </h4>
<blockquote>
<p>
Vous pouvez installer les outils et bibliothèques nécessaires pour la compilation de Tux Paint sur MSYS2 en utilisant "<code>pacman</code>", sauf pour SDL_Pango. </p>
<p>
"<code>ntldd</code>" est un petit outil qui examine les fichiers exécutables de windows en vue de lister les fichiers DLL (<code>.dll</code>) qui leur sont nécessaires. Le process de fabrication de Tux Paint pour fournir des fichiers binaires s'en sert pour trouver les fichiers <code>.dll</code> requis. </p>
<p>
FLTK est un ensemble d'outils multiplateforme utilisé par "Tux Paint Config.". Vous pouvez en pas l'installer si vous compilez <em>seulement</em> "Tux Paint". </p>
<p>
<blockquote>
<code>
$ pacman -S mingw-w64-i686-SDL_{image,mixer,ttf}<br/>
$ pacman -S mingw-w64-i686-librsvg<br/>
$ pacman -S mingw-w64-i686-fribidi<br/>
$ pacman -S mingw-w64-i686-libimagequant<br/>
$ pacman -S mingw-w64-i686-fltk<br/>
$ pacman -S mingw-w64-i686-ntldd-git
</code>
</blockquote>
</p>
<p>
<strong>Nota !</strong>Fermez l'interpréteur de commandes avant de passer à la suite. </p>
</blockquote>
<h4>
Installe SDL_Pango et réinstalle SDL sur l'environnement 32bit </h4>
<blockquote>
<p>
SDL_Pango doit être installé manuellement. De plus, vous devez réinstaller SDL à partir du code source, sinon vous verrez s'ouvrir une fenêtre blanche inutile au démarrage de Tux Paint. </p>
<p>
Cette fois-ci, utilisez le shell MinGW "32bit". Ouvrez le shell depuis le "Menu de Démarrage" -&gt; "MSYS2 64bit" -&gt; "MSYS2 MinGW 32-bit" </p>
<h5>SDL_Pango</h5>
<blockquote>
<p>
Tout d'abord, vous devrez préparer l'archive source et un patch qui est requis, dans le même répertoire. </p>
<ul>
<li>
Télécharger <a href="https://sourceforge.net/projects/sdlpango/files/SDL_Pango/0.1.2/SDL_Pango-0.1.2.tar.gz/download">source tar-ball of SDL_Pango-0.1.2</a> depuis <a href="https://sourceforge.net/projects/sdlpango/">SDL_Pango's page on Sourceforge.net</a>. </li>
<li>
Télécharger <a href="http://johnnypops.co.uk/tuxpaint/SDL_Pango-configure-extra-api.patch">un fichier patch</a> depuis <a href="http://www.johnnypops.co.uk/tuxpaint/">La page web de John Popplewell traitant des "instructions pour la compilation de Tux Paint - MinGW/MSYS"</a>. (Ceci ajoute une fonctionnalité supplémentaire (requise) à SDL_Pango.) </li>
</ul>
<p>
Compiler et installer SDL_Pango comme suit. <blockquote>
<code>
$ tar zxvf SDL_Pango-0.1.2.tar.gz<br/>
$ cd SDL_Pango-0.1.2/<br/>
$ patch -p0 &lt; ../SDL_Pango-configure-extra-api.patch<br/>
$ ./configure --prefix=/mingw32 &amp;&amp; make &amp;&amp; make install
</code>
</blockquote>
</p>
</blockquote>
<h5>SDL</h5>
<blockquote>
<p>
Télécharger <a href="http://www.libsdl.org/release/SDL-1.2.15.tar.gz">source tar-ball of SDL_1.2.15</a> depuis <a href="http://www.libsdl.org/">libsdl.org</a>. </p>
<p>
Réinstallez SDL comme suit. <blockquote>
<code>
$ tar zxvf SDL-1.2.15.tar.gz<br/>
$ cd SDL-1.2.15<br/>
$ ./configure --prefix=/mingw32 &amp;&amp; make &amp;&amp; make install
</code>
</blockquote>
</p>
</blockquote>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>
<a name="imagemagick" id="imagemagick">ImageMagick</a>
</h4>
<blockquote>
<p>
<a href="https://imagemagick.org">ImageMagick</a> est un ensemble d'outils en ligne de commande pour créer, éditer, composer ou convertir des images bitmap, et qui soupporte un grand nombre de formats d'image.Tux Paint utilise deux fonctions ("convert" and "composite") pour générer des vignettes pour les images de démarrage et des modèles durant le process de compiltaion. </p>
<p>
L'utilisation des binaires officiels tirés de "<a href="https://imagemagick.org/script/download.php#windowsand">Versions binaires pour Windows</a>" est recommandée car les commandes installées avec "<code>pacman</code>" sur MinGW/MSYS ne fonctionnent pas comme elles devraient ! </p>
<p>
N'oubliez pas de cocher "Installer les utilitaires hérités (par ex. convert)" pour l'installation, car le processus de compilation de Tux Paint les utilise. </p>
<p>
Ajoutez le chemin où ImageMagick est installé au début de votre variable d'environnement "PATH". Par exemple : <blockquote>
<code>
$ export PATH=/c/Program\ Files/ImageMagick-7.0.10-Q16-HDRI:$PATH
</code>
</blockquote>
</p>
<p>
Vous pouvez rendre ceci permanent en ajoutant ce qui précède à votre fichier de configuration du shell BASH, "<code>~/.bash_profile</code>". </p>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>Tux Paint</h4>
<blockquote>
<p>
Vous pouvez compiler des binaires 64bit en utilisant le shell MSYS2 64bit, et des binaires 32bit en utilisant le shell MSYS2 32bit. </p>
<ul>
<li>
Choisissez "MSYS2 64bit" -&gt; "MSYS2 MinGW 64-bit" dans le "Menu de Démarrage" pour ouvrir le shell 64bit </li>
<li>
Choisissez "MSYS2 64bit" -&gt; "MSYS2 MinGW 32-bit" dans le "Menu de Démarrage" pour ouvrir le shell 32bit </li>
</ul>
<p>
Compilez Tux Paint avec la commande suivante : <blockquote>
<code>
$ make bdist-win32
</code>
</blockquote>
</p>
<p>
<strong>Note:</strong> At this point, you will want to build "Tux Paint Config." for Windows, so it can be included along with "Tux Paint", if you're making an official (or test) release. The build process will look for it in a directory named "<code>tuxpaint-config</code>" (with no version number, e.g., "<code>tuxpaint-config-X.Y.Z</code>"). See "Tux Paint Config."'s INSTALL.txt documentation for details. </p>
<p>
All the files needed for starting Tux Paint (and Tux Paint Config.) are collected in the directory for binary distribution "<code>bdist</code>" directory under "<code>win32</code>". You can start them by double-clicking their executable (<code>.exe</code>) files in the "<code>bdist</code>" directory. </p>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>Construire l'installateur de Tux Paint sous Windows :</h4>
<blockquote>
<p>
<a href="https://jrsoftware.org/isinfo.php">Inno Setup</a> is used to build executable installer for Tux Paint. Therefore you have to install it in the first place. </p>
<p>
</p>
<p>
Then, you can easily build an executable installer by right-clicking on the "<code>tuxpaint.iss</code>" icon in the "<code>win32</code>" directory and selecting "Compile" on the list. It will run for a while, and eventually you will find a "<code>tuxpaint-<i>X.Y.Z</i>-win32-installer.exe</code>" file in the same directory. </p>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>Utliser l'installateur de Tux Paint sous Windows :</h4>
<blockquote>
<p>
Double-cliquez sur l'exécutable du programme d'installation de Tux Paint (fichier .EXE) et Suivez les instructions.
@ -231,6 +558,8 @@
À ce stade, vous pouvez cliquer sur «Installer» pour installer Tux Paint ! </p>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>Modification des paramètres à l'aide du raccourci :</h4>
<blockquote>
<p>
@ -267,6 +596,8 @@
Quand vous avez fini, appuyez sur "OK". </p>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>Si quelque chose ne va pas :</h4>
<blockquote>
<p>
@ -277,7 +608,12 @@
</blockquote>
</blockquote>
<h3>Utilisateurs de Linux/Unix :</h3>
<hr size="1" noshade />
<h3>
<a name="compiling-linux" id="compiling-linux">
Utilisateurs de Linux/Unix </a>
</h3>
<blockquote>
<h4>Compilation :</h4>
<blockquote>
@ -294,11 +630,13 @@
</blockquote>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>
Désactivation du support SVG (donc des dépendances Cairo, libSVG, et svg-cairo) </h4>
<blockquote>
<p>
Pour désactiver le support de SVG (par ex. si votre système n'a pas de bibliothèque Cairo, ou d'autres choses dont SVG est dépendan), vous pouvez exécuter "<code>make</code>" avec <code>SVG_LIB= SVG_CFLAGS= NOSVGFLAG=NOSVG</code> :
Pour désactiver le support de SVG (par ex. si votre système n'a pas de bibliothèque Cairo, ou d'autres choses dont SVG est dépendan), vous pouvez exécuter "<code>make</code>" avec <code style="white-space: nowrap;">SVG_LIB= SVG_CFLAGS= NOSVGFLAG=NOSVG</code> :
<blockquote>
<code>
$ make SVG_LIB= SVG_CFLAGS=
@ -306,6 +644,8 @@
</blockquote>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>
Désactivation du support Pango (donc des dépendances Pango, Cairo, etc ...) </h4>
<blockquote>
@ -318,6 +658,8 @@
</blockquote>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>Désactiver le son lors de la compilation :</h4>
<blockquote>
Si vous n'avez pas de carte son ou si vous préférez créer le programme sans support sonore (et donc sans dépendance <code>SDL_mixer</code>), vous pouvez exécuter "<code>make</code>" avec "<code>SDL_MIXER_LIB=</code>" comme paramètre : </p>
@ -328,18 +670,24 @@
</blockquote>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>Autres options :</h4>
<blockquote>
<p>
Diverses autres options (par exemple, les dossiers d'installation) peuvent être remplacées; voir dans "<code>Makefile</code>" pour plus de détails. </p>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>Si vous obtenez des erreurs :</h4>
<blockquote>
<p>
Si vous avez des erreurs lors de la compilation, assurez-vous d'avoir les bibliothèques adéquates installées (voir ci-dessus). Si vous utilisez les versions issues des paquets des bibliothèques (par exemple, les RPM sous RedHat ou les DEB sous Debian), assurez-vous d'avoir choisi également les packages "<code>-dev</code>" ou "<code>-devel</code>" correspondants, sinon vous ne pourrez pas compiler Tux Paint (et d'autres programmes) provenant des sources ! </p>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>Installation :</h4>
<blockquote>
<p>
@ -422,15 +770,155 @@
</blockquote>
</blockquote>
</blockquote>
<hr size="1" noshade />
<h3>
<a name="compiling-macos" id="compiling-macos">
macOS Users </a>
</h3>
<p style="font-size: small;">
<em>
septembre 21, 2021 Mark K. Kim &lt;<a href="mailto:markuskimius@gmail.com">markuskimius@gmail.com</a>&gt;
</em>
</p>
<blockquote>
<p>
Tux Paint 0.9.22 and earlier required building Tux Paint from the Xcode IDE. Starting with 0.9.23, however, Tux Paint for macOS is built as though it were a Linux application. </p>
<h4>Prérequis</h4>
<blockquote>
<p>
Although Tux Paint is built without the Xcode IDE, Xcode itself is still required to build Tux Paint. <a href="https://developer.apple.com/xcode/ide/">Download it from the App Store</a>, and launch it once to accept its license agreements. You may also need to install the Xcode command line tools using the command: <blockquote>
<code>
xcode-select --install
</code>
</blockquote>
</p>
<p>
Building Tux Paint also requires various libraries. We install them from MacPorts where possible, source code otherwise. Install MacPorts to the default <code>/opt/local</code> path according to the instructions found on their website: <a href="https://www.macports.org/">https://www.macports.org/</a> <ul>
<li><code>ImageMagick</code></li>
<li><code>cairo</code></li>
<li><code>fribidi</code></li>
<li><code>lbzip2</code></li>
<li><code>libimagequant</code><sup>*</sup></li>
<li><code>libpaper</code></li>
<li><code>libpng</code></li>
<li><code>librsvg</code></li>
<li><code>libsdl</code></li>
<li><code>libsdl_image</code></li>
<li><code>libsdl_mixer</code></li>
<li><code>libsdl_pango</code></li>
<li><code>libsdl_ttf</code></li>
<li><code>pkgconfig</code></li>
<li><code>zlib</code></li>
</ul>
... mais vous devriez installer tout paquet requis par la dernière version de Tux Paint.<br/>
<br/>
<sup>*</sup> Non disponible depuis MacPorts à ce moment, voir ci-dessous. </p>
<h5>libimagequant</h5>
<blockquote>
<p>
<code>libimagequant</code> is not available from MacPorts as of this writing. It can be installed from the source code as follows. It should be installed to <code>/opt/local</code> (same as MacPorts) for the library to be included in <code>TuxPaint.dmg</code>. <blockquote>
<code>
$ git clone https://github.com/ImageOptim/libimagequant.git<br/>
$ cd libimagequant<br/>
$ ./configure --prefix=/opt/local<br/>
$ make<br/>
$ sudo make install
</code>
</blockquote>
</p>
</blockquote>
<p>
<strong>WARNING:</strong> Having any UNIX-like toolset installed on your Mac besides MacPorts and Xcode, such as Fink or Brew, will prevent your app bundle from being portable. Be sure Fink and Brew are not accessible from your build environment. </p>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>Comment construire</h4>
<blockquote>
<p>
Tapez simplement : <blockquote>
<code>
% make<br/>
% make install
</code>
</blockquote>
... to create the <code>TuxPaint.app</code> application bundle that can be run in-place or copied to <code>/Applications</code>. It also creates <code>TuxPaint.dmg</code> for distribution. </p>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>Problèmes connus</h4>
<blockquote>
<ul>
<li>
A macOS binary built on a specific version of macOS only runs on that version of macOS or later. To ensure Tux Paint can run on the oldest version of macOS possible, build it on the oldest version of macOS available. As of this writing we know Tux Paint cannot be built to run on macOS 10.7 or earlier.<br/>
<br/>
See "Old Versions of macOS" below for best-effort instructions on how to obtain, install, and build Tux Paint on an old version of macOS. </li>
</ul>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>Vieilles versions de macOS</h4>
<blockquote>
<p>
Some old versions of macOS can be downloaded from Apple's support page: <a href="https://support.apple.com/en-us/HT211683">https://support.apple.com/en-us/HT211683</a> </p>
<p>
macOS does allow dual booting of multiple versions of the OS, but it's safer and easier to install the old macOS onto a flash drive. Wherever you're installing it, the target drive's partitioniong scheme and partition type must match what the old macOS expects, so use the Disk Utility to partition and format the flash drive accordingly. </p>
<p>
As of this writing, the oldest version of macOS available on Apple's support site is Yosemite 10.10, which expects "GPT (GUID Partition Table)" partitioning scheme instead of the older MBR scheme, and "Mac OS Extended (Journaled)" as the partition type instead of the newer APFS partition type. </p>
<p>
Upon launching the installer, if you get a popup about macOS being too old or new to be installed, a bootable installer can be created using the instructions found here: <a href="https://support.apple.com/en-mide/HT201372">https://support.apple.com/en-mide/HT201372</a> </p>
<p>
It has been found that macOS can be installed onto the bootable media itself, so you can make the flash drive into a bootable installer then install the old macOS onto the same flash drive. </p>
<p>
Once the old macOS is installed, you may find the Xcode on the App Store is too new to run on the version of the old macOS. Old versions of Xcode can be downloaded from Apple's Developer site in an area accessible with free registration: <a href="https://developer.apple.com/download/more/">https://developer.apple.com/download/more/</a> </p>
<p>
The list of macOS versions and the last version of Xcode compatible with them are laid out nicely on the Wikipedia page on Xcode: <a href="https://en.wikipedia.org/wiki/Xcode#Version_comparison_table">https://en.wikipedia.org/wiki/Xcode#Version_comparison_table</a> </p>
<p>
And because Xcode is being installed manually, you can skip the step to install the Xcode command line tools (do not run "<code style="white-space: nowrap;">xcode-select --install</code>") but otherwise build Tux Paint using the same steps described in the earlier part of this document. </p>
</blockquote>
</blockquote>
</blockquote>
<h2>Débogage :</h2>
<blockquote>
Le débogage (vers "STDOUT", par exemple le terminal, ou vers un fichier "<code>stdout.txt</code>", sous Windows) peut être activé en définissant "<code>DEBUG</code>" (et, si un mode verbeux est souhaité, "<code>VERBOSE</code>") <code># define</code> dans "<code>src/debug.h</code>. </blockquote>
<hr size="2" noshade />
<h2>Désinstallation de Tux Paint :</h2>
<h2>
<a name="debugging" id="debugging">
Débogage </a>
</h2>
<blockquote>
<h3>Windows</h3>
Le débogage &mdash; vers "STDOUT", avec Linux et Unix, vers un fichier "<code>stdout.txt</code>"avec Windows, et vers le fichier "<code>/tmp/tuxpaint.log</code>" avec macOS &mdash; peut être activé en définissant "<code>DEBUG</code>" (et, si un mode verbeux est souhaité, "<code>VERBOSE</code>") <code># define</code> dans "<code>src/debug.h</code>, et en (re)compilant Tux Paint. </blockquote>
<hr size="2" noshade />
<h2>
<a name="uninstalling" id="uninstalling">
Désinstallation de Tux Paint </h2>
</h2>
<blockquote>
<h3>
<a name="uninstalling-windows" id="uninstalling-windows">
Windows </a>
</h3>
<blockquote>
<h4>Utilisation du désinstalleur</h4>
<blockquote>
@ -448,10 +936,27 @@
</blockquote>
</blockquote>
<h3>Linux</h3>
<hr size="1" noshade />
<h3>
<a name="uninstalling-macos" id="uninstalling-macos">
macOS </a>
</h3>
<blockquote>
<p>
Dans le répertoire source de Tux Paint (où vous avez compilé Tux Paint), vous pouvez utiliser une cible "<code>make uninstall</code>" pour désinstaller Tux Paint. Par défaut, cela doit être fait par l'utilisateur "root" ("superutilisateur"), mais si vous avez installé Tux Paint à un autre endroit (par ex. en mettant "<code>PREFIX=...</code>" à "<code>make</code>" et "<code>make install</code>", vous ne pourrez pas, et il faudra fournier les mêmes réglages ici. (Voir les instructions d'installation ci-dessus pour plus d'informations.) </p>
Delete "<code>TuxPaint.app</code>" from the "Applications" folder. Data files, including the configuration files, stamps, and saved pictures, may be found in "<code style="white-space: nowrap;">Bibliothèque/Support d'Application/Tux Paint</code>" (all users) and "<code style="white-space: nowrap;">/Users/<i>USERNAME</i>/Library/Application Support/TuxPaint</code>" (individual users). </p>
</blockquote>
<hr size="1" noshade />
<h3>
<a name="uninstalling-linux" id="uninstalling-linux">
Linux </a>
</h3>
<blockquote>
<p>
Dans le répertoire source de Tux Paint (où vous avez compilé Tux Paint), vous pouvez utiliser une cible "<code style="white-space: nowrap;">make uninstall</code>" pour désinstaller Tux Paint. Par défaut, cela doit être fait par l'utilisateur "root" ("superutilisateur"), mais si vous avez installé Tux Paint à un autre endroit (par ex. en mettant "<code>PREFIX=...</code>" à "<code>make</code>" et "<code style="white-space: nowrap;">make install</code>", vous ne pourrez pas, et il faudra fournir les mêmes réglages ici. (Voir <a href="#compiling-linux>les instructions d'installation ci-dessus</a> pour plus d'informations.) </p>
</blockquote>
<blockquote>
</body>

5375
docs/fr_FR.UTF-8/html/OPTIONS.html
View file

File diff suppressed because it is too large Load diff

2
docs/fr_FR.UTF-8/html/PNG.html
View file

@ -17,7 +17,7 @@
width="205"
height="210"
alt="Tux Paint"><br>
version 0.9.26<br/>
version 0.9.27<br/>
Documentation sur PNG pour Tux Paint </h1>
<p>

20
docs/fr_FR.UTF-8/html/README.html
View file

@ -17,7 +17,7 @@
width="205"
height="210"
alt="Tux Paint"><br>
version 0.9.26 </h1>
version 0.9.27 </h1>
<h3>
Un programme simple pour les enfants </h3>
@ -28,7 +28,7 @@
</p>
<p>
juin 28, 2021 </p>
septembre 5, 2021 </p>
</center>
<hr size="2"
@ -239,7 +239,7 @@
noshade>
<h3>
Utilisateurs de macOS </h3>
macOS Users </h3>
<blockquote>
<p>
@ -408,6 +408,15 @@
<p>
Si vous maintenez le bouton de la souris enfoncé et déplacez la souris, elle dessine au fur et à mesure que vous vous déplacez. </p>
<p>
Some brushes are animated &mdash; they change their shape as you draw them. A good example of this is the vines brush that ships with Tux Paint. These brushes will have a small "filmstrip" icon drawn on their Selector buttons. </p>
<p>
Other brushes are directional &mdash; they will draw a different shape depending on what direction you are painting with them. An example of this is the arrow brush that ships with Tux Paint. These brushes have a small 8-way arrow icon drawn on their Selector buttons. </p>
<p>
Finally, some brushes can be both direction <em>and</em> animated. Examples of this are the cat and squirrel brushes that ship with Tux Paint. These brushes will have both the "filmstrip" and 8-way arrow icons. </p>
<p>
Pendant que vous dessinez, un son est joué. Plus la brosse est grosse, plus le son est grave. </p>
<br clear="all">
@ -503,6 +512,9 @@
<p>
Relâchez la souris pour terminer la ligne. On entend alors le son "sproing !". </p>
<p>
Some brushes are animated, and will show a pattern of shapes along the line. Others are directional, and will show a different shape depending on the angle of the brush. And finally some are both animated and directional. See "Paint", above, to learn more. </p>
<br clear="all">
<p align="center">
@ -605,7 +617,7 @@
Choisissez une police (parmi les «Lettres» disponibles sur la droite) et une couleur (dans la palette de couleurs en bas). Cliquez sur l'écran et un curseur apparaîtra. Tapez un texte et il apparaîtra à l'écran. </p>
<p>
Appuyez sur <strong><code>[Enter]</code></strong> ou <strong><code>[Return]</code></strong> et le texte sera inclus dans l'image et le curseur se déplacera d'une ligne vers le bas. </p>
Appuyez sur <b><code>[Entrée]</code></b> ou <b><code>[Retour]</code></b> et le texte sera inclus dans l'image et le curseur se déplacera d'une ligne vers le bas. </p>
<p>
Sinon, appuyez sur <strong><code>[Tab]</code></strong> et le texte sera inclus dans l'image, mais le curseur se déplacera vers la droite du texte, plutôt que vers le bas d'une ligne et vers la gauche. (Cela peut être utile pour créer une ligne de texte avec des couleurs, des polices, des styles et des tailles variés.) </p>

2
docs/fr_FR.UTF-8/html/SIGNALS.html
View file

@ -17,7 +17,7 @@
width="205"
height="210"
alt="Tux Paint"><br>
version 0.9.26<br/>
version 0.9.27<br/>
Documentation sur les signaux </h1>
<p>

2
docs/fr_FR.UTF-8/html/SVG.html
View file

@ -17,7 +17,7 @@
width="205"
height="210"
alt="Tux Paint"><br>
version 0.9.26<br/>
version 0.9.27<br/>
Documentation sur SVG </h1>
<p>

30
docs/gl_ES.UTF-8/ADVANCED-STAMPS-HOWTO.txt
View file

@ -1,9 +1,27 @@
Tux Paint
versión 0.9.26 «Como facer» os selos avanzados
versión 0.9.27 «Como facer» os selos avanzados
Copyright © 2006-2021 por Albert Cahalan e outros; vexa AUTHORS (AUTORES).
http://www.tuxpaint.org/
29 de Agosto de 2021
----------------------------------------------------------------------
+-------------------------------------------+
|Índice |
|-------------------------------------------|
| * Sobre este «Como facelo» |
| * A elección da imaxe é crucial |
| * Preparar a máscara |
| * Substituír a franxa e os píxeles lixo |
| * Gardar a imaxe para Tux Paint |
+-------------------------------------------+
----------------------------------------------------------------------
----------------------------------------------------------------------
Sobre este «Como facelo»
Este «Como facelo» supón que quere facer un excelente selo de Tux Paint,
@ -18,6 +36,8 @@ Sobre este «Como facelo»
sólida perfectos tamén se fan mellor con software personalizado, pero
non son difíciles de facer do seguinte xeito.
----------------------------------------------------------------------
A elección da imaxe é crucial
Licenza
@ -71,6 +91,8 @@ A elección da imaxe é crucial
que debuxar outros novos. Se só un está enterrado, pode que poida
copiar o outro como substituto.
----------------------------------------------------------------------
Preparar a imaxe
Primeiro de todo, asegúrese de evitar gardar de novo a imaxe como JPEG.
@ -108,6 +130,8 @@ Preparar a imaxe
imaxe normalmente. Isto provocaría a perda de datos. Máis adiante se lle
darán instrucións especiais de escalado.
----------------------------------------------------------------------
Preparar a máscara
Acostúmese a facer [Ctrl]-premer e [Alt]-premer nas imaxes en miniatura
@ -167,6 +191,8 @@ Preparar a máscara
agardada. Inverta a selección e logo pínteas coa ferramenta de lapis.
Faga esta operación tanto para branco como para negro.
----------------------------------------------------------------------
Substituír a franxa e os píxeles lixo
Se sigue a ver a máscara, seleccione por cor. Escolla o negro. Reduza a
@ -231,6 +257,8 @@ Substituír a franxa e os píxeles lixo
empregar a ferramenta de lapis (ou seleccionar arrastrar e soltar cor)
para garantir que o resultado se comprime ben.
----------------------------------------------------------------------
Gardar a imaxe para Tux Paint
É moi doado esnaquizar un traballo arreo. Os editores de imaxes poden

52
docs/gl_ES.UTF-8/ENVVARS.txt
View file

@ -1,11 +1,11 @@
Tux Paint
versión 0.9.26
versión 0.9.27
Documentación de variábeis de contorno
Copyright © 2021-2021 por varios colaboradores; vexa AUTHORS (AUTORES).
http://www.tuxpaint.org/
11 de Maio de 2021
8 de Agosto de 2021
----------------------------------------------------------------------
@ -36,25 +36,23 @@ Variábeis de contorno relacionadas co almacenamento
XDG_CONFIG_HOME
En Linux e noutras plataformas onde se usan os estándares X
Desktop Group, a localización dos ficheiros de configuración do
usuario. Especificamente, onde atopar «user-dirs.dirs», onde se
podería definir o «XDG_PICTURES_DIR». Úsase para exportar debuxos
e GIF animados. Xeralmente estabelecese en algo así como
«$HOME/Pictures/». Se non se especifica, Tux Paint comproba no
directorio «$HOME/.config/». Se non se pode atopar a
configuración, Tux Paint simplemente exporta debuxos e GIF a
«$HOME».
On Linux and other platforms where the X Desktop Group standards
are used, the location of the user's configuration files.
Specifically, where to find "user-dirs.dirs", where the
"XDG_PICTURES_DIR" might be defined. It is used for exporting
drawings and animated GIFs. Generally it's set to something like
"$HOME/Pictures/". If not specified, Tux Paint checks in the
directory "$HOME/.config/". If the configuration cannot be found,
Tux Paint simply exports drawings and GIFs to "$HOME".
XDG_DATA_HOME
En Linux e noutras plataformas onde se usan os estándares X
Desktop Group, a localización dos directorios de datos do usuario.
En concreto, onde atopar o directorio «Trash». Úsase cando se
eliminan imaxes do diálogo «Abrir» de Tux Paint. Se non se define,
úsase a localización «$HOME/.local/share/Trash/», se está
dispoñíbel. Se non, as imaxes bórranse simplemente no canto de
movelas a calquera outro lugar.
On Linux and other platforms where the X Desktop Group standards
are used, the location of the user's data directories.
Specifically, where to find the "Trash" directory. It is used when
deleting images from Tux Paint's "Open" dialog. If not set, the
location "$HOME/.local/share/Trash/" is used, if available. If
not, images are simply deleted, rather than moved anywhere.
TEMP
@ -72,12 +70,11 @@ Variábeis de contorno relacionadas co idioma
LC_MESSAGES
Especifica o idioma que debe empregar Tux Paint na súa interface
de usuario. Anulada polas opcións da liña de ordes «--lang» e
«--locale» ou as súas equivalentes do ficheiro de configuración.
Utilízase a variábel de contorno 'LANGUAGE', se está definida. Se
non, «LC_ALL» úsase como alternativa. Após «LC_MESSAGES» e,
finalmente, «LANG».
Specify the language Tux Paint should utilize in its user
interface. Overridde by the "--lang" and "--locale" command-line
options or their configuration file counterparts. The "LANGUAGE"
environment variable is used, if set. If not, "LC_ALL" is used as
a fallback. Then "LC_MESSAGES", and finally "LANG".
Variábeisbles de contorno relacionadas co que se amosa
@ -95,7 +92,6 @@ Variábeisbles de contorno relacionadas co que se amosa
SDL_VIDEO_WINDOW_POS
Solicita onde colocar a xanela de Tux Paint. Normalmente
estabelécese en «center» polo propio Tux Paint, a menos que a
variábel de contorno xa estea estabelecida (por exemplo, en
«nopref», que significa «sen preferencia»).
Requests where to position Tux Paint's window. Normally set to
"center" by Tux Paint itself, unless the environment variable is
already set (e.g., to "nopref", meaning "no preference").

32
docs/gl_ES.UTF-8/EXTENDING.txt
View file

@ -1,11 +1,11 @@
Ampliar
Tux Paint
versión 0.9.26
versión 0.9.27
Copyright © 2002-2021 por varios colaboradores; vexa AUTHORS (AUTORES).
http://www.tuxpaint.org/
31 de Maio de 2021
6 de Setembro de 2021
----------------------------------------------------------------------
@ -221,17 +221,27 @@ Pinceis
Engada unha liña que conteña a palabra «directional» ao ficheiro de
datos debrush's.
Pinceis direccionais animados
Rotating Brushes
Pode mesturar funcións animadas e direccionais nun pincel. Use ambas
as opcións («frames=N» e «directional»), en liñas separadas no
ficheiro «.dat» do pincel.
As of Tux Paint version 0.9.27, you may now create rotating brushes.
As the brush is used, it is rotated 360 degrees, depending on the
direction the brush is going.
Coloque o pincel de xeito que cada conxunto de formas 3x3 de
dirección estea distribuído nunha ampla imaxe PNG. Por exemplo, se o
pincel ten 30x30 e hai 5 fotogramas, sería de 450x90. (Os píxeles
máis a esquerda de 150x90 da imaxe representan as 9 formas de
dirección do primeiro cadro, por exemplo).
Engada unha liña que conteña a palabra «rotate» ao ficheiro de datos
debrush's.
Animated Directional or Rotating Brushes
You may mix both animated and either directional or rotating
features into one brush. Use both options desired ("frames=N" and
"directional" or "rotate"), in separate lines in the brush's ".dat"
file.
For directional brushes, lay the brush out so that each 3x3 set of
directional shapes are laid out across a wide PNG image. For
example, if the brush is 30x30 and there are 5 frames, it would be
450x90. (The leftmost 150x90 pixels of the image represent the 9
direction shapes for the first frame, for example.)
Coloque os ficheiros PNG de pincel (e calquera ficheiro de texto de
datos) no directorio «brushes».

19
docs/gl_ES.UTF-8/FAQ.txt
View file

@ -1,10 +1,25 @@
Tux Paint
versión 0.9.26 Preguntas máis frecuentes
versión 0.9.27 Preguntas máis frecuentes
Copyright © 2002-2021 por varios colaboradores; vexa AUTHORS (AUTORES).
http://www.tuxpaint.org/
2 de Xuño de 2021
29 de Agosto de 2021
----------------------------------------------------------------------
+--------------------------------------------+
|Índice |
|--------------------------------------------|
| * Relacionado co debuxo |
| * Problemas de interface |
| * Impresión |
| * Gardar |
| * Problemas de son |
| * Problemas no modo de pantalla completa |
| * Outros problemas |
| * Axuda / Contacto |
+--------------------------------------------+
----------------------------------------------------------------------

489
docs/gl_ES.UTF-8/INSTALL.txt
View file

@ -1,26 +1,46 @@
Tux Paint
versión 0.9.26
versión 0.9.27
Documentación da instalación
Copyright © 2002-2021 por varios colaboradores; vexa AUTHORS (AUTORES).
http://www.tuxpaint.org/
9 de Marzo de 2021
5 de Setembro de 2021
----------------------------------------------------------------------
Requisitos:
+----------------------------------------------------+
|Índice |
|----------------------------------------------------|
| * Requirements |
| * Simple DirectMedia Layer library (libSDL) |
| * Outras bibliotecas |
| * Compiling and Installation |
| * Usuarios de Windows |
| * Usuarios de Linux/Unix |
| * Usuarios de macOS |
| * Debugging |
| * Uninstalling Tux Paint |
| * Windows |
| * macOS |
| * Linux |
+----------------------------------------------------+
libSDL
----------------------------------------------------------------------
Requirements
Simple DirectMedia Layer library (libSDL)
Tux Paint require a «Simple DirectMedia Layer Library (libSDL)», unha
biblioteca de programación multimedia de código aberto dispoñíbel
baixo a licenza pública GNU Lesser General Public License (LGPL).
Xunto con libSDL, Tux Paint depende doutras bibliotecas «de axuda» de
SDL: SDL_Image (para ficheiros gráficos), SDL_TTF e (opcionalmente)
SDL_Pango (para compatibilidade de tipo True Type) e, opcionalmente,
SDL_Mixer (para efectos de son).
Along with libSDL, Tux Paint depends on a number of other SDL 'helper'
libraries: SDL_Image (for graphics files), SDL_gfx (for some graphical
functions, like rotation), SDL_TTF and (optionally) SDL_Pango (for
True Type Font support) and, optionally, SDL_Mixer (for sound
effects).
Usuarios de Linux/Unix:
@ -30,6 +50,9 @@ Requisitos:
* libSDL: http://www.libsdl.org/
* SDL_Image: http://www.libsdl.org/projects/SDL_image/
* SDL_gfx:
https://www.ferzkopp.net/wordpress/2016/01/02/sdl_gfx-sdl2_gfx/
(https://sourceforge.net/projects/sdlgfx/)
* SDL_TTF: http://www.libsdl.org/projects/SDL_ttf/
* SDL_Pango: http://sourceforge.net/projects/sdlpango/ (opcional)
* SDL_Mixer: http://www.libsdl.org/projects/SDL_mixer/ (opcional)
@ -120,54 +143,261 @@ Requisitos:
http://netpbm.sourceforge.net/
Compilación e instalación:
----------------------------------------------------------------------
Compiling and Installation
Tux Paint publícase baixo a Licenza Pública Xeral de GNU (GPL) (consulte
«COPYING.txt» para máis detalles) e, polo tanto, o «código fonte» do
programa está dispoñíbel libremente.
Usuarios de Windows:
Usuarios de Windows
Compilación:
25 de Outubro de 2020 Shin-ichi TOYAMA shin1@wmail.plala.or.jp
<shin1@wmail.plala.or.jp>
Compiling Set-Up
A partir de febreiro de 2005 (comezando con Tux Paint 0.9.15), o
«Makefile» inclúe compatibilidade para construír nun sistema Windows
usando MinGW/MSYS (http://www.mingw.org/).
usando MinGW/MSYS (https://sourceforge.net/projects/msys2/).
Após configurar o contorno e construír e instalar todas as
dependencias, use estas ordes en MSYS para construír, instalar e
executar:
Many tools and libraries are required to build Tux Paint. The
package management system "pacman" helps you install them
automatically solving complicated dependencies.
Antes da versión 0.9.20:
Download the latest MSYS2 environment from
https://sourceforge.net/projects/msys2/files/Base/ and install it
where you'd like (the default is "C:\msys64")
$ make win32
$ make install-win32
$ tuxpaint
Open the MSYS2 shell from the "Start Menu" -> "MSYS2 64bit" ->
"MSYS2 MSYS" and execute following command (press [Intro] or
[Retorno] to accept the defaults for all questions):
Versión 0.9.20 e posteriores:
pacman -Syu
$ make
$ make install
$ tuxpaint
This will update core system and the window will close
automatically. Repeat the steps above one more time to finish the
remaining update process.
Use a seguinte orde para crear unha versión axeitada para a
redistribución co instalador ou nun ficheiro zip:
Within the MSYS2 shell, run the following command to install basic
development tools:
pacman -S base-devel msys2-devel git
Proceed to the next "MinGW 64bit (x86_64) toolchains" section, or skip
to the "MinGW 32bit (i686) toolchains" section if you need only a
32bit build environment.
-------------------------------------------------------
MinGW 64bit (x86_64) toolchains
Within the MSYS2 shell, run the following command to install basic
64bit development tools:
pacman -S mingw-w64-x86_64-toolchain
64bit (x86_64) dependency libraries for Tux Paint
You can install tools and libraries required for compiling Tux Paint
on MSYS2/MINGW using "pacman" except for SDL_Pango.
"ntldd" is a small tool which examine windows executable files to
list Dynamic Link Library (.dll) files they depends on. Tux Paint's
packaging process for binary distribution uses it to find required
.dll files.
FLTK is a cross-platform GUI toolkit used by "Tux Paint Config.".
You can skip installing it if you are only building "Tux Paint".
$ pacman -S mingw-w64-x86_64-SDL_{image,mixer,ttf}
$ pacman -S mingw-w64-x86_64-librsvg
$ pacman -S mingw-w64-x86_64-fribidi
$ pacman -S mingw-w64-x86_64-libimagequant
$ pacman -S mingw-w64-x86_64-fltk
$ pacman -S mingw64/mingw-w64-x86_64-ntldd-git
Note: Close the shell before proceeding to the remaining process.
Install SDL_Pango and re-install SDL on the 64bit environment
SDL_Pango should be installed manually. In addition, you have to
re-install SDL from the source code or you will see unnecessary
blank window opens when starting Tux Paint.
This time, use the MinGW "64bit" shell. Open the shell from the
"Start Menu" -> "MSYS2 64bit" -> "MSYS2 MinGW 64-bit"
SDL_Pango
At first, you have to prepare source tar-ball and a required patch
in the same directory.
* Download source tar-ball of SDL_Pango-0.1.2 from SDL_Pango's
page on Sourceforge.net.
* Download a patch file from John Popplewell's "Tux Paint -
MinGW/MSYS build instructions" webpage. (This adds some extra
(required) functionality to SDL_Pango.)
Build and install SDL_Pango as follows.
$ tar zxvf SDL_Pango-0.1.2.tar.gz
$ cd SDL_Pango-0.1.2/
$ patch -p0 < ../SDL_Pango-configure-extra-api.patch
$ ./configure --prefix=/mingw64 && make && make install
SDL
Download source tar-ball of SDL_1.2.15 from libsdl.org.
Re-install SDL as follows.
$ tar zxvf SDL-1.2.15.tar.gz
$ cd SDL-1.2.15
$ ./configure --prefix=/mingw64 && make && make install
Proceed to the next "MinGW 32bit (i686) toolchains" section, or skip
to the "ImageMagick" section if you need only a 64bit build
environment.
-------------------------------------------------------
MinGW 32bit (i686) toolchains
Within the MSYS2 shell, run the following command to install basic
32bit development tools:
pacman -S mingw-w64-i686-toolchain
32bit (i686) dependency libraries for Tux Paint
You can install tools and libraries required for compiling Tux Paint
on MSYS2/MINGW using "pacman" except for SDL_Pango.
"ntldd" is a small tool which examine windows executable files to
list Dynamic Link Library (.dll) files they depends on. Tux Paint's
packaging process for binary distribution uses it to find required
.dll files.
FLTK is a cross-platform GUI toolkit used by "Tux Paint Config.".
You can skip installing it if you are only building "Tux Paint".
$ pacman -S mingw-w64-i686-SDL_{image,mixer,ttf}
$ pacman -S mingw-w64-i686-librsvg
$ pacman -S mingw-w64-i686-fribidi
$ pacman -S mingw-w64-i686-libimagequant
$ pacman -S mingw-w64-i686-fltk
$ pacman -S mingw-w64-i686-ntldd-git
Note: Close the shell before proceeding to the remaining process.
Install SDL_Pango and re-install SDL on the 32bit environment
SDL_Pango should be installed manually. In addition, you have to
re-install SDL from the source code or you will see unnecessary
blank window opens when starting Tux Paint.
This time, use the MinGW "32bit" shell. Open the shell from the
"Start Menu" -> "MSYS2 64bit" -> "MSYS2 MinGW 32-bit"
SDL_Pango
At first, you have to prepare source tar-ball and a required patch
in the same directory.
* Download source tar-ball of SDL_Pango-0.1.2 from SDL_Pango's
page on Sourceforge.net.
* Download a patch file from John Popplewell's "Tux Paint -
MinGW/MSYS build instructions" webpage. (This adds some extra
(required) functionality to SDL_Pango.)
Build and install SDL_Pango as follows.
$ tar zxvf SDL_Pango-0.1.2.tar.gz
$ cd SDL_Pango-0.1.2/
$ patch -p0 < ../SDL_Pango-configure-extra-api.patch
$ ./configure --prefix=/mingw32 && make && make install
SDL
Download source tar-ball of SDL_1.2.15 from libsdl.org.
Re-install SDL as follows.
$ tar zxvf SDL-1.2.15.tar.gz
$ cd SDL-1.2.15
$ ./configure --prefix=/mingw32 && make && make install
-------------------------------------------------------
ImageMagick
ImageMagick is a compilation of command line tools to create, edit,
compose, or convert bitmap images supporting quite a large number of
image formats. Tux Paint uses two functions ("convert" and
"composite") in it to generate thumbnails for startar images and
templates during the build process.
Using official binary release available from "Windows Binary
Release" is recommended, due to the commands installed with "pacman"
on MinGW/MSYS not working as expected!
Do not forget to enable "Install legacy utilities (e.g. convert)"
while installing it, because Tux Paint's build process uses them.
Add the path to the directory in which ImageMagick is installed at
the top of your "PATH" environment variable. For example:
$ export PATH=/c/Program\ Files/ImageMagick-7.0.10-Q16-HDRI:$PATH
You can make this permanent by adding the above to your the BASH
shell configuration file, "~/.bash_profile".
-------------------------------------------------------
Tux Paint
You can compile 64bit binaries using MSYS2 64bit shell, and 32bit
binaries using MSYS2 32bit shell, respectively.
* Select "MSYS2 64bit" -> "MSYS2 MinGW 64-bit" from the "Start
Menu" to open the 64bit shell.
* Select "MSYS2 64bit" -> "MSYS2 MinGW 32-bit" from the "Start
Menu" to open the 32bit shell.
Compile Tux Paint with the following command:
$ make bdist-win32
Ou se está a construír para Win9x/ME:
Note: At this point, you will want to build "Tux Paint Config." for
Windows, so it can be included along with "Tux Paint", if you're
making an official (or test) release. The build process will look
for it in a directory named "tuxpaint-config" (with no version
number, e.g., "tuxpaint-config-X.Y.Z"). See "Tux Paint Config."'s
INSTALL.txt documentation for details.
$ BDIST_WIN9X=1 make bdist-win32
All the files needed for starting Tux Paint (and Tux Paint Config.)
are collected in the directory for binary distribution "bdist"
directory under "win32". You can start them by double-clicking their
executable (.exe) files in the "bdist" directory.
Antes de que calquera dos anteriores funcione, cómpre configurar o
contorno e construír ou instalar as bibliotecas das que depende Tux
Paint. John Popplewell xuntou aquí algunhas instrucións para facelo:
-------------------------------------------------------
http://www.johnnypops.co.uk/tuxpaint/
Building the Tux Paint Windows Installer:
Lea as notas pertinentes se está a construír para Win9X/ME.
Inno Setup is used to build executable installer for Tux Paint.
Therefore you have to install it in the first place.
Executar o instalador:
Then, you can easily build an executable installer by right-clicking
on the "tuxpaint.iss" icon in the "win32" directory and selecting
"Compile" on the list. It will run for a while, and eventually you
will find a "tuxpaint-X.Y.Z-win32-installer.exe" file in the same
directory.
-------------------------------------------------------
Running the Tux Paint Windows Installer:
Faga dobre clic no executábel do instalador de Tux Paint (ficheiro
.EXE) e siga as instrucións.
@ -186,6 +416,8 @@ Compilación e instalación:
Neste punto, pode premer en «Instalar» para instalar Tux Paint.
-------------------------------------------------------
Cambiar os axustes usando o acceso directo:
Para cambiar os axustes do programa, prema co botón dereito no
@ -214,6 +446,8 @@ Compilación e instalación:
Cando teña rematado, prema en «Aceptar».
-------------------------------------------------------
Se algo vai mal:
Se ao facer dobre clic no atallo para executar Tux Paint, non ocorre
@ -225,7 +459,9 @@ Compilación e instalación:
maiúsculas e minúsculas incorrectas (maiúsculas «Z» no canto de
minúsculas «z») ou a falta (ou exceso) de «-» (guións).
Usuarios de Linux/Unix:
----------------------------------------------------------------------
Usuarios de Linux/Unix
Compilación:
@ -239,6 +475,8 @@ Compilación e instalación:
$ make
-------------------------------------------------------
Desactivar a compatibilidade de «SVG» (e, polo tanto, as dependencias de
«Cairo, libSVG, e svg-cairo»:
@ -249,6 +487,8 @@ Compilación e instalación:
$ make SVG_LIB= SVG_CFLAGS=
-------------------------------------------------------
Desactivar a compatibilidade de «Pango» (e, polo tanto, as dependencias de
«Pango, Cairo, etc.»:
@ -260,6 +500,8 @@ Compilación e instalación:
$ make SDL_PANGO_LIB=
-------------------------------------------------------
Desactivación do son en tempo de compilación:
Se non te unha tarxeta de son ou prefire construír o programa sen
@ -268,11 +510,15 @@ Compilación e instalación:
$ make SDL_MIXER_LIB=
-------------------------------------------------------
Outras opcións:
Outras opcións (p. ex.: rutas de instalación) poden ser anuladas;
véxaas en «Makefile» para máis detalles.
-------------------------------------------------------
Se se producen erros:
Se recibe algún erro durante o tempo de compilación, asegúrese de
@ -282,6 +528,8 @@ Compilación e instalación:
correspondentes paquetes «-dev» ou «-devel», se non, non poderá
compilar Tux Paint (e outros programas) dende o código fonte.
-------------------------------------------------------
Instalar:
Supoñendo que non se produciron erros graves, agora pode instalar o
@ -360,13 +608,150 @@ Compilación e instalación:
Nota: Esta lista non está actualizada. Consulte «Makefile» e
«Makefile-i18n» para ver unha lista completa.
Depuración:
----------------------------------------------------------------------
A depuración (a «STDOUT», por exemplo, á terminal ou a un ficheiro
«stdout.txt» en Windows) pódese activar co axuste «DEBUG» (e, se se
quere un rexistro detallado, «VERBOSE») #define en «src/debug.h».
Usuarios de macOS
Desinstalación de Tux Paint:
21 de Setembro de 2021 Mark K. Kim <markuskimius@gmail.com>
Tux Paint 0.9.22 and earlier required building Tux Paint from the
Xcode IDE. Starting with 0.9.23, however, Tux Paint for macOS is built
as though it were a Linux application.
Prerequisites
Although Tux Paint is built without the Xcode IDE, Xcode itself is
still required to build Tux Paint. Download it from the App Store,
and launch it once to accept its license agreements. You may also
need to install the Xcode command line tools using the command:
xcode-select --install
Building Tux Paint also requires various libraries. We install them
from MacPorts where possible, source code otherwise. Install
MacPorts to the default /opt/local path according to the
instructions found on their website: https://www.macports.org/
* ImageMagick
* cairo
* fribidi
* lbzip2
* libimagequant^*
* libpaper
* libpng
* librsvg
* libsdl
* libsdl_image
* libsdl_mixer
* libsdl_pango
* libsdl_ttf
* pkgconfig
* zlib
... but you should install any package that is required by the
latest version of Tux Paint.
^* Not available from MacPorts as of this writing, see below.
libimagequant
libimagequant is not available from MacPorts as of this writing.
It can be installed from the source code as follows. It should be
installed to /opt/local (same as MacPorts) for the library to be
included in TuxPaint.dmg.
$ git clone https://github.com/ImageOptim/libimagequant.git
$ cd libimagequant
$ ./configure --prefix=/opt/local
$ make
$ sudo make install
WARNING: Having any UNIX-like toolset installed on your Mac besides
MacPorts and Xcode, such as Fink or Brew, will prevent your app
bundle from being portable. Be sure Fink and Brew are not accessible
from your build environment.
-------------------------------------------------------
How to Build
Simply, run:
% make
% make install
... to create the TuxPaint.app application bundle that can be run
in-place or copied to /Applications. It also creates TuxPaint.dmg
for distribution.
-------------------------------------------------------
Known Issues
* A macOS binary built on a specific version of macOS only runs on
that version of macOS or later. To ensure Tux Paint can run on
the oldest version of macOS possible, build it on the oldest
version of macOS available. As of this writing we know Tux Paint
cannot be built to run on macOS 10.7 or earlier.
See "Old Versions of macOS" below for best-effort instructions
on how to obtain, install, and build Tux Paint on an old version
of macOS.
-------------------------------------------------------
Old Versions of macOS
Some old versions of macOS can be downloaded from Apple's support
page: https://support.apple.com/en-us/HT211683
macOS does allow dual booting of multiple versions of the OS, but
it's safer and easier to install the old macOS onto a flash drive.
Wherever you're installing it, the target drive's partitioniong
scheme and partition type must match what the old macOS expects, so
use the Disk Utility to partition and format the flash drive
accordingly.
As of this writing, the oldest version of macOS available on Apple's
support site is Yosemite 10.10, which expects "GPT (GUID Partition
Table)" partitioning scheme instead of the older MBR scheme, and
"Mac OS Extended (Journaled)" as the partition type instead of the
newer APFS partition type.
Upon launching the installer, if you get a popup about macOS being
too old or new to be installed, a bootable installer can be created
using the instructions found here:
https://support.apple.com/en-mide/HT201372
It has been found that macOS can be installed onto the bootable
media itself, so you can make the flash drive into a bootable
installer then install the old macOS onto the same flash drive.
Once the old macOS is installed, you may find the Xcode on the App
Store is too new to run on the version of the old macOS. Old
versions of Xcode can be downloaded from Apple's Developer site in
an area accessible with free registration:
https://developer.apple.com/download/more/
The list of macOS versions and the last version of Xcode compatible
with them are laid out nicely on the Wikipedia page on Xcode:
https://en.wikipedia.org/wiki/Xcode#Version_comparison_table
And because Xcode is being installed manually, you can skip the step
to install the Xcode command line tools (do not run "xcode-select
--install") but otherwise build Tux Paint using the same steps
described in the earlier part of this document.
----------------------------------------------------------------------
Debugging
Debugging output — to "STDOUT" on Linux and Unix, to a "stdout.txt" file
on Windows, and to the file "/tmp/tuxpaint.log" on macOS — can be
enabled by setting "DEBUG" (and, if verbose logging is wanted,
"VERBOSE") #defines in "src/debug.h" and (re)compiling Tux Paint.
----------------------------------------------------------------------
Uninstalling Tux Paint
Windows
@ -385,12 +770,24 @@ Desinstalación de Tux Paint:
Tamén é posíbel usar a entrada «TuxPaint (só eliminar)« na sección
Engadir/Eliminar programas do Panel de control.
----------------------------------------------------------------------
macOS
Delete "TuxPaint.app" from the "Applications" folder. Data files,
including the configuration files, stamps, and saved pictures, may be
found in "Library/Application Support/TuxPaint" (all users) and
"/Users/USERNAME/Library/Application Support/TuxPaint" (individual
users).
----------------------------------------------------------------------
Linux
Dentro do directorio de orixe de Tux Paint (onde compilou Tux Paint),
pode usar o destino «make uninstall» para desinstalar Tux Paint. De
xeito predeterminado, debe facelo o usuario «root» («superusuario»),
mais se instalou Tux Paint noutro lugar (por exemplo, usando a
configuración «PREFIX=...» en «make» e «make install»), pode que non e
queira proporcionar a mesma configuración aquí. (Consulte as
instrucións de instalación anteriores para obter máis información.)
Within the Tux Paint source directory (where you compiled Tux Paint),
you can use the "make uninstall" target to uninstall Tux Paint. By
default, this must be done by the "root" user ('superuser'), but if
you installed Tux Paint somewhere else (e.g., using a "PREFIX=..."
setting to "make" and "make install"), you may not, and will want to
provide those same settings here. (See the installation instructions
above for further information.)

2020
docs/gl_ES.UTF-8/OPTIONS.txt
View file

File diff suppressed because it is too large Load diff

2
docs/gl_ES.UTF-8/PNG.txt
View file

@ -1,5 +1,5 @@
Tux Paint
versión 0.9.26
versión 0.9.27
Documentación PNG
Copyright © 2007-2021 por varios colaboradores; vexa AUTHORS (AUTORES).

30
docs/gl_ES.UTF-8/README.txt
View file

@ -1,12 +1,12 @@
Tux Paint
versión 0.9.26
versión 0.9.27
Un sinxelo programa de debuxo para cativos
Copyright © 2002-2021 por varios colaboradores; vexa AUTHORS (AUTORES).
http://www.tuxpaint.org/
28 de Xuño de 2021
5 de Setembro de 2021
----------------------------------------------------------------------
@ -226,6 +226,22 @@ Ferramentas dispoñíbeis
Se mantén premido o botón do rato e move o rato, irá
debuxando a medida que se move.
Some brushes are animated — they change their shape as you
draw them. A good example of this is the vines brush that
ships with Tux Paint. These brushes will have a small
"filmstrip" icon drawn on their Selector buttons.
Other brushes are directional — they will draw a different
shape depending on what direction you are painting with
them. An example of this is the arrow brush that ships with
Tux Paint. These brushes have a small 8-way arrow icon drawn
on their Selector buttons.
Finally, some brushes can be both direction and animated.
Examples of this are the cat and squirrel brushes that ship
with Tux Paint. These brushes will have both the "filmstrip"
and 8-way arrow icons.
Mentres debuxa, soa un son. Canto maior sexa o pincel, menor
será o ton.
@ -287,6 +303,12 @@ Ferramentas dispoñíbeis
Solte o rato para completar a liña. Soará un «chimpo».
Some brushes are animated, and will show a pattern of shapes
along the line. Others are directional, and will show a
different shape depending on the angle of the brush. And
finally some are both animated and directional. See "Paint",
above, to learn more.
----------------------------------------------------------------------
Ferramenta «Formas»
@ -348,8 +370,8 @@ Ferramentas dispoñíbeis
inferior). prema na pantalla e aparecerá un cursor. Escriba
un texto e aparecerá na pantalla.
Prema [Enter] ou [Return] e o texto será debuxado na imaxe e
o cursor moverase cara abaixo unha liña.
Prema [Intro] ou [Retorno] e o texto será debuxado na imaxe
e o cursor moverase cara abaixo unha liña.
Como alternativa, prema [Tab] e o texto será debuxado na
imaxe, mais o cursor moverase á dereita do texto, no canto

2
docs/gl_ES.UTF-8/SIGNALS.txt
View file

@ -1,5 +1,5 @@
Tux Paint
versión 0.9.26
versión 0.9.27
Documentación de sinais
Copyright © 2019-2021 por varios colaboradores; vexa AUTHORS (AUTORES).

2
docs/gl_ES.UTF-8/SVG.txt
View file

@ -1,5 +1,5 @@
Tux Paint
versión 0.9.26
versión 0.9.27
Documentación SVG
Copyright © 2007-2021 por varios colaboradores; vexa AUTHORS (AUTORES).

81
docs/gl_ES.UTF-8/html/ADVANCED-STAMPS-HOWTO.html
View file

@ -17,16 +17,62 @@
width="205"
height="210"
alt="Tux Paint"><br>
versión 0.9.26 «Como facer» os selos avanzados </h1>
versión 0.9.27 «Como facer» os selos avanzados </h1>
<p>
Copyright &copy; 2006-2021 por Albert Cahalan e outros; vexa AUTHORS (AUTORES).<br>
<a href="http://www.tuxpaint.org/">http://www.tuxpaint.org/</a>
</p>
<p>
29 de Agosto de 2021 </p>
</center>
<hr size="2"
noshade>
<table border="2"
cellspacing="0"
cellpadding="2"
summary="Índice">
<tr>
<th>
Índice </th>
</tr>
<tr>
<td>
<ul>
<li>
<a href="#about">Sobre este «Como facelo»</a>
</li>
<li>
<a href="#choice">A elección da imaxe é crucial</a>
</li>
<li>
<a href="#prepare_mask">Preparar a máscara</a>
</li>
<li>
<a href="#replace_fringe">Substituír a franxa e os píxeles lixo</a>
</li>
<li>
<a href="#save">Gardar a imaxe para Tux Paint</a>
</li>
</ul>
</td>
</tr>
</table>
<hr size="2"
noshade>
<hr size="2"
noshade>
<h2>
Sobre este «Como facelo» </h2>
<a name="about" id="about">
Sobre este «Como facelo» </a>
</h2>
<blockquote>
<p>
@ -36,8 +82,13 @@
Este «Como facelo» supón que está a tratar con obxectos opacos normais. O tratamento de obxectos semitransparentes (lume, ventilador en movemento, globo infantil) ou obxectos que dan luz (lume, bombilla, sol) faise mellor cun software personalizado. As imaxes con fondos de cor sólida perfectos tamén se fan mellor con software personalizado, pero non son difíciles de facer do seguinte xeito. </p>
</blockquote>
<hr size="2"
noshade>
<h2>
A elección da imaxe é crucial </h2>
<a name="choice" id="choice">
A elección da imaxe é crucial </a>
</h2>
<blockquote>
<h3>
@ -78,6 +129,9 @@
</blockquote>
</blockquote>
<hr size="2"
noshade>
<h2>
Preparar a imaxe </h2>
@ -116,8 +170,13 @@
<b>Advertencia:</b> unha vez que teña a máscara, non pode rotar nin escalar a imaxe normalmente. Isto provocaría a perda de datos. Máis adiante se lle darán instrucións especiais de escalado. </p>
</blockquote>
<hr size="2"
noshade>
<h2>
Preparar a máscara </h2>
<a name="prepare_mask" id="prepare_mask">
Preparar a máscara </a>
</h2>
<blockquote>
<p>
@ -151,8 +210,13 @@
Ver e editar a máscara. Seleccione por cor, escollendo negro ou branco. O máis probábel é que vexa pintas non seleccionadas que non son da cor agardada. Inverta a selección e logo pínteas coa ferramenta de lapis. Faga esta operación tanto para branco como para negro. </p>
</blockquote>
<hr size="2"
noshade>
<h2>
Substituír a franxa e os píxeles lixo </h2>
<a name="replace_fringe" id="replace_fringe">
Substituír a franxa e os píxeles lixo </a>
</h2>
<blockquote>
<p>
@ -188,8 +252,13 @@
Tux Paint pode reducir a escala das imaxes nun factor moi grande, polo que é importante estender moito o bordo do obxecto cara a fóra. Xusto no bordo do obxecto, debe ser moi preciso respecto diso. A medida que se afasta do o, pode ser un pouco desleixado. É razoábel pintar cara a fóra unha ducia de píxeles ou máis. Canto máis lonxe vaia, máis pode Tux Paint reducir sen crear franxas de cor feas. Para as áreas que están a máis duns poucos píxeles de distancia do bordo do obxecto, debería empregar a ferramenta de lapis (ou seleccionar arrastrar e soltar cor) para garantir que o resultado se comprime ben. </p>
</blockquote>
<hr size="2"
noshade>
<h2>
Gardar a imaxe para Tux Paint </h2>
<a name="save" id="save">
Gardar a imaxe para Tux Paint </a>
</h2>
<blockquote>
<p>

12
docs/gl_ES.UTF-8/html/ENVVARS.html
View file

@ -17,7 +17,7 @@
width="205"
height="210"
alt="Tux Paint"><br>
versión 0.9.26<br/>
versión 0.9.27<br/>
Documentación de variábeis de contorno </h1>
<p>
@ -26,7 +26,7 @@
</p>
<p>
11 de Maio de 2021 </p>
8 de Agosto de 2021 </p>
</center>
<hr>
@ -61,7 +61,7 @@
<dd>
<p>
En Linux e noutras plataformas onde se usan os estándares X Desktop Group, a localización dos ficheiros de configuración do usuario. Especificamente, onde atopar «<code>user-dirs.dirs</code>», onde se podería definir o «<code>XDG_PICTURES_DIR</code>». Úsase para exportar debuxos e GIF animados. Xeralmente estabelecese en algo así como «<code>$HOME/Pictures/</code>». Se non se especifica, Tux Paint comproba no directorio «<code>$HOME/.config/</code>». Se non se pode atopar a configuración, Tux Paint simplemente exporta debuxos e GIF a «<code>$HOME</code>». </p>
On Linux and other platforms where the X Desktop Group standards are used, the location of the user's configuration files. Specifically, where to find "<code>user-dirs.dirs</code>", where the "<code>XDG_PICTURES_DIR</code>" might be defined. It is used for exporting drawings and animated GIFs. Generally it's set to something like "<code>$HOME/Pictures/</code>". If not specified, Tux Paint checks in the directory "<code>$HOME/.config/</code>". If the configuration cannot be found, Tux Paint simply exports drawings and GIFs to "<code>$HOME</code>". </p>
</dd>
<dt>
@ -70,7 +70,7 @@
<dd>
<p>
En Linux e noutras plataformas onde se usan os estándares X Desktop Group, a localización dos directorios de datos do usuario. En concreto, onde atopar o directorio «<code>Trash</code>». Úsase cando se eliminan imaxes do diálogo «Abrir» de Tux Paint. Se non se define, úsase a localización «<code>$HOME/.local/share/Trash/</code>», se está dispoñíbel. Se non, as imaxes bórranse simplemente no canto de movelas a calquera outro lugar. </p>
On Linux and other platforms where the X Desktop Group standards are used, the location of the user's data directories. Specifically, where to find the "<code>Trash</code>" directory. It is used when deleting images from Tux Paint's "Open" dialog. If not set, the location "<code>$HOME/.local/share/Trash/</code>" is used, if available. If not, images are simply deleted, rather than moved anywhere. </p>
</dd>
<dt>
@ -101,7 +101,7 @@
<dd>
<p>
Especifica o idioma que debe empregar Tux Paint na súa interface de usuario. Anulada polas opcións da liña de ordes «<code>--lang</code>» e «<code>--locale</code>» ou as súas equivalentes do ficheiro de configuración. Utilízase a variábel de contorno '<code>LANGUAGE</code>', se está definida. Se non, «<code>LC_ALL</code>» úsase como alternativa. Após «<code>LC_MESSAGES</code>» e, finalmente, «<code>LANG</code>». </p>
Specify the language Tux Paint should utilize in its user interface. Overridde by the "<code>--lang</code>" and "<code>--locale</code>" command-line options or their configuration file counterparts. The "<code>LANGUAGE</code>" environment variable is used, if set. If not, "<code>LC_ALL</code>" is used as a fallback. Then "<code>LC_MESSAGES</code>", and finally "<code>LANG</code>". </p>
</dd>
</dl>
@ -124,7 +124,7 @@
</dt>
<dd>
<p>
Solicita onde colocar a xanela de Tux Paint. Normalmente estabelécese en «<code>center</code>» polo propio Tux Paint, a menos que a variábel de contorno xa estea estabelecida (por exemplo, en «<code>nopref</code>», que significa «sen preferencia»). </p>
Requests where to position Tux Paint's window. Normally set to "<code>center</code>" by Tux Paint itself, unless the environment variable is already set (e.g., to "<code>nopref</code>", meaning "no preference"). </p>
</dd>
</dl>

21
docs/gl_ES.UTF-8/html/EXTENDING.html
View file

@ -18,7 +18,7 @@
width="205"
height="210"
alt="Tux Paint"><br>
versión 0.9.26 </h1>
versión 0.9.27 </h1>
<p>
Copyright &copy; 2002-2021 por varios colaboradores; vexa AUTHORS (AUTORES).<br>
@ -26,7 +26,7 @@
</p>
<p>
31 de Maio de 2021 </p>
6 de Setembro de 2021 </p>
</center>
<hr size="2"
@ -367,14 +367,25 @@
</blockquote>
<h4>
Pinceis direccionais animados </h4>
Rotating Brushes </h4>
<blockquote>
<p>
Pode mesturar funcións animadas e direccionais nun pincel. Use ambas as opcións («<code><b>frames=<i>N</i></b></code>» e «<code><b>directional</b></code>»), en liñas separadas no ficheiro «<code>.dat</code>» do pincel. </p>
As of Tux Paint version 0.9.27, you may now create rotating brushes. As the brush is used, it is rotated 360 degrees, depending on the direction the brush is going. </p>
<p>
Coloque o pincel de xeito que cada conxunto de formas 3x3 de dirección estea distribuído nunha ampla imaxe PNG. Por exemplo, se o pincel ten 30x30 e hai 5 fotogramas, sería de 450x90. (Os píxeles máis a esquerda de 150x90 da imaxe representan as 9 formas de dirección do primeiro cadro, por exemplo). </p>
Engada unha liña que conteña a palabra «<code><b>rotate</b></code>» ao ficheiro de datos debrush's. </p>
</blockquote>
<h4>
Animated Directional or Rotating Brushes </h4>
<blockquote>
<p>
You may mix both animated and either directional or rotating features into one brush. Use both options desired ("<code><b>frames=<i>N</i></b></code>" and "<code><b>directional</b></code>" or "<code><b>rotate</b></code>"), in separate lines in the brush's "<code>.dat</code>" file. </p>
<p>
For directional brushes, lay the brush out so that each 3x3 set of directional shapes are laid out across a wide PNG image. For example, if the brush is 30x30 and there are 5 frames, it would be 450x90. (The leftmost 150x90 pixels of the image represent the 9 direction shapes for the first frame, for example.) </p>
</blockquote>
</blockquote>

104
docs/gl_ES.UTF-8/html/FAQ.html
View file

@ -17,7 +17,7 @@
width="205"
height="210"
alt="Tux Paint"><br>
versión 0.9.26 Preguntas máis frecuentes </h1>
versión 0.9.27 Preguntas máis frecuentes </h1>
<p>
Copyright &copy; 2002-2021 por varios colaboradores; vexa AUTHORS (AUTORES).<br>
@ -25,13 +25,60 @@
</p>
<p>
2 de Xuño de 2021 </p>
29 de Agosto de 2021 </p>
</center>
<hr>
<hr size="2"
noshade>
<table border="2"
cellspacing="0"
cellpadding="2"
summary="Índice">
<tr>
<th>
Índice </th>
</tr>
<tr>
<td>
<ul>
<li>
<a href="#drawing">Relacionado co debuxo</a>
</li>
<li>
<a href="#interface">Problemas de interface</a>
</li>
<li>
<a href="#printing">Impresión</a>
</li>
<li>
<a href="#saving">Gardar</a>
</li>
<li>
<a href="#audio">Problemas de son</a>
</li>
<li>
<a href="#fullscreen">Problemas no modo de pantalla completa</a>
</li>
<li>
<a href="#other">Outros problemas</a>
</li>
<li>
<a href="#contact">Axuda / Contacto</a>
</li>
</ul>
</td>
</tr>
</table>
<hr size="2"
noshade>
<h2>
Relacionado co debuxo </h2>
<a name="drawing" id="drawing">
Relacionado co debuxo </a>
</h2>
<dl>
<dt>
@ -101,10 +148,13 @@
</dd>
</dl>
<hr>
<hr size="2"
noshade>
<h2>
Problemas de interface </h2>
<a name="interface" id="interface">
Problemas de interface </a>
</h2>
<dl>
<dt>
@ -212,10 +262,13 @@
</dd>
</dl>
<hr>
<hr size="2"
noshade>
<h2>
Impresión </h2>
<a name="printing" id="printing">
Impresión </a>
</h2>
<dl>
<dt>
@ -282,10 +335,13 @@
</dd>
</dl>
<hr>
<hr size="2"
noshade>
<h2>
Gardar </h2>
<a name="saving" id="saving">
Gardar </a>
</h2>
<dl>
<dt>
@ -382,10 +438,13 @@
</dd>
</dl>
<hr>
<hr size="2"
noshade>
<h2>
Problemas de son </h2>
<a name="audio" id="audio">
Problemas de son </a>
</h2>
<dl>
<dt>
@ -507,10 +566,13 @@
</dd>
</dl>
<hr>
<hr size="2"
noshade>
<h2>
Problemas no modo de pantalla completa </h2>
<a name="fullscreen" id="fullscreen">
Problemas no modo de pantalla completa </a>
</h2>
<dl>
<dt>
@ -569,10 +631,13 @@
</dd>
</dl>
<hr>
<hr size="2"
noshade>
<h2>
Outros problemas </h2>
<a name="other" id="other">
Outros problemas </a>
</h2>
<dl>
<dt>
@ -744,10 +809,13 @@
</dd>
</dl>
<hr>
<hr size="2"
noshade>
<h2>
Axuda / Contacto </h2>
<a name="contact" id="contact">
Axuda / Contacto </a>
</h2>
<p>
Hai algunha pregunta que non ve respondida? Agradecémoslle que nolo diga. Para elo, pode subscribirse e publicar na nosa lista de correo «tuxpaint-users»: </p>

625
docs/gl_ES.UTF-8/html/INSTALL.html
View file

@ -17,7 +17,7 @@
width="205"
height="210"
alt="Tux Paint"><br>
versión 0.9.26<br/>
versión 0.9.27<br/>
Documentación da instalación </h1>
<p>
@ -26,21 +26,88 @@
</p>
<p>
9 de Marzo de 2021 </p>
5 de Setembro de 2021 </p>
</center>
<hr>
<hr size="2" noshade />
<h2>Requisitos:</h2>
<table border="2"
cellspacing="0"
cellpadding="2"
summary="Índice">
<tr>
<th>
Índice </th>
</tr>
<tr>
<td>
<ul>
<li>
<a href="#requirements">Requirements</a>
<ul>
<li>
<a href="#req-libsdl">Simple DirectMedia Layer library (libSDL)</a>
</li>
<li>
<a href="#req-other-libs">Outras bibliotecas</a>
</li>
</ul>
</li>
<li>
<a href="#compiling">Compiling and Installation</a>
<ul>
<li>
<a href="#compiling-windows">Usuarios de Windows</a>
</li>
<li>
<a href="#compiling-linux">Usuarios de Linux/Unix</a>
</li>
<li>
<a href="#compiling-macos">Usuarios de macOS</a>
</li>
</ul>
</li>
<li>
<a href="#debugging">Debugging</a>
</li>
<li>
<a href="#uninstalling">Uninstalling Tux Paint</a>
<ul>
<li>
<a href="#uninstalling-windows">Windows</a>
</li>
<li>
<a href="#uninstalling-macOS">macOS</a>
</li>
<li>
<a href="#uninstalling-linux">Linux</a>
</li>
</ul>
</li>
</ul>
</td>
</tr>
</table>
<hr size="2" noshade />
<h2>
<a name="requirements" id="requirements">
Requirements </a>
</h2>
<blockquote>
<h3>libSDL</h3>
<h3>
<a name="req-libsdl" id="req-libsdl">
Simple DirectMedia Layer library (libSDL) </a>
</h3>
<blockquote>
<p>
Tux Paint require a «Simple DirectMedia Layer Library (libSDL)», unha biblioteca de programación multimedia de código aberto dispoñíbel baixo a licenza pública GNU Lesser General Public License (LGPL). </p>
<p>
Xunto con libSDL, Tux Paint depende doutras bibliotecas «de axuda» de SDL: SDL_Image (para ficheiros gráficos), SDL_TTF e (opcionalmente) SDL_Pango (para compatibilidade de tipo True Type) e, opcionalmente, SDL_Mixer (para efectos de son). </p>
Along with libSDL, Tux Paint depends on a number of other SDL 'helper' libraries: SDL_Image (for graphics files), SDL_gfx (for some graphical functions, like rotation), SDL_TTF and (optionally) SDL_Pango (for True Type Font support) and, optionally, SDL_Mixer (for sound effects). </p>
<h4>Usuarios de Linux/Unix:</h4>
<blockquote>
@ -49,6 +116,7 @@
<ul>
<li>libSDL: <a href="http://www.libsdl.org/">http://www.libsdl.org/</a></li>
<li>SDL_Image: <a href="http://www.libsdl.org/projects/SDL_image/">http://www.libsdl.org/projects/SDL_image/</a></li>
<li>SDL_gfx: <a href="https://www.ferzkopp.net/wordpress/2016/01/02/sdl_gfx-sdl2_gfx/">https://www.ferzkopp.net/wordpress/2016/01/02/sdl_gfx-sdl2_gfx/</a> (<a href="https://sourceforge.net/projects/sdlgfx/">https://sourceforge.net/projects/sdlgfx/</a>)</li>
<li>SDL_TTF: <a href="http://www.libsdl.org/projects/SDL_ttf/">http://www.libsdl.org/projects/SDL_ttf/</a></li>
<li>SDL_Pango: <a href="http://sourceforge.net/projects/sdlpango/">http://sourceforge.net/projects/sdlpango/</a> (opcional)</li>
<li>SDL_Mixer: <a href="http://www.libsdl.org/projects/SDL_mixer/">http://www.libsdl.org/projects/SDL_mixer/</a> (opcional)</li>
@ -62,7 +130,10 @@
</blockquote>
</blockquote>
<h3>Outras bibliotecas</h3>
<h3>
<a name="req-other-libs" id="req-other-libs">
Outras bibliotecas </a>
</h3>
<blockquote>
<p>
Tux Paint tamén aproveita outras bibliotecas libres con licenza LGPL. En Linux, do mesmo xeito que SDL, deberían estar xa instaladas ou estar dispoñíbeis para a súa instalación como parte da súa distribución de Linux. </p>
@ -110,7 +181,7 @@
<h4>Compatibilidade de SVG</h4>
<blockquote>
<p>
A partir de Tux Paint 0.9.17, Tux Paint pode cargar imaxes SVG (Scalable Vector Graphics — Gráficos Vectoriais Escalábeis) como selos. Admítense dous conxuntos de bibliotecas e pódese desactivar completamente a compatibilidade SVG (a través de «<code>make SVG_LIB:=</code>») </p>
A partir de Tux Paint 0.9.17, Tux Paint pode cargar imaxes SVG (Scalable Vector Graphics — Gráficos Vectoriais Escalábeis) como selos. Admítense dous conxuntos de bibliotecas e pódese desactivar completamente a compatibilidade SVG (a través de «<code style="white-space: nowrap;">make SVG_LIB:=</code>») </p>
<h5>librsvg-2 &amp; libCairo2 (bibliotecas máis recentes)</h5>
<ul>
@ -155,66 +226,322 @@
</blockquote>
</blockquote>
<h2>Compilación e instalación:</h2>
<hr size="2" noshade />
<h2>
<a name="compiling" id="compiling">
Compiling and Installation </a>
</h2>
<blockquote>
<p>
Tux Paint publícase baixo a Licenza Pública Xeral de GNU (GPL) (consulte «COPYING.txt» para máis detalles) e, polo tanto, o «código fonte» do programa está dispoñíbel libremente. </p>
<h3>Usuarios de Windows:</h3>
<h3>
<a name="compiling-windows" id="compiling-windows">
Usuarios de Windows </a>
</h3>
<p style="font-size: small;">
<em>
25 de Outubro de 2020 Shin-ichi TOYAMA shin1@wmail.plala.or.jp &lt;<a href="mailto:shin1@wmail.plala.or.jp">shin1@wmail.plala.or.jp</a>&gt;
</em>
</p>
<blockquote>
<h4>Compilación:</h4>
<h4>Compiling Set-Up</h4>
<blockquote>
<p>
A partir de febreiro de 2005 (comezando con Tux Paint 0.9.15), o «<code>Makefile</code>» inclúe compatibilidade para construír nun sistema Windows usando MinGW/MSYS (<a href="http://www.mingw.org/">http://www.mingw.org/</a>). </p>
A partir de febreiro de 2005 (comezando con Tux Paint 0.9.15), o «<code>Makefile</code>» inclúe compatibilidade para construír nun sistema Windows usando MinGW/MSYS (<a href="https://sourceforge.net/projects/msys2/">https://sourceforge.net/projects/msys2/</a>). </p>
<p>
Após configurar o contorno e construír e instalar todas as dependencias, use estas ordes en MSYS para construír, instalar e executar: </p>
<h5>Antes da versión 0.9.20:</h5>
<blockquote>
<code>
$ make win32<br/>
$ make install-win32<br/>
$ tuxpaint
</code>
</blockquote>
<h5>Versión 0.9.20 e posteriores:</h5>
<blockquote>
<code>
$ make<br/>
$ make install<br/>
$ tuxpaint
</code>
</blockquote>
Many tools and libraries are required to build Tux Paint. The package management system "<code>pacman</code>" helps you install them automatically solving complicated dependencies. </p>
<p>
Use a seguinte orde para crear unha versión axeitada para a redistribución co instalador ou nun ficheiro zip: </p>
<blockquote>
<code>
$ make bdist-win32
</code>
</blockquote>
Download the latest MSYS2 environment from <a href="https://sourceforge.net/projects/msys2/files/Base/">https://sourceforge.net/projects/msys2/files/Base/</a> and install it where you'd like (the default is "<code>C:\msys64</code>") </p>
<p>
Ou se está a construír para Win9x/ME: </p>
<blockquote>
<code>
$ BDIST_WIN9X=1 make bdist-win32
</code>
</blockquote>
<p>
Antes de que calquera dos anteriores funcione, cómpre configurar o contorno e construír ou instalar as bibliotecas das que depende Tux Paint. John Popplewell xuntou aquí algunhas instrucións para facelo: </p>
<p>
<a href="http://www.johnnypops.co.uk/tuxpaint/">http://www.johnnypops.co.uk/tuxpaint/</a>
Open the MSYS2 shell from the "Start Menu" -&gt; "MSYS2 64bit" -&gt; "MSYS2 MSYS" and execute following command (press <b><code>[Intro]</code></b> or <b><code>[Retorno]</code></b> to accept the defaults for all questions):
<blockquote>
<code>
pacman -Syu
</code>
</blockquote>
</p>
<p>
Lea as notas pertinentes se está a construír para Win9X/ME. </p>
This will update core system and the window will close automatically. Repeat the steps above one more time to finish the remaining update process. </p>
<p>
Within the MSYS2 shell, run the following command to install basic development tools: <blockquote>
<code>
pacman -S base-devel msys2-devel git
</code>
</blockquote>
</p>
</blockquote>
<h4>Executar o instalador:</h4>
<p>
<i>
Proceed to the next "<a href="#64bit">MinGW 64bit (x86_64) toolchains</a>" section, or skip to the "<a href="#32bit">MinGW 32bit (i686) toolchains</a>" section if you need only a 32bit build environment. </i>
</p>
<hr size="1" noshade width="75%" />
<h4>
<a name="64bit" id="64bit">
MinGW 64bit (x86_64) toolchains </a>
</h4>
<blockquote>
<p>
Within the MSYS2 shell, run the following command to install basic 64bit development tools: <blockquote>
<code>
pacman -S mingw-w64-x86_64-toolchain
</code>
</blockquote>
</p>
</blockquote>
<h4>
64bit (x86_64) dependency libraries for Tux Paint </h4>
<blockquote>
<p>
You can install tools and libraries required for compiling Tux Paint on MSYS2/MINGW using "<code>pacman</code>" except for SDL_Pango. </p>
<p>
"<code>ntldd</code>" is a small tool which examine windows executable files to list Dynamic Link Library (<code>.dll</code>) files they depends on. Tux Paint's packaging process for binary distribution uses it to find required <code>.dll</code> files. </p>
<p>
FLTK is a cross-platform GUI toolkit used by "Tux Paint Config.". You can skip installing it if you are <em>only</em> building "Tux Paint". </p>
<p>
<blockquote>
<code>
$ pacman -S mingw-w64-x86_64-SDL_{image,mixer,ttf}<br/>
$ pacman -S mingw-w64-x86_64-librsvg<br/>
$ pacman -S mingw-w64-x86_64-fribidi<br/>
$ pacman -S mingw-w64-x86_64-libimagequant<br/>
$ pacman -S mingw-w64-x86_64-fltk<br/>
$ pacman -S mingw64/mingw-w64-x86_64-ntldd-git
</code>
</blockquote>
</p>
<p>
<strong>Note:</strong> Close the shell before proceeding to the remaining process. </p>
</blockquote>
<h4>
Install SDL_Pango and re-install SDL on the 64bit environment </h4>
<blockquote>
<p>
SDL_Pango should be installed manually. In addition, you have to re-install SDL from the source code or you will see unnecessary blank window opens when starting Tux Paint. </p>
<p>
This time, use the MinGW "64bit" shell. Open the shell from the "Start Menu" -&gt; "MSYS2 64bit" -&gt; "MSYS2 MinGW 64-bit" </p>
<h5>SDL_Pango</h5>
<blockquote>
<p>
At first, you have to prepare source tar-ball and a required patch in the same directory. </p>
<ul>
<li>
Download <a href="https://sourceforge.net/projects/sdlpango/files/SDL_Pango/0.1.2/SDL_Pango-0.1.2.tar.gz/download">source tar-ball of SDL_Pango-0.1.2</a> from <a href="https://sourceforge.net/projects/sdlpango/">SDL_Pango's page on Sourceforge.net</a>. </li>
<li>
Download <a href="http://johnnypops.co.uk/tuxpaint/SDL_Pango-configure-extra-api.patch">a patch file</a> from <a href="http://www.johnnypops.co.uk/tuxpaint/">John Popplewell's "Tux Paint - MinGW/MSYS build instructions" webpage</a>. (This adds some extra (required) functionality to SDL_Pango.) </li>
</ul>
<p>
Build and install SDL_Pango as follows. <blockquote>
<code>
$ tar zxvf SDL_Pango-0.1.2.tar.gz<br/>
$ cd SDL_Pango-0.1.2/<br/>
$ patch -p0 &lt; ../SDL_Pango-configure-extra-api.patch<br/>
$ ./configure --prefix=/mingw64 &amp;&amp; make &amp;&amp; make install
</code>
</blockquote>
</p>
</blockquote>
<h5>SDL</h5>
<blockquote>
<p>
Download <a href="http://www.libsdl.org/release/SDL-1.2.15.tar.gz">source tar-ball of SDL_1.2.15</a> from <a href="http://www.libsdl.org/">libsdl.org</a>. </p>
<p>
Re-install SDL as follows. <blockquote>
<code>
$ tar zxvf SDL-1.2.15.tar.gz<br/>
$ cd SDL-1.2.15<br/>
$ ./configure --prefix=/mingw64 &amp;&amp; make &amp;&amp; make install
</code>
</blockquote>
</p>
</blockquote>
</blockquote>
<p>
<i>
Proceed to the next "<a href="#32bit">MinGW 32bit (i686) toolchains</a>" section, or skip to the "<a href="#imagemagick">ImageMagick</a>" section if you need only a 64bit build environment. </i>
</p>
<hr size="1" noshade width="75%" />
<h4>
<a name="32bit" id="32bit">
MinGW 32bit (i686) toolchains </a>
</h4>
<blockquote>
<p>
Within the MSYS2 shell, run the following command to install basic 32bit development tools: <blockquote>
<code>
pacman -S mingw-w64-i686-toolchain
</code>
</blockquote>
</p>
</blockquote>
<h4>
32bit (i686) dependency libraries for Tux Paint </h4>
<blockquote>
<p>
You can install tools and libraries required for compiling Tux Paint on MSYS2/MINGW using "<code>pacman</code>" except for SDL_Pango. </p>
<p>
"<code>ntldd</code>" is a small tool which examine windows executable files to list Dynamic Link Library (<code>.dll</code>) files they depends on. Tux Paint's packaging process for binary distribution uses it to find required <code>.dll</code> files. </p>
<p>
FLTK is a cross-platform GUI toolkit used by "Tux Paint Config.". You can skip installing it if you are <em>only</em> building "Tux Paint". </p>
<p>
<blockquote>
<code>
$ pacman -S mingw-w64-i686-SDL_{image,mixer,ttf}<br/>
$ pacman -S mingw-w64-i686-librsvg<br/>
$ pacman -S mingw-w64-i686-fribidi<br/>
$ pacman -S mingw-w64-i686-libimagequant<br/>
$ pacman -S mingw-w64-i686-fltk<br/>
$ pacman -S mingw-w64-i686-ntldd-git
</code>
</blockquote>
</p>
<p>
<strong>Note:</strong> Close the shell before proceeding to the remaining process. </p>
</blockquote>
<h4>
Install SDL_Pango and re-install SDL on the 32bit environment </h4>
<blockquote>
<p>
SDL_Pango should be installed manually. In addition, you have to re-install SDL from the source code or you will see unnecessary blank window opens when starting Tux Paint. </p>
<p>
This time, use the MinGW "32bit" shell. Open the shell from the "Start Menu" -&gt; "MSYS2 64bit" -&gt; "MSYS2 MinGW 32-bit" </p>
<h5>SDL_Pango</h5>
<blockquote>
<p>
At first, you have to prepare source tar-ball and a required patch in the same directory. </p>
<ul>
<li>
Download <a href="https://sourceforge.net/projects/sdlpango/files/SDL_Pango/0.1.2/SDL_Pango-0.1.2.tar.gz/download">source tar-ball of SDL_Pango-0.1.2</a> from <a href="https://sourceforge.net/projects/sdlpango/">SDL_Pango's page on Sourceforge.net</a>. </li>
<li>
Download <a href="http://johnnypops.co.uk/tuxpaint/SDL_Pango-configure-extra-api.patch">a patch file</a> from <a href="http://www.johnnypops.co.uk/tuxpaint/">John Popplewell's "Tux Paint - MinGW/MSYS build instructions" webpage</a>. (This adds some extra (required) functionality to SDL_Pango.) </li>
</ul>
<p>
Build and install SDL_Pango as follows. <blockquote>
<code>
$ tar zxvf SDL_Pango-0.1.2.tar.gz<br/>
$ cd SDL_Pango-0.1.2/<br/>
$ patch -p0 &lt; ../SDL_Pango-configure-extra-api.patch<br/>
$ ./configure --prefix=/mingw32 &amp;&amp; make &amp;&amp; make install
</code>
</blockquote>
</p>
</blockquote>
<h5>SDL</h5>
<blockquote>
<p>
Download <a href="http://www.libsdl.org/release/SDL-1.2.15.tar.gz">source tar-ball of SDL_1.2.15</a> from <a href="http://www.libsdl.org/">libsdl.org</a>. </p>
<p>
Re-install SDL as follows. <blockquote>
<code>
$ tar zxvf SDL-1.2.15.tar.gz<br/>
$ cd SDL-1.2.15<br/>
$ ./configure --prefix=/mingw32 &amp;&amp; make &amp;&amp; make install
</code>
</blockquote>
</p>
</blockquote>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>
<a name="imagemagick" id="imagemagick">ImageMagick</a>
</h4>
<blockquote>
<p>
<a href="https://imagemagick.org">ImageMagick</a> is a compilation of command line tools to create, edit, compose, or convert bitmap images supporting quite a large number of image formats. Tux Paint uses two functions ("convert" and "composite") in it to generate thumbnails for startar images and templates during the build process. </p>
<p>
Using official binary release available from "<a href="https://imagemagick.org/script/download.php#windowsand">Windows Binary Release</a>" is recommended, due to the commands installed with "<code>pacman</code>" on MinGW/MSYS not working as expected! </p>
<p>
Do not forget to enable "Install legacy utilities (e.g. convert)" while installing it, because Tux Paint's build process uses them. </p>
<p>
Add the path to the directory in which ImageMagick is installed at the top of your "PATH" environment variable. For example: <blockquote>
<code>
$ export PATH=/c/Program\ Files/ImageMagick-7.0.10-Q16-HDRI:$PATH
</code>
</blockquote>
</p>
<p>
You can make this permanent by adding the above to your the BASH shell configuration file, "<code>~/.bash_profile</code>". </p>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>Tux Paint</h4>
<blockquote>
<p>
You can compile 64bit binaries using MSYS2 64bit shell, and 32bit binaries using MSYS2 32bit shell, respectively. </p>
<ul>
<li>
Select "MSYS2 64bit" -&gt; "MSYS2 MinGW 64-bit" from the "Start Menu" to open the 64bit shell. </li>
<li>
Select "MSYS2 64bit" -&gt; "MSYS2 MinGW 32-bit" from the "Start Menu" to open the 32bit shell. </li>
</ul>
<p>
Compile Tux Paint with the following command: <blockquote>
<code>
$ make bdist-win32
</code>
</blockquote>
</p>
<p>
<strong>Note:</strong> At this point, you will want to build "Tux Paint Config." for Windows, so it can be included along with "Tux Paint", if you're making an official (or test) release. The build process will look for it in a directory named "<code>tuxpaint-config</code>" (with no version number, e.g., "<code>tuxpaint-config-X.Y.Z</code>"). See "Tux Paint Config."'s INSTALL.txt documentation for details. </p>
<p>
All the files needed for starting Tux Paint (and Tux Paint Config.) are collected in the directory for binary distribution "<code>bdist</code>" directory under "<code>win32</code>". You can start them by double-clicking their executable (<code>.exe</code>) files in the "<code>bdist</code>" directory. </p>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>Building the Tux Paint Windows Installer:</h4>
<blockquote>
<p>
<a href="https://jrsoftware.org/isinfo.php">Inno Setup</a> is used to build executable installer for Tux Paint. Therefore you have to install it in the first place. </p>
<p>
</p>
<p>
Then, you can easily build an executable installer by right-clicking on the "<code>tuxpaint.iss</code>" icon in the "<code>win32</code>" directory and selecting "Compile" on the list. It will run for a while, and eventually you will find a "<code>tuxpaint-<i>X.Y.Z</i>-win32-installer.exe</code>" file in the same directory. </p>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>Running the Tux Paint Windows Installer:</h4>
<blockquote>
<p>
Faga dobre clic no executábel do instalador de Tux Paint (ficheiro .EXE) e siga as instrucións.
@ -231,6 +558,8 @@
Neste punto, pode premer en «Instalar» para instalar Tux Paint. </p>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>Cambiar os axustes usando o acceso directo:</h4>
<blockquote>
<p>
@ -267,6 +596,8 @@
Cando teña rematado, prema en «Aceptar». </p>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>Se algo vai mal:</h4>
<blockquote>
<p>
@ -277,7 +608,12 @@
</blockquote>
</blockquote>
<h3>Usuarios de Linux/Unix:</h3>
<hr size="1" noshade />
<h3>
<a name="compiling-linux" id="compiling-linux">
Usuarios de Linux/Unix </a>
</h3>
<blockquote>
<h4>Compilación:</h4>
<blockquote>
@ -294,11 +630,13 @@
</blockquote>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>
Desactivar a compatibilidade de «SVG» (e, polo tanto, as dependencias de «Cairo, libSVG, e svg-cairo»: </h4>
<blockquote>
<p>
Para desactivar a compatibilidade con SVG (por exemplo, se o seu sistema non é compatíbel coa biblioteca de Cairo ou outras dependencias relacionadas co SVG), pode executar «<code>make</code>» engadindo «<code>SVG_LIB= SVG_CFLAGS= NOSVGFLAG=NOSVG</code>»:
Para desactivar a compatibilidade con SVG (por exemplo, se o seu sistema non é compatíbel coa biblioteca de Cairo ou outras dependencias relacionadas co SVG), pode executar «<code>make</code>» engadindo «<code style="white-space: nowrap;">SVG_LIB= SVG_CFLAGS= NOSVGFLAG=NOSVG</code>»:
<blockquote>
<code>
$ make SVG_LIB= SVG_CFLAGS=
@ -306,6 +644,8 @@
</blockquote>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>
Desactivar a compatibilidade de «Pango» (e, polo tanto, as dependencias de «Pango, Cairo, etc.»: </h4>
<blockquote>
@ -318,6 +658,8 @@
</blockquote>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>Desactivación do son en tempo de compilación:</h4>
<blockquote>
Se non te unha tarxeta de son ou prefire construír o programa sen asistencia de son (e polo tanto sen a dependencia <code>SDL_mixer</code>), pode executar «<code>make</code>» con «<code>SDL_MIXER_LIB=</code>» engadido: </p>
@ -328,18 +670,24 @@
</blockquote>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>Outras opcións:</h4>
<blockquote>
<p>
Outras opcións (p. ex.: rutas de instalación) poden ser anuladas; véxaas en «<code>Makefile</code>» para máis detalles. </p>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>Se se producen erros:</h4>
<blockquote>
<p>
Se recibe algún erro durante o tempo de compilación, asegúrese de ter instaladas as bibliotecas axeitadas (ver máis arriba). Se está a empregar versións empaquetadas das bibliotecas (por exemplo, RPM en RedHat ou DEB en Debian), asegúrese de obter tamén os correspondentes paquetes «<code>-dev</code>» ou «<code>-devel</code>», se non, non poderá compilar Tux Paint (e outros programas) dende o código fonte. </p>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>Instalar:</h4>
<blockquote>
<p>
@ -422,15 +770,155 @@
</blockquote>
</blockquote>
</blockquote>
<hr size="1" noshade />
<h3>
<a name="compiling-macos" id="compiling-macos">
Usuarios de macOS </a>
</h3>
<p style="font-size: small;">
<em>
21 de Setembro de 2021 Mark K. Kim &lt;<a href="mailto:markuskimius@gmail.com">markuskimius@gmail.com</a>&gt;
</em>
</p>
<blockquote>
<p>
Tux Paint 0.9.22 and earlier required building Tux Paint from the Xcode IDE. Starting with 0.9.23, however, Tux Paint for macOS is built as though it were a Linux application. </p>
<h4>Prerequisites</h4>
<blockquote>
<p>
Although Tux Paint is built without the Xcode IDE, Xcode itself is still required to build Tux Paint. <a href="https://developer.apple.com/xcode/ide/">Download it from the App Store</a>, and launch it once to accept its license agreements. You may also need to install the Xcode command line tools using the command: <blockquote>
<code>
xcode-select --install
</code>
</blockquote>
</p>
<p>
Building Tux Paint also requires various libraries. We install them from MacPorts where possible, source code otherwise. Install MacPorts to the default <code>/opt/local</code> path according to the instructions found on their website: <a href="https://www.macports.org/">https://www.macports.org/</a> <ul>
<li><code>ImageMagick</code></li>
<li><code>cairo</code></li>
<li><code>fribidi</code></li>
<li><code>lbzip2</code></li>
<li><code>libimagequant</code><sup>*</sup></li>
<li><code>libpaper</code></li>
<li><code>libpng</code></li>
<li><code>librsvg</code></li>
<li><code>libsdl</code></li>
<li><code>libsdl_image</code></li>
<li><code>libsdl_mixer</code></li>
<li><code>libsdl_pango</code></li>
<li><code>libsdl_ttf</code></li>
<li><code>pkgconfig</code></li>
<li><code>zlib</code></li>
</ul>
... but you should install any package that is required by the latest version of Tux Paint.<br/>
<br/>
<sup>*</sup> Not available from MacPorts as of this writing, see below. </p>
<h5>libimagequant</h5>
<blockquote>
<p>
<code>libimagequant</code> is not available from MacPorts as of this writing. It can be installed from the source code as follows. It should be installed to <code>/opt/local</code> (same as MacPorts) for the library to be included in <code>TuxPaint.dmg</code>. <blockquote>
<code>
$ git clone https://github.com/ImageOptim/libimagequant.git<br/>
$ cd libimagequant<br/>
$ ./configure --prefix=/opt/local<br/>
$ make<br/>
$ sudo make install
</code>
</blockquote>
</p>
</blockquote>
<p>
<strong>WARNING:</strong> Having any UNIX-like toolset installed on your Mac besides MacPorts and Xcode, such as Fink or Brew, will prevent your app bundle from being portable. Be sure Fink and Brew are not accessible from your build environment. </p>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>How to Build</h4>
<blockquote>
<p>
Simply, run: <blockquote>
<code>
% make<br/>
% make install
</code>
</blockquote>
... to create the <code>TuxPaint.app</code> application bundle that can be run in-place or copied to <code>/Applications</code>. It also creates <code>TuxPaint.dmg</code> for distribution. </p>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>Known Issues</h4>
<blockquote>
<ul>
<li>
A macOS binary built on a specific version of macOS only runs on that version of macOS or later. To ensure Tux Paint can run on the oldest version of macOS possible, build it on the oldest version of macOS available. As of this writing we know Tux Paint cannot be built to run on macOS 10.7 or earlier.<br/>
<br/>
See "Old Versions of macOS" below for best-effort instructions on how to obtain, install, and build Tux Paint on an old version of macOS. </li>
</ul>
</blockquote>
<hr size="1" noshade width="75%" />
<h4>Old Versions of macOS</h4>
<blockquote>
<p>
Some old versions of macOS can be downloaded from Apple's support page: <a href="https://support.apple.com/en-us/HT211683">https://support.apple.com/en-us/HT211683</a> </p>
<p>
macOS does allow dual booting of multiple versions of the OS, but it's safer and easier to install the old macOS onto a flash drive. Wherever you're installing it, the target drive's partitioniong scheme and partition type must match what the old macOS expects, so use the Disk Utility to partition and format the flash drive accordingly. </p>
<p>
As of this writing, the oldest version of macOS available on Apple's support site is Yosemite 10.10, which expects "GPT (GUID Partition Table)" partitioning scheme instead of the older MBR scheme, and "Mac OS Extended (Journaled)" as the partition type instead of the newer APFS partition type. </p>
<p>
Upon launching the installer, if you get a popup about macOS being too old or new to be installed, a bootable installer can be created using the instructions found here: <a href="https://support.apple.com/en-mide/HT201372">https://support.apple.com/en-mide/HT201372</a> </p>
<p>
It has been found that macOS can be installed onto the bootable media itself, so you can make the flash drive into a bootable installer then install the old macOS onto the same flash drive. </p>
<p>
Once the old macOS is installed, you may find the Xcode on the App Store is too new to run on the version of the old macOS. Old versions of Xcode can be downloaded from Apple's Developer site in an area accessible with free registration: <a href="https://developer.apple.com/download/more/">https://developer.apple.com/download/more/</a> </p>
<p>
The list of macOS versions and the last version of Xcode compatible with them are laid out nicely on the Wikipedia page on Xcode: <a href="https://en.wikipedia.org/wiki/Xcode#Version_comparison_table">https://en.wikipedia.org/wiki/Xcode#Version_comparison_table</a> </p>
<p>
And because Xcode is being installed manually, you can skip the step to install the Xcode command line tools (do not run "<code style="white-space: nowrap;">xcode-select --install</code>") but otherwise build Tux Paint using the same steps described in the earlier part of this document. </p>
</blockquote>
</blockquote>
</blockquote>
<h2>Depuración:</h2>
<blockquote>
A depuración (a «STDOUT», por exemplo, á terminal ou a un ficheiro «<code>stdout.txt</code>» en Windows) pódese activar co axuste «<code>DEBUG</code>» (e, se se quere un rexistro detallado, «<code>VERBOSE</code>») <code>#define </code> en «<code>src/debug.h</code>». </blockquote>
<hr size="2" noshade />
<h2>Desinstalación de Tux Paint:</h2>
<h2>
<a name="debugging" id="debugging">
Debugging </a>
</h2>
<blockquote>
<h3>Windows</h3>
Debugging output &mdash; to "STDOUT" on Linux and Unix, to a "<code>stdout.txt</code>" file on Windows, and to the file "<code>/tmp/tuxpaint.log</code>" on macOS &mdash; can be enabled by setting "<code>DEBUG</code>" (and, if verbose logging is wanted, "<code>VERBOSE</code>") <code>#define</code>s in "<code>src/debug.h</code>" and (re)compiling Tux Paint. </blockquote>
<hr size="2" noshade />
<h2>
<a name="uninstalling" id="uninstalling">
Uninstalling Tux Paint </h2>
</h2>
<blockquote>
<h3>
<a name="uninstalling-windows" id="uninstalling-windows">
Windows </a>
</h3>
<blockquote>
<h4>Uso do desinstalador</h4>
<blockquote>
@ -448,10 +936,27 @@
</blockquote>
</blockquote>
<h3>Linux</h3>
<hr size="1" noshade />
<h3>
<a name="uninstalling-macos" id="uninstalling-macos">
macOS </a>
</h3>
<blockquote>
<p>
Dentro do directorio de orixe de Tux Paint (onde compilou Tux Paint), pode usar o destino «<code>make uninstall</code>» para desinstalar Tux Paint. De xeito predeterminado, debe facelo o usuario «root» («superusuario»), mais se instalou Tux Paint noutro lugar (por exemplo, usando a configuración «<code>PREFIX=...</code>» en «<code>make</code>» e «<code>make install</code>»), pode que non e queira proporcionar a mesma configuración aquí. (Consulte as instrucións de instalación anteriores para obter máis información.) </p>
Delete "<code>TuxPaint.app</code>" from the "Applications" folder. Data files, including the configuration files, stamps, and saved pictures, may be found in "<code style="white-space: nowrap;">Library/Application Support/TuxPaint</code>" (all users) and "<code style="white-space: nowrap;">/Users/<i>USERNAME</i>/Library/Application Support/TuxPaint</code>" (individual users). </p>
</blockquote>
<hr size="1" noshade />
<h3>
<a name="uninstalling-linux" id="uninstalling-linux">
Linux </a>
</h3>
<blockquote>
<p>
Within the Tux Paint source directory (where you compiled Tux Paint), you can use the "<code style="white-space: nowrap;">make uninstall</code>" target to uninstall Tux Paint. By default, this must be done by the "root" user ('superuser'), but if you installed Tux Paint somewhere else (e.g., using a "<code>PREFIX=...</code>" setting to "<code>make</code>" and "<code style="white-space: nowrap;">make install</code>"), you may not, and will want to provide those same settings here. (See the <a href="#compiling-linux">installation instructions above</a> for further information.) </p>
</blockquote>
<blockquote>
</body>

5373
docs/gl_ES.UTF-8/html/OPTIONS.html
View file

File diff suppressed because it is too large Load diff

2
docs/gl_ES.UTF-8/html/PNG.html
View file

@ -17,7 +17,7 @@
width="205"
height="210"
alt="Tux Paint"><br>
versión 0.9.26<br/>
versión 0.9.27<br/>
Documentación PNG </h1>
<p>

18
docs/gl_ES.UTF-8/html/README.html
View file

@ -17,7 +17,7 @@
width="205"
height="210"
alt="Tux Paint"><br>
versión 0.9.26 </h1>
versión 0.9.27 </h1>
<h3>
Un sinxelo programa de debuxo para cativos </h3>
@ -28,7 +28,7 @@
</p>
<p>
28 de Xuño de 2021 </p>
5 de Setembro de 2021 </p>
</center>
<hr size="2"
@ -408,6 +408,15 @@
<p>
Se mantén premido o botón do rato e move o rato, irá debuxando a medida que se move. </p>
<p>
Some brushes are animated &mdash; they change their shape as you draw them. A good example of this is the vines brush that ships with Tux Paint. These brushes will have a small "filmstrip" icon drawn on their Selector buttons. </p>
<p>
Other brushes are directional &mdash; they will draw a different shape depending on what direction you are painting with them. An example of this is the arrow brush that ships with Tux Paint. These brushes have a small 8-way arrow icon drawn on their Selector buttons. </p>
<p>
Finally, some brushes can be both direction <em>and</em> animated. Examples of this are the cat and squirrel brushes that ship with Tux Paint. These brushes will have both the "filmstrip" and 8-way arrow icons. </p>
<p>
Mentres debuxa, soa un son. Canto maior sexa o pincel, menor será o ton. </p>
<br clear="all">
@ -503,6 +512,9 @@
<p>
Solte o rato para completar a liña. Soará un «chimpo». </p>
<p>
Some brushes are animated, and will show a pattern of shapes along the line. Others are directional, and will show a different shape depending on the angle of the brush. And finally some are both animated and directional. See "Paint", above, to learn more. </p>
<br clear="all">
<p align="center">
@ -605,7 +617,7 @@
Escolla un tipo de letra (entre as «Letras» dispoñíbeis á dereita) e unha cor (na paleta de cores preto da parte inferior). prema na pantalla e aparecerá un cursor. Escriba un texto e aparecerá na pantalla. </p>
<p>
Prema <strong><code>[Enter]</code></strong> ou <strong><code>[Return]</code></strong> e o texto será debuxado na imaxe e o cursor moverase cara abaixo unha liña. </p>
Prema <b><code>[Intro]</code></b> ou <b><code>[Retorno]</code></b> e o texto será debuxado na imaxe e o cursor moverase cara abaixo unha liña. </p>
<p>
Como alternativa, prema <strong><code>[Tab]</code></strong> e o texto será debuxado na imaxe, mais o cursor moverase á dereita do texto, no canto de baixar unha liña e á esquerda. (Isto pode ser útil para crear unha liña de texto con cores, tipos de letra, estilos e tamaños mesturados.) </p>

2
docs/gl_ES.UTF-8/html/SIGNALS.html
View file

@ -17,7 +17,7 @@
width="205"
height="210"
alt="Tux Paint"><br>
versión 0.9.26<br/>
versión 0.9.27<br/>
Documentación de sinais </h1>
<p>

2
docs/gl_ES.UTF-8/html/SVG.html
View file

@ -17,7 +17,7 @@
width="205"
height="210"
alt="Tux Paint"><br>
versión 0.9.26<br/>
versión 0.9.27<br/>
Documentación SVG </h1>
<p>

30
docs/ja_JP.UTF-8/ADVANCED-STAMPS-HOWTO.txt
View file

@ -1,9 +1,27 @@
Tux Paint
バージョン 0.9.26 スタンプ作成の詳細について
バージョン 0.9.27 スタンプ作成の詳細について
Copyright © 2006-2021 by Albert Cahalan ほか; "AUTHORS" 参照.
http://www.tuxpaint.org/
2021年8月29日
----------------------------------------------------------------------
+-----------------------+
|目次 |
|-----------------------|
| * この解説について |
| * 使用する画像の選択 |
| * マスクの設定 |
| * 縁取りと不要なピクセルの除去 |
| * Tux Paint 用の画像の保存 |
+-----------------------+
----------------------------------------------------------------------
----------------------------------------------------------------------
この解説について
この解説では、デジカメ写真などのJPEG画像をもとに、PNG形式で、高いクォリティの Tux Paint
@ -11,6 +29,8 @@
扱う対象としては、通常の透明ではないものを前提としており、半透明のもの（火、動く扇風機の羽根、風船）や発光するもの（火、電球、太陽）を扱うには、専用のソフトウェアを使用するのが最適です。背景が完全なベタ塗りの画像も、専用のソフトを使うのが良いですが、以下のようにしても問題はありません。
----------------------------------------------------------------------
使用する画像の選択
著作権
@ -40,6 +60,8 @@
生き物の足や車のホイールなどにも注意が必要です。これらが何かに隠れて見えなくなっている場合は新しく描き足す必要があります。隠れているのが一部だけの場合は、他の部分をコピーして描き換えることができるかもしれません。
----------------------------------------------------------------------
画像の準備
まず、画像をJPEGで保存し直さないようにしてください。これは品質低下の原因となります。jpegtranという特別なツールを使えば、品質を維持したまま画像を切り抜くことができます。
@ -64,6 +86,8 @@
注意：マスクを設定した後は、画像の回転や拡大縮小は行えません。これはデータ損失の原因となります。サイズを調整するための特別な方法は後述します。
----------------------------------------------------------------------
マスクの設定
レイヤーダイアログのサムネイル画像を [Ctrl] キーを押しながらクリックしたり、[Alt]
@ -91,6 +115,8 @@
マスクを表示して編集します。黒か白の色で領域を選択します。ほとんどの場合、選択されていない色の斑点が残っていると思います。選択範囲を反転させ、鉛筆ツールを使ってこれらの点を取り除きます。この作業を白と黒の両方で行います。
----------------------------------------------------------------------
縁取りと不要なピクセルの除去
マスクをを表示しながら、黒で領域を選択した後、選択範囲を数ピクセル縮小します。ただし、マスクの端から縮小しないように注意してください（縮小することで、ミスを防いだりやり直したりすることができます）
@ -118,6 +144,8 @@
タックスペイントでは、画像を非常に大きく縮小することができるため、オブジェクトの輪郭を外側に大きく広げることが重要です。オブジェクトの輪郭の部分では、非常に正確に処理する必要がありますが、輪郭から離れるにつれて、少々手を抜いても大丈夫です。十数ピクセル以上外側まで描くとちょうど良くなります。これを太くすればするだけ、Tux
Paintは汚い色の縁どりを発生させずにスケールダウンすることができます。オブジェクトの端から数ピクセル以上離れた部分については、鉛筆ツール（またはドラッグ＆ドロップで適当に色を選択）を使用して、結果がきれいに縮小されるようにしてください。
----------------------------------------------------------------------
Tux Paint 用の画像の保存
せっかくの労作も簡単にダメになることがあります。画像編集ソフトは、不透明度0％の領域のピクセルを勝手にで破棄することがあります。この現象が発生する条件は、ソフトウェアのバージョンによっても異なります。慎重を期すため、画像を直接PNGとして保存してみてください。その後、不透明度0％の部分が黒くなったり白くなったりしていないことを確認するために、もう一度画像を読み込んでみてください。ディスクスペースを節約するため（そして自分のミスを隠すため）に画像を縮小する必要がある場合、ほぼ確実に

4
docs/ja_JP.UTF-8/ENVVARS.txt
View file

@ -1,11 +1,11 @@
Tux Paint
バージョン 0.9.26
バージョン 0.9.27
Environment Variables Documentation
Copyright © 2021-2021 by various contributors; "AUTHORS" 参照.
http://www.tuxpaint.org/
2021年5月11日
2021年8月 8日
----------------------------------------------------------------------

31
docs/ja_JP.UTF-8/EXTENDING.txt
View file

@ -1,11 +1,11 @@
Extending
Tux Paint
バージョン 0.9.26
バージョン 0.9.27
Copyright © 2002-2021 by various contributors; "AUTHORS" 参照.
http://www.tuxpaint.org/
2021年5月31日
2021年9月 6日
----------------------------------------------------------------------
@ -212,17 +212,26 @@ Brushes
Add a line containing the word "directional" to the brush's data
file.
Animated Directional Brushes
Rotating Brushes
You may mix both animated and directional features into one brush.
Use both options ("frames=N" and "directional"), in separate lines
in the brush's ".dat" file.
As of Tux Paint version 0.9.27, you may now create rotating brushes.
As the brush is used, it is rotated 360 degrees, depending on the
direction the brush is going.
Lay the brush out so that each 3x3 set of directional shapes are
laid out across a wide PNG image. For example, if the brush is 30x30
and there are 5 frames, it would be 450x90. (The leftmost 150x90
pixels of the image represent the 9 direction shapes for the first
frame, for example.)
Add a line containing the word "rotate" to the brush's data file.
Animated Directional or Rotating Brushes
You may mix both animated and either directional or rotating
features into one brush. Use both options desired ("frames=N" and
"directional" or "rotate"), in separate lines in the brush's ".dat"
file.
For directional brushes, lay the brush out so that each 3x3 set of
directional shapes are laid out across a wide PNG image. For
example, if the brush is 30x30 and there are 5 frames, it would be
450x90. (The leftmost 150x90 pixels of the image represent the 9
direction shapes for the first frame, for example.)
Place the brush image PNGs (and any data text files) in the "brushes"
directory.

19
docs/ja_JP.UTF-8/FAQ.txt
View file

@ -1,10 +1,25 @@
Tux Paint
バージョン 0.9.26 Frequently Asked Questions
バージョン 0.9.27 Frequently Asked Questions
Copyright © 2002-2021 by various contributors; "AUTHORS" 参照.
http://www.tuxpaint.org/
2021年6月 2日
2021年8月29日
----------------------------------------------------------------------
+------------------------------+
|目次 |
|------------------------------|
| * Drawing-related |
| * Interface Problems |
| * Printing |
| * Saving |
| * Audio Problems |
| * Fullscreen Mode Problems |
| * Other Probelms |
| * Help / Contact |
+------------------------------+
----------------------------------------------------------------------

474
docs/ja_JP.UTF-8/INSTALL.txt
View file

@ -1,26 +1,46 @@
Tux Paint
バージョン 0.9.26
バージョン 0.9.27
Installation Documentation
Copyright © 2002-2021 by various contributors; "AUTHORS" 参照.
http://www.tuxpaint.org/
2021年3月 9日
2021年9月 5日
----------------------------------------------------------------------
Requirements:
+----------------------------------------------------+
|目次 |
|----------------------------------------------------|
| * Requirements |
| * Simple DirectMedia Layer library (libSDL) |
| * Other Libraries |
| * Compiling and Installation |
| * Windows のユーザー |
| * Linux または Unix のユーザー |
| * macOS のユーザー |
| * Debugging |
| * Uninstalling Tux Paint |
| * Windows |
| * macOS |
| * Linux |
+----------------------------------------------------+
libSDL
----------------------------------------------------------------------
Requirements
Simple DirectMedia Layer library (libSDL)
Tux Paint requires the Simple DirectMedia Layer Library (libSDL), an
Open Source multimedia programming library available under the GNU
Lesser General Public License (LGPL).
Along with libSDL, Tux Paint depends on a number of other SDL 'helper'
libraries: SDL_Image (for graphics files), SDL_TTF and (optionally)
SDL_Pango (for True Type Font support) and, optionally, SDL_Mixer (for
sound effects).
libraries: SDL_Image (for graphics files), SDL_gfx (for some graphical
functions, like rotation), SDL_TTF and (optionally) SDL_Pango (for
True Type Font support) and, optionally, SDL_Mixer (for sound
effects).
Linux/Unix Users:
@ -30,6 +50,9 @@ Requirements:
* libSDL: http://www.libsdl.org/
* SDL_Image: http://www.libsdl.org/projects/SDL_image/
* SDL_gfx:
https://www.ferzkopp.net/wordpress/2016/01/02/sdl_gfx-sdl2_gfx/
(https://sourceforge.net/projects/sdlgfx/)
* SDL_TTF: http://www.libsdl.org/projects/SDL_ttf/
* SDL_Pango: http://sourceforge.net/projects/sdlpango/ (optional)
* SDL_Mixer: http://www.libsdl.org/projects/SDL_mixer/ (optional)
@ -116,55 +139,261 @@ Requirements:
http://netpbm.sourceforge.net/
Compiling and Installation:
----------------------------------------------------------------------
Compiling and Installation
Tux Paint is released under the GNU General Public License (GPL) (see
"COPYING.txt" for details), and therefore the 'source code' to the
program is available freely.
Windows Users:
Windows のユーザー
Compiling:
2020年10月25日 Shin-ichi TOYAMA shin1@wmail.plala.or.jp
<shin1@wmail.plala.or.jp>
Compiling Set-Up
As of February 2005 (starting with Tux Paint 0.9.15), the "Makefile"
includes support for building on a Windows system using MinGW/MSYS
(http://www.mingw.org/).
(https://sourceforge.net/projects/msys2/).
After configuring the environment and building and installing all
the dependencies, use these commands, in MSYS, to build, install and
run:
Many tools and libraries are required to build Tux Paint. The
package management system "pacman" helps you install them
automatically solving complicated dependencies.
Prior to version 0.9.20:
Download the latest MSYS2 environment from
https://sourceforge.net/projects/msys2/files/Base/ and install it
where you'd like (the default is "C:\msys64")
$ make win32
$ make install-win32
$ tuxpaint
Open the MSYS2 shell from the "Start Menu" -> "MSYS2 64bit" ->
"MSYS2 MSYS" and execute following command (press [Enter] or
[Return] to accept the defaults for all questions):
Version 0.9.20 and beyond:
pacman -Syu
$ make
$ make install
$ tuxpaint
This will update core system and the window will close
automatically. Repeat the steps above one more time to finish the
remaining update process.
Use the following command to build a version suitable for
redistribution with the installer or in a zip-file:
Within the MSYS2 shell, run the following command to install basic
development tools:
pacman -S base-devel msys2-devel git
Proceed to the next "MinGW 64bit (x86_64) toolchains" section, or skip
to the "MinGW 32bit (i686) toolchains" section if you need only a
32bit build environment.
-------------------------------------------------------
MinGW 64bit (x86_64) toolchains
Within the MSYS2 shell, run the following command to install basic
64bit development tools:
pacman -S mingw-w64-x86_64-toolchain
64bit (x86_64) dependency libraries for Tux Paint
You can install tools and libraries required for compiling Tux Paint
on MSYS2/MINGW using "pacman" except for SDL_Pango.
"ntldd" is a small tool which examine windows executable files to
list Dynamic Link Library (.dll) files they depends on. Tux Paint's
packaging process for binary distribution uses it to find required
.dll files.
FLTK is a cross-platform GUI toolkit used by "Tux Paint Config.".
You can skip installing it if you are only building "Tux Paint".
$ pacman -S mingw-w64-x86_64-SDL_{image,mixer,ttf}
$ pacman -S mingw-w64-x86_64-librsvg
$ pacman -S mingw-w64-x86_64-fribidi
$ pacman -S mingw-w64-x86_64-libimagequant
$ pacman -S mingw-w64-x86_64-fltk
$ pacman -S mingw64/mingw-w64-x86_64-ntldd-git
Note: Close the shell before proceeding to the remaining process.
Install SDL_Pango and re-install SDL on the 64bit environment
SDL_Pango should be installed manually. In addition, you have to
re-install SDL from the source code or you will see unnecessary
blank window opens when starting Tux Paint.
This time, use the MinGW "64bit" shell. Open the shell from the
"Start Menu" -> "MSYS2 64bit" -> "MSYS2 MinGW 64-bit"
SDL_Pango
At first, you have to prepare source tar-ball and a required patch
in the same directory.
* Download source tar-ball of SDL_Pango-0.1.2 from SDL_Pango's
page on Sourceforge.net.
* Download a patch file from John Popplewell's "Tux Paint -
MinGW/MSYS build instructions" webpage. (This adds some extra
(required) functionality to SDL_Pango.)
Build and install SDL_Pango as follows.
$ tar zxvf SDL_Pango-0.1.2.tar.gz
$ cd SDL_Pango-0.1.2/
$ patch -p0 < ../SDL_Pango-configure-extra-api.patch
$ ./configure --prefix=/mingw64 && make && make install
SDL
Download source tar-ball of SDL_1.2.15 from libsdl.org.
Re-install SDL as follows.
$ tar zxvf SDL-1.2.15.tar.gz
$ cd SDL-1.2.15
$ ./configure --prefix=/mingw64 && make && make install
Proceed to the next "MinGW 32bit (i686) toolchains" section, or skip
to the "ImageMagick" section if you need only a 64bit build
environment.
-------------------------------------------------------
MinGW 32bit (i686) toolchains
Within the MSYS2 shell, run the following command to install basic
32bit development tools:
pacman -S mingw-w64-i686-toolchain
32bit (i686) dependency libraries for Tux Paint
You can install tools and libraries required for compiling Tux Paint
on MSYS2/MINGW using "pacman" except for SDL_Pango.
"ntldd" is a small tool which examine windows executable files to
list Dynamic Link Library (.dll) files they depends on. Tux Paint's
packaging process for binary distribution uses it to find required
.dll files.
FLTK is a cross-platform GUI toolkit used by "Tux Paint Config.".
You can skip installing it if you are only building "Tux Paint".
$ pacman -S mingw-w64-i686-SDL_{image,mixer,ttf}
$ pacman -S mingw-w64-i686-librsvg
$ pacman -S mingw-w64-i686-fribidi
$ pacman -S mingw-w64-i686-libimagequant
$ pacman -S mingw-w64-i686-fltk
$ pacman -S mingw-w64-i686-ntldd-git
Note: Close the shell before proceeding to the remaining process.
Install SDL_Pango and re-install SDL on the 32bit environment
SDL_Pango should be installed manually. In addition, you have to
re-install SDL from the source code or you will see unnecessary
blank window opens when starting Tux Paint.
This time, use the MinGW "32bit" shell. Open the shell from the
"Start Menu" -> "MSYS2 64bit" -> "MSYS2 MinGW 32-bit"
SDL_Pango
At first, you have to prepare source tar-ball and a required patch
in the same directory.
* Download source tar-ball of SDL_Pango-0.1.2 from SDL_Pango's
page on Sourceforge.net.
* Download a patch file from John Popplewell's "Tux Paint -
MinGW/MSYS build instructions" webpage. (This adds some extra
(required) functionality to SDL_Pango.)
Build and install SDL_Pango as follows.
$ tar zxvf SDL_Pango-0.1.2.tar.gz
$ cd SDL_Pango-0.1.2/
$ patch -p0 < ../SDL_Pango-configure-extra-api.patch
$ ./configure --prefix=/mingw32 && make && make install
SDL
Download source tar-ball of SDL_1.2.15 from libsdl.org.
Re-install SDL as follows.
$ tar zxvf SDL-1.2.15.tar.gz
$ cd SDL-1.2.15
$ ./configure --prefix=/mingw32 && make && make install
-------------------------------------------------------
ImageMagick
ImageMagick is a compilation of command line tools to create, edit,
compose, or convert bitmap images supporting quite a large number of
image formats. Tux Paint uses two functions ("convert" and
"composite") in it to generate thumbnails for startar images and
templates during the build process.
Using official binary release available from "Windows Binary
Release" is recommended, due to the commands installed with "pacman"
on MinGW/MSYS not working as expected!
Do not forget to enable "Install legacy utilities (e.g. convert)"
while installing it, because Tux Paint's build process uses them.
Add the path to the directory in which ImageMagick is installed at
the top of your "PATH" environment variable. For example:
$ export PATH=/c/Program\ Files/ImageMagick-7.0.10-Q16-HDRI:$PATH
You can make this permanent by adding the above to your the BASH
shell configuration file, "~/.bash_profile".
-------------------------------------------------------
Tux Paint
You can compile 64bit binaries using MSYS2 64bit shell, and 32bit
binaries using MSYS2 32bit shell, respectively.
* Select "MSYS2 64bit" -> "MSYS2 MinGW 64-bit" from the "Start
Menu" to open the 64bit shell.
* Select "MSYS2 64bit" -> "MSYS2 MinGW 32-bit" from the "Start
Menu" to open the 32bit shell.
Compile Tux Paint with the following command:
$ make bdist-win32
Or if building for Win9x/ME:
Note: At this point, you will want to build "Tux Paint Config." for
Windows, so it can be included along with "Tux Paint", if you're
making an official (or test) release. The build process will look
for it in a directory named "tuxpaint-config" (with no version
number, e.g., "tuxpaint-config-X.Y.Z"). See "Tux Paint Config."'s
INSTALL.txt documentation for details.
$ BDIST_WIN9X=1 make bdist-win32
All the files needed for starting Tux Paint (and Tux Paint Config.)
are collected in the directory for binary distribution "bdist"
directory under "win32". You can start them by double-clicking their
executable (.exe) files in the "bdist" directory.
Before any of the above will work, you need to configure the
environment and build or install the libraries that Tux Paint
depends upon. John Popplewell put together some instructions for
doing that here:
-------------------------------------------------------
http://www.johnnypops.co.uk/tuxpaint/
Building the Tux Paint Windows Installer:
Read the relevant notes if building for Win9X/ME.
Inno Setup is used to build executable installer for Tux Paint.
Therefore you have to install it in the first place.
Running the Installer:
Then, you can easily build an executable installer by right-clicking
on the "tuxpaint.iss" icon in the "win32" directory and selecting
"Compile" on the list. It will run for a while, and eventually you
will find a "tuxpaint-X.Y.Z-win32-installer.exe" file in the same
directory.
-------------------------------------------------------
Running the Tux Paint Windows Installer:
Double-click the Tux Paint installer executable (.EXE file) and
follow the instructions.
@ -183,6 +412,8 @@ Compiling and Installation:
At this point, you can click 'Install' to install Tux Paint!
-------------------------------------------------------
Changing the Settings Using the Shortcut:
To change program settings, right-click on the TuxPaint shortcut and
@ -211,6 +442,8 @@ Compiling and Installation:
When you have finished, click "OK."
-------------------------------------------------------
If Something Goes Wrong:
If, when you double-click on the shortcut to run Tux Paint, nothing
@ -222,7 +455,9 @@ Compiling and Installation:
just be due to incorrect character-case (capital 'Z' instead of
lowercase 'z') or a missing (or extra) '-' (dash).
Linux/Unix Users:
----------------------------------------------------------------------
Linux または Unix のユーザー
Compiling:
@ -235,6 +470,8 @@ Compiling and Installation:
$ make
-------------------------------------------------------
Disabling SVG support (and hence Cairo, libSVG, and svg-cairo dependencies):
To disable SVG support (e.g., if your system is not currently
@ -244,6 +481,8 @@ Compiling and Installation:
$ make SVG_LIB= SVG_CFLAGS=
-------------------------------------------------------
Disabling Pango support (and hence Pango, Cairo, etc. dependencies):
Prior to version 0.9.18, Tux Paint used the libSDL_ttf library for
@ -254,6 +493,8 @@ Compiling and Installation:
$ make SDL_PANGO_LIB=
-------------------------------------------------------
Disabling Sound at Compile-time:
If you don't have a sound card, or would prefer to build the program
@ -262,11 +503,15 @@ Compiling and Installation:
$ make SDL_MIXER_LIB=
-------------------------------------------------------
Other options:
Various other options (e.g., installation paths) may be overridden;
see them in "Makefile" for further details.
-------------------------------------------------------
If you get errors:
If you receive any errors during compile-time, make sure you have
@ -276,6 +521,8 @@ Compiling and Installation:
packages as well, otherwise you won't be able to compile Tux Paint
(and other programs) from source!
-------------------------------------------------------
Installng:
Assuming no fatal errors occured, you can now install the program so
@ -351,13 +598,150 @@ Compiling and Installation:
Note: This list is out of date. See "Makefile" and "Makefile-i18n"
for a complete list.
Debugging:
----------------------------------------------------------------------
Debugging (to "STDOUT", e.g. to the terminal, or to a "stdout.txt" file,
on Windows) can be enabled by setting "DEBUG" (and, if verbose logging
is wanted, "VERBOSE") #defines in "src/debug.h".
macOS のユーザー
Uninstalling Tux Paint:
2021年9月21日 Mark K. Kim <markuskimius@gmail.com>
Tux Paint 0.9.22 and earlier required building Tux Paint from the
Xcode IDE. Starting with 0.9.23, however, Tux Paint for macOS is built
as though it were a Linux application.
Prerequisites
Although Tux Paint is built without the Xcode IDE, Xcode itself is
still required to build Tux Paint. Download it from the App Store,
and launch it once to accept its license agreements. You may also
need to install the Xcode command line tools using the command:
xcode-select --install
Building Tux Paint also requires various libraries. We install them
from MacPorts where possible, source code otherwise. Install
MacPorts to the default /opt/local path according to the
instructions found on their website: https://www.macports.org/
* ImageMagick
* cairo
* fribidi
* lbzip2
* libimagequant^*
* libpaper
* libpng
* librsvg
* libsdl
* libsdl_image
* libsdl_mixer
* libsdl_pango
* libsdl_ttf
* pkgconfig
* zlib
... but you should install any package that is required by the
latest version of Tux Paint.
^* Not available from MacPorts as of this writing, see below.
libimagequant
libimagequant is not available from MacPorts as of this writing.
It can be installed from the source code as follows. It should be
installed to /opt/local (same as MacPorts) for the library to be
included in TuxPaint.dmg.
$ git clone https://github.com/ImageOptim/libimagequant.git
$ cd libimagequant
$ ./configure --prefix=/opt/local
$ make
$ sudo make install
WARNING: Having any UNIX-like toolset installed on your Mac besides
MacPorts and Xcode, such as Fink or Brew, will prevent your app
bundle from being portable. Be sure Fink and Brew are not accessible
from your build environment.
-------------------------------------------------------
How to Build
Simply, run:
% make
% make install
... to create the TuxPaint.app application bundle that can be run
in-place or copied to /Applications. It also creates TuxPaint.dmg
for distribution.
-------------------------------------------------------
Known Issues
* A macOS binary built on a specific version of macOS only runs on
that version of macOS or later. To ensure Tux Paint can run on
the oldest version of macOS possible, build it on the oldest
version of macOS available. As of this writing we know Tux Paint
cannot be built to run on macOS 10.7 or earlier.
See "Old Versions of macOS" below for best-effort instructions
on how to obtain, install, and build Tux Paint on an old version
of macOS.
-------------------------------------------------------
Old Versions of macOS
Some old versions of macOS can be downloaded from Apple's support
page: https://support.apple.com/en-us/HT211683
macOS does allow dual booting of multiple versions of the OS, but
it's safer and easier to install the old macOS onto a flash drive.
Wherever you're installing it, the target drive's partitioniong
scheme and partition type must match what the old macOS expects, so
use the Disk Utility to partition and format the flash drive
accordingly.
As of this writing, the oldest version of macOS available on Apple's
support site is Yosemite 10.10, which expects "GPT (GUID Partition
Table)" partitioning scheme instead of the older MBR scheme, and
"Mac OS Extended (Journaled)" as the partition type instead of the
newer APFS partition type.
Upon launching the installer, if you get a popup about macOS being
too old or new to be installed, a bootable installer can be created
using the instructions found here:
https://support.apple.com/en-mide/HT201372
It has been found that macOS can be installed onto the bootable
media itself, so you can make the flash drive into a bootable
installer then install the old macOS onto the same flash drive.
Once the old macOS is installed, you may find the Xcode on the App
Store is too new to run on the version of the old macOS. Old
versions of Xcode can be downloaded from Apple's Developer site in
an area accessible with free registration:
https://developer.apple.com/download/more/
The list of macOS versions and the last version of Xcode compatible
with them are laid out nicely on the Wikipedia page on Xcode:
https://en.wikipedia.org/wiki/Xcode#Version_comparison_table
And because Xcode is being installed manually, you can skip the step
to install the Xcode command line tools (do not run "xcode-select
--install") but otherwise build Tux Paint using the same steps
described in the earlier part of this document.
----------------------------------------------------------------------
Debugging
Debugging output — to "STDOUT" on Linux and Unix, to a "stdout.txt" file
on Windows, and to the file "/tmp/tuxpaint.log" on macOS — can be
enabled by setting "DEBUG" (and, if verbose logging is wanted,
"VERBOSE") #defines in "src/debug.h" and (re)compiling Tux Paint.
----------------------------------------------------------------------
Uninstalling Tux Paint
Windows
@ -376,6 +760,18 @@ Uninstalling Tux Paint:
It is also possible to use the entry "TuxPaint (remove only)" in the
Control Panel Add/Remove programs section.
----------------------------------------------------------------------
macOS
Delete "TuxPaint.app" from the "Applications" folder. Data files,
including the configuration files, stamps, and saved pictures, may be
found in "Library/Application Support/TuxPaint" (all users) and
"/Users/USERNAME/Library/Application Support/TuxPaint" (individual
users).
----------------------------------------------------------------------
Linux
Within the Tux Paint source directory (where you compiled Tux Paint),

1563
docs/ja_JP.UTF-8/OPTIONS.txt
View file

File diff suppressed because it is too large Load diff

2
docs/ja_JP.UTF-8/PNG.txt
View file

@ -1,5 +1,5 @@
Tux Paint
バージョン 0.9.26
バージョン 0.9.27
PNG Documentation
Copyright © 2007-2021 by various contributors; "AUTHORS" 参照.

26
docs/ja_JP.UTF-8/README.txt
View file

@ -1,12 +1,12 @@
Tux Paint
バージョン 0.9.26
バージョン 0.9.27
子供向けのシンプルなお絵かきプログラム
Copyright © 2002-2021 by various contributors; "AUTHORS" 参照.
http://www.tuxpaint.org/
2021年6月28日
2021年9月 5日
----------------------------------------------------------------------
@ -172,6 +172,22 @@ Tux Paint の起動
ボタンを押したままマウスを動かすと、描画できます。
Some brushes are animated — they change their shape as you
draw them. A good example of this is the vines brush that
ships with Tux Paint. These brushes will have a small
"filmstrip" icon drawn on their Selector buttons.
Other brushes are directional — they will draw a different
shape depending on what direction you are painting with
them. An example of this is the arrow brush that ships with
Tux Paint. These brushes have a small 8-way arrow icon drawn
on their Selector buttons.
Finally, some brushes can be both direction and animated.
Examples of this are the cat and squirrel brushes that ship
with Tux Paint. These brushes will have both the "filmstrip"
and 8-way arrow icons.
描画中にはサウンドが流れます。筆の大きさが大きいほど、低い音になります。
----------------------------------------------------------------------
@ -206,6 +222,12 @@ Tux Paint の起動
マウスを放すと、バネのような効果音とともに線が描画されます。
Some brushes are animated, and will show a pattern of shapes
along the line. Others are directional, and will show a
different shape depending on the angle of the brush. And
finally some are both animated and directional. See "Paint",
above, to learn more.
----------------------------------------------------------------------
「かたち」ツール

2
docs/ja_JP.UTF-8/SIGNALS.txt
View file

@ -1,5 +1,5 @@
Tux Paint
バージョン 0.9.26
バージョン 0.9.27
Signals Documentation
Copyright © 2019-2021 by various contributors; "AUTHORS" 参照.

2
docs/ja_JP.UTF-8/SVG.txt
View file

@ -1,5 +1,5 @@
Tux Paint
バージョン 0.9.26
バージョン 0.9.27
SVG Documentation
Copyright © 2007-2021 by various contributors; "AUTHORS" 参照.

81
docs/ja_JP.UTF-8/html/ADVANCED-STAMPS-HOWTO.html
View file

@ -17,16 +17,62 @@
width="205"
height="210"
alt="Tux Paint"><br>
バージョン 0.9.26 スタンプ作成の詳細について </h1>
バージョン 0.9.27 スタンプ作成の詳細について </h1>
<p>
Copyright &copy; 2006-2021 by Albert Cahalan ほか; "AUTHORS" 参照.<br>
<a href="http://www.tuxpaint.org/">http://www.tuxpaint.org/</a>
</p>
<p>
2021年8月29日 </p>
</center>
<hr size="2"
noshade>
<table border="2"
cellspacing="0"
cellpadding="2"
summary="目次">
<tr>
<th>
目次 </th>
</tr>
<tr>
<td>
<ul>
<li>
<a href="#about">この解説について</a>
</li>
<li>
<a href="#choice">使用する画像の選択</a>
</li>
<li>
<a href="#prepare_mask">マスクの設定</a>
</li>
<li>
<a href="#replace_fringe">縁取りと不要なピクセルの除去</a>
</li>
<li>
<a href="#save">Tux Paint 用の画像の保存</a>
</li>
</ul>
</td>
</tr>
</table>
<hr size="2"
noshade>
<hr size="2"
noshade>
<h2>
この解説について </h2>
<a name="about" id="about">
この解説について </a>
</h2>
<blockquote>
<p>
@ -36,8 +82,13 @@
扱う対象としては、通常の透明ではないものを前提としており、半透明のもの（火、動く扇風機の羽根、風船）や発光するもの（火、電球、太陽）を扱うには、専用のソフトウェアを使用するのが最適です。背景が完全なベタ塗りの画像も、専用のソフトを使うのが良いですが、以下のようにしても問題はありません。 </p>
</blockquote>
<hr size="2"
noshade>
<h2>
使用する画像の選択 </h2>
<a name="choice" id="choice">
使用する画像の選択 </a>
</h2>
<blockquote>
<h3>
@ -78,6 +129,9 @@
</blockquote>
</blockquote>
<hr size="2"
noshade>
<h2>
画像の準備 </h2>
@ -116,8 +170,13 @@
<b>注意：</b>マスクを設定した後は、画像の回転や拡大縮小は行えません。これはデータ損失の原因となります。サイズを調整するための特別な方法は後述します。 </p>
</blockquote>
<hr size="2"
noshade>
<h2>
マスクの設定 </h2>
<a name="prepare_mask" id="prepare_mask">
マスクの設定 </a>
</h2>
<blockquote>
<p>
@ -151,8 +210,13 @@
マスクを表示して編集します。黒か白の色で領域を選択します。ほとんどの場合、選択されていない色の斑点が残っていると思います。選択範囲を反転させ、鉛筆ツールを使ってこれらの点を取り除きます。この作業を白と黒の両方で行います。 </p>
</blockquote>
<hr size="2"
noshade>
<h2>
縁取りと不要なピクセルの除去 </h2>
<a name="replace_fringe" id="replace_fringe">
縁取りと不要なピクセルの除去 </a>
</h2>
<blockquote>
<p>
@ -188,8 +252,13 @@
タックスペイントでは、画像を非常に大きく縮小することができるため、オブジェクトの輪郭を外側に大きく広げることが重要です。オブジェクトの輪郭の部分では、非常に正確に処理する必要がありますが、輪郭から離れるにつれて、少々手を抜いても大丈夫です。十数ピクセル以上外側まで描くとちょうど良くなります。これを太くすればするだけ、Tux Paintは汚い色の縁どりを発生させずにスケールダウンすることができます。オブジェクトの端から数ピクセル以上離れた部分については、鉛筆ツール（またはドラッグ＆ドロップで適当に色を選択）を使用して、結果がきれいに縮小されるようにしてください。 </p>
</blockquote>
<hr size="2"
noshade>
<h2>
Tux Paint 用の画像の保存 </h2>
<a name="save" id="save">
Tux Paint 用の画像の保存 </a>
</h2>
<blockquote>
<p>

4
docs/ja_JP.UTF-8/html/ENVVARS.html
View file

@ -17,7 +17,7 @@
width="205"
height="210"
alt="Tux Paint"><br>
バージョン 0.9.26<br/>
バージョン 0.9.27<br/>
Environment Variables Documentation </h1>
<p>
@ -26,7 +26,7 @@
</p>
<p>
2021年5月11日 </p>
2021年8月 8日 </p>
</center>
<hr>

Some files were not shown because too many files have changed in this diff Show more