<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.comp.lib.boost.documentation">
    <title>gmane.comp.lib.boost.documentation</title>
    <link>http://blog.gmane.org/gmane.comp.lib.boost.documentation</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lib.boost.documentation/4940"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lib.boost.documentation/4936"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lib.boost.documentation/4935"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lib.boost.documentation/4929"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lib.boost.documentation/4927"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lib.boost.documentation/4925"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lib.boost.documentation/4924"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lib.boost.documentation/4920"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lib.boost.documentation/4919"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lib.boost.documentation/4915"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lib.boost.documentation/4904"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lib.boost.documentation/4895"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lib.boost.documentation/4890"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lib.boost.documentation/4885"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lib.boost.documentation/4883"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lib.boost.documentation/4878"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lib.boost.documentation/4875"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lib.boost.documentation/4868"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lib.boost.documentation/4867"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lib.boost.documentation/4853"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lib.boost.documentation/4940">
    <title>standard for locating appropriate header file toinclude from doc page?</title>
    <link>http://comments.gmane.org/gmane.comp.lib.boost.documentation/4940</link>
    <description>&lt;pre&gt;A documentation URL like

http://www.boost.org/doc/libs/1_49_0/libs/*ptr_container*/doc/*ptr_array*
.html

means I should include &amp;lt;boost/ptr_container/ptr_array.hpp&amp;gt;, right? Or is
there no such convention? The actual documentation text has always lacked
any easily discoverable mention of the relevant header to include (and less
frequently needed - the library name for the linker).

It would be nice if the docs actually listed the header to include, of
course, for people landing from a web search or a link.
_______________________________________________
Boost-docs mailing list
Boost-docs&amp;lt; at &amp;gt;lists.boost.org
http://lists.boost.org/mailman/listinfo.cgi/boost-docs
&lt;/pre&gt;</description>
    <dc:creator>Jonathan Graehl</dc:creator>
    <dc:date>2012-05-25T18:25:03</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lib.boost.documentation/4936">
    <title>[quickbook] Problem with [pre element</title>
    <link>http://comments.gmane.org/gmane.comp.lib.boost.documentation/4936</link>
    <description>&lt;pre&gt;I have a problem with this [pre] block:

[pre
                                       1
                                       2
                                       6
                                      24
                                     120
                                     720
                                    5040
                                   40320
................Limit of 16 bit integers
                                  362880
                                 3628800
                                39916800
                               479001600
................Limit of 32 bit integers
                              6227020800
                             87178291200
                           1307674368000
                          20922789888000
                         355687428096000
                        6402373705728000
                      121645100408832000
                     2432902008176640000
................Limit of 64 bit integers
                    51090942171709&lt;/pre&gt;</description>
    <dc:creator>John Maddock</dc:creator>
    <dc:date>2012-04-12T11:32:43</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lib.boost.documentation/4935">
    <title>Sort headers correctly</title>
    <link>http://comments.gmane.org/gmane.comp.lib.boost.documentation/4935</link>
    <description>&lt;pre&gt;Hi,

If I have files like so:

boost/bar/xxx.hpp
boost/foo/www.hpp
boost/foo/yyy.hpp
boost/aaa.hpp
boost/zzz.hpp

Doxygen+Boostbook will give them in the following order:

boost/aaa.hpp
boost/foo/www.hpp
boost/bar/xxx.hpp
boost/foo/yyy.hpp
boost/zzz.hpp

i.e. it only looks at the name of the file and not at the path.

Is there a way to fix this?
&lt;/pre&gt;</description>
    <dc:creator>Mathias Gaunard</dc:creator>
    <dc:date>2012-03-27T12:31:15</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lib.boost.documentation/4929">
    <title>[quickbook and boostbook] sections and pages</title>
    <link>http://comments.gmane.org/gmane.comp.lib.boost.documentation/4929</link>
    <description>&lt;pre&gt;Dear quickbook/boostbook wizards,

I'm fooling around with sections and it struck me that only the 
top-level sections are isolated on separate pages. How can I let 
quickbook/boostbook/bjam know that I want the subsections to be on 
separate pages as well?

My Jamfile:


main.qbk:


The resulting table of contents (as I want it):


The generated pages (not as I want it):


How I'd want the pages to be generated:


This is, by the way, a type of information I'd expect to find in the 
quickbook or boostbook documentation. Unfortunately neither provides 
any clue on how paging can be adjusted.

Hopefully somebody can help me out... thanks in advance.

-Julian
&lt;/pre&gt;</description>
    <dc:creator>Julian Gonggrijp</dc:creator>
    <dc:date>2012-03-17T09:39:51</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lib.boost.documentation/4927">
    <title>quickbook/boostbook relationship</title>
    <link>http://comments.gmane.org/gmane.comp.lib.boost.documentation/4927</link>
    <description>&lt;pre&gt;I thought I understood this:

// docbook includes all the transformations to generate "general purpose" 
documents
// xslt transforms docbook elements to html or whatever.
docbook xml -&amp;gt;xslt -&amp;gt; html or (fo -&amp;gt;pdf)  or ?..

// boostbook adds a bunch of new elements specialized for C++ library 
documentation
// xslt transforms this to docbook elements.  The output of this 
transformation can be used above.
boostbook xml -&amp;gt; xslt-&amp;gt; docbook xml

// quickbook defines a new "more convenient syntax" for C++ library 
documents
// quickbook transforms this syntax to boostbook syntax to be used above.
quickbook source -&amp;gt; quickbook -&amp;gt; boostbook xml.

OK this always made sense to me.

I look in the documentation for boost book xml and I find a lot of elements
such as function, method, etc with a fairly elaborate structure   This also 
makes
sense since the object is to capture the "meaning" or "structure" of the 
documentation
(and by implication the library being documented).

BUT when I look a the quickbook syntax I don&lt;/pre&gt;</description>
    <dc:creator>Robert Ramey</dc:creator>
    <dc:date>2012-03-09T23:05:57</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lib.boost.documentation/4925">
    <title>Why not use the xml catalog in Linux?</title>
    <link>http://comments.gmane.org/gmane.comp.lib.boost.documentation/4925</link>
    <description>&lt;pre&gt;Trying to build the boost documentation on openSUSE fails because the
stylesheets are in /usr/share/xml/docbook/stylesheet/nwalsh/current (a
symlink to the current version) and not in
/usr/share/xml/docbook/stylesheet/nwalsh where boost.book searches. This
begs the question why you check that at all on Linux. All standard stylesheets and
dtds can be found via the catalog so /etc/xml/catalog is the only thing that
needs to be referenced besides the boost.book specific stuff.

Being not very familiar with JAM (boost is the only package I maintain for
SLES/openSUSE that uses it), how would I have to change boostbook.jam in
order to conditionally not use docbook-xsl-dir and docbook-dtd-dir?

Currently I simply use the attached patch for boostbook.jam but that doesn't
make it conditional on OS.

Philipp
_______________________________________________
Boost-docs mailing list
Boost-docs&amp;lt; at &amp;gt;lists.boost.org
http://lists.boost.org/mailman/listinfo.cgi/boost-docs
&lt;/pre&gt;</description>
    <dc:creator>Philipp Thomas</dc:creator>
    <dc:date>2012-02-29T10:10:14</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lib.boost.documentation/4924">
    <title>QuickBook Chapter Numbers</title>
    <link>http://comments.gmane.org/gmane.comp.lib.boost.documentation/4924</link>
    <description>&lt;pre&gt;Hi,

Some library documentations start with Chapter 1.0, for example: bimap, 
ICL, and also Boost.Geometry.

Many do have a proper chapter number. How is this number assigned? I 
cannot find the difference between our main QBK and for example that of 
Chrono, which has a proper chapter number.

Should we add a dependency in doc\Jamfile.v2 ?

Because I see this line &amp;lt;implicit-dependency&amp;gt;../libs/chrono/doc//chrono 
it seems logical that geometry (and some other libs) should be added 
there. Is then a chapter number assigned?

Or does it work otherwise?

Thanks, Barend
&lt;/pre&gt;</description>
    <dc:creator>Barend Gehrels</dc:creator>
    <dc:date>2012-02-12T11:21:05</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lib.boost.documentation/4920">
    <title>More equation woes.....</title>
    <link>http://comments.gmane.org/gmane.comp.lib.boost.documentation/4920</link>
    <description>&lt;pre&gt;Some more experimentation reveals that:

* IE9 will only support the MathJax scripts if the script is loaded from a 
subdirectory of the one containing the HTML (a non-starter) otherwise you 
get a security warning (which I missed the first time), and if you either 
miss the warning or just follow IE9's advice and block the script then all 
the equations disappear :-(
* I tried using SVG's instead of MathML or Tex, and Oh dear that's as bad 
:-(
Yes IE9 supports SVG's, but in order for a graceful fallback be provided for 
earlier IE users you have to use &amp;lt;object&amp;gt; tags - that's OK that's what the 
Docbook stylesheets generate - except IE9 (and only IE9) won't then display 
either the SVG or the fallback image unless the image has explicit width and 
height attributes.  If that's not bad enough, IE and all the other browsers 
handle the width and height attributes differently.   I'm mean seriously 
what the &amp;amp;&amp;amp;^%$$ does MS think it's doing here?  Anyhow, I simply can't find 
a magic combination of factors that &lt;/pre&gt;</description>
    <dc:creator>John Maddock</dc:creator>
    <dc:date>2012-02-02T11:19:12</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lib.boost.documentation/4919">
    <title>Experimenting with equation (MathJax) support</title>
    <link>http://comments.gmane.org/gmane.comp.lib.boost.documentation/4919</link>
    <description>&lt;pre&gt;I've been experimenting with the tentative equation handling support in 
Trunk, and have some observations:

* There's no docs.... took me a while to figure out what to do...
* I added quickbook markup as follows to doc/test/test.qbk to test both 
LaTex and MathML support:

[section Equations]

This equation is formatted from Latex text:

'''&amp;lt;inlinemediaobject&amp;gt;&amp;lt;textobject role="tex"&amp;gt;ax^2 + bx + c = 
0&amp;lt;/textobject&amp;gt;&amp;lt;/inlinemediaobject&amp;gt;'''

This equation is formed from MathML:

'''&amp;lt;inlinemediaobject&amp;gt;&amp;lt;textobject role="MathML"&amp;gt;&amp;lt;?dbhtml-include 
href="test.mml"?&amp;gt;&amp;lt;/textobject&amp;gt;&amp;lt;/inlinemediaobject&amp;gt;'''

[endsect]

Then I modified the Jamfile to add an xsl:path attribute so that test.mml 
could be found in the current directory, and everything builds OK, raw HTML 
output looks OK to.

* The equations are both rendered correctly in Firefox, but MathJax support 
is only present in the HTML if a Tex object is present - I guess some change 
to our XSL stylesheets is required for the latter (and that I can't set the 
role t&lt;/pre&gt;</description>
    <dc:creator>John Maddock</dc:creator>
    <dc:date>2012-02-01T19:28:21</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lib.boost.documentation/4915">
    <title>[quickbook] Why doesn't this work?</title>
    <link>http://comments.gmane.org/gmane.comp.lib.boost.documentation/4915</link>
    <description>&lt;pre&gt;I'm rather confused.. I keep trying to use templates to reduce some of 
the repetition in doing the tree TR proposal. And I ran into a strange 
error. I've reduced my problem down to this code:

   [template tr_ref[id] [link [id] tr]]
   [tr_ref hierarchy.req]

It produces this error:

   x.qbk:2: error: Mismatched code bracket

The error happens on the use of the template. If the template isn't used 
it's fine. And if the template is changed to this:

   [template tr_ref[id] [link id tr.[id]]]
   [tr_ref hierarchy.req]

No error happens. Any idea what's going on?

Rene.

&lt;/pre&gt;</description>
    <dc:creator>Rene Rivera</dc:creator>
    <dc:date>2012-01-21T05:01:28</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lib.boost.documentation/4904">
    <title>How to build the documentation</title>
    <link>http://comments.gmane.org/gmane.comp.lib.boost.documentation/4904</link>
    <description>&lt;pre&gt;Hi

I created a small patch for libs/python/doc/tutorial/doc/tutorial.qbk

How can I check that it builds correctly and generates propper html?


Regards.

Pedro.
_______________________________________________
Boost-docs mailing list
Boost-docs&amp;lt; at &amp;gt;lists.boost.org
http://lists.boost.org/mailman/listinfo.cgi/boost-docs
&lt;/pre&gt;</description>
    <dc:creator>Pedro Larroy</dc:creator>
    <dc:date>2011-12-25T18:35:40</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lib.boost.documentation/4895">
    <title>Preventing private member functions from appearing inthe doxygen reference info</title>
    <link>http://comments.gmane.org/gmane.comp.lib.boost.documentation/4895</link>
    <description>&lt;pre&gt;I'm struggling to stop private member functions from appearing in the Doxygen reference section of
Quickbook generated stuff.

private member functions do not appear in the Standalone Doxygen docs, and I've tried to set the
corresponding &amp;lt;doxygen:param&amp;gt; settings in the jamfile.

&amp;lt;doxygen:param&amp;gt;EXTRACT_ALL=NO
    &amp;lt;doxygen:param&amp;gt;EXTRACT_PRIVATE=NO
    &amp;lt;doxygen:param&amp;gt;EXTRACT_STATIC=NO &amp;lt;doxygen:param&amp;gt;HIDE_UNDOC_MEMBERS=YES 
 &amp;lt;doxygen:param&amp;gt;HIDE_UNDOC_MEMBERS=YES
 &amp;lt;doxygen:param&amp;gt;HIDE_UNDOC_CLASSES=YES

but I'm still getting the private members listed.

Please can anyone confirm that they have seen this working as expected, supressing private members?

(This will confirm that I am missing something).

Or any others suggestions on tracing this?

Thanks

Paul

---
Paul A. Bristow,
Prizet Farmhouse, Kendal LA8 8AB  UK
+44 1539 561830  07714330204
pbristow&amp;lt; at &amp;gt;hetp.u-net.com
&lt;/pre&gt;</description>
    <dc:creator>Paul A. Bristow</dc:creator>
    <dc:date>2011-12-08T18:59:53</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lib.boost.documentation/4890">
    <title>[Quickbook] How to control the layout of a table?</title>
    <link>http://comments.gmane.org/gmane.comp.lib.boost.documentation/4890</link>
    <description>&lt;pre&gt;How is the layout of a table controlled? Vertical alignment,
horizontal alignment, border size, cell padding, cell spacing, width,
background color, etc.

How can the special handling of the first row be suppressed?

How are columns or rows spanned?

--Beman
&lt;/pre&gt;</description>
    <dc:creator>Beman Dawes</dc:creator>
    <dc:date>2011-12-06T14:44:06</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lib.boost.documentation/4885">
    <title>Quickbook glob includes..</title>
    <link>http://comments.gmane.org/gmane.comp.lib.boost.documentation/4885</link>
    <description>&lt;pre&gt;I've just checked in the ability to "[include *.qbk]" multiple files at 
once. This is in the quickbook dev branch. The implementation of glob is 
a port to C++ from the C one present inside the b2 engine. Note, I 
didn't add tests for this. Will do that later after some time for people 
to look at it and doing any needed changes from that.

Feedback welcome.

&lt;/pre&gt;</description>
    <dc:creator>Rene Rivera</dc:creator>
    <dc:date>2011-12-01T04:39:17</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lib.boost.documentation/4883">
    <title>Sample TR2 library proposal using Quickbook</title>
    <link>http://comments.gmane.org/gmane.comp.lib.boost.documentation/4883</link>
    <description>&lt;pre&gt;I've added a sample TR2 library proposal to trunk at
boost-root\tools\quickbook\extra\cxx_committee.

It's based on René and Bernhard's
http://svn.boost.org/svn/boost/sandbox/tree/libs/tree/proposal

It sort of works. The document does get produced, but it just looks
like a regular boost library, not like a standards committee document.
In the tree proposal, the external stylesheet gets replaced by inline
styles. That's a requirement for the committee, as the html has to be
complete without reference to an external stylesheet. But that doesn't
happen with the cxx_committee version, even though the Jamfile,
proposal.qbk, and proposal.css files were originally copied from the
tree sandbox proposal subdirectory.

Rene, what did you do to cause the stylesheet to be inlined?

--Beman
&lt;/pre&gt;</description>
    <dc:creator>Beman Dawes</dc:creator>
    <dc:date>2011-11-30T16:09:58</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lib.boost.documentation/4878">
    <title>Using Quickbook for TR2 proposals?</title>
    <link>http://comments.gmane.org/gmane.comp.lib.boost.documentation/4878</link>
    <description>&lt;pre&gt;Presumably, several Boost developers will be working on TR2 proposals
soon, and Quickbook seems like it might be an attractive way to create
and maintain those proposals as they go through the committee process.

In particular, I'd like to maintain a single source for reference
documentation.  Since I already follow the standard library's
conventions for specifications, the textual differences like different
namespaces should be easy to cope with using quickbook macros and
conditions.

Is the FAQ "Can I use QuickBook for non-Boost documentation?" entry
the best place to start?

http://www.boost.org/doc/libs/1_48_0/doc/html/quickbook/faq.html

It might be helpful if we could put together an example for generating
TR2 proposals.

Is Quickbook a reasonable approach?

Comments?

--Beman
&lt;/pre&gt;</description>
    <dc:creator>Beman Dawes</dc:creator>
    <dc:date>2011-11-29T17:07:45</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lib.boost.documentation/4875">
    <title>Effects of document-type?</title>
    <link>http://comments.gmane.org/gmane.comp.lib.boost.documentation/4875</link>
    <description>&lt;pre&gt;The Quickbook docs for document-type list the names (book, article,
library, etc.) but gives no indication as to what the effects are.
Does a stylesheet change? Do other settings change?

See http://www.boost.org/doc/libs/1_48_0/doc/html/quickbook/syntax.html#quickbook.syntax.block.document

The best response would be if someone could update the docs, perhaps
by converting the list of names to a table showing the effect of each
name.

Thanks,

--Beman
&lt;/pre&gt;</description>
    <dc:creator>Beman Dawes</dc:creator>
    <dc:date>2011-11-29T14:56:44</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lib.boost.documentation/4868">
    <title>Quickbook wish list..</title>
    <link>http://comments.gmane.org/gmane.comp.lib.boost.documentation/4868</link>
    <description>&lt;pre&gt;While doing the documentation for the Predef library I'm working on I've
run into a set of features that seems either inconsistent or just missing.
I thought it would be good to share the list for future reference and
general feedback:

* Ability to apply syntax coloring to code blocks one at a time. Right now
one can globally switch the language system with "[c++]" etc. But what I'd
rather have is the capability to to a temporary switch (i.e. a push and
pop). In my case I want to set the global default to "teletype" and then
choose "c++" for certain places.

* Ability to use code callouts in regular code blocks instead of just in
code "import". This seems like just a consistency issue. It seems to me
that the code markup aspect available to the "import" should be available
to code blocks also. Although right now callouts are the only feature in
this context.

* And of course I've already mentioned the file inclusion/extraction from
code files.

* And the related include/import with file globs. (I'm actually&lt;/pre&gt;</description>
    <dc:creator>Rene Rivera</dc:creator>
    <dc:date>2011-11-22T16:18:42</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lib.boost.documentation/4867">
    <title>qbk and org-mode</title>
    <link>http://comments.gmane.org/gmane.comp.lib.boost.documentation/4867</link>
    <description>&lt;pre&gt;
Another format that IMO has a lot to recommend it is Emacs' Org mode.
It's very mature, completely programmable in all the ways I think Boost
needs, widely used, and well-supported outside of Boost.  It has the
disadvantage of depending on Emacs (or Emacs+Vim --
http://www.vim.org/scripts/script.php?script_id=3342) and being
completely incompatible syntax with existing qbk.  Mitigating factors:
those editors are free, we are talking about a syntax redesign anyhow,
and automated conversion should be possible.

Just something to consider before we invent a new programmable system.

&lt;/pre&gt;</description>
    <dc:creator>Dave Abrahams</dc:creator>
    <dc:date>2011-11-08T20:52:58</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lib.boost.documentation/4853">
    <title>A downside of qbk</title>
    <link>http://comments.gmane.org/gmane.comp.lib.boost.documentation/4853</link>
    <description>&lt;pre&gt;
I've been meaning to point out the difference between 

https://github.com/boost-lib/parameter/blob/master/doc/index.rst
https://github.com/boost-lib/spirit/blob/master/doc/introduction.qbk

As long as qbk is a full-fledged programming language, we may never be
able to expect better.  Any ideas?  Does anyone think we can possibly
convince GitHub to include a qbk processor?

&lt;/pre&gt;</description>
    <dc:creator>Dave Abrahams</dc:creator>
    <dc:date>2011-11-06T18:40:32</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lib.boost.documentation/4842">
    <title>How to start Quickbook lists items with a newparagraphs</title>
    <link>http://comments.gmane.org/gmane.comp.lib.boost.documentation/4842</link>
    <description>&lt;pre&gt;I am getting a warning

multiprecision.qbk:425: warning: line breaks generate invalid boostbook (will only note first
occurrence).

from attempts to a get items in a list to have a bold line, then start a new paragraph.

# [*Precision - Compile-time Versus versus Run-time.][br]
After consultation on the Boost list,
it was decided that the best compromise was to fix precision compile-time,
rather than allow the choice to be made at run-time.[br]
A major factor was the sheer difficulty of achieving a run-time solution,
but also the risk of performance penalty, longer compile times,
risk of errors from complexity, greater difficulty of testing.

to display

1 *First list item heading in bold.*
First para of first list item,
...
i.

A second paragraph in this numbered list.

2 *Second list item in bold with a newline at the end*
This is a para about the second list.

This is 2nd paragraph of second list item

...

Is there anything I should I be doing to achieve this layout?

(which seems to produce the right ou&lt;/pre&gt;</description>
    <dc:creator>Paul A. Bristow</dc:creator>
    <dc:date>2011-11-01T15:51:55</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.lib.boost.documentation">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.lib.boost.documentation</link>
  </textinput>
</rdf:RDF>

