Bug 132896 - FILEOPEN PPTX: Image ignores its rotation
Summary: FILEOPEN PPTX: Image ignores its rotation
Status: RESOLVED DUPLICATE of bug 132893
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
4.1 all versions
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:pptx
Depends on:
Blocks:
 
Reported: 2020-05-09 21:51 UTC by Alvaro Segura
Modified: 2020-05-11 13:43 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
sample PPTX showing bad behavior (64.02 KB, application/vnd.openxmlformats-officedocument.presentationml.presentation)
2020-05-09 21:54 UTC, Alvaro Segura
Details
Comparison of PowerPoint vs Impress rendering (31.00 KB, image/png)
2020-05-09 21:55 UTC, Alvaro Segura
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alvaro Segura 2020-05-09 21:51:10 UTC
Description:
A PPTX contains an image rotated 90 degrees, saved in PowerPoint. When loading, this image appears without that rotation.

I then noticed that if I then further rotate the image in Impress with the mouse, the interactive markers show that the image container does rotate, but the image rendered inside stays still.

Steps to Reproduce:
Steps explained in the description. A sample will be attached.

Actual Results:
Image stays oriented as originally

Expected Results:
Image should appear rotated.


Reproducible: Always


User Profile Reset: No



Additional Info:
-
Comment 1 Alvaro Segura 2020-05-09 21:54:17 UTC
Created attachment 160576 [details]
sample PPTX showing bad behavior

Look at the letter C in the right column. The embedded PNG file had the C rotated, so it was further rotated after embedding in PowerPoint to make it look upright. That works in PowerPoint, but not in Impress.
Comment 2 Alvaro Segura 2020-05-09 21:55:22 UTC
Created attachment 160577 [details]
Comparison of PowerPoint vs Impress rendering
Comment 3 Alvaro Segura 2020-05-09 21:56:46 UTC
Comment on attachment 160577 [details]
Comparison of PowerPoint vs Impress rendering

This bug is about the letter "C" orientation. The rest of differences belong to other bugs.
Comment 4 Xisco Faulí 2020-05-11 10:24:01 UTC
Reproduced in

Reproduced in

Version: 7.0.0.0.alpha1+
Build ID: 86bc13248c1d9f63b10aac304bdf0361d1dcc47f
CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: gtk3; 
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

Version: 5.2.0.0.alpha1+
Build ID: 5b168b3fa568e48e795234dc5fa454bf24c9805e
CPU Threads: 4; OS Version: Linux 4.8; UI Render: default; 
Locale: ca-ES (ca_ES.UTF-8)

Version: 4.3.0.0.alpha1+
Build ID: c15927f20d4727c3b8de68497b6949e72f9e6e9e

Version 4.1.0.0.alpha0+ (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a)
Comment 5 Xisco Faulí 2020-05-11 10:36:15 UTC
After rereading the description, I'm a bit confused. At first I thought this issue was about the text but you are talking about an image. Which image is it? OTOH, is it an import issue or an export issue ?
Comment 6 Alvaro Segura 2020-05-11 12:53:55 UTC
Sorry, yes, now I think I didn't choose a good example. The problem is with the letter "C" at the right which is actually an image.

The bug appeared in a real PPT with this "Smart Art Picture Accent List" template from PowerPoint. It adds columns of items, each with a title (vertical text) and with an *image* as an icon to each column (at the top). I needed to rotate one of the images becuuse it was badly rotated in the source image file.

So, I made a simplified version of this slide for the bug report (and for confidentiality), and changed the 3 picures with those 3 letters (Yes, they are actually images). I thought letters were good to highlight the wrong orientation.

In fact that real PPT showed 2 bugs: the other is about the upside-down texts (Bug 132893). And I used the same slide in both bug reports.
Comment 7 Xisco Faulí 2020-05-11 13:43:07 UTC
I do believe this issue is directly related to bug 132893.
Let's close it as a duplicate of bug 132893 for the time being.
We can always reopen it later on

*** This bug has been marked as a duplicate of bug 132893 ***