Bug 44904 - FORMATTING error when open existing file with formarted header
Summary: FORMATTING error when open existing file with formarted header
Status: RESOLVED DUPLICATE of bug 43695
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.5.0 Beta3
Hardware: x86-64 (AMD64) Windows (All)
: medium major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-18 08:01 UTC by christof.spies
Modified: 2012-01-18 08:54 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
LO Writer file (119.67 KB, application/vnd.oasis.opendocument.text-template)
2012-01-18 08:01 UTC, christof.spies
Details
Screenshot OK (21.66 KB, image/png)
2012-01-18 08:01 UTC, christof.spies
Details
Screenshot broken format (15.41 KB, image/png)
2012-01-18 08:02 UTC, christof.spies
Details

Note You need to log in before you can comment on or make changes to this bug.
Description christof.spies 2012-01-18 08:01:01 UTC
Created attachment 55738 [details]
LO Writer file

Open the attached file.
The header is bad formated with
LOdev 3.5.0beta3 
Build-ID: e40af8c-10029e3-615e522-88673a2-727f724

Header is ok with
LibreOffice 3.4.5 
OOO340m1 (Build:502)

I'm working with W7 64bit.
Comment 1 christof.spies 2012-01-18 08:01:36 UTC
Created attachment 55739 [details]
Screenshot OK
Comment 2 christof.spies 2012-01-18 08:02:23 UTC
Created attachment 55740 [details]
Screenshot broken format
Comment 3 Rainer Bielefeld Retired 2012-01-18 08:25:42 UTC
This seems to be a DUP of "Bug 43695 - VIEWING for particular picture configuration broken" except reporter can explain detailed why view in 3.4. is correct and in 3.5 is wrong.
Comment 4 christof.spies 2012-01-18 08:43:29 UTC
Yes, seam that the LO 3.4.5 is handling the wrapping information of the picture in the wrong way.
And LO 3.5.beta is doing it correct now.
Changing the wrapping settings of the picture correct is fixing the problem.
Comment 5 christof.spies 2012-01-18 08:54:44 UTC

*** This bug has been marked as a duplicate of bug 43695 ***