Bug 120762 - Photo transparency does not save or load when working in ODT->.docx format with Writer.
Summary: Photo transparency does not save or load when working in ODT->.docx format wi...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All All
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
: 134356 (view as bug list)
Depends on:
Blocks: DOCX-Images
  Show dependency treegraph
 
Reported: 2018-10-22 00:40 UTC by BVZ
Modified: 2023-06-08 16:45 UTC (History)
6 users (show)

See Also:
Crash report or crash signature:


Attachments
Logo originally transparent in *odt. Pasted and saved in this *.docx, but transparency not saved. (52.71 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2018-10-22 00:46 UTC, BVZ
Details
ODT original (60.80 KB, application/vnd.oasis.opendocument.text)
2018-12-13 07:21 UTC, BVZ
Details

Note You need to log in before you can comment on or make changes to this bug.
Description BVZ 2018-10-22 00:40:36 UTC
Description:
I often work with documents that include a 'watermark' image, such that the image itself is formatted to be transparent and in the background of the page. I can edit, and save, this kind of image formatting with no problems in *.odt documents, but the changes never save in *.docx documents.

Steps to Reproduce:
1. Take *.docx document with image transparency formatted into a part of the document 
2. Open using LibreOffice
3. 

Actual Results:
The image with some percentage of transparency appeared as if it had no transparency.

Expected Results:
The image formatting should stay the same, whether the document is being worked on in Microsoft Office or LibreOffice.


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
Comment 1 BVZ 2018-10-22 00:46:53 UTC
Created attachment 145887 [details]
Logo originally transparent in *odt. Pasted and saved in this *.docx, but transparency not saved.
Comment 2 Chen yu an 2018-11-29 09:31:59 UTC
Bug confirmed.

Version: 6.3.0.0.alpha0+ (x64)
Build ID: 0f25a3c36f27fd51453b9a9115f236b83c143684
CPU threads: 8; OS: Windows 10.0; UI render: GL; VCL: win; 
TinderBox: Win-x86_64@42, Branch:master, Time: 2018-11-27_20:06:55
Locale: zh-TW (zh_TW); UI-Language: en-US
Calc: threaded
Comment 3 Chen yu an 2018-11-29 09:33:48 UTC Comment hidden (obsolete)
Comment 4 Dieter 2018-11-29 20:59:55 UTC
Set to NEW because of comment 2
Comment 5 Xisco Faulí 2018-12-05 15:19:22 UTC
Hello BVZ,
Could you please attach the original .ODT file? Otherwise, we can't investigate this issue.
I have set the bug's status to 'NEEDINFO'. Please change it back to 'NEW' once the requested document is provided.
Comment 6 BVZ 2018-12-07 06:41:54 UTC
Hi Xisco,

Thanks for looking into this. The problem actually does not concern image transparency when working in *.odt files, this feature works as intended.

The problem is when one tries to save image transparency in *.docx files, closes said file with image transparency setting, then reopens that same file. The 'saved' image transparency does not appear as saved and the image only appears with its initial opacity.
Comment 7 Xisco Faulí 2018-12-07 09:53:28 UTC
Hello BVZ,
Yes, i know, that's why I'm asking for the original .ODT to investigate the conversion from .ODT to .DOCX
Comment 8 BVZ 2018-12-13 07:21:13 UTC
Created attachment 147490 [details]
ODT original
Comment 9 BVZ 2018-12-13 07:24:53 UTC
Hi Xisco, I see, understood and uploaded. 

Also FYI, I did some other photo editing saved to .docx recently and none of it saved when I reopened the document. These issues didn't involve transparency, but possibly related since they are about saving in .docx.
Comment 10 Dieter 2018-12-13 08:20:33 UTC
I confirm it with attachment from comment 8 and

Version: 6.2.0.0.beta1 (x64)
Build ID: d1b41307be3f8c19fe6f1938cf056e7ff1eb1d18
CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; 
Locale: en-US (de_DE); UI-Language: en-GB
Calc: threaded

and

Version: 5.4.7.2 (x64)
Build-ID: c838ef25c16710f8838b1faec480ebba495259d0
CPU-Threads: 4; BS: Windows 6.19; UI-Render: GL; 
Gebietsschema: de-DE (de_DE); Calc: CL
Comment 11 Dieter 2020-06-30 09:24:24 UTC
*** Bug 134356 has been marked as a duplicate of this bug. ***