W3C home > Mailing lists > Public > www-style@w3.org > August 2009

RE: [CSS3 gcpm] CMYK colors and color management.

From: David Perrell <davidp@hpaa.com>
Date: Sun, 2 Aug 2009 18:50:59 -0700
To: "W3C style mailing list" <www-style@w3.org>
Chris Murphy wrote:
| So you'd color manage images but not color manage CSS content?

Did I say that?

| We have
| that very problem right now with RGB and it's a big sticking point
| when different kinds of content can and can't be color managed
| correctly. It causes discontinuity between, say a CSS background and
| the borders of neighboring images or images with transparency and...

Not sure how many are stuck. Authors can ensure all content is sRGB or
untagged. But, yes, it seems discontinuity has occurred with PNG due to
overambitious gamma correction[1]. And now Firefox 3.5 is color-correcting
PNG and JPG[2] without correcting other content. Will this produce a
firestorm of discontinuity disgust among color-profile-ignorant users,
prompting them to besiege the W3C with demands for corrective action? More
likely they'll continue to wonder why each application treats the same data
differently. And they just might wonder why color correction can't be done
transparently throughout their entire system, not just on an app-by-app
basis. Monitors, display adapters, printers...they can all communicate with
the OS. Can't they just get along?

| The point is there is such a thing as RGB output and yet CSS doesn't
| have a mechanism for that...

As well it shouldn't.

| and what's
| proposed is untagged CMYK. I definitely think this is a case of cart
| before the horse.

Just say "neigh" to print device color spaces!

David Perrell

[1] http://hsivonen.iki.fi/png-gamma/
[2] http://hacks.mozilla.org/2009/06/color-correction/
Received on Monday, 3 August 2009 01:51:59 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:07:38 UTC