MathType MTEF v.4 (MathType 3.5)

This document describes MTEF, the binary equation format used by MathType 3.5 (all platforms). MTEF is embedded in OLE equation objects produced by MathType, as well as in all the file formats in which MathType can save equations. The methods used by MathType to embed this information in such files are described in a separate document. See How MTEF is Stored in Files and Objects.

This document describes the binary equation format used by MathType 3.5 (all platforms). Although MTEF is not the most friendly medium for defining equations, there have been so many requests for this information, we decided to publish it anyway. We must warn the reader that it is not an easy format to understand and, more importantly, MathType is not at all forgiving in its processing of it. This means that if you send MathType MTEF with errors, it might crash. At a minimum, you will get an equation with formatting problems. Also, it is a binary format. This means that you can't use character strings to represent equations and it makes creating MTEF a little harder with programming languages like Visual Basic.

How MathType stores an equation description in an OLE equation object, a file, or on the clipboard is not described here. Please see the document on MathType MTEF Storage for more information on this subject.

MTEF data exists in the following versions:

Version 2 differs from version 1 only in the format of the header.

The version 1 header consists of a single byte version number. This number is 1 if the MTEF was generated on the Mac or 101 if it was generated by the Windows version.

The version 2 header consists of a 5-byte header:

This section describes the actual MTEF data following the header. MTEF data consists of a series of records. Each record starts with a tag byte containing the record type and some flag bits. The overall structure is:

• initial SIZE record
• PILE or LINE record
• contents of PILE or LINE
• END record

Most MTEF values are bytes. Word values (16-bit) are written low-order byte followed by high-order byte. All dimensional values are expressed in MathType’s internal units, 32nds of a point (A point is 1/72 inch).

Each tag byte consists of a record type in the low-order 4 bits and option flags in the high-order 4 bits. The following record types are used:

The option flag values are record-dependent:

LINE, CHAR, TMPL, PILE, MATRIX, and EMBELL records may store the result of nudging (small offsets applied by the user). A nudged record has the xfLMOVE flag (0x8) set in the tag byte and the tag byte is followed immediately by the nudge offset. The nudge offset consists of either two bytes or six, depending on the amount of offset. If -128 < dx < +128 and -128 < dy < +128, then the offsets are stored as two bytes, dx followed by dy, where each value is biased by 128. Otherwise, two bytes of 128 are stored, followed by the (unbiased) offsets, dx and dy, stored as 16-bit values.

CHAR records contain a typeface value (biased by 128). If the value is positive, it represents one of MathType’s styles:

If the value is negative, it represents an explicit font as specified by a FONT record.

LINE, CHAR, TMPL, PILE, MATRIX, and RULER records are followed by object lists that define contents of each equation structure. Each object list contains a sequence of records of any type and terminated by an END record. In a special case for LINE records, if there are no objects in the list, the xfNULL flag will be set in the tag byte and the object list is omitted entirely (i.e. no END record). Although there are no restrictions made by the MTEF format on what record types may occur in any particular list, the user interface prevents certain things from happening. For example, the object list defining the contents of a pile contains only LINE records.

Contains just the tag byte. No flags are defined.

Consists of:

• tag (1)
• [nudge] if xfLMOVE is set
• [line spacing] if xfLSPACE is set
• [RULER record] if xfRULER is set
• object list contents of line (a single pile, characters and templates, or nothing)

The line spacing value, if present, is the distance between the baseline of this line and the line above it.

Consists of:

• tag (2)
• [nudge] if xfLMOVE is set
• [typeface] typeface value (see FONT below) + 128
• [character] character value (encoding depends on typeface)
• [embellishment list] if xfEMBELL is set (embellishments)

Associated with every font is an encoding (a one-to-one mapping between character value and glyph; e.g. ASCII). The character represented by the character value is determined according to the encoding of the typeface value. The encodings used by MathType are documented by Wiris Tech Note #9.

Consists of:

• tag (3)
• [nudge] if xfLMOVE is set
• [selector] template selector code
• [variation] template variation code
• [options] template-specific options
• [subobject list] either a single character (e.g. sigma in a summation) and/or lines

The template selector and variation codes determine the class of the template and various properties of the template, such as which subobjects can be deleted by the user (see Template Selectors and Variations for a list). The class of a template determines the order and meaning of each of its subobjects (see Template Subobject Order).

The template-specific options field is only used for integrals and fence templates:

Consists of:

• tag (4)
• [nudge] if xfLMOVE is set
• [halign] horizontal alignment
• [valign] vertical alignment
• [RULER record] if xfRULER is set
• [object list] list of lines contained by the pile

Horizontal alignment:

Vertical alignment:

Consists of:

• tag (5)
• [nudge] if xfLMOVE is set
• [valign] vertical alignment of matrix within container
• [h_just] horizontal alignment within columns
• [v_just] vertical alignment within columns
• [rows] number of rows
• [cols] number of columns
• [row_parts] row partition line types
• [col_parts] column partition line types
• [object list] list of lines, one for each element of the matrix, in order from left-to-right and top-to-bottom

The values for valign, h_just, and v_just are described in PILE above.

The row partition line type list consists of two-bit values for each possible partition line (one more than the number of rows), rounded out to the nearest byte. Each value determines the line style of the corresponding partition line (0 for none, 1 for solid, 2 for dashed, or 3 for dotted). Similarly for the column partition lines.

Consists of:

• tag (6)
• [nudge] if xfLMOVE is set
• [embell] embellishment type

The embellishment types are:

Consists of:

• tag (7)
• [n_stops] number of tab-stops
• [tab-stop list] tab-stops in order from left-to-right

Each tab stop is described by a tab-stop type (0 for left, 1 for center, 2 for right, 3 for equal, 4 for decimal), followed by a 16-bit offset from the left end of the slot or pile with which it is associated.

Consists of:

• tag (8)
• [tface] typeface number
• [style] 1 for italic and/or 2 for bold
• [name] font name (null-terminated)

This record associates a typeface number with an explicit font and style. The typeface number is the negative (which makes it positive) of the typeface value (unbiased) that appears in CHAR records that might follow a given FONT record. For example, a 3 in the FONT record corresponds to 125 (-3 + 128) in the CHAR record.

Consists of one of the following cases:

if lsize < 0 (explicit point size):

• tag (9)
• 101
• -lsize (16 bits)

else if –128 < dsize < +128:

• tag (9)
• lsize
• dsize + 128

else: (large delta)

• tag (9)
• 100
• lsize
• dsize (16 bits)

Sizes in MathType are represented as a pair of values, lsize and dsize. Lsize stands for "logical size", dsize for "delta size". If it is negative, it is an explicit point size (in 32nds of a point) negated and dsize is ignored. Otherwise, lsize is one of the following typesize values and dsize is a delta from that size:

Consists of:

• tag (10-14)

These records are just short ways of specifying a simple typesize where dsize is zero. The tag value represents an lsize + 10. So if the tag value is 10, it means equation content following it will be Full size (szFULL), tag value 11 means szSUB, and so on.

This section shows the selector and variation codes for all the templates. The symbols shown here are internal identifiers in MathType and are for reference only. The class names can be used to determine the order of subobjects in the list following the template tag (see Template Subobject Order).

The following list shows the order of subobjects for each template class:

ArcBoxClass vector notation

• main slot

ArroBoxClass expanding arrows

• main slot
• arrow character

BarBoxClass over-bars and under-bars

• main slot

BigOpBoxClass integrals, summations, products, etc.

• main slot (summand, integrand)
• upper slot
• lower slot
• large operator character

DiracBoxClass three-part bracket structure

• left slot
• right slot
• left angle bracket (optional)
• vertical bar
• right angle bracket (optional)

FracBoxClass fractions with a horizontal bar

• numerator slot
• denominator slot

HBrBoxClass horizontal expanding braces

• main slot
• small slot
• brace character

LDivBoxClass long division

• dividend slot
• quotient slot

LimBoxClass limits

• main slot
• lower slot
• upper slot

ParBoxClass parenthesized or bracketed slots

• main slot
• left fence character (optional)
• right fence character (optional)

RootBoxClass radical sign

• main slot
• radicand slot

ScrBoxClass subscripts and superscripts

• subscript slot
• superscript slot

SlashBoxClass fractions with a diagonal bar

• numerator slot
• denominator slot

VectorBoxClass box with upper or lower arrow

• main slot