Description: The shape dashes are rendered differently after docx export (creating different effect) Steps to Reproduce: 1. Open the attached file 2. Save as DOCX 3. File reload Actual Results: Compared results Expected Results: Ideally the same Reproducible: Always User Profile Reset: No Additional Info: Version: 7.2.0.0.alpha0+ (x64) Build ID: 315c7570c4a72f4c834086082825533b1e50d1bf CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL
Created attachment 168447 [details] Example file
@Regina I the feeling I'm asking the impossible here.. Even the ODT is opened differently on older versions.. However if same calculations are used.. it look the same for all document types? Or kind of rounding involved (or something like that)
Thank you for reporting the bug. I can confirm that the bug is present in Version: 7.0.3.1 (x64) Build ID: d7547858d014d4cf69878db179d326fc3483e082 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL Version: 7.2.0.0.alpha0+ (x64) Build ID: 761a672d62df1891b9f4f367a499b220ab2b33fa CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL
The shapes are indeed different. The Smiley from the toolbar in LO reflects the geometry from MSO binary. These binary shapes are not directly available in OOXML. So LibreOffice has two options: A) Map it to a similar shape available in the preset shapes of OOXML, or B) convert it to a custom geometry. Currently option A) is used for the smiley. On import the preset shape of OOXML is kept, because the file has no information, that it was in original a shape from MS binary format. The MSO binary geometry has the start point at the left of the shape, the OOXML preset shape has it at the right of the shape. The line is drawn clockwise. Dashing starts with a dash at the start point. To get the same in ODT as in DOCX, you need to start with an OOXML shape. I consider this a "Wont fix".
(In reply to Regina Henschel from comment #4) > I consider this a "Wont fix". Sounds reasonable. However throwing it into UX to get more input/insights/feedback. The sample file is obviously not real life; and kind of uncertain if there are cases where it could be relevant.. --- Self memo: should go to the compatibility wiki
Regina is the expert in this field => WF (NOB since it's a bug) (In reply to Telesto from comment #5) > Self memo: should go to the compatibility wiki Good idea!