On 2/27/22 1:18 PM, Frank Steimke wrote:
/No block Elements within para/
That's in my 80% because neither ODF nor OOXML do allow tables or
lists in paragraphs. I would see a great benefit when the DocBook
based structural interchange format would allow easy transformation
into office
Hello List,
I would like to propose a project "canonical DocBook" to the DocBook TC,
and I am interested in the opinion of this mailing list. I hope this is
the right list.
DocBook is a great system for creating technical documents. We use it
successfully for various purposes, which include
On Sun, 27 Feb 2022 at 11:02, Frank Steimke
wrote:
> My suggestion is that the DocBook TC standardize and document the
> canonical DocBook format.
(My view). This is the problem Frank?
I'm sure, even within the TC, that defining and agreeing which 'form'
is to be named Canonical
would be
What would be a better way to accomplish this?
Ask Norm to document its internal format so that a particular community
can choose it as the "de facto standard" for developing own stylesheets
based on it?
Frank
Am 27.02.22 um 12:09 schrieb Dave Pawson:
On Sun, 27 Feb 2022 at 11:02, Frank
On Sun, 27 Feb 2022 at 11:20, Frank Steimke
wrote:
>
> What would be a better way to accomplish this?
>
> Ask Norm to document its internal format so that a particular community
> can choose it as the "de facto standard" for developing own stylesheets
> based on it?
Not sure at all Frank.
OK, i see. Not so easy.
However, i never wanted to be unfair to anyone. My hope or expectation
was that the stylesheets are already available, because we have XslTNG.
We have the stylesheets for preprocessing in XslTNG, but we do not have
a documentation of the DocBook subset they produce.
> Our own stylesheets are therefore divided into at least phases. First,
[…]
> As far as I can see, the XSL 3 stylesheets for XslTNG are also similar
> in structure.
Yep. The xslTNG stylesheets go through several standard stages:
1. Normalize the logical structure (get rid of entity refs,
Thank you very much for your comments and suggestions, Norm. Please
allow a few remarks.
/"After a while, this starts to feel less like a canonical DocBook and
more like a structural interchange format"./
Yes, based on DocBook. After all, the result of standard steps 1 to 7 is
almost a
Yes. If the para element has an xml:id attribute, you will have to
decide which of the elements in the generated sequence should get that
id. I would vote for the first Element, but every other Element is also
possible. A reference to the para element in DocBook references a larger
area
