Created attachment 115462 [details] Contains original ODT, exported DOCX, and PNG screen snippet. Create a table in an ODT file. Add spacing around table (in my example, top and bottom == 0.08"). Export to 2013 DOCX. Open DOCX in LO. Table properties have spacing == zero.
Also, DOCX --> DOCX forgets table spacing. DOCX --> ODT remembers spacing.
Reproducible with LO 4.4.2.2, Win 8.1 It works with odt, but it doesn't work with doc and docx.
Reproduced in LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4
** Please read this message in its entirety before responding ** 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Bug is still present as described and also with new file created from scratch. Version: 7.1.1.1 / LibreOffice Community Build ID: 575c5867c4cc13d7ae78f9ce39a54a52ed38c769 CPU threads: 8; OS: Linux 5.10; UI render: default; VCL: kf5 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded
*** Bug 148767 has been marked as a duplicate of this bug. ***
Created attachment 186978 [details] The original file and its docx version in master Still a problem in Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 9a555d79b3b00793edf1d51a8a7c76b723cc436d CPU threads: 14; OS: Windows 10.0 Build 19045; UI render: default; VCL: win Locale: en-US (hu_HU); UI: en-US Calc: threaded Such settings could be exported now(?) by putting the whole table into a splitting textframe with these spacing values at save time, and it would roundtrip reasonably well.
While Gabor's comment 7 may be correct, I'm quite sure this report should just be closed as NOTABUG. Isn't this a limitation of the MS formats? I mean, what is the DOCX setting that would do such a thing? In the UI I don't notice anything that allows a top and bottom margin for an inline table. Floating a table simply to preserve top and bottom margins is a very heavy price to pay - it will cause many more problems than what it is worth.