Philippe Nobili wrote: > > After some thoughts on how we could best succeed in maintaining several > conversion layers and switching from one to another dynamically , we > came to the conclusion that the best might be to use the "parameter set" > feature that has been added in XMLMind 4.3. > > The idea would be, instead of having several DocBook customizations, to > manually write several parameter sets defined in our XXE DocBook > customization and swtich from one to another before conversion. The more > complex XSLT stylesheet customization itself (for example for PDF) is > loaded from the parameter set using the docb.toPS.transform property > (i.e. <property name="docb.toPS.transform" url="true">xxxxxxxx). > > We would like to take your advise before we start: > > 1) Does the above idea makes sense ? (it is so easy to do that we have > doubts...) > > 2) How can we use the parameter sets from the command line utility > *convertdoc* ? > > The latest is very important to us because we intensively use your (very > convenient) command line utility to publish documents nightly in batch > mode (acitivity reports, software documentation updates, etc etc..). > Having strictly the same results from either route (batch vs > interactive) is very important. >
* No, what you describe cannot work. A named parameter set cannot contain: <property name="docb.toPS.transform" url="true"> because this is not a XSLT style sheet parameter. The ``load/save parameter'' sets feature of XXE v4.3 is just a convenient way to avoid a user from retyping XSLT style sheet parameter values in the "Change Document Conversion Parameters" dialog box. (http://www.xmlmind.com/xmleditor/_distrib/doc/help/com.xmlmind.xmleditapp.kit.part.ConversionParametersEditor.html) Note that a named parameter set cannot be selected or activated. A user can just ``load'' it, which means: erase the current contents of the "Change Document Conversion Parameters" dialog box and instead copy the contents of the loaded parameter set. * convertdoc (http://www.xmlmind.com/xmleditor/_distrib/doc/commands/convertdoc.html) is XXE without a GUI. This command line utility uses exactly the same configuration files, add-ons, user preferences, etc, as the interactive, graphical, XXE. convertdoc currently has no option which allows to ``load'' a named parameter set. * You really need to create a 100% custom replacement for xslMenu.incl. Doing this is *not* a lot of work (fell free to copy the stock xslMenu.incl and heavily modify it). Doing this is clean, reliable and easy to maintain. Easier to maintain than attempting to heavily parameterize the stock xslMenu.incl. Pavel ?kop?k did that successfully in the past and it worked fine for him (thanks Pavel for your feedback!).
