From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Stephen J. Turnbull" Newsgroups: gmane.emacs.devel Subject: Re: sRGB color support in NS port [PATCH] Date: Sun, 22 Dec 2013 09:31:26 +0900 Message-ID: <87ob49ohep.fsf@uwakimon.sk.tsukuba.ac.jp> 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> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 X-Trace: ger.gmane.org 1387672310 7502 80.91.229.3 (22 Dec 2013 00:31:50 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 22 Dec 2013 00:31:50 +0000 (UTC) Cc: Steve Purcell , Eli Zaretskii , Jan =?utf-8?Q?Dj=C3=A4rv?= , Bozhidar Batsov , emacs-devel To: David De La Harpe Golden Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Dec 22 01:31:55 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 1VuWxW-0004Hq-RW for ged-emacs-devel@m.gmane.org; Sun, 22 Dec 2013 01:31:54 +0100 Original-Received: from localhost ([::1]:56152 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VuWxV-0008H6-UZ for ged-emacs-devel@m.gmane.org; Sat, 21 Dec 2013 19:31:53 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:60050) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VuWxM-0008Gv-6o for emacs-devel@gnu.org; Sat, 21 Dec 2013 19:31:51 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VuWxE-0003kE-TR for emacs-devel@gnu.org; Sat, 21 Dec 2013 19:31:44 -0500 Original-Received: from mgmt2.sk.tsukuba.ac.jp ([130.158.97.224]:45583) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VuWx6-0003hz-QD; Sat, 21 Dec 2013 19:31:29 -0500 Original-Received: from uwakimon.sk.tsukuba.ac.jp (uwakimon.sk.tsukuba.ac.jp [130.158.99.156]) by mgmt2.sk.tsukuba.ac.jp (Postfix) with ESMTP id 3DFE69709A5; Sun, 22 Dec 2013 09:31:26 +0900 (JST) Original-Received: by uwakimon.sk.tsukuba.ac.jp (Postfix, from userid 1000) id 33CAC136F25; Sun, 22 Dec 2013 09:31:26 +0900 (JST) In-Reply-To: <52B5F992.2020505@harpegolden.net> X-Mailer: VM undefined under 21.5 (beta34) "kale" 2a0f42961ed4 XEmacs Lucid (x86_64-unknown-linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 130.158.97.224 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:166715 Archived-At: David De La Harpe Golden writes: > But Emacs is presently primarily a (coding-friendly) text-editor > (leaving aside recent discussions about wysiwig word processing). So > sRGB, whatever its failings, seems fairly adequate for emacs' normal > duties. +1 Please, let's stop trying to make core Emacs suitable for tasks that other projects have spent man-decades (in some cases, man-centuries) on. > If emacs devs were to just up and declare: > > """On color-management-capable platforms, where possible emacs shall > default to sRGB for interpretation of rgb triples without any explicit > color space declaration.""" > > (and maybe a related: """emacs will adopt the static list of > HTML/CSS/SVG named-color definitions where applicable, superseding any > historical X11/emacs named-color definitions - and user-defined > named-colors on platforms that support them (i.e. X11) - where they > clash""" [3][4]) +0.9 IWBNI Emacs also provided a way to get the effect of the old names. I doubt anybody is going to notice the difference between sRGB and RGB (except maybe themers who are matching WMs that use a different color space). But if names conflict, anything can happen. (It was years before I realized that "cyan" was on the G side of B, and a bit embarrassing when my nose was rubbed in the fact. :-) > 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, and provide a trivial textual translator for those strings, plus one that reads in rgb.txt as device-dependent. > (The alternative, changing ns/mac and w32 to treat #RRGGBB as > device-dependent and require explicit color space prefixing for anything > else for full "feature"-compatibility with X11, doesn't seem all that > attractive, but would also be consistent... I mention it for > completeness) It doesn't seem very future-proof. Steve