Hi,
On Tue, 6 Oct 2015 15:35:10 +1100
Aristedes Maniatis wrote:
> [...]
> I guess I'm just not understanding a fundamental concept in docbook
> then. I had always assumed docbook was a pure documentation schema
> and not intended to model real world concepts.
According to its
On 2015-10-05 22:48, Stefan Seefeld wrote:
there was a project as part of Boost (http://boost.org) to augment
DocBook with a more complete vocabulary for API documentation, which
ultimately became "BoostBook"
(http://www.boost.org/doc/libs/1_59_0/doc/html/boostbook.html).
This has been ported
On 06.10.2015 16:52, maxwell wrote:
> On 2015-10-05 22:48, Stefan Seefeld wrote:
>> there was a project as part of Boost (http://boost.org) to augment
>> DocBook with a more complete vocabulary for API documentation, which
>> ultimately became "BoostBook"
>>
Back about 2 years ago, there was a thread concerning a problem with Kindle
TOCs.
If you use the html element for toc.list.type (as recommended for Kindle)
and the CSS style "list-style-type: none" to suppress the numbers, some devices
work fine, but others, including older Kindle devices and
Aristedes Maniatis writes:
> I guess I'm just not understanding a fundamental concept in docbook
> then. I had always assumed docbook was a pure documentation schema and
> not intended to model real world concepts. When I look at
Well. Every now and then, we've been persuaded to
Hi Matteo,
On Tue, 6 Oct 2015 15:36:53 +0200
Matteo Regazzo wrote:
> [...]
> Does the DocBook include something like a "NOT" conditionfor the
> profiling?
Unfortunately, the profiling stylesheet doesn't support a NOT condition.
It would be very convenient to have one.
Dear all,
usually when I insert a condition in the tags of my document I have a
condition for every case.
I mean: if I have to show the value "3" in case of the first condition
and the value "5" in the second one, I write, for example:
/35/
in this way I can decide which value has to be