Re: [Boost-docs] [quickbook][phoenix] Can't build Phoenix as a PDF.

Subject: Re: [Boost-docs] [quickbook][phoenix] Can't build Phoenix as a PDF.
From: John Maddock (boost.regex_at_[hidden])
Date: 2011-06-22 08:56:33

>> Am I correct in thinking that these anchors are created by quickbook?
>
> Yes, they're created for headings. The markup looks like this:
>
>  <anchor id="phoenix.preface"/>
>  <bridgehead renderas="sect1" id="phoenix.preface-heading">
>    <link linkend="phoenix.preface">Preface</link>
>  </bridgehead>
>
> At one point I tried:
>
>  <bridgehead renderas="sect1" id="phoenix.preface">
>    <link linkend="phoenix.preface">Preface</link>
>  </bridgehead>
>
> But using the linkend inside the bridgehead with the id it links to
> caused something to go wrong (I forget what). If we didn't make
> headers link to themselves, there wouldn't be a need to add an anchor.
> It's not really a very useful feature in pdfs, so I could possibly add
> a flag to disable it.

Hmm, that's not ideal, consider if the user does a:

bjam html
bjam pdf

Then the docbook file is built for html first, and not rebuilt for the PDF 
build.

I was going to suggest the code you posted above, so if that doesn't 
work..... I don't know... how about something like:

<bridgehead renderas="sect1">
    <phrase id="phoenix.preface"/><link 
linkend="phoenix.preface">Preface</link>
 </bridgehead>

Thanks, John.

PS will try and see if the XEP XML validation can be turned off, also the 
issue has been reported to the Docbook guys at: 
http://sourceforge.net/tracker/?func=detail&atid=373747&aid=3324138&group_id=21935