https://bugs.documentfoundation.org/show_bug.cgi?id=147655

[email protected] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |UNCONFIRMED
     Ever confirmed|1                           |0

--- Comment #4 from [email protected] ---
Here are steps to reproduce the issue, without requiring an existing document.
The problem only occurs for me when either "Deletions in Margin" or "Insertions
in Margin" is enabled.

Libre Office 7.4.0.3 (x64), Windows 10.

1. Open Writer.
2. Create a new document (File → New → Text Document).
3. Make sure "Record Track Changes" is disabled for now.
4. Type or paste any badly written text, e.g. "Hello, Misterrr Boo, how are".
5. Enable "Record Track Changes" and "Show Tracked Changes".
6. Correct the text by deleting something and inserting something, e.g. delete
the extra r's in "Misterrr", and insert " you?". at the end, resulting in a
correct sentence: "Hello, Mister Boo, how are you?". (Do not simply copy-paste
the correct sentence over the old sentence: we need to actually make a deletion
and an insertion.)
7. CRUCIAL STEP: In the little dropdown menu at View Track Changes, pick
"Deletions in Margin". (It doesn't matter 
8. Save the document as a .DOCX file.
9. Close the document.
10. Reopen the file.

You will now see somewhat unpredictable data loss. The deletion "rr" has
disappeared altogether. The part "Boo, how are" is marked as a deletion even
though it should be marked as unchanged text. The insertion "you?" is shown as
unchanged text even though it should be marked as an insertion.

If you then disable "Show Tracked Changes", you will see that it is not just a
display issue: the words incorrectly marked as a deletion have actually
disappeared.

The problem even occurs if you disable "Show Tracked Changes" after picking
"Detetions in Margin" and before saving the document.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to