all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Miles Bader <miles@gnu.org>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: Emacs-Devel devel <emacs-devel@gnu.org>,
	Lennart Borgman <lennart.borgman@gmail.com>,
	Jason Rumney <jasonr@gnu.org>
Subject: Re: Which one has the right color, Emacs or GIMP?
Date: Tue, 28 Jul 2009 10:44:31 +0900	[thread overview]
Message-ID: <87fxchbmyo.fsf@catnip.gol.com> (raw)
In-Reply-To: <87ljm9bnna.fsf@uwakimon.sk.tsukuba.ac.jp> (Stephen J. Turnbull's message of "Tue, 28 Jul 2009 10:29:45 +0900")

"Stephen J. Turnbull" <stephen@xemacs.org> writes:
>  > GIMP, as a specialist image editing application, is probably taking 
>  > things like monitor gamma into consideration.
>
> I thought of that, but upon reconsideration I hope GIMP would not do
> that.  RGBA? is the color equivalent of assembly language.
>
> If you want to deal with monitor gamma etc, use a color space designed
> for such adaptation.

Huh?  RGBA is just a notation for a storage format, it says nothing
about how the components should or should-not-be interpreted.

The gimp, however (and emacs) needs to worry about such things
regardless, since in the end it's in charge of what the user sees;
hopefully there's helpful meta-data which says what to do...

-Miles

-- 
We live, as we dream -- alone....




  reply	other threads:[~2009-07-28  1:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-27 13:38 Which one has the right color, Emacs or GIMP? Lennart Borgman
2009-07-27 14:25 ` Andreas Schwab
2009-07-27 14:32   ` Lennart Borgman
2009-07-27 23:52 ` Jason Rumney
2009-07-28  1:29   ` Stephen J. Turnbull
2009-07-28  1:44     ` Miles Bader [this message]
2009-07-28  2:44       ` Stephen J. Turnbull
2009-07-28  3:28         ` Miles Bader
2009-07-28  4:40           ` Stephen J. Turnbull
2009-07-28  6:20             ` Miles Bader

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fxchbmyo.fsf@catnip.gol.com \
    --to=miles@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jasonr@gnu.org \
    --cc=lennart.borgman@gmail.com \
    --cc=stephen@xemacs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.