> Thank you for your suggestion. However it's pretty difficult to > implement that: our home-made auto-completion currently requires its > bound list to be sorted alphabetically. > > OK, thank you for the reply; the view you mention help a little bit, we'll use it for now.
We have another question, related to how transformation parameters are
passed to XSLT stylesheets from XXE parameter sets.
Our problem is the following:
+ We have our XSLT transformation running fine from XMLMind (XML to XML)
without changing the default parameters setting
+ In our stylesheets, we however have a couple of transformation
parameters that we can change to fine tune the conversion, for
instance (excerpt from our param.xsl file):
<xsl:param name="coding.for.all.groups" select="0"/>
The parameter is tested during the transformation, eg.g
<xsl:when test="$coding.for.all.groups = 1">......
+ From command line, that's no problem, we can use any XSLT 2.0 engine
(e.g. Saxon-9) and specify coding.for.all.groups=1 to change the default
transformation.
If we want to edit this parameter from XXE ( see capture
setting_coding.jpg), we get an error when processing our XML document:
"
Command execution has failed:
net.sf.trans.XPathexception: Cannot compare xs:string to xs:integer
"
We understand what it means, but do not how to specify the parameter's
value in XXE...then
Many thank again,
Philippe.
<<attachment: philippe_nobili.vcf>>
-- XMLmind XML Editor Support List [email protected] http://www.xmlmind.com/mailman/listinfo/xmleditor-support
