Description: FILEOPEN DOC/DOCX: Table height larger compared to ODT (since 7.1) Steps to Reproduce: 1. Open the attached file 2. Save to DOCX 3. File reload 4. Open the ODT again 5. Switch back and forward between ODT/DOCX (notice the difference) Actual Results: Table height difference Expected Results: Not so Reproducible: Always User Profile Reset: No Additional Info: Found in Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 36efb384a66b6dd645e0ae80fd7df68370a9dc8b CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: nl-NL Calc: CL and in Version: 7.1.0.0.beta1+ (x64) Build ID: f9fab4203c1aa0b9a3f27ce2713b6d5addc7df19 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: nl-NL Calc: CL not in 7.0
Created attachment 174177 [details] Example file
Confirm in Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: c97bdca2d7abf30a99c45192b8f49c5bf76ca035 CPU threads: 4; OS: Linux 5.11; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded
This seems to have begun at the below commit. Adding Cc: to Michael Stahl ; Could you possibly take a look at this one? Thanks 9495f24f8b825bbff3c6a73cacd7e8ee5f359150 is the first bad commit commit 9495f24f8b825bbff3c6a73cacd7e8ee5f359150 Author: Jenkins Build User <tdf@pollux.tdf> Date: Fri Sep 25 01:45:31 2020 +0200 source 38aa699f265c17548769aaa4f20e1ae35d18f202 https://git.libreoffice.org/core/+/38aa699f265c17548769aaa4f20e1ae35d18f202 tdf#134782 sw: split AddParaSpacingToTableCells flag in 2
Please set Importance. This is Minor at best, low to lowest.
so if i revert the commit in comment #3, nothing changes. if i try the latest libreoffice-7-0, -6-4 still the same result. but with libreoffice-6-3 we get the same looks when loading the exported DOCX as when loading the ODT. however, it turns out that Word 2013 shows the DOCX exported by LO 6.3 differently than LO 6.3, and in the same way as current LO => LO 6.3 DOCX import is wrong so it looks like this never actually worked => removing regression the ODT file has: <config:config-item config:name="AddParaSpacingToTableCells" config:type="boolean">true</config:config-item> <config:config-item config:name="AddParaLineSpacingToTableCells" config:type="boolean">false</config:config-item> AFAIK Word doesn't support such a mode directly. there is some code in MSWordExportBase::OutputTextNode() that checks the spacing setting and clears a Lower-space ... but the paragraphs in the table don't have a RES_UL_SPACE so the test is skipped and adding ADD_PARA_LINE_SPACING_TO_TABLE_CELLS there doesn't help. sw/source/filter/ww8/wrtw8nds.cxx: if (!m_rDoc.getIDocumentSettingAccess().get(DocumentSettingId::ADD_PARA_SPACING_TO_TABLE_CELLS)) not sure what to do about this but it doesn't look obvious.
(In reply to Timur from comment #4) > Please set Importance. This is Minor at best, low to lowest. Well page flow of documents on export is kind of important (at least to me). If you have a nice layout in ODT, but this this being screwed on export. The big question is more how likely is this to occur. I get the impression that this isn't regular, based on comment 5. But well that wasn't something to be known, before you demoted the bug.
Dear Telesto, 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