W3C home > Mailing lists > Public > www-style@w3.org > September 2013

Re: [css-gcpm][css-color] device-cmyk() interaction with RGB-space colors.

From: Rik Cabanier <cabanier@gmail.com>
Date: Tue, 24 Sep 2013 14:12:38 -0700
Message-ID: <CAGN7qDCVQuOzq2UbzcX+f27+1j86bzs093hB611aWDy-GZ_jnQ@mail.gmail.com>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: Simon Sapin <simon.sapin@exyr.org>, www-style list <www-style@w3.org>
On Tue, Sep 24, 2013 at 2:06 PM, Tab Atkins Jr. <jackalmage@gmail.com>wrote:

> On Tue, Sep 24, 2013 at 2:02 PM, Rik Cabanier <cabanier@gmail.com> wrote:
> >> As such, CMYK colors must be converted to an equivalent RGB color
> >
> > I think you meant to reverse that . RGB colors are converted to CMYK
> during
> > the printing process.
>
> No, I meant what I wrote.  We *must* have RGB colors in memory, so we
> can do compositing/blending/etc.  Those are only defined over RGB
> colors.
>

I see. Things like compositing and blending do not require color conversion
though.
If we extend filters, those don't require it either.



>
> > IMO, I think this is something that should be done by the print processor
> > and not the browser since it most likely will not have the correct
> > information to make this decision.
>
> Yeah, but we can't actually preserve the color in CMYK.
>
> ~TJ
>
Received on Tuesday, 24 September 2013 21:13:04 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:34 UTC