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


Hi Takeshi Abe,

Takeshi Abe schrieb:
Hi Regina,

I found the commit 4f294a90877d2f91bb88c7d6cd5b74e8e546a025 is the origin of
the difference, which makes SmParser::Parse() avoid wrapping a node of type
NTEXT within another node of type NEXPRESSION in simple cases.
It affects SmTextNode::CreateTextFromNode() checking whether each of identifier
nodes should be quoted or not.
I have submitted a possible fix [1] to gerrit, while of course we still have
to handle mathvariant attribute in MathML for solving the entire issue.

[1] https://gerrit.libreoffice.org/17613

that is great, that you find a usable solution.

There exists not only the problem of the attribute mathvariant, but a lot of more problems. But I think, that needs a separate discussion how to get a smooth transition from starmath to MathML, which is specified to be the language of equations in ODF.

Kind regards
Regina



Cheers,
-- Takeshi Abe

On Sun, 02 Aug 2015 03:00:14 +0900 (JST), Takeshi Abe <tabe@fixedpoint.jp> wrote:
On Sat, 01 Aug 2015 19:24:16 +0200, Regina Henschel <rb.henschel@t-online.de> wrote:
Unfortunately the problem is deeper. There should not be any quotes, because the
element <mi> from MathML should be mapped to a variable in starmath, but
actually it is mapped to a text. Removing the italic style cured only a symptom,
the element has still the wrong font and is the wrong type.
I agree with your view.



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.