Bug 134596 - FILEOPEN DOC : Abnormal row spacing
Summary: FILEOPEN DOC : Abnormal row spacing
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.1.0.3 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisected, bisected, filter:doc
Depends on:
Blocks: DOC-Paragraph
  Show dependency treegraph
 
Reported: 2020-07-07 06:14 UTC by NSO LibreOffice Team
Modified: 2025-06-14 03:13 UTC (History)
6 users (show)

See Also:
Crash report or crash signature:


Attachments
Example file (31.00 KB, application/msword)
2020-07-07 06:14 UTC, NSO LibreOffice Team
Details
Difference comparison of row spacing (229.53 KB, application/vnd.oasis.opendocument.text)
2020-07-07 06:17 UTC, NSO LibreOffice Team
Details

Note You need to log in before you can comment on or make changes to this bug.
Description NSO LibreOffice Team 2020-07-07 06:14:18 UTC
Created attachment 162739 [details]
Example file

Description:
Using libreoffice document to open the common domain test document (doc),  Abnormal row spacing.

Steps to Reproduce:
1.Using libreoffice document to open the common domaintest document (docx)
2.Abnormal row spacing

Actual Results:
Open the document, Abnormal row spacing

Expected Results:
Row spacing should remain the same 


Reproducible: 
Always


Additional Info:
Version Infomation
Version: 7.1.0.0.alpha0+ (x64)
Build ID: 4c14c88cc681abab787a461a1bea502a777f37e6
CPU threads: 12; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win
Locale: zh-CN (zh_CN); UI: en-US
Calc: threaded
Comment 1 NSO LibreOffice Team 2020-07-07 06:17:47 UTC
Created attachment 162740 [details]
Difference comparison of row spacing
Comment 2 Xisco Faulí 2020-07-10 17:09:39 UTC
Reproduced in

Version: 7.1.0.0.alpha0+
Build ID: 12bfedfac3b141fe6c91b0e5ae5b3fb2ba817c48
CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded
Comment 3 Xisco Faulí 2020-07-10 17:12:50 UTC
also reproduced in

Version: 6.1.0.0.alpha1+
Build ID: 3a801799536e6870f2fb111b1cc00b9575a35a39
CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: gtk3; 
Locale: en-US (en_US.UTF-8); Calc: group

but not in

Version: 5.4.0.0.alpha1+
Build ID: 9feb7f7039a3b59974cbf266922177e961a52dd1
CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: gtk3; 
Locale: en-US (en_US.UTF-8); Calc: group
Comment 4 Buovjaga 2020-07-11 11:54:31 UTC
The bibisecting of this report is reserved for new QA team members in training. Bibisecting should be done using the win32-6.1 repo.
Comment 5 raal 2020-09-07 15:33:14 UTC
This seems to have begun at the below commit.
Adding Cc: to Mike Kaganski ; Could you possibly take a look at this one?
Thanks
 b021e0f87b4b6f75c2aaff1088522525618c17b5 is the first bad commit
commit b021e0f87b4b6f75c2aaff1088522525618c17b5
Author: Jenkins Build User <tdf@pollux.tdf>
Date:   Tue Apr 3 10:02:16 2018 +0200

    source b9955b2083ffdc1f99bc8be6b09d806fa3279a16

author	Mike Kaganski <mike.kaganski@collabora.com>	2018-04-02 08:54:59 +0100
committer	Katarina Behrens <Katarina.Behrens@cib.de>	2018-04-03 09:43:56 +0200
commit b9955b2083ffdc1f99bc8be6b09d806fa3279a16 (patch)
tree 8deabb3c56c55833392d8454feac519740caaafd
parent 14198f2191f216592f00b72221771704b3ce4636 (diff)
tdf#93173: Remove arbitrary line spacing limit
Comment 6 Mike Kaganski 2020-09-07 15:58:49 UTC
Not truly a regression. The line spacing now is correct (for line "项目名称:" in page 1, it's 300% in LO 7.0.1.2, matching MS Word's "Multiple - 3"). But there seems to be some specifics with Word's handling of this paragraph (or maybe my en-US MS Office doesn't show me some of the properties there ... something like LO doesn't show some properties when Asian language support is not activated)?
Comment 7 Justin L 2022-02-23 12:53:35 UTC
I agree with Mike that this likely is not a regression. Something font related?
Comment 8 QA Administrators 2025-06-14 03:13:25 UTC
Dear NSO LibreOffice Team,

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