DITA Compare 8.0.0 introduced comparison of MathML. This feature allows users of MathML to produce a valid, renderable comparison output if MathML inputs are valid and renderable.
How it Works
Using XML Compare's MathML comparison, users will get an output with changes highlighted using the
mathbackground attribute. Delta information is also retained if further processing is required. Note that as we are using
mathbackground to display change, this may interfere with and overwrite your own use of
If the comparison finds a
<math> element (in the
namespace) in an input document MathML comparison is switched on automatically. There is also an option to switch MathML comparison off if you do not require it.
Whitespace is normalised as per instructions in the MathML specification i.e. space between elements is removed, and space within elements is normalised (leading & trailing spaces removed, spaces between words collapsed to a single space).
We have found in testing that Firefox is the best browser for rendering MathML.
We have provided three levels of granularity of results. To demonstrate the granularity, let's use what should be a familiar formula to many people:
...and make some tweaks...
Inline mode will mark changes at the lowest level (ie. for MathML elements mi, mo, mn) as possible. This is the default mode. We achieve this by wrapping changes in an
<mrow> to keep the number of required arguments in certain elements, e.g.
Using our example, an inline result will look as such:
Note for example when changing b2 to b3, the change has been wrapped in an
<mrow> to keep
<msubsup>'s required arguments correct.
If we cannot display the changes inline, we fall back to producing a "detailed adjacent" view to ensure the output is valid and renderable.
This mode is a side-by-side view that duplicates the inputs, with individual changes highlighted. For readability, we have added a grey background and a small gap between the two formulas.
Here's what our example looks like using this mode:
Adjacent mode is the simplest view and just duplicates the two inputs to give a "before" and "after" view.
MathML has been implemented as an M.V.P to garner feedback from customers. As such, there are various limitations to it:
- User will have to specify catalog for the MathML.
- We are currently only handling Presentation Markup.
- Inline comparison will only mark inline changes to
- Our comparison presumes your MathML inputs are valid MathML. If they aren't, you may get incorrect results. We may consider validation of MathML inputs in a future release. This would allow us to provide information when inputs aren't valid, and suggest how to fix the errors.
- We are currently ignoring changes to MathML attributes and resolving by picking the B version.