Hi Jan,

2007/8/28, Jan Van Besien <[EMAIL PROTECTED]>:
> Hi all,
>
> I have a question about documentation generation. We have a lot of
> documentation in the apt format (and some in docbook), used to generate
> a maven site. A customer has the requirement to have this documentation
> in an offline format, PDF would be nice.

Site is already an offline doc :)

> I've browsed around a lot and experimented a bit, but I'm currently lost
> on what my best shot would be.
>
> 1) The maven-doxia-plugin and doxia's "book" support
> (http://maven.apache.org/doxia/book/) seem to do exactly what I want. At
> least in theory, because in practice it all looks unfinished. Generating

It is in the doxia sandbok, so for me, it is a normal way.

> latex documents is the only thing I could more or less get to work (that
> is with manual postprocessing to fix images and characters that should
> be escaped but were not).
>
> 2) I explored (a little) the idea to write all documentation in docbook
> (iso apt) and use something else (maven plugin or not) to generate pdf
> from the docbook files. The problem is that site generation from docbook
> files doesn't support docbook5 (yet?).

The doxia-module-docbook-simple seems to be able to parse some
docbook5 tags (I saw docbook5 ref in the parser), but the DocBookSink
uses only docbook4. Patches are welcome.

Other way, you could write pure docbook documents and use the Jboss plugin
(http://labs.jboss.com/maven-jdocbook-plugin )

> 3) I could simply print the generated html pages from the site
> generation to pdf documents.

It is the purpose of doxia-doc-renderer project. Actually, it uses
itext to produce single pdf or rtf docs. It can also generate one
document with a TOC (ie merge all apt, xdoc... files). You could write
a small mojo which calls docRenderer.render( ... );

Ok, I know, the rendering with iText is not really beautiful vs fop :(
but a good new is that Lukas has developed a fop module :) You could
find it in the doxia sandbox.

HTH.

Cheers,

Vincent

> What would be the best way to go? I think the first is conceptually the
> best. The second (using docbook 4.x) has to be investigated further, but
> it also implies rewriting most doc in docbook (iso apt).
>
> Other ideas are very welcome.
>
> Thanks in advance
> Jan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to