From: Richard Ash <richard@au...> - 2008-11-16 21:03:03
We need to resolve the issue with exporting the manual for 1.4.0 from
mediawiki to other formats. For anyone who doesn't know, Dominic wrote a
mediawiki -> xml -> pdf toolchain for Audacity, which is currently
broken for reasons we don't really understand, probably because it can't
absorb some bits of mediawiki syntax. It's written in python, and we
don't have the resources to fix it in the short term.
The problem of wanting to export mediawiki to other formats is not
unique to Audacity, however. It essentially affects a large number of
mediawiki using organisations. As a result there is now some fairly
serious effort being expended towards a "proper" solution, in the form
of the Collection extension.
This offers a way to specify a set of wiki pages which are to be
exported, then render them to a number of formats, including PDF and
ODF. xhtml export is supposed to be on the way (it's in the back-end
libraries, although it may not work), from which simplified html export
could be adapted.
I've been using this on a project at work, and in general it seems to be
a solid project, with a small but responsive team developing it. This
means that in general the burden of making it work with the content we
have on the manual wiki doesn't fall on us:
1) because the majority of things we do will have already been done
elsewhere and fixed before we hit them.
2) we can report bugs out to someone else when we do find them.
The funding for the development is coming from a print-on-demand outfit
in Germany who see themselves getting a return from people ordering
print copies of wiki contents. So there is a well maintained path to be
able to print hard copies of the manual if we wish to (we would have to
negotiate with them if we wished to make any income from such a scheme).
This is not an integral part of the set-up, especially if we run our own
rendering server rather than using theirs.
Anyway, my point is that I think we should install the extension on the
manual wiki and see where we get to, and what works/doesn't. This might
provide a low-effort route to unblock one of the P1 issues to release.