- From: Joey Sabey via GitHub <sysbot+gh@w3.org>
- Date: Mon, 21 Feb 2022 20:49:54 +0000
- To: public-svg-issues@w3.org
This is certainly a fair point, though I remain concerned that as it stands there are a lot of projects with no plans to support past version 1.1 (at least in the short to mid-term) and the lack of specificity in the spec seems to be actively blocking any attempt to produce more standard output between renderers in the here & now. I must confess that I don't know hardly enough about how this is all intended to work under the hood to understand what precisely is meant by 'platform independent' in this instance, or why exactly that would be the case... I will note as an example for the sake of clarity that when rendering the same SVG to different resolutions, with kernelUnitLength set, visually different images are produced by e.g. resvg and the renderer in Chrome, while visually similar images are produced by e.g. inkscape, ImageMagick, and the renderer in Firefox. (On this machine, at least) I don't know if there is something I am missing in the spec that makes it more clear what the 'intended' behaviour is, or if there is a way that it can be clarified if not, or if it is (regrettably) just a lost cause for this version of the spec. Given how far out actual support for/implementations of future versions of the spec seem to be though I feel I might as well try and see how and where I can push for at least _some_ degree of better consistency for now. -- GitHub Notification of comment by Omnikron13 Please view or discuss this issue at https://github.com/w3c/svgwg/issues/873#issuecomment-1047219929 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 21 February 2022 20:49:56 UTC