- From: Chris Murphy <lists@colorremedies.com>
- Date: 2008年7月21日 23:47:10 -0400
- To: L. David Baron <dbaron@dbaron.org>
- Cc: www-style@w3.org
- Message-Id: <5B48260D-5B1C-47CE-881F-014DEF0B7ADD@colorremedies.com>
That whole paragraph. I think what happens to values outside the display's gamut is up to the CMS being used. There is no one right way to deal with out of gamut colors. The spec even says it should be either clipped or gamut mapped. I'm not thinking of a third option, but if there is one, and it's not recommended that would be nice to know (perhaps more interesting than relevant). And also it says clipped or mapped, but only when the gamut is known. If it's not known, then what? The spec doesn't say what to do if it's not known. If the goal is to get consistency among browsers, then color management needs to be required, and the exact transformation process needs to be required also. That requires a level of specificity that is not in the current language. If the goal is merely to suggest that color management should be done in order to have a chance at preserving color appearance, then let's leave it at that. Each UA will have to decide whether to clip, or to map. And if they map, how they map. Chris Murphy On Jul 21, 2008, at 10:42 PM, L. David Baron wrote: > On Monday 2008年07月21日 21:29 -0400, Chris Murphy wrote: >> Paragraph starting with "Values outside the device gamut should be >> slipped...when the gamut is known." I'd remove the whole. The phrase >> "For a typical CRT monitor, whose device gamut is the same as >> sRGB..." >> demonstrates a fundamental problem that we have with the LCD world of >> today in that there is no typical LCD display and their gamut can be >> decidedly smaller than that of sRGB. > > Remove the whole what? > > We should say something about what happens to values outside the > device gamut. > > -David > > -- > L. David Baron http://dbaron.org/ > Mozilla Corporation http://www.mozilla.com/
Received on Tuesday, 22 July 2008 03:50:41 UTC