Bug 42112 - WMF/EMF from particular DOC file not properly loaded and shapes not visible (workaround : comment #14)
Summary: WMF/EMF from particular DOC file not properly loaded and shapes not visible (...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: graphics stack (show other bugs)
Version:
(earliest affected)
3.4.3 release
Hardware: All All
: medium normal
Assignee: Not Assigned
QA Contact:
URL:
Whiteboard:
Keywords: preBibisect, regression
Depends on:
Blocks:
 
Reported: 2011-10-22 07:25 UTC by Rpnpif
Modified: 2016-04-15 09:03 UTC (History)
8 users (show)

See Also:


Attachments
The doc file to test (73.00 KB, application/msword)
2011-10-22 07:27 UTC, Rpnpif
Details
The odt file after converting (32.03 KB, application/vnd.oasis.opendocument.text)
2011-10-22 07:28 UTC, Rpnpif
Details
The pdf file after converting (67.08 KB, application/pdf)
2011-10-22 07:29 UTC, Rpnpif
Details
screenshot of OpenOffice (13.96 KB, image/png)
2011-10-29 09:57 UTC, Rpnpif
Details
screenshot of LO (9.58 KB, image/png)
2011-10-29 09:57 UTC, Rpnpif
Details
The doc file to test - screenshot preview in LO 3.5.7.2 and 3.6.0.4 (64.40 KB, image/jpeg)
2015-02-23 09:53 UTC, Timur
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Rpnpif 2011-10-22 07:25:38 UTC
(All Linux, probably same with MS Windows). All releases of LO.

1. Load the Doc-et-graphique.doc (see attachment) in LO (all releases).
   The graphic draw is partially invisible.
2. Save as Doc-et-graphique.odt.
3. Reload Doc-et-graphique.odt. The graphic draw is still partially invisible.
4. Load Doc-et-graphique.doc in OpenOffice 3.2.1 or 3.3. All is fine. Graphic draw is full visible.
5. Load Doc-et-graphique.odt, created by LO, in OpenOffice. All is still fine.
6. With LO, export Doc-et-graphique.pdf. Graphic draw is wrong with same lacks (in Evince).
Comment 1 Rpnpif 2011-10-22 07:27:17 UTC
Created attachment 52631 [details]
The doc file to test
Comment 2 Rpnpif 2011-10-22 07:28:19 UTC
Created attachment 52632 [details]
The odt file after converting
Comment 3 Rpnpif 2011-10-22 07:29:51 UTC
Created attachment 52633 [details]
The pdf file after converting

This issue is important for usability of LO.
Comment 4 Rpnpif 2011-10-29 09:57:17 UTC
Created attachment 52894 [details]
screenshot of OpenOffice
Comment 5 Rpnpif 2011-10-29 09:57:57 UTC
Created attachment 52895 [details]
screenshot of LO
Comment 6 Rpnpif 2011-10-29 09:58:52 UTC
Same issue with LO 3.4.4-RC1
Comment 7 Cor Nouws 2011-10-31 04:40:05 UTC
.
Comment 8 A (Andy) 2013-01-20 12:59:05 UTC
reproducible with LO 3.6.4.3. (Win7 Home, 64bit)

in Word 2007 everything looks fine
Comment 9 Urmas 2013-02-19 18:25:07 UTC
*** Bug 61058 has been marked as a duplicate of this bug. ***
Comment 10 Rpnpif 2013-03-24 18:35:19 UTC
(In reply to comment #9)
> *** Bug 61058 has been marked as a duplicate of this bug. ***

Hi,
I think that it is an error : Bug 61058 is not a duplicate of this bug. (confusion with 42122).
This comment is for archives.
Comment 11 Rpnpif 2014-06-21 09:35:06 UTC
Same bug with LO 4.2.5.2, Build ID: 61cb170a04bb1f12e77c884eab9192be736ec5f5.
Comment 12 Rpnpif 2014-09-01 04:55:24 UTC
This bug is still existing in LO 4.3.1.2.
Comment 13 Timur 2014-12-09 16:35:38 UTC
(In reply to Rpnpif from comment #6)
> Same issue with LO 3.4.4-RC1

Reproduced in Windows, but not with that version. Testing in Win 7 x64:
- Document opens fine in OO and in LO 3.4 and also fine in 3.5.
- Starting from 3.6.0 up to now (4.3.4 and 4.4.0 beta) preview is wrong and  shapes are not visible.

So it's not "regression against OO" and I delete that from the title, but Regression keyword remains. MS Word says "Microsoft Word Picture" for this object, so I change that in title also.

Double click on object opens it fine but in another Writer window. There, it can be edited, but it can't be closed and have object updated in the original Writer document, as it should and as Word does. This should be another bug, if not already reported.
Comment 14 Rpnpif 2014-12-10 10:53:38 UTC
(In reply to Timur from comment #13)

Hi,

I had not seen what you wrote about 3.4 or 3.5 releases. So do not get too hasty conclusions. Perhaps, now it is another bug.

It is a regression against OO from which LO comes. I think that you should not edit the summary thus.

But you are right with your workaround :

Double-click on the object that opens itself in another window. Then copy-paste this new object instead of the original object. Save on disk.
With LO 4.4 on Debian Linux, the reopen of this new file works fine.

So you are right : the bug is concerning NOW (with LO 4.3.4) the loading code.

Perhaps, this will give ideas to developers.
Comment 15 retired 2015-01-05 20:28:05 UTC
Arrows and thin line still missing.
OS X 10.10.1 LO 4.5 Version: 4.5.0.0.alpha0+
Build ID: 2d59c0c940ac61240992502256c966b2cb4f9daa
TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2015-01-04_01:16:22
Locale: de_
Comment 16 Jean-Baptiste Faure 2015-02-21 22:27:49 UTC
(In reply to Timur from comment #13)
> [...]
> Double click on object opens it fine but in another Writer window. There, it
> can be edited, but it can't be closed and have object updated in the
> original Writer document, as it should and as Word does. This should be
> another bug, if not already reported.

You can then copy&paste the graphics from a Writer window to the other. Then saving, closing, reopening works fine.

Tested with LibreOffice 4.4.2.0.0+ built at home under Ubuntu 14.10 x86-64.

Best regards. JBF
Comment 17 Timur 2015-02-23 09:53:12 UTC
Created attachment 113618 [details]
The doc file to test - screenshot preview in LO 3.5.7.2 and 3.6.0.4
Comment 18 Timur 2015-02-23 10:00:09 UTC
(In reply to Rpnpif from comment #14)
> It is a regression against OO from which LO comes. I think that you should
> not edit the summary thus.
Regression against OO means that bug doesn't exist in OO and exists in the first version after that, LO 3.3.0. It's not the case here. Version is where bug started to appear. 
According to "The doc file to test - screenshot preview in LO 3.5.7.2 and 3.6.0.4" I change version to 3.6.0.4.
Comment 19 Rpnpif 2015-02-23 18:27:43 UTC
@Timur : The policy of this bugs site says that the version must be "The earliest version of the software in which the bug can be reproduced."

https://bugs.documentfoundation.org/page.cgi?id=fields.html#version

So I remove your change.

Regards.
Comment 20 Rpnpif 2015-09-04 15:59:01 UTC
This issue that was now minor by the workaround, is reproducible in LO 5.0.1.1.
Comment 21 Robinson Tryon (qubit) 2015-12-14 05:40:06 UTC
Migrating Whiteboard tags to Keywords: (preBibisect)
[NinjaEdit]
Comment 22 Rpnpif 2015-12-27 11:28:38 UTC
This issue is still present in Version 5.1.0.1.
Comment 23 Jean-Baptiste Faure 2016-04-15 04:38:48 UTC
How the original bugdoc (https://bugs.documentfoundation.org/attachment.cgi?id=52631) has been created? By using MSWord (which version) or by using LO or OOo ?

Best regards. JBF
Comment 24 Rpnpif 2016-04-15 08:36:32 UTC
(In reply to Jean-Baptiste Faure from comment #23)
> How the original bugdoc
> (https://bugs.documentfoundation.org/attachment.cgi?id=52631) has been
> created? By using MSWord (which version) or by using LO or OOo ?

It is an old file created by MSWord 97, perhaps modified by Openoffice 3.x.
Comment 25 Jean-Baptiste Faure 2016-04-15 09:03:05 UTC
(In reply to Rpnpif from comment #24)
> (In reply to Jean-Baptiste Faure from comment #23)
> > How the original bugdoc
> > (https://bugs.documentfoundation.org/attachment.cgi?id=52631) has been
> > created? By using MSWord (which version) or by using LO or OOo ?
> 
> It is an old file created by MSWord 97, perhaps modified by Openoffice 3.x.

So, we don't know if the bug is an import bug in LO or an export bug in OOo.
I think that a progress in fixing this bug is possible only if we are able to decide between both possibilities. If the file has been modified by OOo before being imported by LO, I think we can close this bug report as WontFix because we can't repair OOo. The workaround from comment #14 shows that the file itself can be repaired.

If the file has not been modified by a MS-Office program, it is another story.

Best regards. JBF