Bug 55775 - pptx import does not show "super-script" correctly
Summary: pptx import does not show "super-script" correctly
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: filters and storage (show other bugs)
(earliest affected) rc
Hardware: Other All
: low normal
Assignee: Not Assigned
Depends on:
Reported: 2012-10-08 19:11 UTC by Matti Aarnio
Modified: 2015-06-15 19:19 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:

Sample PPTX with engineering superscripts showing badly (1.49 MB, application/vnd.openxmlformats-officedocument.presentationml.presentation)
2012-10-08 19:11 UTC, Matti Aarnio
Sample where the number of colors is in 2^xx format (84.87 KB, application/vnd.openxmlformats-officedocument.presentationml.presentation)
2012-11-29 19:22 UTC, andre

Note You need to log in before you can comment on or make changes to this bug.
Description Matti Aarnio 2012-10-08 19:11:45 UTC
Created attachment 68276 [details]
Sample PPTX with engineering superscripts showing badly

Importing engineering presentations in pptx format has always been a bit poor to read:

Text appears as following at my screen:

  17:03 STABLE BEAMS #3138. Initial luminosity ~7.3x1033 cm-2s-1

while it would be meaningful if it appeared something like this:
(requires courier font to make sense)

                                                      33   -2 -1
  17:03 STABLE BEAMS #3138. Initial luminosity ~7.3x10   cm  s 

The attached PPTX at Slide 4 has this defined as following XML:
      <a:spcPts val="1200"/>
    <a:rPr dirty="0" lang="en-US" smtClean="0" sz="2000"/>
    <a:t>17:03 STABLE BEAMS #3138. Initial luminosity ~7.3x10</a:t>
    <a:rPr baseline="30000" dirty="0" lang="en-US" smtClean="0" sz="2000"/>
    <a:rPr dirty="0" lang="en-US" smtClean="0" sz="2000"/>
    <a:t> cm</a:t>
    <a:rPr baseline="30000" dirty="0" lang="en-US" smtClean="0" sz="2000"/>
    <a:rPr dirty="0" lang="en-US" smtClean="0" sz="2000"/>
    <a:rPr baseline="30000" dirty="0" lang="en-US" smtClean="0" sz="2000"/>
    <a:rPr dirty="0" lang="en-US" smtClean="0" sz="2000"/>
    <a:t> </a:t>
  <a:endParaRPr dirty="0" lang="en-US" sz="2000"/>
Comment 1 Joel Madero 2012-10-19 17:34:09 UTC


Marking as NEW & Prioritizing

Normal: Can prevent high quality work when using MS Office as well as LibreOffice. No workaround really, just stuck with incorrect formatting

Low: Very specific situation which isn't very common -- superscripts in general just aren't used very often. Furthermore, only occurs if document is in PPTX format and created in MS Office. User base affected probably low
Comment 2 andre 2012-11-29 19:22:10 UTC
I don't think it's a low prio bug, or at least it's a bug which produces incorrect values.

When we look at the example, then we see that the values are eithe 10^33 or 1033, just worlds away.

I did see this problem also in this example where the number of colors ist either 2^24 or 2^48 colors.

When playing the presentation it shows 224 or 248 colors (That's definitively a problem)
Comment 3 andre 2012-11-29 19:22:42 UTC
Created attachment 70800 [details]
Sample where the number of colors is in 2^xx format
Comment 4 Joel Madero 2012-11-29 19:26:20 UTC
There are to components to bug prioritization:

Normal is the status which means it's affecting professional quality work (which is what you're saying)

Low: Relative to a lot of other normal status bugs, this is a low priority. If you query out in FDO all the normal bugs you'll see what I mean, a lot of them are some serious issues that will affect almost all users (or a large portion of them). This one is very specific, I know that for those users it does affect it's going to be an issue but in the grand scheme of 5,000 or so bugs, this is the correct prioritization
Comment 5 QA Administrators 2015-04-19 03:21:08 UTC
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

   *Test to see if the bug is still present on a currently supported version of LibreOffice (4.4.1 or later)

   *If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior
   *If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System

Please DO NOT

   *Update the version field
   *Reply via email (please reply directly on the bug tracker)
   *Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case)

If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 

1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3)


2. Test your bug 
3. Leave a comment with your results. 
4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 
4b. If the bug was not present in 3.3 - add "regression" to keyword

Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa

Thank you for your help!

-- The LibreOffice QA Team This NEW Message was generated on: 2015-04-18
Comment 6 Buovjaga 2015-06-15 19:19:50 UTC
Checked attachment 68276 [details] with MS PPT viewer and it matches current LibO.

Win 7 Pro 64-bit Version:
Build ID: 01a189abcd9a4ca472a74b3b2c000c9338fc2c91
TinderBox: Win-x86@39, Branch:master, Time: 2015-06-14_07:46:28
Locale: fi-FI (fi_FI)