My latest foray into ant:
Xinclude processing, fo output using xep.
path id=xslt.processor.classpath
pathelement path=/myjava/saxon655.jar / !-- Saxon jar --
pathelement path=/myjava/resolver.jar/ !-- resolver jar --
pathelement path=${websiteHome}/extensions/saxon64.jar/ !--
docbook
On Thu, Apr 10 2008 11:36:06 +0100, [EMAIL PROTECTED] wrote:
My latest foray into ant:
...
target name=fo depends=init, clean.pdf
echoGenerate the fo output/echo
java classname=${xslt.processor.class}
fork=yes
dir=${in.dir}
failonerror=true
classpath
tagged on PDF
processing).
It seemed easier and faster to use Saxon from the java command.
-Original Message-
From: Tony Graham [mailto:[EMAIL PROTECTED]
Sent: Thu 4/10/2008 8:46 AM
To: docbook-apps@lists.oasis-open.org
Subject: Re: [docbook-apps] ant and db5, xinclude and fo output
On Thu, Apr 10, 2008 at 2:20 PM, Johnson, Eric [EMAIL PROTECTED] wrote:
one to resolve the xincludes then one to process the content. Since we are
also using profiling that resulted in a three stage process (5 if we tagged
on PDF processing).
It seemed easier and faster to use Saxon from the
