Thu, 25 Jun 2009 07:21:16 -0700
Josh Andler <
scislac@...> kirjoitti:
> 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?
As Bulia Byak just noted, Inkscape generates filters with
color-interpolation-filters="sRGB" so no need to edit manually the
files generated with 0.47.
An also, I don't want to belittle the problem, but this "key new
feature" has been like this since 0.45 and it wasn't until lately that
the problem was spotted. For real color-interpolation-filters support, I
believe there exists a simple solution and a high-quality solution.
Simple: when needed, transform the filter input image to linearRGB and
the output image back to sRGB. Colour quantization problems likely
(read: banding)
High-Quality: make filters use 16 bit colours internally and do the
simple solution. Would help with some other quality issues, too. This
qould require a fair amount of work, so I'd be wary of pushing such
update in this late in release cycle. (or we could create special
versions of filters so they do sRGB->linearRGB->sRGB conversion
internally -- lots of work and doesn't account for the possibility of
linearRGB input images)
--
Niko Kiirala
niko@...
------------------------------------------------------------------------------
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...
https://lists.sourceforge.net/lists/listinfo/inkscape-devel