Talk:BSicon/Colors/Archive 1

From Wikimedia Commons, the free media repository
Jump to: navigation, search
Archive This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page.

Old discussion

Moved from Category talk:Icons for railway descriptions/other colors. (Seems that all points has been covered meanwhile in the discussion above, but still, here for reference.)

It has been suggested that the BS icon hex value color sets be replaced with ones using "natural" names. This table displays each of the colors in use, alongside the closest named HTML color. (Some are much closer than others, and two sets— FFFF00  and  A9A9AA —are exact matches.) The last column lists a possible two-letter mnemonic for each color. Note that perception of color is not only very subjective, but also varies from monitor to monitor. Useddenim (talk) 12:37, 22 September 2012 (UTC)

Set color Closest HTML named color Mn.
0256A4 RoyalBlue 4169e1 RB
1A8BB9 SteelBlue 4682b4 SB
339999 DarkCyan 008b8b DC
3399FF DodgerBlue 1e90ff DB
9999FF LightSlateBlue 8470ff LS
99CCFF LightSkyBlue 87cefa LB
71592E Maroon 800000 MN
CC6600 Chocolate d2691e CH
EF161E Red ff0000 RD
FFAB2E Orange ffa500 OR
FFFF00 Yellow ffff00 YL
029B52 SeaGreen 2e8b57 SG
99CC00 YellowGreen 9acd32 YG
34C924 LimeGreen 32cd32 LG
B4EEB4 PaleGreen 98fb98 PG
999999 Gray 808080 GR
A9A9AA DarkGray a9a9aa DG
C0C0C0 Silver c71585 SI
B5198D MediumVioletRed c71585 VR

Close colours

Moved from Talk:BSicon/Obsolete and deletions#Close colours.

I am aware that "the human eye can distinguish about 10 million different colors", but I really doubt that we need as many colour sets for BSicons. Consider light blues, greys and light greens below. There are other pairs of close colours (and even triplets), but more readily distinguishable, so I'll leave them to please the aesthetics of different users. Besides, the RGB codes may be possibly assigned officially in other countries, who knows... In case of 999999/A9A9AA, 3399FF/029EE0 and 99CC00/B3D52E, the first set in a pair is always more developed that the other, while the second is only used for Moscow Metro lines (Serpukhovsko-Timiryazevskaya, Filyovskaya and Lyublinskaya respectively) in non-Russian Wikipedias (French and Spanish generally). Ru:wp uses the former colour sets, and as far as I know there are no official RGB codes for Moscow Metro. So, unless anybody opposes, I will replace all uses of icons from A9A9AA, 029EE0 and 99CC00 sets and nominate them for deletion. YLSS (talk) 20:49, 14 February 2013 (UTC)

There are several sensible reasons against keeping and mantaining sets of close color icons — not only because they cannot be used in the same diagram (where contrast is paramount), but also that a less attentive editor might mix and match from these sets to create or edit diagrams which are “good enough” with almost identical color shades, instead of exact matches. This goes against the very modularity and clearness having diagrams made from standartized building blocks is all about, after all. (However, discussions about colors should be covered in Talk:BSicon/Icon geometry and SVG code neatness, not here.) -- Tuválkin 00:13, 15 February 2013 (UTC)


moved from Talk:BSicon/New icons and icon requests#PNGs inside SVGs

Anyway,   (KBHFa 0065BD) seems to be yet another shade of blue and hard to tell apart from   (uKBHFa BlnU8). These additions seem to be frivolous — I’d have these two as duplicates and assimilated into the other BlnU8 icons. -- Tuválkin 03:54, 19 February 2013 (UTC)

I just noticed that, while the original uploader labelled these two as "0065BD", s/he had painted them in RGB:0078BE instead, which is closest to the single icon for the Mita line roundels in the icon set. Compare:
  (TokyoMita)  (lDST blue)
  (CPICma 0065BD)  (CPICma blue)
  (KBHFa 0065BD)  (KBHFa blue)
The whole thing is an unredeemable mess. Unless someone says no, I'll recolor and rename these two as Mita-color icons and later one have them integrated in any of the blue sets. -- Tuválkin 04:42, 20 February 2013 (UTC)
✓ Done -- Tuválkin 12:19, 21 February 2013 (UTC)

I would say that we need three or four shades of darker blue:

  1. 003399 - the "u" set. My bold proposal would be to rename respective categories to something other than "set blue". Maybe "U-Bahn", "light rail", "navy" or just "dark blue"? 'Cause I would reserve simple "blue" for some other set, for the ease of naming them.
  2. Something around 0256A4 or 00619F - present set 0256A4 and BlnU8. If I understand Туча right, this would get a wider usage after Moscow line 3 is repainted with it. This could be plain "blue" or possibly "indigo".
  3. 1A8BB9 - set 0256A4, which is used for Moscow line 11, but may give way to 339999 (I'll discuss this at ru.wp; if not merged, this set could be renamed "cerulean", although I'm afraid of such long names.)
  4. Possibly a fourth is needed for 0078BE & 0079C2. If implemented, this one could be plain "blue".

-- YLSS (talk) 22:45, 14 March 2013 (UTC)

I like that bold proposal ;-) I suggest "set u", cannot be simpler than that. ("U-Bahn" and "light rail" are not good because these icons are also used for canals.) -- Tuválkin 04:09, 15 March 2013 (UTC)
Here’s the existing blues — there are lot of them and hard to coalesce in clearly insular clusters. I agree that three, even four, are possible/necessary between u-blue and the already established set azure. At least 2 are mandatory, to tell apart Berlin’s U8 and U7, and Tokyo’s Mita and Tozai. (Of course one of these could be u-Blue and/or Azure, reducing this need to one single additional shade of blue, or even to zero…) Here's those blues, updated from above: -- Tuválkin 09:16, 24 March 2013 (UTC)
BSicon ulDST.svg BSicon lMENDEa.svg BSicon BHF denim.svg 100px BSicon lMENDEa.svg 100px BSicon BHF sky.svg BSicon lMENDEa.svg BSicon KDSTa azure.svg
set 0256A4
21 icons
15 icons
set 0078BE
9 icons
3 icons
set 1A8BB9
40 icons
10 icons
1 icons
set azure
53 icons
✓ u-Blue ✓ denim ✓ blue ✓ cerulean ✓ sky ✓ Azure
003399 0252A4 00619F 0078BE 0079C2 1A8BB9 069DD3 00A7DB 3399FF
6482C0 6597C6 649EC3 64ACD6 64ACD8 73B7D3 67C2E3 64C8E7 99CCFF
0695FF 85BBE0
  1. ∪ set 0256A4 (0252A2) + BlnU8 (00619F)
  2. ∪ set 0078BE (0078BE) + Mita (0079C2)
  3. ∪ BlnU7 (069DD3) + Tozal (00A7DB)
Useddenim (talk) 12:42, 24 March 2013 (UTC)
I agree and seems we have a consensus on the clustering. I reflected this in the table above, with provisional names going from “Blue I” to “Blue IV”. However the final exact shade and the names need to be decided too. Concerning the former, I'm sure we all agree that these 4 colors should be maximally different among themselves and from either u-Blue and Azure. As for the latter so far we have more or less agreed that the word "blue" (used only in the u-blue categories, not filenames) will be available and is to be use — this means 3 new names. -- Tuválkin 02:39, 27 March 2013 (UTC)

I think "cerulean" is a fine name for any of the sets (after all, we used "vert"). Circeus (talk) 06:37, 27 March 2013 (UTC)

BTW, I have second thoughts about "cerulean"... If we use it, and since we already have "fuchsia", "saffron" & "lavender", I have a strange desire to rename "red" as "vermilion", "jade" as "celadon" and "teal" as "viridian". Pity that "cinnabar" and "pewter" aren't used as colour names - although we can be the first ones to do so. What a beautiful Pallet we would then have! ;) YLSS (talk) 05:41, 5 April 2013 (UTC)

“Blue I”

  • I think we should keep the Berlin shade, as it is hazy and smokey and most distinct fron u-blue, even iff not less dark. Set 0256A4 has 21 icons but 9 of them need to be changed anyway, because they have an unacceptable ex-shade, so there’s not too much extra work for this. ✓ Done
  • As for the name, "indigo" was suggested. While it is not very close to actual indigo, it is a well known color name, more than "cerulean" or even "cobalt" (see name matches).

-- Tuválkin 02:39, 27 March 2013 (UTC)

Actually, indigo's purpleness is artificial given that traditionally it was much more blue. Since that this particular shade looks very much like the color of jeans (which were indeed traditional dyed with indigo), I think "denim" is a usable name if we choose to eschew Indigo as being "too purple". Circeus (talk) 00:44, 2 April 2013 (UTC)
So what does that make exICON_denim? Useddenim (talk) 01:04, 2 April 2013 (UTC)
Why, that’s you! -- Tuválkin 02:05, 2 April 2013 (UTC)
Denim sounds cool and appropriate. — ⟨µzdzisław⟩ 16:31, 3 April 2013 (UTC)
"Denim" ✓ implemented. -- Tuválkin 12:46, 5 April 2013 (UTC)
And the Category:Icons for railway descriptions/Berlin U-Bahn is now history. Well done! — ⟨µzdzisław⟩ 07:00, 6 April 2013 (UTC)
And there’s also sapphireToo bad we seem to have a handful of names for “Blue Iand none so far for #“Blue III”… -- Tuválkin 00:55, 5 April 2013 (UTC)

“Blue II”

OneTwoThreeTwo more: a singleton   (KBHFr 00A0DD) and set 0078BE, in which most icons are named 0077BE and some 0078BE but all have 0078BE in SVG code, partly uploaded to Commons and partly to ru.wp (pls do not move or reload them until those at ru.wp are deleted). YLSS (talk) 16:28, 11 March 2013 (UTC)

I will keep off till you say go, promised! -- Tuválkin 20:36, 11 March 2013 (UTC)
  • These are so close that joining three Mita icons into nine 0078BEs is a nobrainer. They stand out well between I and II, too, and are more or less in line, and halfway, with u-blue and azure.
  • Both these RGBs are closest to something called “true blue” — maybe call it simply "blue", then, as YLSS suggested above.

-- Tuválkin 02:39, 27 March 2013 (UTC)

✓ Recolored, renamed, and moved to "set 0078BE" while set blue is still used for something else. KBHFa was common to both sets, so the least used was deleted, its much better code used in the other. -- Tuválkin 09:37, 2 April 2013 (UTC)
I don't think the name "blue" can be used for any of the new colours, as the set blue contains all the original u-icons. Related is the mismatch between the shades of blue in the table at {{BS-color}} and the category to which the link under the word "blue" points. So, it's either the colour "blue" is dropped altogether (or just serves as a redirect to u-icons), or the set blue category gets renamed to set u, akin to Category:Icons for railway descriptions/set f, but the latter miiight require some wider consensus. I personally would be in favour of the former. — ⟨µzdzisław⟩ 08:13, 4 April 2013 (UTC)
Well, that was our with Tuválkin intention (the latter, that is). We now have fully fleshed-out set red & set green, distinct from "klassisch Rot" & "klassisch Grün", so it would be only appropriate to have a set blue as well. YLSS (talk) 08:56, 4 April 2013 (UTC)

“Blue III”

  • This one is slightly tealish and very pastel, still quite different from teal. Being a single set, nothing to change in the main color, but the ex-shade needs to be fixed?
  • closest English color name is bondi blue — we need to come up with something better.

-- Tuválkin 02:39, 27 March 2013 (UTC)

Let me suggest the color name "glaucous". While the exact rgb value given, 6082B6, is distant from 1A8BB9 (70.640), the hue angle is close enough (197° ≅ 216°) to this to be acceptable, as this color name is notoriously generic. -- Tuválkin 02:07, 5 April 2013 (UTC)
Quite an obscure word (for me, as a non-native speaker). YLSS (talk) 05:41, 5 April 2013 (UTC)
I think we’re mostly non-native speakers here. "Glaucous" is also hard on the spelling, but quite accurate on the naming, that’s why I propose it. -- Tuválkin 16:32, 5 April 2013 (UTC)
If we stick to having one set called blue, we only need to come up with one otehr word to have the problem fixed. I think "sapphire" is a lot more flexible then we give credit to it. I'm also not sure ultramarine or "steel" are entirely out of the picture either. If we use "sky", what about "water"? Circeus (talk) 16:09, 5 April 2013 (UTC)
"Water" reminds of "aqua", and that's a very light cyan. But of course water can take many colors. My only problem is how it could be mixed up with   (WASSER). :-\ -- Tuválkin 16:51, 5 April 2013 (UTC)
(I have some intentions on using "steel" for another colour, even though they may not come to life... YLSS (talk) 18:35, 5 April 2013 (UTC))

Would this set benefit if we tinge it a little bit towards green, without bringing it close to "teal"? YLSS (talk) 18:35, 5 April 2013 (UTC)

Maybe, why not? It is now unused and independent from mergings, so, if the result is make it more distinct from anyone else, I’d say go ahead. -- Tuválkin 20:25, 5 April 2013 (UTC)
Satisfied myself with recolouring ex with 73B7D3, its proper opacity=0.6 and greener. YLSS (talk) 21:11, 7 April 2013 (UTC)

I note that this was meanwhile renamed to "cerulean" — well, not the best of choices, considering that this seem to be an etymological equivalent of "sky" and ite spelling is anything but simple. However, and since the colorimentric defintion seems to be that anything goes, well… Why not, really? -- Tuválkin 02:35, 7 April 2013 (UTC)

Yes, having boiled in my brains for a months, "cerulean" wore down and now I think of it as an appropriate name. At least it is an established colour-word that I've encountered several times, and being the most blue of cyans and one of the most green of blues, it suits perfectly. YLSS (talk) 19:09, 7 April 2013 (UTC)

“Blue IV”

  • Berlin 10:1 Tokyo here no doubts here. THe RGBs are very close, again, and distinct from the neighbours.
  • The name "robin egg" (or "robin"?) begs for a better idea.

-- Tuválkin 02:39, 27 March 2013 (UTC)

I wanted to propose deleting BlnU7 as near duplicates of "azure", but if you want to keep them... YLSS (talk) 18:55, 1 April 2013 (UTC)
It was your idea («we need three or four shades of darker blue»), even if immediately supported by me. :-) This is a shade of blue that is close enough to azure only in brightness and saturation, but not in hue. -- Tuválkin 02:43, 2 April 2013 (UTC)
I meant three or four including "u-blue" (the list is numbered), but do as you like, sharp eye! ;). YLSS (talk) 13:03, 2 April 2013 (UTC)
I’m sorry, I was mistaken: It was Useddenim’s idea, rather, (at 12:42, 24 March) to join alsmot identical parts to form what’s now I, II, and IV, leaving III unchanged. Oh, well, song sung blue — everybody has one :-) -- Tuválkin 15:18, 2 April 2013 (UTC)

Could "sky" be a reasonably simple name? Circeus (talk) 06:37, 27 March 2013 (UTC)

"Sky" is a good name for a variety of shades of blue hues (regardless of its specific meaning), so it is a very good suggestion, perfect for any shade which cannot be covered by a more specific name. -- Tuválkin 23:24, 27 March 2013 (UTC)
"Sky" IMO can only be applied to this one, if any - others are too dark. YLSS (talk) 18:55, 1 April 2013 (UTC)

Formerly existing icons of set 029EE0 (16 of them) and the lone 00A0DD must be undeleted to be added to this set. Even though their usage was replaced, even though they are probably duplicates of the Berlin ones: They need to be assessed and then (some) deleted as dupes or equivalents. -- Tuválkin 16:58, 1 April 2013 (UTC)

Don't you think that you overdo sometimes?.. 1) If you really need it, you can undelete   (CPICla 029EE0),   (CPICr 029EE0),   (CPICre 029EE0),   (ABZrg 029EE0),   (KDSTr 029EE0),   (exBHF 029EE0),   (KBHFxa 029EE0),   (KBHFe 029EE0),   (exKBHFa 029EE0),   (KBHFa 029EE0),   (TUNNELa 029EE0) &   (WBRÜCKE 029EE0), BHF, STR & STRrf are already in BlnU7. 2) 00A0DD is   (KBHFr azure) now. YLSS (talk) 18:55, 1 April 2013 (UTC)
We’re dedicating ourselves to organizing a minor subset of repository of diagram elements which are one of a myriad of elements that make up a free online encyclopedia. Overdoing? Yes (we all are), and proudly so! ;-) Reviving those icons is better than just uploading new ones because of file history. Too bad about 00A0DD, but no sleep lost over it now. Thanks for putting out the 029EE0 filenames! -- Tuválkin 02:43, 2 April 2013 (UTC)
All ✓ Done. -- Tuválkin 08:17, 2 April 2013 (UTC)

Light blues

BSicon ENDEa azure.svg BSicon lMENDEa.svg
ENDEa 3399FF ROOT 029EE0

(see #Close colours above for reasons)

Nobody opposes using "azure" as the target name for this one? YLSS (talk) 22:45, 14 March 2013 (UTC)

Great name. It is close enough to “True Blue” (not a great name), shown at en:Azure (color)#True Blue. -- Tuválkin 04:09, 15 March 2013 (UTC)
✓ Renamed. YLSS (talk) 14:26, 18 March 2013 (UTC)


I've moved from ru.wp five icons of pure cyan shade (#00FFFF), and together with those from #RizhMZD they make up quite a full set. This colour is actually quite different from all light blues that we have, and what's more important, it is a major web colour. So, on second thoughts, I guess we should give this set a chance. However, all former RizhMZD icons should be re-painted from current 67f8ff (or vice versa?), and I don't know what to do with multicolored icons. YLSS (talk) 18:46, 11 March 2013 (UTC)

I should say that saturated spectral colors such as                are an eye sore and most major wikipedias have recomendations against them in their style manuals (e.g.: en:WP:COLOR and en:Wikipedia:Manual of Style/Text formatting#Color -- Tuválkin 17:00, 21 March 2013 (UTC)). While I agree that cyan is an important color and that these icons should be integrated, not discarded, I’d suggest something less eye-searing (and more likely to be useful), such as Tiffany Blue or turquoise… -- Tuválkin 03:35, 14 March 2013 (UTC)
Most likely you are right. I just assigned a good name to it. YLSS (talk) 22:45, 14 March 2013 (UTC)

I renamed & moved the remaining RizhMZDs to set cyan. Tuválkin, could you please choose some colour (and ex) and repaint them? I guess you have a better eye for this ;) I can only note that Tiffany Blue is nearly identical to ex_teal. I didn't repaint anything, but renamed with an assumption that black segments should become ex_cyan (BTW, the original uploader actually applied opacity=0.62 to them at first), while those with blue segments can fill up for "eBHF" etc. since plain BHFs already exist from the other set. YLSS (talk) 22:30, 28 March 2013 (UTC)

Okay, I can take care of these babies (still need to finish the ochres, though). You’re right about the proximity of our ex-cyan with Tiffany blue, so lets go with turquoise = 40E0D0, then? Its ex-value is 8AEAE1, b.t.w. -- Tuválkin 04:24, 29 March 2013 (UTC)
✓ Done-- Tuválkin 08:21, 29 March 2013 (UTC)
Thanks! (8AEAE1 seems to offer little contrast with 40E0D0, but... oh, to the hell with that set!) YLSS (talk) 08:38, 29 March 2013 (UTC)


Also noticed that yellow  ffd702  and Berlin U4  fffd403  are indistinguishable from each other. Another candidate for combining. Useddenim (talk) 10:54, 21 August 2012 (UTC)

If I understand the matters right, BSicons that use the colour FFD702 were for some time uploaded both as "BSicon XXX yellow" and "BSicon XXX FFD702", with the former pattern gradually replacing the latter (I finalized a couple of instances). So that's settled. The "ex" subset was also uploaded both as "BSicon exXXX yellow" and "BSicon exXXX FFD702"; however, the colours used were different: FFEB81 and FFF3A9 respectively. "Ex yellow"/FFEB81 likewise supplanted "ex FFD702"/FFF3A9; I finalized several instances, and created Category:Icons for railway descriptions/set FFF3A9. All icons in it are currently unused and have near-duplicates in parent categories, so I guess they should be deleted. Any objections? YLSS (talk) 17:30, 5 February 2013 (UTC)

Don't forget Category:Icons for railway descriptions/set yellow and Category:Icons for railway descriptions/Berlin U-Bahn, which (on my monitors, at least) are virtually indistinguishable:

BSicon STR yellow.svg BSicon lMENDEa.svg

See also Category:Icons for railway descriptions/other colors. Useddenim (talk) 01:30, 15 February 2013 (UTC)

I'm not really aware of the purpose of Berlin U-Bahn set, so, for my part, I'll leave it alone. YLSS (talk) 18:13, 15 February 2013 (UTC)
The Moscow, Tokyo, and Berlin sets are joined in separate special categories, but there’s no reason to treat them separately — they could be (and some already are) used in other projects, and would gain from stranadrtized treatment. -- Tuválkin 03:23, 16 February 2013 (UTC)
Ah, I see the prehistory now. Well, there's no separate category for Moscow Metro now, and I don't have enough authority to mess with Tokyo and Berlin systems. YLSS (talk) 14:43, 17 February 2013 (UTC)
I just reüploaded the eight Berlin U4 icons changed to FFD702 yellow. However, except for   (uENDEl BlnU4), all of them already have same shape equivalents in the yellow set, meaning they will be deleted as dupes (or converted to redirects, if we’re having those). Before that happens, is should be verified for each icon wheather the privliged duplicate has better codr, and if not it should be replaced with the to-be-discarded one’s. That seems to be the case of   (uKBHFe BlnU4) versus   (KBHFe yellow) -- Tuválkin 02:34, 9 March 2013 (UTC)
✓ Done. -- Tuválkin 21:27, 22 March 2013 (UTC)


Added yellow+red. Apparently remains of the olden days, created in 2010 by a user now indefinitely blocked, used in a single template. Together with C0C0C0 above can be replaced by regular sets. YLSS (talk) 18:46, 17 February 2013 (UTC)

I think this was an attempt at emphasising the edges of paler colors, and a pretty much borked attempt, at that. Also, I could not find any use for these files, and AndreyA seems to be not banned. Either way, I agree that these icons must go. -- Tuválkin 05:29, 18 February 2013 (UTC)
That's because I already replaced all of them. Only ru:Шаблон:Маршрут 1A (Брюссель) employed them, but I don't know what for: Line 1 of Brussels Metro is purple, but the template represented part of Line 6 (blue) and part of Line 5 (dark yellow) as "Line 1A". So I switched it to the generic blues. AndreyA is banned from ru:wp. YLSS (talk) 05:58, 18 February 2013 (UTC)
Some of the yellow+red set, the tunnel ones, can be fixed to be used in the yellow set. The rest can be safely tagged for deletion. -- Tuválkin 20:53, 12 March 2013 (UTC)
Almost done. The names, with "yellow+red", will be changed to simple "yellow". -- Tuválkin 02:54, 13 March 2013 (UTC)
✓ Done. -- Tuválkin 21:27, 22 March 2013 (UTC)


Some ex-yellow ideas:

  • The current ex-yellow value is FFEB81, and does offer better contrast than the 60%-opacity value FDE565; by keeping it, we also avoid reuploading 27 icons.
  • Thanks to YLSS’s report below, we are reminded that Category:Icons for railway descriptions/set FFF3A9 can be fully replaced as the ex-version of regular yellow icons. I’ll be marking them for speedy deletion.
  • Likewise,   (HBHF jaune) can be slightly recolored to RGB:FFEB81 and renamed   (exBHFq_yellow).

-- Tuválkin 16:30, 6 March 2013 (UTC)

All ✓ Done. -- Tuválkin 17:24, 6 March 2013 (UTC)


BSicon lMENDEa.svg BSicon lMENDEa.svg BSicon lMENDEa.svg
1 icon
MosMetro 1
7 icons
set EF161E
27 icons

This seems to be a straightfoward case, as there are only two bright red icon “sets” (one of them with the grand total of 1 icon). Bright red is probably never be a popular set, as there’s the huge set of regular icons (in dark red) to draw from when ilustrating any system’s Red Line (see example). (It is also the same generic color as the   (POINTERr) icon family and the Spanish and Danish SBHF logos.) Two matters need to be adressed:

  • The "ex" color in set EF161E, affecting only one icon   (KBHFxe EF161E), which is the same as the standard icons’ ex color, and should not be. I went ahead and fixed it, as it had only one use, and created a new   (exKBHFe EF161E) to match (before it used a regular   (exKBHFe) shade of red). I don't like to do stuff without consensus, but this was unmessy and simple, unlike others.
  • Which RGB value to chose for the definitive version, wheather EF161E or E60012. Maybe the Tokyo color looks prettier and maybe it does match some official spec, unlike EF161E?

-- Tuválkin 21:06, 21 February 2013 (UTC)

I got this reply from the uploader of the Tokyo icon set: In short, there’s no need to strictly adhere to these exact RGBs. It is therefore simpler to change one icon to match 15 other icons than the opposite. Since the "ex" matter is fixed and the color name is uncontroversial ("red"), this set could be the 1st to be fully fixed, as soon as there is agreement about brackets vs. space in the filenames. -- Tuválkin 12:42, 22 February 2013 (UTC)
The newly added 7 icons including FF0000 red from the poorly designed (and poorly named, and poorly coded, and thankfully barely used) #RizhMZD set do not rock this boat. Mimimal changes concerining the shade of red upon recoloring them to EF161E, especially since they are used only in abandoned user pages. -- Tuválkin 16:13, 4 March 2013 (UTC)

Light greens

BSicon KBHFxe lime.svg BSicon lMENDEa.svg

(see #Close colours above for reasons)

Wow, I've just uncovered a devious, cunning and deeply-rooted plot to Slavicize Wikimedia, I even have regrets undoing it. Half of icons in 99CC00 set are actually named not "99CC00", but "99СС00". If you don't get the difference, the latter has Cyrillic letter С (es, corresponding to Latin S) instead of Latin C. What a beautiful fishing practice... YLSS (talk) 21:33, 23 February 2013 (UTC)

Тһаԏ’ѕ аԝѕоте! (By the way: This section should be split into Greys, Light Blues, and Light Greens. Can you do it?) -- Tuválkin 21:44, 23 February 2013 (UTC)

Nobody opposes using "lime" for this one? "Apple green" or "yellow-green" seem closer, but "lime" is shorter, commoner and is broader in meaning. YLSS (talk) 22:45, 14 March 2013 (UTC)

Lime green is closest to 2DBE2C, but lime is BFFF00, so I guess it is a good idea. -- Tuválkin 04:09, 15 March 2013 (UTC)
✓ Renamed. YLSS (talk) 14:26, 18 March 2013 (UTC)

Shinjuku & BlnU1

60px BSicon fexlDST.svg BSicon BHF jade.svg
7FD77E 6CBB5A 53B147

I’m thinking — maybe ex-vert (7FD77E) is close enough to Shinjuku (6CBB5A)? -- Tuválkin 21:25, 20 March 2013 (UTC)

Meh, bad idea, per se. Whatever happens to Shinjuku’s RGB, it will be deal with in parallel with Berlin U1 (53B147). Should that be relabelled and recolored as ex-vert (7FD77E)? Maybe, we need to think. -- Tuválkin 18:22, 22 March 2013 (UTC)

(This pair seems to be the last one undecided...) Since we now have so many blues and so many purples, and since on the other hand the human eye is most sensitive to greens, I suppose 53B147 can be kept. The name: grass, fern, forest?.. Not mantis, save me... YLSS (talk) 14:01, 2 April 2013 (UTC) Or while no verts have been renamed yet... Maybe 53B147=green and 2DBE2C=leaf? YLSS (talk) 15:07, 2 April 2013 (UTC)

I’m not so hot about "leaf". I think that we either go for more or less accepted color names (even unusual ones, like saffron) or, if we go for whimsical names, we should stick to their (necessarily narrow) use, by calculating the nearest neighbor to those listed in en:Category:Shades of color templates. And "leaf", surprisingly, is not even a recognized color name, even among the many weird names listed at en:Variations_of_green.
There is a green shade name, though, that’s suitable for a more or less wide range of light greens, and whose exact definition in the lists above is not too far from 2DBE2C — is Emerald. I suggest that instead of leaf, leaving 53B147=green. -- Tuválkin 17:06, 2 April 2013 (UTC)
Yes, I considered that one, but somehow I visualise "emerald" to be ideally appropriate for ug/g set. And those mineral-named colours tend to be not very bright, so IMO they would rather suit 53B147... What about "jade"? YLSS (talk) 19:37, 2 April 2013 (UTC)
I was thinking of exactly the same on my way back here after dinner, what a coincidence! Furthermore emerald is said to be slightly blueish, while jade is milkish. It is perfect for the combination of Shinjuku and U1. -- Tuválkin 01:43, 3 April 2013 (UTC)

On the other hand, I was thinking too that, while 1<<15, the shade of green of U1 is much closer to “vert” than Shinjuku is. Wouldn’t we be better served with a more distinct color value, even with the added toil of recoloring a 14 icons more? -- Tuválkin 01:43, 3 April 2013 (UTC)

I also though about that ;) However, wouldn't 6CBB5A be too close to fex=64B164? Well, BlnUs are your sphere of influence, so it's up to you ;) YLSS (talk) 06:50, 3 April 2013 (UTC)
No influence spheres here, I think, as the whole idea was to join all these disparate incon set and harmonize it. As for Shinjuku (6CBB5A)fex (64B164), well, I never noticed it, but you’re obviously right and their distance (16,248) is smaller than between U1 (53B147) and vert (2DBE2C) (48,394). So, seems that the singleton   (TokyoShinjuku) can be renamed   (fexlDST) and the rest (U1) left unchanged. -- Tuválkin 12:17, 3 April 2013 (UTC)

Vert & B4EEB4

BSicon lMENDEa.svg BSicon exBHFq green.svg BSicon BHF green.svg
B4EEB4 ex_vert vert

This extremely faint set could be tinted up to match some other colour's ex. (AFAIK, it was created only to represent a proposed line of Novosibirsk Metro that has since been reassigned some magenta colour and is represented by plain Bahn ex's at ru.wp.) Since it has balanced red and blue components, I guess ex_vert would be most appropriate? BTW, after current greens finally become the "f"-set, maybe verts should be renamed "green" as the most brilliantly green shade? "Lime", IMO, better suits 99CC00 above. YLSS (talk) 15:05, 14 March 2013 (UTC)

Just like about "u"-blue above, I agee. The categories could be renamed "set f" and "set g", and relese the name "green" for this bighter color. -- Tuválkin 04:09, 15 March 2013 (UTC)
  • recoloring ✓ Done
  • renaming of icons ✓ Done -- Tuválkin 21:09, 10 April 2013 (UTC)
  • renaming of category ✓ Done -- Tuválkin 21:09, 10 April 2013 (UTC)
-- Tuválkin 03:15, 18 March 2013 (UTC)
Bummer, I overlooked the table above and recolored using the 60% opacity. Then I had to recolor the three already existing almost-match ex-verts. Oh well. -- Tuválkin 05:04, 18 March 2013 (UTC)

(How ironic... Once I had "exLSTRq green" renamed to   (exLUECKEq vert) - 'cause the colour was ex_vert, not ex_green, and there were no LSTR's de facto at that moment. The redirect remained and now, thanks to Tuválkin, it showed up in its soon-to-be-proper place. And the file will have to be moved back soon. YLSS (talk) 20:20, 22 March 2013 (UTC))

But   (fLSTRq) is correctly colored, what’s the trouble?… And both files’ global use seems to be okay… -- Tuválkin 05:41, 23 March 2013 (UTC)
No, no trouble at all, just irony (with exLSTR). YLSS (talk) 10:33, 23 March 2013 (UTC)

Set 34C924

Are these (    ) supposed to be full width (nominal 500×500px) or half width? -- Tuválkin 23:29, 3 August 2012 (UTC)

Also set D1E231 (    ). Do we fix them, or wait for User 699 (talk · contribs) to fall flat on his face when he tries to creat an RDT? Useddenim (talk) 00:22, 4 August 2012 (UTC)
Well, it works as long as no curves or forks are needed. These should be fixed, anyway, or maybe conflated with any of the existing “other colors”. -- Tuválkin 04:10, 5 August 2012 (UTC)

Fixing ✓ Done. -- Tuválkin 15:31, 19 August 2012 (UTC)

FYI: After conversation with the original uploader, deleted all 34c924's and D1E231's. YLSS (talk) 18:49, 17 February 2013 (UTC)
Well, that’s not good at all. The original uploader doesn’t own the files. I had worked on those icons, they could be useful, maybe merged into similar colors. For one thing, they had good SVG, what's not what can be said of most these color icons we’re planning on renaming now. -- Tuválkin 07:26, 18 February 2013 (UTC)
I asked User:Túrelio to revive these, as they can be salvaged:
  •   (exABZlg d1e231) and   (exSTR D1E231): These are CBCF4E, and are marked as the ex version of D1E231, which doesn’t add up (ex should be lighter and whitier). They are very close to the ex versions of set 99CC00, and, while   (exSTR 99CC00) already exists,   (exABZlg d1e231) can be slightly recolored and added to this set. ✓ Done
  •   (KBHFa D1E231) is accurately named, however. It is similar enough to   (TokyoYurakucho) but also to the B3D52E set:   (KBHFa B3D52E). ✓ Done but see below.
  •   (exSTR 66CC00), as mentioned above, the name is wrong, as it is really colored 66CC00, so no reason for "ex". It is closest to   (STR vert) and can be safely killed off as its duplicate. ✓ Done
  •   (KBHFa 34c924) is very close to the vert set, too, where a   (KBHFa vert) exists, but with wrong geometry — this can replace it; upon renaming, this will be seamless. ✓ Done
-- Tuválkin 09:50, 8 March 2013 (UTC)


Turns out that   (KBHFa D1E231) (see above) was accurately named (i.e., icon color matching the RGB in the filename) only because I made it so when I replaced the original messed up SVG, assuming that the filename was accurate. As it was, the original color was CBCF4E, which is even closer to   (TokyoYurakucho) than before (vectorial RGB discance: 17.720; both have en:old gold as closest named color shade), and therefore can be dully merged. This color set has now two six(-- Tuválkin 12:22, 2 April 2013 (UTC)) icons — maybe it will never need more, but at least it is integrated in a logical system. ✓ Done -- Tuválkin 14:13, 11 March 2013 (UTC)

I named this "golden" — not "gold" because that color name is closest to our yellow, and instead of its closest "old gold" to avoid a two-word colorname. -- Tuválkin 01:02, 16 March 2013 (UTC)


BSicon KBHFa teal.svg BSicon lMENDEa.svg BSicon lMENDEa.svg BSicon lMENDEa.svg
KBHFa 339999
31 icons
4 icons
uBHF BlnU3
10 icons
1 icon

Also these two four. -- Tuválkin 07:00, 18 February 2013 (UTC)

Or is there a need for two shades of medium teal? -- Tuválkin 11:04, 18 February 2013 (UTC)
Medium teal, yes, because light teal is acqua(marine) / tuquoise, and dark teal is petrel blue… ;-) -- Tuválkin 13:58, 18 February 2013 (UTC)
(I mean petrol, not petrel, but apparently neither is used in English: The former exists in French and the latter exists only in its recyprocal form. But we digress.) -- Tuválkin 17:56, 23 February 2013 (UTC)

Anyway, lets merge these four? I suggest the name "teal" — wich is short, single worded, well known, and adequate (even though these match more closely to the more narrowly defined jungle green and persian green), and I also suggest that we keep 339999 — because it means less icons will be affected and is easier to memorize when creating icons manually. Opinions? -- Tuválkin 18:33, 23 February 2013 (UTC)

Totally agree, but let's wait for others' opinions. YLSS (talk) 20:40, 23 February 2013 (UTC)

As already said above, ten ex339999 are actually 3399FF and IMO should be just renamed as such, after analizing their considering their usage, as well (and even more carefully) four e/x icopns which include both 339999 and 3399FF. These latter could be, depending on their use, either transformed into special two-color icons (like  ) or recolored to match its proper ex color shade: 82C0C0. -- Tuválkin 18:33, 23 February 2013 (UTC)

Well, they are actually named 3399FF, I made sure of it some time ago. Those are redirects from old pre-move titles that you see in 339999 category, plus three duplicate files that were tagged as such by me two weeks ago (when will they get deleted?), plus four XXXxa/xXXXa's, which can be either recolored or deleted altogether as unused. YLSS (talk) 20:38, 23 February 2013 (UTC)
Unused redirects should be deleted, in principle. If those four are unused, better recolor them to 82C0C0, IMO. -- Tuválkin 21:16, 23 February 2013 (UTC)


And another candidate for merging:

BSicon BHF brown.svg BSicon lMENDEa.svg BSicon lMENDEa.svg BSicon lMENDEa.svg
BHF brown
6 icons
BHF 71592E
17 icons
uBHF BlnU5
4 icons

see below

They aren't as close as the others, but they're not that far apart, either. Useddenim (talk) 21:43, 15 February 2013 (UTC)

I think RGB:71592E is a better choice for unification, too, as RGB:71592E seems to dark and hard to tell apart from black. -- Tuválkin 15:18, 17 February 2013 (UTC)
Yeah, I agree they should be merged. But which one to which one? 71592E is used in many Wikipedias, but only for Moscow metro line (ru:Шаблон:Кольцевая линия (Москва)); "brown" is only used in ru:wp for a planned line of Saint Petersburg metro (ru:Шаблон:Красносельско-Калининская линия). The colour used for the Moscow line in the official scheme is somewhere between 71592E and brown/8D5B2D. (I guess I'd better drop a note at ru:wp as well.) YLSS (talk) 14:55, 17 February 2013 (UTC)
The 1st step of this kind of merging is to recolor the different sets so they all have the same exact shade (even if the RGB in the filenames will be unaccurate). That, unlike, moving/renaming, doesn’t affect the articles/diagrams using the icons (only visually, and not much). Is is something simple, and 100% centralized here in Commons. And it is not a hard job, as in the worst case we’d be looking at reuploading 23 icons: No big deal. -- Tuválkin 16:50, 4 March 2013 (UTC)
Please note that, as mentioned somewhere else, we do have not two but fourthree brown icon sets: U5, Fukutoshin, 71592E, and brown. I added the two missing ones above. -- Tuválkin 15:35, 17 February 2013 (UTC)


BSicon KDSTr ochre.svg BSicon lMENDEa.svg
Ochre Tawny

I think two different browns are necessary. I thought a lighter shade, as the Tokyo roundel, could use the "ex" version of a darker one, but the ex-brown shades are all too greyish. Or maybe CC6600 could fill the role or a lighter brown? Here’s → how they compare. Lets merge these two? -- Tuválkin 11:16, 23 February 2013 (UTC)

I suggest "ochre" for the name, even though 44 icons are closer to tawny and only 1 is closer to ochre. Opinions? -- Tuválkin 11:16, 23 February 2013 (UTC)

Okay, since nobody disagrees, I’ll recolor   (TokyoFukutoshin) to CC6600. -- Tuválkin 02:46, 2 March 2013 (UTC)
✓ Done — and see below for the proposed renaming. -- Tuválkin 15:02, 5 March 2013 (UTC)


Even with CC6600 out of the way, classified as ochre, we still have sixseven different shades of orange to be sorted out. They must to be integrated as at least two final shades, and not into a single shade of orange, because two of these six are part of the Berlin set (U9 and U2) and they obviously need to be kept distinct, even if they get tweaked in their exact RGB. -- Tuválkin 00:55, 10 March 2013 (UTC)

BSicon KBHFa saffron.svg BSicon lMENDEa.svg BSicon lMENDEa.svg BSicon lMENDEa.svg BSicon lMENDEa.svg BSicon ENDEa orange.svg BSicon lMENDEa.svg
19 icons

3 icons
31 icons
1 icon
uBHF BlnU9
9 icons
BHF orange
123 icons
uBHF BlnU2
14 icons
  • I’m sure nobody disagrees with unifying FFA500 with FFAB2E, right?
  • Unifying F25821 into FF6600 is less straightforward but still the way to go.
  • As for EB851C and F39700, while much less similar, the only sensible thing is to assimilate them as part of the FFAB2E set, too.

Any alternative suggestions? -- Tuválkin 02:06, 10 March 2013 (UTC)

Seems that YLSS likes the color name "saffron". Alright, let’s go! -- Tuválkin 19:40, 14 March 2013 (UTC)
'Twas your suggestion! Indeed I spent some time inquiring whether it suits or not. And it's better than "carrot" ;) YLSS (talk) 20:16, 14 March 2013 (UTC)
And definitely better than "stick"! 8•P Useddenim (talk) 02:32, 15 March 2013 (UTC)
Concerning the need for keeping Berlin’s U2 and U9 clearly distinct, changing U2’s F25821 to FF6600 could be a mistake, as it makes it lighter, but U9’s EB851C would also be made lighter (FFAB2E), so I guess it is okay? -- Tuválkin 15:54, 10 March 2013 (UTC)
From a brief glance at de:U-Bahnlinie_2_(Berlin), I got the impression that it is regarded as a "red" line, so I guess merging F25821 into orange wouldn't be good. Better ask Uzdzislaw's advice (or Axpde's). YLSS (talk) 16:40, 10 March 2013 (UTC)
I see your point — likely these F25821 icons need to be replaced with red ones, then. But that’s a matter of Wikipedia, not for Commons. What we have here is a set of orange icons, which could have been used somewhere else as such (maybe they were, in some other project off the Wikimedia name space). We need to treat them as orange. (To make it easier, I’ll make red versions of all needed icons, so that wp:en can change from F25821 effortlessly.) -- Tuválkin 10:42, 16 March 2013 (UTC)
Well,   (uBHF BlnU2) is used for en:Template:Brussels metro line 5 RDT Brussels M5 in wp:en, and that’s clearly orange… If Berlin U2 is better served with red icons, I made sure all BlnU2 icons exist also in the set red. It is out of Common’s hands, now, and we could go ahead and merge U2 to set orange. -- Tuválkin 03:20, 21 March 2013 (UTC)
Hi there, awesome work going on I see! I'd personally replace U2 by red, also because it's definitely redder on the operator site (I mean the red bullet boxes in the station list). — ⟨µzdzisław⟩ 23:44, 23 March 2013 (UTC)
✓ Done -- Tuválkin 22:19, 31 March 2013 (UTC)
I'll rather see U9 to be orange than saffron, although it's also a matter of opinion. — ⟨µzdzisław⟩ 23:44, 23 March 2013 (UTC)
✓ Done, too, but now maybe U2 and U9 are too close? Maybe U2 should be darker, bahn-red”, for contrast? (Anyway, this talk belong at en:wp, not here!) -- Tuválkin 22:40, 31 March 2013 (UTC)
I had this “good idea” that FFAB2E (and Moscow’s FFA500) could be integrated as ex-versions of orange (which are currently FF9955, very close, and whose 60% opacity is FDA164, ditto) — however set FFAB2E already has a set of ex-icons, and its use (use/disuse in French wp about Moscow Metro line 6) needs them. So, no unifying, here. -- Tuválkin 01:48, 10 March 2013 (UTC)

About F09E36

One more set now, F09E36. Presently at Category:Kaluzhsko-Rizhskaya Line. YLSS (talk) 20:36, 10 March 2013 (UTC)

Good grief. Туча knows well that this discussion is going on and yet decides to create new icons named in a way that goes against the growing consensus above, and keeps them “hidden” in a category off away the rest. Talk about good faith, really. (See also this.)
Anyway, this new shade of orange is close enough to FFAB2E to allow for a seamless integration, yes?
-- Tuválkin 21:04, 10 March 2013 (UTC)
That’s the way Туча is: see this and this. Useddenim (talk) 23:10, 10 March 2013 (UTC)
To his defence: he had no intention of hiding this and moved his uploads to root category. His reply at ru.wp (Please forgive any mistranslations, either someone's got to learn English, or others Russian.):

I guess that the colours at Template:MOSMETRO_color were taken from some official map a long time ago. <...> I noticed that the colours of template head and of icons themselves differ greatly, and tweaked one to suit the other. That's all. This colour is far more pleasant than the bright toxic orange. Concerning the fact that icons should differ, then delete close German colours, not Moscow ones. However, I said from the start that this is a bad option, and it would be better to leave everything as it is: each Wikipedia has with its own colours, and Germans do not teach Muscovites, Muscovites do not teach those from Saint Petersburg, and the latter do not teach Japanese on what colour to paint their templates with.

Well, he has a point. YLSS (talk) 23:51, 10 March 2013 (UTC)
He does? Maybe, but it is a terrible point to make. Doing nothing allows things like having two slightly differently colored sets of icons, one for Moscow subway line 6 in Russian Wikipedia and another for the same in Spanish and French Wikipedias. Doing nothing now allows for things like that to multiply as wikipedias grow, needlessly swelling the amount of semantically and graphically equivalent BSicons.
  • If he wants to have and use independent icon sets, then he should be uploading them to wp:ru, not to :commons. (Good luck with that…)
  • As for his criticism about the shade of orange, nobody is suggesting that Moscow subway line 6 should be rendered as bright orange (while he himself mentioned   (BHF orange) as an «other version» of   (BHF moscow6) — WTF?), but unified with the other shades of pale orange, one of which was created to illustrated that very same Moscow subway line 6, in use if the French and Spanish wikipedias.
  • As for what gets to be «deleted», usually we have been favouring, among two or more really close colors, the one that has more icons to it, although after reuploading RGB changed SVGs and renaming them, and collapsing unmatching sets, it is really a melting pot, not a game of Risk.
-- Tuválkin 01:16, 11 March 2013 (UTC)
  1. I do not understand, what you mean about the BHF orange, i just pointed out, which icon i was oriented, when i made the next, because it was not always orange in all cases, some orange icons hefty large size have in bytes. When the picture is quite difficult, i just wrote that it is a derivative work, and if it is very simple, i just gave a link to other version.
  2. FFAB2E, i think, may be deleted, because it is now little used, i changed it in french wikipedias, and, i known, it was never used for this circuit in the spanish.
  3. I think all the free images should be loaded on commons.
  4. What is it, game of Risk?--Туча (talk) 07:30, 11 March 2013 (UTC)
A game of world conquest; see en:Risk (game). Useddenim (talk) 14:54, 11 March 2013 (UTC)

I've posted at ru.wp a note on colours on current "official" maps, which number at least at five. Since FFAB2E looks very much close to the midway FBAA33 and F09E36 does not, I guess I'll begin merging "moscow6" into "FFAB2E", renaming them at the same time as "saffron". Any objections? YLSS (talk) 17:17, 14 March 2013 (UTC)

I’m all for it. (Back in 1999 I lived for a couple weeks close to Ясенево, so I get a voice on this.) -- Tuválkin 19:40, 14 March 2013 (UTC)
After discussion with Туча, I merged "moscow6" into "saffron". I haven't re-uploaded any files with a single colour; if Туча doesn't do this, after a couple of days I'll do. YLSS (talk) 13:29, 15 March 2013 (UTC)
Я изменил все картинки saffron, имевшие цвета F09E36 и F5BE79, на цвета FFAB2E и FFC969 соотвественно, как вы просили. Чёрт с вами. --Туча (talk) 18:23, 15 March 2013 (UTC)
I changed all the icons [to] saffron, the color had F09E36 and F5BE79, the colors FFAB2E and FFC969 appropriately, as you requested. Damn you all. (Translation courtesy google) Useddenim (talk) 03:33, 16 March 2013 (UTC) I changed all saffron icons, which in fact were F09E36 and F5BE79 color after renameing, to FFAB2E and FFC969 respectively, as you requested.--Туча (talk) 12:44, 16 March 2013 (UTC)

Lines with multiple colors

Renaming multiple color icons

The 45 icons currently at Category:Icons for railway descriptions/set CC6600 present an interesting case. I’ll lay out here my ideas about their renaming, as an example on how to deal with those pesky faux "ex" icons, and also with mixed icons which include other colors:

  • 29 icons using only CC6600; named FOO_CC6600.
    Trivial situation.
  • 2 icons using FF6600; named exFOO_CC6600:
    •   (exCONTr CC6600)
    •   (exCONTl CC6600)

    These can be renamed to integrate the orange set (RGB matches, as observed), and replaced with identical icons using the RGB value agreed upon to be this set’s "ex" color — DEA164. Naming is trivial. (✓ Done:   (CONTl orange) already existed — usage changed. -- Tuválkin 01:54, 11 March 2013 (UTC))

  • 2 icons using CC6600 and FF6600; named eFOO_CC6600:
    •   (eABZrg CC6600)
    •   (eABZlg CC6600)

    As above, these can be replaced with proper "e" coloring, using DEA164. ✓ Done -- Tuválkin 17:47, 12 March 2013 (UTC) However, these icons can be renamed to cover any need of their standing for not regular+ex but for ochre+orange (as seems to be the case of the current use, although Vienna U6 would be better illustrated with brown…) — I suggest using filenames with "m" added with both color names connected with a "+":   (mABZrg ochre+orange) inspired on   (mABZrg).

  • 3 icons using CC6600 and normal; named FOO_CC6600:
    •   (tKRZ+tunnel CC6600)
    •   (tKRZ CC6600)
    •   (KRZu CC6600)

    As above but with only "+ochre" (either after the space or inside the bracket pair); these icons, where the normal-red line shows across, should be renamed to reflect the fact that normal trumps ochre, but swapping "u" for "o", the placement of "t", and adding "q".

  • 3 icons using CC6600 and green;
    • named FOO_green_CC6600:
      •   (tKRZ green CC6600)
      •   (KRZol green CC6600)
      •   (xAKRZue green CC6600) (shouldn’t be "x")

      As above: considering that this is the special footpath green, instead of a double colorname with an "+", I suggest adding "fm" before the rootname (analogous to the many "um" icons) and "+ochre". Again, footpath-green trumps ochre, so these icons will need some general name fixing.

  • 4 icons using FF6600 and green;
    • 2 named e/x/FOO_green_CC6600:
      •   (evSTRrf green CC6600)
      •   (vxKBHFa green CC6600)

      As above, these can be duplicated — the uncanged code renamed to add to the orange set, and these ex-ochre recolored to DEA164. All to be renamed with "m" and "f" before the root, its placement w.r.t. "x" and "e" matching the many disused icons in the mixed set.

    • 2 named FOO_green_CC6600:
      •   (ABZlg green CC6600)
      •   (ABZrf green CC6600)

      These two exactly as above, but spawning fixed 3 icons each, not 2, because they were obviously misnamed, lacking a prefix "e".

  • One coopted icon (see #Ochre+Tawny?), to be renamed:
    •   (TokyoFukutoshin)lDST_ochre

    (or whatever other name, depending on the ongoing discussion about spaces vs. brackets, and the prefix for legende)

How does it sound as a plan? -- Tuválkin 03:13, 4 March 2013 (UTC)

Berlin U-bahn

I figure it would make sense to split   (uvSTR BlnU12) and the like into separate, single-coloured icons for overlay use. Should I do it? — ⟨µzdzisław⟩ 10:40, 9 March 2013 (UTC)

✓ Done:   (uvSTR- BlnU1)   (udSTR BlnU1)   (v-STR orange) uv-STR BlnU2   (dSTR orange) udSTR BlnU2(U2 meanwhile renamed. -- Tuválkin 15:43, 1 April 2013 (UTC)). Useddenim (talk) 21:53, 9 March 2013 (UTC)
✓ Also done:   (uvBS2+r BlnU1)   (uvSTR+r- BlnU1)   (vBS2l orange) uvBS2l BlnU2   (v-STRr orange) uv-STRr BlnU2(U2 meanwhile renamed. -- Tuválkin 15:43, 1 April 2013 (UTC)). So now all the BlnU12 icons   (uvSTR BlnU12)   (uvSTRg+r BlnU12)   (uvSTRg+r-STR BlnU12)   (uvSTRr-KRZ BlnU12) are used only in userspaces and can be therefore (?) deprecated or deleted. — ⟨µzdzisław⟩ 13:41, 10 March 2013 (UTC)
While I agree that overlays is the way to go for any imaginable use of differently colored icon sets, I’m firmly convinced that a naming system that allows for single-icon depiction of disparate color lines is a big plus — as indeed has been part of the BSicon system since the 1st "m" icon was created.
I’d like to keep these icons, at least for now, as guinea pigs for mixed set naming rules — replacing them in the wp:en Belin U-bahn diagram is nonethe less a good idea, as it already uses overlays other than these, and is bound to need more in the future.
-- Tuválkin 19:10, 10 March 2013 (UTC)


And there is Category:Icons for railway descriptions/RizhMZD, most of which should be deleted. Single-colour icons could possibly be salvaged, if we need yet another shade of light blue (do we?..). YLSS (talk) 14:17, 4 March 2013 (UTC)

I moved it back from the obsolete category to under "other colors", and will add them to the tables above. (Sorry about that, YLSS, and sorry for chopping your comment to pieces, too!) You’re very right about the single-color ones being useful, and, while we certainly don’t need yet another light blue, we could make use of the "MO MZD" color shade, adding it to the fuchsianew “ruby” set — a color share we’re strangely almost missing on our rainbow. -- Tuválkin 15:10, 4 March 2013 (UTC)

The colors in this set, from simplest to weirdest usage, follow. Let’s fix this thing. -- Tuválkin 18:35, 4 March 2013 (UTC)

Here’s the renamings/redirections I suggest:
redirect to existing icons new u icons
  (STR RizhMZD)   (uSTR)   (ABZlfg RizhMZD)   (uABZgxl+r), akin to   (ABZgxl+r)
  (STRq 67f8ff)   (uSTRq) new uf icons
  (STRlf RizhMZD)   (uSTRlf)   (ABZdg 67f8ff green)   (ufABZdg), akin to   (ueABZdg)
  (STRlg RizhMZD 1)   (uSTRlg)   (KRZo RizhMZD 1)   (ufKRZo)
  (STRrf RizhMZD)   (uSTRrf) new u icons + another color
  (STRrg RizhMZD)   (uSTRrg)   (KRZo RizhMZD)   (uemKRZo +saffron)
  (ABZlf RizhMZD 2)   (uABZlf)   (KRZu RizhMZD 1)   (umKRZu +ruby)
  (ABZlg RizhMZD)   (uABZlg)   (KRZu RizhMZD)   (umKRZu +red)
  (STRr+l RizhMZD)   (uSTRr+l)   (ABZlf RizhMZD 1)   (umABZlf +red), cp.   (umABZlf)
  (ABZlg RizhMZD 1)   (uxABZlg)   (ABZlf RizhMZD)   (umABZlf red+), cp.   (mABZlf)
  (ABZrg RizhMZD 1)   (ueABZrg)   (ABZdrf RizhMZD)   (umABZrxl ruby+)
  (eABZdg RizhMZD)   (ueABZdg) new red icons
  (ABZdrf RizhMZD 1)   (uABZdrf)   (STRq RizhMZD 1)   (STRq red)
  (eGRENZE RizhMZD)   (ueGRENZE)   (eABZ3lf RizhMZD)   (eABZq+l red)
  (WaterBridge RizhMZD)   (uWBRÜCKE) new orange icons
  (BHF RizhMZD)   (uBHF)   (STRq RizhMZD)   (STRq orange)
  (exBHF RizhMZD)   (ueBHF)? (and another one I cannot locate)
  (HST RizhMZD)   (uHST) new ruby icons
  (KBFa RizhMZD)   (uKBHFa)   (STR MO MZD)   (STR ruby)
  (KDSe RizhMZD)   (uKDSTe)   (STRq MO MZD)   (STRq ruby)
  (ABZrg RizhMZD)   (uABZrg)   (eABZ3lf MO MZD)   (ABZq+l ruby)
  (BHF MosMetro7)   (exBHF violet)   (eABZ3lg MO MZD)   (eABZqr ruby)
  (BHF MosMetro1)   (BHF EF161E)  (BHF red)   (ABZdlr MO MZD)   (ABZdlr ruby)
  (STR RizhMZD 1)   (STR EF161E)  (STR red)   (KRZo MO MZD)   (eKRZo ruby)
In total we gain one useful icon,   (uABZgxl+r), maybe three —   (STRq orange) and   (STRq red), and a bunch of still almost useless but at least consistenly named ones, as we eliminate a whole bunch of oddball namings and designs, with no loss for any project and gaining that no user in the future will be tempted to use them as they were. Anyone against these changes? Opinions? -- Tuválkin 18:57, 7 March 2013 (UTC)
Unnecessary, IMO. In the user template, these all should be replaced with plain red icons for railways, not the blue ones. Rubies could be salvaged. YLSS (talk) 19:13, 7 March 2013 (UTC)
Talking as wp:ru editor, I think you are absoluetely right (these two diagrams are not in use anyway, right?); talking as Commons editors, I saw we should salvage as much as possible. -- Tuválkin 07:01, 8 March 2013 (UTC)
RizhMZD green

green, 2 icons (all partial): Identical to #f-Green: As far as the green part goes, can be swiftly integrated. -- Tuválkin 18:35, 4 March 2013 (UTC)

RizhMZD red

red, 7 icons (4 partial): integrated with the rest. ✓ Done -- Tuválkin 18:35, 4 March 2013 (UTC)

RizhMZD orange

orange, 3 icons (1 partial): to be integrated with set FFAB2E, very close. -- Tuválkin 18:35, 4 March 2013 (UTC)

RizhMZD purple

ex-purple, 1 icon: #Purples is a wasps’ nest I am not in a hurry to poke, but at least one thing is clear:   (BHF_MosMetro7) (the only singleton among the 43 icons of #RizhMZD set) is identical to   (exBHF violet), and it is unused in the article space. Looks like a clean replace case, even if later on the latter will have to be recolored to something closer to 800080’s ex-eqv. B164B1. -- Tuválkin 16:33, 4 March 2013 (UTC)

✓ Done -- Tuválkin 16:40, 4 March 2013 (UTC)

purple, 8 icons (5 partial): As said this color shade, reddish purple (“ruby”), is almost absent in our palette. Can it be merged with any of the above? -- Tuválkin 18:35, 4 March 2013 (UTC)

New Category:Icons for railway descriptions/set ruby created. -- Tuválkin 20:18, 7 March 2013 (UTC)
See discussion. -- Tuválkin 02:49, 8 March 2013 (UTC)
RizhMZD black

black, 10 icons (all partial): Neither clear nor easy, but after considering the usage and naming, I suggest that we consider the black track segments of these icons to be disused track — which is rendered in the subdued "ex" shade in typical icons. To this hint not only the prefix "e" in some of these icons, but also the fact that black is usely exclusively along with other colors (as also green, and although the set contains two icons with typical paler "ex" color — blue and purple). I suggest therefore to recolor and rename all these as such. -- Tuválkin 18:35, 4 March 2013 (UTC)

RizhMZD blues

blue, 29 icons (9 partial): This is the trickiest. -- Tuválkin 18:35, 4 March 2013 (UTC)

Well, yes. I come to the following unexpected conclusion: While painted in very light blue, this line, to be faithful to the graphical spirit of our BSicons, is to be understood as a regular blue line. Please compare these two, as contrasted with their normal-red counterparts:

  •   (BHF RizhMZD)   :   (BHF)
  •   (exBHF RizhMZD) :   (exBHF) (or meant   (eBHF)?)

See that the color for the track line in use is deliberately different from that for a station in use, indeed being even lighter than that of a disused station. I defend that this style is too far removed from what are our usual practices and should be replaced by icons showing the same color for all features in use. Since the only use is a couple of abandoned user pages, the simplest way to procede, I think, is to assume that regular "u" blue was meant (instead of an yet-to-be-decided other shade of blue) and thusly redo/redirect these icons. That, along with the reinterpretation of RizhMZD black lines above as "ex" will result in the replacing of most of these RizhMZD bluse icons with existing ones. (Should a specific need arise for a light blue line with darker startion, both in use and disused, that can still be covered by BSicons, by use of differently colored overlays or even two-color icons.) -- Tuválkin 16:44, 7 March 2013 (UTC)

(As an aside: The reason behind creating this set was, I believe, the fact that several years ago all ten lines of Moscow commuter railways were assigned official colours, e.g. cyan for Rizhskoye. Fencing along the railways was painted correspondingly. Otherwise, these colours didn't show up anywhere, and few people are aware of these colours' existence (in contrast to Moscow Metro). So, ru.wp uses plain red icons for railways. YLSS (talk) 18:31, 7 March 2013 (UTC))
I see — why didn’t he made the station and halts roundels cyan also? Makes no sense. Oh well — we’re still better served with new two-color icons where one color is vastly used, than we’d been with both rare colors. Should anyone want to create cyan icons — well, we have them! -- Tuválkin 07:01, 8 March 2013 (UTC)

I've moved from ru.wp five icons of pure cyan shade (#00FFFF), and together with those from RizhMZD they make up quite a full set. YLSS (talk) 18:46, 11 March 2013 (UTC)

Sounds good. :-) -- Tuválkin 01:38, 14 March 2013 (UTC)