Bug 161939 - FILEOPEN DOCX Line spacing too large in bulleted list
Summary: FILEOPEN DOCX Line spacing too large in bulleted list
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.2.0.4 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: DOCX-Bullet-Number-Outline-Lists
  Show dependency treegraph
 
Reported: 2024-07-07 15:47 UTC by Maxime Lapointe
Modified: 2024-10-09 04:17 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
File showing the bug. Open in Word vs Writer (33.01 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2024-07-07 15:48 UTC, Maxime Lapointe
Details
PDF exported from office.com (167.17 KB, application/pdf)
2024-08-28 15:51 UTC, Buovjaga
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Maxime Lapointe 2024-07-07 15:47:26 UTC
Description:
Word and Writer have different vertical spacing between bullets in the joined document. Visually, it's as if Writer had a full empty line between the bullets, which breaks expectation.

In the original document's case (not joined, I only joined a simplified example), 4 bullets had the expected spacing and only 2 of them had the extra spacing in LibreOffice, making the problem quite jarring.

Steps to Reproduce:
Open the attached file. I don't know what the user did to generate this problematic case.

Actual Results:
In Word: The bullets and text are vertically close without a big spacing, as if on a next line
In Writer: The bullets are have vertical spacing as if an empty line / interline was setup

Expected Results:
Both behave the same, which I guess means Writer behaving like Word:

The bullets and text are vertically close without a big spacing, as if on a next line


Reproducible: Always


User Profile Reset: No

Additional Info:
I tried on multiple Linux installations and all have the problem.

The problem shows in the editing and when printing (I tried with PDF)

Version: 24.2.4.2 (X86_64) / LibreOffice Community
Build ID: d29029bfb700ea4a272da1366c5f5e7c14e351b5
CPU threads: 16; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: fr-CA (fr_CA.UTF-8); UI: fr-FR
Calc: threaded
Comment 1 Maxime Lapointe 2024-07-07 15:48:37 UTC
Created attachment 195150 [details]
File showing the bug. Open in Word vs Writer
Comment 2 Buovjaga 2024-08-28 15:51:33 UTC
Created attachment 196069 [details]
PDF exported from office.com
Comment 3 Buovjaga 2024-08-28 16:05:50 UTC
Bibisected the change with linux-42max to de516780bf2d5f74afe643033bfc528c53013902
bnc#816593 DOCX import: let w:before not overwrite w:beforeAutospacing

Not sure, if this is a regression, so not marking as such. Let's ask what Miklos thinks.

Still confirmed in

Arch Linux 64-bit
Version: 25.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 47fbbd7c6b9ea6b4a20f05fdf8870cb9e125fb21
CPU threads: 8; OS: Linux 6.10; UI render: default; VCL: kf6 (cairo+wayland)
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
Calc: CL threaded
Built on 28 August 2024

Version: 25.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 4e04e96334a841865914c1629202912e343c4cb2
CPU threads: 2; OS: Windows 11 X86_64 (10.0 build 22621); UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-GB
Calc: threaded
Comment 4 Miklos Vajna 2024-08-29 06:22:13 UTC
Ilmari: thanks for the bisect.

This is odd, the render result in Writer is definitely buggy, but if you look at the paragraph options on the UI, then Word has automatic before/after spacing and single line spacing; Writer has above/below paragraph spacing set to 0 and also single line spacing. So in theory if there is a difference here, then the Writer spacing would be smaller, not larger.

At the same time, the above commit just fixed the priority between two conflicting attributes, so if that causes any problems, this simply uncovered an existing problem, because then this really just worked by accident before.

So I guess this is a case of "yes, this is a bug, it is worth fixing, but it wasn't really working before, not a true regression".