Bug 83306 - FILEOPEN: Regression importing .docx files with Autoshape images
Summary: FILEOPEN: Regression importing .docx files with Autoshape images
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Drawing (show other bugs)
Version: 4.4.0.0.alpha0+ Master
Hardware: Other Windows (All)
: medium normal
Assignee: Not Assigned
QA Contact:
URL:
Whiteboard: filter:docx
Keywords: regression
Depends on:
Blocks:
 
Reported: 2014-08-31 18:04 UTC by Luke
Modified: 2015-01-12 08:48 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments
Comparison of Writer 4.3 vs 4.4 (157.79 KB, image/png)
2014-08-31 18:04 UTC, Luke
Details

Description Luke 2014-08-31 18:04:36 UTC
Created attachment 105497 [details]
Comparison of Writer 4.3 vs 4.4

This bug was discovered in a LO 4.4 running in windows 7. LibreOffice 4.4 importer puts extra lines in  MS Office docx files with autoshapes. I have attached an example.

Steps to reproduce the bug:
1. Open attachment 81230 [details] AutoShapedrawing.docx document in Writer 4.3 
2. Open attachment 81230 [details] AutoShapedrawing.docx document in Writer 4.4.x
3. Compare the documents.

Note the additional stray line in Windows that does not exist in Linux. Ever since LO started supporting AutoShapes, it has not handled nested shapes properly(Bug 66058), but this regression in Windows makes it look even worse.
Comment 1 Jacques Guilleron 2014-08-31 21:50:22 UTC
Hi Luke,

I reproduce with LO 4.4.0.0.alpha0+
Build ID: 37b9ea92ba81d74764a2345a9c75c65bfd272d2b
TinderBox: Win-x86@42, Branch:master, Time: 2014-08-26_09:37:01
& Windows 7 Home Premium

regards,

Jacques
Comment 2 Xisco Faulí 2014-10-30 14:16:54 UTC
I change the software field to Windows (All) as this can't be reproduced in Linux
Comment 3 foss 2015-01-12 08:48:43 UTC
just another data point:
no repro on OSX 10.10.1 LO 4.4.2 and 4.5.0 (from today)


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.