By the way, you can work around the "climbing" href problem described in
my previous post by changing the "out" parameter in the <xep> elements
from this:
out="${dita.map.output.dir}${file.separator}${dita.topic.filename.root}.
pdf"
to this:
out="${output.dir}${file.separator}${dita.map.filename.root}.pdf"
It seems that the DITA toolkit reproduces the folder structure it
creates in the temp.dir (which it uses to keep links working during
processing) when it outputs a map. XXE doesn't know about this
additional output path, though, so its copyFile step fails. This
workaround forces the pdf to be created in the original ouput directory,
as XXE expects.
BTW, you can use this workaround with the default FOP engine too, but
you'll have to create and point to your own build file similar to my
instructions for XEP. Just use this <antcall> element instead of the
<xep> task in the [your_project_name].topic2pdf target:
<antcall target="dita.fo2pdf">
<param name="input"
value="${dita.map.output.dir}${file.separator}${dita.topic.filename.root
}.fo"></param>
<param name="output"
value="${output.dir}${file.separator}${dita.topic.filename.root}.pdf"></
param>
</antcall>
And use this <antcall> element instead of the <xep> task in the
[your_project_name].map2pdf target:
<antcall target="dita.fo2pdf">
<param name="input"
value="${dita.map.output.dir}${file.separator}${dita.map.filename.root}.
fo"></param>
<param name="output"
value="${output.dir}${file.separator}${dita.map.filename.root}.pdf"></pa
ram>
</antcall>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://www.xmlmind.com/pipermail/xmleditor-support/attachments/20060801/8c9efa3e/attachment.htm
