Bug 140823

Summary:	Images anchored to character shifting after DOC/DOCX export
Product:	LibreOffice	Reporter:	Telesto <telesto>
Component:	Writer	Assignee:	Attila Bakos (NISZ) <bakos.attilakaroly>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	dgp-mail, libreoffice
Priority:	medium
Version:	3.5.0 release
Hardware:	All
OS:	All
Whiteboard:
Crash report or crash signature:		Regression By:
Bug Depends on:
Bug Blocks:	104468
Attachments:	Example file

Description Telesto 2021-03-05 11:55:37 UTC

Description:
Images anchored to character shifting after DOCX export

Steps to Reproduce:
1. open the attached file
2. Save as DOCX
3. File reload

Actual Results:
Starting from second image on top everything shifted to the right

Expected Results:
Same as ODT


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: 722ec600e85cca2e94e82e69f8d13773061172b9
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win
Locale: nl-NL (nl_NL); UI: nl-NL
Calc: CL

Comment 1 Telesto 2021-03-05 11:55:50 UTC

Created attachment 170238 [details]
Example file

Comment 2 Telesto 2021-03-05 11:57:12 UTC

Also in
Versie: 4.4.7.2 
Build ID: f3153a8b245191196a4b6b9abd1d0da16eead600
Locale: nl_NL

Comment 3 Telesto 2021-03-05 11:59:22 UTC

And in
Versie 4.0.0.3 (Bouw-id: 7545bee9c2a0782548772a21bc84a9dcc583b89)

Comment 4 Telesto 2021-03-05 12:03:11 UTC

And in
LibreOffice 3.5.0rc3 
Build ID: 7e68ba2-a744ebf-1f241b7-c506db1-7d53735

Comment 5 Dieter 2021-03-22 07:22:09 UTC

I confirm it with

Version: 7.1.2.1 (x64) / LibreOffice Community
Build ID: 094b4116e8de6d2085e9b65d26912d6eac4c74a9
CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: en-GB
Calc: CL

Additional remarks:
I can't see, that everything shifts to the right, but only one image and its duplicates. Image is anchored "To Character" and horizontal position is "Paragraph area"

Comment 6 Attila Bakos (NISZ) 2021-05-05 06:31:26 UTC


*** This bug has been marked as a duplicate of bug 138782 ***