Hello everybody, I would like to react on a message from April this year, where catalog usage in resolving XIncludes hrefs is discussed:
> Barbara Estes wrote: > >/ I updated standard XXE-Editor from version 2.7 to 3.2. I had edited the > />/ XXE-Editor catalog previously to rewrite URI's for use with xi:included > />/ files. I edited the catalog with the new version to include my rewrite > />/ URI paths but it is not happening. It is throwing errors saying the > />/ path cannot be found. > />/ > />/ After the standard rewriteURI that comes in the catalog (shown below), I > />/ added the following: > />/ <rewriteURI uriStartString="xxe-config:" rewritePrefix="." /> > />/ <rewriteURI uriStartString="file:///core/" <file:///core/%22> > />/ rewritePrefix="file:///E:/wip/core/help/" <file:///E:/wip/core/help/%22> > /> > />/ <rewriteURI uriStartString="file:///gen/" <file:///gen/%22> > />/ rewritePrefix="file:///E:/wip/gen/help/" <file:///E:/wip/gen/help/%22> /> > />/ > />/ When I load the file in XXE-Editor, I get the following warning message: > />/ /chapter/sect1/xi:include: > />/ cannot load file "\core\generic\genericText.xml": > />/ \core\generic\genericText.xml (The system cannot find the path specified) > />/ > />/ In the file, the xi:include looks like this: > />/ > />/ <xi:include href="file:///core/generic/genericText.xml" > <file:///core/generic/genericText.xml%22> > />/ xpointer="genericText_configuration" > />/ xmlns:xi="http://www.w3.org/2001/XInclude"; > <http://www.w3.org/2001/XInclude%22>> > />/ </xi:include> > />/ > />/ So why did this work before, but will not work now. I can't figure it > out. > />/ > / > What you did is OK, and the XML Catalog works fine in XXE, but starting > from version V2.8 Patch 1 (November 29, 2004), *xi:includes* are no > longer XML Catalog enabled. (Yes, this is a regression.) > > Why? > > - "File|Save As" cannot handle modular documents where an XML catalog is > used to resolve the locations found in the href attribute of xi:include. > How is the "Save as" working? When I tried to save modular document with this command, it saves unexpanded <xi:include> elements normally, which is expected behaviour. I can imagine, that when resolving the includes (for document rendering in the editor), catalog could be used. Anyway, the included parts are not directly editable. When saving the document, original <xi:include> elements could be saved again (catalog-unresolved), so where is the problem with "Save as"? > - xi:includes are supposed to be used *internally* by XXE to create > modular documents. In such case, the fact that xi:includes are not XML > Catalog enabled is not a problem. Yes, but catalog resolving makes modularity far more powerful. I know that inserting <xi:include> by commands Paste as reference available in XXE now provide no mechanism how to insert arbitrary XInclude. But one could suppose that there are also other XML file sources with XIncludes. Not all documents are created using XXE. Best regards Tomas Hajek -- _______________________________________________________________________ Tomas Hajek /_________/ Design engineer / ___ __ Integrated Circuits for Car Radio Applications /\ ( / / / /__) \/ / / / /_/ STMicroelectronics IBC Building E-mail: tomas.hajek at st.com Pobrezni 3 Work : +420 222 336 137 186 00 Praha 8 Tina : 139 6137 Czech Republic Fax : +420 222 336 116 _______________________________________________________________________ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.xmlmind.com/pipermail/xmleditor-support/attachments/20061006/4f96a15b/attachment.htm
