[ http://jira.codehaus.org/browse/DOXIA-24?page=comments#action_58030 ]
Jose Gonzalez Gomez commented on DOXIA-24:
--
Jason, I don't know if you're talking about a plugin when you say to rework
this as a module, but just in case, I submitted a while ago a docbook plugin to
the mojo project that does this (uses the Docbook stylesheets to generate its
output) and has a bit more of functionality (automatic creation of olink
database and resolution of links among documents using olink). This plugin
reads (by default) the stylesheets from the published Internet location but is
able to read them from an user provided location if specified by a parameter of
the plugin.
You may find it at http://mojo.codehaus.org/docbook-maven-plugin/
> [PATCH] better docbook support through the use of docbook xsl stylesheets
> -
>
> Key: DOXIA-24
> URL: http://jira.codehaus.org/browse/DOXIA-24
> Project: doxia
> Type: Improvement
> Reporter: Lars Trieloff
> Attachments: docbook-xsl-support.patch
>
>
> The current state of DocBook support in Doxia is still unsatisfactory. It is
> now able to handle the most important elements, but there is still an
> important problem left out: handling of xref-links. This type of links points
> to another docbook element and is expected to be replaced with a text
> describing the element by the processing system. For example an xref pointing
> to a chapter would be replaced with the text "Chapter N: 'Title of Chapter
> N'". Implementing this functionality using the XML Pull Parser currently used
> in Doxia is a massive effort because it leads to duplicating a lot of
> functionality already available in the DocBook XSL Stylesheets, the standard
> solution for processing DocBook XML and involves caching of more or less the
> whole DocBook document.
> My proposed solution is simple, elegant, but quite heavyweight: I use the
> DocBook XSL Stylesheets (which will be bundled with the doxia.jar) and
> transform the DocBook input document into a temporary XHTML document. The
> stylesheets are driven by a customization layer that turns off any
> unnecessary features like autogenerated tables of contents and navigation
> graphics.
> The temporary XHTML document is processed by the Doxia's XhtmlParser into a
> DoxiaModel. The DocBook XSL stylesheets and the XhtmlParser take care of
> maintaining the section nesting of the document, so that no important
> information will be lost.
> If the DocBook DTD changes, no Java programming is neccessary, all you need
> to do is updating the enclosed DocBook XSL stylesheets. The system is able to
> handle all of the DocBook elements and offers all advanced features of the
> DocBook XSL stylesheets like autogenerated texts and so on.
> There is only one major drawback: Parsing the DocBook stylesheets takes an
> huge amount of memory, but it is still possible to run maven with the default
> java heap space.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
