Re: SVG2 CR - Catmull-Rom curve commands missing??

Fully Agree!,

I heard some voices (eg. SVG standard being stalled blocking Inkscape
development) but I had no idea on the scale of stagnation.
The original input requirements look awesome!
and it's truly sad that any work still being done on it focuses rather on
throwing stuff out of scope just to quickly bump up the number.

While it could seem to be rational to release some important (?) changes
now rather than postpone the whole release
it really works against the standard.
Releasing half cooked stuff (or even worse: only some minor, cosmetic
changes) doesn't bring the incentive for adoption.
Again, that's actually harming the standard - Check out XSLT2.0 support by
Microsoft or in browsers…

What is really surprising is that this is happening now, when first SVG
standard is finally very well supported (all browsers!, all vector drawing
software) and the industry is now awaiting a long list of improvements (

On Sat, 10 Nov 2018 at 14:29, Dr. Olaf Hoffmann <>

> Hello,
> almost all new features identified to be required in the beginning of SVG 2
> are absent in the current draft:
> After all these years and compared to SVG 1.1 and SVG tiny 1.2 the current
> draft for SVG 2 looks like stagnation or even regression.
> It is quite surprising, that it did not already simply end as a note and
> work
> on SVG is stopped completely.
> Alternatively, looking on the current draft for SVG 2, it seems to be time
> now
> to reject this and to start from the beginning with the list of
> requirements
> from 2012 ;o)
> Else there is low chance, that authors and audience can enjoy new features
> in
> this century ;o)
> >Hello,
> >
> >What happened to this great idea?
> >
> >
> paths.html#PathDataCatmullRomCommand
> >
> >we wait 8 long years, hoping and only to find it missing now?
> >Thank you,
> >Kind Regards
> >~Msciwoj

Received on Monday, 12 November 2018 08:14:49 UTC