attached is the example, coupl of notes;-
the first part configures the paths for the classpaths, it needs to
match your system
then i've used properties for input/output paths to make things easier
this stuff tends to go in a separate "init" target that can be depended upon
i note that your attempting to process a directory full of files, this
exmaple only does a single file
however saxon will except a dir for in and out params , however you
can't filter out files like "empty.xml" - this is what I meant by a
downside of the java task - it doesn't do stuff that style/xslt does for
you. you would have to eddit the fop task for multiple files as well.
oh one other detail, i use forward slashes on all paths - ant usually
tranlates these for you. this *isn't* done for things passed as
arguments to the java task.
with some hacking this should meet your needs...
HTH,
Ian
Wendy Smoak wrote:
> [sorry, wrong button before...]
>
> From: "Ian Atkin" <>
>
>> I have a working example build script with ant 1.6.2, saxon 6.5.3,
>> docbook-xsl 1.68.1 and fop 0.20.5 if your interested...
>
>
> What I was trying to say is, Yes! An example build file would be great.
> I've got the 'fop' task working for .fo -> .pdf, but the only way I can
> get the .fo file is with Cygwin and 'xmlto'.
>
> Thanks,
> Wendy Smoak
>
>
>
