Bug 75933 - IMPORT MathML: wrong position of superscript
Summary: IMPORT MathML: wrong position of superscript
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Formula Editor (show other bugs)
Version:
(earliest affected)
4.2.0.0.beta1
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-09 01:39 UTC by Mike Kaganski
Modified: 2015-12-15 03:44 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Testsuite for wrong superscript in imported MML (54.32 KB, application/zip)
2014-03-09 01:39 UTC, Mike Kaganski
Details
Superscript position (52.44 KB, image/png)
2015-12-15 03:13 UTC, Marcos Souza
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Kaganski 2014-03-09 01:39:19 UTC
Created attachment 95384 [details]
Testsuite for wrong superscript in imported MML

The attachment contains MML that, when imported, has wrong position of a superscript (it is attributed to preceeding subscript, not to main variable). The problematic part is marked on the screenshot that is also in attachment. The screenshot contains both current import state and expected result.

Marcos, please take a look at this. Thanks!
Comment 1 Jean-Baptiste Faure 2014-05-01 16:07:57 UTC
Indeed if I open the mml file with LibO and Firefox I got different views.
It seems that when importing the mml code, Starmath should include the first subscript between {}.

Tested with LibO 4.2.5.0.0+ under Linux / Ubuntu 14.04 x86-64.

Best regards. JBF
Comment 2 Marcos Souza 2015-12-15 03:12:13 UTC
Hi guys,

testing with the current master, the superscript position is correct. Should this bug be closed as fixed...?
Comment 3 Marcos Souza 2015-12-15 03:13:26 UTC
Created attachment 121309 [details]
Superscript position
Comment 4 Mike Kaganski 2015-12-15 03:44:06 UTC
(In reply to Marcos Souza from comment #2)
> testing with the current master, the superscript position is correct. Should
> this bug be closed as fixed...?

Yes, I see this, too. Great!
The reason is that the import was greatly improved (by you? Thank you!) in master. A lot of needless tags were removed, and the result is clear. The preceeding subscript does not contain the "italic" keyword, so everything is OK.

Just one note. Hopefully, the new code does handle right those cases where such keywords are required, and correctly braces those parts.

Closing WORKSFORME.