Created attachment 67283 [details] Example DOC and DOCX files and source ODT. Joined cells in table cause table distortion after save to doc and docx and reopen in LO. Steps to reproduce: 1. In writer insert any table. 2. Join some two or more cells. 3. Save as DOC (2003) and DOCX. 4. Reopen files in LO. In both cases table is distorted (in different way). Libreoffice 3.6.1.2 Windows 7, 32 bit.
Confirmed this bug, using the same ODF-file as V.K. I have have had the same problem exporting tables in MS Office formats (97, doc and 2007, docx) and getting a corrupted result, when reopening the files in LibreOffice 3.6.0.4. The two files exported from LO are read correctly by MS Word 2010 (Windows). The Word 97 file is read correctly by the slightly obsolete NeoOffice 3.1.2 p9 (based on Open Office), whereas the Word 2007 file is corrupted in NeoOffice, in the same way as in LO. Both LO and NeoOffice read the ODF file correctly. LibreOffice 3.6.0.4 OS X 10.8.1
Thanks for bugreport What about merged cells lost, slightly resembles this: Bug 35991 - merged cells in tables in DOC files not saved correctly by Writer What about distortion: Looks like 32-bit specific bug
Created attachment 68151 [details] test case for testing saving to doc with this file distortion happens when saving to doc format reproduced in 3.6.2 on Fedora 64 bit
changing version to 3.6.0 as most early reproduced
Bibisected both cases (saving as doc and docx).
Created attachment 87708 [details] sasha's test odt save as doc, shown in pdf file Tested in 4.1.2.3 Save sasha.libreoffice's test odt file as doc is totally in a mass, see the attached pdf.
Created attachment 87709 [details] sasha's test odt save as docx, shown in pdf file Tested in 4.1.2.3 When save sasha.libreoffice's test file as docx, it totally in a mass, and the page bocame portrait rather than landscape, see attached pdf.
(This is an automated message.) Setting priority to highest as this is a 4.1 MAB. This is part of an effort to make the importance of MAB reflected in priority too.
Confirmed on 4.3 built Sun Mar 23 23:07:35 2014 +0100 Quite serious - leaving as Major - Highest
bug still confirmed in later version (see comment above) moving to the mab4.2 list since 4.1.x is END OF LIFE
Removing bibisected keywords as from the comments it could have been introduced anywhere between 3.1.2 and 3.6.0.4 (Comment 1) and a bibisect could clarify.
still reproducible under Win8.1 64bit using LibO 4.3.4.1 and 4.5.0.0alpha moving bug to mab4.3 list since 4.2.x is END OF LIFE
Ubuntu 14.10 can not reproduce this with LO 4332 or 4.5 alpha 0
Problem with example from Comment 0 cannot be reproduced anymore. Title changed from "FILESAVE and FILEOPEN: Joined cells in table cause table distortion after save to doc and docx and reopen in LO" to "FILESAVE: Joined cells in table cause table distortion after save to DOC, DOCX (example in Comment 3)" (In reply to Kevin Suo from comment #7) > When save sasha.libreoffice's test file as docx, it totally in a mess Still so with LO 4.4.0. > the page became portrait rather than landscape. This may be some other bug, like Bug 88267 - Page orientation doesn't export to .doc/.docx. Just for a reference and a test. (In reply to sasha.libreoffice from comment #4) > changing version to 3.6.0 as most early reproduced This has never worked fine. So, doesn't seem to be a regression as marked. Looks inherited from OO for doc.
Updated version per last comment.
Issues with .docx export are not inherited from OOo by definition :) (they still don't support it). This bug should probably be split up into separate reports for the specific issues with the .doc and .docx filters, though that would take some investigation - bugs of the form "fix everything that is wrong with this file!" don't tend to be easy to attract developer attention to. Regardless, LO 3.3.0 doesn't export attachment 68151 [details] correctly to either .doc or .docx, so the remaining issues aren't regressions and can't be bibisected. Adjusting metadata to suit.
** 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
I can't repro. The DOC or DOCX exported from the ODT look fine to me (or I'm i missing something?) Version: 5.5.0.0.alpha0+ Build ID: 076ed447f694239d5c67adee528ea6e471d909ff CPU threads: 4; OS: Windows 6.19; UI render: default; TinderBox: Win-x86@42, Branch:master, Time: 2017-06-09_23:54:20 Locale: nl-NL (nl_NL); Calc: CL
Maybe Comment 14 and example in Comment 3. Still the same, wrong.
Created attachment 134790 [details] ODT vs. DOC screenshot bug still present in LibO 5.3.4.2 and recent 6.0.0.0 alpha daily buil. see attached screenshot.
** 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
This bug should've been closed for original report and new one opened for Sasha's example but with minimal test case.
Lowering importance: Highest + Inherit from OOo doesn't make much sense at this point anymore...
Dear V.K., 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://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
Dear V.K., 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