https://issues.apache.org/ooo/show_bug.cgi?id=119118
--- Comment #15 from Armin Le Grand <armin.le.gr...@me.com> --- ALG: No, please re-read above and task 123433: There are two usages of svg:d in AOO: (a) ODF XML context (b) SVG import For (a) it is - for import: not possible to get away from the slightly changed paradigm/error of the new last point in svg:d consuming without potentially breaking all existing ODF files - for export: possible to get around this by writing 'M' after 'z' instead of 'm' so that it is a valid svg_d and does not contain the error -> all derivates can read it This means: - All files written from now on can be imported independent from that error - All files written earlier still need that 'wrong' (or: ODF-specific) interpretation of the new start point and use that - Derivates (like LO) will be able to read new files without error - Reading files from derivates will still lead to errors; of course these derivates have the choice to do the same changes if they are interested that the OOO-version which is most used in the world can load their user's stuff without that error... For (b) pure svg:d is now used (currently only import anyways; the svg exporter has it's own svg:d writer). -- You are receiving this mail because: You are on the CC list for the bug. You are watching all bug changes.
