Dear Timothy, It may be a namespace issue. For example, if a DTD specifies a default namespace it may be possible that in oXygen the SVG catalogs are already set and you get the elements in the SVG namespace while in the command line the DTD is not visible and you get the elements in no namespace and thus your XSLT will not match anything and you get only the header. Please note that this is just a wild guess, I can tell more if you provide a sample XML and XSLT. Best Regards, George -- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 5/22/12 3:30 PM, Reaves, Timothy wrote:
I have a stlyesheet I use to clean up SVG files. I have a transofrmation scenario created that uses Saxon 9EE (I have a license for Saxon as well). The transform runs in oXygen and produces the expected output. However, when I run Saxon from the command line, all I get in the output is the XML header. What would cause the command line execution to produce different results to the in-application transformation?
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user