Details
-
Type:
New Feature
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: docbook
-
Labels:None
-
Complexity:Novice
Description
I've added preliminary support for the following:
1. Image support: Docbook lets you add media files to the Docbook source files using the media object tag. In the case of images, this means that a image can be included in the Docbook file, and the stylesheets will turn this into an IMG tag. In order for this to work the image file must be present in the target directory tree where the xhtml files are being generated. I've added a process that copies every file in the docbook source directory that doesn't have an XML extension to the target directory, so images included with a relative path will be perfectly viewable in the generated xhtml.
2. Docbook stylesheets are parametrizable using a huge amount of parameters (for example, here you have the HTML parameter reference: http://docbook.sourceforge.net/release/xsl/current/doc/html/). Creating a plugin parameter for every stylesheet parameter makes no sense, as this would be a huge amount of work and shouyld be continously mantained. I've added support for specifying a parameters file, where all these parameters may be specified. The plugin parses this file and passes all the parameters found to the Docbook stylesheets.
Concerning the parametrization support: I would propose making it possible to specify a customization layer stylesheet for each transformation format (xhtml and pdf) that can contain custom parameters and custom templates that are used by many docbook users to get documents in their corporate identity.
Being able to specify parameters from the pom.xml, perhaps even dynamic values would be another worthwile feature.