The "Edit>Compare Documents" command does not detect changes in tables properly.
If I make a minor change in a table, Writer has the following problems:
(1) The whole table is shown as "deleted",
(2) A new table (with the changed cell) is shown as "inserted".
The impression is that Writer treats the table as atomic change (it cannot detect changes at cell/row/column level).
(3) While the Writer shows one deleted table and one inserted table, the "Accept or reject changes" window does not have related entries.
Even if you go through all entries in this window one by one, Writer will never highlight the inserted table OR the deleted table, and offer you to accept or reject that particular change.
In other words, the earlier impression that "Writer treats entire table as a single unit" does not hold true now!
(4) The "Accept or reject changes" window can highlight only the first and last cells of inserted table; not the entire "inserted" table.
Note that these cells may not be changed at all!
(5) The "Accept or reject changes" window can NOT highlight the deleted table at all.
(6) The actually changed cell (which should have been the SOLE focus of this exercise) is NOT highlighted at all.
To sum up, the Writer misses the entire point of highlighting just the changes, and letting the user decide whether to accept it.
I conducted an experiment, in which I created a simple document with some text and a table. I duplicated that document and added a small text to one cell of the table.
Then I compared these documents using Edit>Compare documents.
I turned on the Edit>Changes>Show option.
I also turned on the Edit>Changes>Accept or reject... option.
I took screenshot of this result, and created a third document called "analysis" to explain what exactly is wrong.
All three documents are attached.
Also see Bug#44847.
Created attachment 66123 [details]
The "Compare documents" command cannot handle changes in a table
There are three files:
1. Original (contains free-flowing text and a table)
2. Modified (contains some small edits in both the text and table)
3. Analysis of the problem (contains annotated screenshot and analysis)
reproducible with LO 18.104.22.168. (Win7 Home, 64bit)
If you have in the table e.g. two changes and you want to accept one and one not then you can also not distinguish that.
** 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 (4.4.2 or later)
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 your help!
-- The LibreOffice QA Team This NEW Message was generated on: 2015-05-02
1. New Text Document.
2. Table → Insert Table: 2 x 2.
3. Type “test” in each cell.
4. Save document.
5. Select “test” in cell A2 and delete.
6. Save document with different name.
7. Edit → Compare Document → Select first document and Open.
There are two tables. Manage Changes shows an insertion and a deletion. The insertion shows cells A1 and B2 highlighted. The deletion does not highlight anything.
One table with redlining showing strikethrough of “test” and Manage Changes showing a deletion.
Build ID: 88805f81e9fe61362df02b9941de8e38a9b5fd16
Yes, I have revealed this bug in 5.0.2, 5.0.4 and 5.1 release. It's awfully, because there are a lot of documents including big tables.
Created attachment 134441 [details]
Created attachment 134442 [details]
A little gift to this bugs 14th(*) birthday: Use LibreOffice Writers "Edit -> Track changes -> Compare Document ..." feature to find out the difference between the two documents Original.odt and Changed.odt you find in the attachments. Hint: Their contents differ by a single character.
*** Bug 116139 has been marked as a duplicate of this bug. ***
*** Bug 120184 has been marked as a duplicate of this bug. ***
Michael/Miklos: It seems LO can only compare a whole table.
Here the steps I did on pc Debian x86-64 with master sources updated today:
- Created a brand new odt file
- Inserted a table 2x2
- Inserted "Test1" in each cell
- Saved the file into Test1.odt
- Changed one cell with Test2
- Saved as the file into Test2.odt
- Compared both files
=> the whole table is indicated.
I put some traces on SwCompareLine::CompareNode (see https://opengrok.libreoffice.org/xref/core/sw/source/core/doc/doccomp.cxx?r=525f75b7#1112
"SimpleTableToText" seems to take the whole table.
(I put you both of you on cc because I didn't know whom to ping about this).
I found this problem very annoying. While this bug is not resolved for 8 years,
I propose a dirty workaround - add a command 'convert ALL tables to text',
similar to 'convert table to text', but in a single command, so that it will be possible to at least quickly review changes.
(In reply to kkivi from comment #12)
> I propose a dirty workaround - add a command 'convert ALL tables to text',
> similar to 'convert table to text', but in a single command, so that it will
> be possible to at least quickly review changes.
A workaround that's available today: Convert the whole document to text using a command-line tool (https://www.systutorials.com/3-ways-of-odt-to-txt-file-conversion-in-command-line-in-linux/ has a few decent options) and then diff the text files using a word-diff tool (I'm abusing "git diff --no-index --word-diff=color" since Git is available for many OSes). That's what I'm using; it's adequate for my current needs.