Generated.

[homepage.git] / blog / Writing_and_translating_documentation_in_Debian_Edu.html

diff --git a/blog/Writing_and_translating_documentation_in_Debian_Edu.html b/blog/Writing_and_translating_documentation_in_Debian_Edu.html
index cf96478dc8df7fc53daa4b4935f80e46337cd73f..0859309fd226c0571c6d07f0bd9967d099e38b0e 100644 (file)
--- 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.</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>
@@ -51,11 +52,10 @@ 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.  The docbook
+support is also buggy, and our build system contain 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