Code that checks ProgIds should do case-insensitive tests.įuture versions of MathType may create high-resolution PICTs (version 2 extended PICTs). For example, MathType 6.x's ProgId is “Equation.DSMT4”.

All OLE 2.0 equations have a ProgId that begins with “equation.” followed by an arbitrary string that uniquely determines which version of MathType owns the object. All OLE 1.0 equations produced by MathType have a ProgId of “equation”. The proper way to do this is to check the object’s ProgId character string. Also, MathType generates other picture comments but they are not Application comments (that is, they do not have a kind of 100).Īpplications that support baseline positioning can process all objects at import/editing time by either scanning the PICT as described above or, if the object is an OLE object (Microsoft’s Object Linking and Embedding technology), performance may be increased by checking first to see if the object is a MathType equation object.

When attempting to recognize a baseline comment, it is important to make sure the data type is zero, because the baseline comment is not the only application comment currently generated by MathType. Type (0 indicates baseline data to follow) Application signature (∑ = Option-w, 183 decimal)

Equation writer for word mac