upCast RT 7.1.3

upCast RT 7.1.3 is one of the most comprehensive tools which can enable you to use Microsoft Word as an authoring application for XML documents.

Take advantage of the widespread availability and familiar user interface of Word or any other RTF savvy office application for structured document authoring. upCast offers a cost-effective way to reuse existing tools for gaining all the benefits of a standardized markup language: XML.

Major Features:

1. Import formats
   • RTF documents conforming to the RTF specification 1.8 (including style info)
   • Word binary documents (using WordLink; only when running on Windows platform with Word installed)
   • Any well-formed XML document (no style info)
2. Processing features
   • Run Upcast Processing Language (UPL) code on documents
   • Transform documents using XSLT (XSLT 1: Xalan, XSLT 2: Saxon-B)
   • Integrate external tools via commandline call
   • Create complex, nested groupings using UPL and the Grouper module
   • Create markup based on regular expressions, even across element boundaries
   • Create markup based on style information
   • Validate against XML DTD, XML Schema and Relax NG
   • In-place transformations, attach custom data to any node
   • List detection heuristics, supporting nested lists
   • Create sub-processing pipelines
   • Perform detailed logging, handle processing errors
   • Sophisticated handling of embedded and referenced images
3. Export formats
   • XML (upCast DTD)
   • XML (internal tree format)
   • RTF (Version 1.6)
   • CSS
4. Interfaces
   • GUI based on Swing
   • Commandline
   • Java API
     

Enhancements:

• New Features
• • UPL: New function set-var() to be able to set variables with dynamically calculated names
  • UPL: New function parse-numbering() to convert a (possibly multi-level) numbering string like "(iv)" or "I-A-3.d)" into a list of integers indicating the number index of each level like {4} or {1,1,3,4}
  • RTF Exporter: new option to specify handling of missing images or images in an unsupported or unrecognized format
• Changes & Improvements
• • Documentation: markup-regex(): Add notice that with a repeating group, only the last instance is handled by markup-regex() as described in javadoc for java.util.regex.Pattern.
  • Documentation: markup-regex(): Add example for parsing out heading numbers by levels.
  • Documentation: markup-regex(): Add example for custom-replace function.
  • When log file path is "-", the console logger is used. You can therefore request output to the console (instead of to a file) by specifying "-Dde.infinityloop.application.logfile=-" on invoking Java.
  • You can now set specifically configured logging filter on the external logger. This can be done programmatically via the Java API or use the system property de.infinityloop.logfilterspec for testing within the GUI.
  • Completely revamped logging filter configuration in the UI. This includes modules, pipelines, preferences and Log Window. In each of these places, you now can specify a fully customizable log filter spec string. This required a change of the pipeline storage format to V4. Format converters from earlier pipeline versions have been implemented and work silently in the background on loading a pipeline file. The UI has changed to an editable combo box with the plain log levels available as pre-defined choices. However, you can write into the edit field and set up any filter spec you like. For syntax, see documentation.
  • Log Window was line-wrapping, which is not desirable. Now, a horizontal scroll bar is shown as needed.
• Fixes
• • Re-setting the WordLink executable path dynamically during program execution was not picked up by the RTF Exporter
  • RunPipeline did not work at all times
  • several corrections in the documentation
  • Pipeline Settings > License: Alt modifier did not work to force relative path
  • Documentation generated by the pipeline doc generator did not warn on missing self-containedness when license setting was "inherit"
  • Calling replace-with-text() does not work on a last sibling node in that the text to replace it with was not inserted, although the node to replace was deleted.
  • UPL: fixed bug in checking signatures of functions with variable argument lists
  • Exporting Ant source or Java source did not report any errors during that op, but showed "successful" message instead.
  • Log window: Disable filter entry field when showing log from file where filtering is not possible

Requirements:

• Java 5 runtime environment or later
• 512 MB of free RAM (recommended)
• Environment compatible and running with Xerces 2.9 or later (Xerces 2.9.1 is delivered with upCast binary)