From: Steve Purcell <steve@sanityinc.com>
To: David De La Harpe Golden <david@harpegolden.net>
Cc: 8402@debbugs.gnu.org, Erik Andrejko <eandrejko@gmail.com>,
Chong Yidong <cyd@stupidchicken.com>
Subject: bug#8402: Acknowledgement (24.0.50; Hex colors are not rendered correctly on OS X (Cocoa))
Date: Thu, 5 May 2011 19:43:04 +0100 [thread overview]
Message-ID: <FCB3A8BF-B9B2-452E-B004-AD1541788473@sanityinc.com> (raw)
In-Reply-To: <4DC2A0FB.7080209@harpegolden.net>
On 5 May 2011, at 14:07, David De La Harpe Golden wrote:
> On 05/05/11 12:13, David De La Harpe Golden wrote:
>> On 05/05/11 10:17, Steve Purcell wrote:
>>>
>>> Would there be a problem if X11 was left as-is, and NS started to
>>> interpret #rrggbb as sRGB?
>>>
>>
>> Shrug. Insofar as with the current situation one can't expect the
>> colors to match across the platforms anyway, I guess it wouldn't matter
>> much.
>
> though (just to spell out more for the archives than respondents who likely understood this) - ns emacs is currently using NSCalibratedRGBColorSpace as Chong Yidong already mentioned and afaics, so it would be a change on ns itself for ns switch to sRGB, I just meant it wouldn't be making interplatform compat worse particularly.
I think I've been conflating sRGB and device colors. What I'd be in favor of right now would be somebody changing NS to use device RGB colors by default, and seeing if the world falls apart. The indications are that it would improve matters for NS emacs users without upsetting anyone else.
Having a customization for the NS colorspace would be a nice-to-have, and the possibility of having colors displayed identically across all window-systems would be a laudable longer-term goal.
next prev parent reply other threads:[~2011-05-05 18:43 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-01 10:01 bug#8402: 24.0.50; Hex colors are not rendered correctly on OS X (Cocoa) Steve Purcell
[not found] ` <handler.8402.B.130165209313902.ack@debbugs.gnu.org>
2011-04-01 11:03 ` bug#8402: Acknowledgement (24.0.50; Hex colors are not rendered correctly on OS X (Cocoa)) Steve Purcell
2011-04-03 21:29 ` Steve Purcell
2011-04-08 4:36 ` Erik Andrejko
2011-04-08 7:15 ` Steve Purcell
2011-04-10 22:38 ` Chong Yidong
2011-04-23 20:36 ` Steve Purcell
2011-05-04 16:58 ` David De La Harpe Golden
2011-05-04 19:31 ` Steve Purcell
2011-05-05 8:14 ` David De La Harpe Golden
2011-05-05 9:17 ` Steve Purcell
2011-05-05 11:13 ` David De La Harpe Golden
2011-05-05 13:07 ` David De La Harpe Golden
2011-05-05 18:43 ` Steve Purcell [this message]
2011-05-05 22:53 ` David De La Harpe Golden
2011-05-06 7:00 ` Steve Purcell
2011-05-06 19:59 ` David De La Harpe Golden
2011-05-06 21:24 ` Steve Purcell
2011-05-05 23:56 ` David De La Harpe Golden
2011-05-07 1:55 ` David De La Harpe Golden
2011-04-14 2:55 ` bug#8402: bug 8402 Travis Vachon
2011-05-04 12:52 ` bug#8402: Acknowledgement (24.0.50; Hex colors are not rendered correctly on OS X (Cocoa)) Steve Purcell
2022-04-23 14:48 ` bug#8402: 24.0.50; Hex colors are not rendered correctly on OS X (Cocoa) Lars Ingebrigtsen
2022-04-23 21:33 ` Howard Melman
2022-04-23 22:22 ` Alan Third
2022-04-24 11:59 ` Lars Ingebrigtsen
2022-04-24 14:27 ` steve
2022-04-24 14:29 ` Lars Ingebrigtsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=FCB3A8BF-B9B2-452E-B004-AD1541788473@sanityinc.com \
--to=steve@sanityinc.com \
--cc=8402@debbugs.gnu.org \
--cc=cyd@stupidchicken.com \
--cc=david@harpegolden.net \
--cc=eandrejko@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).