Bug 60413 - Images in header disappear in Word for Mac OSX after save to Word 97 format
Summary: Images in header disappear in Word for Mac OSX after save to Word 97 format
Status: RESOLVED NOTOURBUG
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: filters and storage (show other bugs)
Version:
(earliest affected)
3.6.5.2 release
Hardware: x86-64 (AMD64) All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisectRequest, filter:doc, regression
Depends on:
Blocks: DOC-Header-Footer
  Show dependency treegraph
 
Reported: 2013-02-07 11:37 UTC by fabien.michel
Modified: 2019-11-02 15:46 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:


Attachments
Sample file (13.82 KB, application/vnd.oasis.opendocument.text)
2013-02-07 11:37 UTC, fabien.michel
Details
Sample fiel saved as .doc (13.50 KB, application/msword)
2013-02-07 11:38 UTC, fabien.michel
Details
Result in Word 2011 (125.96 KB, image/png)
2013-02-07 11:39 UTC, fabien.michel
Details
Sample file (13.82 KB, application/vnd.oasis.opendocument.text)
2013-02-07 11:39 UTC, fabien.michel
Details
Sample file saved as .doc (13.50 KB, application/msword)
2013-02-07 11:40 UTC, fabien.michel
Details
message in header when opening docx in Word for Mac 2011 (20.82 KB, image/png)
2013-02-07 17:39 UTC, Jorendc
Details
Sometime it work on Word for Mac 2011 (157.74 KB, image/png)
2013-02-08 09:37 UTC, fabien.michel
Details
DOC exported with 3.5.0 (oldest of 43all Linux bibisect repo) (13.50 KB, application/msword)
2018-06-28 11:36 UTC, Buovjaga
Details

Note You need to log in before you can comment on or make changes to this bug.
Description fabien.michel 2013-02-07 11:37:46 UTC
Created attachment 74330 [details]
Sample file

Steps to reproduce :
 - Create empty writer file.
 - Insert header
 - Insert picture (jpg or png) in the header.
 - Save the file in word 97 format (.doc)
 - Open this file in MS Office 2011 (yes, on mac)

The image in header is invisible but still selectable. In Word 2011 if you change the transparency of the picture value then reset it to zero, the image re-appear.

This doesn't occur if the image is in the footer or the body.
This doesn't occur if the file is saved as .docx
I have not been able to reproduce with word 2003 on Win XP.
Comment 1 fabien.michel 2013-02-07 11:38:25 UTC
Created attachment 74331 [details]
Sample fiel saved as .doc
Comment 2 fabien.michel 2013-02-07 11:39:09 UTC
Created attachment 74332 [details]
Result in Word 2011
Comment 3 fabien.michel 2013-02-07 11:39:37 UTC
Created attachment 74333 [details]
Sample file
Comment 4 fabien.michel 2013-02-07 11:40:02 UTC
Created attachment 74334 [details]
Sample file saved as .doc
Comment 5 Jorendc 2013-02-07 17:39:03 UTC
I can confirm this behavior using Mac OSX 10.8.2 and LibreOffice 4.0 final.

I created a new document following your steps and save it as doc and docx. I open both documents in Word for Mac 2011. When I open the doc I can confirm attached screenshot. When I open the docx there'll be a message (see attached image).

Kind regards,
Joren
Comment 6 Jorendc 2013-02-07 17:39:43 UTC
Created attachment 74366 [details]
message in header when opening docx in Word for Mac 2011
Comment 7 fabien.michel 2013-02-08 09:37:31 UTC
Created attachment 74413 [details]
Sometime it work on Word for Mac 2011
Comment 8 fabien.michel 2013-02-08 09:38:08 UTC
Very strange, I do not reproduce this error with docx format in Word 2011 on MacOS 10.7.5. I've posted an attachement similar to Jorendc one.
Comment 9 QA Administrators 2015-04-19 03:20:09 UTC Comment hidden (obsolete)
Comment 10 Julien Nabet 2016-07-03 09:50:33 UTC Comment hidden (obsolete)
Comment 11 Alex Thurgood 2016-09-01 12:35:37 UTC
Bug still present when open doc file in Word 2011 that was produced with

LibreOffice Version: 5.2.0.4
Build ID: 066b007f5ebcc236395c7d282ba488bca6720265
CPU Threads: 2; OS Version: Mac OS X 10.11.6; UI Render: default; 
Locale: en-GB (fr.UTF-8)
Comment 12 Alex Thurgood 2016-09-01 12:38:38 UTC
Same problem occurs when loading the doc file into Word 15.25 (Office 2016) for OSX.
Comment 13 Xisco Faulí 2017-09-29 08:48:44 UTC Comment hidden (obsolete)
Comment 14 eisa01 2017-11-05 20:17:00 UTC
Still present. The .doc does not show the header image in Word 15.39

Did a couple tests to confirm this being an issue with all LibreOffice OSes when opened on Mac Word.
If I open the Mac produced .doc in Windows Word 2007, then the header image do show
If I open the Windows produced .doc in Mac Word 2016, then the header image don't show
If I open a Windows Word 2007 produced .doc from the .docx LibreOffice Mac export, the the image shows in Windows Word and Mac Word

So the .doc that LibreOffice produces in both Windows and Mac version can't be read properly by Word for Mac.

Workaround is to use .docx

This was not present in a .doc export from Mac LO 3.3, so this is a regression. To bibisect this we would have to get sample documents from a Linux repository?

Setting OS to all

Version: 6.0.0.0.alpha1+
Build ID: 7e03c4eed72452fdfb87341214a21956c08ba969
CPU threads: 2; OS: Mac OS X 10.12.6; UI render: default; 
TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2017-10-25_23:45:02
Locale: en-US (en_US.UTF-8); Calc: group

Version: 5.4.0.3 (x64)
Build ID: 7556cbc6811c9d992f4064ab9287069087d7f62c
CPU threads: 1; OS: Windows 6.1; UI render: default; 
Locale: en-US (en_US); Calc: group
Comment 15 Buovjaga 2018-06-28 11:36:17 UTC
Created attachment 143186 [details]
DOC exported with 3.5.0 (oldest of 43all Linux bibisect repo)

If this file already shows the problem, bibisectRequest can be changed to preBibisect
Comment 16 eisa01 2018-06-28 16:26:39 UTC
I'm not seeing this issue any more with the sample file at all

I think it may be related to Microsoft having aligned the code base across all platforms since the start of 2018. Tested on Mac Word 16.9.1

So, would this be not our bug, or is it still a bug for older versions of Mac Office?
Comment 17 QA Administrators 2019-10-15 02:29:17 UTC Comment hidden (obsolete)
Comment 18 eisa01 2019-11-02 15:46:45 UTC
Closing this as not our bug, per comment 18

This was fixed by macOS Word getting an aligned code base with Windows Word