Bug 154399 - FILEOPEN PPTX: table cells renders differently due to missing word break (unless manually enabling hyphenation)
Summary: FILEOPEN PPTX: table cells renders differently due to missing word break (unl...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:pptx
Depends on:
Blocks: PPTX Hyphenation
  Show dependency treegraph
 
Reported: 2023-03-26 00:43 UTC by Gerald Pfeifer
Modified: 2025-12-13 03:14 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
Sample slide (PPTX) (92.61 KB, application/vnd.openxmlformats-officedocument.presentationml.presentation)
2023-03-26 00:43 UTC, Gerald Pfeifer
Details
Visual comparison Office 365 vs LibreOffice (69.27 KB, image/png)
2023-03-26 00:48 UTC, Gerald Pfeifer
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Gerald Pfeifer 2023-03-26 00:43:33 UTC
Created attachment 186225 [details]
Sample slide (PPTX)

Slide 21 of attachment #127409 [details] from bug #102261 renders differently in
LibreOffice than PowerPoint due to a missing word break/line break, in
the end resulting in three lines instead of just two.

Once I manually set "Tools - Language - Hyphenation" the respective 
table cell shrinks from 3 lines to 2, as in PowerPoint.

This is really not ideal from a user perspective where one usually simply
wants to open an *existing* presentation and have it appear similar to
how it shows in PowerPoint. 

Is there anything we can/should do by default? Such as enabling 
hyphenation when importing a PPTX?
Comment 1 Gerald Pfeifer 2023-03-26 00:48:08 UTC
Created attachment 186226 [details]
Visual comparison Office 365 vs LibreOffice
Comment 2 Buovjaga 2023-04-13 12:41:42 UTC
Confirmed

Arch Linux 64-bit, X11
Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 9470fca71139f9e439ce61b4c93dd33022c2cc6d
CPU threads: 8; OS: Linux 6.2; UI render: default; VCL: kf5 (cairo+xcb)
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
Calc: threaded
Built on 13 April 2023
Comment 3 QA Administrators 2025-12-13 03:14:08 UTC
Dear Gerald Pfeifer,

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 with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

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) from https://downloadarchive.documentfoundation.org/libreoffice/old/

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: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug