Dear Christian, Thanks! We fixed this issue today and it will be available in 11.1. Version 11.1 is planned for December but we probably will make a beta available a few weeks before the release.
Best Regards, George -- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com Christian Wittern wrote: > Dear George, > > George Cristian Bina wrote: >> Hi Christian, >> >> There is no support for using variables for the input bindings, sorry >> about the documentation/feature missmatch. We already fixed this in >> the current development adding support for editor variables when you >> specify the input bindings. >> Actually the XProc scenarios support will be improved in oXygen 11.1 >> as we already added support for specifying parameters and options. > I am looking forward to this, since the current way makes XProc more or > less unusable. Even if I call a XProc scenario from an XML file, there > is no way that this scenario could pick up the current XML file as the > input file. > >> >> The ${cfn} stands for current file name and it is computed depending >> on whatever the current file is. If the selected editor is an XProc >> file then that will contain that file name. Please note that one of >> the interesting improvements in version 11 was that any type of >> scenario can be set for any file so you can set an XProc scenario for >> an XML file and then if you execute the transformation with that file >> as the current file then the ${cfn} variable will be expanded to that >> file filename. > Right, this is what I would expect from the way the other scenarios > behave. But I experience the following: > > I have a XProc scenario called md-db2xml.xpl. In the input port, of > that file, I am setting tthe XML file to JY006.xml. Now I have that > file (JY006.xml) open in the editor and configure a XProc scenario for > this file. In the output port, I set the file to > file:///tmp/{$cfn}-tei.xml (and always forget to press 'commit' before > pressing 'OK' -- this seems quite counterintuitive and different from > other dialogs, is this really necessary? ). The resulting file I am > expecting should be JY006-tei.xml in /tmp. However, I do get > /tmp/md-db2xml-tei.xml, which is annoying and unexpected. > So I guess I have to wait for the next release to really start using > this feature. > > All the best, > > Christian >> >> Best Regards, >> George > > _______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
