[
https://issues.apache.org/jira/browse/DBF-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12884634#action_12884634
]
chris snow commented on DBF-10:
-------------------------------
I agree with Steve - ot being able to modularise your documentation makes this
project only suitable for small documentation efforts.
By the way, there are some xinclude instructions on
http://www.devx.com/Java/Article/35301/1954
> Support for xi:include
> ----------------------
>
> Key: DBF-10
> URL: https://issues.apache.org/jira/browse/DBF-10
> Project: DocBook Framework
> Issue Type: New Feature
> Affects Versions: 1.0
> Reporter: S.W.
>
> I have the following use-case: I created a software-guide with docbook and in
> the appendix I need to include a long license text. I have the license text
> in another docbook-file. It's possible that the license text needs to be
> referenced in several documents. As I don't want to copy & paste the license
> text in the main document, I tried to include it by using the xi:include
> mechanism. At the end of the docbook (but before the </book> tag of course),
> I inserted the following line:
> <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"; href="license.xml" />
> After including the license text with xi:include, I started the ant-build to
> create html and pdf-documents. But the content of the included docbook-file
> isn't included in the html-output and the pdf-file wasn't created at all.
> The message on the console at the pdf-target is:
> [java] xi:include encountered in book, but no template matches.
> And at the html-target:
> [java] No template matches xi:include in book.
> I suggest that DBF should support xi:include, because in my opinion it's an
> important feature for creating modular documents.
> Kind regards
> Steve
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
