Created attachment 86247 [details]
DOCX containing a table with deleted cells
When loading the attached DOCX into LO and exporting back to DOCX - the deleted cells in the original DOCX's table become 'merged' cells in the exported DOCX.
Steps to reproduce:
1. Load the attached DOCX in LO
2. Save as NEW.DOCX
3. Load the NEW.DOCX in Word
4. Table contains no deleted cells
LO exports the table with no deleted cells (deleted cells are turned to merged cells in the table).
LO should export the table with the deleted cells.
Operating System: All
Version: 188.8.131.52.alpha0+ Master
Created attachment 86248 [details]
DOCX exported by LO with no deleted cells
Created attachment 86249 [details]
Screenshot comparison between original DOCX and exported DOCX
Thank you for your bug report,
I can reproduce this bug running LibreOffice:
Build ID: 164b6ce7b27c0a9ec19019e7b078b9f8f382007d
TinderBox: Win-x86@39, Branch:master, Time: 2013-09-28_16:39:4
And Mircosoft Word 2007
Adam Co committed a patch related to this issue.
It has been pushed to "master":
fdo#69644 - fix docx export of wrong number and width of columns
The patch should be included in the daily builds available at
http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
Affected users are encouraged to test the fix and report feedback.
This doesn't seem fixed, tested with LO 4.4.0.
Also not Filesave problem, but rather Fileopen problem, because LO opens wrong, as shown in the screenshot.
I change title from "FILESAVE: DOCX Export loses deleted cells from table (table now has no deleted cells)" to "FILEOPEN: Writer opens DOCX with cells already deleted from table".
** 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.5 or 5.2.1 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)
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!
Build ID: 33f5bc54aaa7fe7aa9335726e30f9c349155e04d
CPU Threads: 4; OS Version: Windows 6.2; UI Render: default;
TinderBox: Win-x86@62-merge-TDF, Branch:MASTER, Time: 2016-12-01_23:21:05
Locale: nl-NL (nl_NL); Calc: CL
*** Bug 69657 has been marked as a duplicate of this bug. ***