From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David De La Harpe Golden Newsgroups: gmane.emacs.devel Subject: Re: sRGB color support in NS port [PATCH] Date: Sun, 22 Dec 2013 21:20:41 +0000 Message-ID: <52B757A9.6080507@harpegolden.net> References: <23825B39C60F460E80B59C5ADF04F637@gmail.com> <83zjnv9yrp.fsf@gnu.org> <16B838CD-13DC-468E-94D1-108EBFE68F6D@swipnet.se> <7FA1C0353EC248D28B9E7242BA7BDFCC@gmail.com> <933E75DF-F665-46C0-8D82-111186A809B1@sanityinc.com> <3C0A35C3-5D2B-4E6A-9C63-9EE98056DC3A@swipnet.se> <1EE253E4-A38A-4747-A96C-F5ABC5C1CB2C@sanityinc.com> <52B5F992.2020505@harpegolden.net> <87ob49ohep.fsf@uwakimon.sk.tsukuba.ac.jp> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1387747259 15093 80.91.229.3 (22 Dec 2013 21:20:59 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 22 Dec 2013 21:20:59 +0000 (UTC) Cc: Steve Purcell , Eli Zaretskii , =?UTF-8?B?SmFuIERqw6Rydg==?= , Bozhidar Batsov , emacs-devel To: "Stephen J. Turnbull" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Dec 22 22:21:06 2013 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1VuqSN-0007M8-Uw for ged-emacs-devel@m.gmane.org; Sun, 22 Dec 2013 22:21:04 +0100 Original-Received: from localhost ([::1]:59294 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VuqSN-0005tR-C3 for ged-emacs-devel@m.gmane.org; Sun, 22 Dec 2013 16:21:03 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:55936) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VuqSG-0005tD-Dz for emacs-devel@gnu.org; Sun, 22 Dec 2013 16:21:01 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VuqSB-0008Vu-47 for emacs-devel@gnu.org; Sun, 22 Dec 2013 16:20:56 -0500 Original-Received: from harpegolden.net ([65.99.215.13]:45171) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VuqS5-0008VY-BY; Sun, 22 Dec 2013 16:20:45 -0500 Original-Received: from [87.198.55.73] (87-198-55-73.ptr.magnet.ie [87.198.55.73]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "David De La Harpe Golden", Issuer "David De La Harpe Golden Personal CA 4" (verified OK)) by harpegolden.net (Postfix) with ESMTPSA id 8E5103C03A; Sun, 22 Dec 2013 21:20:43 +0000 (UTC) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20131103 Icedove/17.0.10 In-Reply-To: <87ob49ohep.fsf@uwakimon.sk.tsukuba.ac.jp> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 65.99.215.13 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:166738 Archived-At: On 22/12/13 00:31, Stephen J. Turnbull wrote: > +0.9 IWBNI Emacs also provided a way to get the effect of the old > names. Not impossible, one could imagine a list of resolvers, or a scope prefix. Though bear in mind there are apparently (sayeth wikipedia) only ~4 real conflicts (though I suppose not rare colors: gray, green, maroon, purple) [1] (at least ignoring user-defined named colors), so it may not be worth it, especially as you could still set the x-like color by rgb triple. > > Unfortunately, "#RRGGBB" and "rgb:r/g/b" and "rgbi:r/g/b" are all > > _explicitly defined_ to be in the vague device-dependent space in the > > X11 syntax (man XParseColors). > > I think the thing to do here is to steal "#RGB" for sRGB, Well, what's more important... That #0DEA84 is the same color on x11/mac/ns/w32 emacs or the same color in x11 emacs/xterm/xclock... Mind you, I do now belatedly recall: last I heard/understood of plans in the area (some time ago now), was that a color-managing compositor plugin component of the "new" color management stack [2] would "soon" mean that any such x11 nominally-device-dependent rgb colors presented by said-new-stack unaware clients _would_ nonetheless ultimately tend to end up being interpreted as sRGB on x11 too (!), despite my earlier claims & their historical definition. Though I don't know how widely adopted that infrastructure is yet [3]. [1] http://en.wikipedia.org/wiki/X11_colors#Color_name_clashes [2] http://www.oyranos.org/compicc/ [3] http://sourceforge.net/p/oyranos/feature-requests/2/#d625