From: Petter Reinholdtsen Date: Fri, 16 Mar 2012 08:59:08 +0000 (+0000) Subject: Generated. X-Git-Url: https://pere.pagekite.me/gitweb/homepage.git/commitdiff_plain/48dabfa20b3c9ff14ff7aeba0b54536bebdaed3e?ds=sidebyside Generated. --- diff --git a/blog/Writing_and_translating_documentation_in_Debian_Edu.html b/blog/Writing_and_translating_documentation_in_Debian_Edu.html index cf96478dc8..faff2b057e 100644 --- a/blog/Writing_and_translating_documentation_in_Debian_Edu.html +++ b/blog/Writing_and_translating_documentation_in_Debian_Edu.html @@ -27,7 +27,8 @@ believe is a very efficient work flow.

    -
  1. The documentation is written in a moinmoin wiki (see for example +
  2. The documentation is written in a +moinmoin wiki (see for example the Squeeze release manual) with support for exporting the content as docbook XML.
    3. @@ -51,11 +52,11 @@ create PDF and HTML version of the original and translated documents.

This setup work very well, but have a few issues. The biggest -issue is that the docbook support in moinmoin is not actively -maintained. This make it hard to upgrade moinmoin. The docbook -support is also buggy, and our build system contain lots of -workarounds to make sure the generated docbook is usable despite these -bugs.

+issue is that the docbook support +we use in moinmoin is not actively maintained. This make it hard +to upgrade moinmoin. The docbook support is also buggy, and our build +system contain lots of workarounds to make sure the generated docbook +is usable despite these bugs.

If you want to have a look at our setup, it is all there in the debian-edu-doc diff --git a/blog/archive/2012/03/03.rss b/blog/archive/2012/03/03.rss index af4cf67123..9b3a2f0a11 100644 --- a/blog/archive/2012/03/03.rss +++ b/blog/archive/2012/03/03.rss @@ -386,7 +386,8 @@ believe is a very efficient work flow.</p> <ol> -<li>The documentation is written in a moinmoin wiki (see for example +<li>The documentation is written in a +<a href="http://moinmo.in">moinmoin wiki</a> (see for example <a href="http://wiki.debian.org/DebianEdu/Documentation/Squeeze">the Squeeze release manual</a>) with support for exporting the content as docbook XML.</li> @@ -410,11 +411,11 @@ create PDF and HTML version of the original and translated documents.</li> </ol> <p>This setup work very well, but have a few issues. The biggest -issue is that the docbook support in moinmoin is not actively -maintained. This make it hard to upgrade moinmoin. The docbook -support is also buggy, and our build system contain lots of -workarounds to make sure the generated docbook is usable despite these -bugs.</p> +issue is that <a href="http://moinmo.in/DocBook">the docbook support +we use in moinmoin</a> is not actively maintained. This make it hard +to upgrade moinmoin. The docbook support is also buggy, and our build +system contain lots of workarounds to make sure the generated docbook +is usable despite these bugs.</p> <p>If you want to have a look at our setup, it is all there in the <a href="http://packages.qa.debian.org/debian-edu-doc">debian-edu-doc diff --git a/blog/archive/2012/03/index.html b/blog/archive/2012/03/index.html index 7f08edc40a..e3da581c1f 100644 --- a/blog/archive/2012/03/index.html +++ b/blog/archive/2012/03/index.html @@ -512,7 +512,8 @@ believe is a very efficient work flow.

    -
  1. The documentation is written in a moinmoin wiki (see for example +
  2. The documentation is written in a +moinmoin wiki (see for example the Squeeze release manual) with support for exporting the content as docbook XML.
    3. @@ -536,11 +537,11 @@ create PDF and HTML version of the original and translated documents.

This setup work very well, but have a few issues. The biggest -issue is that the docbook support in moinmoin is not actively -maintained. This make it hard to upgrade moinmoin. The docbook -support is also buggy, and our build system contain lots of -workarounds to make sure the generated docbook is usable despite these -bugs.

+issue is that the docbook support +we use in moinmoin is not actively maintained. This make it hard +to upgrade moinmoin. The docbook support is also buggy, and our build +system contain lots of workarounds to make sure the generated docbook +is usable despite these bugs.

If you want to have a look at our setup, it is all there in the debian-edu-doc diff --git a/blog/index.html b/blog/index.html index 84eebf2047..17bfa09f29 100644 --- a/blog/index.html +++ b/blog/index.html @@ -29,7 +29,8 @@ believe is a very efficient work flow.

    -
  1. The documentation is written in a moinmoin wiki (see for example +
  2. The documentation is written in a +moinmoin wiki (see for example the Squeeze release manual) with support for exporting the content as docbook XML.
    3. @@ -53,11 +54,11 @@ create PDF and HTML version of the original and translated documents.

This setup work very well, but have a few issues. The biggest -issue is that the docbook support in moinmoin is not actively -maintained. This make it hard to upgrade moinmoin. The docbook -support is also buggy, and our build system contain lots of -workarounds to make sure the generated docbook is usable despite these -bugs.

+issue is that the docbook support +we use in moinmoin is not actively maintained. This make it hard +to upgrade moinmoin. The docbook support is also buggy, and our build +system contain lots of workarounds to make sure the generated docbook +is usable despite these bugs.

If you want to have a look at our setup, it is all there in the debian-edu-doc diff --git a/blog/index.rss b/blog/index.rss index dcd4a1d910..6afb23c5d5 100644 --- a/blog/index.rss +++ b/blog/index.rss @@ -18,7 +18,8 @@ believe is a very efficient work flow.</p> <ol> -<li>The documentation is written in a moinmoin wiki (see for example +<li>The documentation is written in a +<a href="http://moinmo.in">moinmoin wiki</a> (see for example <a href="http://wiki.debian.org/DebianEdu/Documentation/Squeeze">the Squeeze release manual</a>) with support for exporting the content as docbook XML.</li> @@ -42,11 +43,11 @@ create PDF and HTML version of the original and translated documents.</li> </ol> <p>This setup work very well, but have a few issues. The biggest -issue is that the docbook support in moinmoin is not actively -maintained. This make it hard to upgrade moinmoin. The docbook -support is also buggy, and our build system contain lots of -workarounds to make sure the generated docbook is usable despite these -bugs.</p> +issue is that <a href="http://moinmo.in/DocBook">the docbook support +we use in moinmoin</a> is not actively maintained. This make it hard +to upgrade moinmoin. The docbook support is also buggy, and our build +system contain lots of workarounds to make sure the generated docbook +is usable despite these bugs.</p> <p>If you want to have a look at our setup, it is all there in the <a href="http://packages.qa.debian.org/debian-edu-doc">debian-edu-doc diff --git a/blog/tags/debian edu/debian edu.rss b/blog/tags/debian edu/debian edu.rss index 09a6f23fef..f10e147e37 100644 --- a/blog/tags/debian edu/debian edu.rss +++ b/blog/tags/debian edu/debian edu.rss @@ -6473,7 +6473,8 @@ believe is a very efficient work flow.</p> <ol> -<li>The documentation is written in a moinmoin wiki (see for example +<li>The documentation is written in a +<a href="http://moinmo.in">moinmoin wiki</a> (see for example <a href="http://wiki.debian.org/DebianEdu/Documentation/Squeeze">the Squeeze release manual</a>) with support for exporting the content as docbook XML.</li> @@ -6497,11 +6498,11 @@ create PDF and HTML version of the original and translated documents.</li> </ol> <p>This setup work very well, but have a few issues. The biggest -issue is that the docbook support in moinmoin is not actively -maintained. This make it hard to upgrade moinmoin. The docbook -support is also buggy, and our build system contain lots of -workarounds to make sure the generated docbook is usable despite these -bugs.</p> +issue is that <a href="http://moinmo.in/DocBook">the docbook support +we use in moinmoin</a> is not actively maintained. This make it hard +to upgrade moinmoin. The docbook support is also buggy, and our build +system contain lots of workarounds to make sure the generated docbook +is usable despite these bugs.</p> <p>If you want to have a look at our setup, it is all there in the <a href="http://packages.qa.debian.org/debian-edu-doc">debian-edu-doc diff --git a/blog/tags/debian edu/index.html b/blog/tags/debian edu/index.html index 346199c628..f7a1733d86 100644 --- a/blog/tags/debian edu/index.html +++ b/blog/tags/debian edu/index.html @@ -7534,7 +7534,8 @@ believe is a very efficient work flow.

    -
  1. The documentation is written in a moinmoin wiki (see for example +
  2. The documentation is written in a +moinmoin wiki (see for example the Squeeze release manual) with support for exporting the content as docbook XML.
    3. @@ -7558,11 +7559,11 @@ create PDF and HTML version of the original and translated documents.

This setup work very well, but have a few issues. The biggest -issue is that the docbook support in moinmoin is not actively -maintained. This make it hard to upgrade moinmoin. The docbook -support is also buggy, and our build system contain lots of -workarounds to make sure the generated docbook is usable despite these -bugs.

+issue is that the docbook support +we use in moinmoin is not actively maintained. This make it hard +to upgrade moinmoin. The docbook support is also buggy, and our build +system contain lots of workarounds to make sure the generated docbook +is usable despite these bugs.

If you want to have a look at our setup, it is all there in the debian-edu-doc diff --git a/blog/tags/english/english.rss b/blog/tags/english/english.rss index 051b259c26..815db584f9 100644 --- a/blog/tags/english/english.rss +++ b/blog/tags/english/english.rss @@ -7361,7 +7361,8 @@ believe is a very efficient work flow.</p> <ol> -<li>The documentation is written in a moinmoin wiki (see for example +<li>The documentation is written in a +<a href="http://moinmo.in">moinmoin wiki</a> (see for example <a href="http://wiki.debian.org/DebianEdu/Documentation/Squeeze">the Squeeze release manual</a>) with support for exporting the content as docbook XML.</li> @@ -7385,11 +7386,11 @@ create PDF and HTML version of the original and translated documents.</li> </ol> <p>This setup work very well, but have a few issues. The biggest -issue is that the docbook support in moinmoin is not actively -maintained. This make it hard to upgrade moinmoin. The docbook -support is also buggy, and our build system contain lots of -workarounds to make sure the generated docbook is usable despite these -bugs.</p> +issue is that <a href="http://moinmo.in/DocBook">the docbook support +we use in moinmoin</a> is not actively maintained. This make it hard +to upgrade moinmoin. The docbook support is also buggy, and our build +system contain lots of workarounds to make sure the generated docbook +is usable despite these bugs.</p> <p>If you want to have a look at our setup, it is all there in the <a href="http://packages.qa.debian.org/debian-edu-doc">debian-edu-doc diff --git a/blog/tags/english/index.html b/blog/tags/english/index.html index b51e01dd0f..7deba794d5 100644 --- a/blog/tags/english/index.html +++ b/blog/tags/english/index.html @@ -8746,7 +8746,8 @@ believe is a very efficient work flow.

    -
  1. The documentation is written in a moinmoin wiki (see for example +
  2. The documentation is written in a +moinmoin wiki (see for example the Squeeze release manual) with support for exporting the content as docbook XML.
    3. @@ -8770,11 +8771,11 @@ create PDF and HTML version of the original and translated documents.

This setup work very well, but have a few issues. The biggest -issue is that the docbook support in moinmoin is not actively -maintained. This make it hard to upgrade moinmoin. The docbook -support is also buggy, and our build system contain lots of -workarounds to make sure the generated docbook is usable despite these -bugs.

+issue is that the docbook support +we use in moinmoin is not actively maintained. This make it hard +to upgrade moinmoin. The docbook support is also buggy, and our build +system contain lots of workarounds to make sure the generated docbook +is usable despite these bugs.

If you want to have a look at our setup, it is all there in the debian-edu-doc