https://bugs.documentfoundation.org/show_bug.cgi?id=112450
Regina Henschel <rb.hensc...@t-online.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rb.hensc...@t-online.de --- Comment #12 from Regina Henschel <rb.hensc...@t-online.de> --- You get the same problem with current applications: Draw a polygon in Writer and export as docx. Because of the fix for tdf#75254 this does not generate a custom shape but only a VML shape. Open the file in Word and add a point to the polygon. Save it in Word. Word converts it to a v:polyline element without adding a custom shape. This does not happen in PowerPoint. I have not tested Excel. Word writes the values in the attribute "points" with units, e.g. 31.2pt,297.7pt. But the import does not consider units. The error is in https://opengrok.libreoffice.org/xref/core/oox/source/vml/vmlshapecontext.cxx?r=e12d4c7e#572 Because the token contains the unit, toInt32() returns 0. If such edited shape is copies from Word to PowerPoint, then it is converted to a custom shape. I don't know whether older PowerPoint versions create v:polyline. It might be necessary do distinguish applications anyway, because of the Twips vs 1/100mm problem. The attribute coordsize, which Word produces, is in Twips, but has no unit. So for Writer the token has to be converted to a number value in Twips to match the coordsize attribute. -- You are receiving this mail because: You are the assignee for the bug.