[gimp-web/gimp-web-static] Added root URL files and how to do it for others
- From: Pat David <patdavid src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [gimp-web/gimp-web-static] Added root URL files and how to do it for others
- Date: Wed, 12 Aug 2015 21:09:54 +0000 (UTC)
commit 243eb9a3736ce2364cc688edfd3e9e2c017f0c09
Author: Pat David <patdavid gmail com>
Date: Wed Aug 12 16:09:11 2015 -0500
Added root URL files and how to do it for others
content/about/index.md | 4 +-
content/about/irc.de.md | 9 +++
content/about/irc.md | 79 +++++++++++++++++++-
content/about/mail_lists.md | 91 +++++++++++++++++++++++
content/about/prehistory.md | 2 +-
content/about/team.md | 96 +++++++++++++++++++++++++
content/about/webmasters.md | 36 +++++++++
content/tutorials/GIMP_Quickies/index.md | 24 +++---
plugins/page_hierarchy_gimp/page_hierarchy.py | 61 ++++++++++------
9 files changed, 360 insertions(+), 42 deletions(-)
---
diff --git a/content/about/index.md b/content/about/index.md
index 61326f7..71f0e0f 100644
--- a/content/about/index.md
+++ b/content/about/index.md
@@ -1,9 +1,7 @@
Title: About GIMP
Date: 2015-07-29T14:40:35-05:00
Modified: 2015-07-29T14:40:43-05:00
-Authors: Pat David
-Summary: About the project.
-slug: about
+Author: Pat David
## Introduction
diff --git a/content/about/irc.de.md b/content/about/irc.de.md
new file mode 100644
index 0000000..e8cbce7
--- /dev/null
+++ b/content/about/irc.de.md
@@ -0,0 +1,9 @@
+Title: IRC Channels Related to GIMP
+Date: 2015-08-11T16:24:52-05:00
+Author: Pat David
+url: irc.de.html
+save_as: irc.de.html
+status: hidden
+lang: de
+
+Mehrere IRC-Kanäle und Mailinglisten sind für die Diskussion GIMP-Themen zur Verfügung. IRC bietet
Echtzeit-Kommunikation, aber bewusst sein, dass es lange Zeit des Schweigens in den Kanälen sein, wenn andere
Benutzer besetzt sind oder von ihren Tastaturen. Wenn Sie die GIMP IRC-Kanälen verbinden, fragen Sie bitte
nicht, wenn jemand Ihnen helfen können. Wenn Sie eine Frage haben, wenden Sie sich direkt und dann geduldig
warten, um zu sehen, wenn jemand antwortet. Weitere Empfehlungen finden Sie unten auf dieser Seite finden.
diff --git a/content/about/irc.md b/content/about/irc.md
index 99ade38..952a61f 100644
--- a/content/about/irc.md
+++ b/content/about/irc.md
@@ -1,7 +1,80 @@
Title: IRC Channels Related to GIMP
Date: 2015-08-11T16:24:52-05:00
Author: Pat David
-slug: ''
-filename: irc.html
+url: irc.html
+save_as: irc.html
+status: hidden
+
+
+Several IRC channels and [mailing lists](/mail_lists.html) are available for discussing GIMP-related topics.
IRC offers real-time communication, but be aware that there may be long periods of silence in the channels
when other users are busy or away from their keyboards. When you join the GIMP IRC channels, please do not
ask if somebody can help you. If you have a question, ask directly and then wait patiently to see if someone
answers. Other recommendations can be found [at the bottom of this page](#rules).
+
+The official GIMP IRC channels are on GIMPNet ([irc.gimp.org](irc://irc.gimp.org/)) and have existed for
more than 10 years. Many [channels related to GTK+ and GNOME](http://live.gnome.org/GnomeIrcChannels) are
also on GIMPNet.
+
+<dl>
+ <dt>irc://irc.gimp.org/<a href="irc://irc.gimp.org/gimp-users">#gimp-users</a></dt>
+ <dd>The main support channel for GIMP users. This is probably the right
+ place to ask questions (but please see the <a href="#rules">hints</a> at the
+ bottom of this page). This channel might be less scary than #gimp,
+ especially for new users...</dd>
+
+ <dt>irc://irc.gimp.org/<a href="irc://irc.gimp.org/gimp">#gimp</a></dt>
+ <dd>This is the main GIMP channel, created in early 1997. Both users and
+ developers hang around, and almost any question about GIMP is ontopic. From
+ a user's point of view, this can be a downside: discussion often focuses on
+ GIMP development and the bleeding edge version of GIMP.</dd>
+
+ <dt>irc://irc.gimp.org/<a href="irc://irc.gimp.org/gimp-web">#gimp-web</a></dt>
+ <dd>A channel devoted to this web site and related GIMP sites. Most active
+ when the migration from <a href="http://classic.gimp.org/";>classic.gimp.org</a> happened a few years
+ ago, it is pretty quiet now. But if you have suggestions or issues with the
+ current website, this channel is for you.</dd>
+
+ <dt>irc://irc.gimp.org/<a href="irc://irc.gimp.org/gimps">#gimps</a></dt>
+ <dd>Being an abbreviation of "gimp social", this channel is for the GIMP
+ people, and anything but GIMP is ontopic here.</dd>
+
+ <dt>irc://irc.gimp.org/<a href="irc://irc.gimp.org/gimp-fr">#gimp-fr</a></dt>
+ <dd>GIMP in French</dd>
+
+</dl>
+
+### Other IRC networks
+
+The main GIMP IRC channels described above are on GIMPNet (irc://irc.gimp.org/), the official network for
topics related to GIMP and GNOME. However, several channels also exist on other IRC networks:
+
+<dl>
+ <dt>irc://irc.freenode.net/<a href="irc://irc.freenode.net/gimp">#gimp</a></dt>
+ <dd>It is recommended that users migrate from that channel to <a
href="irc://irc.gimp.org/gimp-users">#gimp-users</a> on GIMPNet, described
+ above.</dd>
+
+ <dt>irc://irc.freenode.net/<a href="irc://irc.freenode.net/gimp-fr">#gimp-fr</a></dt>
+ <dd>It is recommended that users migrate from that channel to <a
href="irc://irc.gimp.org/gimp-fr">#gimp-fr</a> on GIMPNet, described
+ above.</dd>
+
+ <dt>irc://irc.freenode.net/<a href="irc://irc.freenode.net/gimp-de">#gimp-de</a></dt>
+ <dd>GIMP in German.</dd>
+
+ <dt>irc://irc.freenode.net/<a href="irc://irc.freenode.net/gimp-pl">#gimp-pl</a></dt>
+ <dd>GIMP in Polish.</dd>
+
+ <dt>irc://irc.freenode.net/<a href="irc://irc.freenode.net/gimp-es">#gimp-es</a></dt>
+ <dd>GIMP in Spanish.</dd>
+
+ <dt>irc://irc.freenode.net/<a href="irc://irc.freenode.net/gimp-it">#gimp-it</a></dt>
+ <dd>GIMP in Italian.</dd>
+
+</dl>
+
+### <a name="rules"></a>Rules and hints
+
+* Don't expect to be greeted. Start talking or listen.
+* <a name="just_ask"></a>Don't ask to ask, just ask. Questions like "May I ask a question?" are obsolete,
you have obviously joined the channel to do something. Questions like "Can someone help me?" cannot be
answered until you have described your problem. Be direct and describe your problem or question immediately.
+* Be patient. This is not a phone support line.
+* Don't ask frequently asked questions. Using a search engine, visiting [this web site](/), the [developer
site](http://wiki.gimp.org/) and reading the [documentation](/docs/) will help you to determine if your
question falls into this category. It's not forbidden to ask the question, though, but you should be prepared
for answers like "RTFM" or "use Google".
+* Don't mess with other users. In case of doubt, they are far more experienced than you, might have admin
status or be the equivalent to gods, IRC operators. An occasional joke is ok (unless your sense of humor is
really weird), but try to keep a minimum of maturity.
+* Don't make fun of other people's problems with the language. English is the language used in the main
GIMP-related channels and it might not be the native language of some users.
+* Don't assume that you can break the rules if others seem to do so. There are a few users in #gimp who
have been granted a jester's license. Additionally, there is an unwritten rule that you may talk offtopic up
to the amount of your ontopic contribution.
+* In #gimp (the main channel), the GIMP developers have special privileges and may use and abuse them. If
you are not comfortable with that, then you should join #gimp-users instead.
+* Don't mess with the admins. You will regret it.
+* Say what you want, tell us what you've done, and be precise about it.
-Chatting us up on irc!
diff --git a/content/about/mail_lists.md b/content/about/mail_lists.md
new file mode 100644
index 0000000..809138c
--- /dev/null
+++ b/content/about/mail_lists.md
@@ -0,0 +1,91 @@
+Title: Mailing Lists
+Date: 2015-08-12T15:47:05-05:00
+Author: Pat David
+url: mail_lists.html
+save_as: mail_lists.html
+status: hidden
+
+
+If you want to discuss features, tips, tricks or contribute to the development of GIMP, then we have several
useful mailing lists and [IRC channels](/irc.html) for you.
+
+<dl>
+ <dt><a href="https://mail.gnome.org/mailman/listinfo/gimp-user-list";>GIMP User</a></dt>
+ <dd>The original (mostly unix based) user list. For the everyday user.
+ Here you will find tips for doing cool effects, user questions, etc.<br>
+ Archives:
+ <a href="https://mail.gnome.org/archives/gimp-user-list/";>GNOME</a>,
+ <a href="http://www.mail-archive.com/gimp-user-list%40gnome.org/";>mail-archive</a>,
+ <a href="http://news.gmane.org/gmane.comp.video.gimp.user/";>Gmane</a>,
+ <a href="http://gimp.1065349.n5.nabble.com/Users-f3.html";>nabble</a>,
+ <a href="http://www.spinics.net/lists/gimp/";>spinics</a><br>
+ Old Archives:
+ <a href="http://www.mail-archive.com/gimp-user%40lists.xcf.berkeley.edu/";>mail-archive</a>
+ </dd>
+
+ <dt><a href="https://mail.gnome.org/mailman/listinfo/gimp-developer-list";>GIMP Developer</a></dt>
+ <dd>The GIMP developer list. For plug-in developers and core program
+ developers; discussion about the source code.<br>
+ Archives:
+ <a href="https://mail.gnome.org/archives/gimp-developer-list/";>GNOME</a>,
+ <a href="http://www.mail-archive.com/gimp-developer-list%40gnome.org/";>mail-archive</a>,
+ <a href="http://news.gmane.org/gmane.comp.video.gimp.devel/";>Gmane</a>,
+ <a href="http://gimp.1065349.n5.nabble.com/Developers-f15145.html";>nabble</a><br>
+ Old Archives:
+ <a href="http://www.mail-archive.com/gimp-developer%40lists.xcf.berkeley.edu/";>mail-archive</a>
+ </dd>
+
+ <dt><a href="https://mail.gnome.org/mailman/listinfo/gegl-developer-list";>GEGL Developer</a></dt>
+ <dd>The GEGL developer list. For developers interested in
+ contributing to <a href="http://www.gegl.org/";>GEGL</a>, the new
+ architecture for image processing.<br>
+ Archives:
+ <a href="https://mail.gnome.org/archives/gegl-developer-list/";>GNOME</a>,
+ <a href="http://www.mail-archive.com/gegl-developer-list%40gnome.org/";>mail-archive</a>,
+ <a href="http://news.gmane.org/gmane.comp.video.gegl.devel/";>Gmane</a><br>
+ Old Archives:
+ <a href="http://www.mail-archive.com/gegl-developer%40lists.xcf.berkeley.edu/";>mail-archive</a>
+ </dd>
+
+ <dt><a href="https://mail.gnome.org/mailman/listinfo/gimp-web-list";>GIMP Web</a></dt>
+ <dd>The GIMP web list. For discussion about the contents and
+ structure of this web site.<br>
+ Archives:
+ <a href="https://mail.gnome.org/archives/gimp-web-list/";>GNOME</a>,
+ <a href="http://www.mail-archive.com/gimp-web-list%40gnome.org/";>mail-archive</a>,
+ <a href="http://news.gmane.org/gmane.comp.video.gimp.web/";>Gmane</a><br>
+ </dd>
+
+ <dt><a href="https://mail.gnome.org/mailman/listinfo/gimp-docs-list";>GIMP Docs</a></dt>
+ <dd>The GIMP documentation list. For discussion about the
+ <a href="http://docs.gimp.org";>GIMP User Manual</a> and all derivative works.<br>
+ Archives:
+ <a href="https://mail.gnome.org/archives/gimp-docs-list/";>GNOME</a>,
+ <a href="http://www.mail-archive.com/gimp-docs-list%40gnome.org/";>mail-archive</a>,
+ <a href="http://news.gmane.org/gmane.comp.video.gimp.documentation/";>Gmane</a><br>
+ Old Archives:
+ <a href="http://www.mail-archive.com/gimp-docs%40lists.xcf.berkeley.edu/";>mail-archive</a>
+ </dd>
+
+</dl>
+## Code of Conduct
+
+Mailing lists are an important communication channel between contributors and users of GIMP. Therefore we
urge you to follow the following common etiquette rules. Failure to observe them, or instructions from the
moderators, may be grounds for reprimand, probation, or removal.
+
+* **Be considerate and respectful**. Every email in our most popular mailing lists, gimp-user@ and
gimp-developer@, will be read by ca. 1,000 subscribers and then aggregated to be seen by an even larger
audience. Please make sure that you add value to the discussion, avoid repetitive arguments, flamewars,
trolling, and personal attacks.
+* **Write in English**. While GIMP community is multinational, we need a _lingua franca_ for communication
which happens to be English. It's OK to have bad skills in English as long as you do your best.
+* **Do basic research**. Chances are that your questions, feature requests, or bug reports have already
been thoroughly discussed, and decisions have already been made. See the list of source for reference below.
+* **Stick to plain text**. Please don't send emails in HTML.
+* **Be specific**. When describing a bug you discovered, please always mention: operating system and its
version, architecture (32bit or 64bit), exact version of GIMP (use <tt>File->About</tt> for reference).
+* **Keep it short**. When replying long threads, please trim unnecessary content and write your replies
inline instead of "top posting".
+
+The code may change in the future, followed by a notification to subscribers.
+
+Please use these sources to check for information on the project, roadmap, feature requests, bug reports
etc.:
+
+* [Bug tracker](https://bugzilla.gnome.org/browse.cgi?product=GIMP). Useful for checking bug reports and
feature reqursts.
+* [Roadmap](http://wiki.gimp.org/index.php/Roadmap). We do not schedule releases, but we plan what things
we work on next.
+* [FAQ](http://www.gimp.org/docs/userfaq.html). There are some frequently asked questions we already
replied.
+* [Usability](http://gui.gimp.org). There's ongoing work to improve user experience of GIMP.
+* [Development](http://wiki.gimp.org/index.php/Main_Page). If you wish to contribute, please check the
wiki for basic information for developers.
+
+We also suggest checking archives of the mailing lists for existing discussions.
diff --git a/content/about/prehistory.md b/content/about/prehistory.md
index c1087ac..4886adb 100644
--- a/content/about/prehistory.md
+++ b/content/about/prehistory.md
@@ -1,7 +1,7 @@
Title: How It All Started...
Date: 2015-07-29T14:40:35-05:00
Modified: 2015-07-29T14:40:43-05:00
-Authors: Pat David
+Author: Pat David
Summary:
diff --git a/content/about/team.md b/content/about/team.md
new file mode 100644
index 0000000..98111d6
--- /dev/null
+++ b/content/about/team.md
@@ -0,0 +1,96 @@
+Title: The GIMP Team
+Date: 2015-08-12T15:47:05-05:00
+Author: Pat David
+url: team.html
+save_as: team.html
+status: hidden
+
+
+
+
+## GIMP Development Team
+
+* Michael Natterer (maintainer)
+* Sven Neumann (maintainer)
+* ... and dozens of others listed in a [separate page](/about/authors.html)
+
+## GIMP Web Team
+
+* Alexandre Prokoudine (maintainer)
+* Michael Schumacher (maintainer)
+* Akkana Peck
+* Alexia Death
+* Barak Itkin
+* Branko Collin
+* Carol Spears
+* Christian Hennecke
+* Clayton Walker
+* Dave Neary
+* Detlef Riekenberg
+* Guillermo S. Romero
+* Helvetix Victorinox (build tools)
+* Henrik Brix Andersen
+* Jakub Friedl
+* Jakub Steiner (2.4 release redesign)
+* Jehan
+* Jernej Simončič
+* Karine Delvare
+* Kevin Cozens
+* Manish Singh
+* Marco Ciampa
+* Martijn van Beers
+* Martijn Weisbeek
+* Martin Nordholts
+* Mat Caughron
+* Michael Muré
+* Michael Natterer
+* Mikael Magnusson
+* Mukund Sivaraman
+* Nathan C. Summers
+* Niklas Mattisson
+* Nils Philippsen
+* Pat David (HTML5 re-design)
+* Raphaël Quinet
+* Rebecca J. Walter
+* rockwlrs
+* Róman Joost
+* rubikcube
+* Shawn T. Amundson
+* Simon Budig
+* spiderworm
+* Sven Claußner
+* Sven Neumann
+* Ville Pätsi (2.0 release redesign)
+* William Skaggs
+
+## Tutorial Authors
+
+* Adrian Likins
+* Atte André Jensen
+* Carol Spears
+* Dave Neary
+* Dov Grobgeld
+* Eric Kidd
+* Eric R. Jeschke
+* Francisco Bustamante Hempe
+* Gautam N. Lad
+* Jakub Steiner
+* James Henstridge
+* Jens T. Lautenbach
+* John Beppu
+* Kevin Turner
+* Marco (LM) Lamberto
+* Mel Boyce
+* Pat David
+* Sam Jones
+* Seth Burgess
+* Simon Budig
+* Tuomas Kuosmanen
+* Ville Pätsi
+* Zach Beane
+
+## Previous Web Site
+
+* From 1997 to 2000, the webmaster's hat was worn by Jens T. Lautenbacher (jtl) and Adrian Likins
(Adrian). In addition, Zach Beane (Xach) maintained the GIMP News site.
+* From 2001 to 2004, the webmaster's hat was picked up by Raphaël Quinet. Sven Neumann contributed most
news items and updated some pages.
+
diff --git a/content/about/webmasters.md b/content/about/webmasters.md
new file mode 100644
index 0000000..b3c138a
--- /dev/null
+++ b/content/about/webmasters.md
@@ -0,0 +1,36 @@
+Title: Contacting the Webmasters
+Date: 2015-08-12T15:47:05-05:00
+Author: Pat David
+url: webmasters.html
+save_as: webmasters.html
+status: hidden
+
+
+
+This site is maintained by a team of volunteers who are constantly trying to improve it. We are all GIMP
users and some of us are also GIMP developers. If you have a question or a comment about GIMP, we will do our
best to help you. However, we get a _lot_ of mail and we may not be able to answer all queries. The best way
to get support is to post your questions and comments to one of the [mailing lists](/mail_lists.html) or [IRC
channels](/irc.html), or to the GIMP newsgroup (comp.graphics.apps.gimp).
+
+If you have a problem with GIMP and you think that you have found a bug or if you would like to suggest a
new feature, you can also take a look at our [bugs page](/bugs/). Your problem may have been reported or
solved already, so please [search and browse](https://bugzilla.gnome.org) for existing reports first.
+
+If you have the feeling that your report will require (longer) discussion - this is true for most feature
requests - then you should bring this topic up on the gimp-developer mailing list first.
+
+## Problems on this web site?
+
+If you detected a problem on one of our pages, such as a broken link or some incorrect information, please
use Bugzilla to [submit a bug report for this web
site](http://bugzilla.gnome.org/enter_bug.cgi?product=gimp-web&component=www.gimp.org&op_sys=All). Several
GIMP contributors are keeping an eye on the bug database regularly so this is probably the best way to tell
us about these problems and to get a timely response. See also [why we are using
Bugzilla](/bugs/why_bugzilla.html).
+
+You can also subscribe to the [gimp-web mailing list](/mail_lists.html) and then submit your improvement
proposals to the list.
+
+## Download mirrors
+
+You can also use Bugzilla to [notify
us](http://bugzilla.gnome.org/enter_bug.cgi?product=gimp-web&component=ftp+mirrors&op_sys=All) if a mirror of
download.gimp.org is gone or if a new one has recently been added. If you want to set up a new mirror, you
may want to use one of the existing rsync mirrors to update your server. Please include the country of your
server in the summary of the bug.
+
+Some hints on the server setup:
+
+* Please try to offer HTTP, FTP and rsync access
+* Check that all README files are present
+* Check that README, MIRRORS and \*.md5 are sent as text/plain
+
+The size of the data as seen on [http://download.gimp.org/pub/](http://download.gimp.org/pub/) is currently
around 4.1 GiB, with gimp and gtk subdirectories amounting to about 3.4 GiB. New releases are uploaded some
time before the announcement is made, so syncing every few days should be sufficient.
+
+## Last resort
+
+If you want to contact us by e-mail, then post to the [gimp-developer mailing list](/mail_lists.html).
diff --git a/content/tutorials/GIMP_Quickies/index.md b/content/tutorials/GIMP_Quickies/index.md
index 9721ba9..e5a31fb 100644
--- a/content/tutorials/GIMP_Quickies/index.md
+++ b/content/tutorials/GIMP_Quickies/index.md
@@ -50,7 +50,7 @@ To resize the image to new dimensions, we need only invoke the **Scale Image** d
This will then open the **Scale Image** dialog:
<figure>
-<img src='{attach}Scale-Image-Dialog.png' alt=''>
+<img src='{attach}Scale-Image-Dialog.png' alt='Scale Image'>
<figcaption>
The **Scale Image** dialog.
</figcaption>
@@ -63,7 +63,7 @@ You’ll also <span style="color: #0080FF;">notice a small chain</span> just to
For example, if you knew that you wanted your image to have a new width of 600px, you can enter that value
in the **Width** input, and the **Height** will automatically change to maintain the aspect ratio of the
image:
<figure>
-<img src='{attach}Scale-Image-Dialog-Scaled.png' alt=''>
+<img src='{attach}Scale-Image-Dialog-Scaled.png' alt='Scaled Image'>
<figcaption>
Changing the **Width** to 600px.
</figcaption>
@@ -76,7 +76,7 @@ Also notice I have shown a different option under **Quality** → Interpolation.
If you want to specify a new size using a different type of value (other than Pixel size), you can change
the type by clicking on the “**px**” spinner:
<figure>
-<img src='{attach}Scale-Image-Dialog-Value-Types.png' alt=''>
+<img src='{attach}Scale-Image-Dialog-Value-Types.png' alt='Value Types'>
<figcaption>
Changing input value types.
</figcaption>
@@ -103,7 +103,7 @@ You can also modify the filesize of an image when exporting it to a format like
Using the same Horsehead Nebula image from above, I have resized it to 200px wide (see above), and exported
it using different levels of JPEG compression:
<figure>
-<img src='{attach}JPG-Compression-Sample.png' alt=''>
+<img src='{attach}JPG-Compression-Sample.png' alt='JPG Compression comparison'>
<figcaption>
Comparison of different JPEG compression levels.
</figcaption>
@@ -118,7 +118,7 @@ When you’ve finished any image modifications you are doing, and are ready to e
This will invoke the **Export Image** dialog:
<figure>
-<img src='{attach}Export-Image-Dialog.png' alt=''>
+<img src='{attach}Export-Image-Dialog.png' alt='Export Image Dialog'>
<figcaption>
</figcaption>
@@ -131,7 +131,7 @@ You can also navigate to a new location on your computer through the **Places**
This will then bring up the **Export Image as JPEG** dialog, where you can change the quality of the export:
<figure>
-<img src='{attach}Export-Image-as-JPEG.png' alt=''>
+<img src='{attach}Export-Image-as-JPEG.png' alt='Export as JPG'>
<figcaption>
</figcaption>
@@ -150,7 +150,7 @@ There are numerous reasons you may want to crop an image. You may want to remove
In a nutshell, cropping is just an operation to trim the image down to a smaller region than what you
started with:
<figure>
-<img src='{attach}Crop-Example.png' alt=''>
+<img src='{attach}Crop-Example.png' alt='Cropping'>
<figcaption>
Original image (left), cropped image (right).
</figcaption>
@@ -159,7 +159,7 @@ Original image (left), cropped image (right).
The procedure to crop an image is straightforward. You can either get to <span style="color: #00FF00;">the
**Crop Tool**</span> through the tools palette:
<figure>
-<img src='{attach}Crop-Tool.png' alt=''>
+<img src='{attach}Crop-Tool.png' alt='Crop Tool'>
<figcaption>
Crop Tool on the Tools Palette.
</figcaption>
@@ -174,7 +174,7 @@ Or you can access the crop tool through the menus:
Now you can Left-Click anywhere on your image canvas, and drag the mouse to a new location to highlight an
initial selection to crop. You don’t have to worry about being exact at this point, as you will be able to
modify the final selection before actually cropping.
<figure>
-<img src='{attach}Crop-First.png' alt=''>
+<img src='{attach}Crop-First.png' alt='Crop First'>
<figcaption>
Initial pass with the Crop Tool.
Crop Tool options (left), cropping on the canvas (right).
@@ -195,7 +195,7 @@ See [the documentation](http://docs.gimp.org/2.8/en/gimp-tool-crop.html) for mor
Another way to crop an image is to make a selection first, using the **Rectangle Select Tool**:
<figure>
-<img src='{attach}Crop-Select-Tool.png' alt=''>
+<img src='{attach}Crop-Select-Tool.png' alt='Crop Select'>
<figcaption>
Rectangle Select Tool.
</figcaption>
@@ -222,7 +222,7 @@ There may also be a time that you’d like to flip an image as well. These comma
If you want to flip your image, the **Transform** menu offers two options, **Flip <span
style="text-decoration: underline;">H</span>orizontally**, or **Flip <span style="text-decoration:
underline;">V</span>ertically**. This operation will mirror your image along the specified axis. For example,
here are all of the flip operations shown in a single image:
<figure>
-<img src='{attach}Flip-Sample-Arrow.jpg' alt=''>
+<img src='{attach}Flip-Sample-Arrow.jpg' alt='Flipping'>
<figcaption>
All flips applied to base image (top left).
</figcaption>
@@ -235,7 +235,7 @@ Image rotation from the **Transform** menu is contrained to either 90° clockwis
Don’t mis-interpret this to mean that GIMP cannot do arbitrary rotations (any angle). Arbitrary rotations
are handled on a per-layer basis, while the image rotation described here is applicable to the entire image
at once.
<figure>
-<img src='{attach}Rotate-Sample.jpg' alt=''>
+<img src='{attach}Rotate-Sample.jpg' alt='Rotating Sample'>
<figcaption>
Original (top left), 90° clockwise (top right)
90° counter-clockwise (bottom left), 180° (bottom right)
diff --git a/plugins/page_hierarchy_gimp/page_hierarchy.py b/plugins/page_hierarchy_gimp/page_hierarchy.py
index 8e62c2a..fa5e6c4 100644
--- a/plugins/page_hierarchy_gimp/page_hierarchy.py
+++ b/plugins/page_hierarchy_gimp/page_hierarchy.py
@@ -35,46 +35,62 @@ def override_metadata(content_object):
if type(content_object) is not contents.Page:
return
page = content_object
- print( "####################" )
- print( "page.get_relative_source_path():" )
- print( page.get_relative_source_path() )
- print( "####################" )
- print( "$$$ METADATA $$$" )
- print( page.metadata )
- print( "$$$$$$$$$$$$$$$$" )
- print( "manual path [1]:" )
- print( os.path.split(page.get_relative_source_path())[1] )
+
+ #print( "####################" )
+ #print( "page.get_relative_source_path():" )
+ #print( page.get_relative_source_path() )
+ #print( "####################" )
+ #print( "$$$ METADATA $$$" )
+ #print( page.metadata )
+ #print( "$$$$$$$$$$$$$$$$" )
+
+ # IF page slug and filename is already set
+ # just return?
+ # Yes - just return - as long as both the slug AND filename
+ # are already set.
+
+ #if 'slug' in page.metadata and 'filename' in page.metadata:
+ if 'url' in page.metadata and 'save_as' in page.metadata:
+ #print( "page.metadata['url'] TEST: " + page.metadata['url'] )
+ #setattr(page, 'override_url', page.metadata['url'] )
+ #page.metadata['slug'] = ''
+ ##setattr(page, 'override_url', page.metadata['slug'] + '/' + page.metadata['filename'] )
+ return
+
+ #print( "manual path [1]:" )
+ #print( os.path.split(page.get_relative_source_path())[1] )
+
#path = get_path(page, page.settings)
path = os.path.split(page.get_relative_source_path())[0]
path = path.replace( os.path.sep, '/' )
- print( "override_metadata, path:" )
- print( path )
+
+ #print( "override_metadata, path:" )
+ #print( path )
def _override_value(page, key):
metadata = copy(page.metadata)
+
+ if 'slug' in metadata:
+ print( "metadata['slug']: " + metadata['slug'])
+
# We override the slug to include the path up to the filename
metadata['slug'] = os.path.join(path, page.slug)
- print( "_override_value, page.slug:" )
- print( page.slug )
- print( "_override_value, metadata['slug']:")
- print( metadata['slug'] )
+ print( "_override_value, page.slug: " + page.slug )
+ print( "_override_value, metadata['slug']: " + metadata['slug'])
metadata['filename'] = os.path.split(page.get_relative_source_path())[1]
metadata['filename'] = os.path.splitext( metadata['filename'])[0] + '.html'
- print( "metadata['filename']:" )
- print( metadata['filename'] )
+ print( "metadata['filename']: " + metadata['filename'] )
# PLD: this is my doing, sorry...
# ok, if path is empty, use page.slug
# if path is not empty, use path
# still need to test if lang works properly after this
if path:
- print( "got path" )
- print( path )
+ print( "got path" + path )
metadata['slug'] = path
else:
- print( "path empty!" )
- print( page.slug )
+ print( "path empty! " + page.slug )
metadata['slug'] = page.slug
if metadata['filename'] != 'index.html':
@@ -88,8 +104,7 @@ def override_metadata(content_object):
for key in ('save_as', 'url'):
if not hasattr(page, 'override_' + key):
setattr(page, 'override_' + key, _override_value(page, key))
- print( "## page.url ##" )
- print( page.url )
+ print( "key: " + key + " , page.url: " + page.url )
def set_relationships(generator):
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]
