From None Tue Jul  4 16:57:57 2023
From: None
To: ntg-context@ntg.nl
Subject: None
Date: Tue, 04 Jul 2023 16:57:57 +0000
Message-ID: <168848987700.321384.7734256330463382523.generated@cgl.ntg.nl>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============4762318470921945333=="

--===============4762318470921945333==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit

XML(DocBook compliant document) => pdf 
converter, as FOP, ie

+----+           +----------+        +----+
|XML | --------> |FOP engine|------->| PDF|
|doc |           +----------+        +----+
|Book|             ^                       
+----+             |                         
                 +-------+
                 |XSL doc|               
                 +--------


+----+           +----------+        +----+
|XML | --------> |ConTeXt   |------->| PDF|
|doc |           +----------+        +----+
|Book|             ^
+----+             |  
                 +----------------+
                 |DocBookInConTeXt|
                 +----------------+

With same input, the output should be the same.

Hence, the only way to specify formatting informations
must be in a xml docbook document, not manipulating intermediate
stylesheets that will corrupt the portability of a document.

So i think that our efforts must be in direction to implement
docbook semantic by DocBookInConTeXt for ConTeXt engine.

For simon:
I just started to study <table> env. in DBinConTeXt, so
what about <colspec> and <spanspec> ?

luigi




--===============4762318470921945333==--