Bug 51920 - FILESAVE: Tracked changes not correctly saved in .doc format
Summary: FILESAVE: Tracked changes not correctly saved in .doc format
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.5.3 release
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-09 17:01 UTC by Matthias Pfau
Modified: 2015-01-29 16:38 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
The cause of the problem: Flags for which changes should be displayed are written wrong (139.03 KB, image/png)
2012-07-09 17:01 UTC, Matthias Pfau
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Matthias Pfau 2012-07-09 17:01:04 UTC
Created attachment 64032 [details]
The cause of the problem: Flags for which changes should be displayed are written wrong

Problem description:
If you track changes in Libre Office and store the document as .doc and open the document with MS Word, the changes are not visible. This makes Libre Office pretty unusable in collaboration scenarios.

The behavior is absolutely independent of the Libre Office setting "Edit > Changes > Show".

The problem is caused by writing wrong flags for which changes should be displayed into the .doc (see screenshot).

Steps to reproduce:
1. Create a new document in libre office and fill it with a sample text
2. Save the document as test.doc
3. Enable track changes
4. Make some changes
5. Save the document
6. Open the document in MS Word

Current behavior:
The changes are not displayed.

Expected behavior:
The changes are displayed in MS Word just like in Libre Office

Platform (if different from the browser): Windows 7, Ubuntu 12.04
              
Browser: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.19 (KHTML, like Gecko) Ubuntu/12.04 Chromium/18.0.1025.168 Chrome/18.0.1025.168 Safari/535.19
Comment 1 Joel Madero 2012-09-18 16:14:34 UTC
I am changing back to default priority. Please do not escalate a bug past the priority that it is, ie. Critical implies crashing, loss of work, etc...this is not a critical bug. I am marking as default, Normal - Medium and then I'll deal with really prioritizing it later.
Comment 2 QA Administrators 2015-01-05 17:52:02 UTC
** 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.3.5 or later): 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)

Thank you for your help!

-- The LibreOffice QA Team
Comment 3 Buovjaga 2015-01-29 16:38:27 UTC
Looks like this has been fixed. Closing as WFM.

Win 8.1 32-bit
MSO 2013

LibreOffice Version: 4.5.0.0.alpha0+
Build ID: 784d069cc1d9f1d6e6a4e543a278376ab483d1eb
TinderBox: Win-x86@62-TDF, Branch:MASTER, Time: 2015-01-25_23:07:36