I agree with Ron's simple summary: use XInclude for large chunks of
text and entities for small. The basic problem is that there's no
elegant way to change bits of the XIncluded text based on the context
of its inclusion:
* XML files + multiple catalog sets are awkward and not supported well
in
My biggest problem with Xinclude is the duplicate ID if a piece of text
is included twice etc. Would it be possible to reset an ID of an
Xincluded test on the Xinclude statement with an attribute, e.g.
xi:include href=venn.xml ***newid=qwerty***
xmlns:xi=http://www.w3.org/2001/XInclude;
We use an XSLT script to add the sortas attribute to the documents before we
turn it over to the Japanese localizers, since some of the translation memory
tools they use do not allow them to modify the structure of the document (and
the attributes attached to an element is considered part of
On 27 sept. 10, at 23:21, Rowland, Larry wrote:
We use an XSLT script to add the sortas attribute to the documents before we
turn it over to the Japanese localizers, since some of the translation memory
tools they use do not allow them to modify the structure of the document (and
the
We have an Ant target that packages up the source files for localization. A
number of scripts are run in the process, but the process of adding sortas
attributes is this:
1) The first step is handled in Ant and is to replace all the ampersands in
the files with a token value using
Another alternative is to set up your environment to make sortas a required
attribute rather than optional. As long as it is empty, most transforms ignore
it. You would need to test and make sure. It does make the file noisier for
the author in a language that does not depend on the
Ron Catterall [mailto:r...@catterall.net] wrote:
My biggest problem with Xinclude is the duplicate ID if a piece of text
is included twice etc. Would it be possible to reset an ID of an
Xincluded test on the Xinclude statement with an attribute, e.g.
xi:include href=venn.xml
XInclude is not part of DocBook. I think you'd need to go through the W3C to
propose enhancements to it. That
said, your solution only solves part of the problem, I think. What about IDs
on elements that are inside
the main XIncluded element? And what about nested XIncludes?
Hm... For
