- From: Boris Dalstein via GitHub <sysbot+gh@w3.org>
- Date: Mon, 02 Dec 2019 18:52:06 +0000
- To: public-svg-issues@w3.org
I generally agree on this, although obviously this is a breaking change, and it makes the syntax slightly less compact for arcs. In summary, the advantages of the proposed change are: - More readable syntax for humans - Easier to write a parser - More consistent with CSS syntax But the disadvantages are: - It is a breaking change (things that were allowed in SVG 1.1 are not allowed anymore in SVG 2) - Slightly less compact notation for arcs I don't know if I would advocate for this change in isolation: if we introduce any breaking change, I'd rather do a wholesale rewrite of the path-data syntax, also disallowing `0.1.2` (currently: `0.1` and `.2`), disallowing `100-200` (currently `100` and `-200`), and making commas either mandatory or disallowed (currently optional) > Since everywhere else in a path `10.050.05` is `10.05` and `0.05`. Actually, `10.050.05` is `10.050` and `.05`, which is yet another proof that we keep getting those wrong and that the syntax should just be disallowed. -- GitHub Notification of comment by dalboris Please view or discuss this issue at https://github.com/w3c/svgwg/issues/755#issuecomment-560529976 using your GitHub account
Received on Monday, 2 December 2019 18:52:08 UTC