Thank you for your quick response. I hadn't thought of your solution (of course). In the meantime I've found an XSLT workaround, but I'll consider if your solution is more convenient. You might consider referring to the 'Extensive use of the "Copy as Reference" command' text on http://www.xmlmind.com/xmleditor/limitations.html.
>From your response I guess that I do not belong to the target audience of your XML editor. In that case I'll keep looking around for better alternatives (no offense intended). Louis Hussein Shafie <hussein at xmlmind.com> 2006-12-11 17:14 Please respond to "xmleditor-support at xmlmind.com" <xmleditor-support at xmlmind.com> To Louis.Strous at consul.com cc "xmleditor-support at xmlmind.com" <xmleditor-support at xmlmind.com> Subject Re: [XXE] Request: make XMLmind XML editor support entities that stand for fixed text I agree with the fact that support of XML variables is really needed, but what's wrong with what is described in "Extensive use of the "Copy as Reference" command"? http://www.xmlmind.com/xmleditor/_distrib/doc/user/tutorial_modular_document.html#extensive_copy_as_reference Wrap your ``XML variables'' in HTML span or DocBook phrase elements. Give each variable a unique ID. Declare and *document* these variables in a companion ``glossary document''. Then simply "Copy as Reference" an ``XML variables'' from the ``glossary document'' and Paste it in the document you are editing. By doing this: [1] You can create, document, maintain, etc, your XML variables using XXE itself. Something you cannot do with references to entities declared in the DTD internal subset. [2] You can easily share your XML variables between different documents. Something you cannot do with references to entities declared in the DTD internal subset. XXE has always been designed as a topic editor (long before DITA was invented). While references to entities are great when you work at the physical level with a bunch of XML files and a text editor, we don't see how references to entities fit in a world of loosely coupled topics conforming to a one or more schemas. This to say that we'll probably never implement your request (no offense intended). -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.xmlmind.com/pipermail/xmleditor-support/attachments/20061211/67324cfa/attachment.htm
