Summary: | FILESAVE: DOCX: Incorrect spacing in footnote after RT (extra CR added b/c of table in footnote) | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | Xisco Faulí <xiscofauli> |
Component: | Writer | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | NEW --- | ||
Severity: | minor | CC: | jluth, kelemeng, xiscofauli |
Priority: | low | Keywords: | bibisected, bisected, filter:docx |
Version: | 6.3.0.0.alpha0+ | ||
Hardware: | All | ||
OS: | All | ||
See Also: |
https://bugs.documentfoundation.org/show_bug.cgi?id=104354 https://bugs.documentfoundation.org/show_bug.cgi?id=136779 https://bugs.documentfoundation.org/show_bug.cgi?id=95804 |
||
Whiteboard: | |||
Crash report or crash signature: | Regression By: | ||
Bug Depends on: | |||
Bug Blocks: | 132615 | ||
Attachments: |
sample file
sample compared MSO 2016 and LO 7.2+ |
Description
Xisco Faulí
2020-05-02 14:14:48 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 There is an extra CR added in each footnote for each save, which is the ultimate problem here I expect. actually, it is on import that the extra CR is added. Probably this is another case for bRemove - but that is getting ridiculous... 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"); Seems to me that only now is import correct, with 1-row tables in footnote, must be seen first with MSO. https://git.libreoffice.org/core/commit/e11c51eefe8c3210cef2b5850f401ba67a401d01 But bug remains, there's additional spacing after the first table. Something like screenshot attachment 170812 [details] in bug 95806. Created attachment 170813 [details]
sample compared MSO 2016 and LO 7.2+
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 MassPing-UntouchedBug |