Hi! Currently I am under high pressure at work, but would like to get into the proto details even in the absence of a web browser. I found it helpful to have things printed (unsafe trees here) in such a situation. So could someone with a working toolchain be so kind and generate a PDF out of the documentation sources and put it into the vault? Thanks, Markus
Markus Werle wrote:
So could someone with a working toolchain be so kind and generate a PDF out of the documentation sources and put it into the vault?
I have tried many times to build Proto's docs as PDF and failed. The error I get is: xslt-xsltproc ../../../bin.v2/libs/proto/doc/gcc-3.4/debug/proto.fo Making portrait pages on USletter paper (8.5inx11in) fop.render.pdf ../../../bin.v2/libs/proto/doc/gcc-3.4/debug/proto.pdf (document [system-id file:/c:/proto/bin.v2/libs/proto/doc/gcc-3.4/debug/proto.fo] (validate [error] There can be only one 'rx:outline' element as a child of 'fo:root'. [validation total: 1 error] I haven't investigated the failure. Perhaps someone else might have more luck than I. (Proto.zip comes with the reference section in BoostBook format (docs/protodoc.xml) so you don't need to set up Doxygen or anything.) -- Eric Niebler Boost Consulting www.boost-consulting.com
Eric Niebler wrote:
Markus Werle wrote:
So could someone with a working toolchain be so kind and generate a PDF out of the documentation sources and put it into the vault?
I have tried many times to build Proto's docs as PDF and failed. The error I get is:
xslt-xsltproc ../../../bin.v2/libs/proto/doc/gcc-3.4/debug/proto.fo Making portrait pages on USletter paper (8.5inx11in) fop.render.pdf ../../../bin.v2/libs/proto/doc/gcc-3.4/debug/proto.pdf (document [system-id file:/c:/proto/bin.v2/libs/proto/doc/gcc-3.4/debug/proto.fo] (validate [error] There can be only one 'rx:outline' element as a child of 'fo:root'. [validation total: 1 error]
I haven't investigated the failure. Perhaps someone else might have more luck than I. (Proto.zip comes with the reference section in BoostBook format (docs/protodoc.xml) so you don't need to set up Doxygen or anything.)
Eric, are you using XEP as the FO processor by any chance? If so you need to turn off both FOP and FOP1 extensions: <format>pdf:<xsl:param>fop1.extensions=0 <format>pdf:<xsl:param>fop.extensions=0 <format>pdf:<xsl:param>xep.extensions=1 HTH, John.
John Maddock wrote:
Eric, are you using XEP as the FO processor by any chance? If so you need to turn off both FOP and FOP1 extensions:
<format>pdf:<xsl:param>fop1.extensions=0 <format>pdf:<xsl:param>fop.extensions=0 <format>pdf:<xsl:param>xep.extensions=1
Thanks, John! Yes, that was it. The resulting pdf is too large for the File Vault, so I uploaded it here: http://boost-sandbox.sourceforge.net/libs/proto/doc/proto.pdf -- Eric Niebler Boost Consulting www.boost-consulting.com
participants (3)
-
Eric Niebler -
John Maddock -
Markus Werle