As Sandy says, its not a matter of right/wrong. Simply expected vs. unexpected.
Sure, if I save an image with a profile and immediately ask what profile the image is tagged with, I would expect the result of nil, not sRGB. However, there is a certain brilliance to having all nil profiles default to sRGB. It's a damn fine idea. However, the question becomes a) Does the image REALLY have an embedded profile? b) If so, When/What put that profile there? (Probably quickly tested by measuring the size of the image) c) If not, should the framework REALLY say there was? I'd think the responsibility of assigning a default profile for non-tagged images should be higher up the food chain. On Mar 23, 2014, at 2:41 PM, Sandy McGuffog <[email protected]> wrote: > Untagged images are a free-for-all - any app or framework can assume whatever > it wants for a color space with them, so there’s no “wrongly” about what > Mavericks does. It’s just different to previous versions. > > So far as I am aware, Apple is (strongly) discouraging the use of Device RGB, > for the good reason that using it leads to inconsistent results. > > Sandy > > > On Mar 23, 2014, at 8:14 PM, Leonardo <[email protected]> wrote: > >> I create a jpg RGB image with Photoshop "without" any icc profile. >> I import it in my app. >> >> NSBitmapImageRep *srcRep = [NSBitmapImageRep imageRepWithData:imageData]; >> NSLog(@"profileName %@", srcRep.colorSpace.localizedName); >> >> On OS X 10.8.5 I properly get "Device RGB". >> On Mavericks 10.9.2 I wrongly get "sRGB IEC61966-2.1". >> >> Therefore I can't understand whether the image: >> 1. has no profile then I have to assign a profile chosen by my user. >> 2. has its own profile then I do not touch it. >> >> I even tried CGColorSpaceCopyName. Same result. >> Did Apple changed its mind on Mavericks giving a profile to all the orphans, >> or am I missing some step? >> >> >> Regards >> -- Leonardo >> >> >> _______________________________________________ >> >> Cocoa-dev mailing list ([email protected]) >> >> Please do not post admin requests or moderator comments to the list. >> Contact the moderators at cocoa-dev-admins(at)lists.apple.com >> >> Help/Unsubscribe/Update your Subscription: >> https://lists.apple.com/mailman/options/cocoa-dev/mcguffogl%40gmail.com >> >> This email sent to [email protected] > > > _______________________________________________ > > Cocoa-dev mailing list ([email protected]) > > Please do not post admin requests or moderator comments to the list. > Contact the moderators at cocoa-dev-admins(at)lists.apple.com > > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/cocoa-dev/caoimghgin%40gmail.com > > This email sent to [email protected] _______________________________________________ Cocoa-dev mailing list ([email protected]) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
