We are having problems maintaining the old "C++" version  of the program "Xalan" for XSL 1.0  processing. This program is triggered through "xychange" when the command line does NOT contain the "-xsl2" option, as we use the default behavior to preserve XSL 1.0 processing.  Since it is a program, it can also be used in scripting by calling "Xalan" directly. In my opinion, no one should be using XSL 1.0 at this point since it is has been far exceeded by 2.0/3.0 with very awkward work arounds for very common transformations and other transformations that are just not possible. The functionality has been replaced by the program "xppxslt",  which uses the Saxon parser, but requires Java.  Saxon is upwards compatible and XSL 1.0 transforms will run as is.

If you are doing XSL processing on XPP, I would like to know:

1. Are you installing Java and running with XSL 2.0+ functionality?

2. Are you calling the program "Xalan" directly in your scripts

3. Can XPP change the requirements to state that you need Java if you are doing any XSL processing at all?

With this in mind, in a future release we would:

1. Stop delivering "Xalan", but leave it on any system so custom scripts would still function.

2. Change "xychange" to automatically use the xppxslt/Saxon processor with or without the "-xslt2" option.

3. Change the requirements documentation to state that Java is required if doing any XSL processing. NOTE: Java is already required if using SVG or the 'xppcompare' program.

Thanks

Steve Piercey

RWS/SDL/XyEnterprise/Xyvision