Bug 132611 - FILESAVE: DOCX: Incorrect spacing in footnote after RT (extra CR added b/c of table in footnote)
Summary: FILESAVE: DOCX: Incorrect spacing in footnote after RT (extra CR added b/c of...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected)
Hardware: All All
: low minor
Assignee: Not Assigned
Keywords: bibisected, bisected, filter:docx
Depends on:
Blocks: Dev-import-export-pages
  Show dependency treegraph
Reported: 2020-05-02 14:14 UTC by Xisco Faulí
Modified: 2023-03-30 03:25 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:

sample file (21.24 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2020-05-02 14:14 UTC, Xisco Faulí
sample compared MSO 2016 and LO 7.2+ (88.36 KB, image/png)
2021-03-29 15:57 UTC, Timur

Note You need to log in before you can comment on or make changes to this bug.
Description Xisco Faulí 2020-05-02 14:14:48 UTC
Created attachment 160225 [details]
sample file

issue found while creating unittest for bug 66496

1. Open sw/qa/extras/ooxmlexport/data/tdf66496.docx -> document has 1 page
2. Export to DOCX
3. Reopen

-> Document has 2 pages


Build ID: cf36fe5eb41910c26d58fb25e54ccf2e0ee01365
CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: gtk3; 
Locale: en-US (en_US.UTF-8); UI-Language: en-US
Calc: threaded
Comment 1 Xisco Faulí 2020-05-02 14:18:21 UTC
The import part was fixed by https://cgit.freedesktop.org/libreoffice/core/commit/?id=dff829e863fd05bedd5bcb713cd80c10fa582932.
Before this commit, the document has 2 pages at import time

@Justin, I thought you might be interested in this issue.

For the unittest, you could reuse https://cgit.freedesktop.org/libreoffice/core/commit/?id=dff829e863fd05bedd5bcb713cd80c10fa582932
Comment 2 Justin L 2020-05-02 15:23:54 UTC
There is an extra CR added in each footnote for each save, which is the ultimate problem here I expect.
Comment 3 Justin L 2020-05-02 17:50:55 UTC
actually, it is on import that the extra CR is added. Probably this is another case for bRemove - but that is getting ridiculous...
Comment 4 Justin L 2020-05-05 10:59:22 UTC
This sample file has footnotes consisting of tables (which are not seen until I wave my magic cursor over them - Ubuntu 16.04 and 20.04).

In sw flowfrm.cxx, I see this patch of code:
    SAL_WARN("sw.core", "Tables in footnotes are not truly supported");
Comment 5 Timur 2021-03-29 15:53:26 UTC
Seems to me that only now is import correct, with 1-row tables in footnote, must be seen first with MSO. 
But bug remains, there's additional spacing after the first table.
Something like screenshot attachment 170812 [details] in bug 95806.
Comment 6 Timur 2021-03-29 15:57:58 UTC
Created attachment 170813 [details]
sample compared MSO 2016 and LO 7.2+
Comment 7 QA Administrators 2023-03-30 03:25:32 UTC
Dear Xisco Faulí,

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