[Bug 123473] The description of complex polygons should be rechecked

[bu...@apache.org]

https://issues.apache.org/ooo/show_bug.cgi?id=123473

Armin Le Grand <Ar...@me.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |Armin.Le.Grand@me.com

--- Comment #1 from Armin Le Grand <Ar...@me.com> ---
ALG: The problem is an old error in the usage of svg:d in ODF files; the svg:d
defines that for using relative coordinates, the ' the next subpath starts at
the same initial point as the current subpath'
(http://www.w3.org/TR/SVG/paths.html#PathElement, 8.3.3 The "closepath"
command).
The ODF implementation uses the last point as current point for the next
sub-path. This is wrong, but correcting this leads to make all existing ODF
files being incompatible. Others have choosen to do so, we did not.
There was a lot of discussion and there are two sides:
(a) To not make all existing ODF files invalid, keep the error and define that
svg:d usage in ODF XML is a little bit 'special' in this point
(b) Change it to pure svg:d and risk that all ever existing ODF files may get
read with errors
The discussion had strong arguments for both sides, thus AOO kept the 'error'
for now. Problem is that there is no easy way to detect inside the ODF if an
svg:d is written with or without that error, thus no hints for correcting this
at load time.
I am working on some changes, e.g. starting svg:d sub-pathes always with an
absolute moveto ('M' instead of 'm'); these will be loaded the same in all
offices. The default import from ODF will have to keep that error, else all
existing ODF files are on risk.
HTH!

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are watching all bug changes.