That is a missing feature. Only for custom shapes a wrap polygon is created and that one is bad. The relevant part is in docxsdrexport.cxx, starting in line 1092. In addition interpretation of text::WrapTextMode_LEFT and text::WrapTextMode:Right is missing. I have already started to work on it, so I would like to take it. But I'm not working full time on LibreOffice, so I need some time. Do you need a quick solution?

I'll work on it and fix it together with the other wrap problems in DocxSdrExport::startDMLAnchorInline.

Created attachment 175062 [details]
The example file and its docx version in current master

The contour wrap seems to be exported correctly now in:

Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: 80a47aae1419842f4496f02028e2b49763aea25b
CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: default; VCL: win
Locale: hu-HU (hu_HU); UI: en-US
Calc: CL

after:
commit 61ef73bb9e06ac7325abc26698314d7e35c164cc	[log]
author	Regina Henschel <rb.henschel@t-online.de>	Sun Aug 08 01:05:09 2021 +0200
committer	Miklos Vajna <vmiklos@collabora.com>	Fri Aug 13 16:00:35 2021 +0200

tdf#143432 and more, improve wrap contour export

Created attachment 175063 [details]
The exported docx in Writer and Word

However it is still not good in Word:
- Writer sees the grouped shape as Optimal wrap with Contour enabled
- Word sees it as Through wrap instead of Tight

Created attachment 175064 [details]
The example file saved by Writer

The relevant part seems to be this in document.xml:

								<wp:wrapThrough wrapText="largest">
									<wp:wrapPolygon edited="0">
										<wp:start x="0"
        											y="0"/>
										<wp:lineTo x="21600"
         											y="0"/>
										<wp:lineTo x="21600"
         											y="21600"/>
										<wp:lineTo x="0"
         											y="21600"/>
										<wp:lineTo x="0"
         											y="0"/>
									</wp:wrapPolygon>
								</wp:wrapThrough>

Created attachment 175065 [details]
The previous example fixed up in Word 2019

After manually fixing it in Word and saving, the relevant looking part in document.xml:

								<wp:wrapTight wrapText="largest">
									<wp:wrapPolygon edited="0">
										<wp:start x="10740"
        											y="0"/>
										<wp:lineTo x="10740"
         											y="7144"/>
										<wp:lineTo x="0"
         											y="8288"/>
										<wp:lineTo x="0"
         											y="14432"/>
										<wp:lineTo x="10502"
         											y="16289"/>
										<wp:lineTo x="10502"
         											y="21433"/>
										<wp:lineTo x="19571"
         											y="21433"/>
										<wp:lineTo x="19571"
         											y="4858"/>
										<wp:lineTo x="21003"
         											y="1143"/>
										<wp:lineTo x="20765"
         											y="0"/>
										<wp:lineTo x="10740"
         											y="0"/>
									</wp:wrapPolygon>
								</wp:wrapTight>

Dear Regina,
bug has been in ASSIGNED status for more than 3 months without any
activity. Resetting it to NEW.
Please assign it back to yourself if you're still working on this.

Dear NISZ LibreOffice Team,

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 with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

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) from https://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: https://web.libera.chat/?settings=#libreoffice-qa

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

Warm Regards,
QA Team

MassPing-UntouchedBug