I'm using an old Xalan-J processor. I have the Stylus Studio processor option set to Xalan-J, and all the classpath options point to some jars for my old Xalan parser, followed by Stylus Studio's classpath, like this:
Subject:Problem with xsl:comment Author:Peta Bowyer Date:31 Aug 2004 03:00 PM
Thanks for the thought Ivan, but that's not it. I am using Preview Text.
I've got the same xsl as in your screen capture, but my HTML just doesn't show the comment. I assume this is because I'm using a different Xalan proccessor from the one provided in Stylus Studio. I will upgrade to the latest parser at some stage, but I can't do it yet.
My old xalan processor handles the comments ok at the command line, so I have put my old xalan first on the classpath before Stylus Studio's $classpath. Shouldn't that invoke the old parser rather than the Xalan-J provided with Stylus Studio? Or am I barking up completely the wrong tree?