- From: Tom Shinnick via GitHub <sysbot+gh@w3.org>
- Date: Sat, 10 Jun 2017 05:30:34 +0000
- To: public-svg-issues@w3.org
That looks very much like the grammar I was referencing and looks unhappily like the same problems. What I'm going to try to do is translate that grammar to something testable, using as basis the project https://github.com/hughsk/svg-path-parser/ which uses [peg.js](https://pegjs.org/) underneath. This is a product of Gavin Kistner (aka @Phrogz) working against the SVG 1.1 grammar. I started hassling him there and ended up here. ([just deserts](https://en.wikipedia.org/wiki/Desert_(philosophy)) for me?) I'd rather have something more like concrete reasons (and demonstrable) for complaint than just "it looks wrong". Question: Is there a sense of what the resolution for w3c/svgwg/issues/286 will be? I could re-introduce `floating-point-constant` into the grammar and perhaps be able to show necessity vis-a-vis extant path strings? -- GitHub Notification of comment by tshinnic Please view or discuss this issue at https://github.com/w3c/svgwg/issues/325#issuecomment-307544054 using your GitHub account
Received on Saturday, 10 June 2017 05:30:40 UTC