Created attachment 118783 [details] documents in docs and odt format It is noted that when saving the document in .docx format, table formats and images twist around and are not appealing, is it possible that you quality assure the layout in different formats please? See page 31 of the docx document attached to start with. Further reading 1. https://en.wikipedia.org/wiki/OpenDocument_technical_specification 2. https://ask.libreoffice.org/en/question/21580/which-is-the-best-docx-format/ and relevant links.
Confirmed the image on page 31 is not centered in its cell in a docx I saved. Image anchoring: ODT: Anchor to paragraph DOCX: Anchor as character Could not find a duplicate report. Frame positions + sizes + backgrounds on page 29 are also messed up in docx. Anchors match, though. Win 7 Pro 64-bit, Version: 5.0.1.2 (32-bit) Build ID: 81898c9f5c0d43f3473ba111d7b351050be20261 Locale: fi-FI (fi_FI) Version: 5.1.0.0.alpha1+ (x64) Build ID: 9ce08dcc2e32c5554ddf71b79173f8854e0568ad TinderBox: Win-x86_64@62-TDF, Branch:MASTER, Time: 2015-09-17_21:43:51 Locale: en-US (fi_FI)
** 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.1.6 or 5.2.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-20161108
Dear Jonathan Camilleri, 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 7.1+.
Created attachment 169034 [details] The offending part of the document in current Writer master Still the same in: Version: 7.2.0.0.alpha0+ (x64) Build ID: e828d62503d06ebde0e41dc2d6dcc87c2dc77173 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win Locale: hu-HU (hu_HU); UI: en-US Calc: CL The original is a frame with an image and caption inside. This is converted to a DML shape on export and that only supports "As character" anchoring in Word/docx. Writer generates this correctly, but the layout will change.
*** Bug 146450 has been marked as a duplicate of this bug. ***
*** Bug 140219 has been marked as a duplicate of this bug. ***
Bug 140219 comment 8 from Miklos: "docx only has to-char (anchored) and as-char (inline), so if the request is to preserve to-para in docx, that's a wontfix." Bug 140219 comment 11 from NISZ-Team: "It seems like the image is anchored to the beginning of the bulleted "Low Color Reference" paragraph and has a <text:soft-page-break/> in the odt, which is not exported to docx, but other properties seem to be exported fine. I'm not sure whether there is anything in docx that could be used here." So is there any solution?
Let's consider a duplicate so far. *** This bug has been marked as a duplicate of bug 135581 ***
*** This bug has been marked as a duplicate of bug 96579 ***