Damien wrote:
> I'm so sad this proposal did not trigger any further discussion.
I had not forgotten about it, but a serious reply is serious work.
actually, a serious reply means solving the open issues around this
theme, some of which you pointed out in your, ehm fiery, posting.
--ps
Omari Stephens wrote:
> For one, as Sven pointed out, we can't ship the AdobeRGB color profile.
> This means that even if we know it _should_ be AdobeRGB, the user will
> need to take some action either to make that profile available or to tag
> it manually.
i think that is a special case of 'inv
hi all,
this is work in progress, mostly in analysis stage and a bit chaotic,
but there are already some conclusions which might be worth discussing.
any comments appreciated,
yahvuu
>From the product vision follows a tightly coupled workflow as default,
where each file should have a profile e
Omari Stephens wrote:
> For one, as Sven pointed out, we can't ship the AdobeRGB color profile.
> This means that even if we know it _should_ be AdobeRGB, the user will
> need to take some action either to make that profile available or to tag
> it manually.
Why can't you apply a profile compati
On 02/08/2010 07:41 PM, Graeme Gill wrote:
>
> Omari Stephens wrote:
>> For one, as Sven pointed out, we can't ship the AdobeRGB color profile.
>> This means that even if we know it _should_ be AdobeRGB, the user will
>> need to take some action either to make that profile available or to tag
>>
Omari Stephens wrote:").
> What does "compatible with AdobeRGB" actually mean?
It means that it was written to conform to Adobe's published
specification of AdobeRGB.
> How does
> "compatible with AdobeRGB" differ from "AdobeRGB"? (Note: I assume that
> you know what you're talking about here
