[gimp-web-devel/hugo: 1/7] some more translation
- From: Pat David <patdavid src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [gimp-web-devel/hugo: 1/7] some more translation
- Date: Sun, 24 Jul 2022 14:30:18 +0000 (UTC)
commit e9b84cda605561f69594d4194682104038c538c5
Author: robin-swift <robinswiftart gmail com>
Date: Sat Jul 23 20:14:05 2022 +0100
some more translation
content/homepage/CHANGELOG.md | 7 -
content/homepage/changelog.md | 16 +-
content/homepage/cvs.md | 13 +-
content/homepage/faq.md | 14 +-
content/homepage/git.md | 158 ++-----------
content/homepage/lists.md | 14 +-
content/homepage/plug-in-template.md | 15 +-
content/homepage/plug-ins.md | 26 +-
content/homepage/screenshots.md | 21 +-
content/homepage/standards.md | 15 +-
public/changelog.html | 2 +-
public/cvs.html | 2 +-
public/faq.html | 446 +++++++++++++++++++++++++++++++++++
public/git.html | 73 +++++-
public/homepage/plug-ins/index.html | 24 +-
public/index.html | 95 ++++----
public/index.xml | 105 +++++----
public/lists.html | 2 +-
public/plug-in-template.html | 2 +-
public/screenshots.html | 139 +++++++++++
public/sitemap.xml | 36 +--
public/standards.html | 2 +-
22 files changed, 867 insertions(+), 360 deletions(-)
---
diff --git a/content/homepage/changelog.md b/content/homepage/changelog.md
index 435b3cd..4426537 100644
--- a/content/homepage/changelog.md
+++ b/content/homepage/changelog.md
@@ -1,12 +1,10 @@
----
-title: "GIMP ChangeLog"
-date: 2022-07-20T19:04:06+01:00
-draft: true
-abbrev: "ChangeLog"
-description: "Keeping an eye on the development."
-type: new
-url: changelog.html
----
++++
+title = "GIMP ChangeLog"
+date = "2022-07-20"
+abbrev = "ChangeLog"
+description = "Keeping an eye on the development."
+url = "changelog.html"
++++
The [GIT repository](https://gitlab.gnome.org/GNOME/gimp/commits/master)
lists all changes in detail. The list below shows the latest
diff --git a/content/homepage/cvs.md b/content/homepage/cvs.md
index e87e879..fb34569 100644
--- a/content/homepage/cvs.md
+++ b/content/homepage/cvs.md
@@ -1,10 +1,9 @@
----
-title: "CVS"
-date: 2022-07-19T20:45:01+01:00
-draft: false
-description: "CVS migrated to Subversion."
-url: cvs.html
----
++++
+title = "CVS"
+date = "2022-07-19"
+description = "CVS migrated to Subversion."
+url = "cvs.html"
++++
GIMP doesn't use CVS any longer. The source code repository has been
migrated to [git](git).
diff --git a/content/homepage/faq.md b/content/homepage/faq.md
index 218e14c..5ea8f50 100644
--- a/content/homepage/faq.md
+++ b/content/homepage/faq.md
@@ -1,10 +1,10 @@
----
-title: "Frequently Asked Questions"
-date: 2022-07-20T19:04:11+01:00
-draft: true
-abbrev: "Developer FAQ"
-description: "New to GIMP Development?"
----
++++
+title = "Frequently Asked Questions"
+date = "2022-07-20"
+abbrev = "Developer FAQ"
+description = "New to GIMP Development?"
+url = "faq.html"
++++
Below you will find a collection of frequently asked questions
regarding development of the GIMP.
diff --git a/content/homepage/git.md b/content/homepage/git.md
index 19477cd..7a8834e 100644
--- a/content/homepage/git.md
+++ b/content/homepage/git.md
@@ -1,138 +1,30 @@
----
-title: "Git"
-date: 2022-07-20T19:04:57+01:00
-draft: true
-abbrev: "Git"
-description: "Living on the bleeding edge"
-url: git.html
----
++++
+title = "Git"
+date = "2022-07-20"
+abbrev = "Git"
+description = "Living on the bleeding edge"
+url = "git.html"
++++
-The GIMP source code lives in the <emphasis>gimp</emphasis>
-repository on the
-<ulink url="https://gitlab.gnome.org";>GNOME git server</ulink>.
+The GIMP source code lives in the `gimp` repository on the
+[GNOME git server](https://gitlab.gnome.org).
For more information on the GNOME git solution, go
-<ulink url="http://live.gnome.org/Git";>here</ulink>.
+[here](https://live.gnome.org/Git).
The GNOME git server hosts a couple of GIMP related repositories:
-<informaltable>
-<tgroup cols="2" align="left">
-<thead>
-<row>
-<entry>Module</entry>
-<entry>Description</entry>
-</row>
-</thead>
-<tbody>
-<row>
-<entry>
-<ulink url="https://gitlab.gnome.org/GNOME/gimp/";>babl</ulink>
-</entry>
-<entry>
-Pixel format conversion library
-</entry>
-</row>
-<row>
-<entry>
-<ulink url="https://gitlab.gnome.org/GNOME/gegl/";>gegl</ulink>
-</entry>
-<entry>
-Generic Graphical Library
-</entry>
-</row>
-<row>
-<entry>
-<ulink url="https://gitlab.gnome.org/GNOME/gimp/";>gimp</ulink>
-</entry>
-<entry>
-GIMP and the standard set of plug-ins
-</entry>
-</row>
-<row>
-<entry>
-<ulink url="https://gitlab.gnome.org/Archive/gimp-data-extras";>gimp-data-extras</ulink>
-</entry>
-<entry>
-GIMP Data files such as brushes, gradients, patterns and the like
-</entry>
-</row>
-<row>
-<entry>
-<ulink url="https://gitlab.gnome.org/GNOME/gimp-gap/";>gimp-gap</ulink>
-</entry>
-<entry>
-GIMP Animation Package, a set of plug-ins that provide
-video editing functionality
-</entry>
-</row>
-<row>
-<entry>
-<ulink url="https://gitlab.gnome.org/GNOME/gimp-help/";>gimp-help-2</ulink>
-</entry>
-<entry>
-GIMP User Manual
-</entry>
-</row>
-<row>
-<entry>
-<ulink url="https://gitlab.gnome.org/GNOME/gimp-perl/";>gimp-perl</ulink>
-</entry>
-<entry>
-GIMP Perl bindings and a bunch of nice gimp-perl scripts
-</entry>
-</row>
-<row>
-<entry>
-<ulink url="https://gitlab.gnome.org/Archive/gimp-plugin-template";>gimp-plugin-template</ulink>
-</entry>
-<entry>
-GIMP Plug-In Template, a starting ground for plug-in developers,
-currently in need of updating with regards to the use of GEGL
-</entry>
-</row>
-<row>
-<entry>
-<ulink url="https://gitlab.gnome.org/Archive/gimp-plugins-unstable";>gimp-plugins-unstable</ulink>
-</entry>
-<entry>
-GIMP plug-ins from the past, a collection of unstable and
-unmaintained plug-ins
-</entry>
-</row>
-<row>
-<entry>
-<ulink url="https://gitlab.gnome.org/GNOME/gimp-ruby";>gimp-ruby</ulink>
-</entry>
-<entry>
-GIMP Ruby-based scripting plug-in
-</entry>
-</row>
-<row>
-<entry>
-<ulink url="https://gitlab.gnome.org/GNOME/gimp-tiny-fu";>gimp-tiny-fu</ulink>
-</entry>
-<entry>
-GIMP Tiny-Fu, a drop-in replacement for Script-Fu
-</entry>
-</row>
-<row>
-<entry>
-<ulink url="https://gitlab.gnome.org/Infrastructure/gimp-web";>gimp-web</ulink>
-</entry>
-<entry>
-The GIMP web site, available at <ulink url="https://www.gimp.org";>www.gimp.org</ulink>
-</entry>
-</row>
-<row>
-<entry>
-<ulink url="https://gitlab.gnome.org/Infrastructure/gimp-web-devel";>gimp-web-devel</ulink>
-</entry>
-<entry>
-The source of the pages you are reading right now
-</entry>
-</row>
-</tbody>
-</tgroup>
-</informaltable>
-
-</webpage>
+| Module | Description |
+|---|---|
+| [babl](https://gitlab.gnome.org/GNOME/gimp) | Pixel format conversion library |
+| [gegl](https://gitlab.gnome.org/GNOME/gegl) | Generic Graphical Library |
+| [gimp](https://gitlab.gnome.org/GNOME/gimp) | GIMP and the standard set of plug-ins |
+| [gimp-data-extras](https://gitlab.gnome.org/Archive/gimp-data-extras) | GIMP Data files such as brushes,
gradients, patterns and the like |
+| [gimp-gap](https://gitlab.gnome.org/GNOME/gimp-gap) | GIMP Animation Package, a set of plug-ins that
provide video editing functionality |
+| [gimp-help](https://gitlab.gnome.org/GNOME/gimp-help) | GIMP User Manual |
+| [gimp-perl](https://gitlab.gnome.org/GNOME/gimp-perl) | GIMP Perl bindings and a bunch of nice gimp-perl
scripts |
+| [gimp-plugin-template](https://gitlab.gnome.org/Archive/gimp-plugin-template) | GIMP Plug-In Template, a
starting ground for plug-in developers, currently in need of updating with regards to the use of GEGL. |
+| [gimp-plugins-unstable](https://gitlab.gnome.org/Archive/gimp-plugins-unstable) | GIMP plug-ins from the
past, a collection of unstable and unmaintained plug-ins |
+| [gimp-ruby](https://gitlab.gnome.org/GNOME/gimp-ruby) | GIMP Ruby-based scripting plug-in |
+| [gimp-tiny-fu](https://gitlab.gnome.org/GNOME/gimp-tiny-fu) | GIMP Tiny-Fu, a drop-in replacement for
Script-Fu |
+| [gimp-web](https://gitlab.gnome.org/Infrastructure/gimp-web) | The GIMP web site, available at
[www.gimp.org](https://www.gimp.org) |
+| [gimp-web-devel](https://gitlab.gnome.org/Infrastructure/gimp-web-devel) | The source of the pages you are
reading right now |
diff --git a/content/homepage/lists.md b/content/homepage/lists.md
index a720c24..81f8687 100644
--- a/content/homepage/lists.md
+++ b/content/homepage/lists.md
@@ -1,11 +1,9 @@
----
-title: "Mailing Lists"
-description: "The finest spam in town"
-date: 2022-07-20T19:05:03+01:00
-draft: false
-type: new
-url: lists.html
----
++++
+title = "Mailing Lists"
+description = "The finest spam in town"
+date = "2022-07-20"
+url = "lists.html"
++++
There are several mailing-lists related to GIMP and
[www.gimp.org lists them all](https://www.gimp.org/mail_lists.html).
diff --git a/content/homepage/plug-in-template.md b/content/homepage/plug-in-template.md
index 3d9bd5b..d2afcc0 100644
--- a/content/homepage/plug-in-template.md
+++ b/content/homepage/plug-in-template.md
@@ -1,11 +1,10 @@
----
-title: "GIMP Plug-In Template"
-abbrev: "Plug-In Template"
-description: "Don't start from scratch"
-date: 2022-07-20T19:05:12+01:00
-draft: false
-url: plug-in-template.html
----
++++
+title = "GIMP Plug-In Template"
+abbrev = "Plug-In Template"
+description = "Don't start from scratch"
+date = "2022-07-20"
+url = "plug-in-template.html"
++++
The GIMP Plug-In Template is an empty GIMP Plug-In that does
nothing. It also has a GUI that allows to control how it achieves
diff --git a/content/homepage/plug-ins.md b/content/homepage/plug-ins.md
index 4747110..603a85d 100644
--- a/content/homepage/plug-ins.md
+++ b/content/homepage/plug-ins.md
@@ -1,19 +1,15 @@
----
-title: "Plug Ins"
-date: 2022-07-20T19:05:09+01:00
-draft: true
----
++++
+title = "Plug-In Development"
+description = "Writing GIMP plug-ins"
+date = "2022-07-20"
++++
----
-title: "Plug-In Development"
-description: "Writing GIMP plug-ins"
----
+* [Writing a GIMP Plug-In Part I](writing-a-plug-in/1)
+* [Writing a GIMP Plug-In Part II](writing-a-plug-in/2)
+* [Writing a GIMP Plug-In Part III](writing-a-plug-in/3)
-* [Writing a GIMP Plug-In Part I](writing-a-plug-in-1)
-* [Writing a GIMP Plug-In Part II](writing-a-plug-in-2)
-* [Writing a GIMP Plug-In Part III](writing-a-plug-in-3)
-
-Make good use of the <ulink url="api/2.0">GIMP 2.0 API reference</ulink>,
+Make good use of the [GIMP 2.0 API reference](api/2.0),
and you can also have a look at a talk about
-<ulink url="http://www.home.unix-ag.org/simon/gimp/guadec2002/gimp-plugin/html/";>GIMP plug-in
programming</ulink> that Simon gave at GUADEC in Sevilla.
+[GIMP plug-in programming](http://www.home.unix-ag.org/simon/gimp/guadec2002/gimp-plugin/html)
+that Simon gave at GUADEC in Sevilla.
diff --git a/content/homepage/screenshots.md b/content/homepage/screenshots.md
index 3801e0a..533fc74 100644
--- a/content/homepage/screenshots.md
+++ b/content/homepage/screenshots.md
@@ -1,22 +1,11 @@
----
++++
+title = "Screenshots"
+description = "What everyone is after..."
+url = "screenshots.html"
++++
----
-
-<?xml version='1.0'?>
-<!DOCTYPE webpage PUBLIC "-//Norman Walsh//DTD Website V2.4.1//EN"
- "dtd/website.dtd">
-
-<webpage id="screenshots" lang="en">
-
-<head>
-<title>Screenshots</title>
-<summary>What everyone is after...</summary>
-</head>
-
-<para>
Here are a few screenshots of the development version. More should
be added...
-</para>
<para role="screenshot">
<ulink url="screenshots/gimp-empty.png">
diff --git a/content/homepage/standards.md b/content/homepage/standards.md
index 3770d1d..530eebe 100644
--- a/content/homepage/standards.md
+++ b/content/homepage/standards.md
@@ -1,11 +1,10 @@
----
-title: "GIMP and Standards"
-date: 2022-07-20T19:05:19+01:00
-draft: true
-abbrev: "Standards"
-description: "Standards GIMP conforms to"
-url: standards.html
----
++++
+title = "GIMP and Standards"
+date = "2022-07-20"
+abbrev = "Standards"
+description = "Standards GIMP conforms to"
+url = "standards.html"
++++
GIMP is supposed to integrate well into your workflow. Thus is
needs to interoperate with other applications and your desktop.
diff --git a/public/changelog.html b/public/changelog.html
index f67f790..a7c125b 100644
--- a/public/changelog.html
+++ b/public/changelog.html
@@ -102,7 +102,7 @@
<main class="content container">
<div class="post">
<h1>GIMP ChangeLog</h1>
- <time datetime=2022-07-20T19:04:06+0100 class="post-date">Wed, Jul 20, 2022</time>
+ <time datetime=2022-07-20T00:00:00Z class="post-date">Wed, Jul 20, 2022</time>
<p>The <a href="https://gitlab.gnome.org/GNOME/gimp/commits/master";>GIT repository</a>
lists all changes in detail. The list below shows the latest
commits. It is generated from the RSS feed delivered by
diff --git a/public/cvs.html b/public/cvs.html
index dcbc9fb..bb865e8 100644
--- a/public/cvs.html
+++ b/public/cvs.html
@@ -102,7 +102,7 @@
<main class="content container">
<div class="post">
<h1>CVS</h1>
- <time datetime=2022-07-19T20:45:01+0100 class="post-date">Tue, Jul 19, 2022</time>
+ <time datetime=2022-07-19T00:00:00Z class="post-date">Tue, Jul 19, 2022</time>
<p>GIMP doesn’t use CVS any longer. The source code repository has been
migrated to <a href="git">git</a>.</p>
diff --git a/public/faq.html b/public/faq.html
new file mode 100644
index 0000000..f6b7561
--- /dev/null
+++ b/public/faq.html
@@ -0,0 +1,446 @@
+<!DOCTYPE html>
+<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en" lang="en">
+<head>
+ <link href="https://gmpg.org/xfn/11"; rel="profile">
+ <meta http-equiv="content-type" content="text/html; charset=utf-8">
+ <meta name="generator" content="Hugo 0.101.0" />
+
+
+ <meta name="viewport" content="width=device-width, initial-scale=1.0">
+
+ <title>Frequently Asked Questions · GIMP Developer Resources</title>
+ <meta name="description" content="New to GIMP Development?" />
+
+
+ <link type="text/css" rel="stylesheet" href="https://developer.gimp.org/css/print.css"; media="print">
+ <link type="text/css" rel="stylesheet" href="https://developer.gimp.org/css/poole.css";>
+ <link type="text/css" rel="stylesheet" href="https://developer.gimp.org/css/syntax.css";>
+ <link type="text/css" rel="stylesheet" href="https://developer.gimp.org/css/hyde.css";>
+ <link rel="stylesheet" href="https://fonts.googleapis.com/css?family=Abril+Fatface|PT+Sans:400,400i,700">
+
+
+
+ <link rel="apple-touch-icon-precomposed" sizes="144x144" href="/apple-touch-icon-144-precomposed.png">
+ <link rel="shortcut icon" href="/favicon.png">
+
+
+ </head>
+
+ <body class=" ">
+ <div class="titlebar">
+ <a href="index.html">
+ <img class="titlebarleft" src="images/developer-left.png" alt="" />
+ </a>
+ <img class="titlebarright" src="images/developer-right.png" alt="" />
+ </div>
+ <div class="webpage">
+ <a name="home" id="home"></a>
+ <table class="layout" summary="Navigation">
+ <tr>
+ <td class="menu">
+ <span class="toplevel">
+ <a href="git.html"> Git </a>
+ <br />
+ </span><span class="toplevel">
+ <a href="https://gitlab.gnome.org/browse/gimp/log/";> ChangeLog </a>
+ <br />
+ </span><span class="toplevel">
+ <a href="https://developer.gimp.org/NEWS";> News </a>
+ <br />
+ </span><span class="toplevel">
+ <a href="https://developer.gimp.org/HACKING";> Hacking </a>
+ <br />
+ </span><span class="toplevel">
+ <a href="bugs.html"> Gitlab </a>
+ <br />
+ </span><span class="toplevel">
+ <a href="lists.html"> Mailing Lists </a>
+ <br />
+ </span><span class="toplevel">
+ <a href="screenshots.html"> Screenshots </a>
+ <br />
+ </span><span class="toplevel">
+ <a href="plug-ins.html"> Plug-In Development </a>
+ <br />
+ </span><span class="toplevel">
+ <a href="api/2.0/index.html"> API Reference </a>
+ <br />
+ </span><span class="toplevel">
+ <a href="writing-api-plug-in/1.html"> Writing A Plug-In </a>
+ <br />
+ </span><span class="toplevel">
+ <a href="plug-in-template.html"> Plug-In Template </a>
+ <br />
+ </span><span class="toplevel">
+ <a href="gimpcon/index.html"> Conference </a>
+ <br />
+ </span><span class="toplevel">
+ <a href="gimpcon/2000/index.html"> GIMPCon 2000 </a>
+ <br />
+ </span><span class="toplevel">
+ <a href="gimpcon/2003/index.html"> GIMPCon 2003 </a>
+ <br />
+ </span><span class="toplevel">
+ <a href="gimpcon/2004/index.html"> GIMPCon 2004 </a>
+ <br />
+ </span><span class="toplevel">
+ <a href="gimpcon/2006/index.html"> GIMPCon 2006 </a>
+ <br />
+ </span><span class="toplevel">
+ <a href="faq.html"> Developer FAQ </a>
+ <br />
+ </span><span class="toplevel">
+ <a href="standards.html"> Standards </a>
+ <br />
+ </span><span class="toplevel">
+ <a href="about.html"> About this Site </a>
+ <br />
+ </span>
+</td>
+
+ <td class="main">
+ <main class="content container">
+ <div class="post">
+ <h1>Frequently Asked Questions</h1>
+ <time datetime=2022-07-20T00:00:00Z class="post-date">Wed, Jul 20, 2022</time>
+ <p>Below you will find a collection of frequently asked questions
+regarding development of the GIMP.</p>
+<h2 id="gimp-development">GIMP Development</h2>
+<h4 id="who-coordinates-gimp-development">Who coordinates GIMP development?</h4>
+<p>GIMP development is coordinated by Wilber the GIMP along
+with a loosely knit team of GIMP developers. The
+developers can be reached through the GIMP developer
+<!-- raw HTML omitted -->mailing list<!-- raw HTML omitted -->.</p>
+<h4 id="how-can-i-become-a-gimp-developer">How can I become a GIMP developer?</h4>
+<p>If you are a developer who wants to start contributing
+code to the GIMP, the best way to get to know its
+structure is by fixing bugs reported in Bugzilla. Pick a
+bug, perhaps ask the advice of another developer as to
+whether he/she thinks it will be an easy bug or not, and
+then fix it. Sounds easy, doesn’t it?</p>
+<p>After helping with a couple of bugs, people will start to
+recognize your immense talent, and you will be on your way
+to becoming a GIMP hacker. Any time you feel able, you
+can pick a smaller enhancement request and have a go at
+implementing it. It’s that easy.</p>
+<h4 id="where-can-i-discuss-gimp-development">Where can I discuss GIMP development?</h4>
+<p>There are several <!-- raw HTML omitted -->mailing
+lists<!-- raw HTML omitted --> associated with the GIMP project.
+Developments related issues can be brought up on the GIMP
+Developer mailing list.</p>
+<p>The GIMP has its own IRC channel on GIMPNet where most of
+the active developers hang out. Join us in #gimp on
+<!-- raw HTML omitted -->irc.gimp.org<!-- raw HTML omitted -->.</p>
+<p>Every once in a while the GIMP developers get together for
+a few days to throw a GIMP Developers Conference, also
+referred to as <!-- raw HTML omitted -->GIMPCon<!-- raw HTML omitted -->.</p>
+<h4 id="where-can-i-find-documentation-for-the-gimp-api">Where can I find documentation for the GIMP
API?</h4>
+<p>You can pass <!-- raw HTML omitted -->–enable-gtk-doc<!-- raw HTML omitted --> to the gimp
+<code>configure</code> script. This requires having
+<!-- raw HTML omitted -->gtk-doc<!-- raw HTML omitted -->
+installed. After running <!-- raw HTML omitted -->make<!-- raw HTML omitted --> you can
+find the GIMP API reference in the
+<code>devel-docs</code> directory.</p>
+<p>Pre-generated API documentation is included in the
+official GIMP tarballs.</p>
+<p>The API reference will normally be installed in
+<code>PREFIX/share/gtk-doc/html</code>. An on
+line version of the GIMP API reference can be found
+<!-- raw HTML omitted -->here<!-- raw HTML omitted -->.</p>
+<h4 id="how-do-i-make-a-stack-trace">How do I make a stack trace?</h4>
+<p>A stack trace is a list of function calls that leads to
+some point in the program. Debugging tools like <!-- raw HTML omitted -->gdb<!-- raw HTML omitted -->
+can get stack traces from crashed applications so that
+developers can figure out what went wrong. By including a
+stack trace with your bug report, it will be much easier
+for the developers to fix the reported problem.</p>
+<p>Information on how to make a stack trace can be found in
+the document <!-- raw HTML omitted -->Capturing
+Stack Traces<!-- raw HTML omitted -->.</p>
+<h4 id="what-is-the-best-way-to-submit-a-patch">What is the best way to submit a patch?</h4>
+<p>The best way to submit a patch is to open a bug report in
+Bugzilla and attach the patch there along with a
+description of what it does and why it should be applied.</p>
+<p>An introduction to how this is done can be found in the
+<!-- raw HTML omitted -->
+How To Create and Submit a Patch<!-- raw HTML omitted --> document.</p>
+<h4 id="what-is-the-preferred-coding-style-used-in-gimp">What is the preferred coding style used in
GIMP?</h4>
+<p>We encourage you to follow the GIMP coding style
+throughout the GIMP project. For the core components
+(application and libs) this coding style is enforced. The
+GIMP coding style is defined as follows:</p>
+<ul>
+<li>Function names are lowercase, words separated by underscores.</li>
+<li>Macros and enums are all uppercase, words separated by underscores</li>
+<li>Types are all words capitalized, no separators between words.</li>
+<li>All functions in header files need to be prototyped.</li>
+<li>Indentation rules are GNU coding style, in particular:
+<ul>
+<li>2 characters indentation level</li>
+<li>Do not use tabs (of course your editor can use tabs, but it should write them to file as 8 spaces
each).</li>
+<li>Opening brackets are on a new line and indented one level.</li>
+<li>Function header have the return type on one line, the name starting in the first column of the following
line. All parameters are prototyped and there’s a new line for each.</li>
+</ul>
+</li>
+</ul>
+<p>Try to make use of GLib’s object system as much as
+possible. Do not create wrappers around functions of
+parent classes. If you end up duplicating code, try to
+create a common parent class and implement the common
+methods there.</p>
+<p>Don’t include headers in headers except where unavoidable
+(e.g. for deriving objects). Opaque typedefs go to
+<code>app/base/base-types.h</code>, <code>app/core/core-types.h</code> etc. See
+<code>devel-docs/includes.txt</code> for a
+detailed description of the include policy.</p>
+<p>Don’t use the GTK wrappers around the GLib object and
+signal system.</p>
+<p>The above coding style, along with other useful
+information, is documented in the file <!-- raw HTML omitted -->HACKING<!-- raw HTML omitted -->.</p>
+<h4 id="how-can-i-configure-my-editor-for-this-coding-style">How can I configure my editor for this coding
style?</h4>
+<p>Your editor will not be able to do everything for you, but
+you can configure most editors so that they use two spaces
+for indentation, use spaces instead of tabs, etc.</p>
+<ul>
+<li>If you are using Emacs, you can insert the following settings into your <code>~/.emacs</code> file:</li>
+</ul>
+<pre tabindex="0"><code>;; Merge this into your custom-set-variables section if you already have one
+(custom-set-variables
+;; Syntax highlighting
+'(global-font-lock-mode t nil (font-lock))
+'(show-paren-mode t nil (paren))
+)
+;; use UTF-8 by default
+(prefer-coding-system 'mule-utf-8)
+;; use the GNU style for C files, spaces instead of tabs, highlight bad spaces
+(setq c-mode-common-hook '(lambda () (c-set-style "gnu")
+ (setq indent-tabs-mode nil)
+ (setq show-trailing-whitespace t))) ]]></programlisting>
+</code></pre><ul>
+<li>If you are using Vim, you can insert the following settings into your <code>~/.vimrc</code> file:</li>
+</ul>
+<pre tabindex="0"><code>syn on " syntax highlighting
+set expandtab " use spaces instead of tabs
+set shiftwidth=2 " default indentation is 2 spaces ]]></programlisting>
+</code></pre><ul>
+<li>If you are using another editor and you know how to configure it correctly, please tell us about it on
the GIMP developer <!-- raw HTML omitted -->mailing list<!-- raw HTML omitted --> so that we can update this
FAQ.</li>
+</ul>
+<h4 id="who-coordinates-the-gimp-translation-efforts">Who coordinates the GIMP translation efforts?</h4>
+<p>Any help with translations is appreciated. If you want to
+help, please get in contact with the people from the
+<!-- raw HTML omitted -->GNOME
+Translation Project<!-- raw HTML omitted --> who coordinate all translation
+efforts for projects hosted in the GNOME GIT repository.</p>
+<p>More information about GIMP and localisation can be found
+in the file <!-- raw HTML omitted -->README.i18n<!-- raw HTML omitted -->.</p>
+<h4 id="how-can-i-support-gimp-development">How can I support GIMP development?</h4>
+<p>By using GIMP and reporting any bugs you find to
+<!-- raw HTML omitted -->Bugzilla<!-- raw HTML omitted -->
+you’re helping a great deal. But there are other
+non-technical ways of supporting the development of The
+GIMP as well.</p>
+<p>GIMP has a web site, application documentation, lots of
+tutorials, and more. Unfortunately, as GIMP develops over
+time, much of this documentation needs to be re-written or
+freshened up, documentation needs to be added for new
+functionality, the web site needs to get a new lick of
+paint and so on.</p>
+<p>If you’re interested in helping out you should drop an
+e-mail to the GIMP developer <!-- raw HTML omitted -->mailing list<!-- raw HTML omitted --> offering your
+help.</p>
+<h2 id="plug-in-development">Plug-In Development</h2>
+<h4 id="is-there-a-plug-in-template-available">Is there a plug-in template available?</h4>
+<p>Yes. An official GIMP plug-in template is available in
+the <!-- raw HTML omitted -->gimp-plugin-template
+<!-- raw HTML omitted --> git module. Snapshots are available at <!-- raw HTML omitted -->ftp.gimp.org<!--
raw HTML omitted -->.</p>
+<h4 id="how-about-a-script-fu-template">How about a Script-Fu template?</h4>
+<p>Yes. Simon Budig has written a fill-in-the-blanks
+Script-Fu template which is available <!-- raw HTML omitted -->here<!-- raw HTML omitted -->.</p>
+<h4 id="how-do-i-get-my-plug-in-included-in-the-gimp">How do I get my plug-in included in the GIMP?</h4>
+<p>The best way to make your plug-in available to the World
+is to submit it to <!-- raw HTML omitted -->the GIMP Plug-In
+Registry<!-- raw HTML omitted -->.</p>
+<p>If you are certain that your plug-in will be useful to all
+GIMP users, then you can ask the GIMP developers to
+consider it for inclusion in future GIMP release. The
+best way to do that is to suggest it on the GIMP developer
+<!-- raw HTML omitted -->mailing list<!-- raw HTML omitted --> or to
+open an enhancement request in Bugzilla. However, we would
+like to limit the number of plug-ins included in the
+standard distribution and encourage all users to use the
+registry.</p>
+<h4 id="how-do-i-debug-a-gimp-plug-in">How do I debug a GIMP plug-in?</h4>
+<p>Eeek! The plug-in you’re working on has a bug in it! And
+the fix isn’t completely obvious, so you want to use
+debugger to see what is going on. But hmm, how does one
+start a plug-in under a debugger if GIMP is the one who is
+starting the plug-in…</p>
+<p>To address this issue, libgimp has some hooks controlled
+by the <code>GIMP_PLUGIN_DEBUG</code> environment
+variable. The idea is that you can attach a debugger to
+the pid of the plug-in you want to debug. The process is
+described in the file <!-- raw HTML omitted -->debug-plug-ins.txt<!-- raw HTML omitted -->.</p>
+<h4 id="will-the-plug-in-i-compiled-against-20-work-with-gimp-22-or-24">Will the plug-in I compiled against
2.0 work with GIMP 2.2 or 2.4?</h4>
+<p>The short answer is yes. GIMP 2.2 and 2.4 are binary
+compatible with plug-ins compiled for GIMP 2.0. The API is
+also backwards source compatible, so your plug-in should
+also compile cleanly against GIMP 2.2 and 2.4.</p>
+<p>If the plug-in you compiled for 2.0 does not work with 2.2
+or 2.4, there is one change which has been made which is
+not backwards compatible, since the old behaviour was
+considered incorrect. If you create a temporary drawable,
+using for example gimp_layer_new(), you are now required
+to add it to an image before calling any functions with
+the drawable as an argument.</p>
+<h2 id="git">GIT</h2>
+<h4 id="what-should-i-put-in-the-commit-message-when-doing-a-git-commit">What should I put in the commit
message when doing a git commit?</h4>
+<p>Please put a short explanation of the change on the first line.
+Then, after an empty line, you can describe the change in more
+detail using as many lines as you need. Try not to exceed 72
+colums.</p>
+<p>If the commit fixes a bug or part of a bug please use the
+bug number and description as the first line of the commit
+message. It’s most convenient to just copy the line from the
+Bugzilla bug page.</p>
+<h2 id="gegl">GEGL</h2>
+<h4 id="what-is-gegl">What is GEGL?</h4>
+<p>GEGL is the <!-- raw HTML omitted -->Generic
+Graphical Library<!-- raw HTML omitted -->. It is supposed to replace the
+handling of various image processing tasks in GIMP in
+a not too distant future (planned for GIMP 2.6).</p>
+<h4 id="what-will-gegl-be-able-to-do">What will GEGL be able to do?</h4>
+<p>GEGL will be a general image processing library. It uses
+a directed acyclic graph, a DAG, to represent image
+processing operations. In the DAG, images are edges, and
+operations are nodes. It takes advantage of this DAG to
+minimize regions which are processed, provide efficient
+caching of operations, and efficient redrawing when a
+parameter of the graph changes.</p>
+<p>GEGL should also be independent of the data type being
+processed and will be able to handle high bit depth
+images, ICC profiles and parallel processing of image
+tiles.</p>
+<h4 id="what-does-all-that-gibberish-mean-for-gimp">What does all that gibberish mean for GIMP?</h4>
+<p>Many highly requested features of the GIMP will be easier
+to do using GEGL. Layer effects, layer groups, and
+adjustment layers are quite easily represented (and
+efficiently calculated) using the DAG organization of GEGL.
+CMYK and high bit depth support will be easier because
+GEGL does not make the same assumptions about color spaces
+and data types that the GIMP does.</p>
+<p>The reusability of image processing operations means that
+plug-ins will be able to be designed in a much more modular
+way. The brush system will be able to become more
+flexible, especially when filter plug-ins are able to be
+used as procedural brush plug-ins.</p>
+<h2 id="bugzilla">Bugzilla</h2>
+<h4 id="what-is-bugzilla">What is Bugzilla?</h4>
+<p>The GIMP project uses <!-- raw HTML omitted -->GNOME Bugzilla<!-- raw HTML omitted --> for
+tracking of bug reports, enhancement requests etc.</p>
+<p>A beginners tutorial describing how to report a bug can be
+found in the <!-- raw HTML omitted -->
+How To Report GIMP Bugs<!-- raw HTML omitted --> document.</p>
+<p>An easy to use interface to reporting GIMP bugs can be
+found on <!-- raw HTML omitted -->bugs.gimp.org<!-- raw HTML omitted -->.</p>
+<h4 id="what-is-the-meaning-of-the-needinfo-status-code-inbugzilla">What is the meaning of the NEEDINFO
status code inBugzilla?</h4>
+<p>If the status of a bug is changed to NEEDINFO it means the
+GIMP developers need more information from the bug
+reporter in order to resolve the bug.</p>
+<p>More information about the meaning of the Bugzilla status
+field codes can be found in <!-- raw HTML omitted -->
+A Bug’s Life Cycle<!-- raw HTML omitted -->.</p>
+<h4 id="what-is-the-best-way-to-refer-to-a-bug-in-bugzilla">What is the best way to refer to a bug in
Bugzilla?</h4>
+<p>The best way to refer to a bug is <!-- raw HTML omitted -->bug
+#nnnnn<!-- raw HTML omitted -->, where nnnnn is the bug number. Using
+<!-- raw HTML omitted -->bug<!-- raw HTML omitted --> before the number allows Bugzilla to
+link to the corresponding bug report automatically. Using
+<!-- raw HTML omitted -->#<!-- raw HTML omitted --> before the number is optional for
+Bugzilla but makes it easier to locate references to bug
+reports in the ChangeLog or in e-mails.</p>
+<p>When referencing multiple bugs, it is better to be a bit
+redundant by writing <!-- raw HTML omitted -->bug #xxxxx, bug #yyyyy and bug
+#zzzzz<!-- raw HTML omitted --> instead of <!-- raw HTML omitted -->bugs #xxxxx, #yyyyy and
+#zzzzz<!-- raw HTML omitted --> in order to allow Bugzilla to link all bugs
+automatically.</p>
+<h4 id="what-is-the-proper-way-of-handling-duplicate-bug-reports">What is the proper way of handling
duplicate bug reports?</h4>
+<p>A bug report describing the same bug as a previous bug
+report should be marked as DUPLICATE of the older one.
+In some exceptional cases, it is possible to mark an old
+bug report as DUPLICATE of a newer one (e.g., when the
+newer bug report has a significantly better description
+than the older one).</p>
+<p>Another exception is when the same person submits the same
+bug report several times (same description): in this case,
+it is better to mark the additional copies of the bug
+report as INVALID in order to avoid inflating the
+statistics about the number of duplicates.</p>
+<h4 id="what-is-the-proper-way-of-marking-a-bug-as-resolved">What is the proper way of marking a bug as
RESOLVED?</h4>
+<p>When fixing a bug, always mention the bug number in the
+commit message. Once the changes are in git, paste the
+relevant part of the commit message (or all of it) in the
+comment field and mark the bug as RESOLVED FIXED.
+These cross-references help a lot when trying to find
+when a bug was fixed, its relations to other bugs, and
+potential regressions.</p>
+<p>A bug that is fixed in git or in an unstable release
+should be marked as RESOLVED FIXED. Optionally, the
+reporter or someone other than the one who fixed the bug
+can mark it as VERIFIED after some testing. When the fix
+is part of a stable release, it can be marked as CLOSED.</p>
+<p>This is explained further in <!-- raw HTML omitted -->A
+Bug’s Life Cycle<!-- raw HTML omitted --> except for the difference between
+stable and unstable releases.</p>
+<h2 id="miscellaneous">Miscellaneous</h2>
+<h4 id="where-can-i-learn-more-about-the-gobject-system-used-by-gimp">Where can I learn more about the
GObject system used by GIMP?</h4>
+<p>The
+<!-- raw HTML omitted -->GObject
+documentation<!-- raw HTML omitted --> has a
+nice <!-- raw HTML omitted -->tutorial<!-- raw HTML omitted --> that you might want to have a look at.</p>
+<h4 id="where-can-i-learn-more-about-color-spaces-etc">Where can I learn more about color spaces etc?</h4>
+<p>Charles Poynton has collected a set of <!-- raw HTML omitted -->Frequently
+Asked Questions about Color<!-- raw HTML omitted -->.</p>
+<h4 id="where-can-i-learn-more-about-image-manipulation-algorithms">Where can I learn more about image
manipulation algorithms?</h4>
+<p>A good source of information is the
+comp.graphics.algorithms list of <!-- raw HTML omitted -->Frequently
+Asked Questions<!-- raw HTML omitted -->.</p>
+<h4 id="is-there-a-gimp-user-faq-available">Is there a GIMP user FAQ available?</h4>
+<p>There is no user FAQ available at the moment. However
+there has been discussions about creating one. If you
+would like to help with this please drop a mail on the
+GIMP developer <!-- raw HTML omitted -->mailing
+list<!-- raw HTML omitted -->.</p>
+<h4 id="how-can-i-contribute-to-this-faq">How can I contribute to this FAQ?</h4>
+<p>If you would like to contribute to this FAQ, send an
+e-mail to the GIMP developer <a href="lists">mailing list</a> with the
+exact text you think should be included (both question and
+answer).</p>
+<p>With your help this FAQ will grow and become more useful.</p>
+
+</div>
+ </main>
+
+
+
+
+ <br />
+ </td>
+ </tr>
+ </table>
+ </div>
+ <div class="linkbar"><a href="http://developer.gimp.org/";>GIMP Developer Resources</a> | <a
href="http://www.gimp.org/";>GIMP Website</a> | <a href="http://www.gegl.org/";>GEGL Website</a></div>
+ <div>
+ <span class="footerleft">
+ <span class="copyright">Copyright © 2003-2022 The GIMP Development Team. </span>
+ </span>
+ <span class="footerright">
+ <a href="mailto:webmaster gimp org">webmaster gimp org</a>
+ </span>
+ </div>
+ <div style="clear: both; margin: 0; width: 100%; "></div>
+ <div class="validator">
+ <span style="position: absolute; left: 0; font-size: xx-small;">
+ <a href="http://validator.w3.org/check/referer";>Validate XHTML</a>
+ </span>
+ </div>
+ </body>
+</html>
diff --git a/public/git.html b/public/git.html
index 1f76997..a19f600 100644
--- a/public/git.html
+++ b/public/git.html
@@ -102,15 +102,74 @@
<main class="content container">
<div class="post">
<h1>Git</h1>
- <time datetime=2022-07-20T19:04:57+0100 class="post-date">Wed, Jul 20, 2022</time>
- <p>The GIMP source code lives in the <!-- raw HTML omitted -->gimp<!-- raw HTML omitted -->
-repository on the
-<!-- raw HTML omitted -->GNOME git server<!-- raw HTML omitted -->.
+ <time datetime=2022-07-20T00:00:00Z class="post-date">Wed, Jul 20, 2022</time>
+ <p>The GIMP source code lives in the <code>gimp</code> repository on the
+<a href="https://gitlab.gnome.org";>GNOME git server</a>.
For more information on the GNOME git solution, go
-<!-- raw HTML omitted -->here<!-- raw HTML omitted -->.</p>
+<a href="https://live.gnome.org/Git";>here</a>.</p>
<p>The GNOME git server hosts a couple of GIMP related repositories:</p>
-<!-- raw HTML omitted -->
-<!-- raw HTML omitted -->
+<table>
+<thead>
+<tr>
+<th>Module</th>
+<th>Description</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td><a href="https://gitlab.gnome.org/GNOME/gimp";>babl</a></td>
+<td>Pixel format conversion library</td>
+</tr>
+<tr>
+<td><a href="https://gitlab.gnome.org/GNOME/gegl";>gegl</a></td>
+<td>Generic Graphical Library</td>
+</tr>
+<tr>
+<td><a href="https://gitlab.gnome.org/GNOME/gimp";>gimp</a></td>
+<td>GIMP and the standard set of plug-ins</td>
+</tr>
+<tr>
+<td><a href="https://gitlab.gnome.org/Archive/gimp-data-extras";>gimp-data-extras</a></td>
+<td>GIMP Data files such as brushes, gradients, patterns and the like</td>
+</tr>
+<tr>
+<td><a href="https://gitlab.gnome.org/GNOME/gimp-gap";>gimp-gap</a></td>
+<td>GIMP Animation Package, a set of plug-ins that provide video editing functionality</td>
+</tr>
+<tr>
+<td><a href="https://gitlab.gnome.org/GNOME/gimp-help";>gimp-help</a></td>
+<td>GIMP User Manual</td>
+</tr>
+<tr>
+<td><a href="https://gitlab.gnome.org/GNOME/gimp-perl";>gimp-perl</a></td>
+<td>GIMP Perl bindings and a bunch of nice gimp-perl scripts</td>
+</tr>
+<tr>
+<td><a href="https://gitlab.gnome.org/Archive/gimp-plugin-template";>gimp-plugin-template</a></td>
+<td>GIMP Plug-In Template, a starting ground for plug-in developers, currently in need of updating with
regards to the use of GEGL.</td>
+</tr>
+<tr>
+<td><a href="https://gitlab.gnome.org/Archive/gimp-plugins-unstable";>gimp-plugins-unstable</a></td>
+<td>GIMP plug-ins from the past, a collection of unstable and unmaintained plug-ins</td>
+</tr>
+<tr>
+<td><a href="https://gitlab.gnome.org/GNOME/gimp-ruby";>gimp-ruby</a></td>
+<td>GIMP Ruby-based scripting plug-in</td>
+</tr>
+<tr>
+<td><a href="https://gitlab.gnome.org/GNOME/gimp-tiny-fu";>gimp-tiny-fu</a></td>
+<td>GIMP Tiny-Fu, a drop-in replacement for Script-Fu</td>
+</tr>
+<tr>
+<td><a href="https://gitlab.gnome.org/Infrastructure/gimp-web";>gimp-web</a></td>
+<td>The GIMP web site, available at <a href="https://www.gimp.org";>www.gimp.org</a></td>
+</tr>
+<tr>
+<td><a href="https://gitlab.gnome.org/Infrastructure/gimp-web-devel";>gimp-web-devel</a></td>
+<td>The source of the pages you are reading right now</td>
+</tr>
+</tbody>
+</table>
</div>
</main>
diff --git a/public/homepage/plug-ins/index.html b/public/homepage/plug-ins/index.html
index ec19c3a..de7a4e8 100644
--- a/public/homepage/plug-ins/index.html
+++ b/public/homepage/plug-ins/index.html
@@ -8,8 +8,8 @@
<meta name="viewport" content="width=device-width, initial-scale=1.0">
- <title>Plug Ins · GIMP Developer Resources</title>
- <meta name="description" content="" />
+ <title>Plug-In Development · GIMP Developer Resources</title>
+ <meta name="description" content="Writing GIMP plug-ins" />
<link type="text/css" rel="stylesheet" href="https://developer.gimp.org/css/print.css"; media="print">
@@ -101,19 +101,17 @@
<td class="main">
<main class="content container">
<div class="post">
- <h1>Plug Ins</h1>
- <time datetime=2022-07-20T19:05:09+0100 class="post-date">Wed, Jul 20, 2022</time>
- <hr>
-<h2 id="description-writing-gimp-plug-ins">title: “Plug-In Development”
-description: “Writing GIMP plug-ins”</h2>
-<ul>
-<li><a href="writing-a-plug-in-1">Writing a GIMP Plug-In Part I</a></li>
-<li><a href="writing-a-plug-in-2">Writing a GIMP Plug-In Part II</a></li>
-<li><a href="writing-a-plug-in-3">Writing a GIMP Plug-In Part III</a></li>
+ <h1>Plug-In Development</h1>
+ <time datetime=2022-07-20T00:00:00Z class="post-date">Wed, Jul 20, 2022</time>
+ <ul>
+<li><a href="writing-a-plug-in/1">Writing a GIMP Plug-In Part I</a></li>
+<li><a href="writing-a-plug-in/2">Writing a GIMP Plug-In Part II</a></li>
+<li><a href="writing-a-plug-in/3">Writing a GIMP Plug-In Part III</a></li>
</ul>
-<p>Make good use of the <!-- raw HTML omitted -->GIMP 2.0 API reference<!-- raw HTML omitted -->,
+<p>Make good use of the <a href="api/2.0">GIMP 2.0 API reference</a>,
and you can also have a look at a talk about
-<!-- raw HTML omitted -->GIMP plug-in programming<!-- raw HTML omitted --> that Simon gave at GUADEC in
Sevilla.</p>
+<a href="http://www.home.unix-ag.org/simon/gimp/guadec2002/gimp-plugin/html";>GIMP plug-in programming</a>
+that Simon gave at GUADEC in Sevilla.</p>
</div>
</main>
diff --git a/public/index.html b/public/index.html
index 089358e..1f1b9f4 100644
--- a/public/index.html
+++ b/public/index.html
@@ -8,81 +8,73 @@
<language>en</language>
<copyright>Copyright 2003-2022 The GIMP Development Team</copyright>
<lastBuildDate>Tue, 19 Jul 2022 00:00:00 +0000</lastBuildDate><atom:link
href="https://developer.gimp.org/index.html/"; rel="self" type="application/rss+xml" />
+ <item>
+ <title>Frequently Asked Questions</title>
+ <link>https://developer.gimp.org/faq.html</link>
+ <pubDate>Wed, 20 Jul 2022 00:00:00 +0000</pubDate>
+
+ <guid>https://developer.gimp.org/faq.html</guid>
+ <description>Below you will find a collection of frequently asked questions regarding development of
the GIMP.
+GIMP Development Who coordinates GIMP development? GIMP development is coordinated by Wilber the GIMP along
with a loosely knit team of GIMP developers. The developers can be reached through the GIMP developer mailing
list.
+How can I become a GIMP developer? If you are a developer who wants to start contributing code to the GIMP,
the best way to get to know its structure is by fixing bugs reported in Bugzilla.</description>
+ </item>
+
<item>
<title>GIMP and Standards</title>
<link>https://developer.gimp.org/standards.html</link>
- <pubDate>Wed, 20 Jul 2022 19:05:19 +0100</pubDate>
+ <pubDate>Wed, 20 Jul 2022 00:00:00 +0000</pubDate>
<guid>https://developer.gimp.org/standards.html</guid>
<description>GIMP is supposed to integrate well into your workflow. Thus is needs to interoperate with
other applications and your desktop. Standards are there to make this happen and so we try to follow
established (and sometimes even proposed) standards. Below you will find a list with links to specifications
that a GIMP developer may find useful.
&lt;varlistentry&gt; &lt;term&gt; &lt;ulink
url=&quot;http://www.w3.org/Graphics/GIF/spec-gif89a.txt&quot;&gt;Graphics Interchange
Format&lt;/ulink&gt; &lt;/term&gt; &lt;listitem&gt; Describes the GIF file format,
used in the GIF plug-in.</description>
</item>
+ <item>
+ <title>GIMP ChangeLog</title>
+ <link>https://developer.gimp.org/changelog.html</link>
+ <pubDate>Wed, 20 Jul 2022 00:00:00 +0000</pubDate>
+
+ <guid>https://developer.gimp.org/changelog.html</guid>
+ <description>The GIT repository lists all changes in detail. The list below shows the latest commits.
It is generated from the RSS feed delivered by the CIA.</description>
+ </item>
+
<item>
<title>GIMP Plug-In Template</title>
<link>https://developer.gimp.org/plug-in-template.html</link>
- <pubDate>Wed, 20 Jul 2022 19:05:12 +0100</pubDate>
+ <pubDate>Wed, 20 Jul 2022 00:00:00 +0000</pubDate>
<guid>https://developer.gimp.org/plug-in-template.html</guid>
<description>The GIMP Plug-In Template is an empty GIMP Plug-In that does nothing. It also has a GUI
that allows to control how it achieves this task. But best of all, it comes with a complete setup for
autoconf, automake, internationalisation and all these things you never wanted to know about.
Thanks to the GIMP Plug-In Template you don&rsquo;t need to worry about all these things. Just download
the tarball, add some magic image manipulation routines and voilà, your own GIMP plug-in.</description>
</item>
- <item>
- <title>Plug Ins</title>
- <link>https://developer.gimp.org/homepage/plug-ins/</link>
- <pubDate>Wed, 20 Jul 2022 19:05:09 +0100</pubDate>
-
- <guid>https://developer.gimp.org/homepage/plug-ins/</guid>
- <description>title: &ldquo;Plug-In Development&rdquo; description: &ldquo;Writing GIMP
plug-ins&rdquo; Writing a GIMP Plug-In Part I Writing a GIMP Plug-In Part II Writing a GIMP Plug-In Part
III Make good use of the GIMP 2.0 API reference, and you can also have a look at a talk about GIMP plug-in
programming that Simon gave at GUADEC in Sevilla.</description>
- </item>
-
- <item>
- <title>Mailing Lists</title>
- <link>https://developer.gimp.org/lists.html</link>
- <pubDate>Wed, 20 Jul 2022 19:05:03 +0100</pubDate>
-
- <guid>https://developer.gimp.org/lists.html</guid>
- <description>There are several mailing-lists related to GIMP and www.gimp.org lists them
all.</description>
- </item>
-
<item>
<title>Git</title>
<link>https://developer.gimp.org/git.html</link>
- <pubDate>Wed, 20 Jul 2022 19:04:57 +0100</pubDate>
+ <pubDate>Wed, 20 Jul 2022 00:00:00 +0000</pubDate>
<guid>https://developer.gimp.org/git.html</guid>
<description>The GIMP source code lives in the gimp repository on the GNOME git server. For more
information on the GNOME git solution, go here.
-The GNOME git server hosts a couple of GIMP related repositories:</description>
+The GNOME git server hosts a couple of GIMP related repositories:
+Module Description babl Pixel format conversion library gegl Generic Graphical Library gimp GIMP and the
standard set of plug-ins gimp-data-extras GIMP Data files such as brushes, gradients, patterns and the like
gimp-gap GIMP Animation Package, a set of plug-ins that provide video editing functionality gimp-help GIMP
User Manual gimp-perl GIMP Perl bindings and a bunch of nice gimp-perl scripts gimp-plugin-template GIMP
Plug-In Template, a starting ground for plug-in developers, currently in need of updating with regards to the
use of GEGL.</description>
</item>
<item>
- <title>Frequently Asked Questions</title>
- <link>https://developer.gimp.org/homepage/faq/</link>
- <pubDate>Wed, 20 Jul 2022 19:04:11 +0100</pubDate>
-
- <guid>https://developer.gimp.org/homepage/faq/</guid>
- <description>Below you will find a collection of frequently asked questions regarding development of
the GIMP.
-GIMP Development Who coordinates GIMP development? GIMP development is coordinated by Wilber the GIMP along
with a loosely knit team of GIMP developers. The developers can be reached through the GIMP developer mailing
list.
-How can I become a GIMP developer? If you are a developer who wants to start contributing code to the GIMP,
the best way to get to know its structure is by fixing bugs reported in Bugzilla.</description>
- </item>
-
- <item>
- <title>GIMP ChangeLog</title>
- <link>https://developer.gimp.org/changelog.html</link>
- <pubDate>Wed, 20 Jul 2022 19:04:06 +0100</pubDate>
+ <title>Mailing Lists</title>
+ <link>https://developer.gimp.org/lists.html</link>
+ <pubDate>Wed, 20 Jul 2022 00:00:00 +0000</pubDate>
- <guid>https://developer.gimp.org/changelog.html</guid>
- <description>The GIT repository lists all changes in detail. The list below shows the latest commits.
It is generated from the RSS feed delivered by the CIA.</description>
+ <guid>https://developer.gimp.org/lists.html</guid>
+ <description>There are several mailing-lists related to GIMP and www.gimp.org lists them
all.</description>
</item>
<item>
- <title>CVS</title>
- <link>https://developer.gimp.org/cvs.html</link>
- <pubDate>Tue, 19 Jul 2022 20:45:01 +0100</pubDate>
+ <title>Plug-In Development</title>
+ <link>https://developer.gimp.org/homepage/plug-ins/</link>
+ <pubDate>Wed, 20 Jul 2022 00:00:00 +0000</pubDate>
- <guid>https://developer.gimp.org/cvs.html</guid>
- <description>GIMP doesn&rsquo;t use CVS any longer. The source code repository has been migrated
to git.</description>
+ <guid>https://developer.gimp.org/homepage/plug-ins/</guid>
+ <description>Writing a GIMP Plug-In Part I Writing a GIMP Plug-In Part II Writing a GIMP Plug-In Part
III Make good use of the GIMP 2.0 API reference, and you can also have a look at a talk about GIMP plug-in
programming that Simon gave at GUADEC in Sevilla.</description>
</item>
<item>
@@ -107,12 +99,21 @@ Below is a list of links to get you started with Gitlab:</description>
</item>
<item>
- <title></title>
- <link>https://developer.gimp.org/homepage/screenshots/</link>
+ <title>CVS</title>
+ <link>https://developer.gimp.org/cvs.html</link>
+ <pubDate>Tue, 19 Jul 2022 00:00:00 +0000</pubDate>
+
+ <guid>https://developer.gimp.org/cvs.html</guid>
+ <description>GIMP doesn&rsquo;t use CVS any longer. The source code repository has been migrated
to git.</description>
+ </item>
+
+ <item>
+ <title>Screenshots</title>
+ <link>https://developer.gimp.org/screenshots.html</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
- <guid>https://developer.gimp.org/homepage/screenshots/</guid>
- <description> </description>
+ <guid>https://developer.gimp.org/screenshots.html</guid>
+ <description>Here are a few screenshots of the development version. More should be
added&hellip;</description>
</item>
</channel>
diff --git a/public/index.xml b/public/index.xml
index 489a5b9..68dc84c 100644
--- a/public/index.xml
+++ b/public/index.xml
@@ -8,81 +8,73 @@
<language>en</language>
<copyright>Copyright 2003-2022 The GIMP Development Team</copyright>
<lastBuildDate>Tue, 19 Jul 2022 00:00:00 +0000</lastBuildDate><atom:link
href="https://developer.gimp.org/index.xml"; rel="self" type="application/rss+xml" />
+ <item>
+ <title>Frequently Asked Questions</title>
+ <link>https://developer.gimp.org/faq.html</link>
+ <pubDate>Wed, 20 Jul 2022 00:00:00 +0000</pubDate>
+
+ <guid>https://developer.gimp.org/faq.html</guid>
+ <description>Below you will find a collection of frequently asked questions regarding development of
the GIMP.
+GIMP Development Who coordinates GIMP development? GIMP development is coordinated by Wilber the GIMP along
with a loosely knit team of GIMP developers. The developers can be reached through the GIMP developer mailing
list.
+How can I become a GIMP developer? If you are a developer who wants to start contributing code to the GIMP,
the best way to get to know its structure is by fixing bugs reported in Bugzilla.</description>
+ </item>
+
<item>
<title>GIMP and Standards</title>
<link>https://developer.gimp.org/standards.html</link>
- <pubDate>Wed, 20 Jul 2022 19:05:19 +0100</pubDate>
+ <pubDate>Wed, 20 Jul 2022 00:00:00 +0000</pubDate>
<guid>https://developer.gimp.org/standards.html</guid>
<description>GIMP is supposed to integrate well into your workflow. Thus is needs to interoperate with
other applications and your desktop. Standards are there to make this happen and so we try to follow
established (and sometimes even proposed) standards. Below you will find a list with links to specifications
that a GIMP developer may find useful.
&lt;varlistentry&gt; &lt;term&gt; &lt;ulink
url=&quot;http://www.w3.org/Graphics/GIF/spec-gif89a.txt&quot;&gt;Graphics Interchange
Format&lt;/ulink&gt; &lt;/term&gt; &lt;listitem&gt; Describes the GIF file format,
used in the GIF plug-in.</description>
</item>
+ <item>
+ <title>GIMP ChangeLog</title>
+ <link>https://developer.gimp.org/changelog.html</link>
+ <pubDate>Wed, 20 Jul 2022 00:00:00 +0000</pubDate>
+
+ <guid>https://developer.gimp.org/changelog.html</guid>
+ <description>The GIT repository lists all changes in detail. The list below shows the latest commits.
It is generated from the RSS feed delivered by the CIA.</description>
+ </item>
+
<item>
<title>GIMP Plug-In Template</title>
<link>https://developer.gimp.org/plug-in-template.html</link>
- <pubDate>Wed, 20 Jul 2022 19:05:12 +0100</pubDate>
+ <pubDate>Wed, 20 Jul 2022 00:00:00 +0000</pubDate>
<guid>https://developer.gimp.org/plug-in-template.html</guid>
<description>The GIMP Plug-In Template is an empty GIMP Plug-In that does nothing. It also has a GUI
that allows to control how it achieves this task. But best of all, it comes with a complete setup for
autoconf, automake, internationalisation and all these things you never wanted to know about.
Thanks to the GIMP Plug-In Template you don&rsquo;t need to worry about all these things. Just download
the tarball, add some magic image manipulation routines and voilà, your own GIMP plug-in.</description>
</item>
- <item>
- <title>Plug Ins</title>
- <link>https://developer.gimp.org/homepage/plug-ins/</link>
- <pubDate>Wed, 20 Jul 2022 19:05:09 +0100</pubDate>
-
- <guid>https://developer.gimp.org/homepage/plug-ins/</guid>
- <description>title: &ldquo;Plug-In Development&rdquo; description: &ldquo;Writing GIMP
plug-ins&rdquo; Writing a GIMP Plug-In Part I Writing a GIMP Plug-In Part II Writing a GIMP Plug-In Part
III Make good use of the GIMP 2.0 API reference, and you can also have a look at a talk about GIMP plug-in
programming that Simon gave at GUADEC in Sevilla.</description>
- </item>
-
- <item>
- <title>Mailing Lists</title>
- <link>https://developer.gimp.org/lists.html</link>
- <pubDate>Wed, 20 Jul 2022 19:05:03 +0100</pubDate>
-
- <guid>https://developer.gimp.org/lists.html</guid>
- <description>There are several mailing-lists related to GIMP and www.gimp.org lists them
all.</description>
- </item>
-
<item>
<title>Git</title>
<link>https://developer.gimp.org/git.html</link>
- <pubDate>Wed, 20 Jul 2022 19:04:57 +0100</pubDate>
+ <pubDate>Wed, 20 Jul 2022 00:00:00 +0000</pubDate>
<guid>https://developer.gimp.org/git.html</guid>
<description>The GIMP source code lives in the gimp repository on the GNOME git server. For more
information on the GNOME git solution, go here.
-The GNOME git server hosts a couple of GIMP related repositories:</description>
- </item>
-
- <item>
- <title>Frequently Asked Questions</title>
- <link>https://developer.gimp.org/homepage/faq/</link>
- <pubDate>Wed, 20 Jul 2022 19:04:11 +0100</pubDate>
-
- <guid>https://developer.gimp.org/homepage/faq/</guid>
- <description>Below you will find a collection of frequently asked questions regarding development of
the GIMP.
-GIMP Development Who coordinates GIMP development? GIMP development is coordinated by Wilber the GIMP along
with a loosely knit team of GIMP developers. The developers can be reached through the GIMP developer mailing
list.
-How can I become a GIMP developer? If you are a developer who wants to start contributing code to the GIMP,
the best way to get to know its structure is by fixing bugs reported in Bugzilla.</description>
+The GNOME git server hosts a couple of GIMP related repositories:
+Module Description babl Pixel format conversion library gegl Generic Graphical Library gimp GIMP and the
standard set of plug-ins gimp-data-extras GIMP Data files such as brushes, gradients, patterns and the like
gimp-gap GIMP Animation Package, a set of plug-ins that provide video editing functionality gimp-help GIMP
User Manual gimp-perl GIMP Perl bindings and a bunch of nice gimp-perl scripts gimp-plugin-template GIMP
Plug-In Template, a starting ground for plug-in developers, currently in need of updating with regards to the
use of GEGL.</description>
</item>
<item>
- <title>GIMP ChangeLog</title>
- <link>https://developer.gimp.org/changelog.html</link>
- <pubDate>Wed, 20 Jul 2022 19:04:06 +0100</pubDate>
+ <title>Mailing Lists</title>
+ <link>https://developer.gimp.org/lists.html</link>
+ <pubDate>Wed, 20 Jul 2022 00:00:00 +0000</pubDate>
- <guid>https://developer.gimp.org/changelog.html</guid>
- <description>The GIT repository lists all changes in detail. The list below shows the latest commits.
It is generated from the RSS feed delivered by the CIA.</description>
+ <guid>https://developer.gimp.org/lists.html</guid>
+ <description>There are several mailing-lists related to GIMP and www.gimp.org lists them
all.</description>
</item>
<item>
- <title>CVS</title>
- <link>https://developer.gimp.org/cvs.html</link>
- <pubDate>Tue, 19 Jul 2022 20:45:01 +0100</pubDate>
+ <title>Plug-In Development</title>
+ <link>https://developer.gimp.org/homepage/plug-ins/</link>
+ <pubDate>Wed, 20 Jul 2022 00:00:00 +0000</pubDate>
- <guid>https://developer.gimp.org/cvs.html</guid>
- <description>GIMP doesn&rsquo;t use CVS any longer. The source code repository has been migrated
to git.</description>
+ <guid>https://developer.gimp.org/homepage/plug-ins/</guid>
+ <description>Writing a GIMP Plug-In Part I Writing a GIMP Plug-In Part II Writing a GIMP Plug-In Part
III Make good use of the GIMP 2.0 API reference, and you can also have a look at a talk about GIMP plug-in
programming that Simon gave at GUADEC in Sevilla.</description>
</item>
<item>
@@ -106,6 +98,15 @@ On www.gimp.org you can find a document describing HOW TO Report GIMP Bugs. You
Below is a list of links to get you started with Gitlab:</description>
</item>
+ <item>
+ <title>CVS</title>
+ <link>https://developer.gimp.org/cvs.html</link>
+ <pubDate>Tue, 19 Jul 2022 00:00:00 +0000</pubDate>
+
+ <guid>https://developer.gimp.org/cvs.html</guid>
+ <description>GIMP doesn&rsquo;t use CVS any longer. The source code repository has been migrated
to git.</description>
+ </item>
+
<item>
<title></title>
<link>https://developer.gimp.org/gimpcon/2003/gimpcon2003-mins-1/</link>
@@ -142,15 +143,6 @@ Below is a list of links to get you started with Gitlab:</description>
<description>&lt;title&gt;Minutes of The GIMP Developers Conference 2003&lt;/title&gt;
&lt;titleabbrev&gt;Minutes&lt;/titleabbrev&gt; &lt;summary&gt;Minutes of the GIMPCon
2003 Meetings&lt;/summary&gt; &lt;para&gt; This meeting was held in the evening of August
7th, 2003. The main issues discussed were: &lt;itemizedlist&gt; &lt;listitem&gt;
&lt;olink targetdocent=&quot;gimpcon2003-mins-1&quot;
localinfo=&quot;foundation&quot;&gt;The GIMP foundation&lt;/olink&gt;
&lt;/listitem&gt; &lt;listitem&gt; &lt;olink
targetdocent=&quot;gimpcon2003-mins-1&quot; localinfo=&quot;manager&quot;&gt;Release
manager&lt;/olink&gt; &lt;/listitem&gt; &lt;listitem&gt; &lt;olink
targetdocent=&quot;gimpcon2003-mins-1&quot; localinfo=&quot;decisions&quot;&gt;Decision
making (or lack of it)&lt;/olink&gt; &a
mp;lt;/listitem&gt; &lt;listitem&gt; &lt;olink
targetdocent=&quot;gimpcon2003-mins-1&quot; localinfo=&quot;general&quot;&gt;General
stuff about CVS, Bugzilla&lt;/olink&gt; &lt;/listitem&gt; &lt;listitem&gt;
&lt;olink targetdocent=&quot;gimpcon2003-mins-1&quot;
localinfo=&quot;communication&quot;&gt;Communication&lt;/olink&gt;
&lt;/listitem&gt; &lt;/itemizedlist&gt; &lt;/para&gt; &lt;para&gt; The
minutes from this meeting can be found &lt;olink
targetdocent=&quot;gimpcon2003-mins-1&quot;&gt;here&lt;/olink&gt;.</description>
</item>
- <item>
- <title></title>
- <link>https://developer.gimp.org/homepage/screenshots/</link>
- <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-
- <guid>https://developer.gimp.org/homepage/screenshots/</guid>
- <description> </description>
- </item>
-
<item>
<title>How to write a GIMP plug-in</title>
<link>https://developer.gimp.org/writing-a-plug-in/1/</link>
@@ -185,5 +177,14 @@ That algorithm is very simple. Each pixel in our image is replaced by a mean val
In the &lt;olink targetdocent=&quot;writing-a-plug-in-2&quot;&gt;second
part&lt;/olink&gt;, I told you about manipulating image data by pixel or row. This time, I will go
farther and process data by tile, which will improve our plug-in performance. I will also update our
algorithm to take larger radius into account, and build a graphical interface to allow changing that
parameter. &lt;para&gt; Let's have a look at our simple algorithm: for each pixel, generate a
(2r+1)x(2r+1) neighbourhood and for each layer, replace the layer's pixel value with the average value in
the neighbourhood.</description>
</item>
+ <item>
+ <title>Screenshots</title>
+ <link>https://developer.gimp.org/screenshots.html</link>
+ <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+
+ <guid>https://developer.gimp.org/screenshots.html</guid>
+ <description>Here are a few screenshots of the development version. More should be
added&hellip;</description>
+ </item>
+
</channel>
</rss>
diff --git a/public/lists.html b/public/lists.html
index 5a7304f..baf3e7e 100644
--- a/public/lists.html
+++ b/public/lists.html
@@ -102,7 +102,7 @@
<main class="content container">
<div class="post">
<h1>Mailing Lists</h1>
- <time datetime=2022-07-20T19:05:03+0100 class="post-date">Wed, Jul 20, 2022</time>
+ <time datetime=2022-07-20T00:00:00Z class="post-date">Wed, Jul 20, 2022</time>
<p>There are several mailing-lists related to GIMP and
<a href="https://www.gimp.org/mail_lists.html";>www.gimp.org lists them all</a>.</p>
diff --git a/public/plug-in-template.html b/public/plug-in-template.html
index 0cc254a..1e2c68d 100644
--- a/public/plug-in-template.html
+++ b/public/plug-in-template.html
@@ -102,7 +102,7 @@
<main class="content container">
<div class="post">
<h1>GIMP Plug-In Template</h1>
- <time datetime=2022-07-20T19:05:12+0100 class="post-date">Wed, Jul 20, 2022</time>
+ <time datetime=2022-07-20T00:00:00Z class="post-date">Wed, Jul 20, 2022</time>
<p>The GIMP Plug-In Template is an empty GIMP Plug-In that does
nothing. It also has a GUI that allows to control how it achieves
this task. But best of all, it comes with a complete setup for
diff --git a/public/screenshots.html b/public/screenshots.html
new file mode 100644
index 0000000..2ec6662
--- /dev/null
+++ b/public/screenshots.html
@@ -0,0 +1,139 @@
+<!DOCTYPE html>
+<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en" lang="en">
+<head>
+ <link href="https://gmpg.org/xfn/11"; rel="profile">
+ <meta http-equiv="content-type" content="text/html; charset=utf-8">
+ <meta name="generator" content="Hugo 0.101.0" />
+
+
+ <meta name="viewport" content="width=device-width, initial-scale=1.0">
+
+ <title>Screenshots · GIMP Developer Resources</title>
+ <meta name="description" content="What everyone is after..." />
+
+
+ <link type="text/css" rel="stylesheet" href="https://developer.gimp.org/css/print.css"; media="print">
+ <link type="text/css" rel="stylesheet" href="https://developer.gimp.org/css/poole.css";>
+ <link type="text/css" rel="stylesheet" href="https://developer.gimp.org/css/syntax.css";>
+ <link type="text/css" rel="stylesheet" href="https://developer.gimp.org/css/hyde.css";>
+ <link rel="stylesheet" href="https://fonts.googleapis.com/css?family=Abril+Fatface|PT+Sans:400,400i,700">
+
+
+
+ <link rel="apple-touch-icon-precomposed" sizes="144x144" href="/apple-touch-icon-144-precomposed.png">
+ <link rel="shortcut icon" href="/favicon.png">
+
+
+ </head>
+
+ <body class=" ">
+ <div class="titlebar">
+ <a href="index.html">
+ <img class="titlebarleft" src="images/developer-left.png" alt="" />
+ </a>
+ <img class="titlebarright" src="images/developer-right.png" alt="" />
+ </div>
+ <div class="webpage">
+ <a name="home" id="home"></a>
+ <table class="layout" summary="Navigation">
+ <tr>
+ <td class="menu">
+ <span class="toplevel">
+ <a href="git.html"> Git </a>
+ <br />
+ </span><span class="toplevel">
+ <a href="https://gitlab.gnome.org/browse/gimp/log/";> ChangeLog </a>
+ <br />
+ </span><span class="toplevel">
+ <a href="https://developer.gimp.org/NEWS";> News </a>
+ <br />
+ </span><span class="toplevel">
+ <a href="https://developer.gimp.org/HACKING";> Hacking </a>
+ <br />
+ </span><span class="toplevel">
+ <a href="bugs.html"> Gitlab </a>
+ <br />
+ </span><span class="toplevel">
+ <a href="lists.html"> Mailing Lists </a>
+ <br />
+ </span><span class="toplevel">
+ <a href="screenshots.html"> Screenshots </a>
+ <br />
+ </span><span class="toplevel">
+ <a href="plug-ins.html"> Plug-In Development </a>
+ <br />
+ </span><span class="toplevel">
+ <a href="api/2.0/index.html"> API Reference </a>
+ <br />
+ </span><span class="toplevel">
+ <a href="writing-api-plug-in/1.html"> Writing A Plug-In </a>
+ <br />
+ </span><span class="toplevel">
+ <a href="plug-in-template.html"> Plug-In Template </a>
+ <br />
+ </span><span class="toplevel">
+ <a href="gimpcon/index.html"> Conference </a>
+ <br />
+ </span><span class="toplevel">
+ <a href="gimpcon/2000/index.html"> GIMPCon 2000 </a>
+ <br />
+ </span><span class="toplevel">
+ <a href="gimpcon/2003/index.html"> GIMPCon 2003 </a>
+ <br />
+ </span><span class="toplevel">
+ <a href="gimpcon/2004/index.html"> GIMPCon 2004 </a>
+ <br />
+ </span><span class="toplevel">
+ <a href="gimpcon/2006/index.html"> GIMPCon 2006 </a>
+ <br />
+ </span><span class="toplevel">
+ <a href="faq.html"> Developer FAQ </a>
+ <br />
+ </span><span class="toplevel">
+ <a href="standards.html"> Standards </a>
+ <br />
+ </span><span class="toplevel">
+ <a href="about.html"> About this Site </a>
+ <br />
+ </span>
+</td>
+
+ <td class="main">
+ <main class="content container">
+ <div class="post">
+ <h1>Screenshots</h1>
+ <time datetime=0001-01-01T00:00:00Z class="post-date">Mon, Jan 1, 0001</time>
+ <p>Here are a few screenshots of the development version. More should
+be added…</p>
+<!-- raw HTML omitted -->
+<!-- raw HTML omitted -->
+<!-- raw HTML omitted -->
+
+</div>
+ </main>
+
+
+
+
+ <br />
+ </td>
+ </tr>
+ </table>
+ </div>
+ <div class="linkbar"><a href="http://developer.gimp.org/";>GIMP Developer Resources</a> | <a
href="http://www.gimp.org/";>GIMP Website</a> | <a href="http://www.gegl.org/";>GEGL Website</a></div>
+ <div>
+ <span class="footerleft">
+ <span class="copyright">Copyright © 2003-2022 The GIMP Development Team. </span>
+ </span>
+ <span class="footerright">
+ <a href="mailto:webmaster gimp org">webmaster gimp org</a>
+ </span>
+ </div>
+ <div style="clear: both; margin: 0; width: 100%; "></div>
+ <div class="validator">
+ <span style="position: absolute; left: 0; font-size: xx-small;">
+ <a href="http://validator.w3.org/check/referer";>Validate XHTML</a>
+ </span>
+ </div>
+ </body>
+</html>
diff --git a/public/sitemap.xml b/public/sitemap.xml
index a82ec16..8e90ae3 100644
--- a/public/sitemap.xml
+++ b/public/sitemap.xml
@@ -2,35 +2,35 @@
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9";
xmlns:xhtml="http://www.w3.org/1999/xhtml";>
<url>
- <loc>https://developer.gimp.org/standards.html</loc>
- <lastmod>2022-07-20T19:05:19+01:00</lastmod>
+ <loc>https://developer.gimp.org/faq.html</loc>
+ <lastmod>2022-07-20T00:00:00+00:00</lastmod>
</url><url>
- <loc>https://developer.gimp.org/plug-in-template.html</loc>
- <lastmod>2022-07-20T19:05:12+01:00</lastmod>
+ <loc>https://developer.gimp.org/standards.html</loc>
+ <lastmod>2022-07-20T00:00:00+00:00</lastmod>
</url><url>
- <loc>https://developer.gimp.org/homepage/plug-ins/</loc>
- <lastmod>2022-07-20T19:05:09+01:00</lastmod>
+ <loc>https://developer.gimp.org/changelog.html</loc>
+ <lastmod>2022-07-20T00:00:00+00:00</lastmod>
</url><url>
- <loc>https://developer.gimp.org/lists.html</loc>
- <lastmod>2022-07-20T19:05:03+01:00</lastmod>
+ <loc>https://developer.gimp.org/plug-in-template.html</loc>
+ <lastmod>2022-07-20T00:00:00+00:00</lastmod>
</url><url>
<loc>https://developer.gimp.org/git.html</loc>
- <lastmod>2022-07-20T19:04:57+01:00</lastmod>
+ <lastmod>2022-07-20T00:00:00+00:00</lastmod>
</url><url>
- <loc>https://developer.gimp.org/homepage/faq/</loc>
- <lastmod>2022-07-20T19:04:11+01:00</lastmod>
- </url><url>
- <loc>https://developer.gimp.org/changelog.html</loc>
- <lastmod>2022-07-20T19:04:06+01:00</lastmod>
+ <loc>https://developer.gimp.org/lists.html</loc>
+ <lastmod>2022-07-20T00:00:00+00:00</lastmod>
</url><url>
- <loc>https://developer.gimp.org/cvs.html</loc>
- <lastmod>2022-07-19T20:45:01+01:00</lastmod>
+ <loc>https://developer.gimp.org/homepage/plug-ins/</loc>
+ <lastmod>2022-07-20T00:00:00+00:00</lastmod>
</url><url>
<loc>https://developer.gimp.org/about.html</loc>
<lastmod>2022-07-19T00:00:00+00:00</lastmod>
</url><url>
<loc>https://developer.gimp.org/bugs.html</loc>
<lastmod>2022-07-19T00:00:00+00:00</lastmod>
+ </url><url>
+ <loc>https://developer.gimp.org/cvs.html</loc>
+ <lastmod>2022-07-19T00:00:00+00:00</lastmod>
</url><url>
<loc>https://developer.gimp.org/</loc>
<lastmod>2022-07-19T00:00:00+00:00</lastmod>
@@ -47,8 +47,6 @@
<loc>https://developer.gimp.org/gimpcon/2003/gimpcon2003-mins/</loc>
</url><url>
<loc>https://developer.gimp.org/gimpcon/2006/</loc>
- </url><url>
- <loc>https://developer.gimp.org/homepage/screenshots/</loc>
</url><url>
<loc>https://developer.gimp.org/categories/</loc>
</url><url>
@@ -63,6 +61,8 @@
<loc>https://developer.gimp.org/writing-a-plug-in/2/</loc>
</url><url>
<loc>https://developer.gimp.org/writing-a-plug-in/3/</loc>
+ </url><url>
+ <loc>https://developer.gimp.org/screenshots.html</loc>
</url><url>
<loc>https://developer.gimp.org/tags/</loc>
</url><url>
diff --git a/public/standards.html b/public/standards.html
index acb2e35..ae71d01 100644
--- a/public/standards.html
+++ b/public/standards.html
@@ -102,7 +102,7 @@
<main class="content container">
<div class="post">
<h1>GIMP and Standards</h1>
- <time datetime=2022-07-20T19:05:19+0100 class="post-date">Wed, Jul 20, 2022</time>
+ <time datetime=2022-07-20T00:00:00Z class="post-date">Wed, Jul 20, 2022</time>
<p>GIMP is supposed to integrate well into your workflow. Thus is
needs to interoperate with other applications and your desktop.
Standards are there to make this happen and so we try to follow
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]
