From: Pip Cet <pipcet@gmail.com>
To: 36304@debbugs.gnu.org
Subject: bug#36304: 27.0.50; request: switch to the superior HTML #RGB convention for colors
Date: Thu, 20 Jun 2019 11:22:24 +0000 [thread overview]
Message-ID: <CAOqdjBfzpaM1v8FJaQ_UBdfmoDWa49phEXieHOjvXLByYCgZwQ@mail.gmail.com> (raw)
This is a request for an incompatible change, which I think will
improve some matters significantly:
The Web convention, used by HTML and SVG, is that #fff is parsed as
#ffffff, and represents "white". The X convention, discouraged for
years, is to accept #fff as shorthand for #f0f0f0, and #ffffff as
shorthand for #ff00ff00ff00, with no way of specifying the whitest
color as six (or three) hex digits.
We're still using the X convention. It's time to switch. The HTML
convention is what virtually everyone would expect these days, it
allows specifying "white" concisely, and it's what we use in some
contexts, such as when rendering SVGs.
Not fixing this would result in somewhat hard-to-track-down color bugs
all over the place, particularly when combining images and text or
using non-X window systems or non-8-bit color depths (again, "#ffffff"
isn't the same as "white" on those!)
There's no reason, as far as I can see, to burden everyone with a
deficiency of one specific graphics backend, in perpetuity,
particularly since the colors will stay similar but not quite the
same.
This issue was discussed years ago as bug #8402, so feel free to mark
this as a duplicate if it helps.
next reply other threads:[~2019-06-20 11:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 11:22 Pip Cet [this message]
2019-06-21 1:54 ` bug#36304: 27.0.50; request: switch to the superior HTML #RGB convention for colors Richard Stallman
2019-06-22 11:23 ` Pip Cet
2019-06-22 11:40 ` Eli Zaretskii
2019-06-22 12:13 ` Pip Cet
2019-06-22 12:35 ` Eli Zaretskii
2019-06-22 14:41 ` Pip Cet
2019-06-22 15:05 ` Eli Zaretskii
2019-06-22 15:33 ` Pip Cet
2019-06-28 8:12 ` Eli Zaretskii
2019-06-28 9:28 ` Pip Cet
2019-06-28 9:42 ` Robert Pluim
2019-06-28 10:00 ` Pip Cet
2019-06-28 13:07 ` Andy Moreton
2019-06-28 12:33 ` Eli Zaretskii
2019-06-28 14:34 ` Pip Cet
2019-06-28 19:54 ` Eli Zaretskii
2019-06-28 21:27 ` Andy Moreton
2019-07-22 2:46 ` Pip Cet
2019-07-27 11:12 ` Eli Zaretskii
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=CAOqdjBfzpaM1v8FJaQ_UBdfmoDWa49phEXieHOjvXLByYCgZwQ@mail.gmail.com \
--to=pipcet@gmail.com \
--cc=36304@debbugs.gnu.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.