This is the
talk page for discussing improvements to the
Infobox color template. |
|
![]() | This template does not require a rating on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||
|
![]() | This template was considered for deletion on 2020 April 6. The result of the discussion was "do not merge". |
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?:
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)
I propose to put "units" to the infobox because this would help to identify the ranges:
-- suruena 10:32, 2005 Apr 10 (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):
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:
-- surueña 08:25, 2005 May 11 (UTC)
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)
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 know what "Normalized to [0-255]" means, but what does "Changing to [0-100]" mean? Lefty 07:20, 11 February 2006 (UTC)
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)
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)
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)
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).
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)
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)
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)
Most templates which include images also include the ability to optionally include caption =
. Over at
Indigo, a caption would be helpful. Can we add the caption parameter as implemented elsewhere? --
Lexein (
talk)
02:06, 24 August 2011 (UTC)
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Please copy the code from Template:Infobox color/sandbox over to Template:Infobox color. Per consensus above, and completed testing. Thanks. -- Quiddity ( talk) 22:15, 26 July 2012 (UTC)
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Once more please, copy the code from Template:Infobox color/sandbox to this template. This change fixes some linewrap problems, using 2 {{ nowrap}} templates, and removes some trailing spaces (see the testcases page for before&after examples). Thanks. -- Quiddity ( talk) 11:42, 31 July 2012 (UTC)
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)
I've updated the sandbox so variations are once again full width. Look okay? (see testcases) PaleAqua ( talk) 08:49, 1 August 2012 (UTC)
This was what I was thinking awhile back Wikipedia talk:WikiProject Color/Archive 7#Discussion about the color boxes. PaleAqua ( talk) 21:39, 1 August 2012 (UTC)
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
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)
I'd like to add three optional params: |RGBnote=
; |HSVnote=
; and |CMYKnote=
. 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)
In August 2013,
SiefkinDR (
talk ·
contribs) 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 (
d
c̄)
20:11, 31 December 2018 (UTC)
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)
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)
For some colors, particularly colors of light rather than colors of objects, such as the "average color of the universe" Cosmic latte, it would make sense to provide the color's CIE coordinates in XYZ, xyY, or in the case of unspecified brightness, just xy. Could those be added as optional fields, to go alongside RGB values when appropriate? — Maggie David P. K. Haynes 2600:1700:C190:4AE0:24B6:2CC0:1A3C:2627 ( talk) 21:12, 17 September 2020 (UTC)
#404735
if you use a colour picker on the
base image (or directly on a screenshot of the website). The Source field in the infobox says the current (incorrect) hex was computed from sRGB values and the computation is correct, but the values clearly are not. So I would (1) fix the hex and (2) cite
[4] this as the source for the colour in the infobox and in the last paragraph of the text.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)
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:
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)
This is the
talk page for discussing improvements to the
Infobox color template. |
|
![]() | This template does not require a rating on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||
|
![]() | This template was considered for deletion on 2020 April 6. The result of the discussion was "do not merge". |
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?:
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)
I propose to put "units" to the infobox because this would help to identify the ranges:
-- suruena 10:32, 2005 Apr 10 (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):
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:
-- surueña 08:25, 2005 May 11 (UTC)
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)
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 know what "Normalized to [0-255]" means, but what does "Changing to [0-100]" mean? Lefty 07:20, 11 February 2006 (UTC)
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)
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)
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)
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).
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)
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)
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)
Most templates which include images also include the ability to optionally include caption =
. Over at
Indigo, a caption would be helpful. Can we add the caption parameter as implemented elsewhere? --
Lexein (
talk)
02:06, 24 August 2011 (UTC)
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Please copy the code from Template:Infobox color/sandbox over to Template:Infobox color. Per consensus above, and completed testing. Thanks. -- Quiddity ( talk) 22:15, 26 July 2012 (UTC)
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Once more please, copy the code from Template:Infobox color/sandbox to this template. This change fixes some linewrap problems, using 2 {{ nowrap}} templates, and removes some trailing spaces (see the testcases page for before&after examples). Thanks. -- Quiddity ( talk) 11:42, 31 July 2012 (UTC)
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)
I've updated the sandbox so variations are once again full width. Look okay? (see testcases) PaleAqua ( talk) 08:49, 1 August 2012 (UTC)
This was what I was thinking awhile back Wikipedia talk:WikiProject Color/Archive 7#Discussion about the color boxes. PaleAqua ( talk) 21:39, 1 August 2012 (UTC)
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
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)
I'd like to add three optional params: |RGBnote=
; |HSVnote=
; and |CMYKnote=
. 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)
In August 2013,
SiefkinDR (
talk ·
contribs) 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 (
d
c̄)
20:11, 31 December 2018 (UTC)
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)
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)
For some colors, particularly colors of light rather than colors of objects, such as the "average color of the universe" Cosmic latte, it would make sense to provide the color's CIE coordinates in XYZ, xyY, or in the case of unspecified brightness, just xy. Could those be added as optional fields, to go alongside RGB values when appropriate? — Maggie David P. K. Haynes 2600:1700:C190:4AE0:24B6:2CC0:1A3C:2627 ( talk) 21:12, 17 September 2020 (UTC)
#404735
if you use a colour picker on the
base image (or directly on a screenshot of the website). The Source field in the infobox says the current (incorrect) hex was computed from sRGB values and the computation is correct, but the values clearly are not. So I would (1) fix the hex and (2) cite
[4] this as the source for the colour in the infobox and in the last paragraph of the text.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)
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:
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)