Re: [Boost-docs] [Quickbook] Different rendering in Chrome [FIXED]

Subject: Re: [Boost-docs] [Quickbook] Different rendering in Chrome [FIXED]
From: Paul A. Bristow (pbristow_at_[hidden])
Date: 2011-06-08 14:52:00

> -----Original Message-----
> From: boost-docs-bounces_at_[hidden] [mailto:boost-docs-bounces_at_[hidden]] On Behalf Of
> Daniel James
> Sent: Wednesday, June 08, 2011 3:33 PM
> To: Discussion of Boost Documentation
> Subject: Re: [Boost-docs] [Quickbook] Different rendering in Chrome [FIXED]
> 
> On 8 June 2011 12:57, John Maddock <boost.regex_at_[hidden]> wrote:
> >
> > However, if we could all agree on how they should look, and the
> > conditions for breaking, then it appears this can be achieved with XSL
> > property sets, see for example:
> > http://docbook.sourceforge.net/release/xsl/current/doc/fo/section.leve
> > l1.properties.html
> 
> Could it be paramaterised? (so that we wouldn't have to agree)

And there are 6 (5 useful?) of these for different levels of sections, and one might reasonably want
1 and 2 to start on new page, but not minor sections 3,4,5 ...

Note - If you use many smallish sections to improve the targeting of the index terms (in html, an
index entry only takes you to the html page - and the page might be quite long so you might have to
use find within the page to locate the index term), you may want not to start each section with a
new page.

So quite useful to parameterize?

(OTOH this seems a sledge hammer when all one really wants is a 'newpage' mark-up!  But maybe that's
the price of creating both html and pdf).

Paul