Bug 73481 - FILESAVE: Converting document from Word 97-2003 .doc format to 2007 .docx XML creates invalid WMF images
Summary: FILESAVE: Converting document from Word 97-2003 .doc format to 2007 .docx XML...
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.1.3.2 release
Hardware: Other Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-10 18:44 UTC by Alex
Modified: 2014-09-03 12:05 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments
example invalid .wmf file generated by LibreOffice (143.27 KB, image/x-wmf)
2014-01-10 18:44 UTC, Alex
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alex 2014-01-10 18:44:03 UTC
Created attachment 91838 [details]
example invalid .wmf file generated by LibreOffice

Tested on two different documents -- when opening a Word 97-2003 (.doc) document in LibreOffice and saving as Word 2007+ (.docx), the .wmf images that are created inside the .docx archive display properly in Word and LibreOffice, but they appear invalid as they cannot be opened in GIMP, ImageMagick, Photoshop, etc. after being extracted from the .docx archive.

This is a problem if trying to use LibreOffice to "normalize" content into preservation-friendly file formats from a Word 97-2003 source.
              
Operating System: Ubuntu
Version: 4.1.3.2 release
Comment 1 Alex 2014-01-10 18:49:51 UTC
Upon further research, this may actually be a regression in libwmf, which is probably used by both ImageMagick and GIMP: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1001570
Comment 2 retired 2014-01-11 22:41:06 UTC
Hi Alex thx for your report. Is this bug still valid / reproducible the latest pre-release 4.2.0.1: http://www.libreoffice.org/download/pre-releases/

Please also try resetting your user profile and let us know if that helps: https://wiki.documentfoundation.org/UserProfile

Should this be still reproducible for you with the latest LO release please set this bug back to UNCONFIRMED. Should this issue be solved set it to WORKSFORME.

Setting to NEEDINFO until more detail is provided.

Can you please provide a test document so this can be tested against and subsequently be confirmed. If your document contains sensitive data, please clear that or replace it with random information. Ideally the docx document which displays correctly under MS word but not in LO.
Comment 3 QA Administrators 2014-08-04 16:17:26 UTC
Dear Bug Submitter,

This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 
https://wiki.documentfoundation.org/QA/FDO/NEEDINFO

If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.


Thank you for helping us make LibreOffice even better for everyone!


Warm Regards,
QA Team
Comment 4 QA Administrators 2014-09-03 12:05:12 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided):

a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. 
Please do not:
a) respond via email 
b) update the version field in the bug or any of the other details on the top section of FDO