Bug 63126 - FORMATTING: Writer doesn't save transparencies of images in .doc(x)
Summary: FORMATTING: Writer doesn't save transparencies of images in .doc(x)
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.0.2.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-04 15:31 UTC by moray33
Modified: 2015-06-19 15:19 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description moray33 2013-04-04 15:31:22 UTC
Problem description: Writer doesn't save transparencies of images in MS Office's .doc

Steps to reproduce:
1. Apply transparency to an image
2. Save it as .doc
3. Open the document with Writer and there's no transparency

Current behavior: Writer doesn't save transparencies of images in MS Office's .doc

Expected behavior:Writer saves transparencies of images in MS Office's .doc

              
Operating System: Windows XP
Version: 4.0.2.2 release
Comment 1 Jorendc 2013-04-08 17:25:42 UTC
Hi,

Thanks for reporting. I can reproduce this behavior using Linux Mint 14 x64 with LibreOffice Version: 4.1.0.0.alpha0+ Build ID: 7b515a57eb6a644860715018656ac0b843b62ba (build today).

I saved the file both as doc and docx. It isn't saved in both ways. Therefore I mark this bug as NEW.

Normal Medium seems to be a good priority.
Normal: does prevent to make high quality work
Medium: default priority in the normal range

Kind regards,
Joren
Comment 2 ign_christian 2013-05-10 06:31:59 UTC
Confirmed, this bug still exist with LO 4.0.3.3 (Win7 Home Premium 32bit) & LO 3.6.6.2 (Ubuntu 12.04.2 LTS)
Comment 3 moray33 2013-08-07 14:15:57 UTC
Confirmed in Windows 7 LibreOffice 4.1.0.4
Comment 4 QA Administrators 2015-04-01 14:40:04 UTC
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

   *Test to see if the bug is still present on a currently supported version of LibreOffice (4.4.1 or later)
   https://www.libreoffice.org/download/

   *If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior
 
   *If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System

Please DO NOT

   *Update the version field
   *Reply via email (please reply directly on the bug tracker)
   *Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 

1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3)

http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug 
3. Leave a comment with your results. 
4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 
4b. If the bug was not present in 3.3 - add "regression" to keyword


Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa

Thank you for your help!

-- The LibreOffice QA Team This NEW Message was generated on: 2015-04-01
Comment 5 moray33 2015-04-01 19:56:51 UTC
It's fixed in LO 4.4.1.2 (Windows 7).
Comment 6 Buovjaga 2015-06-19 15:19:01 UTC
WFM per comment 7.