Denis Bradford wrote: > I'm seeing a couple of problems with XMLMind 3.6.0 and 3.6.1, when > editing DocBook content with xincludes. XMLMind doc has some caveats > about using xincludes (such as the restriction against editing in > place), but these seem like bugs:
This certainly makes XMLmind XML Editor uncomfortable to use in some cases, but you cannot call these bugs (bug=error in logic). Such problems are listed in our User's Wish List http://www.xmlmind.com/xmleditor/wish_list.html in the "Annoying Behaviors" section. > * Can't cut (CTRL+X) text that contains an xinclude. For example: > > <para>There are important differences in environment and practices that > you should be aware of if you are upgrading from a x.x version > to a <xi:include href="../common/replaceable.xml" > xmlns:xi="http://www.w3.org/2001/XInclude" xpointer="nextver"/> > version.</para> > > Note that in my case, the xinclude resolves to <phrase > id="nextver">5.0</phrase>, and is represented in the XMLMind editor that > way. I can cut the entire para or the phrase element, but not a > selection that includes both text and the phrase. > For example, if I select content from "upgrading" to the last "version", > CTRL+X has no effect. Hard to fix (anything related to the text selection is hard to fix or improve). We will do our best to improve this. But don't hold your breath: I cannot give you my word that we'll succeed. > * Can't use DocBook menu table operations. For example, take this sample: > <informaltable> > <tgroup cols="1"> > <thead> > <row> > <entry align="center">Version <xi:include > href="../common/replaceable.xml" > xmlns:xi="http://www.w3.org/2001/XInclude" xpointer="boylston"/></entry> > </row> > </thead> > > <tbody> > <row> > <entry>PATH is not set during install.</entry> > </row> > </tbody> > </tgroup> > </informaltable> > > With this sample table, all table commands in the DocBook > Column, Row, > and Cell submenus are greyed out (although I can use normal keyboard > commands on selected rows and cells). If I remove the xinclude, the > DocBook menu commands are enabled and work normally. > We'll do our best to improve the behavior of XXE in this case.

