Boost logo

Boost-Build :

Subject: Re: [Boost-build] New doc format.
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2018-01-22 03:17:44


On 01/21/2018 08:04 PM, Rene Rivera via Boost-build wrote:
> On Sat, Jan 20, 2018 at 4:59 PM, Rene Rivera <grafikrobot_at_[hidden]> wrote:
>> On Sat, Jan 20, 2018 at 4:16 PM, Steven Watanabe via Boost-build <
>> boost-build_at_[hidden]> wrote:
>>> <snip>
>>> I think it shouldn't be too hard to auto-generate
>>> tags wrapping each part. It should be unambiguous,
>>> since it's the name of whatever jam construct is
>>> being documented.
>> Looks reasonable.
> One thing that occurred to me after some stewing.. I would want to make
> sure that there's still a mechanism for using custom tags (even if the
> syntax is different than the asciidoctor syntax). I don't want to be
> painted into a corner as to what kind of documentation structure I must
> use. As the inevitable will happen and we will find contexts in which the
> default doesn't work (or is not ideal). And I can't tell from the changes
> if you preserved that capability.

I think it should work if you put the tag in
an asciidoc comment:

// tag::xxx

// end::xxx

as this will simply be passed through.

In Christ,
Steven Watanabe

Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at