Bug 107756 - FILESAVE: RTF: after a single deleted character with revision tracking, the rest of the paragraph is exported as deleted in RTF
Summary: FILESAVE: RTF: after a single deleted character with revision tracking, the r...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.6.7.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:rtf
Depends on:
Blocks: RTF-Track-Changes
  Show dependency treegraph
 
Reported: 2017-05-10 16:52 UTC by Christian Nieber
Modified: 2025-06-22 03:13 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
example with a deleted comma. revision tracking disappears if this is saved in ODT format. (25.21 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2017-05-10 16:52 UTC, Christian Nieber
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Nieber 2017-05-10 16:52:10 UTC
Created attachment 133217 [details]
example with a deleted comma. revision tracking disappears if this is saved in ODT format.

The example contains a comma deleted with revision tracking. In RTF export, the (normal) rest of the paragraph is marked as deleted.
This bug is somewhat slippery, If I delete the next page, the bug goes away. Also I wasn't able to save the example in ODT format, since the revision marks disappear.
Comment 1 Buovjaga 2017-05-13 18:25:13 UTC
I confirm. What is the origin of this DOCX? Microsoft Office version xxxx?

It's already changing as RTF in 3.6, but in a different way. The ODT changes in the same way.

Arch Linux 64-bit, KDE Plasma 5
Version: 5.4.0.0.alpha1+
Build ID: c0968aa4673a8ac9a8a09a0e291b58b94bdbb35e
CPU threads: 8; OS: Linux 4.10; UI render: default; VCL: kde4; 
Locale: fi-FI (fi_FI.UTF-8); Calc: group
Built on May 13th 2016

Arch Linux 64-bit
Version 3.6.7.2 (Build ID: e183d5b)
Comment 2 Christian Nieber 2017-05-13 18:47:03 UTC
The docx was created With Word 2010 on Windows.
Comment 3 QA Administrators 2018-10-06 02:50:42 UTC Comment hidden (obsolete)
Comment 4 Roman Kuznetsov 2019-12-28 13:33:40 UTC
still repro in

Version: 6.5.0.0.alpha0+
Build ID: e22a3f596ce50b5166063e217d96ef674a54d380
CPU threads: 4; OS: Mac OS X 10.15.2; UI render: GL; VCL: osx; 
Locale: ru-RU (ru_RU.UTF-8); UI-Language: en-US
Calc: threaded
Comment 5 Sophie Sipasseuth 2023-06-22 12:31:41 UTC
The bug is still present in this version of Libre Office:

Version: 6.1.7.0.0+
Build ID: 5b3765f4d881e7ddefd0c4aad6886a46f000b4fc
CPU threads: 4; OS: Windows 10.0; UI render: default; 
Locale: fr-FR (fr_FR); Calc: CL
Comment 6 Sophie Sipasseuth 2023-06-22 12:33:50 UTC
Also here:

Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 174a72f3fd50d1146d6bedd4cc2a1971aa33be67
CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: default; VCL: win
Locale: fr-FR (fr_FR); UI: fr-FR
Calc: CL threaded
Comment 7 QA Administrators 2025-06-22 03:13:48 UTC
Dear Christian Nieber,

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