Also I have implemented other options to this setting, such as the category, the date, the author, this kind of things.
Finally, I have setted the ARTICLE_PERMALINK_STRUCTURE option as null in pelican.conf.py sample file.
It seems the manpages ``pelican-themes.en.1`` and
``pelican-themes.fr.1`` were only used for the Debian packages.
Unforunately, ``dh_manpages`` seems to support installation of manpages
depending of their languages, so i've changed the settings and only
``pelican-themes.1`` is generated, this avoids having to rename the
manpages before packaging...
The documentation about making themes for Pelican is now generated in
the file ``pelican-theming.1``.
- The `simple` theme can now be extended with the syntax `{% extends "!simple/index.html" %}`
instead of `{% extends "simple/index.html" %}` to avoid conflicts with a `simple/` folder.
- If a template is missing in a theme, it will be replaced by the
corresponding template of the `simple` theme, so it's possible to
make a new theme with only two file: a `base.html` file that
extends the `base.html` file of the `simple` theme, and a CSS
stylesheet, for example.
Templates from the `simple` themes can be used in the other themes using
the `extends` keyword:
{% extends "simple/index.html" %}
This does not affect the behavior of Pelican:, so there is no need to modify
the existing themes.
This attempts to fix several issues:
1. The regexp that's supposed to catch href's doesn't work at all and even if it did match anything, it has too many parentheses for the following loop.
2. When a relative URL is replaced then it is done globally on the text and not per instance. So this `<a href="/foo/bar">/foo/bar</a>` will incorrectly get reformatted to `<a href="./static/foo/bar">./static/foo/bar</a>`.
3. Query parameter URLs are rewritten but shouldn't: `<a href="?foo=bar">` gets rewritten to `<a href="./static/?foo=bar">`
4. The joiner is producing too many slashes: `"." + "static" + "/files/image.png"` => `./static//files/image.png`.
