• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Panther, sRGB, web browsers
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Panther, sRGB, web browsers


  • Subject: Re: Panther, sRGB, web browsers
  • From: John Fieber <email@hidden>
  • Date: Mon, 15 Dec 2003 14:37:11 -0500

On Dec 12, 2003, at 6:14 PM, John Gnaegy wrote:

Safari assumes untagged images to be in the space of the default display's profile. This is the same behavior as Preview, so the nice thing is an image opened in Preview looks the same as an image opened in Safari, whether it has an embedded profile or not.

[...]

I imagine the choice came down on the side of assuming the display's profile for untagged data in order to have a unified behavior with other cocoa apps on the system.

Okay, I'm now puzzled by this. In "ColorSync on Mac OS X" (http://developer.apple.com/technotes/tn/tn2035.html) under the heading "ColorSync Changes for Mac OS 10.2"

Profile Changes when Printing or Displaying Untagged Data

PDF Display

On Mac OS 10.2, untagged RGB data in PDF will be tagged with the Generic RGB profile, and as a result it will be color-matched to the screen.

On earlier versions of Mac OS X, untagged RGB data in PDF would be tagged with the system profile (the profile returned by the CMGetSystemProfile function), and as a result, no color-matching to the screen would occur (because both the source and destination profiles for the match would be identical).

The is arguably sensible an a total-colorsync universe--even untagged data will at least look consistent (if incorrect) from display to display. And consistency and predictability are what color management is all about.

So, is the above note changes in 10.2 not completely accurate, or do all the Apple applications override this default assumption of Generic RGB in 10.2+ with the old default assumption of the display profile? Or does "PDF display" in context mean something other than the PDF that the core graphics/Quartz drawing APIs generate?

It is a neat idea to have color management integrated at the system level such that applications using the Cocoa APIs and Quartz get it more or less automatically, but at the same time the actual implementation and documentation of the implementation seems rather confusing, particularly when it comes to printing (as I've posted in detail before).

-john
_______________________________________________
colorsync-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/colorsync-users
Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Re: Panther, sRGB, web browsers
      • From: Chris Murphy <email@hidden>
References: 
 >Panther, sRGB, web browsers (From: Chris Murphy <email@hidden>)
 >Re: Panther, sRGB, web browsers (From: Steve Upton <email@hidden>)
 >Re: Panther, sRGB, web browsers (From: Chris Murphy <email@hidden>)
 >Re: Panther, sRGB, web browsers (From: John Gnaegy <email@hidden>)

  • Prev by Date: Re: epson 2200 > blackpoint compensation
  • Next by Date: Re: Link/abstract profiles in Photoshop
  • Previous by thread: Re: Panther, sRGB, web browsers
  • Next by thread: Re: Panther, sRGB, web browsers
  • Index(es):
    • Date
    • Thread