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: Daniel James (dnljms_at_[hidden])
Date: 2011-06-22 09:30:47

On 22 June 2011 09:56, John Maddock <boost.regex_at_[hidden]> wrote:
>>
>> 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

It'd be a boost build feature, so you'd add something like
'<linked-headers>off' to your pdf rule. Hopefully we could include the
feature in the path to keep the intermediate files separated.

> 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>

I'll give it a go.