[Openicc] Open Source compatible AdobeRGB profile

Lars Borg borg at adobe.com
Thu Jul 27 11:19:15 PDT 2006


Adobe provided the Adobe RGB spec to enable vendors to make 
compatible profiles without violating Adobe's trademark or copyright.
Make sure you use the exact numbers as provided in the spec, 
otherwise obviously you're not compatible. This includes using the 
same format version number.
Of course, the file name, profile description, and copyright, shall 
be different from the ones used by Adobe. The spec suggests how you 
can name a compatible profile.

One way to weed out incompatible profiles is to use your new profile 
in an image, and set Photoshop's color settings to Adobe RGB and to 
report mismatches on open. On opening the image, Photoshop checks the 
colorimetry of the two profiles.

Lars


At 12:11 PM +0200 7/7/06, Kai-Uwe Behrmann wrote:
>Adobe itself recommends to use "compatible with Adobe RGB (1998)" as
>naming for AdobeRGB like colour spaces. This is probably due to
>preparation to get this colour space adopted into standards, as
>Gilles Caulier from digiKam project pointed out.
>see: http://www.adobe.com/adobergb
>
>As "compatible with Adobe RGB (1998).icc" is a bit unconventional for a
>file name I would like to name the profile compatibleWithAdobeRGB.icc .
>This is better recognizable and not limited to EXIF.
>
>Gilles and others,
>would you take advantage of that profile? I like to packaged it
>into the Oyranos' profiles collection. Location is /usr/share/color/icc
>on linux.
>
>License can be free.
>
>regards
>Kai-Uwe Behrmann
>                                 + development for color management
>                                 + imaging / panoramas
>                                 + email: ku.b at gmx.de
>                                 + http://www.behrmann.name
>
>
>Am 05.07.06, 23:32 +0200 schrieb Kai-Uwe Behrmann:
>
>>  Hubert,
>>  maybe the AdobeRGB colour space can be refered as exif_second.icc ?
>>  If it would help, I could create this profile and put into Oyranos.
>>  A link from exif_second.icc to AdobeRGB.icc should suffice. As Adobe
>>  stores profiles in a hierarchy I see no problems later on.
>>  The link would be used by applications only as they select by filename.
>>  Users see then "exif second" in the UI.
>>
>>  regards
>>  Kai-Uwe Behrmann
>>                                  + development for color management
>>                                  + imaging / panoramas
>>                                  + email: ku.b at gmx.de
>>                                  + http://www.behrmann.name
>>
>>
>>  Am 05.07.06, 22:31 +0200 schrieb Sven Neumann:
>>
>>  > Hi,
>>  >
>>  > On Wed, 2006-07-05 at 16:29 -0400, Hubert Figuiere wrote:
>>  > 
>>  > > > What about http://www.eci.org/eci/en/040_colour_standards.php ? Their
>>  > > > profiles could serve as an alternative for AdobeRGB, couldn't they?
>>  > >
>>  > > How does it help if the pictures are in the AdobeRGB colorspace?
>>  >
>>  > Users would still have to download the AdobeRGB profile from Adobe, of
>>  > course. But at least they would have a reasonable RGB profile to work
>>  > with. And long-term it might make AdobeRGB less important.
>>  >
>>  >
>>  > Sven
>>  >
>_______________________________________________
>openicc mailing list
>openicc at lists.freedesktop.org
>http://lists.freedesktop.org/mailman/listinfo/openicc



More information about the openicc mailing list