A corrupt MathType object may trigger the following warning from Word during
eXtyles processing:
Word was unable to write some of the embedded objects due to
insufficient memory or disk space.
If the document has MathType equations, the warning may indicate that one or more
of them is corrupt. To work with such a document in eXtyles, the corrupt MathType
equation must be located, deleted, and re-keyed.
One strategy for locating a corrupt equation is the "binary search," in which the
corrupt equation is isolated by a progressive halving of the document. The procedure
for a binary search in a Word document is as follows:
(1) Copy and paste the first half of the document into a new Word document.
(2) Save this new document as an RTF file (saving to RTF triggers the same problem
as eXtyles processing).
(3) If you were able to save the RTF successfully, read (a); if you were not, read
(b):
(a) The half of the document you just saved does not contain the corrupt
equation. Return to step 2 with the second half of the original document.
(b) The half of the document you just saved contains the corrupt equation. Divide
this half of the document in half and return to step 2 until you locate the corrupt
equation.
(4) Once you have isolated the corrupt equation, delete this equation from the
original document and re-key a new equation.
eXtyles Reports a MathType Translation Error-14 during Export
A MathType translation error-14 occurs when an equation has been set up in a
manner that prevents proper conversion from MathType format to MathML. Often,
but not always, this error occurs when an author has incorrectly used superscript
or subscript in part of the equation.
To resolve this problem, each equation associated with the error must be corrected
by hand in the Word document. Search for the following comment in the exported XML
document and note which equation it precedes:
ERROR-14 IN MATHTYPE CONVERSION. PLEASE CORRECT MANUALLY.
The part of the equation causing this error will be missing in the XML version of the
equation when compared against the MathType version. To resolve the problem, correct
the equation in Word with MathType, using MathType operations that are compatible with
MathML. Once the equations have been corrected, the manuscript should export without
error.
Note: MathType 6.5 has an improved MathML translation that reduces the incidence of
these errors significantly. If you are not using version 6.5 of MathType with an eXtyles
XML export, we recommend that you upgrade.
Word Crashes When eXtyles Exports a Document Containing MathType Equations
On rare occasions, when exporting a document containing a large number of MathType
equations, a user will experience a Word crash. This crash is triggered by a bad
interaction between Word and MathType, and it often occurs between the following
stages of export: "checking paragraphs" and "Loading MathType translators."
A workaround has been devised to preclude this interaction. The user should hold
down the shift key when selecting the export option and keep holding the shift key
until eXtyles displays this message box:
This message brought to you in place of a Microsoft Word crash
Once the box is displayed, the user may release the shift key and click OK. The
remainder of the export process will execute without issue.
Double-Clicking on a MathType Equation after an eXtyles Process Is Run Opens a Different Equation
Occasionally, double-clicking on a MathType equation
after an eXtyles process has been run will open an entirely
different equation for editing. The problem is related to
the save to RTF that's performed "under the hood" by eXtyles.
In some cases (which have not been clearly defined to Inera),
saving a Word document to RTF (even without eXtyles
installed) will cause this problem with MathType equations when the
RTF file is then closed and reopened. To avoid this behavior,
run the MathType menu function Convert Equations on the Whole
Document with the type set to Convert Equations to MathType
equations.
Note that this conversion does not work properly in some
versions of MathType 5.x. It does, however, work in the most
recent versions of MathType 5.
A tech note
from Design Science provides information related to this issue.