However, in my *transform command*, the stylesheet does define two
prefixes, '*xsl*' and '*geov*'; it behaves as if only '*xsl*' had been
defined:
<cfg:command name="setDefaultItem">
<cfg:macro trace="true">
<cfg:sequence>
<cfg:get expression="serialize($implicitElement)"/>
/<cfg:transform source="%_">
<xsl:stylesheet version="1.0"
xmlns:geov="http://www.cggveritas.com/geovation/module/2.0";
xmlns:xsl="http://www.w3.org/1999/XSL/Transform";>
/
Surely some obvious tiny thing that I fail to see... ?
No, it's just a bug in XXE, which will be fixed in next release.
Dear M. Shafie,
There is no software without bug and no bug without software... We
implemented this feature differently in our plugin, so we can live
without transform command for now. However, we are quite familiar with
XSL, so the ability to use it in our plugin gives us a great potential
for improvement; the bug-fix will be eventually welcome...
Something completely different related to ID-generation; in our XML
dialect, all elements need to be uniquely identified by XML IDs; these
IDs are used internally, so we want to avoid at all price our authors to
bother about them.
So, we added the *generateIds="true"* property to the
*newElementContent* element in our .xxe file. And this works fine. We
have a couple of additional questions to definitely improve ID's
management for our XXE plugin:
1)*[minor]* Is there a way to control how these IDs are generated ?
(e.g. providing a common prefix or so)
2) *[important]* If we write templates for some elements, is there a way
to add automatically generated IDs in the generated elements, i.e. a
kind of equivalent to the XSL "*generate-id(.)*" function call ? So
far all we could do is assign erroneous IDs, e.g. id="???" to the new
elements (so, we removed the use of templates since we cannot end-up
with invalid files).
3) *[vital] *The copy/paste feature of XXE is really great; is there is
a way to "override" (this is probably a wrong terminology) it to force
IDs of new elements to be re-generated ? (otherwise we end-up with
duplcate IDs which has very bad consequences in our case). What we had
in mind is a mechanism which would allow us to automatically change
copied elements.
Many thanks for your advises, and congratulations for your excellent
product,
Philippe.
--
XMLmind XML Editor Support List
[email protected]
http://www.xmlmind.com/mailman/listinfo/xmleditor-support
