[gimp-web/gimp-web-static] Added pre-generated .html files from /unix dir
- From: Pat David <patdavid src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [gimp-web/gimp-web-static] Added pre-generated .html files from /unix dir
- Date: Mon, 5 Oct 2015 17:34:51 +0000 (UTC)
commit 3e5b8d7e8d8313f35f5cf03c289c41dc450efe84
Author: Pat David <patdavid gmail com>
Date: Mon Oct 5 12:34:41 2015 -0500
Added pre-generated .html files from /unix dir
content/about/meta/file-list.md | 16 +-
content/tutorials/Film_Grain/index.md | 2 +-
content/tutorials/Smart_Sharpening/index.md | 2 +-
content/unix/gimprc.html | 7 +
content/unix/gtkrc | 40 ++
content/unix/gtkrc.html | 7 +
content/unix/howtos/bugzilla.htrw | 219 ++++++++
content/unix/howtos/bugzilla.md | 62 ++
content/unix/howtos/gimp-midi.htrw | 109 ++++
content/unix/howtos/gimp-midi.md | 49 ++
content/unix/howtos/howto-template.htrw | 68 +++
content/unix/howtos/tile_cache.htrw | 212 +++++++
content/unix/howtos/tile_cache.md | 60 ++
content/unix/man-gimp-2.0.html | 408 ++++++++++++++
content/unix/man-gimp-remote-2.0.html | 130 +++++
content/unix/man-gimprc-2.0.html | 803 +++++++++++++++++++++++++++
content/unix/man-gimptool-2.0.html | 321 +++++++++++
content/unix/ui-calibrate.png | Bin 0 -> 17616 bytes
content/unix/ui-log.png | Bin 0 -> 53359 bytes
content/unix/ui-monitor.png | Bin 0 -> 35994 bytes
content/unix/ui-performance.png | Bin 0 -> 36637 bytes
content/unix/ui-personal.png | Bin 0 -> 34579 bytes
content/unix/ui-welcome.png | Bin 0 -> 43644 bytes
23 files changed, 2505 insertions(+), 10 deletions(-)
---
diff --git a/content/about/meta/file-list.md b/content/about/meta/file-list.md
index 579d495..e8f1fca 100644
--- a/content/about/meta/file-list.md
+++ b/content/about/meta/file-list.md
@@ -222,14 +222,14 @@ The main page links go to legacy WGO, the link icon (if there) will go to the po
<del><http://www.gimp.org/unix/gimprc.html></del> [<i class="fa
fa-link"></i>]({filename}../../unix/gimprc.md)
<http://www.gimp.org/unix/gtkrc.html>
<http://www.gimp.org/unix/index.html> (Obsoleted? Directs to downloads page...)
-<http://www.gimp.org/unix/man-gimp-2.0.html>
-<http://www.gimp.org/unix/man-gimprc-2.0.html>
-<http://www.gimp.org/unix/man-gimp-remote-2.0.html>
-<http://www.gimp.org/unix/man-gimptool-2.0.html>
+<del><http://www.gimp.org/unix/man-gimp-2.0.html></del> [<i class="fa
fa-link"></i>]({filename}../../unix/man-gimp-2.0.html)
+<del><http://www.gimp.org/unix/man-gimprc-2.0.html></del> [<i class="fa
fa-link"></i>]({filename}../../unix/man-gimprc-2.0.html)
+<del><http://www.gimp.org/unix/man-gimp-remote-2.0.html></del> [<i class="fa
fa-link"></i>]({filename}../../unix/man-gimp-remote-2.0.html)
+<del><http://www.gimp.org/unix/man-gimptool-2.0.html></del> [<i class="fa
fa-link"></i>]({filename}../../unix/man-gimptool-2.0.html)
<http://www.gimp.org/unix/user_install.html>
-<http://www.gimp.org/unix/howtos/bugzilla.html>
-<http://www.gimp.org/unix/howtos/gimp-midi.html>
-<http://www.gimp.org/unix/howtos/howto-template.html>
-<http://www.gimp.org/unix/howtos/tile_cache.html>
+<del><http://www.gimp.org/unix/howtos/bugzilla.html></del> [<i class="fa
fa-link"></i>]({filename}../../unix/howtos/bugzilla.md)
+<del><http://www.gimp.org/unix/howtos/gimp-midi.html> </del> [<i class="fa
fa-link"></i>]({filename}../../unix/howtos/gimp-midi.md)
+<del><http://www.gimp.org/unix/howtos/howto-template.html> </del> [<i class="fa
fa-link"></i>]({filename}../../unix/fonts.md)
+<del><http://www.gimp.org/unix/howtos/tile_cache.html> </del> [<i class="fa
fa-link"></i>]({filename}../../unix/howtos/tile_cache.md)
<http://www.gimp.org/windows/index.html> (Obsoleted? Directs to downloads page...)
diff --git a/content/tutorials/Film_Grain/index.md b/content/tutorials/Film_Grain/index.md
index 3914aaf..8dc07b5 100644
--- a/content/tutorials/Film_Grain/index.md
+++ b/content/tutorials/Film_Grain/index.md
@@ -24,7 +24,7 @@ This is a subject for another, longer tutorial. But here are the basic steps:
5. Flatten the image.
6. Choose an interesting area of the noise, and make it into a tileable pattern.
-([GIMP pattern file](film-grain-vertical.pat))
+([GIMP pattern file](film-grain-vertical.pat))
Some good ways of making tileable patterns include **Make Seamless**, the [Resynthesizer and
Homogenizer](http://www.logarithmic.net/pfh/resynthesizer/), mirroring, and hand-editing. You'll have to
experiment a bit. In the following example, we'll use a weird, vertically-striped noise pattern. It looks
like some kind of scanner noise, or perhaps an artifact of old newsprint.
diff --git a/content/tutorials/Smart_Sharpening/index.md b/content/tutorials/Smart_Sharpening/index.md
index e1ff700..91f3a45 100644
--- a/content/tutorials/Smart_Sharpening/index.md
+++ b/content/tutorials/Smart_Sharpening/index.md
@@ -142,7 +142,7 @@ Select the Layers tab in the Layers dialog and click on the anchor button (). You should see "marching ants".
+Select the Sharpening Mask channel and click the "Channel to Selection" button
(). You should see "marching ants".
You can experiment with feathering the selection here if you want; I usually don't.
diff --git a/content/unix/gimprc.html b/content/unix/gimprc.html
new file mode 100644
index 0000000..eb6d861
--- /dev/null
+++ b/content/unix/gimprc.html
@@ -0,0 +1,7 @@
+<html>
+<body>
+<pre>
+<!--#include virtual="gimprc" -->
+</pre>
+</body>
+</html>
diff --git a/content/unix/gtkrc b/content/unix/gtkrc
new file mode 100644
index 0000000..3fd69ee
--- /dev/null
+++ b/content/unix/gtkrc
@@ -0,0 +1,40 @@
+# pixmap_path "<dir 1>:<dir 2>:<dir 3>:..."
+#
+# include "rc-file"
+#
+# style <name> [= <name>]
+# {
+# <option>
+# }
+#
+# widget <widget_set> style <style_name>
+# class <widget_class_set> style <style_name>
+#
+# You can add your own GIMP-specific GTK styles here.
+
+
+#
+# Example keybinding to remap Help to F2
+#
+binding "gimp-help-binding"
+{
+ bind "F2" { "show-help" (255) }
+ bind "KP_F2" { "show-help" (255) }
+ bind "<shift>F2" { "show-help" (whats-this) }
+ bind "<shift>KP_F2" { "show-help" (whats-this) }
+ bind "<ctrl>F2" { "show-help" (tooltip) }
+ bind "<ctrl>KP_F2" { "show-help" (tooltip) }
+}
+
+# class "GtkWidget" binding "gimp-help-binding"
+
+
+#
+# The dock separator DND highlight color is configurable.
+#
+style "gimp-red-separator-style"
+{
+ bg[SELECTED] = "#aa2448"
+}
+
+# widget "*gimp-dock-separator*" style "gimp-red-separator-style"
diff --git a/content/unix/gtkrc.html b/content/unix/gtkrc.html
new file mode 100644
index 0000000..5efbe7f
--- /dev/null
+++ b/content/unix/gtkrc.html
@@ -0,0 +1,7 @@
+<html>
+<body>
+<pre>
+<!--#include virtual="gtkrc" -->
+</pre>
+</body>
+</html>
diff --git a/content/unix/howtos/bugzilla.htrw b/content/unix/howtos/bugzilla.htrw
new file mode 100644
index 0000000..8b05850
--- /dev/null
+++ b/content/unix/howtos/bugzilla.htrw
@@ -0,0 +1,219 @@
+<!--#include virtual="/includes/wgo-xhtml-init.xhtml" -->
+<title>GIMP - How To Report GIMP Bugs</title>
+<!--#include virtual="/includes/wgo-look-feel.xhtml" -->
+<!--#include virtual="/includes/wgo-page-init.xhtml" -->
+
+<h1>EEK! A Bug!</h1>
+
+<h2>or How To Report GIMP Bugs</h2>
+<p>
+ If you find a bug or think you find a bug, it is very important to report it.
+ If the developers don't know it is broken (or might be broken), they can't
+ fix it. So there you are at your computer trying to do something with GIMP
+ and it freaks out at you. It can be a frightening experience at times.
+</p>
+
+<h3>First, Next, Third</h3>
+<p>
+ First: Get out a piece of paper or open a text file and scribble down
+ everything you can remember about what you were doing when it happened. Also
+ write down the exact wording of any error messages you received.
+</p>
+<p>
+ Next: Go away and yell and scream and do whatever you need to do to relax
+ again. Your next step will be to brave bugzilla, the GNOME bug tracker. It is
+ used to track bug reports and requests for enhancements for GIMP and GTK+).
+</p>
+<p>
+ Third: Check to see if your bug has been reported yet. Go to the
+ <a href="home:gimp-bugzilla_stable_current">Current Bug List</a> to see if
+ something that looks like your bug has been reported yet. Don't worry if it
+ has, you can still help. See the section: <a href="#enhance">Enhancing Bug Reports</a>.
+ If you can't find something that sounds like your bug there, you will need to
+ report it.
+</p>
+
+<h2>Getting Ready to Report and Reporting a Bug</h2>
+<p>
+ The goal of the following is to give the developers as much information about
+ what goes wrong as possible. This helps them find out what needs to be fixed.
+</p>
+
+<h3>The Steps</h3>
+<ol>
+ <li>
+ <p>
+ Use <kbd>gimp --version</kbd> or the about dialog to check your GIMP
+ version. Next check with <a href="http://www.gimp.org/";>www.gimp.org</a> to see
+ what the most recent GIMP release is. If your GIMP is old, update then
+ try to to reproduce the bug. Your bug may have been fixed in the most
+ recent release. If you are running GIMP from CVS, update your CVS and
+ recompile.
+ </p>
+ </li>
+ <li>
+ <p>
+ Attempt to reproduce the problem. Go do what you were doing when it
+ happened and see if you can do it again.
+ </p>
+ <p>
+ If using GIMP for GNU/Linux, start the program from a terminal with the
+ command <kbd>gimp</kbd>. Sometimes the program will output error messages
+ that can help. This is especially important if GIMP crashes completely
+ without warning. After reproducing the bug, copy the error messages from
+ your terminal into somewhere where you can save them for the bug report.
+ It is better to give too much information than not enough.
+ </p>
+ <p>
+ To narrow down the exact cause of the problem, attempt to reproduce it
+ in other ways. Prepare yourself to explain how to reproduce it in your
+ bug report. If you are running GIMP in another language, try switching
+ your GIMP to English so you can report menu items exactly with the
+ English menu item name. It helps. (Developers generally understand
+ English) If you cannot reproduce the bug, assume it was some weird
+ freak event and don't report it. If it recurs, consult with your
+ appropriate <a href="/mail_lists.html">user mailing list</a>. Perhaps
+ someone else can find the key to reproducing it.
+ </p>
+ </li>
+ <li>
+ <p>
+ Prepare to face the horror. Go to <a href="https://bugzilla.gnome.org/";>bugzilla.gnome.org</a>.
+ If you don't have a login yet, follow the directions to create one. The
+ reason to do this and report a bug with your e-mail address is so the
+ developers can contact you if they have any questions (see also
+ <a href="/bugs/why_bugzilla.html">why we are using Bugzilla</a>). That
+ way if we miss some useful tidbit of debugging information, they can
+ tell you what to do to get it. Log in.
+ </p>
+ </li>
+ <li>
+ <p>
+ Select "Enter a New Bug Report". From the list of products
+ provided, select GIMP. This opens the actual entry form.
+ </p>
+ </li>
+ <li>
+ <p>
+ Here you have to tell the developers everything about your system, your
+ version of GIMP, and your bug. Just do your best to tell them about it.
+ A crappy bug report is better than no report at all, but if you write
+ down everything you can clearly, you will create a decent bug report.
+ </p>
+ </li>
+ <ol>
+ <li>
+ <p>
+ Select the "version" that corresponds with the GIMP version in which you
+ found the bug. It is the information you got with <kbd>gimp --version</kbd> or by looking in Help
-> About.
+ </p>
+ </li>
+ <li>
+ <p>
+ Select the appropriate "component". If you don't know what component
+ it is, submit the bug under General. Descriptions of the components
+ are <a href="home:gimp-bugzilla_components">available</a>.
+ </p>
+ </li>
+ <li>
+ <p>
+ Classify the "severity" of your bug. If the bug causes
+ GIMP to crash totally or do other really ucky things so you can't
+ use the program at all, classify it as critical. If it completely
+ disables some part of GIMP, classify it as major (for example, keeps
+ you from using a tool). Most bugs are "normal". If you don't know
+ what severity to use, call it "normal". Trivial bugs are
+ annoying but don't really keep you from using the program. Cosmetic
+ bugs are things like spelling errors or UI (User Interface,
+ "the look and feel") issues. If you are requesting a new
+ feature, choose "enhancement". Don't worry if you choose
+ the wrong severity. The people getting your bug report will adjust
+ it. Don't mark it higher than it really is just to get their
+ attention.
+ </p>
+ </li>
+ <li>
+ <p>
+ Select your "operating system". Bugs in <a
+ href="wgo:wingimp">GIMP for Windows</a> and <a
+ href="wgo:gimp-unix">GIMP for GNU/Linux</a> are not always
+ identical. It would be annoying to get a Linux GIMP developer
+ trying to reproduce a Windows-specific bug. Do not select
+ "All" for the operating system unless you have verified
+ yourself that the bug affects more than one. The developers who
+ will take care of your bug may change that later, once the bug is
+ confirmed.
+ </p>
+ </li>
+ <li>
+ <p>
+ Leave "Assigned to:" blank. Bugzilla will do that automatically. Only worry
+ about CC: if you want to send a copy of your bug report to someone else.
+ </p>
+ </li>
+ <li>
+ <p>
+ For "Summary", write a brief description of your bug. This summary
+ will help other users see if their bug might be like your bug. Write something
+ that would help you if you were looking for a bug like yours.
+ </p>
+ </li>
+ <li>
+ <p>
+ "Description" is the hard part. It is the actual bug report. First
+ provide the detailed description of your bug: a brief overview of when it
+ happened and exactly what went wrong (including error messages). Next,
+ describe step-by-step how to reproduce the bug. Use the exact name of menu
+ items. Describe tools, windows, and clicks as precisely as possible. If they
+ can't reproduce the bug, it will be very hard for them to fix it. Last, tell
+ them anything else you can think of that might be relevant. This could include
+ recently installed programs or hardware that might interfere with GIMP.
+ </p>
+ </li>
+ </ol>
+</ol>
+
+<h2><a name="enhance">Enhancing Bug Reports</a></h2>
+<p>
+ If someone has already reported a bug like yours, read the bug report
+ carefully. Read through all the additional comments. Make sure every bit of
+ information you know about the bug is in there. If your version is different
+ or you had a slightly different experience with the bug, add a comment
+ providing your information. Check the status of the bug carefully. If it is
+ marked "NEEDINFO", see if you can provide the information needed. Do not add
+ a "me too" comment unless your comment provides additional information that
+ might be helpful for the developer.
+</p>
+<p>
+ If you have provided a bug report and later get more information (like a more
+ specific error message or fancy stuff like a trace), add a comment to your
+ original bug with that information. It is especially important to add a
+ comment if you somehow resolve your bug. For example, you update something
+ else on your system and the bug no longer appears. In that case, add a comment
+ describing what you updated from what version to what version that resolved
+ the bug.
+</p>
+
+<h2>The Wait Patiently Part</h2>
+<p>
+ <cite>Whee!!</cite> You survived! If you managed to get through all this and submit your
+ bug report, be happy. Be proud. You will later get e-mails about your bug.
+ It might include a request for more information. If you get something that
+ says your bug is not a bug, do not be discouraged from reporting in the future.
+ Next time it might be. Submitting careful bug reports and providing additional
+ information where possible helps make GIMP better. The day will come where you
+ submit a bug and later get an e-mail that says your bug is "FIXED"
+ or "RESOLVED". Then you will know that some developer out there found
+ your bug, reproduced it, and fixed it.
+</p>
+
+<!--#include virtual="/includes/wgo-page-fini.xhtml" -->
+ <div>
+ <span id="footerleft">
+ How To Bugzilla © 2002 <a href="mailto:bex gimp org">Rebecca J. Walter</a>
+ </span>
+ <span id="footerright">
+ <a href="mailto:webmaster gimp org">webmaster gimp org</a>
+ </span>
+ </div>
+<!--#include virtual="/includes/wgo-xhtml-fini.xhtml" -->
diff --git a/content/unix/howtos/bugzilla.md b/content/unix/howtos/bugzilla.md
new file mode 100644
index 0000000..4caf6ec
--- /dev/null
+++ b/content/unix/howtos/bugzilla.md
@@ -0,0 +1,62 @@
+Title: EEK! A Bug!
+Date: 2004
+Modified: 2015-10-05T10:19:55-05:00
+Author: Pat David
+
+
+## or How To Report GIMP Bugs
+
+If you find a bug or think you find a bug, it is very important to report it. If the developers don't know
it is broken (or might be broken), they can't fix it. So there you are at your computer trying to do
something with GIMP and it freaks out at you. It can be a frightening experience at times.
+
+### First, Next, Third
+
+First: Get out a piece of paper or open a text file and scribble down everything you can remember about what
you were doing when it happened. Also write down the exact wording of any error messages you received.
+
+Next: Go away and yell and scream and do whatever you need to do to relax again. Your next step will be to
brave bugzilla, the GNOME bug tracker. It is used to track bug reports and requests for enhancements for GIMP
and GTK+).
+
+Third: Check to see if your bug has been reported yet. Go to the [Current Bug
List](http://bugzilla.gnome.org/buglist.cgi?product=GIMP&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=NEEDINFO&form_name=query)
to see if something that looks like your bug has been reported yet. Don't worry if it has, you can still
help. See the section: [Enhancing Bug Reports](#enhance). If you can't find something that sounds like your
bug there, you will need to report it.
+
+## Getting Ready to Report and Reporting a Bug
+
+The goal of the following is to give the developers as much information about what goes wrong as possible.
This helps them find out what needs to be fixed.
+
+### The Steps
+
+1. Use <kbd>gimp --version</kbd> or the about dialog to check your GIMP version. Next check with
[www.gimp.org](http://www.gimp.org/) to see what the most recent GIMP release is. If your GIMP is old, update
then try to to reproduce the bug. Your bug may have been fixed in the most recent release. If you are running
GIMP from CVS, update your CVS and recompile.
+
+2. Attempt to reproduce the problem. Go do what you were doing when it happened and see if you can do it
again.
+
+ If using GIMP for GNU/Linux, start the program from a terminal with the command <kbd>gimp</kbd>.
Sometimes the program will output error messages that can help. This is especially important if GIMP crashes
completely without warning. After reproducing the bug, copy the error messages from your terminal into
somewhere where you can save them for the bug report. It is better to give too much information than not
enough.
+
+ To narrow down the exact cause of the problem, attempt to reproduce it in other ways. Prepare yourself
to explain how to reproduce it in your bug report. If you are running GIMP in another language, try switching
your GIMP to English so you can report menu items exactly with the English menu item name. It helps.
(Developers generally understand English) If you cannot reproduce the bug, assume it was some weird freak
event and don't report it. If it recurs, consult with your appropriate [user mailing list](/mail_lists.html).
Perhaps someone else can find the key to reproducing it.
+
+3. Prepare to face the horror. Go to [bugzilla.gnome.org](https://bugzilla.gnome.org/). If you don't have a
login yet, follow the directions to create one. The reason to do this and report a bug with your e-mail
address is so the developers can contact you if they have any questions (see also [why we are using
Bugzilla](/bugs/why_bugzilla.html)). That way if we miss some useful tidbit of debugging information, they
can tell you what to do to get it. Log in.
+
+4. Select "Enter a New Bug Report". From the list of products provided, select GIMP. This opens the actual
entry form.
+
+5. Here you have to tell the developers everything about your system, your version of GIMP, and your bug.
Just do your best to tell them about it. A crappy bug report is better than no report at all, but if you
write down everything you can clearly, you will create a decent bug report.
+
+1. Select the "version" that corresponds with the GIMP version in which you found the bug. It is the
information you got with <kbd>gimp --version</kbd> or by looking in Help -> About.
+
+2. Select the appropriate "component". If you don't know what component it is, submit the bug under
General. Descriptions of the components are
[available](http://bugzilla.gnome.org/describecomponents.cgi?product=GIMP).
+
+3. Classify the "severity" of your bug. If the bug causes GIMP to crash totally or do other really ucky
things so you can't use the program at all, classify it as critical. If it completely disables some part of
GIMP, classify it as major (for example, keeps you from using a tool). Most bugs are "normal". If you don't
know what severity to use, call it "normal". Trivial bugs are annoying but don't really keep you from using
the program. Cosmetic bugs are things like spelling errors or UI (User Interface, "the look and feel")
issues. If you are requesting a new feature, choose "enhancement". Don't worry if you choose the wrong
severity. The people getting your bug report will adjust it. Don't mark it higher than it really is just to
get their attention.
+
+4. Select your "operating system". Bugs in [GIMP for Windows](wgo:wingimp) and [GIMP for
GNU/Linux](wgo:gimp-unix) are not always identical. It would be annoying to get a Linux GIMP developer trying
to reproduce a Windows-specific bug. Do not select "All" for the operating system unless you have verified
yourself that the bug affects more than one. The developers who will take care of your bug may change that
later, once the bug is confirmed.
+
+5. Leave "Assigned to:" blank. Bugzilla will do that automatically. Only worry about CC: if you want to
send a copy of your bug report to someone else.
+
+6. For "Summary", write a brief description of your bug. This summary will help other users see if their
bug might be like your bug. Write something that would help you if you were looking for a bug like yours.
+
+7. "Description" is the hard part. It is the actual bug report. First provide the detailed description of
your bug: a brief overview of when it happened and exactly what went wrong (including error messages). Next,
describe step-by-step how to reproduce the bug. Use the exact name of menu items. Describe tools, windows,
and clicks as precisely as possible. If they can't reproduce the bug, it will be very hard for them to fix
it. Last, tell them anything else you can think of that might be relevant. This could include recently
installed programs or hardware that might interfere with GIMP.
+
+## Enhancing Bug Reports
+
+If someone has already reported a bug like yours, read the bug report carefully. Read through all the
additional comments. Make sure every bit of information you know about the bug is in there. If your version
is different or you had a slightly different experience with the bug, add a comment providing your
information. Check the status of the bug carefully. If it is marked "NEEDINFO", see if you can provide the
information needed. Do not add a "me too" comment unless your comment provides additional information that
might be helpful for the developer.
+
+If you have provided a bug report and later get more information (like a more specific error message or
fancy stuff like a trace), add a comment to your original bug with that information. It is especially
important to add a comment if you somehow resolve your bug. For example, you update something else on your
system and the bug no longer appears. In that case, add a comment describing what you updated from what
version to what version that resolved the bug.
+
+## The Wait Patiently Part
+
+<cite>Whee!!</cite> You survived! If you managed to get through all this and submit your bug report, be
happy. Be proud. You will later get e-mails about your bug. It might include a request for more information.
If you get something that says your bug is not a bug, do not be discouraged from reporting in the future.
Next time it might be. Submitting careful bug reports and providing additional information where possible
helps make GIMP better. The day will come where you submit a bug and later get an e-mail that says your bug
is "FIXED" or "RESOLVED". Then you will know that some developer out there found your bug, reproduced it, and
fixed it.
+
diff --git a/content/unix/howtos/gimp-midi.htrw b/content/unix/howtos/gimp-midi.htrw
new file mode 100644
index 0000000..ed5a790
--- /dev/null
+++ b/content/unix/howtos/gimp-midi.htrw
@@ -0,0 +1,109 @@
+<!--#include virtual="/includes/wgo-xhtml-init.xhtml" -->
+<title>GIMP - Controlling GIMP with MIDI devices</title>
+<!--#include virtual="/includes/wgo-look-feel.xhtml" -->
+<!--#include virtual="/includes/wgo-page-init.xhtml" -->
+
+<h1>Controlling GIMP with MIDI devices</h1>
+
+<h2>What?</h2>
+<p>
+ Since version 2.2, GIMP comes with a module that allows to control
+ it using MIDI devices. Currently this is only supported on GNU/Linux
+ with either the OSS or the ALSA sound drivers. It might work on
+ other platforms as well if there is a way to access the raw MIDI
+ stream by opening a device.
+</p>
+
+<h2>Enabling the MIDI Module</h2>
+
+<p>
+ To make the UI of GIMP's MIDI controller visible you need to edit a
+ configuration file when GIMP is not running. Open
+ <tt>~/.gimp-2.2/controllerrc</tt> in an editor and add the following
+ lines to the end of the file:
+</p>
+
+<pre class="code">
+(GimpControllerInfo "MIDI"
+ (enabled yes)
+ (debug-events yes)
+ (controller "ControllerMidi"
+ (device "alsa")
+ (channel -1))
+ (mapping))
+</pre>
+
+<p>
+ Then start GIMP from a shell (so that you can see textual output we
+ need later), open the preferences, go to the "Input Controllers" page in
+ the "Input Devices" section and select the newly appeared "MIDI" Tab.
+</p>
+
+<h2>Configuring the MIDI Source</h2>
+
+<h3>ALSA:</h3>
+<p>
+ Enter "alsa" in the "Device" entry in the configuration. GIMP then
+ sets up an Alsa-Output-Port (check with "<tt>aconnect -lo</tt>"). You
+ can then use your preferred tool to configure Alsa to connect a MIDI
+ source to GIMP. When your MIDI device e.g. provides an Input-Port
+ 72:0 and GIMP provides the Output-Port 128:0 you can connect the two
+ Ports with "<tt>aconnect 72:0 128:0</tt>".
+</p>
+
+<h3>OSS:</h3>
+<p>
+ The Open Sound System provides a device file for the raw MIDI events.
+ You need to enter the name of this device file into the "Device"
+ entry in the configuration (e.g. "/dev/midi00").
+</p>
+
+<h3>The MIDI channel</h3>
+
+<p>
+ Each MIDI source sends events on a specific "Channel" (0 to 15,
+ sometimes also referred as 1 to 16). You can configure if GIMP should
+ listen to all channels (-1) or to just a specific channel.
+</p>
+
+<p>
+ If your MIDI setup works correctly and the "Dump events from this
+ controller" is enabled as well as "Enable this controller" you should
+ see some text scrolling by when you hit some keys or turn some
+ controllers on your midi device, describing the Event that just
+ happened.
+</p>
+
+<h2>Assigning Actions to Events</h2>
+
+<p>
+ You can now use this information to map MIDI Events to Actions in
+ GIMP. At the bottom of the configuration page is a list with all events
+ that GIMP can recognize. Scroll to the event that you want to assign an
+ action to and doubleclick its entry. Then select an Action from the
+ dialog that pops up and doubleclick its entry. Now this action gets
+ invoked when the specific MIDI event happens.
+</p>
+
+<p>
+ Please note that some actions fit perfectly to some MIDI Events: Actions
+ like "context-background-blue-set" can immediately use the numerical
+ value provided by midi controller events.
+</p>
+
+<p>
+ Have fun.
+</p>
+
+<!--#include virtual="/includes/wgo-page-fini.xhtml" -->
+ <div>
+ <span id="footerleft">
+ How To © 2005 <a href="mail:People-Budig_Simon">Simon Budig</a>.
+ Licensed under the terms of the
+ <a href="http://www.gnu.org/licenses/gpl.html";>GNU GPL</a>.
+ </span>
+ <span id="footerright">
+ <a href="mailto:webmaster gimp org">webmaster gimp org</a>
+ </span>
+ </div>
+<!--#include virtual="/includes/wgo-xhtml-fini.xhtml" -->
diff --git a/content/unix/howtos/gimp-midi.md b/content/unix/howtos/gimp-midi.md
new file mode 100644
index 0000000..ca7b7ab
--- /dev/null
+++ b/content/unix/howtos/gimp-midi.md
@@ -0,0 +1,49 @@
+Title: Controlling GIMP with MIDI devices
+Date: 2004
+Modified: 2015-10-05T10:19:55-05:00
+Author: Pat David
+
+
+## What?
+
+Since version 2.2, GIMP comes with a module that allows to control it using MIDI devices. Currently this is
only supported on GNU/Linux with either the OSS or the ALSA sound drivers. It might work on other platforms
as well if there is a way to access the raw MIDI stream by opening a device.
+
+## Enabling the MIDI Module
+
+To make the UI of GIMP's MIDI controller visible you need to edit a configuration file when GIMP is not
running. Open <tt>~/.gimp-2.2/controllerrc</tt> in an editor and add the following lines to the end of the
file:
+
+ :::
+ (GimpControllerInfo "MIDI"
+ (enabled yes)
+ (debug-events yes)
+ (controller "ControllerMidi"
+ (device "alsa")
+ (channel -1))
+ (mapping))
+
+Then start GIMP from a shell (so that you can see textual output we need later), open the preferences, go to
the "Input Controllers" page in the "Input Devices" section and select the newly appeared "MIDI" Tab.
+
+## Configuring the MIDI Source
+
+### ALSA:
+
+Enter "alsa" in the "Device" entry in the configuration. GIMP then sets up an Alsa-Output-Port (check with
"<tt>aconnect -lo</tt>"). You can then use your preferred tool to configure Alsa to connect a MIDI source to
GIMP. When your MIDI device e.g. provides an Input-Port 72:0 and GIMP provides the Output-Port 128:0 you can
connect the two Ports with "<tt>aconnect 72:0 128:0</tt>".
+
+### OSS:
+
+The Open Sound System provides a device file for the raw MIDI events. You need to enter the name of this
device file into the "Device" entry in the configuration (e.g. "/dev/midi00").
+
+### The MIDI channel
+
+Each MIDI source sends events on a specific "Channel" (0 to 15, sometimes also referred as 1 to 16). You can
configure if GIMP should listen to all channels (-1) or to just a specific channel.
+
+If your MIDI setup works correctly and the "Dump events from this controller" is enabled as well as "Enable
this controller" you should see some text scrolling by when you hit some keys or turn some controllers on
your midi device, describing the Event that just happened.
+
+## Assigning Actions to Events
+
+You can now use this information to map MIDI Events to Actions in GIMP. At the bottom of the configuration
page is a list with all events that GIMP can recognize. Scroll to the event that you want to assign an action
to and doubleclick its entry. Then select an Action from the dialog that pops up and doubleclick its entry.
Now this action gets invoked when the specific MIDI event happens.
+
+Please note that some actions fit perfectly to some MIDI Events: Actions like "context-background-blue-set"
can immediately use the numerical value provided by midi controller events.
+
+Have fun.
+
diff --git a/content/unix/howtos/howto-template.htrw b/content/unix/howtos/howto-template.htrw
new file mode 100644
index 0000000..8e471eb
--- /dev/null
+++ b/content/unix/howtos/howto-template.htrw
@@ -0,0 +1,68 @@
+<!--#include virtual="/includes/wgo-xhtml-init.xhtml" -->
+<title>GIMP - How To Title</title>
+<!--#include virtual="/includes/wgo-look-feel.xhtml" -->
+<!--#include virtual="/includes/wgo-page-init.xhtml" -->
+<!-- -->
+<!-- How To Use This Template -->
+<!-- Any file with the extension .htrw will be sent through the attribute -->
+<!-- rewriter (/programmatic/tools/rewrite_attrs.py) when the site is -->
+<!-- installed. The url dictionary for the rewriter is maintained in -->
+<!-- /admin/gimp-web-urls -b> -->
+<!-- -->
+<!-- You can test the page you're writing (without having to install the -->
+<!-- whole site) by building a little local rewrite_attrs programme which -->
+<!-- you can run by hand: -->
+<!-- -->
+<!-- cd into /programmatic and type "make clean webtools". This produces -->
+<!-- the file /programmatic/tools/rewrite-attrs that will test your files -->
+<!-- before you commit them. -->
+<!-- -->
+<!-- Typing "./rewrite-attrs --help" will give you a very brief help -->
+<!-- -->
+<!-- Please remove this comment block before commiting your page source. -->
+<!-- -->
+<!-- thank you -->
+<!-- carol -->
+
+<h1>How To Title</h1>
+
+<h2>A subtitle</h2>
+<p>
+ Information.
+</p>
+<ol>
+ <li>A list of something</li>
+ <li>More in the list.</li>
+</ol>
+<h3>an even more subtitle</h3>
+<p>
+ This is a key stroke <kbd>Ctrl+C</kbd>.
+</p>
+<pre class="code">
+/* Comment in code and a code example */
+
+main()
+{
+ printf("Something something\n");
+}
+</pre>
+<p>
+ More information about the code or something.
+</p>
+
+<h1>Another header (if needed)</h1>
+<h2>Another subtitle</h2>
+<p>
+ More information.
+</p>
+
+<!--#include virtual="/includes/wgo-page-fini.xhtml" -->
+ <div>
+ <span id="footerleft">
+ How To © 2002 <a href="mailto:webmaster gimp org">Author name</a>
+ </span>
+ <span id="footerright">
+ <a href="mailto:webmaster gimp org">webmaster gimp org</a>
+ </span>
+ </div>
+<!--#include virtual="/includes/wgo-xhtml-fini.xhtml" -->
diff --git a/content/unix/howtos/tile_cache.htrw b/content/unix/howtos/tile_cache.htrw
new file mode 100644
index 0000000..32e5c91
--- /dev/null
+++ b/content/unix/howtos/tile_cache.htrw
@@ -0,0 +1,212 @@
+<!--#include virtual="/includes/wgo-xhtml-init.xhtml" -->
+<title>GIMP - How To Set Your Tile Cache</title>
+<!--#include virtual="/includes/wgo-look-feel.xhtml" -->
+<!--#include virtual="/includes/wgo-page-init.xhtml" -->
+
+<h1>How To Set Your Tile Cache</h1>
+<h2>or Tile Cache Recommendations</h2>
+
+<p><em><strong>Quick summary</strong> for those who do not want to
+read all this: if your system has good swapping behavior (like most
+GNU/Linux systems) and if you have enough virtual memory (swap), then set
+the tile cache size as high as possible. If not, then set it to about
+80% of the available RAM on your system. If you are not satisfied
+with this quick advice, then keep on reading...</em></p>
+
+<p>
+ Image processing can require a lot of memory. GIMP uses the
+ operating system services to handle memory, up to a given point,
+ past which it uses its own system so it does not eat all system
+ memory resources. This system consists in sending old data to files
+ in the disk. The decision point is what Tile Cache determines, the
+ limit of operating system resources to use, and is measured in Bytes
+ (or multiples, like MegaBytes). It does not include GIMP's own memory,
+ just the space required for the image data.
+</p>
+<p>
+ A low value means that GIMP sends data really quickly to disk, not
+ making real use of the avaliable RAM and making the disks work
+ without real reason. A too high value, and the other applications
+ start to have less system resources forcing them to swap space,
+ which is making the disks work too, or maybe some will even get
+ killed or start to malfunction due lack of RAM.
+</p>
+
+<h3>How to choose a number for Tile Cache?</h3>
+<p>
+ There are some ways to decide what value to use as Tile Cache, as
+ well as some tricks:
+</p>
+<ul>
+ <li>
+ Forget about this and hope the default works. It worked when
+ computers had few RAM and people just tried to make small images
+ with GIMP while running one or two applications each time. If you
+ want something easy and only use GIMP to make screenshoots and
+ some logos, probably the best solution.
+ </li>
+ <li>
+ Ask someone to do it for you, which in the case of a computer
+ serving multiple users at the same time can be a good idea, that
+ way the administrator and other users do not get mad at you for
+ abusing the machine, nor you get a badly underperfoming GIMP. If
+ it is your machine and a single user at a given time, it could
+ mean money, or drinks, as price for the service. ;]
+ </li>
+ <li>
+ Start changing the value a bit each time and check that it goes
+ faster and faster with each increase, but the systems does not
+ complain about lack of memory. Be forewarned that sometimes lack
+ of memory ends with some applications being killed to make space
+ for the others.
+ </li>
+ <li>
+ Do some simple maths and calculate a viable value. Maybe you will
+ have to tune it later, but maybe you have to tune it anyway with
+ the other previous methods. At least you know what is happening
+ and can get the best from your computer.
+ </li>
+</ul>
+
+<h3>What number to use for Tile Cache?</h3>
+<p>
+ Let's guess you prefer the last option, and get a nice value to
+ start with. First, you need to get some data about your computer.
+ This data is the RAM installed, the operating system's swap space
+ avaliable and a general idea about the speed of the disks that store
+ the operating system's swap and the directory used for GIMP's
+ swap. You do not need to do disk tests, nor check the RPM of them,
+ the thing is to see which one seems clearly faster or slower or all
+ similar. Remember you can change GIMP's swap directory in
+ <Toolbox> -> File -> Preferences -> Folders ->
+ Swap Dir.
+</p>
+<p>
+ Next thing to do is to see how much resources you require for other
+ apps you want to run at the same time than GIMP. So start all your
+ tools and do some work with them, except GIMP of course, and check
+ the usage. You can use applications like free or top, depends in
+ what OS and what environment you use. The numbers you want is the
+ memory left, including file cache. Modern UNIX keep a really small
+ area free, to be able to keep big file and buffer caches. GNU/Linux's
+ free does the maths for you, check the column that says
+ "free", and the line "-/+ buffers/cache". Note
+ down also the free swap.
+</p>
+<p>
+ Now time for decisions and simple maths. Basically the concept is
+ to decide if you want to base all Tile Cache in free RAM, or free RAM
+ plus operating system free swap:
+</p>
+<ol>
+ <li>
+ Do you change applications a lot? Or keep working in GIMP for a
+ long time? If you stay long times in GIMP, you can consider free
+ RAM plus free swap as avaliable, or not, you have to check
+ following points. If unsure about that times being long or not,
+ check next steps too. If you are sure you switch all the apps
+ every few time, only count free RAM and just go to final decision,
+ no more things to check.
+ </li>
+ <li>
+ Does operating system swap live in the same physical disk than
+ GIMP swap? If so, use RAM and swap, as this way you will try to keep
+ disk access over a fixed, compact, area for more time. Otherwise
+ check next.
+ </li>
+ <li>
+ The disk that holds the swap is faster or same speed than the disk
+ that holds GIMP's swap? If slower, take only free RAM, if faster
+ or similar, use free RAM and swap. This way we avoid a slow disk when
+ there is a fast one doing nothing.
+ </li>
+ <li>
+ You got a number, be it just the free RAM or the free RAM plus the
+ free OS swap. Reduce it a bit, to be on the safe side, and that is
+ the Tile Cache you could use as a good start.
+ </li>
+</ol>
+<p>
+ As you can see, all is about checking the free resources, and decide
+ if the OS swap is worth using or will cause more problems than help.
+</p>
+
+<h3>Tuning the value and other helpful changes.</h3>
+<p>
+ There are some reason you want to adjust the value. The basic one is
+ changing your computer usage pattern, or changing hardware. That
+ could mean you assumptions about how you use your computer, or the
+ speed of it, are not longer valid. That would require a reevaluation
+ of the previous steps, which can drive you to a similar value or a
+ completly new value.
+</p>
+<p>
+ Other reason to change the value is because you detect it goes too slowly
+ inside GIMP but changing to other applications is fast, which probably
+ means tile size is too low. Or maybe you get complaints from other
+ applications about not having enough memory, so probably better lower
+ tile size if it is not already really small.
+</p>
+<p>
+ If you decided to use only RAM and it goes slow, you could try
+ increasing the value a bit, but never to use also all the free swap.
+ If the case is the contrary, using both RAM and swap, and you have
+ problems about lack of resources, decrease it.
+</p>
+<p>
+ More tricks are to put the Swap Dir in a very fast disk, or in a
+ different disk than the rest of things. Spreading the operating
+ system swap over multiple disks is also a good way to speed up
+ things, in general. And of course, maybe you have to buy more RAM or
+ stop using lots of programs at the same time, you can not expect to
+ edit a poster in a computer with 16MB and be fast.
+</p>
+<p>
+ On a side note: you can make your title or status bar show the memory
+ usage (if not already doing so). That is the simplest way to keep an eye
+ on how much memory you are using per image, and thus see what is the typical
+ usage you get or if a image is just an exception and not worth the hassle
+ of changing values.
+</p>
+
+
+<h3>Some info about GIMP memory usage.</h3>
+<p>
+ You can check what memory requirements your images have in advance.
+ The bigger the images and the number of undos, the more resources you
+ need. This is another way to choose a number, but it is only good if
+ you always work in the same kind of images, and thus the real
+ requirements do not vary. It is also good to know if you will require
+ more RAM and/or disk space so you can go shopping for hardware with
+ a better idea of what you need (lots of RAM vs not so much RAM and better
+ get a faster CPU, for example).
+</p>
+<p>
+ First is the memory for the pixel data. Each layer requires layer width
+ * layer height * 3 bytes for RGB background without alpha or * 4 for RGB
+ layers with alpha.
+</p>
+<p>
+ Then GIMP needs to store the selection mask, which is a width *
+ height of the total image. Next, the composed image, which is what
+ you see in your screen, requires image width * height * 5,33. The
+ fractional part is because, starting with GIMP 2.4, the composed
+ image is kept in several sizes. You can combine these two values as
+ image width * height * 6,33.
+</p>
+<p>
+ Last, there is some overhead GIMP needs to know where pixels are stored,
+ so round the number up or add a 5-10% to be in safe side. For medium
+ and big images, what really counts is the pixel related memory.
+</p>
+
+<!--#include virtual="/includes/wgo-page-fini.xhtml" -->
+ <div>
+ <span id="footerleft">
+ How To © 2003 <a href="mail:People-Romero_Guillermo_S">Guillermo S. Romero</a>
+ </span>
+ <span id="footerright">
+ <a href="mailto:webmaster gimp org">webmaster gimp org</a>
+ </span>
+ </div>
+<!--#include virtual="/includes/wgo-xhtml-fini.xhtml" -->
diff --git a/content/unix/howtos/tile_cache.md b/content/unix/howtos/tile_cache.md
new file mode 100644
index 0000000..d806f69
--- /dev/null
+++ b/content/unix/howtos/tile_cache.md
@@ -0,0 +1,60 @@
+Title: How To Set Your Tile Cache
+Date: 2004
+Modified: 2015-10-05T10:19:55-05:00
+Author: Pat David
+
+
+## or Tile Cache Recommendations
+
+_**Quick summary** for those who do not want to read all this: if your system has good swapping behavior
(like most GNU/Linux systems) and if you have enough virtual memory (swap), then set the tile cache size as
high as possible. If not, then set it to about 80% of the available RAM on your system. If you are not
satisfied with this quick advice, then keep on reading..._
+
+Image processing can require a lot of memory. GIMP uses the operating system services to handle memory, up
to a given point, past which it uses its own system so it does not eat all system memory resources. This
system consists in sending old data to files in the disk. The decision point is what Tile Cache determines,
the limit of operating system resources to use, and is measured in Bytes (or multiples, like MegaBytes). It
does not include GIMP's own memory, just the space required for the image data.
+
+A low value means that GIMP sends data really quickly to disk, not making real use of the avaliable RAM and
making the disks work without real reason. A too high value, and the other applications start to have less
system resources forcing them to swap space, which is making the disks work too, or maybe some will even get
killed or start to malfunction due lack of RAM.
+
+### How to choose a number for Tile Cache?
+
+There are some ways to decide what value to use as Tile Cache, as well as some tricks:
+
+* Forget about this and hope the default works. It worked when computers had few RAM and people just tried
to make small images with GIMP while running one or two applications each time. If you want something easy
and only use GIMP to make screenshoots and some logos, probably the best solution.
+* Ask someone to do it for you, which in the case of a computer serving multiple users at the same time
can be a good idea, that way the administrator and other users do not get mad at you for abusing the machine,
nor you get a badly underperfoming GIMP. If it is your machine and a single user at a given time, it could
mean money, or drinks, as price for the service. ;]
+* Start changing the value a bit each time and check that it goes faster and faster with each increase,
but the systems does not complain about lack of memory. Be forewarned that sometimes lack of memory ends with
some applications being killed to make space for the others.
+* Do some simple maths and calculate a viable value. Maybe you will have to tune it later, but maybe you
have to tune it anyway with the other previous methods. At least you know what is happening and can get the
best from your computer.
+
+### What number to use for Tile Cache?
+
+Let's guess you prefer the last option, and get a nice value to start with. First, you need to get some data
about your computer. This data is the RAM installed, the operating system's swap space avaliable and a
general idea about the speed of the disks that store the operating system's swap and the directory used for
GIMP's swap. You do not need to do disk tests, nor check the RPM of them, the thing is to see which one seems
clearly faster or slower or all similar. Remember you can change GIMP's swap directory in <Toolbox> -> File
-> Preferences -> Folders -> Swap Dir.
+
+Next thing to do is to see how much resources you require for other apps you want to run at the same time
than GIMP. So start all your tools and do some work with them, except GIMP of course, and check the usage.
You can use applications like free or top, depends in what OS and what environment you use. The numbers you
want is the memory left, including file cache. Modern UNIX keep a really small area free, to be able to keep
big file and buffer caches. GNU/Linux's free does the maths for you, check the column that says "free", and
the line "-/+ buffers/cache". Note down also the free swap.
+
+Now time for decisions and simple maths. Basically the concept is to decide if you want to base all Tile
Cache in free RAM, or free RAM plus operating system free swap:
+
+1. Do you change applications a lot? Or keep working in GIMP for a long time? If you stay long times in
GIMP, you can consider free RAM plus free swap as avaliable, or not, you have to check following points. If
unsure about that times being long or not, check next steps too. If you are sure you switch all the apps
every few time, only count free RAM and just go to final decision, no more things to check.
+2. Does operating system swap live in the same physical disk than GIMP swap? If so, use RAM and swap, as
this way you will try to keep disk access over a fixed, compact, area for more time. Otherwise check next.
+3. The disk that holds the swap is faster or same speed than the disk that holds GIMP's swap? If slower,
take only free RAM, if faster or similar, use free RAM and swap. This way we avoid a slow disk when there is
a fast one doing nothing.
+4. You got a number, be it just the free RAM or the free RAM plus the free OS swap. Reduce it a bit, to be
on the safe side, and that is the Tile Cache you could use as a good start.
+
+As you can see, all is about checking the free resources, and decide if the OS swap is worth using or will
cause more problems than help.
+
+### Tuning the value and other helpful changes.
+
+There are some reason you want to adjust the value. The basic one is changing your computer usage pattern,
or changing hardware. That could mean you assumptions about how you use your computer, or the speed of it,
are not longer valid. That would require a reevaluation of the previous steps, which can drive you to a
similar value or a completly new value.
+
+Other reason to change the value is because you detect it goes too slowly inside GIMP but changing to other
applications is fast, which probably means tile size is too low. Or maybe you get complaints from other
applications about not having enough memory, so probably better lower tile size if it is not already really
small.
+
+If you decided to use only RAM and it goes slow, you could try increasing the value a bit, but never to use
also all the free swap. If the case is the contrary, using both RAM and swap, and you have problems about
lack of resources, decrease it.
+
+More tricks are to put the Swap Dir in a very fast disk, or in a different disk than the rest of things.
Spreading the operating system swap over multiple disks is also a good way to speed up things, in general.
And of course, maybe you have to buy more RAM or stop using lots of programs at the same time, you can not
expect to edit a poster in a computer with 16MB and be fast.
+
+On a side note: you can make your title or status bar show the memory usage (if not already doing so). That
is the simplest way to keep an eye on how much memory you are using per image, and thus see what is the
typical usage you get or if a image is just an exception and not worth the hassle of changing values.
+
+### Some info about GIMP memory usage.
+
+You can check what memory requirements your images have in advance. The bigger the images and the number of
undos, the more resources you need. This is another way to choose a number, but it is only good if you always
work in the same kind of images, and thus the real requirements do not vary. It is also good to know if you
will require more RAM and/or disk space so you can go shopping for hardware with a better idea of what you
need (lots of RAM vs not so much RAM and better get a faster CPU, for example).
+
+First is the memory for the pixel data. Each layer requires layer width * layer height * 3 bytes for RGB
background without alpha or * 4 for RGB layers with alpha.
+
+Then GIMP needs to store the selection mask, which is a width * height of the total image. Next, the
composed image, which is what you see in your screen, requires image width * height * 5,33\. The fractional
part is because, starting with GIMP 2.4, the composed image is kept in several sizes. You can combine these
two values as image width * height * 6,33.
+
+Last, there is some overhead GIMP needs to know where pixels are stored, so round the number up or add a
5-10% to be in safe side. For medium and big images, what really counts is the pixel related memory.
+
diff --git a/content/unix/man-gimp-2.0.html b/content/unix/man-gimp-2.0.html
new file mode 100644
index 0000000..31ea9aa
--- /dev/null
+++ b/content/unix/man-gimp-2.0.html
@@ -0,0 +1,408 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML><HEAD><TITLE>Man page of GIMP</TITLE>
+<STYLE TYPE="text/css">
+DIV.section {margin-left:2cm}
+</STYLE>
+</HEAD><BODY>
+<H1>GIMP</H1>
+Section: GIMP Manual Pages (1)<BR>Updated: March 23 2004<BR><A HREF="#index">Index</A>
+<HR>
+
+<A NAME="lbAB"> </A>
+<H2>NAME</H2>
+
+gimp - an image manipulation and paint program.
+<A NAME="lbAC"> </A>
+<H2>SYNOPSIS</H2>
+
+<B>gimp</B>
+
+[-h] [--help] [-v] [--version] [--verbose] [--no-shm]
+[--no-cpu-accel] [--display <I>display</I>] [-d] [--no-data]
+[-f] [--no-fonts] [-i] [--no-interface] [-s] [--no-splash]
+[--session <I><name></I>] [-g] [--gimprc <I><gimprc></I>]
+[--system-gimprc <I><gimprc></I>] [--dump-gimprc]
+[--console-messages] [--debug-handlers]
+[-b] [--batch <I><commands></I>]
+[<I>filename</I>] ...
+<P>
+<A NAME="lbAD"> </A>
+<H2>DESCRIPTION</H2>
+
+<P>
+
+The <I>GIMP</I> is the GNU Image Manipulation Program. It is used to
+edit and manipulate images. It can load and save a variety of image
+formats and can be used to convert between formats.
+</P>
+<P>
+
+GIMP can also be used as a paint program. It features a set of drawing
+and painting tools such as airbrush, clone, pencil, and paint
+brush. Painting and drawing tools can be applied to an image with a
+variety of paint modes. It also offers an extensive array of
+selection tools like rectangle, ellipse, fuzzy select, bezier select,
+intelligent scissors, and select by color.
+</P>
+<P>
+
+GIMP offers a variety of plugins that perform a variety of image
+manipulations. Examples include bumpmap, edge detect, gaussian blur,
+and many others.
+</P>
+<P>
+
+In addition, GIMP has several scripting extension which allow for
+advanced non-interactive processing and creation of images.
+</P><P>
+<A NAME="lbAE"> </A>
+<H2>OPTIONS</H2>
+
+
+The <I>gimp</I> accepts the following options:
+<DL COMPACT>
+<DT><B>-h, --help</B>
+
+<DD>
+Display a list of all commandline options.
+<DT><B>-v, --version</B>
+
+<DD>
+Output the version info.
+<DT><B>--verbose</B>
+
+<DD>
+Show startup messages.
+<DT><B>--no-shm</B>
+
+<DD>
+Do not use shared memory between GIMP and its plugins.
+Instead of using shared memory, GIMP will send the data via pipe. This
+will result in slower performance than using shared memory.
+<DT><B>--no-cpu-accel</B>
+
+<DD>
+Do not use CPU accelerations such as MMX or SSE even if GIMP detects
+that your CPU provides this functionality.
+<DT><B>-d, --no-data</B>
+
+<DD>
+Do not load patterns, gradients, palettes, or brushes. Often useful
+in non-interactive situations where startup time is to be minimized.
+<DT><B>-f, --no-fonts</B>
+
+<DD>
+Do not load any fonts. No text functionality will be available if this
+option is used.
+<DT><B>-i, --no-interface</B>
+
+<DD>
+Run without a user interface.
+<DT><B>--display </B><I>display</I>
+
+<DD>
+Use the designated X display.
+<DT><B>-s, --no-splash</B>
+
+<DD>
+Do not show the splash screen.
+<DT><B>--session </B><I><name></I>
+
+<DD>
+Use a different sessionrc for this GIMP session. The given session
+name is appended to the default sessionrc filename.
+<DT><B>-g, --gimprc </B><I><gimprc></I>
+
+<DD>
+Use an alternative gimprc instead of the default one. Useful in
+cases where plugins paths or machine specs may be different.
+<DT><B>--system-gimprc </B><I><gimprc></I>
+
+<DD>
+Use an alternate system gimprc file.
+<DT><B>--dump-gimprc</B>
+
+<DD>
+Output a gimprc file with default settings.
+<DT><B>--debug-handlers</B>
+
+<DD>
+Enable debugging signal handlers.
+<DT><B>-c, --console-messages</B>
+
+<DD>
+Do not popup dialog boxes on errors or warnings. Print the messages on
+the console instead.
+<DT><B>--stack-trace-mode </B><I>{never|query|always}</I>
+
+<DD>
+If a stack-trace should be generated in case of fatal signals.
+<DT><B>--pdb-compat-mode </B><I>{off|on|warn}</I>
+
+<DD>
+If the PDB should provide aliases for deprecated functions.
+<DT><B>-b, --batch </B><I><commands></I>
+
+<DD>
+Execute the set of <I><commands></I> non-interactively. The set
+of <I><commands></I> is typically in the form of a script that
+can be executed by one of the GIMP scripting extensions. When
+<I><commands></I> is <B>-</B> the commands are read from standard
+input.
+<DT><DD>
+</DL>
+</P><P>
+
+<A NAME="lbAF"> </A>
+<H2>ENVIRONMENT</H2>
+
+</P><P>
+
+<DL COMPACT>
+<DT><B>DISPLAY</B>
+
+<DD>
+to get the default host and display number.
+<DT><B>XENVIRONMENT</B>
+
+<DD>
+to get the name of a resource file that overrides the global resources
+stored in the RESOURCE_MANAGER property.
+</DL>
+</P><P>
+<A NAME="lbAG"> </A>
+<H2>FILES</H2>
+
+GIMP's data files are stored in ${prefix}/share/gimp/2.0, where ${prefix}
+is set on install, but is typically /usr/local. GIMP's system-wide
+configuration files are stored in ${prefix}/etc/gimp/2.0.
+Most GIMP configuration is read in from the user's init file,
+<B>$HOME</B>/.gimp-2.0/gimprc. The system wide equivalent is in
+${prefix}/etc/gimprc. The system wide file is parsed
+first and the user gimprc can override the system settings.
+${prefix}/etc/gimprc_user is the default gimprc
+placed in users' home directories the first time GIMP is run.
+</P>
+<P>
+<B>$HOME</B>/.gimp-2.0/devicerc - holds settings for input devices
+together with the tool, colors, brush, pattern and gradient
+associated to that device.
+</P>
+<P>
+<B>$HOME</B>/.gimp-2.0/documents - lists all images that have been
+opened or saved using GIMP.
+</P>
+<P>
+<B>$HOME</B>/.gimp-2.0/gtkrc - users set of gimp-specific GTK config
+settings. Options such as widget color and fonts sizes can be set
+here.
+</P>
+<P>
+${prefix}/etc/gimp/2.0/gtkrc - sytem wide default set of gimp-specific GTK+
+config settings.
+</P>
+<P>
+<B>$HOME</B>/.gimp-2.0/menurc - user's set of keybindings.
+</P>
+<P>
+${prefix}/etc/gimp/2.0/menurc - system wide set of keybindings.
+</P>
+<P>
+<B>$HOME</B>/.gimp-2.0/parasiterc - Description of all available GIMP
+parasites. This is file is recreated everytime GIMP starts up.
+</P>
+<P>
+<B>$HOME</B>/.gimp-2.0/sessionrc - This file takes session-specific
+info (that is info, you want to keep between two gimp-sessions). You
+are not supposed to edit it manually, but of course you can do. This
+file will be entirely rewritten every time you quit the GIMP. If this
+file isn't found, defaults are used.
+</P>
+<P>
+<B>$HOME</B>/.gimp-2.0/templaterc - Image templates are kept in this
+file. New images can conveniently created from these templates. If
+this file isn't found, defaults are used.
+</P>
+<P>
+${prefix}/etc/gimp/2.0/unitrc - default user unit database. It contains the
+unit definitions for centimeters, meters, feet, yards, typographic
+points and typographic picas and is placed in users home directories
+the first time the GIMP is ran. If this file isn't found, defaults are
+used.
+</P>
+<P>
+<B>$HOME</B>/.gimp-2.0/unitrc - This file contains your user unit
+database. You can modify this list with the unit editor. You are not
+supposed to edit it manually, but of course you can do. This file
+will be entirely rewritten every time you quit the GIMP.
+</P>
+<P>
+<B>$HOME</B>/.gimp-2.0/plug-ins - location of user installed plugins.
+</P>
+<P>
+<B>$HOME</B>/.gimp-2.0/pluginrc - plugin initialization values are
+stored here. This file is parsed on startup and regenerated if need
+be.
+</P>
+<P>
+<B>$HOME</B>/.gimp-2.0/modules - location of user installed modules.
+</P>
+<P>
+<B>$HOME</B>/.gimp-2.0/tmp - default location that GIMP uses as
+temporary space.
+</P>
+<P>
+${prefix}/share/gimp/2.0/brushes - system wide brush files.
+</P>
+<P>
+<B>$HOME</B>/.gimp-2.0/brushes - user created and installed brush
+files. These files are in the .gbr, .gih or .vbr file formats.
+</P>
+<P>
+<B>$HOME</B>/.gimp-2.0/curves - Curve profiles and presets as saved from
+the Curves tool.
+</P>
+<P>
+<B>$HOME</B>/.gimp-2.0/gimpressionist - Presets and user created brushes
+and papers are stored here.
+</P>
+<P>
+<B>$HOME</B>/.gimp-2.0/levels - Level profiles and presets as saved from
+the Levels tool.
+</P>
+<P>
+${prefix}/share/gimp/2.0/palettes - the system wide palette files.
+</P>
+<P>
+<B>$HOME</B>/.gimp-2.0/palettes - user created and modified palette
+files. This files are in the .gpl format.
+</P>
+<P>
+${prefix}/share/gimp/2.0/patterns - basic set of patterns for use in GIMP.
+</P>
+<P>
+<B>$HOME</B>/.gimp-2.0/patterns - user created and installed gimp
+pattern files. This files are in the .pat format.
+</P>
+<P>
+${prefix}/share/gimp/2.0/gradients - standard system wide set of gradient files.
+</P>
+<P>
+<B>$HOME</B>/.gimp-2.0/gradients - user created and installed gradient
+files.
+</P>
+<P>
+${prefix}/share/gimp/2.0/scripts - system wide directory of scripts
+used in Script-Fu and other scripting extensions.
+</P>
+<P>
+<B>$HOME</B>/.gimp-2.0/scripts - user created and installed scripts.
+</P>
+<P>
+${prefix}/share/gimp/2.0/gflares - system wide directory used by the gflare
+plug-in.
+</P>
+<P>
+<B>$HOME</B>/.gimp-2.0/gflares - user created and installed gflare
+files.
+</P>
+<P>
+${prefix}/share/gimp/2.0/gfig - system wide directory used by the gfig plug-in.
+</P>
+<P>
+<B>$HOME</B>/.gimp-2.0/gfig - user created and installed gfig files.
+</P>
+<P>
+${prefix}/share/gimp/2.0/images/gimp_splash.png - image used for the GIMP splash
+screen.
+</P>
+<P>
+${prefix}/share/gimp/2.0/images/gimp_logo.png - image used in the GIMP about
+dialog.
+</P>
+<P>
+${prefix}/share/gimp/2.0/tips/gimp-tips.xml - tips as displayed in the "Tip of
+the Day" dialog box.
+</P>
+<P>
+<A NAME="lbAH"> </A>
+<H2>SUGGESTIONS AND BUG REPORTS</H2>
+
+Any bugs found should be reported to the online bug-tracking system
+available on the web at <A HREF="http://bugzilla.gnome.org/.";>http://bugzilla.gnome.org/.</A> Before
reporting
+bugs, please check to see if the bug has already been reported.
+</P>
+<P>
+When reporting GIMP bugs, it is important to include a reliable way to
+reproduce the bug, version number of GIMP (and probably GTK), OS name
+and version, and any relevant hardware specs. If a bug is causing a
+crash, it is very useful if a stack trace can be provided. And of
+course, patches to rectify the bug are even better.
+</P>
+<P>
+<A NAME="lbAI"> </A>
+<H2>OTHER INFO</H2>
+
+</P>
+<P>
+The canonical place to find GIMP info is at <A HREF="http://www.gimp.org/.";>http://www.gimp.org/.</A>
+Here you can find links to just about many other GIMP sites,
+tutorials, data sets, mailing list archives, and more.
+</P>
+<P>
+There is also a GIMP User Manual available at
+<A HREF="http://manual.gimp.org/";>http://manual.gimp.org/</A> that goes into much more detail
+about the interactive use of GIMP.
+</P>
+<P>
+The latest version of GIMP and the GTK+ libs is always available at
+<A HREF="http://download.gimp.org/";>http://download.gimp.org/.</A>
+</P>
+<P>
+<A NAME="lbAJ"> </A>
+<H2>AUTHORS</H2>
+
+Spencer Kimball and Peter Mattis.
+</P>
+<P>
+With patches, fixes, plugins, extensions, scripts,
+translations, documentation, and more from lots
+and lots of people all over the world.
+</P>
+<P>
+<A NAME="lbAK"> </A>
+<H2>SEE ALSO</H2>
+
+<B><A HREF="man-gimprc-2.0.html">gimprc</A></B>(5),
+
+<B><A HREF="man-gimptool-2.0.html">gimptool</A></B>(1),
+
+<B><A HREF="man-gimp-remote-2.0.html">gimp-remote</A></B>(1)
+
+</P>
+<P>
+
+<HR>
+<A NAME="index"> </A><H2>Index</H2>
+<DL>
+<DT><A HREF="#lbAB">NAME</A><DD>
+<DT><A HREF="#lbAC">SYNOPSIS</A><DD>
+<DT><A HREF="#lbAD">DESCRIPTION</A><DD>
+<DT><A HREF="#lbAE">OPTIONS</A><DD>
+<DT><A HREF="#lbAF">ENVIRONMENT</A><DD>
+<DT><A HREF="#lbAG">FILES</A><DD>
+<DT><A HREF="#lbAH">SUGGESTIONS AND BUG REPORTS</A><DD>
+<DT><A HREF="#lbAI">OTHER INFO</A><DD>
+<DT><A HREF="#lbAJ">AUTHORS</A><DD>
+<DT><A HREF="#lbAK">SEE ALSO</A><DD>
+</DL>
+<HR>
+</P>
+<P>
+This document was created by
+<A HREF="http://www.w3.org/Tools/man2html.html";>man2html</A>,
+using the manual pages.<BR>
+Time: 19:32:44 GMT, March 29, 2004
+</P>
+</BODY>
+</HTML>
diff --git a/content/unix/man-gimp-remote-2.0.html b/content/unix/man-gimp-remote-2.0.html
new file mode 100644
index 0000000..f2a85a1
--- /dev/null
+++ b/content/unix/man-gimp-remote-2.0.html
@@ -0,0 +1,130 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML><HEAD><TITLE>Man page of GIMP-REMOTE</TITLE>
+</HEAD><BODY>
+<p>
+<H1>GIMP-REMOTE</H1>
+Section: GIMP Manual Pages (1)<BR>Updated: March 23 2004<BR><A HREF="#index">Index</A>
+
+<A NAME="lbAB"> </A>
+<H2>NAME</H2>
+
+gimp-remote - tells a running GIMP to open a (local or remote) image file.
+<A NAME="lbAC"> </A>
+<H2>SYNOPSIS</H2>
+
+<B>gimp-remote</B>
+
+[-h] [--help] [-v] [--version] [--display <I>display</I>]
+[-e] [--existing] [-q] [--query] <I>filename</I> ...
+</p><p>
+<A NAME="lbAD"> </A>
+<H2>DESCRIPTION</H2>
+
+</p><p>
+
+<I>gimp-remote</I> is a small utility that tells a running GIMP to open
+one or more (local or remote) image files. It does so by searching
+for a GIMP toolbox on the active display. If it can find a GIMP
+toolbox, a synthetic drop event is created which makes GIMP think the
+files would have been dropped onto the toolbox. More than one filename
+or URL can be specified on the commandline.
+</p><p>
+
+If no GIMP window is found, <I>gimp-remote</I> will start a new GIMP
+instance and ask it to load the specified images. If no filename or
+URL is given, <I>gimp-remote</I> will start a new GIMP. This behaviour
+can be altered using the command-line options described below.
+</p><p>
+<A NAME="lbAE"> </A>
+<H2>OPTIONS</H2>
+
+
+<I>gimp-remote</I> accepts the following options:
+<DL COMPACT>
+<DT><B>-h, --help</B>
+
+<DD>
+Display a list of all commandline options.
+<DT><B>-v, --version</B>
+
+<DD>
+Output the version info.
+<DT><B>--display </B><I>display</I>
+
+<DD>
+Use the designated X display.
+<DT><B>-e, --existing</B>
+
+<DD>
+If no running GIMP instance is found, don't start a new one but exit.
+<DT><B>-q, --query</B>
+
+<DD>
+Check if GIMP is running and exit. A status code of 0 indicates that
+a GIMP toolbox window has been found on this display.
+</DL>
+</p><p>
+<A NAME="lbAF"> </A>
+<H2>EXAMPLES</H2>
+
+<DL COMPACT>
+<DT><B>gimp-remote <A
HREF="http://classic.gimp.org/icons/frontpage-small.gif";>http://www.gimp.org/icons/frontpage-small.gif</A></B>
+
+<DD>
+Loads the image from the GIMP website into a running GIMP or starts
+a new one.
+<DT><B>gimp-remote wilber.xcf wilma.xcf</B>
+
+<DD>
+Loads the local files wilber.xcf and wilma.xcf into a running GIMP
+or starts a new one.
+</DL>
+</p><p>
+<A NAME="lbAG"> </A>
+<H2>ENVIRONMENT</H2>
+
+</p><p>
+
+<DL COMPACT>
+<DT><B>DISPLAY</B>
+
+<DD>
+to get the default host and display number.
+</p><p>
+</DL>
+<A NAME="lbAH"> </A>
+<H2>AUTHORS</H2>
+
+Sven Neumann and Simon Budig.
+</p><p>
+<A NAME="lbAI"> </A>
+<H2>SEE ALSO</H2>
+
+<B><A HREF="man-gimp-2.0.html">gimp</A></B>(1),
+
+<B><A HREF="man-gimp-2.0.html">gimprc</A></B>(5),
+
+<B><A HREF="man-gimptool-2.0.html">gimptool</A></B>(1)
+
+</p><p>
+
+<HR>
+<A NAME="index"> </A><H2>Index</H2>
+<DL>
+<DT><A HREF="#lbAB">NAME</A><DD>
+<DT><A HREF="#lbAC">SYNOPSIS</A><DD>
+<DT><A HREF="#lbAD">DESCRIPTION</A><DD>
+<DT><A HREF="#lbAE">OPTIONS</A><DD>
+<DT><A HREF="#lbAF">EXAMPLES</A><DD>
+<DT><A HREF="#lbAG">ENVIRONMENT</A><DD>
+<DT><A HREF="#lbAH">AUTHORS</A><DD>
+<DT><A HREF="#lbAI">SEE ALSO</A><DD>
+</DL>
+<HR>
+This document was created by
+<A HREF="http://www.w3.org/Tools/man2html.html";>man2html</A>,
+using the manual pages.<BR>
+Time: 20:45:50 GMT, March 29, 2004
+</p>
+</BODY>
+</HTML>
diff --git a/content/unix/man-gimprc-2.0.html b/content/unix/man-gimprc-2.0.html
new file mode 100644
index 0000000..0c84717
--- /dev/null
+++ b/content/unix/man-gimprc-2.0.html
@@ -0,0 +1,803 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML><HEAD><TITLE>Man page of GIMPRC</TITLE>
+</HEAD><BODY>
+<p>
+<H1>GIMPRC</H1>
+Section: File Formats (5)<BR>Updated: Version 2.0.0<BR><A HREF="#index">Index</A>
+
+<A NAME="lbAB"> </A>
+<H2>NAME</H2>
+
+gimprc - gimp configuration file
+<A NAME="lbAC"> </A>
+<H2>DESCRIPTION</H2>
+
+The
+<B>gimprc</B>
+
+file is a configuation file read by the GIMP when it starts up. There
+are two of these: one system-wide one stored in
+${prefix}/etc/gimp/2.0/gimprc and a per-user <B>$HOME</B>/.gimp-2.0/gimprc
+which may override system settings.
+</p><p>
+Comments are introduced by a hash sign (#), and continue until the end
+of the line. Blank lines are ignored.
+</p><p>
+The
+<B>gimprc</B>
+
+file associates values with properties. These properties may be set
+by lisp-like assignments of the form:
+</p><p>
+<DL COMPACT>
+<DT><DD>
+<B>(</B><I>property-name value</I><B>)</B>
+<DT>where:<DD>
+<DT><I>property-name</I>
+
+<DD>
+is one of the property names described below.
+<DT><I>value</I>
+
+<DD>
+is the value the property is to be set to.
+</DL>
+
+</p><p>
+Either spaces or tabs may be used to separate the name from the value.
+</p><p>
+
+<A NAME="lbAD"> </A>
+<H2>PROPERTIES</H2>
+
+Valid properties and their default values are:
+</p><p>
+<DL COMPACT>
+<DT>(temp-path "${gimp_dir}/tmp")<DD>
+
+Sets the temporary storage directory. Files will appear here during the course
+of running the GIMP. Most files will disappear when the GIMP exits, but some
+files are likely to remain, so it is best if this directory not be one that is
+shared by other users. This is a single folder.
+
+<DT>(swap-path "${gimp_dir}")<DD>
+
+Sets the swap file location. The gimp uses a tile based memory allocation
+scheme. The swap file is used to quickly and easily swap tiles out to disk and
+back in. Be aware that the swap file can easily get very large if the GIMP is
+used with large images. Also, things can get horribly slow if the swap file is
+created on a directory that is mounted over NFS. For these reasons, it may be
+desirable to put your swap file in "/tmp". This is a single folder.
+
+<DT>(stingy-memory-use no)<DD>
+
+There is always a tradeoff between memory usage and speed. In most cases, the
+GIMP opts for speed over memory. However, if memory is a big issue, try to
+enable this setting. Possible values are yes and no.
+
+<DT>(num-processors 1)<DD>
+
+On multiprocessor machines, if GIMP has been compiled with --enable-mp this
+sets how many processors GIMP should use simultaneously. This is an integer
+value.
+
+<DT>(tile-cache-size 64M)<DD>
+
+The tile cache is used to make sure the GIMP doesn't thrash tiles between
+memory and disk. Setting this value higher will cause the GIMP to use less
+swap space, but will also cause the GIMP to use more memory. Conversely, a
+smaller cache size causes the GIMP to use more swap space and less memory.
+The integer size can contain a suffix of 'B', 'K', 'M' or 'G' which makes GIMP
+interpret the size as being specified in bytes, kilobytes, megabytes or
+gigabytes. If no suffix is specified the size defaults to being specified in
+kilobytes.
+
+<DT>(interpolation-type linear)<DD>
+
+Sets the level of interpolation used for scaling and other transformations.
+Possible values are none, linear and cubic.
+
+<DT>(plug-in-path "${gimp_dir}/plug-ins:${gimp_plug_in_dir}/plug-ins")<DD>
+
+Sets the plug-in search path. This is a colon-separated list of folders to
+search.
+
+<DT>(module-path "${gimp_dir}/modules:${gimp_plug_in_dir}/modules")<DD>
+
+Sets the module search path. This is a colon-separated list of folders to
+search.
+
+<DT>(environ-path "${gimp_dir}/environ:${gimp_plug_in_dir}/environ")<DD>
+
+Sets the environ search path. This is a colon-separated list of folders to
+search.
+
+<DT>(brush-path "${gimp_dir}/brushes:${gimp_data_dir}/brushes")<DD>
+
+Sets the brush search path. This is a colon-separated list of folders to
+search.
+
+<DT>(brush-path-writable "${gimp_dir}/brushes")<DD>
+
+<BR> This is a colon-separated list of folders to search.
+
+<DT>(pattern-path "${gimp_dir}/patterns:${gimp_data_dir}/patterns")<DD>
+
+Sets the pattern search path. This is a colon-separated list of folders to
+search.
+
+<DT>(pattern-path-writable "${gimp_dir}/patterns")<DD>
+
+<BR> This is a colon-separated list of folders to search.
+
+<DT>(palette-path "${gimp_dir}/palettes:${gimp_data_dir}/palettes")<DD>
+
+Sets the palette search path. This is a colon-separated list of folders to
+search.
+
+<DT>(palette-path-writable "${gimp_dir}/palettes")<DD>
+
+<BR> This is a colon-separated list of folders to search.
+
+<DT>(gradient-path "${gimp_dir}/gradients:${gimp_data_dir}/gradients")<DD>
+
+Sets the gradient search path. This is a colon-separated list of folders to
+search.
+
+<DT>(gradient-path-writable "${gimp_dir}/gradients")<DD>
+
+<BR> This is a colon-separated list of folders to search.
+
+<DT>(font-path "${gimp_dir}/fonts:${gimp_data_dir}/fonts")<DD>
+
+Where to look for fonts. This is a colon-separated list of folders to search.
+
+<DT>(font-path-writable "${gimp_dir}/fonts")<DD>
+
+<BR> This is a colon-separated list of folders to search.
+
+<DT>(default-brush "Circle (11)")<DD>
+
+Specify a default brush. The brush is searched for in the specified brush
+path. This is a string value.
+
+<DT>(default-pattern "Pine")<DD>
+
+Specify a default pattern. The pattern is searched for in the specified
+pattern path. This is a string value.
+
+<DT>(default-palette "Default")<DD>
+
+Specify a default palette. The palette is searched for in the specified
+palette path. This is a string value.
+
+<DT>(default-gradient "FG to BG (RGB)")<DD>
+
+Specify a default gradient. The gradient is searched for in the specified
+gradient path. This is a string value.
+
+<DT>(default-font "Sans")<DD>
+
+Specify a default font. The font is searched for in the fontconfig font path.
+<BR> This is a string value.
+
+<DT>(global-brush yes)<DD>
+
+When enabled, the selected brush will be used for all tools. Possible values
+are yes and no.
+
+<DT>(global-pattern yes)<DD>
+
+When enabled, the selected pattern will be used for all tools. Possible
+values are yes and no.
+
+<DT>(global-palette yes)<DD>
+
+When enabled, the selected palette will be used for all tools. Possible
+values are yes and no.
+
+<DT>(global-gradient yes)<DD>
+
+When enabled, the selected gradient will be used for all tools. Possible
+values are yes and no.
+
+<DT>(global-font yes)<DD>
+
+When enabled, the selected font will be used for all tools. Possible values
+are yes and no.
+
+<DT>(default-image<DD>
+<BR> (width 256)
+<BR> (height 256)
+<BR> (unit inches)
+<BR> (xresolution 72.000000)
+<BR> (yresolution 72.000000)
+<BR> (resolution-unit inches)
+<BR> (image-type rgb)
+<BR> (fill-type background-fill)
+<BR> (comment "Created with The GIMP"))
+
+Sets the default image in the "File/New" dialog. This is a parameter list.
+
+<DT>(default-grid<DD>
+<BR> (style intersections)
+<BR> (fgcolor (color-rgba 0.000000 0.000000 0.000000 1.000000))
+<BR> (bgcolor (color-rgba 1.000000 1.000000 1.000000 1.000000))
+<BR> (xspacing 10.000000)
+<BR> (yspacing 10.000000)
+<BR> (spacing-unit inches)
+<BR> (xoffset 0.000000)
+<BR> (yoffset 0.000000)
+<BR> (offset-unit inches))
+
+Specify a default image grid. This is a parameter list.
+
+<DT>(undo-levels 5)<DD>
+
+Sets the minimal number of operations that can be undone. More undo levels are
+kept available until the undo-size limit is reached. This is an integer
+value.
+
+<DT>(undo-size 4M)<DD>
+
+Sets an upper limit to the memory that is used per image to keep operations on
+the undo stack. Regardless of this setting, at least as many undo-levels as
+configured can be undone. The integer size can contain a suffix of 'B', 'K',
+
+kilobytes, megabytes or gigabytes. If no suffix is specified the size defaults
+to being specified in kilobytes.
+
+<DT>(undo-preview-size large)<DD>
+
+Sets the size of the previews in the Undo History. Possible values are tiny,
+extra-small, small, medium, large, extra-large, huge, enormous and gigantic.
+
+<DT>(pluginrc-path "${gimp_dir}/pluginrc")<DD>
+
+Sets the pluginrc search path. This is a single filename.
+
+<DT>(layer-previews yes)<DD>
+
+Sets whether GIMP should create previews of layers and channels. Previews in
+the layers and channels dialog are nice to have but they can slow things down
+when working with large images. Possible values are yes and no.
+
+<DT>(layer-preview-size medium)<DD>
+
+Sets the default preview size for layers and channels. Possible values are
+tiny, extra-small, small, medium, large, extra-large, huge, enormous and
+gigantic.
+
+<DT>(thumbnail-size normal)<DD>
+
+Sets the size of the thumbnail saved with each image. Note that GIMP can not
+save thumbnails if layer previews are disabled. Possible values are none,
+normal and large.
+
+<DT>(install-colormap no)<DD>
+
+Install a private colormap; might be useful on pseudocolor visuals. Possible
+values are yes and no.
+
+<DT>(min-colors 144)<DD>
+
+Generally only a concern for 8-bit displays, this sets the minimum number of
+system colors allocated for the GIMP. This is an integer value.
+
+<DT>(marching-ants-speed 300)<DD>
+
+Speed of marching ants in the selection outline. This value is in
+milliseconds (less time indicates faster marching). This is an integer value.
+
+<DT>(resize-windows-on-zoom no)<DD>
+
+When enabled, the image window will automatically resize itself, when zooming
+into and out of images. Possible values are yes and no.
+
+<DT>(resize-windows-on-resize no)<DD>
+
+When enabled, the image window will automatically resize itself, whenever the
+physical image size changes. Possible values are yes and no.
+
+<DT>(default-dot-for-dot yes)<DD>
+
+When enabled, this will ensure that each pixel of an image gets mapped to a
+pixel on the screen. Possible values are yes and no.
+
+<DT>(initial-zoom-to-fit yes)<DD>
+
+When enabled, this will ensure that the full image is visible after a file is
+opened, otherwise it will be displayed with a scale of 1:1. Possible values
+are yes and no.
+
+<DT>(perfect-mouse yes)<DD>
+
+When enabled, the X server is queried for the mouse's current position on each
+motion event, rather than relying on the position hint. This means painting
+with large brushes should be more accurate, but it may be slower. Perversely,
+on some X servers enabling this option results in faster painting. Possible
+values are yes and no.
+
+<DT>(cursor-mode tool-icon)<DD>
+
+Sets the mode of cursor the GIMP will use. Possible values are tool-icon,
+tool-crosshair and crosshair.
+
+<DT>(cursor-updating yes)<DD>
+
+Context-dependent cursors are cool. They are enabled by default. However,
+they require overhead that you may want to do without. Possible values are
+yes and no.
+
+<DT>(show-brush-outline yes)<DD>
+
+When enabled, all paint tools will show a preview of the current brush's
+outline. Possible values are yes and no.
+
+<DT>(image-title-format "%D*%f-%p.%i (%t, %L) %z%%")<DD>
+
+Sets the text to appear in image window titles. This is a format string;
+certain % character sequences are recognised and expanded as follows:
+<BR>
+
+
+<BR>
+
+%% literal percent sign
+<BR>
+
+%f bare filename, or "Untitled"
+<BR>
+
+%F full path to file, or "Untitled"
+<BR>
+
+%p PDB image id
+<BR>
+
+%i view instance number
+<BR>
+
+%t image type (RGB, grayscale, indexed)
+<BR>
+
+%z zoom factor as a percentage
+<BR>
+
+%s source scale factor
+<BR>
+
+%d destination scale factor
+<BR>
+
+%Dx expands to x if the image is dirty, the empty string otherwise
+<BR>
+
+%Cx expands to x if the image is clean, the empty string otherwise
+<BR>
+
+%l the number of layers
+<BR>
+
+%L the number of layers (long form)
+<BR>
+
+%m memory used by the image
+<BR>
+
+%n the name of the active layer/channel
+<BR>
+
+%P the PDB id of the active layer/channel
+<BR>
+
+%w image width in pixels
+<BR>
+
+%W image width in real-world units
+<BR>
+
+%h image height in pixels
+<BR>
+
+%H image height in real-world units
+<BR>
+
+%u unit symbol
+<BR>
+
+%U unit abbreviation
+<BR>
+
+
+<BR>
+
+
+<DT>(image-status-format "%n (%m)")<DD>
+
+Sets the text to appear in image window status bars. This is a format string;
+certain % character sequences are recognised and expanded as follows:
+<BR>
+
+
+<BR>
+
+%% literal percent sign
+<BR>
+
+%f bare filename, or "Untitled"
+<BR>
+
+%F full path to file, or "Untitled"
+<BR>
+
+%p PDB image id
+<BR>
+
+%i view instance number
+<BR>
+
+%t image type (RGB, grayscale, indexed)
+<BR>
+
+%z zoom factor as a percentage
+<BR>
+
+%s source scale factor
+<BR>
+
+%d destination scale factor
+<BR>
+
+%Dx expands to x if the image is dirty, the empty string otherwise
+<BR>
+
+%Cx expands to x if the image is clean, the empty string otherwise
+<BR>
+
+%l the number of layers
+<BR>
+
+%L the number of layers (long form)
+<BR>
+
+%m memory used by the image
+<BR>
+
+%n the name of the active layer/channel
+<BR>
+
+%P the PDB id of the active layer/channel
+<BR>
+
+%w image width in pixels
+<BR>
+
+%W image width in real-world units
+<BR>
+
+%h image height in pixels
+<BR>
+
+%H image height in real-world units
+<BR>
+
+%u unit symbol
+<BR>
+
+%U unit abbreviation
+<BR>
+
+
+<BR>
+
+
+<DT>(confirm-on-close yes)<DD>
+
+Ask for confirmation before closing an image without saving. Possible values
+are yes and no.
+
+<DT>(monitor-xresolution 72.000000)<DD>
+
+Sets the monitor's horizontal resolution, in dots per inch. If set to 0,
+forces the X server to be queried for both horizontal and vertical resolution
+information. This is a float value.
+
+<DT>(monitor-yresolution 72.000000)<DD>
+
+Sets the monitor's vertical resolution, in dots per inch. If set to 0, forces
+the X server to be queried for both horizontal and vertical resolution
+information. This is a float value.
+
+<DT>(monitor-resolution-from-windowing-system yes)<DD>
+
+When enabled, the GIMP will use the monitor resolution from the windowing
+system. Possible values are yes and no.
+
+<DT>(navigation-preview-size medium)<DD>
+
+Sets the size of the navigation preview available in the lower right corner of
+the image window. Possible values are tiny, extra-small, small, medium,
+large, extra-large, huge, enormous and gigantic.
+
+<DT>(default-view<DD>
+<BR> (show-menubar yes)
+<BR> (show-rulers yes)
+<BR> (show-scrollbars yes)
+<BR> (show-statusbar yes)
+<BR> (show-selection yes)
+<BR> (show-layer-boundary yes)
+<BR> (show-guides yes)
+<BR> (show-grid no)
+<BR> (padding-mode default)
+<BR> (padding-color (color-rgba 1.000000 1.000000 1.000000 1.000000)))
+
+Sets the default settings for the image view. This is a parameter list.
+
+<DT>(default-fullscreen-view<DD>
+<BR> (show-menubar no)
+<BR> (show-rulers no)
+<BR> (show-scrollbars no)
+<BR> (show-statusbar no)
+<BR> (show-selection no)
+<BR> (show-layer-boundary no)
+<BR> (show-guides no)
+<BR> (show-grid no)
+<BR> (padding-mode custom)
+<BR> (padding-color (color-rgba 0.000000 0.000000 0.000000 1.000000)))
+
+Sets the default settings used when an image is viewed in fullscreen mode.
+This is a parameter list.
+
+<DT>(activate-on-focus yes)<DD>
+
+When enabled, an image will become the active image when its image window
+receives the focus. This is useful for window managers using "click to focus".
+<BR> Possible values are yes and no.
+
+<DT>(transparency-size medium-checks)<DD>
+
+Sets the size of the checkerboard used to display transparency. Possible
+values are small-checks, medium-checks and large-checks.
+
+<DT>(transparency-type gray-checks)<DD>
+
+Sets the manner in which transparency is displayed in images. Possible values
+are light-checks, gray-checks, dark-checks, white-only, gray-only and
+black-only.
+
+<DT>(snap-distance 8)<DD>
+
+This is the distance in pixels where Guide and Grid snapping activates. This
+is an integer value.
+
+<DT>(default-threshold 15)<DD>
+
+Tools such as fuzzy-select and bucket fill find regions based on a seed-fill
+algorithm. The seed fill starts at the intially selected pixel and progresses
+in all directions until the difference of pixel intensity from the original is
+greater than a specified threshold. This value represents the default
+threshold. This is an integer value.
+
+<DT>(info-window-per-display no)<DD>
+
+When enabled, the GIMP will use a different info window per image view.
+Possible values are yes and no.
+
+<DT>(trust-dirty-flag no)<DD>
+
+When enabled, the GIMP will not save if the image is unchanged since opening
+it. Possible values are yes and no.
+
+<DT>(save-device-status no)<DD>
+
+Remember the current tool, pattern, color, and brush across GIMP sessions.
+Possible values are yes and no.
+
+<DT>(save-session-info yes)<DD>
+
+Save the positions and sizes of the main dialogs when the GIMP exits.
+Possible values are yes and no.
+
+<DT>(restore-session yes)<DD>
+
+Let GIMP try to restore your last saved session on each startup. Possible
+values are yes and no.
+
+<DT>(show-tips yes)<DD>
+
+Enable to display a handy GIMP tip on startup. Possible values are yes and
+no.
+
+<DT>(show-tool-tips yes)<DD>
+
+Enable to display tooltips. Possible values are yes and no.
+
+<DT>(tearoff-menus yes)<DD>
+
+When enabled, menus can be torn off. Possible values are yes and no.
+
+<DT>(can-change-accels no)<DD>
+
+When enabled, you can change keyboard shortcuts for menu items by hitting a
+key combination while the menu item is highlighted. Possible values are yes
+and no.
+
+<DT>(save-accels yes)<DD>
+
+Save changed keyboard shortcuts when the GIMP exits. Possible values are yes
+and no.
+
+<DT>(restore-accels yes)<DD>
+
+Restore saved keyboard shortcuts on each GIMP startup. Possible values are
+yes and no.
+
+<DT>(last-opened-size 10)<DD>
+
+How many recently opened image filenames to keep on the File menu. This is an
+integer value.
+
+<DT>(max-new-image-size 64M)<DD>
+
+GIMP will warn the user if an attempt is made to create an image that would
+take more memory than the size specified here. The integer size can contain a
+suffix of 'B', 'K', 'M' or 'G' which makes GIMP interpret the size as being
+specified in bytes, kilobytes, megabytes or gigabytes. If no suffix is
+specified the size defaults to being specified in kilobytes.
+
+<DT>(theme-path "${gimp_dir}/themes:${gimp_data_dir}/themes")<DD>
+
+Sets the theme search path. This is a colon-separated list of folders to
+search.
+
+<DT>(theme "Default")<DD>
+
+The name of the theme to use. This is a string value.
+
+<DT>(use-help yes)<DD>
+
+When enabled, pressing F1 will open the help browser. Possible values are yes
+and no.
+
+<DT>(help-locales "")<DD>
+
+Specifies the language preferences used by the help system. This is a
+colon-separated list of language identifiers with decreasing priority. If
+empty, the language is taken from the user's locale setting. This is a string
+value.
+
+<DT>(help-browser gimp)<DD>
+
+Sets the browser used by the help system. Possible values are gimp and
+web-browser.
+
+<DT>(web-browser "mozilla %s")<DD>
+
+Sets the external web browser to be used. This can be an absolute path or the
+name of an executable to search for in the user's PATH. If the command
+contains '%s' it will be replaced with the URL, else the URL will be appended
+to the command with a space separating the two. This is a single filename.
+
+<DT>(toolbox-window-hint normal)<DD>
+
+The window type hint that is set on the toolbox. This may affect how your
+window manager decorates and handles the toolbox window. Possible values are
+normal and utility.
+
+<DT>(dock-window-hint normal)<DD>
+
+The window type hint that is set on dock windows. This may affect the way your
+window manager decorates and handles dock windows. Possible values are normal
+and utility.
+
+<DT>(fractalexplorer-path "${gimp_dir}/fractalexplorer:${gimp_data_dir}/fractalexplorer")<DD>
+
+Where to search for fractals used by the Fractal Explorer plug-in. This is a
+colon-separated list of folders to search.
+
+<DT>(gfig-path "${gimp_dir}/gfig:${gimp_data_dir}/gfig")<DD>
+
+Where to search for Gfig figures used by the Gfig plug-in. This is a
+colon-separated list of folders to search.
+
+<DT>(gflare-path "${gimp_dir}/gflare:${gimp_data_dir}/gflare")<DD>
+
+Where to search for gflares used by the GFlare plug-in. This is a
+colon-separated list of folders to search.
+
+<DT>(gimpressionist-path "${gimp_dir}/gimpressionist:${gimp_data_dir}/gimpressionist")<DD>
+
+Where to search for data used by the Gimpressionist plug-in. This is a
+colon-separated list of folders to search.
+
+<DT>(script-fu-path "${gimp_dir}/scripts:${gimp_data_dir}/scripts")<DD>
+
+This path will be searched for scripts when the Script-Fu plug-in is run.
+This is a colon-separated list of folders to search.
+</DL>
+</p><p>
+
+<A NAME="lbAE"> </A>
+<H2>PATH EXPANSION</H2>
+
+Strings of type PATH are expanded in a manner similar to
+<B><A HREF="http://www.gnu.org/software/bash/bash.html";>bash</A></B>(1).
+
+Specifically: tilde (~) is expanded to the user's home directory. Note that
+the bash feature of being able to refer to other user's home directories
+by writing ~userid/ is not valid in this file.
+</p><p>
+
+${variable} is expanded to the current value of an environment variable.
+There are a few variables that are pre-defined:
+</p><p>
+<DL COMPACT>
+<DT><I>gimp_dir</I>
+
+<DD>
+The personal gimp directory which is set to the value of the environment
+variable GIMP2_DIRECTORY or to ~/.gimp-2.0.
+<DT><I>gimp_data_dir</I>
+
+<DD>
+Nase for paths to shareable data, which is set to the value of the
+environment variable GIMP2_DATADIR or to the compiled-in default value
+${prefix}/share/gimp/2.0.
+<DT><I>gimp_plug_in_dir</I>
+
+<DD>
+Base to paths for architecture-specific plugins and modules, which is set
+to the value of the environment variable GIMP2_PLUGINDIR or to the
+compiled-in default value ${exec_prefix}/lib/gimp/2.0.
+<DT><I>gimp_sysconf_dir</I>
+
+<DD>
+Path to configuration files, which is set to the value of the environment
+variable GIMP2_SYSCONFDIR or to the compiled-in default value
+${prefix}/etc/gimp/2.0.
+</DL>
+</p><p>
+<A NAME="lbAF"> </A>
+<H2>FILES</H2>
+
+<DL COMPACT>
+<DT><I>${prefix}/etc/gimp/2.0/gimprc</I>
+
+<DD>
+System-wide configuration file
+<DT><I></I><B>$HOME</B>/.gimp-2.0/gimprc
+
+<DD>
+Per-user configuration file
+</DL>
+</p><p>
+<A NAME="lbAG"> </A>
+<H2>SEE ALSO</H2>
+
+<B><A HREF="man-gimp-2.0.html">gimp</A></B>(1),
+
+<B><A HREF="man-gimptool-2.0.html">gimptool</A></B>(1),
+
+<B><A HREF="man-gimp-remote-2.0.html">gimp-remote</A></B>(1)
+
+</p><p>
+
+<HR>
+<A NAME="index"> </A><H2>Index</H2>
+<DL>
+<DT><A HREF="#lbAB">NAME</A><DD>
+<DT><A HREF="#lbAC">DESCRIPTION</A><DD>
+<DT><A HREF="#lbAD">PROPERTIES</A><DD>
+<DT><A HREF="#lbAE">PATH EXPANSION</A><DD>
+<DT><A HREF="#lbAF">FILES</A><DD>
+<DT><A HREF="#lbAG">SEE ALSO</A><DD>
+</DL>
+<HR>
+This document was created by
+<A HREF="http://www.w3.org/Tools/man2html.html";>man2html</A>,
+using the manual pages.<BR>
+Time: 00:01:13 GMT, March 30, 2004
+</p>
+</BODY>
+</HTML>
diff --git a/content/unix/man-gimptool-2.0.html b/content/unix/man-gimptool-2.0.html
new file mode 100644
index 0000000..411065d
--- /dev/null
+++ b/content/unix/man-gimptool-2.0.html
@@ -0,0 +1,321 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML><HEAD><TITLE>Man page of GIMPTOOL-2.0</TITLE>
+</HEAD><BODY>
+<p>
+<H1>GIMPTOOL-2.0</H1>
+Section: GIMP Manual Pages (1)<BR>Updated: March 23 2004<BR><A HREF="#index">Index</A>
+
+<A NAME="lbAB"> </A>
+<H2>NAME</H2>
+
+gimptool-2.0 - script to perform various GIMPy functions
+<A NAME="lbAC"> </A>
+<H2>SYNOPSIS</H2>
+
+<B>gimptool-2.0</B>
+
+[--prefix<I>[=DIR]</I>] [--exec-prefix<I>[=DIR]</I>] [--version]
+[--help] [--quiet] [--silent] [-n] [--just-print] [--dry-run]
+[--recon] [--bindir] [--sbindir] [--libexecdir] [--datadir]
+[--sysconfdir] [--sharedstatedir] [--localstatedir] [--libdir]
+[--infodir] [--mandir] [--includedir] [--gimpplugindir]
+[--gimpdatadir] [--libs] [--libs-noui] [--cflags] [--cflags-noi]
+[--build <I>plug-in.c</I>]
+[--build-strip <I>plug-in.c</I>] [--install <I>plug-in.c</I>]
+[--install-strip <I>plug-in.c</I>] [--install-admin <I>plug-in.c</I>]
+[--install-bin <I>plug-in</I>]
+[--install-admin-strip <I>plug-in.c</I>]
+[--install-bin-strip <I>plug-in</I>]
+[--install-admin-bin <I>plug-in</I>]
+[--install-script <I>script.scm</I>]
+[--install-admin-script <I>script.scm</I>]
+[--uninstall-bin <I>plug-in</I>] [--uninstall-admin-bin <I>plug-in</I>]
+[--uninstall-script <I>script.scm</I>]
+[--uninstall-admin-script <I>script.scm</I>]
+</p><p>
+<A NAME="lbAD"> </A>
+<H2>DESCRIPTION</H2>
+
+</p><p>
+
+<I>gimptool-2.0</I> is a tool that can, among other things, build
+plug-ins or scripts and install them if they are distributed in one
+source file.
+</p><p>
+
+<I>gimptool-2.0</I> can also be used by programs that need to know what
+libraries and include-paths <I>GIMP</I> was compiled with. This is
+especially useful in Makefiles.
+</p><p>
+<A NAME="lbAE"> </A>
+<H2>OPTIONS</H2>
+
+
+<I>gimptool-2.0</I> accepts the following options:
+<DL COMPACT>
+<DT><B>--version</B>
+
+<DD>
+Print the currently installed version of <I>GIMP</I> on the standard output.
+<DT><B>--help</B>
+
+<DD>
+Print out the help blurb, showing commonly used commandline options.
+<DT><B>--quiet</B>
+
+<DD>
+Run quietly without echoing any of the build commands.
+<DT><B>--silent</B>
+
+<DD>
+Run silently without echoing any of the build commands. Same as --quiet.
+<DT><B>-n</B>
+
+<DD>
+Test mode. Print the commands but dont actually execute them. Useful for
+making dry runs for testing.
+<DT><B>--just-print</B>
+
+<DD>
+Test mode. Print the commands but dont actually execute them. Same as -n.
+<DT><B>--dry-run</B>
+
+<DD>
+Test mode. Print the commands but dont actually execute them. Same as -n.
+<DT><B>--recon</B>
+
+<DD>
+Test mode. Print the commands but dont actually execute them. Same as -n.
+<DT><B>--bindir</B>
+
+<DD>
+Outputs the bindir used to install the <I>GIMP</I>.
+<DT><B>--sbindir</B>
+
+<DD>
+Outputs the sbindir used to install the <I>GIMP</I>.
+<DT><B>--libexecdir</B>
+
+<DD>
+Outputs the libexecdir used to install the <I>GIMP</I>.
+<DT><B>--datadir</B>
+
+<DD>
+Outputs the datadir used to install the <I>GIMP</I>.
+<DT><B>--sysconfdir</B>
+
+<DD>
+Outputs the sysconfdir used to install the <I>GIMP</I>.
+<DT><B>--sharedstatedir</B>
+
+<DD>
+Outputs the sharedstatedir used to install the <I>GIMP</I>.
+<DT><B>--localstatedir</B>
+
+<DD>
+Outputs the localstatedir used to install the <I>GIMP</I>.
+<DT><B>--libdir</B>
+
+<DD>
+Outputs the libdir used to install the <I>GIMP</I>.
+<DT><B>--infodir</B>
+
+<DD>
+Outputs the infodir used to install the <I>GIMP</I>.
+<DT><B>--mandir</B>
+
+<DD>
+Outputs the mandir used to install the <I>GIMP</I>.
+<DT><B>--includedir</B>
+
+<DD>
+Outputs the includedir used to install the <I>GIMP</I>.
+<DT><B>--gimpdatadir</B>
+
+<DD>
+Outputs the actual directory where the <I>GIMP</I> data files were installed.
+<DT><B>--gimpplugindir</B>
+
+<DD>
+Outputs the actual directory where the <I>GIMP</I> plugins were installed.
+<DT><B>--build </B><I>plug-in.c</I>
+
+<DD>
+Compile and link <I>plug-in.c</I> into a <I>GIMP</I> plug-in.
+<DT><B>--build-strip </B><I>plug-in.c</I>
+
+<DD>
+Compile,link, and strip <I>plug-in.c</I> into a <I>GIMP</I> plug-in.
+<DT><B>--install </B><I>plug-in.c</I>
+
+<DD>
+Compile, link, and install <I>plug-in.c</I> into the user's personal
+<I>GIMP</I> plug-in directory (<B>$HOME</B>/.gimp-2.0/plug-ins)
+<DT><B>--install-strip </B><I>plug-in.c</I>
+
+<DD>
+Compile, link,strip, and install <I>plug-in.c</I> into the user's
+personal <I>GIMP</I>
+plug-in directory (<B>$HOME</B>/.gimp-2.0/plug-ins)
+<DT><B>--install-admin </B><I>plug-in.c</I>
+
+<DD>
+Compile, link, and install <I>plug-in.c</I> into the system-wide <I>GIMP</I>
+plug-in directory (${exec_prefix}/lib/gimp/2.0/plug-ins)
+<DT><B>--install-bin </B><I>plug-in</I>
+
+<DD>
+Install <I>plug-in</I> into the user's personal <I>GIMP</I>
+plug-in directory (<B>$HOME</B>/.gimp-2.0/plug-ins)
+<DT><B>--install-admin-bin </B><I>plug-in</I>
+
+<DD>
+Install <I>plug-in</I> into the system-wide <I>GIMP</I>
+plug-in directory (${exec_prefix}/lib/gimp/2.0/plug-ins)
+<DT><B>--install-bin-strip </B><I>plug-in</I>
+
+<DD>
+Install stripped <I>plug-in</I> into the user's personal <I>GIMP</I>
+plug-in directory (<B>$HOME</B>/.gimp-2.0/plug-ins)
+<DT><B>--install-admin-bin-strip </B><I>plug-in</I>
+
+<DD>
+Install stripped <I>plug-in</I> into the system-wide <I>GIMP</I>
+plug-in directory (${exec_prefix}/lib/gimp/2.0/plug-ins)
+<DT><B>--install-script </B><I>script.scm</I>
+
+<DD>
+Install <I>script.scm</I> into the user's personal <I>GIMP</I>
+script directory (<B>$HOME</B>/.gimp-2.0/scripts)
+<DT><B>--install-admin-script </B><I>script.scm</I>
+
+<DD>
+Install <I>script.scm</I> into the system-wide <I>GIMP</I>
+script directory (${prefix}/share/gimp/2.0/scripts)
+<DT><B>--uninstall-bin </B><I>plug-in</I>
+
+<DD>
+Uninstall <I>plug-in</I> from the user's personal <I>GIMP</I>
+plug-in directory (<B>$HOME</B>/.gimp-2.0/plug-ins)
+<DT><B>--uninstall-admin-bin </B><I>plug-in</I>
+
+<DD>
+Uninstall <I>plug-in</I> from the system-wide <I>GIMP</I>
+plug-in directory (${exec_prefix}/lib/gimp/2.0/plug-ins)
+<DT><B>--uninstall-script </B><I>script.scm</I>
+
+<DD>
+Uninstall <I>script.scm</I> from the user's personal <I>GIMP</I>
+script directory (<B>$HOME</B>/.gimp-2.0/scripts)
+<DT><B>--uninstall-admin-script </B><I>script.scm</I>
+
+<DD>
+Uninstall <I>script.scm</I> from the system-wide <I>GIMP</I>
+script directory (${prefix}/share/gimp/2.0/scripts)
+<DT><B>--libs</B>
+
+<DD>
+Print the linker flags that are necessary to link a <I>GIMP</I> plug-in.
+<DT><B>--libs-noui</B>
+
+<DD>
+Print the linker flags that are necessary to link a <I>GIMP</I> plug-in, for
+plugins that do not require the GTK libs.
+<DT><B>--cflags</B>
+
+<DD>
+Print the compiler flags that are necessary to compile a <I>GIMP</I> plug-in.
+<DT><B>--clags-noui</B>
+
+<DD>
+Print the compiler flags that are necessary to compile a <I>GIMP</I> plug-in
+for plugins that do not require the GTK libs.
+<DT><B>--prefix=PREFIX</B>
+
+<DD>
+If specified, use PREFIX instead of the installation prefix that <I>GIMP</I>
+was built with when computing the output for the --cflags and
+--libs options. This option is also used for the exec prefix
+if --exec-prefix was not specified. This option must be specified
+before any --libs or --cflags options.
+<DT><B>--exec-prefix=PREFIX</B>
+
+<DD>
+If specified, use PREFIX instead of the installation exec prefix that
+<I>GIMP</I> was built with when computing the output for the --cflags
+and --libs options. This option must be specified before any
+--libs or --cflags options.
+</p><p>
+</DL>
+<A NAME="lbAF"> </A>
+<H2>ENVIRONMENT</H2>
+
+</p><p>
+
+<DL COMPACT>
+<DT><B>CC</B>
+
+<DD>
+to get the name of the desired C compiler.
+<DT><B>CFLAGS</B>
+
+<DD>
+to get the preferred flags to pass to the C compiler for plug-in building.
+<DT><B>DESTDIR</B>
+
+<DD>
+to add a prefix to the install/uninstall path.
+<DT><B>LDFLAGS</B>
+
+<DD>
+to get the prefered flags for passing to the linker.
+<DT><B>LIBS</B>
+
+<DD>
+for passing extra libs that may be needed in the build process. For example,
+LIBS=-lintl .
+<DT><B>PKG_CONFIG</B>
+
+<DD>
+to get the location of the pkg-config program used to determine details
+about your glib, pango and gtk+ installation.
+</DL>
+</p><p>
+<A NAME="lbAG"> </A>
+<H2>SEE ALSO</H2>
+
+<B><A HREF="man-gimp-2.0.html">gimp</A></B>(1),
+
+<B><A HREF=" man-gimprc-2.0.html">gimprc</A></B>(5),
+
+</p><p>
+<A NAME="lbAH"> </A>
+<H2>AUTHORS</H2>
+
+gimptool was written by Manish Singh (<A HREF="mailto:yosh gimp org">yosh gimp org</A>) and is based on
+gtk-config by Owen Taylor (<A HREF="mailto:owen gtk org">owen gtk org</A>).
+</p><p>
+This man page was written by Ben Gertzfield (<A HREF="mailto:che debian org">che debian org</A>), and tweaked
+by Manish Singh (<A HREF="mailto:yosh gimp org">yosh gimp org</A>), Adrian Likins (<A HREF="mailto:adrian
gimp org">adrian gimp org</A>) and Marc
+Lehmann (<A HREF="mailto:pcg goof com">pcg goof com</A>>).
+</p><p>
+
+<HR>
+<A NAME="index"> </A><H2>Index</H2>
+<DL>
+<DT><A HREF="#lbAB">NAME</A><DD>
+<DT><A HREF="#lbAC">SYNOPSIS</A><DD>
+<DT><A HREF="#lbAD">DESCRIPTION</A><DD>
+<DT><A HREF="#lbAE">OPTIONS</A><DD>
+<DT><A HREF="#lbAF">ENVIRONMENT</A><DD>
+<DT><A HREF="#lbAG">SEE ALSO</A><DD>
+<DT><A HREF="#lbAH">AUTHORS</A><DD>
+</DL>
+<HR>
+This document was created by
+<A HREF="http://www.w3.org/Tools/man2html.html";>man2html</A>,
+using the manual pages.<BR>
+Time: 20:34:06 GMT, March 29, 2004
+</P>
+</BODY>
+</HTML>
diff --git a/content/unix/ui-calibrate.png b/content/unix/ui-calibrate.png
new file mode 100644
index 0000000..ac1c8bb
Binary files /dev/null and b/content/unix/ui-calibrate.png differ
diff --git a/content/unix/ui-log.png b/content/unix/ui-log.png
new file mode 100644
index 0000000..e08f10d
Binary files /dev/null and b/content/unix/ui-log.png differ
diff --git a/content/unix/ui-monitor.png b/content/unix/ui-monitor.png
new file mode 100644
index 0000000..5594883
Binary files /dev/null and b/content/unix/ui-monitor.png differ
diff --git a/content/unix/ui-performance.png b/content/unix/ui-performance.png
new file mode 100644
index 0000000..18d2580
Binary files /dev/null and b/content/unix/ui-performance.png differ
diff --git a/content/unix/ui-personal.png b/content/unix/ui-personal.png
new file mode 100644
index 0000000..6cdcf3f
Binary files /dev/null and b/content/unix/ui-personal.png differ
diff --git a/content/unix/ui-welcome.png b/content/unix/ui-welcome.png
new file mode 100644
index 0000000..e4ea485
Binary files /dev/null and b/content/unix/ui-welcome.png differ
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]
![http://classic.gimp.org/icons/frontpage-small.gif"](http://classic.gimp.org/icons/frontpage-small.gif"){kind=link}
