Bug 131443 - pptx import: Incorrect alignment of text
Summary: pptx import: Incorrect alignment of text
Status: RESOLVED DUPLICATE of bug 104909
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
6.4.0.3 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-03-20 14:39 UTC by Frederic Parrenin
Modified: 2020-03-22 17:33 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
.pptx file to reproduce the problem (77.99 KB, application/vnd.openxmlformats-officedocument.presentationml.presentation)
2020-03-20 14:39 UTC, Frederic Parrenin
Details
.png screenshot comparing the slide in Impress and PowerPoint. (539.38 KB, image/png)
2020-03-22 11:20 UTC, Frederic Parrenin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Frederic Parrenin 2020-03-20 14:39:35 UTC
Created attachment 158837 [details]
.pptx file to reproduce the problem

Steps to reproduce:
- open the attached pptx file in LO 6.4 and PowerPoint
- compare
=> the last line is not aligned in the same way
Comment 1 Oliver Grimm 2020-03-21 23:17:57 UTC
Your sample file uses the font Tahoma which is not a standard font on my machine. Other bug reports say that font embedding is broken with LibreOffice for pptx files.

Therefore, can you confirm that you have the font Tahoma installed on your system and thus rule out that this is a problem of displaying a substituted vs. original font?

In addition, please provide the info given under "Main Menu | Help | About".
Comment 2 Frederic Parrenin 2020-03-22 11:20:46 UTC
Created attachment 158869 [details]
.png screenshot comparing the slide in Impress and PowerPoint.

Yes, I have the Tahoma font installed on my system.
Apparently, it is a problem with tabulations.
I attach a screenshot comparing the slide in Impress and PowerPoint.
Comment 3 Timur 2020-03-22 17:33:41 UTC
Simple search finds this is a duplicate.

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