On Apr 15, 2006, at 3:02 PM, bulia byak wrote:
I must admit I don't understand this kind of reasoning. "Desaturate"
has a perfectly intuitive meaning for everyone, and I don't see how
the fact that I'm going to print it on some kind of printer might ever
affect that meaning. Desaturate is a _creative_ thing, see? I don't
want no stinkin' CMYK interfering with my creative choices. If that
particular printer can't print my design adequately, it's a problem
with the printer, not with my image.
No...
It's *very* much a problem with your image (counting a *.svg file as 'your image'). And it doesn't have to be CMYK output either, that's just the first example that comes to mind that people for professional reasons (aka in their day-to-day work) need.
I'll follow up with more details shortly, but it's *very* much an appropriate thing. As I mentioned, unless the code in Inkscape for tweaking colors takes more that just sRGB fallback values into account, it's going to be outdated when it first goes in.
The point is.. before 0.44 is out we'll have gradients and such switch from
"fill: #ff00ff"
to
"fill: #ff00ff icc-color(target, 0.5, 0.0, 0.3, 1.0)"
Ideally in that situation we'd do the main work in the more capable colorspace covered in the specified icc profile, and just update the sRGB fallback values as a side effect, not as the main driver.
That's the very minimum we'll need to support. We can go *way* above that and stay with SVG 1.1 even. And if we support some SVG 1.2 features (as is planned... and as ksvg happens to support at the moment), then we can do even more.
*However* before we chase rabbits and such, I'll need to get together detailed information, questions, and a few answers. Then I'll toss those out in a new thread.