• 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: Thu, 18 Dec 2003 16:31:59 -0500

On Dec 18, 2003, at 4:06 PM, John Gnaegy wrote:

Can we look forward to a New and Improved version of the ColorSync on MacOS X document in the future to clarify some of this? Or is the current implementation state just as confusing as it seems such that more documentation would just reaffirm the confusion?

What part is confusing? As it is now, standard Cocoa behavior is to match images to the display's profile. In the case of untagged data, the display's profile is assumed as the source, which means basically that no match occurs.

What is confusing is that it appears to directly contradicts what tn2035 states:

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).

If this is actually correct, then all the commonly used APIs must be arranging for the data to be tagged with the display profile by the time it hits Quartz for rendering. If this is the case, a simple note mentioning that would go a long way towards reducing this bit of confusion.

And would a similar thing be happening for printing? In trying to unravel color problems with assorted applications when printing, I've found that queued PDF data is actually often tagged with Generic RGB (as suggested in the 10.2 updates section of tn2035). Having one assumption for display (the display profile) and a different one for printing doesn't seem to be consistent with the goals of ColorSync.

-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: John Gnaegy <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>)
 >Re: Panther, sRGB, web browsers (From: John Fieber <email@hidden>)
 >Re: Panther, sRGB, web browsers (From: Chris Murphy <email@hidden>)
 >Re: Panther, sRGB, web browsers (From: John Fieber <email@hidden>)

  • Prev by Date: Re: Panther, sRGB, web browsers
  • Next by Date: Re: Panther, sRGB, web browsers
  • Previous by thread: Re: Panther, sRGB, web browsers
  • Next by thread: Re: Panther, sRGB, web browsers
  • Index(es):
    • Date
    • Thread