On 2/10/10, yahvuu wrote:
> Among garden-variety photo labs, it's pretty much standard to discard any
> color profile information and just assume sRGB.
It's pretty much standard where you live maybe, but not where *I* live :)
Alexandre
___
Gimp-develop
Martin Nordholts wrote:
> "4) When an image with an explicit profile is exported
>c) If the file format has no way to embed color profile information,
> (FIXME!)"
>
> In terms of a problem, this is pretty similar to "when an image has
> several layers and we export to an image format that d
I had composed a response, and then shortly before sending, WIFI on my
laptop conked out. I think yahvuu covered most of what I was going to
say, though. I'll send it anyway when I pull the laptop out again.
--xsdg
On 02/10/2010 07:09 PM, yahvuu wrote:
> Martin Nordholts wrote:
>> On 02/07/20
Martin Nordholts wrote:
> On 02/07/2010 04:55 AM, Omari Stephens wrote:
> "1) When an image is opened with no associated color profile, we assume
> that it is encoded in sRGB space."
>
> I don't think we should assume that, do you have an example use case
> where that is a good idea?
I think t
On 02/07/2010 04:55 AM, Omari Stephens wrote:
> Hi, all
>
> I wrote up a quick spec for how GIMP should deal with color profiles
> associated with files and images. The spec is attached, and is also
> attached to bug 608961. If you have any general thoughts/comments, I
> would love to hear them, bu
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
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:
> 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
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
On 02/08/2010 01:39 AM, Graeme Gill wrote:
> Omari Stephens wrote:
>> Obviously, options for both of these things are "prompt the user." It seems
>> like there
>> should be better alternatives, but I'm not sure what they might be.
>> guiguru? others?
>
> You're better having a set of default
Omari Stephens wrote:
> Obviously, options for both of these things are "prompt the user." It seems
> like there
> should be better alternatives, but I'm not sure what they might be.
> guiguru? others?
You're better having a set of defaults that the user can configure,
so they aren't constan
NOTE: if someone wants to think about the UI/UX involved in the color
management spec, I would really appreciate it. Right now, I have no
time for thinking outside the box — it's all I can do to find 30 minutes
here and there to do some GIMP hacking as it is. So if you don't want
to see more
Hi all,
Omari Stephens wrote:
> Hi, all
>
> I wrote up a quick spec for how GIMP should deal with color profiles
> associated with files and images. The spec is attached, and is also
> attached to bug 608961. If you have any general thoughts/comments, I
> would love to hear them, but please not
13 matches
Mail list logo
