Re: [Boost-docs] Sphinx integration

Subject: Re: [Boost-docs] Sphinx integration
From: Mateusz Łoskot (mateusz_at_[hidden])
Date: 2011-10-17 14:54:52

On 16 October 2011 14:14, Dave Abrahams <dave_at_[hidden]> wrote:
> on Thu Oct 13 2011, Mateusz Łoskot <> wrote:
>> On 13 October 2011 03:16, Rene Rivera <grafikrobot_at_[hidden]> wrote:
>>> On 10/11/2011 8:57 AM, Mateusz Loskot wrote:
>>>> Now, regarding the implementation of such translator:
>>>> - is there anything already available in current doc tools in Boost,
>>>> Vault,...?
>>>> - if not, where it should go? separate cmd line tool like quickbook?
>>>> - what's best way to parse XML for BoostDoc for ? libxml, Boost.Tree,
>>>> Spirit?
>>> <>
>>> And there's support for using that already in the b2 "doxygen.jam" file
>>> <>:
>>> # Which processor to use for various translations from Doxygen.
>>> feature.feature doxygen.processor : xsltproc doxproc : propagated implicit ;
>> Thanks, I will take a look.
>>> And of course the currently used xsltproc translator. Is this what you are
>>> wanting? Or did I not understand the thread?
>> The latter is also possible. The more I'm thinking about the initial
>> issue, the more I'm convinced about its utopian nature.
> Hi Mateusz,
> I've been intending to ask what you mean by this.  I do hope you're not
> giving up.

Hi Dave,

Not giving up, but scaling down and not going big :-)
I will stick to improving Boost.Geometry docs instead of Boost docs at large.
Also, I'm allergic to Boost.Build scripting, so I won't be able to
provide enough
integration, etc. I have no resources for that.

First, I need to improve our custom Doxygen processor written in C++
using 3rd-party RapidXml library. First, I need to get rid of the
RapidXml and use
Boost-based tool like Boost.PropertyTree.
My plan is to make it general-purpose tool, so perhaps rest of Boost
will like it.

Best regards,

Mateusz Loskot,
Charter Member of OSGeo,
Member of ACCU,

This archive was generated by hypermail 2.1.7 : 2017-11-11 08:50:41 UTC