Template talk:Infobox color

message: Adding the International Klein Blue (Pantone 285) I found different values for the CMYK value (  and ). I suppose that one of the problems is that the color ranges are different. Is the following correct?:
* Hex triplet : 00 - FF
* RGB: 0 - 255
* CMYK: 0 - 255
* HSV: 0-360°, 0-100%, 0-100%
I will convert the CMYK value I've found (0-100) to the correct range (0-255). Please, if I'm wrong please correct the International Klein Blue article. Thanks. --suruena 16:23, 2005 Apr 9 (UTC)
:Ranges are part of the problem, but the most important thing is that conversion to CMYK is not standardised. This is why CMYK has no place in these info boxes, except for colors defined by some standard in terms of CMYK. Notinasnaid 10:07, 26 February 2006 (UTC)
thread_title:  Color ranges 

message: I think the color values you provide here can be misinformation. Has any of you consulted a real color expert before doing this? You cannot send a set of RGB or CMYK values to a printer (I mean a person, not a computer peripheral) and expect him/her to give you your expected color. These color spaces are device-dependant!
You cannot just create a color in Photoshop and get its color values from that program. -- Toytoy 01:47, Apr 29, 2005 (UTC)
:I agree. Does anyone else see a major problem with the whole concept of providing these boxes for nonstandardised colors? It is original research, and should be removed. Notinasnaid 10:01, 26 February 2006 (UTC)
thread_title:  Please think twice 

message: I know what "Normalized to [0-255]" means, but what does "Changing to [0-100]" mean? Lefty 07:20, 11 February 2006 (UTC)
thread_title: Changing to [0-100]

message: I think it should read sRGB instead of RGB. Not only would it be preferable to have an absolute color space in the infobox, but I think that most RGB values in this infobox are already in sRGB as it is. Any comments? Shinobu 02:00, 5 March 2006 (UTC)
replies: text: It would at least have some meaning. At the moment it is not meaningful except for colors that are defined by some standard in uncalibrated RGB.  The CMYK should absolutely be removed in all cases except those that are uncalibrated CMYK in some standard.  But there is a far more serious problem with these info boxes: there are no sources, no references. Under Wikipedia rules anything without a source should be removed.  If the box is to remain, it needs to indicate according to what standard or reference this is "Red", "Burnt umber" or whatever. I think a significant amount of (forbidden) original research has gone into some of the colors. Notinasnaid 21:01, 6 March 2006 (UTC)
thread_title:  sRGB 

message: I just reverted a change at Orange (colour) where an anon changed all of the instances of "colour" (which was standard within the article) to "color". While I'm sure the edit was made in good faith, I reverted it to "colour" since the article was at "colour", rather than "color", and since guidelines suggest that consistency is important. I realized soon afterwards that I should check for other instances of the word "color" rather than "colour" in the article, and started a quick word search. I noted that each instance of this template used "color". Since this is awkward for articles written with the "colour" spelling, I propose that another parameter be added to this template: spelling. If there were a parameter that let the spelling be set, it would be much easier to standardize articles without automatically favoring the spelling used by this template. Nihiltres 19:29, 7 November 2006 (UTC)
replies: text: Since nobody's responded, I'm going to try to modify the template myself. I'll add how to use this extra feature to the template documentation once I'm done. Nihiltres 16:56, 13 November 2006 (UTC)
thread_title:  color vs. colour 

message: I would add Direct color:
The user could specify yes / no. By default direct color name would be set to 'no . See : :Template:Shades_of_green, [edit] Shades of green in text. —The preceding unsigned comment was added by Altermike (talk • contribs) 09:33, 18 March 2007 (UTC)
thread_title:  Direct color 

message: While I think that the addition of the  as a link explaining the infobox is quite appropriate, its overlap with the "hex"-parameter-coloured field can be disruptive in some articles, such as Orange (colour), where its blue color in comparison to the one discussed is disruptive or jarring. If someone can figure out a way to change the template so as to avoid this problem, I'm sure that many users will appreciate the small aesthetic improvement. Suggestions? Nihiltres 00:09, 5 April 2007 (UTC)
replies: text: I can think of a couple possibilities. One is to use an approach similar to textcolor. However that would require alternate versions of the image. Another possibility is to move it to the Color coordinates line. It actually might make more sense to have it there. PaleAqua 00:32, 5 April 2007 (UTC)
replies: text:  It looks much nicer now that you've moved it - I agree that it makes more sense there. Thanks, Nihiltres 02:31, 5 April 2007 (UTC)
thread_title:  infobox "about" link image 

message: would it be possible to add an option to have a block of the colour instead of a image? as it can be hard to get an idea of the colour from just the background of the text.  I would do it myself but don't have that much experience with template making, and don't want to break anything.--UltraMagnus (talk) 16:10, 1 October 2009 (UTC)
replies: text: How big a block? I suppose this is doable, although I'm still not convinced it's that useful. Chris Cunningham (not at work) - talk 11:11, 15 October 2009 (UTC)
thread_title:  suggestion 

message: We do have some color conversion templates. I suggest we employ them in this template so there only needs to be one set of RGB specified (probably in percentages) and others, like hash code, 8bit RGB values, HSL, HSV and probably more (not CMYK of course) would be generated automatically. — Christoph Päper 23:46, 10 September 2010 (UTC)
replies: text: We applied automatic conversion on it.wikipedia (see :it:Template:Infobox colore generico and :it:Template:Codifica colore). In this way, hex code is used to calculate automatically the following parameters: R, G, B, C, M, Y, K, H, L and V. Wavelenght is used instead to calculate frequency and photon energy. Please let me know if we can use the same principle here. --Daniele Pugliesi (talk) 14:56, 27 January 2020 (UTC)
thread_title:  Automatic conversion 

message: Looks like the new version is causing # to be treated as a numbered list when given as part of a parameter for wavelengths and frequencies. Probably not really worth fixing as it is rarely used that way and I fixed the one instance I found. PaleAqua (talk) 00:15, 31 July 2012 (UTC)
thread_title:  New version of the template breaks ## example values in wavelength and frequency parameters. 

message: Please copy the latest version of sandbox to the live template. ( I'm wondering if full protection is still necessary for this Infobox. Some of the other color project templates that were protected as highly visible templates have been since become semi-protected. )
PaleAqua (talk) 21:28, 1 August 2012 (UTC)
replies: text: , with the same entity -> Unicode tweak for degrees and dashes as before. As for unprotection, the usual procedure is to ask the admin who locked the template originally; I agree that this doesn't need more than semiprotection in any case, and personally I'd just drop protection altogether. Chris Cunningham (user:thumperward) (talk) 11:39, 2 August 2012 (UTC)
replies: text:  Thanks, I just asked Wknight94 about unprotection. PaleAqua (talk) 13:23, 2 August 2012 (UTC)
thread_title:  Edit request on 1 August 2012 

message: I'd like to add three optional params: ; ; and . If present, they will render after the closing parenthesis of the RGB, HSV, and CMYK value groups, respectively. The purpose is to provide cites for the individual coordinate sets, which are currently being inserted by appending them to the last color parameter in the set, creating ugly placement inside the parentheses and before the the final '%' (e.g. at Amaranth (color)). Any objections? —[AlanM1(talk)]— 23:15, 9 October 2013 (UTC)
replies: text: Those references should really be removed. Most of the coordinates given are Wikipedia:Synthesis. The current over use of color infoboxes implies that the color has an exact one to one representation of color terms to (s)RGB coordinate, which is not true. The references are basically just color coordinate calculators. Also RGB <-> CMYK conversions are dependent on several of factors, include the type of paper and the set of inks, as well as the whole additive vs subtractive thing.. PaleAqua (talk) 00:57, 10 October 2013 (UTC)
thread_title:  Add ref params 

message: In August 2013,  removed the implementation of the symbolism parameter in 9 of the 11 major color group articles as subjective, unsourced, and better covered in that article text. He/she removed the parameter from the remaining two articles (Green and Pink) about a month later for consistency. As it is unlikely to be used in any of the more specific color articles, should I remove the parameter outright? –LaundryPizza03 (dc̄) 20:11, 31 December 2018 (UTC)
thread_title:  Removing symbolism parameter 

message: Please watch out: neither color coordinates can be found in this infobox. Only color coordinates would be CIE xy and CIELAB L*a*b*. All are missing from the infobox. ZJ (talk) 16:03, 31 July 2020 (UTC)
replies: text: A good point. Where is the capacity to include L*a*b coordinates. GraemeLeggett (talk) 21:55, 13 January 2022 (UTC)
replies: text: I could easily code an automatic conversion to CIELab or CIELChab if there's consensus this information should appear in the infobox. Personally, I'm afraid this may not add much value to the articles about colors (but I might be wrong on this). CIELab is useful for measuring perceptual color contrast, but the coordinates themselves are not very useful for much else, see list of color spaces and their uses. To avoid feature creep (and the possible addition of as many color conversions as one can think of), I think it's best to pick which coordinates are really notable and useful, worthy of an encyclopedia for the general audience. I added CIELChuv because it is designed for perceptual uniformity and commonly used in information visualization. Like HSL and HSV, one can look at CIELChuv coordinates and have a good idea of what colour they represent, and comparisons between two pairs of such coordinates are meaningful to humans with normal vision: if two colours are perceived as having approximately the same lightness, L will be approximately the same regardless of other aspects; if they're perceived to have approximately the same hue, h will be approximately the same; and if they're approximately as colourful, even if their hues are very distinct, C will be approximately the same. You don't get that with the simpler HSV and HSL spaces, nor CIELab. --Fernando Trebien (talk) 18:46, 17 January 2022 (UTC)
replies: text: My opinion that the title line must be "dominant wvelength of colour stimulus" in short: dominant wavelength to fill in the title line space of the template. ZJ (talk) 12:28, 16 October 2023 (UTC)
thread_title:  bad titleline 

message: May I suggest a parameter to control the alignment of this infobox, as offered, for example, in Infobox_enzyme? 
This could help the readability of an article where the Infobox template is used within the body, such as Turquoise. Regards, Guffydrawers (talk) 12:52, 3 September 2020 (UTC)
thread_title:  Alignment 

message: I've commented on Talk:Shades of gray#Usage of space but I figure it's relevant here as well.  — Preceding unsigned comment added by 92.67.227.181 (talk) 20:39, 28 May 2022 (UTC)
thread_title:  Relevant comment on Talk:Shades of gray 

message: A constant hassle in this talkpage, in WP:COLOR, and pretty much all color articles, is the assumption that all colors can or should somehow be defined by specific sRGB coordinates. The format of these infoboxes has made it all too easy to find some questionable online source that will define any color term by sRGB, but I'd argue that most colors with an infobox should NOT be defined by a single sRGB coordinate and in many cases, no sRGB coordinates should be given at all.
I started a discussion in WP:COLOR, but it didn't get much traction. Technically, it is more specific to this template anyway. What I suggest(ed), is a way to classify colors based on how they are defined. I recommended the following classes:
* based on a digital definition or defined directly to sRGB (or at least CIEXYZ) coordinates. This would include web colors (e.g. Shades of yellow#Computer web color yellow) and most modern brand colors (e.g. Android green). These infoboxes would stay as-is.
* based on a pigment, defined chemically (e.g. Prussian blue or mummy brown); these do not have a direct relation to CIEXYZ and may not even represent a precise color. I would completely remove sRGB coordinates from this class of colors.
* based on some vague, imprecise natural referent (e.g. sapphire or sky blue), that must be best represented by a range of colors or shades. I'd be inclined to define these qualitatively instead of qualitative, or give an array of example colors, such as is done currently (in a way) with basic color terms like blue, see inset.
* based inextricably on a fixed, "precise" natural referent (e.g. uranian blue), that could be represented by a single color, and could make sense to define as in sRGB.
* a basic color term, (e.g. dark blue) that is vague by definition and can be related to a range of applicable colors, as we see in the inset, but defining dark blue in sRGB is pointless!
* based on a proprietary referent (anything pantone, crayola, RAL, Munsell, etc.) that can mostly be transformed rather reliably to CIEXYZ; I've seen many claim that this is an IP problem, but I don't know enough about how that is handled in WP.
The content of an infobox would therefore differ depending on what class the color term falls into, and of course, there can be several definitions of a color in different color classes, as we already see with most basic colors like blue, which starts with 6 definitions of "blue", spanning several classes. An indication of the class, in the infobox, with a hoverbox defining the class would also be useful. Curran919 (talk) 11:28, 8 January 2023 (UTC)
thread_title:  Defining a Color "Class"