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

Mentioned FontForge, as per

Browse source 
http://sourceforge.net/mailarchive/message.php?msg_id=12383130
Moved some less important FAQ items down.
This commit is contained in:
William Kendrick 2005-10-09 22:15:30 +00:00
parent 63e9dcb656
commit c94ed6af40
2 changed files with 408 additions and 381 deletions
Download patch file Download diff file Expand all files Collapse all files

290
docs/FAQ.txt
View file

@ -12,12 +12,44 @@
Drawing-related
* Fonts I added to Tux Paint only show squares
The TrueType Font you're using might have the wrong encoding. If it's
'custom' encoded, for example, you can try running it through FontForge
(http://fontforge.sourceforge.net/) to convert it to an ISO-8859 format.
(Email us if you need help with special fonts.)
* The Rubber Stamp tool is greyed out!
This means that Tux Paint either couldn't find any stamp images, or was
asked not to load them.
If you installed Tux Paint, but did not install the separate, optional
"Stamps" collection, quit Tux Paint and install it now. It should be
available from the same place you got the main Tux Paint program. (Note:
As of version 0.9.14, Tux Paint comes with a small collection of example
stamps.)
If you don't want to install the default collection of stamps, you can
just create your own. See the README documentation for more on creating
PNG image files, TXT text description files, WAV sound files, and DAT
text data files that make up stamps.
Finally, if you install the stamps, and think they should be loading,
check to see that the "nostamps" option isn't being set. (Either via a
"--nostamps" option to Tux Paint's command line, or "nostamps=yes" in
the configuration file.)
If so, either change/remove the "nostamps" option, or you can override
it with "--stamps" on the command line or "nostamps=no" or "stamps=yes"
in a configuration file.
* The Magic "Fill" Tool Looks Bad
Tux Paint is probably comparing exact pixel colors when filling. This
is faster, but looks worse. Run the command "tuxpaint --version" from
a command line, and you should see, amongst the other output: "Low
Quality Flood Fill enabled".
Tux Paint is probably comparing exact pixel colors when filling.
This is faster, but looks worse. Run the command "tuxpaint
--version" from a command line, and you should see, amongst the
other output: "Low Quality Flood Fill enabled".
To change this, you must rebuild Tux Paint from source. Be sure to
remove or comment out any line that says:
@ -37,31 +69,6 @@ Drawing-related
in the "tuxpaint.c" file in the "src" directory.
* The Rubber Stamp tool is greyed out!
This means that Tux Paint either couldn't find any stamp images, or
was asked not to load them.
If you installed Tux Paint, but did not install the separate, optional
"Stamps" collection, quit Tux Paint and install it now. It should be
available from the same place you got the main Tux Paint program.
(Note: As of version 0.9.14, Tux Paint comes with a small collection
of example stamps.)
If you don't want to install the default collection of stamps, you can
just create your own. See the README documentation for more on
creating PNG image files, TXT text description files, WAV sound files,
and DAT text data files that make up stamps.
Finally, if you install the stamps, and think they should be loading,
check to see that the "nostamps" option isn't being set. (Either via a
"--nostamps" option to Tux Paint's command line, or "nostamps=yes" in
the configuration file.)
If so, either change/remove the "nostamps" option, or you can override
it with "--stamps" on the command line or "nostamps=no" or
"stamps=yes" in a configuration file.
Interface Problems
* Stamp thumbnails in the Stamp Selector look bad
@ -86,9 +93,9 @@ Interface Problems
* The color picker buttons are ugly squares, not pretty buttons!
Tux Paint was probably compiled with the nice looking color selector
buttons disabled. Run the command: "tuxpaint --version" from a command
line. If, amongst the other output, you see the text: "Low Quality
Color Selector enabled", then this is what's happening.
buttons disabled. Run the command: "tuxpaint --version" from a
command line. If, amongst the other output, you see the text: "Low
Quality Color Selector enabled", then this is what's happening.
Rebuild Tux Paint from source. Be sure to remove or comment out any
line that says:
@ -101,27 +108,29 @@ Interface Problems
The "uppercase" option is on.
If you're running Tux Paint from a command-line, make sure you're not
giving it an "--uppercase" option.
If you're running Tux Paint from a command-line, make sure you're
not giving it an "--uppercase" option.
If you're running Tux Paint by double-clicking an icon, check the
properties of the icon to see if "--uppercase" is listed as a
command-line argument.
If "--uppercase" isn't being sent on the command line, check
Tux Paint's configuration file ("~/.tuxpaintrc" under Linux and Unix,
"tuxpaint.cfg" under Windows) for a line reading: "uppercase=yes".
Tux Paint's configuration file ("~/.tuxpaintrc" under Linux and
Unix, "tuxpaint.cfg" under Windows) for a line reading:
"uppercase=yes".
Either remove that line, or simply run Tux Paint with the command-line
argument: "--mixedcase", which will override the uppercase setting.
Either remove that line, or simply run Tux Paint with the
command-line argument: "--mixedcase", which will override the
uppercase setting.
Or use Tux Paint Config. and make sure "Show Uppercase Text Only"
(under "Languages") is not checked.
* Tux Paint is in a different language!
Make sure your locale setting is correct. See "Tux Paint won't switch
to my language", below.
Make sure your locale setting is correct. See "Tux Paint won't
switch to my language", below.
* Tux Paint won't switch to my language
@ -155,8 +164,9 @@ Interface Problems
* Make sure you have the necessary font
Some translations require their own font. Chinese and
Korean, for example, need Chinese and Korean TrueType Fonts
installed and placed in the proper location, respectively.
Korean, for example, need Chinese and Korean TrueType
Fonts installed and placed in the proper location,
respectively.
The appropriate fonts for such locales can be downloaded
from the Tux Paint website:
@ -165,21 +175,22 @@ Interface Problems
Printing
* Tux Paint won't print, gives an error, or prints garbage (Unix/Linux)
* Tux Paint won't print, gives an error, or prints garbage
(Unix/Linux)
Tux Paint prints by creating a PostScript rendition of the picture and
sending it to an external command. By default, this command is the
"lpr" printing tool.
Tux Paint prints by creating a PostScript rendition of the picture
and sending it to an external command. By default, this command is
the "lpr" printing tool.
If that program is not available (for example, you're using CUPS, the
Common Unix Printing System, and do not have "cups-lpr" installed),
you will need to specify an appropriate command using the
"printcommand" option in Tux Paint's configuration file. (See the
OPTIONS documentation.)
If that program is not available (for example, you're using CUPS,
the Common Unix Printing System, and do not have "cups-lpr"
installed), you will need to specify an appropriate command using
the "printcommand" option in Tux Paint's configuration file. (See
the OPTIONS documentation.)
Note: Versions of Tux Paint prior to 0.9.15 used a different default
command for printing, "pngtopnm | pnmtops | lpr", as Tux Paint output
PNG format, rather than PostScript.
command for printing, "pngtopnm | pnmtops | lpr", as Tux Paint
output PNG format, rather than PostScript.
If you had changed your "printcommand" option prior to Tux Paint
0.9.15, you will need to go back and alter it to accept PostScript.
@ -189,16 +200,16 @@ Printing
The "print delay" option is on. You can only print once every
X seconds.
If you're running Tux Paint from a command-line, make sure you're not
giving it a "--printdelay=..." option.
If you're running Tux Paint from a command-line, make sure you're
not giving it a "--printdelay=..." option.
If you're running Tux Paint by double-clicking an icon, check the
properties of the icon to see if "--printdelay=..." is listed as a
command-line argument.
If a "--printdelay=..." option isn't being sent on the command line,
check Tux Paint's configuration file ("~/.tuxpaintrc" under Linux and
Unix, "tuxpaint.cfg" under Windows) for a line reading:
check Tux Paint's configuration file ("~/.tuxpaintrc" under Linux
and Unix, "tuxpaint.cfg" under Windows) for a line reading:
"printdelay=...".
Either remove that line, set the delay value to 0 (no delay), or
@ -207,8 +218,8 @@ Printing
Or, you can simply run Tux Paint with the command-line argument:
"--printdelay=0", which will override the configuration file's
setting, and allow unlimited printing. (You won't have to wait between
prints.)
setting, and allow unlimited printing. (You won't have to wait
between prints.)
Or use Tux Paint Config. and make sure "Print Delay" (under
"Printing") is set to "0 seconds."
@ -217,19 +228,20 @@ Printing
The "no print" option is on.
If you're running Tux Paint from a command-line, make sure you're not
giving it a "--noprint" option.
If you're running Tux Paint from a command-line, make sure you're
not giving it a "--noprint" option.
If you're running Tux Paint by double-clicking an icon, check the
properties of the icon to see if "--noprint" is listed as an argument.
properties of the icon to see if "--noprint" is listed as an
argument.
If "--noprint" isn't on the command-line, check Tux Paint's
configuration file ("~/.tuxpaintrc" under Linux and Unix,
"tuxpaint.cfg" under Windows) for a line reading: "noprint=yes".
Either remove that line, or simply run Tux Paint with the command-line
argument: "--print", which will override the configuration file's
setting.
Either remove that line, or simply run Tux Paint with the
command-line argument: "--print", which will override the
configuration file's setting.
Or use Tux Paint Config. and make sure "Allow Printing" (under
"Printing") is checked.
@ -241,8 +253,8 @@ Saving
The "save over" option is enabled. (This disables the prompt that
would appear when you click 'Save.')
If you're running Tux Paint from a command-line, make sure you're not
giving it a "--saveover" option.
If you're running Tux Paint from a command-line, make sure you're
not giving it a "--saveover" option.
If you're running Tux Paint by double-clicking an icon, check the
properties of the icon to see if "--saveover" is listed as an
@ -252,12 +264,12 @@ Saving
configuration file ("~/.tuxpaintrc" under Linux and Unix,
"tuxpaint.cfg" under Windows) for a line reading: "saveover=yes".
Either remove that line, or simply run Tux Paint with the command-line
argument: "--saveoverask", which will override the configuration
file's setting.
Either remove that line, or simply run Tux Paint with the
command-line argument: "--saveoverask", which will override the
configuration file's setting.
Or use Tux Paint Config. and make sure "Ask Before Overwriting" (under
"Saving") is checked.
Or use Tux Paint Config. and make sure "Ask Before Overwriting"
(under "Saving") is checked.
Also, see "Tux Paint always saves a new picture!", below.
@ -266,8 +278,8 @@ Saving
The "never save over" option is enabled. (This disables the prompt
that would appear when you click 'Save.')
If you're running Tux Paint from a command-line, make sure you're not
giving it a "--saveovernew" option.
If you're running Tux Paint from a command-line, make sure you're
not giving it a "--saveovernew" option.
If you're running Tux Paint by double-clicking an icon, check the
properties of the icon to see if "--saveovernew" is listed as an
@ -277,12 +289,12 @@ Saving
configuration file ("~/.tuxpaintrc" under Linux and Unix,
"tuxpaint.cfg" under Windows) for a line reading: "saveover=new".
Either remove that line, or simply run Tux Paint with the command-line
argument: "--saveoverask", which will override the configuration
file's setting.
Either remove that line, or simply run Tux Paint with the
command-line argument: "--saveoverask", which will override the
configuration file's setting.
Or use Tux Paint Config. and make sure "Ask Before Overwriting" (under
"Saving") is checked.
Or use Tux Paint Config. and make sure "Ask Before Overwriting"
(under "Saving") is checked.
Also, see "Tux Paint always saves over my old picture!", above.
@ -305,33 +317,33 @@ Audio Problems
system's rerouter (e.g., run "artsdsp tuxpaint" or
"esddsp tuxpaint", instead of simply "tuxpaint").
If sound seems to work otherwise (and you're sure no other program is
"blocking" the sound device), then Tux Paint is either running with a
"no sound" option or was compiled with sound support disabled
If sound seems to work otherwise (and you're sure no other program
is "blocking" the sound device), then Tux Paint is either running
with a "no sound" option or was compiled with sound support disabled
entirely.
To test whether sound support was enabled when Tux Paint was compiled,
run Tux Paint from a command line, like so:
To test whether sound support was enabled when Tux Paint was
compiled, run Tux Paint from a command line, like so:
tuxpaint --version
If, amongst the other information, you see "Sound disabled", then the
version of Tux Paint you're running has sound disabled. Recompile
Tux Paint, and be sure NOT to build the "nosound" target. (i.e., don't
run "make nosound") Be sure the SDL_mixer library and its development
headers are available!
If, amongst the other information, you see "Sound disabled", then
the version of Tux Paint you're running has sound disabled.
Recompile Tux Paint, and be sure NOT to build the "nosound" target.
(i.e., don't run "make nosound") Be sure the SDL_mixer library and
its development headers are available!
If Tux Paint wasn't build without sound support, make sure you're not
running Tux Paint with the "--nosound" option as a command-line
If Tux Paint wasn't build without sound support, make sure you're
not running Tux Paint with the "--nosound" option as a command-line
argument.
If it's not, then check the configuration file ("~/.tuxpaintrc" under
Linux and Unix, and "tuxpaint.cfg" under Windows) for a line reading:
"nosound=yes".
If it's not, then check the configuration file ("~/.tuxpaintrc"
under Linux and Unix, and "tuxpaint.cfg" under Windows) for a line
reading: "nosound=yes".
Either remove that line, or simply run Tux Paint with the command-line
argument: "--sound", which will override the configuration file's
setting.
Either remove that line, or simply run Tux Paint with the
command-line argument: "--sound", which will override the
configuration file's setting.
Or use Tux Paint Config. and make sure "Enable Sound Effects" (under
"Video & Sound") is checked.
@ -356,21 +368,23 @@ Fullscreen Mode Problems
Linux users - Your X-Window server is probably not set with the
ability to switch to the desired resolution: 800×600. (or whatever
resolution you have Tux Paint set to run at.) (This is typically done
manually under the X-Window server by pressing [Ctrl]-[Alt]-[KeyPad
Plus] and -[KeyPad Minus].)
resolution you have Tux Paint set to run at.) (This is typically
done manually under the X-Window server by pressing
[Ctrl]-[Alt]-[KeyPad Plus] and -[KeyPad Minus].)
For this to work, your monitor must support that resolution, and you
need to have it listed in your X server configuration.
Check the "Display" subsection of the "Screen" section of your XFree86
or X.org configuration file (typically "/etc/X11/XF86Config-4" or
"/etc/X11/XF86Config", depending on the version of XFree86 you're
using; 3.x or 4.x, respectively, or "/etc/X11/xorg.conf" for X.org).
Check the "Display" subsection of the "Screen" section of your
XFree86 or X.org configuration file (typically
"/etc/X11/XF86Config-4" or "/etc/X11/XF86Config", depending on the
version of XFree86 you're using; 3.x or 4.x, respectively, or
"/etc/X11/xorg.conf" for X.org).
Add "800x600" (or whatever resolution(s) you want) to the appropriate
"Modes" line. (e.g., in the "Display" subsection that contains 24-bit
color depth ("Depth 24"), which is what Tux Paint tries to use.) e.g.:
Add "800x600" (or whatever resolution(s) you want) to the
appropriate "Modes" line. (e.g., in the "Display" subsection that
contains 24-bit color depth ("Depth 24"), which is what Tux Paint
tries to use.) e.g.:
Modes "1280x1024" "1024x768" "800x600" "640x480"
@ -382,8 +396,8 @@ Fullscreen Mode Problems
The "fullscreen" option is set.
If you're running Tux Paint from a command-line, make sure you're not
giving it a "--fullscreen" option.
If you're running Tux Paint from a command-line, make sure you're
not giving it a "--fullscreen" option.
If you're running Tux Paint by double-clicking an icon, check the
properties of the icon to see if "--fullscreen" is listed as an
@ -393,9 +407,9 @@ Fullscreen Mode Problems
configuration file ("~/.tuxpaintrc" under Linux and Unix,
"tuxpaint.cfg" under Windows) for a line reading: "fullscreen=yes".
Either remove that line, or simply run Tux Paint with the command-line
argument: "--windowed", which will override the configuration file's
setting.
Either remove that line, or simply run Tux Paint with the
command-line argument: "--windowed", which will override the
configuration file's setting.
Or use Tux Paint Config. and make sure "Fullscreen" (under "Video &
Sound") is not checked.
@ -416,13 +430,13 @@ Other Probelms
isn't run too many times at once (e.g., due to a child impatiently
clicking its icon more than once).
Even if the lockfile exists, it contains the 'time' Tux Paint was last
run. If it's been more than 30 seconds, Tux Paint should run fine, and
simply update the lockfile with the current time.
Even if the lockfile exists, it contains the 'time' Tux Paint was
last run. If it's been more than 30 seconds, Tux Paint should run
fine, and simply update the lockfile with the current time.
If multiple users are sharing the directory where this file is stored
(e.g., on a shared network drive), then you'll need to disable this
feature.
If multiple users are sharing the directory where this file is
stored (e.g., on a shared network drive), then you'll need to
disable this feature.
To disable the lockfile, add the "--nolockfile" argument to
Tux Paint's command-line.
@ -433,40 +447,43 @@ Other Probelms
Tux Paint's toolbar (greying it out), and prevents Tux Paint from
being quit using the [Escape] key.
If Tux Paint is not in fullscreen mode, simply click the window close
button on Tux Paint's title bar. (i.e., the "(x)" at the upper right.)
If Tux Paint is not in fullscreen mode, simply click the window
close button on Tux Paint's title bar. (i.e., the "(x)" at the upper
right.)
If Tux Paint is in fullscreen mode, you will need to use the [Shift] +
[Control] + [Escape] sequence on the keyboard to quit Tux Paint.
If Tux Paint is in fullscreen mode, you will need to use the [Shift]
+ [Control] + [Escape] sequence on the keyboard to quit Tux Paint.
(Note: with or without "noquit" set, you can always use the [Alt] +
[F4] combination on your keyboard to quit Tux Paint.)
* I don't want "noquit" mode enabled!
If you're running Tux Paint from a command-line, make sure you're not
giving it a "--noquit" option.
If you're running Tux Paint from a command-line, make sure you're
not giving it a "--noquit" option.
If you're running Tux Paint by double-clicking an icon, check the
properties of the icon to see if "--noquit" is listed as an argument.
properties of the icon to see if "--noquit" is listed as an
argument.
If "--noquit" isn't on the command-line, check Tux Paint's
configuration file ("~/.tuxpaintrc" under Linux and Unix,
"tuxpaint.cfg" under Windows) for a line reading: "noquit=yes".
Either remove that line, or simply run Tux Paint with the command-line
argument: "--quit", which will override the configuration file's
setting.
Either remove that line, or simply run Tux Paint with the
command-line argument: "--quit", which will override the
configuration file's setting.
Or use Tux Paint Config. and make sure "Disable Quit Button and
[Escape] Key" (under "Simplification") is not checked.
* Tux Paint keeps writing weird messages to the screen / to a text file
* Tux Paint keeps writing weird messages to the screen / to a text
file
A few messages are normal, but if Tux Paint is being extremely verbose
(like listing the name of every rubber-stamp image it finds while
loading them), then it was probably compiled with debugging output
turned on.
A few messages are normal, but if Tux Paint is being extremely
verbose (like listing the name of every rubber-stamp image it finds
while loading them), then it was probably compiled with debugging
output turned on.
Rebuild Tux Paint from source. Be sure to remove or comment out any
line that says:
@ -477,7 +494,8 @@ Other Probelms
* Tux Paint is using options I didn't specify!
By default, Tux Paint first looks at configuration files for options.
By default, Tux Paint first looks at configuration files for
options.
* Unix and Linux
@ -501,8 +519,8 @@ Other Probelms
Then, any options sent as command-line arguments are used.
This means that if anything is set in a configuration file that you
don't want set, you'll need to either change the config. file (if you
can), or override the option on the command-line.
don't want set, you'll need to either change the config. file (if
you can), or override the option on the command-line.
For example, if "/etc/tuxpaint/tuxpaint.conf" includes an option to
disable sound:

61
docs/html/FAQ.html
View file

@ -28,6 +28,41 @@ com/tuxpaint/</a></p>
<h2>Drawing-related</h2>
<li><em>Fonts I added to Tux&nbsp;Paint only show squares</em>
<p>The TrueType Font you're using might have the wrong encoding.
If it's 'custom' encoded, for example, you can try running it through
FontForge
(<a href="http://fontforge.sourceforge.net/"
>http://fontforge.sourceforge.net/</a>) to convert it to an
ISO-8859 format. (Email us if you need help with special fonts.)</p>
<li><em>The Rubber Stamp tool is greyed out!</em>
<p>This means that Tux&nbsp;Paint either couldn't find any stamp images,
or was asked not to load them.</p>
<p>If you installed Tux&nbsp;Paint, but did not install the separate,
optional "Stamps" collection, quit Tux&nbsp;Paint and install it now.
It should be available from the same place you got the main
Tux&nbsp;Paint program. <i>(Note: As of version 0.9.14, Tux&nbsp;Paint
comes with a small collection of example stamps.)</i></p>
<p>If you don't want to install the default collection of stamps,
you can just create your own. See the <a href="README.html">README
documentation</a> for more on creating PNG image files, TXT text
description files, WAV sound files, and DAT text data files that
make up stamps.</p>
<p>Finally, if you install the stamps, and think they should be loading,
check to see that the "nostamps" option isn't being set.
(Either via a "--nostamps" option to Tux&nbsp;Paint's command line, or
"nostamps=yes" in the configuration file.)</p>
<p>If so, either change/remove the "nostamps" option, or you can
override it with "--stamps" on the command line or
"nostamps=no" or "stamps=yes" in a configuration file.</p>
</li>
<ul>
<li><em>The Magic "Fill" Tool Looks Bad</em>
<p>Tux&nbsp;Paint is probably comparing exact pixel colors when filling.
@ -57,32 +92,6 @@ com/tuxpaint/</a></p>
<p>in the "tuxpaint.c" file in the "src" directory.</p>
</li>
<li><em>The Rubber Stamp tool is greyed out!</em>
<p>This means that Tux&nbsp;Paint either couldn't find any stamp images,
or was asked not to load them.</p>
<p>If you installed Tux&nbsp;Paint, but did not install the separate,
optional "Stamps" collection, quit Tux&nbsp;Paint and install it now.
It should be available from the same place you got the main
Tux&nbsp;Paint program. <i>(Note: As of version 0.9.14, Tux&nbsp;Paint
comes with a small collection of example stamps.)</i></p>
<p>If you don't want to install the default collection of stamps,
you can just create your own. See the <a href="README.html">README
documentation</a> for more on creating PNG image files, TXT text
description files, WAV sound files, and DAT text data files that
make up stamps.</p>
<p>Finally, if you install the stamps, and think they should be loading,
check to see that the "nostamps" option isn't being set.
(Either via a "--nostamps" option to Tux&nbsp;Paint's command line, or
"nostamps=yes" in the configuration file.)</p>
<p>If so, either change/remove the "nostamps" option, or you can
override it with "--stamps" on the command line or
"nostamps=no" or "stamps=yes" in a configuration file.</p>
</li>
</ul>
<h2>Interface Problems</h2>