Bug 81679

Summary: FILEOPEN: Some text wrongly displayed as subscript when opening .pptx
Product: LibreOffice Reporter: ravingdesi
Component: ImpressAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED WORKSFORME    
Severity: normal CC: barta
Priority: medium    
Version: 4.2.5.2 release   
Hardware: Other   
OS: All   
Whiteboard: BSA
Crash report or crash signature: Regression By:

Description ravingdesi 2014-07-23 15:52:56 UTC 
When opening a pptx file, a whole part of the text is shown as subscript although only certain letters should be shown as subscript.

Steps to reproduce:
1. Download https://dl.dropboxusercontent.com/u/17406199/bugtmp/Bug13.pptx
2. Open in libreoffice
3. Compare to results in MS office

Current behavior:
Currently, libreoffice displays more of the text as subscript than it should:
https://dl.dropboxusercontent.com/u/17406199/bugtmp/Bug13_2.png

Expected behavior:
Should look as in MS office (screenshot from office 2010):
https://dl.dropboxusercontent.com/u/17406199/bugtmp/Bug13_1.png
Operating System: Ubuntu
Version: 4.2.5.2 release
Comment 1 tommy27 2014-07-23 17:39:19 UTC 
same issue in LibO 4.2.5.2 under Win7x64. status NEW.
did it work in previous LibO releases?
Comment 2 tommy27 2014-07-23 19:29:40 UTC 
works fine in 4.1.5.3
regression of the 4.2.x branch

however works again in 4.4.0.0.alpha0+
Build ID: b9dca968c6fd0ab5ca140c65b0e54d153cd34986
TinderBox: Win-x86@42, Branch:master, Time: 2014-07-18_22:51:20

closing this as RESOLVED WORKSFORME since it's at least fixed in master branch
so let's hope that the fix in 4.4.x is going to be backported in next 4.2.x and 4.3.x releases as well.
Comment 3 ravingdesi 2014-07-28 15:35:11 UTC 
Apparently has been backported to 4.2.6 as bug does not occur here on 4.2.6.2.
Maybe this should be added to the list of fixed bugs in 4.2.6.
Comment 4 tommy27 2014-07-28 15:40:33 UTC 
(In reply to comment #3)
> Apparently has been backported to 4.2.6 as bug does not occur here on
> 4.2.6.2.
> Maybe this should be added to the list of fixed bugs in 4.2.6.

the list of fixed bugs is automatically generated by a script 
maybe the current fix is a side effect of another related bugfix

anyway, glad to know it's fine in 4.2.6