Created attachment 185491 [details] shapes using hatch fill Open attached file and save it to docx. Open the file in Word. Error: Word cannot open the file. Problem is, that LO writes the markup so, as if it is a bitmap fill, but does not provide the bitmap, which results in an empty rId attribute. Expected: In case a corresponding preset fill exists in OOXML, the fil is exported with <a:pattFill> element. The available preset fills are listed in section 20.1.10.51 in ISO/IEC 29500-1:2016(E). Those cover most of our predefined hatch and pattern fill as long as the user does not change the angle. In case there is no suitable kind of fill in OOXML, the fill is exported as bitmap fill and the needed bitmap is correctly exported and referenced.
Created attachment 185495 [details] Screenshot comparing 7.5 7.6 Word Word allows to recover the file (Microsoft® Word para Microsoft 365 MSO (versión 2301 compilación 16.0.16026.20002) de 64 bit. But changing the hatching in the figures. Saving with 7.5 or 7.6, gives the same result in Word.
Partially reproducible. Version: 7.5.1.1 (X86_64) / LibreOffice Community Build ID: bd819218336a5be54a11b986ea4dd2db2efb120e CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 9788a565b3241d1bd62394b9e29c322361d05f80 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded Jumbo
I am getting oox/source/export/drawingml.cxx:1499: unhandled graphic type 0 when it tries to write out the ESCHER_Prop_fillBlip in VMLExport::Commit. bisected to 4.2 commit dbc7c605d65cc2dc37af3d2077ac553754bc4f7d Author: Armin Le Grand on Tue Oct 9 14:41:38 2012 +0000 Resolves: #i121183# enhance export of ppt hatch masterpagebackground
Justin Luth committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/5132255021aa61f8a1fa7d8de820cb3528699812 tdf#153761 vml export: avoid corrupt docx: don't write empty r:id It will be available in 24.8.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.
Justin Luth committed a patch related to this issue. It has been pushed to "libreoffice-24-2": https://git.libreoffice.org/core/commit/38ff7cd25af90dcde19f33aaede23935df6758d8 tdf#153761 vml export: avoid corrupt docx: don't write empty r:id It will be available in 24.2.2. 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.
I'm going to leave this open because the hatch fill is still unreadable by Word (and LO for that matter). I think the problem is that lclDrawHatch is trying to output an EMF graphic. (bOOxmlExport probably should be tied to EscherPropertyContainer - it is WRONG when lclDrawHatch is called.) [I tried to resurrect this for page background, but failed. https://gerrit.libreoffice.org/c/core/+/163471]
This need to even further investigation to find out some erroneous source codes.
Dear Regina Henschel, 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
Word no longer needs to repair something. The predefined hatch looks good, but the image for the user defined hatch is still missing. Tested in Version: 26.8.0.0.alpha0+ (X86_64) Build ID: bb24b8ec8f8a3bef6efece607479fff9541e30ff CPU threads: 32; OS: Windows 11 X86_64 (build 26200); UI render: Skia/Vulkan; VCL: win Locale: de-DE (de_DE); UI: en-US Calc: threaded