From: John Maddock (john_at_[hidden])
Date: 2007-09-24 06:42:08
Rene,
While I've got your attention I've two more Boostbook bbv2 niggles, sorry!
1) Is there a way to restrict xslt param's to specific build-types only - so
I can have different pdf and html settings: .png's for one and .svg's for
the other for example? I've tried adding
<toolset>pdf:<xsl:param>admon.graphics.extension=".svg"
or:
<target-type>pdf:<xsl:param>admon.graphics.extension=".svg"
or
<variant>pdf:<xsl:param>admon.graphics.extension=".svg"
But none seem to work, any ideas?
2) PDF generation is really annoying me: it insists on placing the generated
PDF and FO files in an "unmentionable" directory under bin.v2/ which means
all relative links to image files get broken, and no images are embedded in
the PDF. Currently the option is to manually copy images into whatever
directory bjam puts the FO file: which varies depending upon what compiler
you have as your default toolset :-( Would it be possible for the FO and
PDF files to be placed in a subdirectory called say "pdf" of the current
build directory, just like html/man pages etc are? Then links to images
would be found when the PDF is built, as would links to admonishments in
boost-root/doc/.
I should say at this point, that I've raised this before with Vladimir and
he's dead set against such a change, but I figured I might just ware him
down if I don't manage to convince you :-)
Many thanks, John.