Subject: Re: [Boost-docs] Quickbook [br] and \n are deprecated. How to avoid lots of warnings? Or should warnings be retired?
From: Paul A. Bristow (pbristow_at_[hidden])
Date: 2010-09-09 11:08:33
> -----Original Message-----
> From: boost-docs-bounces_at_[hidden] [mailto:boost-docs-
> bounces_at_[hidden]] On Behalf Of Daniel James
> Sent: Wednesday, September 08, 2010 11:24 PM
> To: Discussion of Boost Documentation
> Subject: Re: [Boost-docs] Quickbook [br] and \n are deprecated. How to
> lots of warnings? Or should warnings be retired?
> On 8 September 2010 19:20, Paul A. Bristow <pbristow_at_[hidden]>
> > I've been creating a FAQ page for Boost.Math
> > I want the question in italic on first line, and the answer in plain
> > font below.
> > And I want them numbered, so I'm using # lists.
> > How Should I create a forced newline other than using [br] or \n?
> > If there isn't a way, should the warning be removed?
> The warning was added before I was involved with quickbook. It doesn't
> have worked - there are still line breaks all over the place.
> My vote would be for removing the warning from '[br]' but keeping it on
> not supporting '\n' in quickbook 1.6 documents.
> > Attached is my desired output. Each FAQ has a number.
> > If I create new paragraphs, the numbering is 1 for each item:-(
> In the current version you can't have paragraphs in lists. This is
something I want
> to deal with, but getting it right is tricky.
> > Is there a right way to do this?
> Take a look at the attached - it uses the docbook markup for Q&As. It uses
> horrible hack for nested paragraphs. We could possibly add something to
> CSS to style it better as well.
I had forgotten that John Maddock had already tackled this problem.
His para 'solution'/skulduggery is:
[template para[text] '''<para>'''[text]'''</para>''']
his para name clashes with yours of course, so a straight boltin failed.
I quickly tried changing your name from para to para0, but that seemed to
cause all the links to fail, for reasons I don't have time to investigate
For now, as a simple sort of chap, I feel is that this is all a bit too
But I can see there could be a better solution and I'll revisit it later.
For this FAQ, I'm quite happy with [br] - but I'd rather not have lots of
I'm not sure I understand why one would want to ban \n, and it will require
some updating of lots of docs.
(But since More Boost docs need updating more regularly, that may not be a
This archive was generated by hypermail 2.1.7 : 2017-11-11 08:50:41 UTC