Rick Lansky wrote: > > Perhaps if I help you understand what we are doing you could this sort > of functionality?
Sure. > We are using stylesheets as a way to provide document validation and > updating. The xincludes are not an issue for the validation, but they > are for the updating. For example, we have some xincludes in a document > that are there as part of a template which we wish to make part of the > document (by cutting and pasting). But we have other sections that we > never wish to update, things such as glossaries--when the glossary file > gets updated, we want the documents which include the glossary to > reflect this. The problem is that when we run a stylesheet that updates > the document (one such stylesheet is used to make sure that every > element in the document has a unique ID tag), the expansion of the > xincludes means that the glossary will no longer be updated automatically. > > I understand that this could also be done using Java DocumentHooks. But > we already use these stylesheets elsewhere in out process, outside of > XMLMind. Applying the stylesheets through XMLMind results in less code > repetition and it ensures that the same results are achieved no matter > how the document is processed. OK, we'll add an attribute to the <copyDocument> process command element which will allow you to save a copy of the document being edited where XIncludes or entity references or both are not expanded. Note that copies of the XIncluded documents or referenced external entities will not be saved in the temporary directory created by the process command. But from what I have undesrtood, this should not annoy you.
