Created attachment 123545 [details] incorrect position 1. create a blank odt document 2. create a paragraph with some value in "Spacing to contents"-"left" (for better visualisation fill the area but it is not necessary) 3. Result is now as expected, i.e. paragraph area starts at page border and first character starts at position paragraph area + set value of "Spacing to contents"-"left" 4. Save the document in docx format 5. open the document in docx format 6. Result is now incorect, i.e. paragraph area starts at position of page boarder minus "Spacing to contents"-"left" so that the first character starts at page boarder What makes this bug major is, that the formatting of the document is broken irreversibly, i.e. even after saving again as odt and formatting a new paragraph from scratch, the result is incorrect and the only workable solution, I have found, is creating a new document and copy paste the content. Otherwise alignment of all paragraph with non-zero value of "Spacing to contents"-"left" is broken.
Hi Ivo, Thanks for reporting. I do not see the issue in 5.0.5.2 or 5.1.1.1 Can you pls attach your test document? Ciao - Cor
Created attachment 123557 [details] example of affected docx Generated in LO Version: 5.1.1.2 Build ID: 1:5.1.1~rc2-0ubuntu1~trusty0 CPU Threads: 4; OS Version: Linux 3.19; UI Render: default; Locale: cs-CZ (cs_CZ.UTF-8)
You are asked to attach original ODT. Please clarify what's "Spacing to contents"-"left", is it indent "before text", or "first line"?
Created attachment 124158 [details] original correct odt document
Created attachment 124159 [details] picture explaining the problem
Repro. Arch Linux 64-bit, KDE Plasma 5 Version: 5.2.0.0.alpha1+ Build ID: 540fee2dc7553152914f7f1d8a41921e765087ef CPU Threads: 8; OS Version: Linux 4.5; UI Render: default; Locale: fi-FI (fi_FI.UTF-8) Built on April 30th 2016
In 4.3.7.2 and daily, the result is a negative indent of the paragraph In 3.4.6.1. and 4.0.0.1 the result is a lost spacing to contents (and an added Outline number to the following paragraph of the test file...)
** 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 on a currently supported version of LibreOffice (5.2.7 or 5.3.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170522
still not ok in Version: 6.0.0.0.alpha0+ Build ID: 368b583b992f2e9cad46c2362c9529a07c36d7a9 CPU threads: 4; OS: Linux 4.10; UI render: default; VCL: gtk2; TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2017-08-10_02:55:46 Locale: nl-NL (nl_NL.UTF-8); Calc: group
** 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
Repro 6.2+. But this is related to Bug 95576, heading style.
Created attachment 159414 [details] 98639_borderSpacing.odt: based on default style - no heading style used. (In reply to Timur from comment #11) > Repro 6.2+. But this is related to Bug 95576, heading style. It is not related to heading style at all. Confirmed in 7.0 master for exporting both as .doc and .docx.
NOTABUG. Try it this way. Create a blank document, save it as .docx, and then close and re-open the blank document that is now in DOCX format. Now when you make your border, it will push into the left and right margins. This is almost certainly due to a compatibility option in order to work the way Microsoft formats work. For example, MS formats have a maximum of 31pt for the border spacing - much less than LO can do. When you save as an MS format, you are stuck with the limitations there. The compatibility was most likely introduced in LO 4.0 with commit 355d25eac764713f4d52eac801ade6e2ff1deab0 by Author: Cédric Bosdonnat on Wed Sep 19 16:19:37 2012 +0200 n#779627: added quite some compat options from the ww8 filter on writerfilter