Template talk:Infobox Color
From Wikipedia, the free encyclopedia
Contents |
[edit] Color ranges
Adding the International Klein Blue (Pantone 285) I found different values for the CMYK value ([1] [2] and [3]). 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)
[edit] Units
I propose to put "units" to the infobox because this would help to identify the ranges:
- HSV (h, s, v) ({{{h}}}°, {{{s}}}%, {{{v}}}%)
--suruena 10:32, 2005 Apr 10 (UTC)
- Done. I've also noted the range into which the other units are normalised. I shall do my best to go back and check this. --Phil | Talk 08:38, Apr 11, 2005 (UTC)
Hello again. If the CMYK value is now being normalised to 0-100 I think we should add some % to specify the units (as with the HSV, like above):
- CMYK (c, m, y, k) ({{{c}}}%, {{{m}}}%, {{{y}}}%, {{{k}}}%)
Also, why not use the same range for the RGB values? I know very little about this theme, but IMHO altough nowadays 8bits are used to represent a component of an RGB value probably in the future the number of bits used to represent every component will be increased. So a percentage is an exact solution that assures the "future", and anyway no information is lost because the 24bit RGB value is maintained in the hex triplet. So I propose to change the RGB representation too:
- RGB (r, g, b) ({{{r}}}%, {{{g}}}%, {{{b}}}%)
--surueña 08:25, 2005 May 11 (UTC)
[edit] modular/splitting template
I suggest a way to add a line "this color is also a named web color" with its hex triplet and swatch.. Circeus 21:49, Apr 20, 2005 (UTC)
- This infobox is big enough for the time being. Also bear in mind that actually very few colors which will have their own article are ikely to be valid web colors. The standard 16 web colors, and the extra added for CSS, are already linked using {{web colors}}. If you want to link to X11 color names from each article linked from there, feel free. Please make a note of what you are doing at WikiProject Color. --Phil | Talk 09:05, Apr 21, 2005 (UTC)
[edit] Please think twice
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)
[edit] Changing to [0-100]
I know what "Normalized to [0-255]" means, but what does "Changing to [0-100]" mean? Lefty 07:20, 11 February 2006 (UTC)
[edit] sRGB
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)
- 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)
Hear hear. How about defining a field that could contain a) a reference (this color is ... by standard this-and-that), b) a definition (this color is red by definiton of the sRGB color model) or c) a notice like "this is only a sample of what this colour might look like and the values used to..." etc. etc. That way the user would know what the numbers mean. If we want to keep the CMYK colors, we would need to have a properly defined CMYK color space. Shinobu 08:39, 7 March 2006 (UTC)
[edit] color vs. colour
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)
- 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)