Robert R. wrote:
... might you point me to some good ways to debug complex/deeply nested XSL scripts. I'm aware that XMLmind can edit them - so far so good. But finding the very obscure issues in existing scripts is eluding me.
All the XSLT developers I know use oXygen XML Editor for doing this and seem to be quite happy with it.
XMLmind XML Editor has been designed to edit prose, not code. It's not adapted at all to develop or debug XSLT stylesheets.
For our own XSLT stylesheets, we just use Emacs and its very good nxml-mode. XSLT 1.0 support is built-in. We have an XSLT 2.0 RELAX NG Schema (courtesy of RenderX folks if my memory serves me well) to add XSLT 2.0 support to nxml-mode.
This being said, we never develop "complex/deeply nested XSL scripts" here at XMLmind. Our XSLT stylesheets may be large, but they are always simple. I mean, they are really "stylesheets", not "scripts".
When an XML document needs complex processing (e.g. DITA conref, filtering, keyref, etc, or DocBook 5.1 "realization" of an assembly), we prefer to implement this as a pre-processing step written in Java which modifies the XML document in place. This is the key to keep our XSLT stylesheets as simple as possible.
-- XMLmind XML Editor Support List xmleditor-support@xmlmind.com http://www.xmlmind.com/mailman/listinfo/xmleditor-support
