You can now distribute your translation rules across a series of translation tables which will be searched sequentially. This allows, for example, factoring of commonly used translation rules into one or more tables which can be shared across a number of web sites.

Translation of entities can be specified via a table at the root level of each translation table. This table maps entity names to entity values. Hence translation of entities can also be factored across multiple translation tables. (Previously entities had to be translated by a script.)

You can specify whether TranslateTree() translates the root node of the parse tree rather than just the child nodes (the previous default behaviour).

The names of the special entries in translation tables (e.g. “_any”) are now defined by constants in the xmltr table (which means you can easily change them if you have a need to do so).

If you wish to preserve the rule cache between calls to TranslateTree() (which can speed up translation of lots of short xml documents) you need to provide your own rule cache table as an address parameter to TranslateTree(). (Previously this was controlled by a boolean parameter to TranslateTree().)

You can no longer provide scripts at the root level of the translation rule table which override built in scripts for finding or processing translation rules. If you want to override the built in scripts, you can provide overriding scripts as parameters to TranslateTree().

The documentation has been modified to reflect the above changes. New xmltr howtos have been added focussing on specific topics.

The documentation is now more extensive. New areas covered include the new features listed below as well as: (i) translation of entities and (ii) many more detailed descriptions of individual scripts in the script summary.

You can now supply default translation rules which will be used if no ordinary or wildcard rule matches a tag pattern.

You can use the “sameas:” prefix in a rule to specify that one tag pattern use the same translation rule as another tag pattern.

You can provide scripts at the root level of the translation rule table which override built in scripts for finding or processing translation rules.

You can preserve the rule cache between calls to TranslateTree() which can speed up translation of lots of short xml documents.