|
Description
Telesto
2020-08-24 06:52:45 UTC
Created attachment 164615 [details]
Example file
Adding bibisectrequest no bibisect the point where this got implemented in they way it currently works. Introduced between 4.3-4.4. It's not a regression, but the fix appears to be incomplete @Barakso Has NISZ interest in this type of issue; as I love to raise attention for certain bugs. But slightly pointless if out of scope of the area of interest (In reply to Telesto from comment #3) > @Barakso > Has NISZ interest in this type of issue; as I love to raise attention for > certain bugs. But slightly pointless if out of scope of the area of interest Sorry for the late answer, I was on vacation. My free time work (community work), what I do under this account, not reflects NISZ interest. So I will ask my company for an official answear. (In reply to Telesto from comment #3) > @Barakso > Has NISZ interest in this type of issue; as I love to raise attention for > certain bugs. But slightly pointless if out of scope of the area of interest We discussed it, our team is interested in DOCX export issues, so feel free to add CC next time our team account (NISZ LibreOffice Team) instead of my personal account. Thanks! Reproduced in: Version: 7.1.0.0.alpha0+ (x64) Build ID: 1e0cfd5662d95cea84e80e4fe10d52c3b1101ae6 CPU threads: 4; OS: Windows 10.0 Build 17134; UI render: Skia/Raster; VCL: win Locale: hu-HU (hu_HU); UI: hu-HU Calc: CL This is not about frame, but about wrong applied wrap. More wraps is wrong: Optimal, Before, After... Those wraps look fine if, after fileopen of saved DOCX, wrap is set to None and reapplied. Moral: test more and feel less free to call devs until issue is clear. Created attachment 166341 [details] Screenshot of the XML parts, side by side, by Writer and by Word. The problem is similar as all remained bugs in meta bug Shape-ODF-OOXML-export (bug 136358). Maybe complete support of custom shapes (from ODF to OOXML) should exist to fix this bug. But the wrap is problem too, see attachment. Created attachment 167020 [details]
Example ODT with 6 wraps
Here is a better example ODT.
Created attachment 167021 [details]
Example ODT with 6 wraps - comparison screenshot
Example ODT with 6 wraps is compared from ODT in LO to opening DOC/X in LO and MSO.
None of opens is fully correct.
DOCX in MSO and LO opens OPTIMAL,BEFORE, AFTER, PARALLEL as Square wrap, BACKGROUND, THROUGH are good.
DOC in LO opens as DOCX.
DOC in MSO is the best, just OPTIMAL is different sided, while BEFORE, AFTER, PARALLEL, BACKGROUND, THROUGH are good.
*** Bug 136386 has been marked as a duplicate of this bug. *** Created attachment 167034 [details]
The example file fixed up in Word manually
To have the desired effect we would need to export these wrap settings (importing them works fine):
Optimal: <wp:wrapTight wrapText="largest">
Before: <wp:wrapTight wrapText="left">
After: <wp:wrapTight wrapText="right">
Paralell: <wp:wrapTight wrapText="bothSides">
Attila Bakos (NISZ) committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/ec33be1d135c1523b4d872eb2f86c515f0419509 tdf#136059 OOXML export: fix shape wrap "Contour" It will be available in 7.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. Filesave as DOCX looks good for wrap, so this seems to be fixed. I didn't check the duplicate. Text reflow is good on reopen in LO but not good in MSO (page 1 opens on two pages), which was also before, so it's another issue. DOC needs to be reported separately. The implemented solution has the problem, that it only works if the path has fixed coordinates and no references to adjustment values or to formulas, and if the path uses a "0 0 21600 21600" viewbox. I'll fix it together with the other wrap problems in DocxSdrExport::startDMLAnchorInline. The follow up report is bug 142433. |