Talk:BSicon/Renaming/Archive 5

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.

CONT & ENDE

BSicon CONT

moved from User talk:Axpde/Archive 1

BSicon CONTr BSicon CONTgq.svg versus exCONTr BSicon exCONTr.svg? Same with CONTl and exCONTl. Please consider fixing. --85.23.70.102 10:11, 6 February 2010 (UTC)

I don't agree with the naming suggestion. From File:BSicon KBHFr.svg, the "r" specifically mentions that it is the right end (with the track facing left). To keep consistency with the KBHF series, CONTl and CONTr can keep; the others need to be changed. Newfraferz17 (talk) 10:58, 2 April 2010 (UTC)
The 'r' indicates that the track continues to the right (seen in "forward driving direction", i.e. from top to bottom of the icon)! axpdeHello! 22:48, 2 April 2010 (UTC)
Wait...I take my words back. I'm confused now; it seems that File:BSicon_STRl.svg BSicon STRfq.svg and File:BSicon_hSTRl.svg BSicon hSTRgq.svg are different too. Which is the correct set?
  • Set 1: KBHFl, CONTl, hSTRl (track comes from the right)
  • Set 2: exCONTl, STRl (track comes from the left)
— Preceding unsigned comment added by Newfraferz17 (talk • contribs) , 3. April 2010, 01:14 Uhr (UTC)
File:BSicon STRl.svg shows the correct direction (to the left), but I have general objections to theses icons because of the inflationary use of the suffix 'l'. IMHO "STRl" should show this BSicon STRlf.svg (which is "STRlf", just to get rid of the 'f'/'g' system in tracks and junctions). Maybe we should introduce another new root as we did with "CONT" ... hmmm.
  1. Symbol support vote.svg Support KBHFl, exCONTl, STRl – track goes to the left (as seen in driving direction)!
  2. Symbol oppose vote.svg Oppose CONTl and hSTRl – track goes to the right (again seen top to bottom)!
axpdeHello! 09:20, 3 April 2010 (UTC)
I back this proposition. Wiebevl (talk) 08:39, 5 April 2010 (UTC)

CONTr

moved from User talk:Axpde/Archive 2

Why did you exchanged CONTl and CONTr icons? Can you differ where's left or right? D.wine (talk) 21:05, 7 November 2010 (UTC)

It's about consistency. You look from an upside down perspective, so down is forward, up is back, etc. -mattbuck (Talk) 22:08, 7 November 2010 (UTC)
It's about stupid. Noone is really interesting WHERE FROM you turn left or right, but WHERE TO you turn: left or right. So it's just mess up. Anyway, this stupid illogical renaming screwed up thousands of route templates all over the wikis. And guess noone's gonna fix it. D.wine (talk) 20:02, 12 November 2010 (UTC)
It's always been the same: Looking in "driving direction", i.e. from top to bottom. It's neither stupid nor illogical, and least of all it's a "renaming", rather a "re-renaming". I don't know what you're going to do, but I've already changed dozens of route templates in a dozen different local projects! Blame whoever you like, but not me nor the original creators of the BSicons! axpdeHello! 08:17, 13 November 2010 (UTC)

Maybe we should enlarge the font of corresponding lines in the policies ... axpdeHello! 23:14, 10 November 2010 (UTC)

ENDEl vs. ENDEr

Since we have   (ENDEa) =>   (ENDExa), why do we have   (ENDEl) ≠>   (ENDExl) and   (ENDEr) ≠>   (ENDExr)? Should these two be swapped in places? If so, could someone with admin rights do this neatly? Thanks. YLSS (talk) 20:37, 22 March 2013 (UTC)

Oh, and also these, if I don't ask much:   (LENDEl) vs.   (LENDEr),   (exLENDEl) vs.   (exLENDEr),   (tENDEl) vs.   (tENDEr),   (extENDEl) vs.   (extENDEr),   (uextENDEl) vs.   (uextENDEr). Thanks again. YLSS (talk) 20:46, 22 March 2013 (UTC)

You're right,   (ENDEl) and   (ENDEr) show the wrong direction. It will be the same confusion as we had with   (CONTl) and   (CONTr), but it has to be done ... :( a×pdeHello! 22:54, 22 March 2013 (UTC)
Back in 2010 there already was a try to correct those icons, but this had been reverted the other day :( a×pdeHello! 23:03, 22 March 2013 (UTC)
Well, that is also an option, although a more time- and effort-consuming one. But I don't get it, should ENDE's be swapped as well or not? If not, then the whole thing is not worth it. YLSS (talk) 11:05, 23 March 2013 (UTC)
The   (CONTl) vs.   (CONTr) problem was handled the same way - and I still find railway diagramms with wrong files. But for the sake of a consistent naming scheme we need to go through it ... a×pdeHello! 12:39, 23 March 2013 (UTC)
But I still don't get it... If all   (KBHFl)'s go leftwards (i.e. come from the right) and you have reloaded   (ENDEl) to look the same, why should   (CONTl) go rightwards? YLSS (talk) 15:52, 23 March 2013 (UTC)
Well, it continues to the left! a×pdeHello! 00:35, 24 March 2013 (UTC)

Now that you've re-uploaded two ENDEs, a lot of templates across dozens of Wikipedias should be manually updated, and the same should be done with other ENDEs... Are you going to proceed with this? After all, you chose that option... If CONTs were switched as well, I could've let a hand, but otherwise I don't see the logic of bringing one thing to order but not the other. YLSS (talk) 11:27, 25 March 2013 (UTC)

connects to l/r
  (ENDEl)   (ENDEr)
ex-   (exENDEl)   (exENDEr)
-x   (ENDExl)   (ENDExr)
L-   (LENDEl)   (LENDEr)
exL-   (exLENDEl)   (exLENDEr)
t-   (tENDEl)   (tENDEr)
ext-   (extENDEl)   (extENDEr)
e.g.   (KBHFl)   (KBHFr)
CONTinues to l/r
  (CONTl)   (CONTr)
As you can see most ENDE icons are named consistently now. And as we did with the CONT icons we have to proceed with the ENDE icons, keeping in mind that we want to have them named consistently for that noone has to remember which icon is named wrong or not ... a×pdeHello! 18:42, 25 March 2013 (UTC)

Back to our rams, as we say in Russia. So what, maybe we should indeed swap CONTs as well? I can take a part in this. YLSS (talk) 09:57, 29 March 2013 (UTC)

Is that silent approval?   (CONTl)  (CONTr)? YLSS (talk) 19:06, 1 April 2013 (UTC)
I don't understand. The continuation icons have already been swapped and ok as they are now?! a×pdeHello! 21:45, 1 April 2013 (UTC)
It's based on the nature of the main feature (→). Useddenim (talk) 01:00, 2 April 2013 (UTC)
Yeah, and I don't understand that... But be that as it may. YLSS (talk) 12:47, 2 April 2013 (UTC)
It is also why probably all of us, when routinely creating diagrams, have to fix after previewing whenever CONTs are used, because, inspite of the clever rationale, they are simply backwards, compared with it is empirically expected, in subconscious analogy with BHF and ENDE.
(Also, the fact that this problem doesn’t emmerge for vertical continuation arrows, as there is both "g/f" and "a/e", is one more hint at the fact that "q" as a general quarter turn switch for the whole icon name is the best way to solve so many disparate icon naming problems.)
-- Tuválkin 01:46, 2 April 2013 (UTC)
Pardon, if I understand right you say all have a problem with seeing the BSicons in "direction-of-travel" therefore we have to quarter-turn the icon noone understands? Sorry, but that's unlogical! a×pdeHello! 13:35, 2 April 2013 (UTC)
Yes, people intuitively assume that arrowheads on a given end of an horizontal line   (CONTr) should be labelled the same way as discs   (KBHFr) and tacks   (ENDEr) — that’s what I said above and there’s no need to ask me to repeat it, as I might just do it. Also sorry that you don’t understand what a quarter turn is (just like you don’t understand Commons categorization), but cannot help you more. You are either incredibly stupid or deliberately sabotaging discussion with fake puzzlement, and I don’t want to engage with either of those. (Others please understand that I’m not complaining he doesn’t agree with me, but that he apparently cannot comprehend someone else’s explanation for a different opinion.) As for things that «noone understands», a good example was your mangling of the 45° ABZs, now again unusable without preview check as they may or may no have been afflicted by your addition of a "g" that… «noone understands». -- Tuválkin 14:33, 2 April 2013 (UTC)
Before the icon was turned around was a list of places using it saved? The list now points both to the correct and incorrect use. I saw that a number of articles got updated but there are still more to go. At this time or around the same time a gap started to appear between icons horizontally. Is this related or a separate issue? Maundwiki (talk) 20:05, 23 April 2013 (UTC)

Most regretfully, I still encounter a lot of cases when Axpde has failed to switch the ENDE icons, in nl.wp, fr.wp, ru.wp... And there are also uENDEs, about which nothing has been done even though they are on Bilderkatalog (I guess it gets quite inconsistent), and also other colours... YLSS (talk) 21:17, 30 May 2013 (UTC)

Til Axpde

moved from File talk:BSicon exENDEl.svg

Danish: Hej User:Axpde. Efter at du har spejl vendt billedet den 25. marts 2013 er der gået koks i skabelonerne på en helt masse jernbane artikler på den danske wikipedia. Blandt andet denne Aalborg-Hadsund Jernbane du bedes lige rette problemet. Da vi ingen forstand har på det. :) Vh --Søren1997 (talk // contributions) 19:48, 21 October 2013 (UTC)

Unfortunately, Axpde has updated only a small part of articles that use   (ENDEl) and related. I have encountered broken templates in ru.wp, fr.wp, no.wp and even de.wp. Moreover,   (uENDEl) and similar still show the older convention design. The only remedy is to manually update those RDTs that you notice: just replace ENDEl with ENDEr in code and vice versa. YLSS (talk) 20:37, 21 October 2013 (UTC)
I wouldn't say "only a small part". And there is no "older convention", just people ignoring the convention (which is as old as the BSicons themselves). a×pdeHello! 12:57, 4 November 2013 (UTC)
OK, not a small part, sorry, but still not a small part is left with ENDEs pointing the wrong way, and there is no easy way to find them now; and I'm only speaking about the "bahn" set. YLSS (talk) 13:37, 4 November 2013 (UTC)
Also, what would be your opinion about dropping "l"/"r" for ENDEs and renaming them   (ENDEeq) etc.? You once wrote that you "have general objections to theses icons [  (CONTl),   (STRl)] because of the inflationary use of the suffix 'l'. IMHO "STRl" should show this  "... YLSS (talk) 13:41, 4 November 2013 (UTC)

fq/gq & aq/eq

I guess this business deserves some postfactum remark. Following Axpde's incomplete attempt at swapping ENDEs (but not uENDEs), to which some ancient leftovers of CONT swapping are added, I decided to put an end to this chaos with an iron fist. The pattern is intuitive:   (CONTfq),   (CONTgq),   (ENDEeq),   (ENDEaq). Thus a distinction is preserved between a line that is actually on one side of an object (i.e. the line ends/starts at the object), and a line that continues past an object to some direction. Those files that contain a single design in their history, or those whose current design is the same as the original one, I renamed. Those that differ in their current design from the original file, I marked with {{COM:WPBS/obsolete}} (which places them into Category:Icons for railway descriptions/obsolete), and uploaded a new file with a new name. When all instances are replaced (if ever), original versions should be merged as older versions of my uploads to preserve attribution etc. So I request everybody: if editing an RDT containing either CONTs or ENDEs across, please update them. (I was glad to notice that these new files have already been used by other users in different Wikipedias!) YLSS (talk) 18:06, 13 December 2013 (UTC)

This note (or something similar) should probably be added to the relevant files, too. Useddenim (talk) 02:45, 14 December 2013 (UTC)
I like the way this gordian knot was finally untangled. -- Tuválkin 19:19, 27 December 2013 (UTC)

UPD: Some month ago, I finished up with the bahn-set ENDEs. YLSS (talk) 17:52, 30 September 2014 (UTC)

vHSTl vs. lv-HST

At the moment, the older   (vHSTl legende) is duplicated by newer   (lv-HST). (The latter should be tagged as duplicate later.) The title of the former is quite established (see en:Wikipedia:Route diagram template/BSicon-stations); however, since we're getting rid of "legende", what should the new title be?   (lvHSTl)? Or rather that same   (lv-HST)? For comparison, we have   (lvHSTc1),   (vHSTg legende),   (lBHFl),   (lBHF-L),   (BHFl). YLSS (talk) 19:55, 4 May 2013 (UTC)

The naming of parallel lines is as follows:
vROOT  indicates both lines:   (vSTR)
v-ROOT indicates the left line only:   (v-STR)
vROOT- indicates the right line only:   (vSTR-)
So, your answer is, “Preserve   (lv-HST).” Useddenim (talk) 22:07, 4 May 2013 (UTC)
'Tis just the answer I wanted. But that brings in another question:   (lvHSTc1) or *  (lv-HSTg)??   (lvHSTg) or *  (lHST-)?? And if the latter, then how the hell are we to call   (lvHSTc1)? Or if the former, then unstrike the previous question. YLSS (talk) 22:54, 4 May 2013 (UTC)
Since you raised the point, I now realize that the "v" in   (lvHSTc1) (et al.) is unnecessary, and should more clearly be named simply   (lHSTc1). Useddenim (talk) 12:40, 5 May 2013 (UTC)
(Well, I have no desire to move those 16 once again...) Let's then stick with   (lv-HST). So, what's with   (vHSTg legende)? What do the others think? YLSS (talk) 17:43, 9 May 2013 (UTC)
Answered to this question by myself having moved "vINTg legende" to   (lINT-). The main question for me was to include "q" or not; however, this is only relevant for e.g.   (BRIDGE-) vs.   (BRIDGEq-). For INT's overlay there is no difference, so it may be dropped. So, TBD:   (lHST-). YLSS (talk) 23:52, 24 May 2013 (UTC)
And please remind me, should it be   (exlv-HST) or   (lv-exHST)? Or, since there is only one feature,   (v-exlHST)? YLSS (talk) 17:58, 9 May 2013 (UTC)
  (exlv-HST). u|e|x only appear to the right of "v" when they do not apply to both lines. E.g.   (vuexKBHFa-eBHF). Useddenim (talk) 19:48, 9 May 2013 (UTC)

Ascents & locks

separated to Talk:BSicon/Renaming/Canals

ugINT

Could someone rename BSIcon ugINT to the correct form? http://commons.wikimedia.org/wiki/File:BSIcon_ugINT.svg Thanks Deonyi 11:04, 18 June 2013 (UTC)

What does that even mean? -- Tuválkin 12:00, 18 June 2013 (UTC)
I guess he meant that there was capital "I" in "BSIcon". I have also renamed "ug" -> "g" as decided here. So,   (gINT). YLSS (talk) 13:20, 18 June 2013 (UTC)
Ah, I didn’t even noticed that (and I done worse in the past). I was not up to date on the ug/g/ugm kerffukle, so I didn’t change that, either. -- Tuválkin 15:45, 18 June 2013 (UTC)
BTW, Tuválkin, are you really going to re-upload all INT-interchanges? I thought that discussion only concerned the circle radius. The "extended" versions currently use either 52.smth or 50. (I've uploaded a couple using the latter.) YLSS (talk) 14:20, 18 June 2013 (UTC)
replied at Talk:BSicon/Icon geometry and SVG code neatness#INT circle radius.

Assymetric bridge

CONTg CONTg BSicon .svg
uexvSTR+l + kSTRgl
BSicon uexvSTR+l.svg
kBRKuf + uexSTRq-
BSicon BRKukg.svg
uexSPLe + STRrg
BSicon uexSPLe.svg
kBRKuf + kABZql
BSicon BRKukg.svg
uexSTRrf + STRlg
BSicon uexSTRrf.svg
CONTf STRlf STRrf
(see here with >2 overlay support)

At en:User:Useddenim/Géofer there’s a can of worms including i.a. this apparently misdrawn bridge:   (BRÜCKE3a). At first sight, and based on its name, it maybe thought to be an overlay match for something like   (uexvSTRq-), but it doesn’t look good (→)   BSicon .svgBSicon BRKukg.svgBSicon uexSTRq-.svg (uexSTRq-kBRKuf) (ren.). Its usage(ren.) shows it to be an one-of overlay for   (kABZql), for which it looks good (→)  BSicon .svgBSicon BRKukg.svgBSicon kABZq+4.svg (kABZqlkBRKuf) (ren.) (it would work well also for  BSicon .svgBSicon BRKukg.svgBSicon kABZq+1.svg (kABZqrkBRKuf) (ren.), of course, although for things like BSicon .svgBSicon BRKukg.svgBSicon eABZq+4.svg (eABZq+4kBRKuf) (ren.) it is not so good). Therefore, I suggest it should be redrawn to eliminate the thin white gaps and renamed to something like   (kBRKuf). -- Tuválkin 20:04, 2 July 2013 (UTC)

✓ Done -- Tuválkin 10:30, 4 August 2013 (UTC)

Misnamed bridge

At en:User:Useddenim/Géofer there’s a can of worms including i.a. this unusually named bridge icon   (xevKRZo). Since the double line (witch is supposed to be the main feature of the icon, as it goes vertically and the icon name includes the "v", and rightly so) goes under the simple line across, it should be named with the "u" suffix, not "o". Right? -- Tuválkin 20:27, 2 July 2013 (UTC)

Yes, but… We’re back to the “three lines on an icon” problem, and that can’t be fixed by simply having the prefix letters in the wrong order. Since the parallel lines are asymmetrical, the icon name should actually be parsed line by line (like the station icon below):   (vKRZu-xKRZu) is my suggestion. (But if you check the upload history of the icon, you’ll see that it was originally uploaded as a KRZo but Géofer (talk · contribs) changed it four months later, and his only explanation was the cryptic comment “Bad Icon”!) Useddenim (talk) 23:23, 2 July 2013 (UTC)
Renamed. Useddenim (talk) 01:18, 3 July 2013 (UTC)

Misnamed station

At en:User:Useddenim/Géofer there’s a can of worms including i.a. this unusually named station icon   (vuexKBHFe-BHF). Since it includes both u-blue and bahn-red, the former in the main (right side) position, it should be preffixed with "um", not just "u", right? -- Tuválkin 20:31, 2 July 2013 (UTC)

Um, I’m not sure. Take a look at en:WP:Route diagram template/Catalog of pictograms/parallel stations#Mixed: only   (mvBHF-exBHF) and   (umvexKBHFa-BHF) use the "m" prefix—everything else omits it (possible because the names are so specific). Useddenim (talk) 21:25, 2 July 2013 (UTC)
For that I would suggest   (umvexKBHFe-BHF) :) NoNews! 12:14, 2 August 2013 (UTC)

mhKRZhl

As I was working on uploading missing icons at w:Wikipedia:Route diagram template/Catalog of pictograms/junctions/crossings I noticed that   (mhKRZhl) seems to be misnamed. If I understand everything correct, it should be   (umhKRZhl), right? As it is currently named, the icon is used in 9 articles on 5 different projects, so I didn't want to just use the move tab at the top. -- Imperator3733 (talk) 06:53, 4 August 2013 (UTC)

✓ Done, but then it struck me that it should be   (umKRZhl) instead, as the main line (vertical) is not elevated itself! :-( It needs rerenaming. -- Tuválkin 10:51, 4 August 2013 (UTC)
✓ Done rerenaming, but there’s a lot of misnamed icons (and redirects) — just check at en:Wikipedia:Route_diagram_template/Catalog_of_pictograms/junctions/crossings#Grade_separated… -- Tuválkin 12:13, 4 August 2013 (UTC)
✓ Done cleaning up the remains (new   (mhKRZhl)). YLSS (talk) 20:13, 16 October 2013 (UTC)

Who deleted so many icons?????

See any page (such as en:Wikipedia:Route diagram template) and you will find there are a great number of icons that can't be shown normally.Who did that?????What happened on earth?????江漢思歸客 (talk) 15:41, 18 September 2013 (UTC)

I'm not seeing any missing icons on that page. Could it be your browser or ISP is blocking images? Vanisaac (talk) 16:35, 18 September 2013 (UTC)

uLJUNC

moved to Talk:BSicon/Renaming/Canals#uLJUNC

xv-STRa vs. ev-STRa

After staring for a long while at these tables, I got an impression that we should swap   (xv-STRa)  (ev-STRa), as well as   (uxv-STRa)  (uev-STRa), right? Unless anybody wants to use this opportunity to rename them to something SPLitty. YLSS (talk) 19:37, 28 October 2013 (UTC)

Changing the preffixes so that the “main” line is the straight one? Good idea; I don’t know what I was thinking when I named those. As for SPL instead of STR, I’m all for it — plus, it makes the renaming easier, as no temporary name will be needed, making the whole renaming/relinking process ⅔s faster. -- Tuválkin 17:48, 29 October 2013 (UTC)
Not so that the "main" line is the straight one, but so that the left (IRL right) line is "main", like in   (evSTR) vs.   (xvSTR). Not as straightforward with splits, but staring for a long while at those tables made me realise that. YLSS (talk) 18:21, 29 October 2013 (UTC)
I see. Well, I trust you. :-) -- Tuválkin 01:01, 30 October 2013 (UTC)

Later on: Now it's   (ev-SHI2gr) &   (xv-SHI2gr). YLSS (talk) 21:33, 23 January 2014 (UTC)

Parallel lines across

DSTq- and -DSTq

I just saw   (DSTq-) and   (-DSTq), and was wondering if they should be normalized with   (vDST-) and   (v-DST) as vDSTq- and v-DSTq. Vanisaac (talk) 21:40, 29 October 2013 (UTC)

Nope. It was decided (at Talk:BSicon/Renaming/SPL#Conclusion? or earlier?) that icons for parallel tracks across that have two roots in their names (incl. a root + lacuna) should not have "v", just because it is useless. YLSS (talk) 22:16, 29 October 2013 (UTC)
Ok, so is there a good reason not to have   (vDST-) and   (v-DST) at DST- and -DST? Vanisaac (talk) 23:19, 29 October 2013 (UTC)
We will then have to rename all such icons to names without "v"; if you really want to do this, you may have a go. In contrast, icons with parallel lines across are less abundant, and a good deal of them have already been uploaded (or renamed) without "v". YLSS (talk) 00:45, 30 October 2013 (UTC)
Even simpler, lets ditch that rule and go for a simpler one: That preffix "v" means double lines always, regardless of their being horizontal, vertical, diagonal, curved, whatever. -- Tuválkin 00:51, 30 October 2013 (UTC)
I should say that I always found particularly silly that rule that says you recognize a horizontal double line icon from a vertical one by the absence of the "v" preffix, especially when suffix "q" exists for the same role. The fact that, according to some, "q" (with "v") means horizontal only in specific circonstances and that absence-of-"v" means horizontal only in a different set of specific circonstances makes it all even sillier. -- Tuválkin 00:51, 30 October 2013 (UTC)
I'm against such a move. First of all, there is no necessity in it: omission or inclusion of "v" does not lead to any naming conflict, as far as I can see. Secondly, there is a chance that some names would clash if we either drop "v" everywhere, or add it. In addition, this dual approach provides us with an additional naming pattern that can prove beneficial in comparison to other variants. YLSS (talk) 21:38, 30 October 2013 (UTC)
Yup, I can even provide an example that there should be a difference:   (vSTRl-) vs.   (STRl-) (as it should be named). Or the possible BSicon .svgBSicon STRq-.svgBSicon SPLe+r.svg    (ABZq+r-ABZg+r) vs. BSicon .svgBSicon v-STR+r.svgBSicon vSTR+r-STR.svg    (vABZq+r-ABZg+r) (leaving aside the matter of applicability of "SPL"). YLSS (talk) 13:27, 4 November 2013 (UTC)

Useddenim, maybe   (DST-DST) (not   (vDSTq)) should be   (DSTq-DSTq)? Or do you propose some other rule? YLSS (talk) 10:28, 4 November 2013 (UTC)

No reply, so renamed it. YLSS (talk) 20:53, 20 November 2013 (UTC)
No reply because I was away on vacation, and just saw your question now. Now the   (vSTRq-) &   (v-STRq) family need to be fixed. (Although, personally I feel that no v + q suffix is redundant.) Useddenim (talk) 02:06, 21 November 2013 (UTC)

Which POV to take?

See also: Talk:BSicon/Renaming/Archive 3#-v as suffix

We currently have a properly named   (tvKRZtq) (parallel tracks across crossing a single vertical), and also an equally properly named   (utKRZtv) (single vertical track crossing parallel across). I don't really think that it is necessary to choose a single way of naming them and get rid of the other. A better solution would be to create permanent redirects from both variations, right?. YLSS (talk) 21:38, 30 October 2013 (UTC)

SPL vs. SHI

Please have a look at Talk:BSicon/Renaming/SPL#SPL vs. SHI. YLSS (talk) 09:08, 27 November 2013 (UTC)

lhSTR et al.

What about simplifying the   (lhSTR) prefix+ROOT to ELEV? (As   (ELEVf) etc. were originally uploaded, but this one would now become ELEVaf). Useddenim (talk) 13:51, 29 December 2013 (UTC)

What about   (lhBHF),   (lhPSLm),   (lhLSTR) etc.? I would like to see them consistently named. YLSS (talk) 17:22, 29 December 2013 (UTC)
  (EBHF),   (EPSLm), etc. I.e. ELEV+suffix for basic structures and E prefix for anything else. Useddenim (talk) 17:31, 29 December 2013 (UTC)
Wouldn't it be just easier to stick to the current pattern? With two standard prefixes "l" & "h", no new root modifiers and no complication of "ELEV here, E- there"? After all, lhSTR is just one letter longer than ELEV. And more explicable:   (hSTRef) =>   (lhSTRef). YLSS (talk) 17:48, 29 December 2013 (UTC)
  (EDAMM)LELEV. (And no jokes about Washed-rind cheese.jpg (EDAM) please.) Explicable? maybe; but intuitive? I don’t know. I find it easier to think that ELEVelevated structure rather than (mentally) parse out l legend(e) h high STR stretch. Useddenim (talk) 18:06, 29 December 2013 (UTC)

Redlinked image

Moved from en:Template talk:Shanghai Metro/Line 6

@Circeus, Useddenim: File:BSicon utABZld.svg has been deleted from Commons, leaving a red link in this template and several others. This seems to be connected with a renaming initiative on Commons (User:Circeus/BSicon renaming/Simple junctions). What is the best way to fix these templates? -- John of Reading (talk) 09:55, 18 January 2014 (UTC)

The short-term fix is to recreate the redirect to   (utABZgl+l) (which I have already done). You will have to contact Fastily (the admin who made the deletion) to find out who made the Speedy Deletion request for the file, as the previous history disappeared when the original was deleted. Useddenim (talk) 17:28, 18 January 2014 (UTC)
Actually, that was a lapse of attention on Fastily's side. Sameboat had tagged the file with the wording "this should be made into a redirect to File:BSicon utABZgl+l.svg" (AFAIR). YLSS (talk) 18:07, 18 January 2014 (UTC)
Thank you for sorting this out. -- John of Reading (talk) 21:28, 18 January 2014 (UTC)

The "C" root prefix

"C" is for cut   (CBHF), and I think that’s good but — it is in use for the Spanish Cercanías roundels, akin to the "S" for German S-Bahn   (SBHF). I found out by chance when, among stations in cuts,   (tCBHF) showed up. Not that tracks and stations located in terrain cuts inside a tunnel are terribly common, but maybe it is not too soon to start renaming Cercanías to match the equivalent Canadian, Danish, and Hungarian icons. -- Tuválkin 19:08, 23 February 2013 (UTC)

My bad. I thought I had caught all the Spanish ones when I did the Canadian and Hungarian ones. Useddenim (talk) 23:16, 23 February 2013 (UTC)
Massive renaming matching the Danish model, then? -- Tuválkin 09:18, 24 February 2013 (UTC)

Could somebody also take care of these:   (CHST) &   (eCHST)? There's a couple more in Category:Icons for railway descriptions/suburban commuter service, but presently they do not seem to pose any conflict. YLSS (talk) 16:21, 30 April 2014 (UTC)

Now ✓ Done. By myself. Ahmm... YLSS (talk) 20:46, 6 September 2014 (UTC)

Transition to tunnel

At Talk:BSicon#TUNNELql Tuválkin wrote:

I restored [  (TUNNELql)], as also   (TUNNELqr), which had been similarly vandalized. I also uploaded their vertical equivalents, as   (TUNNELg) and   (TUNNELf). This matter brings up two questions: One of naming, another of semantics.

  • Concerning naming, these four icons present yet again a clear example how bad is having square icons with a previleged sense for vertical lines and none for horizontal lines. Using a trailing "q" as a general 90º rotation switch, as I defend, the horizontal version of these would be named simply as their vertical counterparts with said "q" appended:
    •   (TUNNELf)  (TUNNELf)  (TUNNELfq)  (TUNNELql)
    •   (TUNNELg)  (TUNNELg)  (TUNNELgq)  (TUNNELqr)
  • <...>

-- Tuválkin 23:52, 29 April 2013 (UTC)

At a later time, Tuválkin has expanded the Category:Icons for railway descriptions/set u/parallel lines/tunnel to ground with a series of new icons (apparently to compensate for overwriting   (uvTUNNELa), the previous version of which looked closer to the present   (uvTNLfa)). However, it appears that he confused "f" ("pushed forward") and "g" ("pushed backward") in the process. Cf.:   (PORTALg) (&   (ABZ3+1g)) but   (TUNNELg) &   (uvTNLga);   (PORTALf) (& the obsolete   (vHSTf legende)) but   (TUNNELf) &   (uvTNLfa). I totally support his system of "fa" vs. "fe" vs. "ga" vs. "ge", and even more do I support his   (uvTNLfa)  (uvTNLfaq), but "f" and "g" should be switched. I would also prefer slightly more "TNLaf" instead of "TNLfa" etc., and this would also facilitate renaming. So what about: Replaced TNL with tSTR, 21:04, 2 November 2013 (UTC)
  •   (uvTNLfa)  (utvSTRag)
  •   (uvTNLge)  (utvSTRef)
  •   (uexvTNLgaq)  (uextvSTRafq)
  •   (vTUNNELa-)  (tvSTRag-)
  •   (exTUNNELlu)  (extSTRaq)
  •   (uTUNNELru)  (utSTReq)
  •   (TUNNELql)  (tSTRagq)
  •   (TUNNELg)  (tSTRef)
etc. Another issue is "TUNNEL" vs. "TNLa/e" vs. "tSTRa/e". "TNL", AFAIK, has only been used in Tuválkin's uploads; the other option has long been used in Category:Icons for railway descriptions/tunnel/uw/portal, and more recently by me in   (t-STRqa) and similar. The benefit of using "tSTRa/e" system is that it allows more flexibility, e.g. we can deal with the likes of   (ABZf+l TUNNELa orange)  (ABZtgal orange); the drawback is that it can potentially conflict with other uses of "a"/"e", as I said above. So I really don't know which one is better. Opinions? YLSS (talk) 21:26, 25 October 2013 (UTC)
I’ve also been using the "tSTRa/e" convention, and I also agree that Tuválkin’s fs and gs need to be reversed. Useddenim (talk) 22:54, 25 October 2013 (UTC)
Yes, that was a mess up — the single line and the double line icons are not in a agreement. I blame not enough coffee for it. Go ahead and rename. If help renaming is necessary, just ask for help and lets divide the task. -- Tuválkin 18:00, 29 October 2013 (UTC)
Well, I don't usually rename things en masse just for the sake of renaming; but if I encounter one in a diagram, I will rename it. Nevertheless, what is your answer: TNLa/e or tSTRa/e? "af" or "fa"? YLSS (talk) 18:45, 29 October 2013 (UTC)
No reply received here, so I started with   (utSTRaq) &   (utSTReq). YLSS (talk) 21:04, 2 November 2013 (UTC)

I guess it's ✓ Done now. YLSS (talk) 17:04, 17 February 2014 (UTC)

KRZ5/KRZ4

Shouldn't   (KRZ5-lf),   (KRZ5-rf),   (KRZ5-rg) &   (KRZ5-lg) actually be named KRZ4 to match   (KRZ4d)? Useddenim (talk) 17:53, 30 June 2013 (UTC)

Symbol keep vote.svg Agree -- Tuválkin 19:08, 30 June 2013 (UTC)
Symbol oppose vote.svg Oppose. I consider Circeus's proposal the best option, incl.   (KRZlr+lr). YLSS (talk) 16:13, 17 November 2013 (UTC)
Good point. Let me change my vote and propose this:
  •   (KRZ5-lf)  (KRZr+lr)
  •   (KRZ5-rf)  (KRZl+lr)
  •   (KRZ5-rg)  (KRZlr+r)
  •   (KRZ5-lg)  (KRZlr+l)
  •   (KRZ4d)    (KRZlr+lr)
-- Tuválkin 21:58, 17 November 2013 (UTC)

✓ Done according to Circeus's proposal. YLSS (talk) 06:47, 5 June 2014 (UTC)

Parallel curves

I don't know whether this was discussed anywhere and what are the precise principles of naming such icons as   (v-STRrg),   (v-STR+l) and   (v-STR+l2), but I was never able to grasp them. So when I needed to rename the charming   (vABZxgrC+r-STR), after a lot of swearing, I settled on   (vABZgnrg+xnrf-STR). The upper branch is "nrg": narrow to the right-shifted-back; and the lower branch is "+xnrf": unused narrow from right-shifted-forward. That is, the system is:   (v-STR+lf),   (v-STR+l) and   (v-STR+lg);   (v-STRl+l) ->   (v-STRlg+lf); while   (vSTR-ABZl+l) is correctly named. I do not propose moving the existent icons (unless necessary), but for new uploads this would be quite a straightforward scheme. If the old "lf", "rf", "lg" & "rg" are not used for them, I do not foresee any conflict. YLSS (talk) 22:39, 27 October 2013 (UTC)

I saw no opposition, so I (expanded and) moved the series of   (v-STRl+l) ->   (v-STRlg+lf) and   (STRl2-STR+l2) ->   (vSTRlg+lf-). YLSS (talk) 22:25, 29 October 2013 (UTC)

An interesting question. The current name of   (exSTRl-STR+l) is unsatisfactory due to the fact that such a name should be occupied by BSicon .svgBSicon -STR+l.svgBSicon exSTRl-.svg . When there are two roots for parallel lines across, prefixes have to be duplicated for both... So, the icon in question can be renamed either to exSTRl-exSTR+l (which would be more representative for a combination of   (exSTRl-) &   (ex-STR+l), but would require some complications in galleries) or to exSTRlg+lf, as a non-parallel version of   (exvSTRlg+lf-) &   (exv-STRlg+lf). Which one is better? YLSS (talk) 18:32, 26 January 2014 (UTC)

Seems like nobody's caring, so I choose   (exSTRlg+lf) as the "main" location of these icons, with redirects from the other option. YLSS (talk) 06:46, 30 January 2014 (UTC)

✓ Done not so long ago. YLSS (talk) 17:12, 17 February 2014 (UTC)

Double curves

Another long-standing mess. Currently we have:

  • in the "u" set: the complete series of   (uvSTRlf),   (uvSTRrf),   (uvSTRlg),   (uvSTRrg), with "e", "x" and "ex" variations (all 2011, Useddenim) and "t" (2012, Pi.1415926535);
  • in the "bahn" set:   (vSTRlf(!)) (2011, Tuválkin);   (vSTR+r) &   (tvSTR+r) (2012, Verminclone);   (vSTRl-STRl) &   (vSTRr-STRr) (2013, BjørnN).

The "vSTRlf"/"rf"/"lg"/"rg" names are occupied in the "bahn" set by redirects from former names of   (vSTRgl), and are very, very far away from being freed. "vSTRl" and "vSTRr" have only recently been renamed to   (SPLaq) and   (SPLeq), but are used only in some dozen pages. The most precise name for e.g.   (uvSTRlg) would be   (uvSTR+rf-STR+rg), as   (uvSTR+rf-) +   (uv-STR+rg) (as I described above). However, that would be a really long name for such a simple feature. Since we seem to have agreed that   (uvSTR+r-) +   (uv-STR+r) would rather form   (uSPL+ra) (or   (uSPLa+r)?) and not "uvSTR+r", I suppose there would be no problem to set the following pattern:   (uvSTRl),   (uvSTRr),   (uvSTR+r),   (uvSTR+l) - or would there be? YLSS (talk) 07:53, 10 December 2013 (UTC)

Symbol keep vote.svg Agree. WRT BSicon .svgBSicon uv-STR+r.svgBSicon uvSTR+r-.svg , the naming pattern so far seems to follow tracing the route top-to-bottom/left-to right. Useddenim (talk) 13:04, 10 December 2013 (UTC)
(Of course it's "a", not "e", thanks. But what's the order of suffixes: "+ra" or "a+r"? I would favour the latter. But that is another topic. YLSS (talk) 13:35, 10 December 2013 (UTC))
  (uSPLa+r): shape » direction/orientation » modification. Useddenim (talk) 04:50, 11 December 2013 (UTC)
(Ah, they are already in existence! Well, that's great. YLSS (talk) 17:05, 12 December 2013 (UTC))

Also ✓ Done. The set expanded to the utmost by Vanisaac & Useddenim. YLSS (talk) 17:12, 17 February 2014 (UTC)

With crossing

Also, I would like to draw your attention to a new peculiar series of icons introduced by BjørnN, which I have grouped under Category:Icons for railway descriptions/parallel railways/junction+crossing/double curve. Initially, I was uneasy with the fact that they use plain "l/r/+l/+r" without "f/g", but I guess that would be an excessive complication in this case. Another option I can think of is   (vABZg+l-ABZg+lu)  (vSTR+vSTR+lo) (ROOT+ROOT). Though I don't think there is really a need to rename them. YLSS (talk) 17:05, 12 December 2013 (UTC)

Parallel interchange

Riddle me this: how should we name this one:   (vBHF-KBHFla)?   (vBHF-KBHFa-R),   (vBHF-R-KBHFa),   (vBHF-M-KBHFa) or even   (vBHF-M-KBHF-Ra)? YLSS (talk) 21:44, 15 November 2013 (UTC) Hm, not   (vBHF-M-KBHFa) at least, 'cause otherwise we won't be able to distinguish   (**vKBHFa-BHF-M) vs. BSicon .svgBSicon v-STR.svgBSicon vKBHF-Ma.svg . YLSS (talk) 21:48, 15 November 2013 (UTC)

I think the best name is   (vBHF-KBHFa-R), where the "-R" sufix refers to the line at the viewers’ left (right side of the direction of travel). On the other hand,   (vBHF-R-KBHFa) should be a double-line square icon equivalent to   (dBHF-R)+  (dKBHFa). -- Tuválkin 20:36, 16 November 2013 (UTC)
OK. (Hm, I though the explanation was "continues to the right, viewed in the direction of travel"; but d'oh, to the hell with explanations...) YLSS (talk) 23:31, 16 November 2013 (UTC)

CONTrf inconsistency

I noticed that   (CONTrf) and   (lCONTrf) are inconsistent. I found this because needed an arrow to the left with its head touching the left icon edge (leaving room on the center of the icon) and had to name it   (CONTfaq). -- Tuválkin 10:19, 7 November 2013 (UTC)

And now I see it should have been better to name it   (CONTfeq) (end) instead. -- Tuválkin 10:24, 7 November 2013 (UTC)
Well, we seem to be using the same prefix for "direction forward" and "shifted forward", but previously this did not seem to pose much problems, as in   (lCONTff). That said, I don't think now that I chose wisely when I named   (lCONTgf); yes, it's moved forward along the direction it's pointing to, but taken universally, it's pushed backward and should rather be   (lCONTgg). Likewise   (lCONTrf) should be   (lCONTggq) (no "l"/"r"!), and   (CONTfaq) should IMHO be   (CONTggq). About   (CONTrf) you can read here - we were unable to find a satisfactory way to name them (that is, the original naming pattern introduced by their creator is as satisfactory as all other proposals). YLSS (talk) 12:43, 7 November 2013 (UTC)
I've moved all my former lCONTs to new titles, with first "f"/"g" pertaining to direction (I'm uneasy with using "a"/"e" for this), and second "f"/"g" pertaining to position along the y-axis, as it is with other classes of icons. Additionally, no "l"/"r"s; and I also uploaded the series of   (lCONTfg),   (lCONTgf),   (lCONTfgq),   (lCONTgfq). These could have been named without the "l" prefix, but... that would mean deducing something about the icon which isn't really there; so legende it is. P.S. I did not touch   (lCONTl), but IMHO it should rather be   (lCONTfq).) YLSS (talk) 12:59, 20 November 2013 (UTC)

Hm, another argument against using "a"/"e" for shifted forward/backward in this case: we already have a whole family of   (uCONTfa) /   (uCONTge) icons. YLSS (talk) 18:48, 2 December 2013 (UTC)

CONTinuation tail

Robot8A had uploaded a version of   (uexvCONTfgr) without the forward (upper) arrow as uexSTRfgr which did not really make sense; I renamed it uexCONT-r (to go with   (uexCONTl)) for lack of any better ideas. Useddenim (talk) 13:53, 5 November 2011 (UTC)

I have renamed it to   (uexCONT+gq), that is "from back". A line thus continues from back to forward:      , uexCONT+gq uexSTRq uexCONTfq. Current   (uexCONTfa) should likewise become   (uexCONT+g). Otherwise, the icon would have become uexCONTfaq – contrast Tuválkin's CONTfaq above (now   (CONTggq)). OK? YLSS (talk) 09:02, 27 December 2013 (UTC)
Pretty much OK, yes. -- Tuválkin 19:39, 27 December 2013 (UTC)

Platforms

  (dtSTRpr) &   (dtSTRpl) are currently unused at those titles, only via redirects from the more appropriate   (tdSTRpr) &   (tdSTRpl). However, instead of requesting them to be moved to those titles, I think it may be better to choose some others and get rid of the rogue "p" suffix (  (dSTRpr) &   (dSTRpl) are also used only sparsely). Tuválkin, I think you're the one who uploaded most of the platform icons lately; do you have any ideas better than the classic tdSTR+BSr & tdSTR+BSl? YLSS (talk) 23:45, 10 January 2014 (UTC)

Create the PFM root (for platform—it works in most languages).
  (dSTRpr)dPFM-R
  (dSTRpl)dPFM-L
  (dtSTRpr)tdPFM-R
  (dtSTRpl)tdPFM-L
Useddenim (talk) 00:12, 11 January 2014 (UTC)
PFM looks good; I have been using PLT myself: I cannot remember if I invented it or just picked up an older use of it. Either way, it is good. -- Tuválkin 12:54, 11 January 2014 (UTC)

Having thought more, I decided to keep the "classic" naming scheme here. After all, the (rail) track and the platform are quite separate objects, and not a "modification" of a simple track. I thought about something like STR+Pl, but then... "BS" is from de:Bahnsteig, so why to invent more? Result:   (dSTR+BSl),   (dSTR+BSr),   (udSTR+BSl),   (udSTR+BSr),   (tdSTR+tBSl),   (tdSTR+tBSr),   (tdSTRe+tBSle),   (tdSTRe+tBSre). If anybody disagrees, feel free to choose some other title. YLSS (talk) 06:09, 7 May 2014 (UTC) Two new also:   (vSTR+BSm) &   (uvSTR+BSm). YLSS (talk) 08:16, 7 May 2014 (UTC)

Duplicate icons

  (dKBHFre),   (dKBHF-Le) et al. need to be rationalized. Useddenim (talk) 18:50, 14 January 2014 (UTC)

I was just looking at those. Recently, an icon that I created -   (uexdKBHFre) - was renamed   (uexdKBHF-Le) and I believe that it's part of a plan to change all the suffixes from la/le/ra/re to -Ra/-Re/-La/-Le. Today, I created fourteen similar icons but in the KHST group, for which I used the new-format suffixes:   (exdKHST-La)   (exdKHST-Le)   (exdKHST-Re)   (uexdKHST-Re)   (uexdKHST-Ra)   (uexdKHST-La)   (dKHST-La)   (dKHST-Le)   (dKHST-Re)   (dKHST-Ra)   (udKHST-Ra)   (udKHST-La)   (udKHST-Le)   (udKHST-Re), and I was careful not to create (say)   (exdKHST-Ra) if the equivalent   (exdKHSTla) already existed. --Redrose64 (talk; at English Wikipedia) 21:57, 14 January 2014 (UTC)
That was really well done! Because dupes were being uploaded quite often lately (  (uexSTR+l-) vs.   (uexvSTR+lq-),   (vSTRl) vs.   (vSTRl-STRl) vs.   (vSTRlf(!))). YLSS (talk) 06:24, 15 January 2014 (UTC)
Useddenim, what do you mean? I've been moving them at an occasion, but if you want do deal with them once and for all, that of course would be good. YLSS (talk) 06:24, 15 January 2014 (UTC)

I guess it's ✓ Done by now. YLSS (talk) 10:03, 10 October 2014 (UTC)

KRX

Before I inadvertently stir up more controversy… Since ÜWlr+rl  (KRX) was OK, then I suggest   (ÜWolr+url)  (KRXo) and   (ÜWolr+orl)  (KRXu) because we’re following the convention of page top-to-bottom then page left-to-right, so   (STR2+4) takes precedence over   (STR3+1). Any thoughts/objections/comments? Useddenim (talk) 00:03, 25 February 2014 (UTC)

Seems to be OK. Were there any other similar cases before? YLSS (talk) 03:12, 25 February 2014 (UTC)
I agree, too. -- Tuválkin 08:14, 25 February 2014 (UTC)

RENAMING

Response

Moved from en:Wikipedia talk:Route diagram template/Catalog of pictograms/stations.

": Btw. someone announced widely to introduce a new version of icons all named English, but I haven't heard much about it lately ... maybe he realised, that there is no sense in reinventing the wheel! But still it's subject to optimising ;-) Bye axpdeHello! 11:03, 6 October 2009 (UTC)"

That someone I believe is me. And i am still working on it. But there are so many icons that people are coming up with, that I've been scaling it back to BASIC icons. I'm crap at reproducing things and uploading them, so you will get a list which translates the DE to EN. Then someone with skill can take the EN and upload it somewhere.

Hopefully it will also settle the direction problem (u/d f/g r/l) also.

Give me to the end of the year. Ta Dkpintar (talk) 15:02, 27 November 2009 (UTC)

2014

Is it not time for us to separate ourselves from the German-based naming conventions and develop some simple icons names for English-speaking or English-using people here?

I've worked on some that I think are simple, easy-to-use, and without multiple permutations that are not necessary.

Thoughts, comments or criticisms?

Thanks

DKPIntar

First, why English? Remember, we are from different places around here, and so everyone can shout "let's rename them to my language!!" Actually, at fr.wp, they had a system of aliasing for some time so that they could write COURBEdar instead of STRrg. Well, that didn't really work, and those aliases are pretty much dead now...
Second, don't forget that these icons are used not only in en.wp, but in several dozens Wikipedias, so once again, no reason to prefer English. One can claim that English is the language of international communication now (malheureusement!), but... actually, we aren't communicating here, just using simple IDs. There is not much difference what to memorise: STN or BHF, CPIC or KBS.
Third, there's already a large number of roots and prefixes/suffixes that derive from English (and a couple from French & Polish).
And last, we should respect the fact that these icons were invented by users from de.wp. Sadly enough, there are no contributors from over there still really active here. We have full right to improve what we've inherited from them in every possible way, but there is no justification to "separate ourselves from the German-based naming conventions".
-- YLSS (talk) 18:07, 23 June 2014 (UTC)
For what it’s worth, when I’ve created new roots, I’ve tried to use mnemonics that work in at least two languages (e.g. SPLit/SPaLten). Useddenim (talk) 03:47, 25 June 2014 (UTC)
«Thoughts, comments or criticisms»? Hm, 1st off my head: Why should I waste my time even considering seriously a guy who cannot type "~~~~"…? Well, really? -- Tuválkin 04:30, 25 June 2014 (UTC)
For the record: Special:Contributions/Dkpintar, Special:ListFiles/Dkpintar, and User talk:Dkpintar&oldid=33298394. -- Tuválkin 05:03, 25 June 2014 (UTC)
Rather these: en:User:Dkpintar & en:User:Dkpintar/sandbox. YLSS (talk) 07:33, 25 June 2014 (UTC)

Elevated uw crossings

A discrepancy has come to my attention. We have   (hKRZ2+4h) but its corresponding u piece is   (uhKRZ2+4). Both would seem equally correct since neither has an "o" or a "u" suffix. (Not that you could have hKRZ2+4u...) Currently hKRZ2+4 is a redirect to   (hKRZ2+4o). Should the u piece be changed? Lost on Belmont (talk) 00:51, 15 July 2014 (UTC)

Yes, when I renamed   (hKRZ2+4)  (hKRZ2+4h), I forgot about   (uhKRZ2+4)  (uhKRZ2+4h). Cf.   (hKRZ) vs.   (hKRZh). Thanks for checking. YLSS (talk) 05:03, 15 July 2014 (UTC)
@Lost on Belmont: in some of your recent uploads, you used background masking (e.g.   (uehKRZ3+1h),   (xhKRZ3+1h)). Why? There was actually a discussion about this, though unfinished... But I would indeed suggest leaving the mask out for simple icons (without additional prefixes like M), and if needed use some masks or some "legende" formations that include a mask (like   (hleer) or   (lhMABZg23)). YLSS (talk) 09:18, 17 July 2014 (UTC)
Hmm. Didn't get pinged for some reason... There were actually two reasons, first was that originally, the diagonal elevated piece that I used to create the e and x versions used a mask and so I added (and expanded it) to the crossing icons. The second reason was that currently, we don't have any diagonal masks. (I've also noted that some of the other elevated uw crossing do have masks, or partial masks.)
The later uploads didn't include the mask for several reasons. One, I figured out a little more about .svg coding (and therefore didn't resort to the came level of copy + paste). Two, I got lazy and just didn't add it. And three, I was aware of the existing (unfinished) discussion on this very topic and figured someone would probably make a statement about the masks. (Again, I have been lazy and haven't gotten around to that discussion yet. Lost on Belmont (talk) 12:32, 17 July 2014 (UTC)

Diagonal + curve

moved to Talk:BSicon/Renaming/ABZ#Diagonal + curve

Mixed shift crossover

What name should   (?????) have? Would MKRXu+SHI1lq fit into the naming scheme? (Also note that this uses a different shape to   (uSHI1lq), because none of those have crossing bridges and I don't know how to draw them, so I took one from   (vxSTRr-uKRZo). If someone could fix that it would be appreciated.) Jc86035 (talkcontributionsuploads) 09:49, 13 September 2015 (UTC)

Pinging a couple of the regulars on these talk pages in case no one notices this or replies. Jc86035 (talkcontributionsuploads) 11:06, 15 September 2015 (UTC)
  • I’d go for   (mKRZuSHI1lq) instead:
  • preffix "m" (mixed) and not modifier "M" (motorway? mask?),
  • "KRZ" (a "+") and not "KRX" (not a "×"),
  • and no "+" (as it could be mistaken for BSicon .svgBSicon SHI1lq.svgBSicon mKRZu.svg (mKRZuSHI1lq) …).
-- Tuválkin 13:04, 15 September 2015 (UTC)
@Tuvalkin: Thanks for the input. I've renamed the file to what you suggested. Jc86035 (talkcontributionsuploads) 11:13, 16 September 2015 (UTC)