Access to saxon -explain
Dear, Is there a simple way to have access to the result of the -explain option from inside OxygenXML ? Regards, Xmlizer
Hello, You can set a Saxon 9 option that is not available in the Preferences dialog in Preferences / XML / XSLT-FO-XQuery / XSLT / Saxon / Saxon-B/SA only if you define Saxon 9 as an external XSLT processor from Preferences / XML / XSLT-FO-XQuery / Custom Engines and set the external processor in the transformation scenario: http://www.oxygenxml.com/doc/ug-oxygen/configuring-custom-xslt-processors.ht... The command line of the external processor should be: java -cp lib/saxon9.jar net.sf.saxon.Transform -s:${xml} -xsl:${xsl} -o:${out} -explain The output of the XSLT transformation will be saved to the output file set in the scenario (the ${out} variable). The output generated by the -explain option will be displayed in the Oxygen Warnings view. Regards, Sorin mozer wrote:
Dear,
Is there a simple way to have access to the result of the -explain option from inside OxygenXML ?
Regards,
Xmlizer
Hello. We're really liking the OxygenXML product, and we're using it more and more as we develop our structured content. While there is a lot hype on using the XSD format, we frankly find the viewing of it in the windows a bit awkward, and at the risk of sounding old, we would prefer to simply have a DTD format to view or to load into certain tools. I know we can convert DTDs into XSDs with OxygenXML. Is it possible to convert XSDs to DTDs within the OxygenXML? Right now, we're using an external tool for that. Thanks. Shaun - Patrick O. Young Senior Systems/Multi-Disciplined Engineer Content Development & Management Systems Raytheon Network Centric Systems (972) 344-1764 (o) young1@raytheon.com
We're really liking the OxygenXML product, and we're using it more and more as we develop our structured content. While there is a lot hype on using the XSD format, we frankly find the viewing of it in the windows a bit awkward, and at the risk of sounding old, we would prefer to simply have a DTD format to view or to load into certain tools. I know we can convert DTDs into XSDs with OxygenXML. Is it possible to convert XSDs to DTDs within the OxygenXML?
Ha... don't be lame... :) Look up the "garden of eden" style and hand code your schemas... the equivalent of a DTD is really basic and is no problem at all to code. It's really nice and simple... it makes writing schemas a pleasure. -- Andrew Welch http://andrewjwelch.com Kernow: http://kernowforsaxon.sf.net/
Hello, I think hand coding the DTD is not really an option for large schemas. There is no direct way for the conversion but you can generate an XML instance document from each XML Schema using the action Generate Sample XML Files from menu Tools. For generating a DTD from an XML instance document run the actions Learn Structure (Ctrl + Shift + L) and Save Structure (Ctrl + Shift + S) available on the menu Document -> XML Document. Regards, Sorin Andrew Welch wrote:
We're really liking the OxygenXML product, and we're using it more and more as we develop our structured content. While there is a lot hype on using the XSD format, we frankly find the viewing of it in the windows a bit awkward, and at the risk of sounding old, we would prefer to simply have a DTD format to view or to load into certain tools. I know we can convert DTDs into XSDs with OxygenXML. Is it possible to convert XSDs to DTDs within the OxygenXML?
Ha... don't be lame... :)
Look up the "garden of eden" style and hand code your schemas... the equivalent of a DTD is really basic and is no problem at all to code.
It's really nice and simple... it makes writing schemas a pleasure.
I think hand coding the DTD is not really an option for large schemas. "Correct" There is no direct way for the conversion but you can generate an XML instance document from each XML Schema using the action Generate Sample XML Files from menu Tools. For generating a DTD from an XML instance document run the actions Learn Structure (Ctrl + Shift + L) and Save Structure (Ctrl + Shift + S) available on the menu Document -> XML Document. Thanks Sorin. We'll give that a try. Shaun - Patrick O. Young Senior Systems/Multi-Disciplined Engineer Content Development & Management Systems Raytheon Network Centric Systems (972) 344-1764 (o) young1@raytheon.com
participants (4)
-
Andrew Welch -
mozer -
Patrick O Young -
Sorin Ristache