Date: prev next · Thread: first prev next last
2015 Archives by date, by thread · List index


Miklos Vajna <vmiklos <at> collabora.co.uk> writes:

On Wed, May 20, 2015 at 07:50:09AM +0000, Yury <yury.tarasievich <at>
gmail.com> wrote:
So, to deal with this, at least with point 2.1, one would need to know where
the processing of starmath metafile used in formula/equation conversion is
located in source. What file, what subroutine?

Word 2003 uses Mathtype to describe the math equations and they are
embedded as OLE objects into the file.

The entry point of the Mathtype import is
starmath/source/mathtype.cxx:557, MathType::Parse().

I *think* the Mathtype export is MathType::ConvertFromStarMath() in the
same file.

Many, many thanks for answering. This is not the code I'm looking for,
however. :)

What you're talking about is the source directory for the translation of
'eqn->mathtype' direction and back. I know this much. :)

I need the place in source (call sequence, possibly?) where the bitmap
attached to equation by starmath as 'ObjectReplacement' is converted to the
bitmap in format word uses (Microsoft metafile?). This thing would be sort
of put 'on top' of the converted starmath object. I can't easily find where
this is done.

If you are more interested about how this native data is embedded to the
document, put a breakpoint on the export method in gdb, and have a look
at the backtrace to see how you get there.

Using gdb is right out for me. :)

-Yury



Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.