Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why are "cornflowerblue" and "cornflower blue" different colors? #15

Open
AlexKnauth opened this issue Jan 19, 2019 · 5 comments
Open

Comments

@AlexKnauth
Copy link
Member

There are several places in racket/draw/private/color.rkt where two names differ by a space, but are defined as the same color. However, "cornflowerblue" and "cornflower blue" seem to break this pattern. Is there a reason why they are different?

Definition of "cornflowerblue":
https://github.com/racket/draw/blob/master/draw-lib/racket/draw/private/color.rkt#L143

 ("cornflowerblue" . #(100 149 237))

#6495ed

Definition of "cornflower blue":
https://github.com/racket/draw/blob/master/draw-lib/racket/draw/private/color.rkt#L249

 ("cornflower blue" . #(68 64 108))

#44406c

It looks like "cornflowerblue" without the space has the same RGB values as the X11 cornflower blue on https://en.wikipedia.org/wiki/Cornflower_blue, so where do the RGB values for "cornflower blue" with the space come from? Is it a mistake or intentional?

@soegaard
Copy link
Member

soegaard commented Jan 19, 2019 via email

@AlexKnauth
Copy link
Member Author

Thanks, I edited to specify that it matches the X11 cornflower blue from that page.

@AlexKnauth
Copy link
Member Author

AlexKnauth commented Jan 19, 2019

A similar thing happened with "cadetblue" and "cadet blue", although with those the difference between them is much less, only #(95 158 160) vs. #(96 160 160), still within 1% of each other.

The X11 definition of cadet blue seems to use the #(95 158 160) version.

@fjsweeney
Copy link

Per PR 16, it was decided that the differences should be maintained (for some reason). Can someone explain that in a better way, then close this issue? (since I am tempted to just make a PR to standardize to the X11 colors, but that is The Wrong Thing, I don't want others to make the same mistake.)

@samth
Copy link
Member

samth commented Sep 27, 2023

The reason not to change is that existing programs (eg slides or image generators or web pages etc) might use the colors, and standardizing would change the behavior of those programs and make the results look different and potentially worse.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants