On 06/25/2009 05:52 AM, Jasper van de Gronde wrote:
In SVG there are two attributes that determine the color space used for operating on color values, these are color-interpolation and color-interpolation-filters (both can be set to either linearRGB or sRGB). For some reason that is completely beyond me the W3C decided to make the initial value sRGB for color-interpolation and linearRGB for color-interpolation-filters... As Inkscape has no support whatsoever for color-interpolation-filters pretty much any file which uses a filter looks wrong in Inkscape.
The last line here seriously worries me for a number of reasons. The most obvious of which is the basic implication that "pretty much any file which uses a filter looks wrong in Inkscape". With all of the work that has been put into filters for this release, it seems like a pretty big mistake to release with an issue that seems to loom so large.
To ensure that your file looks the same in Inkscape as in other viewers, use color-interpolation-filters="sRGB" (as far as I know it's perfectly valid to do this just once, on the root SVG element). I've attached a file that shows how Batik renders filters-turb-01-f.svg with this modification.
I have a very important Q here for others... Should this be a release blocker? It sure sounds like a pretty significant one to me.
I can see the bug tracker post-release now, "Filters in inkscape are buggy/broken", and a bunch more like it. If people need to manually modify a file to get other renderers to create the same output (or to get our output to match others), it's fundamentally broken as far as the users are concerned (myself included).
Not only is this something that we want to get corrected for our users, but this is one of those project reputation issues. It will be well over a year since our last release and one of our key new features is "broken" compatibility-wise with other SVG renderers/editors... and yet we're still on track to knowingly release with it?
Will others please chime in on this?
Cheers, Josh