I think Paul is probably the one who knows the most about this, but I'll post to the list to be sure I don't miss anything.

As I mentioned before, I'm reworking the build to gradle so that

1. We can do away with the old ant version that is not compatible with recent Java versions 2. Automatically get the necessary libraries and other dependencies (so no more manually getting the lib folder (and hopefully: tools)) to build

However, I'm running into a number of things that I'd like some input on.

1. Is the monohtml task ever actually used? If so for which documents?

2. In src/docs/xsl/ some of the stylesheets (eg fo.xsl, html.xsl and htmlbase.xsl) have relative paths to the stylesheets in docbook-stylesheets. If I want to be able to automatically get the necessary stylesheets, I need to be able to use the catalog definition, eg instead of

<xsl:import href="../../../tools/docbook-stylesheets/html/chunk-common.xsl"/>

it would use

<xsl:import href="http://docbook.sourceforge.net/release/xsl/current/html/chunk-common.xsl"/>

And then the catalog file from the stylesheet dependency would resolve that to the correct files. Is there any other reason for the use of these relative paths other than the build itself?

3. Similarly, the xml sources define relative paths to the DTD:

<!DOCTYPE set PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "../../tools/docbook-dtd/docbookx.dtd">

If I'm going to do away with the tools folder, these become invalid. Is that a problem? Otherwise I can always add a task that automatically downloads and unzips this to that location.

Mark Rotteveel

Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-docs mailing list

Reply via email to