MorganaXProc (Implements XProc 1.0) / Blog: Recent posts

This is a service update with a lot of minor changes under the hood.

The basic new features are:

• New implementation of p:validate-with-relax-ng: Support for option „dtd-id-idref-warnings“ added.
• Reworked handling of XML 1.1.: XML 1.1 documents are now detected before they are handled by an xml-parser, so parsers cannot crush anymore.
• Further improvement of error messages: defaulted names are now visible in error messages.
• Defaulted names are non longer NCNames but constructed as suggested in recommendation. All NCNames are now usable by pipeline authors.
• Improved error messages in p:try when p:group and/or p:catch is missing.
• Introducing test-suite reporter: You can now test your MorganaXProc configuration against the XProc Test Suite. Check out command line interface with no parameters to get a usage hint.

Service release 1 to MorganaXProc 0.95 is released.

Changes:

• Fixing a bug which might lead to a null pointer exception when a file with an unknown content-type is loaded in http-request with scheme "file".
• Fixing a bug which might lead to an inaccessible resource in p:xquery's fn:doc() when documentBaseURI is set to null in MorganaXProc's configuration.
• Fixed spelling in some error messages and getting version information for XQuery processor right.
• Improving error details for xml-syntax exceptions in pipelines and input documents.
• Changing allocation of prefixes for namespaces in p:data’s wrapper, so that „c“ is used for „http://www.w3.org/ns/xproc-step“ even if this namespace is not explicitly used in the pipeline.
• Improving compilation error messages: They now contain line and column in pipeline source, where error occurred.
• Improving runtime error messages: They now contain line and column in pipeline source, where error occurred.
• Improving readability of compilation errors in console.
• Adding method „getMemoryUsed()“ to XProcOutput to deliver info about pipeline’s memory consumption.
• Improving debugging information by introducing timing and memory information into debug reports.