In order to do XSLT processing with schema PSVI information (in
particular, attribute defaults), I have created a little SAX parser
factory for Xerces that turns on all the schema stuff. I can then use
this with, for example, Saxon, to do schema-aware XSLT (for example,
DITA-aware processing that depends on the class= attribute).
I'm trying to figure out how to integrate this parser with Oxygen so
that I can run my transforms from within Oxygen.
I tried adding the necessary JVM arg to the oxygen INI file adding the
library with the parser factory class to the classpath, but it didn't
seem to do anything--I suspect that the XSLT process needs it's own JVM
args spec, but the only thing I saw as a place to specify a transformer
factory (I can do if I have to but then I'm looked into a specific
version of Saxon, for example).
Have I missed something or am I going about this the wrong way?
Thanks,
Eliot
--
W. Eliot Kimber
Professional Services
Innodata Isogen
8500 N. Mopac, Suite 402
Austin, TX 78759
(214) 954-5198
ekimber(a)innodata-isogen.com
www.innodata-isogen.com
package com.innodata.xerces;
import javax.xml.parsers.ParserConfigurationException;
import org.apache.xerces.jaxp.SAXParserFactoryImpl;
import org.xml.sax.SAXNotRecognizedException;
import org.xml.sax.SAXNotSupportedException;
public class ValidatingSAXParserFactory extends SAXParserFactoryImpl {
public ValidatingSAXParserFactory() throws SAXNotRecognizedException, SAXNotSupportedException, ParserConfigurationException {
this.setFeature("http://xml.org/sax/features/validation", true);
this.setFeature("http://apache.org/xml/features/validation/dynamic", true);
this.setFeature("http://apache.org/xml/features/validation/schema", true);
this.setFeature("http://apache.org/xml/features/validation/schema/normalized-value", true);
this.setFeature("http://xml.org/sax/features/namespace-prefixes", true);
}
}
Dear list members,
For the Windows install kit of oXygen we consider replacing the Java
help bundle which is opened by pressing the F1 key or by going to menu
Help -> Help with a native Windows bundle (a CHM file) with the same
content. Of course the F1 key will continue to open the bundle at a
specific help page. We would like to remove the Java help jar file from
the Windows installation and replace it with the CHM file instead of
including both the jar file and the CHM file. This avoids increasing the
size of the Windows install kit. Without the Java help jar file the
Dynamic Help View does not work any more as it loads the help pages that
it must display from this jar file. Do you think that removing the
Dynamic Help View from oXygen on Windows is an acceptable price for
replacing the Java help dialog with a native Windows help package?
Regards,
Sorin
http://www.oxygenxml.com
