Hi Michael,
You can achieve what you want by moving the code samples elsewhere when
you make topics. An Xinclude that does not resolve is left as an
xi:include element in the output of the parser. Then move the code files
back.
Bob Stayton
Sagehill Enterprises
[email protected]
On 5/8/2019 2:47 AM, Fritsch, Michael wrote:
Hello,
I have large DocBook books which use xi:inlucde to include chapters
and sections in the Book element. Now, I use the topic-maker-chunk.xsl
file and the xsltproc processor to create topics from the Book,
Chapter and Section element.
In principle, everything is fine. I get a lot of topic files and the
assembly file.
However, in my initial documents I also include code examples inside
the programlisting element using xi:include. During the
transformation, these code examples are included into the topic
documents. It would be much better in this case, when the xi:include
elements would be preserved. Is there a way to achieve this?
Best regards,
Michael
Dr. Michael Fritsch
Technical Editor
tel +49.40.325587.214
fax +49.40.325587.999
[email protected] <mailto:[email protected]>_
CoreMedia AG - Content matters.
Ludwig-Erhard-Str. 18
20459 Hamburg, Germany
www.coremedia.com <http://www.coremedia.com/>
------------------------------------------------------------
Executive Board: Sören Stamer, Dr. Klemens Kleiminger
Supervisory Board: Professor Dr. Florian Matthes (Chairman)
Trade Register: Amtsgericht Hamburg, HR B 76277
----------------------------------------------------------------------
*Stay up to date and _subscribe to our newsletters
<http://l.coremedia.com/news>_***
