Hello, Please see my answers below. Khaled Aly wrote:
- There probably should be a way to validate *.xsl files since there is an XSL (1.0) DTD. When I try to validate I get an error msg that JAXP isn't installed.
"The transformer JAXP is not present! Please install it in the folder: file:/C:/Program Files/Oxygen XML Editor 8.2/lib/"
That error message occurs when you select JAXP as the validation engine in Options -> Preferences -> XML -> XSLT/FO/XQuery -> XSLT but the JAXP engine is not set correctly. Setting a JAXP engine implies setting the name of the main Java class of the engine in the Value field in the section JAXP XSLT Transformer of the preferences page mentioned above and adding the jar file of the engine in the folder specified in the error message. As Lars mentioned oXygen validates XSLT stylesheets with the engine set in "XSLT 1.0 validate with". XSLT validation implies more than checking the syntax of the stylesheet against a DTD and this is why an XSLT transformer must be set as validation engine.
- Anyone has links to multiple output extension XSL elements when Saxon or Xalan are used for transformation to HTML (analogous to the <xt:document)?
In XSLT 2.0 you have the xsl:result-document element. If you must use XSLT 1.0 please read about the Saxon output extension: http://saxon.sourceforge.net/saxon6.5.5/extensions.html#saxon:output and about the Xalan redirect extensions: http://xml.apache.org/xalan-j/extensionslib.html#redirect
- Soren: any plans of introducing a "tagged" view in the next release, in addition to "Text" and "Grid"?
I am not sure what you mean by tagged view. I think the Text mode of the XML editor provides a tagged view of an XML document. The next release will introduce a CSS-driven tagless editor which you can try in the oXygen 9 beta version announced on this list by George several days ago: http://www.oxygenxml.com/pipermail/oxygen-user/2007-September/001323.html
- I'm not familiar with Eclipse and I currently use the standalone oXygen version. But I believe Eclipse must have Ant installed, so would this be of help for editing and executing Ant build files for DITA on the same platform? I'm not sure, otherwise, if Oxygen built-in transformers (e.g. Saxon 6.5.5) can be use with a 'standalone' Ant version, or would one in this case need to install the processor separately?
Yes, Eclipse comes with a built-in Ant plugin with support for editing build files (an Ant editor with syntax highlight, content completion for Ant elements and attributes) and for executing them. If you want to use Ant as a standalone tool you can apply a stylesheet with Xalan extensions from the build script without any additional configuration as Ant comes with Xalan as the engine which executes the "xslt" / "style" Ant element. If you want to use Saxon extensions you have to add the Saxon 6.5 jar file to the folder [Ant-install-folder]/lib and to specify the name of the Saxon's implementation of javax.xml.transform.TransformerFactory (that is com.icl.saxon.TransformerFactoryImpl) in the "factory" child element of the "xslt" element of your Ant build file. For calling Ant from oXygen as external tool please read the following section of the oXygen user manual which includes a complete example: http://www.oxygenxml.com/doc/ug-standalone/integrating-external-tools.html#i... Regards, Sorin