The solution proposed by Claus Rasmussen is actually perfect for us (proxy file) .
---------------------------------------- Davy Toch wrote: > > The solution we currently use to avoid that XInclude/parse=\"text\" > sections are replaced by the actual content is to have a convention on > where to store all files included with XInclude/parse=\"text\", e.g. in a > folder 'src' relative to current DocBook document. > > The person editing the DocBook document must then: > 1) don't have the 'src' folder locally > 2) temporarily rename the 'src' folder locally > > This way, opening the DocBook document will give errors regarding > XInclude/parse=\"text\", but this allows to modify the DocBook > document without the risk of replacing the XInclude/parse=\"text\" > sections with the actual content. I know it's not ideal, but at > least this allows to keep the DocBook document modular. > > Question : isn't there a way in XXE to force XInclude/parse=\"text\" > sections not being resolved, even when the file it points to exists? > This way, the person editing the DocBook document wouldn't need to > perform 1) or 2). Currently, there is no way to do this. Even if this feature was supported, unless you use a schema where xi:include has been declared as being a first class element, your document would be *structurally* *invalid*. And working on structurally invalid documents (red icon) is really not comfortable in XXE. XXE has been designed to support modular documents, where the module is an element and absolutely not a piece of text. Why don't you use elements? Even very fine-grained elements such a DocBook phrase or XHTML span (see http://www.xmlmind.com/xmleditor/_distrib/doc/user/tutorial_modular_document.html#extensive_copy_as_reference). Now if you like many features of XXE but, neverthless, absolutely need XInclude/parse=\"text\" or general support of entities or any other feature not supported by XXE, you should really consider using another XML editor. No offense intended: I just hate to make you loose your time with our product. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.xmlmind.com/pipermail/xmleditor-support/attachments/20060410/fb75fa15/attachment.htm
