The first step for getting something like conrefs is to raise it with the
DocBook Technical Committee. Please file an RFE in the DocBook project on
SourceForge. That will get it onto the TC agenda.
Bob Stayton
Sagehill Enterprises
[EMAIL PROTECTED]
----- Original Message -----
From: "Peter Desjardins" <[EMAIL PROTECTED]>
To: "Barton Wright" <[EMAIL PROTECTED]>
Cc: "Johnson, Eric" <[EMAIL PROTECTED]>; <[email protected]>;
<[EMAIL PROTECTED]>
Sent: Friday, May 09, 2008 1:35 PM
Subject: Re: [docbook-apps] RE: [docbook] RE: [docbook-apps] db 5 and Dita
anyone?
On Fri, May 9, 2008 at 4:08 PM, Barton Wright
<[EMAIL PROTECTED]> wrote:
Another +1 for a non-xinclude conref feature.
No one talks about the hidden cost of xincludes, which is that they are
expensive in terms of the time they take in a large Java-based doc build
process. The more xincludes our doc set accrues, the longer the doc build
takes.
This is the biggest problem I have encountered with DocBook. I've
achieved whatever content reuse I've needed so far using xincludes and
xpointer. I posted the permutations that I find useful here:
http://wiki.docbook.org/topic/DocBookCookbook
But they only work with xmllint.
My experience with xincludes is that they resolve very quickly,
though. Especially after I configured an XML catalog for xmllint, it
resolves my intricate web of xincludes in seconds. Maybe the
difference is that you are using a Java tool to resolve them?
I would gladly give up the xincludes for a DocBook content sharing
feature.
Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
