Bug 50481 - Writer FILEOPEN: recorded changes in DOC file shown incorrectly, whole document shown as changed
Summary: Writer FILEOPEN: recorded changes in DOC file shown incorrectly, whole docume...
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.5.3 release
Hardware: x86-64 (AMD64) Linux (All)
: high normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords: bibisected, regression
Depends on:
Blocks:
 
Reported: 2012-05-29 18:59 UTC by andre.piotrowski
Modified: 2015-12-17 06:52 UTC (History)
6 users (show)

See Also:
Crash report or crash signature:


Attachments
A short example "doc" file saved by Papyrus (3 one line paragraphs, the first replaced by another, tracing of changes activated, the deleted line contains an "ö" ) (2.46 KB, application/msword)
2012-05-29 18:59 UTC, andre.piotrowski
Details
What I see: A snapshot of the corresponding doc file opened with LO. (22.34 KB, image/jpeg)
2012-05-29 19:07 UTC, andre.piotrowski
Details
The same as the first example, but with "o" instead of "ö". (2.46 KB, application/msword)
2012-05-29 19:09 UTC, andre.piotrowski
Details
What I see: A snapshot of the second doc file opened with LO. (25.34 KB, image/jpeg)
2012-05-29 19:11 UTC, andre.piotrowski
Details
First attachment, saved as PDF using msWord 2007 (24.47 KB, application/pdf)
2012-11-10 07:49 UTC, sasha.libreoffice
Details

Note You need to log in before you can comment on or make changes to this bug.
Description andre.piotrowski 2012-05-29 18:59:11 UTC
Created attachment 62248 [details]
A short example "doc" file saved by Papyrus (3 one line paragraphs, the first replaced by another, tracing of changes activated, the deleted line contains an "ö" )

Problem description: 
LibreOffice doesn't read text files correctly that are saved with Papyrus (using WINE) when tracing of changes is active.

Steps to reproduce:
1. Write a text file with Papyrus, three paragraphs.
2. Enable tracing of changes.
3. Replace the entire first paragraph.
4. Save the file as doc file.
5. Open the file with LibreOffice.

Current behavior:
One behaviour (it's not always the same): The third paragraph is displayed in a wrong position. It can be (for instance, when the deleted first parapraph contains a german umlaut accent), that the second and third paragraph are marked as deleted. (Long files take extreme long time to load because of the "neverending" changes.)

Expected behavior:
Guess… (Papyrus displays the file as expected.)

Platform (if different from the browser): 
              
Browser: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:12.0) Gecko/20100101 Firefox/12.0
Comment 1 andre.piotrowski 2012-05-29 19:07:16 UTC
Created attachment 62249 [details]
What I see: A snapshot of the corresponding doc file opened with LO.
Comment 2 andre.piotrowski 2012-05-29 19:09:56 UTC
Created attachment 62250 [details]
The same as the first example, but with "o" instead of "ö".
Comment 3 andre.piotrowski 2012-05-29 19:11:15 UTC
Created attachment 62251 [details]
What I see: A snapshot of the second doc file opened with LO.
Comment 4 andre.piotrowski 2012-05-31 01:08:30 UTC
These docs are displayed correctly by Word 2004 and OpenOffice 3.3
(on a Mac mini, Mac OS X 10.4.11)
Comment 5 Robert Großkopf 2012-09-29 10:09:57 UTC
Can't confirm the bug with openSUSE 12.1 64bit rpm and LO 3.6.2.1.
Could you please test it with a newer version of LO?
Comment 6 Thomas Hackert 2012-09-29 10:22:32 UTC
Hello Andre, 
I cannot confirm this bug with Debian Testing x86 on my eeePC 1000H with LO Version 3.6.2.2 (Build ID: da8c1e6). Would you be so kind to test this issue with a newer version of LO than 3.5.3, please? It would be interesting to see, if this issue is still valid in 3.6.x. If it is still valid, it would be nice, if you can give us some more information about your hardware, graphics driver, java version and the like ... ;)
HTH
Thomas.
Comment 7 sasha.libreoffice 2012-11-09 12:54:29 UTC
I see that in document used font "Arial regular". May be problem is with this font. I have installed it, but it not helps in reproducing problem.
[not reproduced] in 3.5.7 and 3.6.3 on RFR 17 64 bit
Comment 8 Urmas 2012-11-10 07:24:12 UTC
All paragraphs are marked as deleted in 3.6.3.2.
Comment 9 sasha.libreoffice 2012-11-10 07:49:42 UTC
Created attachment 69854 [details]
First attachment, saved as PDF using msWord 2007
Comment 10 sasha.libreoffice 2012-11-10 07:57:50 UTC
Indeed, in Word two last lines not stroked out, as shown in attachment.
Initially I thought that problem is that in LO two last rows is shown one over another, as shown on screenshots. Sorry for not understand problem from first attempt.

not reproduced in 3.4.2 on Windows XP 32 bit, therefore regression beginning from 3.5.0 version
[reproduced] in 3.5.0 beta 3 on Windows XP 32 bit
[reproduced] in 3.6.3 on RFR 17 64 bit
Comment 11 Robinson Tryon (qubit) 2013-10-19 00:11:38 UTC
Remove comma from whiteboard.
Comment 12 Mirosław Zalewski 2013-10-24 14:42:02 UTC
All tests done on Linux Debian, amd64.

I could reproduce problem on 4.0.6 released today, but I could NOT reproduce it on 4.1.2.

I tried to bibisect this issue. It was not easy, as it was fixed in master, not introduced; and git does not support that workflow.

Anyway (commit id are from LO git, not bibisect git history): 7908692490120350f2ad45241f7b19ba52dc0489 - last version where this bug is visible d9bfa462ba8dd0a966fe913fad49f300ea48f638 - test file can not be opened, LO shows "General input/output error" edba90dc39fc3141a8a9e441aa97b46baa4c6ca2 -last version where "general I/O" error message is shown 90a2c73f903b8d07b52dc7774fd7296b2bf0c125 - bug can NOT be reproduced

So, it seems to be fixed in master somewhere between 12 July and 20 August (most likely between 17 August and 20 August). Whatever fixed that, seems to be backported to 4.1.2, as this one is not affected.

4.0.6 was the last release from 4.0 line. It is affected, but I see little chance to see it fixed there (unless there will be unplanned release and we manage to find and backport fix).

All in all, I think we can close this bug as fixed. 4.0 users will eventually switch to 4.1, where this is fixed.

If there are no objections, I will mark this as RESOLVED FIXED in two weeks from now.
Comment 13 Mirosław Zalewski 2013-11-07 21:39:23 UTC
Since no one commented since my last comment, I am closing this.
Comment 14 Joel Madero 2013-11-07 21:41:26 UTC
I believe WFM is right status as we don't have the patch/author of the fix - updating
Comment 15 Robinson Tryon (qubit) 2015-12-17 06:52:27 UTC
Migrating Whiteboard tags to Keywords: (bibisected)
[NinjaEdit]