Talk:BSicon/Renaming

From Wikimedia Commons, the free media repository
Jump to navigation Jump to search

See also: Talk:BSicon/Renaming/SPL,
Talk:BSicon/Renaming/ABZ,
Talk:BSicon/Renaming/k and
Talk:BSicon/Renaming/Canals

WSTR[edit]

@Useddenim, Tuvalkin: Should   (hWSTR) etc. be renamed to treat W as "this track is water" rather than "this track crosses water" (i.e. to KRZW;   (WBRÜCKE2) would probably become KRZWo2 or 2KRZWo or something similar)? This would reconcile the railway icons' naming with that of the water junctions like   (WABZgl). This was originally advocated by YLSS in 2014, though I didn't think it made sense until renaming   (kWKRZq+4u) in October. Jc86035 (talk) 14:02, 24 December 2017 (UTC)

  • Looks like a good idea. -- Tuválkin 16:00, 25 December 2017 (UTC)
  • Okay; but, we can't use 2 as a suffix because of the potential conflicts with   (STR2), etc. Useddenim (talk) 14:25, 26 December 2017 (UTC)
    @Useddenim: We could use it as a prefix (as with 1 for BRÜCKE1 etc.); incidentally I was thinking of making 4HUB (from 45°, 4 corners) icons for aligning HUBaq, HUB2 etc. with   (BHF2) etc.. Jc86035 (talk) 08:57, 27 December 2017 (UTC)
    @Jc86035: Wouldn't HUB2+g be a better name for the   (BHF2) overlay (similar to   (CONT2+g)? Useddenim (talk) 14:19, 27 December 2017 (UTC)
    @Useddenim: No, I meant like a   (HUB2) or   (HUBaq) where the HUB fits correctly with a   (BHF+1). I’ve seen some fudging of station positions in diagrams like w:en:Template:WMATA Blue Line where a 3HUB-G2 (or similar name) would be needed to fit 3ACCr+1 in the HUB properly. Jc86035 (talk) 15:21, 27 December 2017 (UTC)

Axpde, I have not reverted you, but I would like you to move   (hWSTR) to   (hKRZW) again and keep it there until you have managed to overturn the consensus above that the W prefix should be used consistently. The file move was discussed here (with that exact file as an example). Don't revert a single file move just to make a point; I moved every file whose name contained "WSTR", and if you want to disagree you are very much welcome to ask about it here instead of clicking revert and not bothering to deal with any of the other similar files that I moved. I am currently aware that I made some errors in this process, like moving   (hWSTRq) to   (hKRZWq) instead of the shorter   (WKRZh), but my main account is "on a wikibreak" (i.e. I locked myself out of it) so I am technically unable to move any files right now.

KRZ means "crossing of to TRACKS", it has every been so and there is no need to overturn a consensus!
It wasn't YOU who invented this system so please don't change things which are contrary to the inventors system! a×pdeHello! 12:56, 2 June 2018 (UTC)
@Axpde: The BSicons cannot be owned by anyone (since they are, after all, hosted on a publicly editable wiki), so gatekeeping the system to those who were around in the mid-2000s would be pointless. As far as I am aware the "system" was created after consensus on 30 September 2006 by Bernina (please correct me if I'm wrong); even icons uploaded on that day have been renamed. In any case, I am the uploader of three-quarters of the BSicons that currently exist and uploaded my first in 2013, and have made more than ten thousand file moves, so you cannot say I did not have a part in it. It's true that many of them are differently coloured copies of icons that previously existed, but even then I have uploaded and redesigned thousands of others.
„Kreuzung“ bedeutet "crossing", richtig?
KRZ has been repurposed for roads (as SKRZ) and for paths (as fKRZ), so it clearly isn't limited to tracks.   (SKRZ-Bu) existed in 2007 as AKRZ-UKu. Jc86035's alternate account (talk) 13:46, 2 June 2018 (UTC)

@Tuvalkin, Useddenim: The errors mentioned are in the titles of these 19 files. I would prefer not to move them to titles which use "l" and "r" somewhat ambiguously, but the current convention, per   (KRZhl), seems to be to ignore that. Jc86035's alternate account (talk) 09:12, 2 June 2018 (UTC)

The files
Current Should be
  (exhKRZWaq) exWKRZhl
  (exhKRZWeq) exWKRZhr
  (exhKRZWq) exWKRZh
  (extKRZWq) exWKRZt
  (hKRZWaq) WKRZhl
  (hKRZWeq) WKRZhr
  (hKRZWq) WKRZh
  (hdKRZWq) hdKRZWq
  (tKRZWq) WKRZt
  (tKRZWq red) WKRZt red
  (uexhKRZWaq) uexWKRZhl
  (uexhKRZWeq) uexWKRZhr
  (uexhKRZWq) uexWKRZh
  (uextKRZWq) uexWKRZt
  (uhKRZWaq) uWKRZhl
  (uhKRZWeq) uWKRZhr
  (uhKRZWq) uWKRZh
  (uhdKRZWq) uhdKRZWq
  (utKRZWq) uWKRZt

Another CPIC renaming scheme[edit]

Since the last one was more than a year ago, I'd like to propose that all CPICs become XBHF, all CPICAs become XACC, and so on. There are currently no BSicon roots (or BSicons) beginning with uppercase X. (Alternately uppercase I could be used.)

  •   (heCPICl)hXBHF-Le
  •   (CPICAa)XACC-Rq
  •   (CPICKl)KXBHF-Feq
  •   (utCPICCCle)utXBHF-Lef
  •   (xCPICma)KXBHF-Mxa
  •   (CPICqq)XPT*
  •   (CPIClg)XPT+r*
  •   (CPICdd)XPTe*
  •   (CPICpassu)STR+XPTq*
  •   (uexCPICpasso)XPTq+uexSTR*
  •   (CPTa)TXPTa

XBHF etc. would use standard -L/-M/-R/q/xa/xe suffixes instead of the current l/m/r/(a and e)/(x prefix + a)/(x prefix + e).   (tCPICCCle) would probably become tXBHFCC-Le or something like that until we decide on how to rename the KBHFCC icons. Jc86035 (talk) 10:19, 9 January 2018 (UTC)

* It just so happens that   (CPICqq) is about the same width as   (BSm), so PT could be reused if we want to rename the platforms as well. Jc86035 (talk) 10:19, 9 January 2018 (UTC)

  • I do like this idea. Seems to be the way to go, and the current state of affairs is a mess. -- Tuválkin 07:07, 10 January 2018 (UTC)
  • As the one who started the CPIC mess, I approve these changes. -- Sameboat - 同舟 (talk · contri.) 03:03, 11 January 2018 (UTC)

@Tuvalkin, Sameboat: ✓ Done (about 511 icons renamed). Outstanding issues include suffix order of -L/-R/-F/-G vs. a/e (I think it would be more correct to swap the suffix order for all of the terminal station icons) and whether   (exXBHFSHI1lr-M) needs to have an extra e/x in the middle (I don't think so, since it would be confusing and this particular icon can be split into parallel lines, but others may think it needs to). Jc86035 (talk) 10:23, 28 April 2018 (UTC)

Crossings?[edit]

@Useddenim, Tuvalkin: Could   (uCROSS),   (gSKRZ-YuEnd) and other similar icons be converted into a standard set of crossings? I would probably assign a suffix to indicate that a line has a break, perhaps uCROSS → ugKRZB (or another suffix).

The issue of assigning more capital prefixes and suffixes is that at some point they'll end up conflicting with roots (there's already DST = embankment + road crossing railway, although this doesn't exist and should be extremely rare), so it could be time to expand into Unicode. Jc86035 (talk) 11:15, 25 February 2018 (UTC)

@Jc86035, Bob1960evens, Zin92::
  • Converting: I’m all for homogenizing the filenames, but it’s better to first ascertain what are these icons being used for. If it’s mere crossing and the gap is only a visual aid, then they should be redrawn to match all the standard crossings like   (mKRZo), or even   (mKRZ), and renamed trivially. If the gap is meaningful (filled up canal with road running across), then a renaming is in order but also a homogenous redrawing. (For the latter I suggest something like BSicon .svgBSicon STRq.svgBSicon lENDE@F.svgBSicon lENDE@G.svg , which doesn’t include the crossed line — reducing the number of needed icons.)
  • Renaming: I agree with adding an uppercase prefix or suffix. The ambiguity issue raised above can be solved (or significantly reduced) if all icon roots are made of exactly three letters (not two, not four). Unicode (meaning non-ASCII Unicode) is a possibility, but seeing how people still have difficulties with "Ü" as if this was the 1970s, we should be wise to avoid more of these.
-- Tuválkin 12:48, 25 February 2018 (UTC)
@Tuvalkin: I agree with your points, though an issue with using lENDEf/g might be if two of the icons are used in a row. Renaming CONT, ENDE, SHI(1–4), etc. might be seen as unnecessary but since almost no one took notice of the proposed wide-ranging CPIC renaming above (and I advertised it in multiple locations on enwiki), it might not really be an issue. Jc86035 (talk) 05:28, 26 February 2018 (UTC)
  • Used in a row, good point. It would look bad, indeed. -- Tuválkin 02:51, 9 April 2018 (UTC)
current suggested
  (uCROSS)   (umgGAP)
  (gSKRZ-YuEnd)   (gGAPSRYq)
  • Okay, both have been redrawn. Lets go back to a renaming discussion: I think we can agree that this kind of crossing (or rather, a non-crossing!) is distinctive enough to have its own iconID. While akin to bridges and regular crossings (and even though it’s likely that there will be a much smaller number of icons involved here), in this feature the “broken” line should be always secondary, so there’s synonimity issues concerning u/o vs. -/q. For the icon ID I suggest GAP, a nice descriptive 3-letter word, even if it’s not German. -- Tuválkin 15:32, 29 April 2018 (UTC)
current suggested
  (uCROSS)   (gGAPq+uSTR)
  (gSKRZ-YuEnd)   (gGAP+RYq)
  • New idea: The gap is the feature, and it can even be standalone — compare   (GAP) and   (GAPq). An unbroken line may go through the gap as an overlaid   (STRq) (or   (STR)), either in a diagram or as a new icon — see the 2nd table. -- Tuválkin 16:10, 29 April 2018 (UTC)
  • No need for a “GAX”, either… -- Tuválkin 16:10, 29 April 2018 (UTC)
@Tuvalkin: ENDEea (from   (tSTRea) = tSTReg + tSTRaf; ENDEea would be equivalent to ENDEe@G + ENDEa@F under new schema)? Jc86035 (talk) 17:19, 29 April 2018 (UTC)

Beta what?[edit]

@Jc86035: I came across   (hvSTR3- β) and   (hv-STR+1 β), wich were moved from the more usual   (hvSTR3-) and   (hv-STR+1) two years ago; the redirects were deleted recently. What’s this? -- Tuválkin 20:08, 6 April 2018 (UTC)

I say "Just move them back". Useddenim (talk) 11:57, 7 April 2018 (UTC)
@Useddenim, Tuvalkin: This was because of   (hv-STR3 β), which I renamed last September so I could upload   (hv-STR3). Since the geometry type is probably never going to be used (predating YLSS's 2014 geometry change), and the filenames were both valid under the current naming conventions, I moved the other two as well in case someone wants to upload the icons. In the current naming scheme the icons for the curve in the ptwiki diagram would probably be hvSTR3, hvSTR3+L, hvSTR3+R, hvSTR+1, hvSTR+1+L, hvSTR+1+R, and two masks. Jc86035's alternate account (talk) 13:13, 7 April 2018 (UTC)
@Jc86035 (1): Thanks for explaining. Lets rename those icons properly, then? The fact that they are used in a diagram should be proof that they are needed. -- Tuválkin 02:49, 9 April 2018 (UTC)
@Tuvalkin: It turns out that with the proposed/de facto use of ~L and ~R (see #Suffixes and #Tildes) they all have perfectly valid names under the current system, so I've renamed all of them. They still need to be reuploaded (for narrow formations and 117.85px parallel lines spacing). Jc86035 (talk) 12:06, 29 April 2018 (UTC)

Suffixes[edit]

@Useddenim, Tuvalkin, Sameboat, Lost on Belmont, Newfraferz87: @Axpde, C21H22N2O2: I spent some time thinking about how to separate the various meanings of L, R, F and G suffixes, and this is what I came up with. It's not perfect, and the suffixes could be changed to clearer or more readable ones, but I think it's better than the somewhat arbitrary mess that we currently have. There are almost 100,000 BSicons now (of which almost all have fairly simple names and are validly named to be consistent with current naming conventions), and the current system does limit us in terms of the combinations of features that an icon can have, and how specific the suffixes can be. This would solve various issues, such as   (hSTR-R) vs.   (uhSHI1+l-R), and the myriad naming issues in finding a good name for   (uhBHFrf) which is consistent with other icons.

  • l, r: curves (STRl)
  • f, g: forward and backward arrow indicators (STRf)
  • L, R, F, G: reserved for prefixes
  • +L, +R, +F, +G: full transform of the icon boundaries in the respective direction (hvSTRa+L) [No pattern] [NOT AFFECTED BY PARALLEL LINES SYNTAX]
  • +l, +r, +f, +g: line connecting from respective direction (STR+l) [Pattern: +lf]
  • ~L, ~R, ~F, ~G: transform all objects from centre of icon to respective icon boundary (lBHF~F, currently lBHFf) [Pattern: ~LF] [NOT AFFECTED BY PARALLEL LINES SYNTAX]
  • ~l, ~r, ~f, ~g: only this side of the primary object(s) is shown (vSTR2~l, currently vSTR2-L / utvSTRa@g~g, currently utlvSTRag) [Pattern: ~lf (¾) or ~l~f (¼)]
    • A halved track is STR~ or ~STR. Somehow, this magically avoids naming conflicts.
  • @L, @R, @F, @G: transform secondary object(s) in respective direction relative to the line or other primary object (lvINT@F-, currently lvINT~f-) [Pattern: @LF]
  • @l, @r, @f, @g: transform auxiliary object(s) in respective direction relative to the line or other primary object (tSTR2a@f, currently tSTR2af / tBHFa@f, currently tBHFaf) [Pattern: @lf]
  • -L, -R, -F, -G: secondary object connection in respective direction (BHF-L) [Pattern: -LF]
  • -l, -r, -f, -g: auxiliary object connection in respective direction (tSTRa-l, currently tSTRal) [Pattern: -lf]
  • (L), (R), (F), (G): only this side of the secondary object(s) is shown (BHF(L)f, currently BHFlf / KRZo(L), currently KRZo-L) [Pattern: (LF) (¾) or (L)(F) (¼)]
  • (l), (r), (f), (g): only this side of the auxiliary object(s) is shown (lhSTR(l), currently lhSTR-L) [Pattern: (lf) (¾) or (l)(f) (¼)]

A somewhat related issue is that icons like   (KBHF-La) would probably appear to have an incorrect suffix order, especially after renaming a bunch of others, and might need to be renamed to KBHFa-L. Maybe this should be done. I'm not sure. Thoughts? Jc86035 (talk) 06:29, 27 April 2018 (UTC)

  • I'm strictly against those "~" or "@" suffixes, because the icon names should be understandable by general public! The names have become incomprehensible enough, so please no more confusion :-( a×pdeHello! 08:44, 28 April 2018 (UTC)
And Your example   (KBHF-La) should indeed be KBHFa-L :-) a×pdeHello! 08:45, 28 April 2018 (UTC)
  • @Axpde: Do you have any better suffix suggestions? There are already icons using ~L and ~R suffixes, and I don't see how they are less comprehensible than -L or -R. I suppose we could use suffixes like .L/.R or ,l/,r instead? Jc86035 (talk) 09:25, 28 April 2018 (UTC)
  • I’m still processing all this, but I like it so far, very much. -- Tuválkin 13:57, 29 April 2018 (UTC)
Connector
Suffix
L R F G l r f g (none)
  (none)

not used

l/r: curves   (STRl)

regular icons

f/g: directionals   (STRf)
+ transforms icon in direction   (hvSTRa+L) connects from direction   (STR+l)

not used

~ transform objects from centre to boundary   (lBHF~F) half of primary object   (vSTR2~l)
  (utvSTRa@g~g)
halved track   (uSTR~)
@ transforms secondary in direction wrt line/primary   (lvINT@F-) transforms auxiliary in direction wrt line/primary   (tSTR2a@f)
  (tBHFa@f)

not used

- secondary connects in direction   (BHF-L) auxiliary connects in direction   (tSTRa-l) single parallel line   (vSTR-)
( ) only part of secondary shown   (BHF(L)f)
  (KRZo(Ll))
only part of auxiliary shown   (lhSTR(l))

not used

Useddenim (talk) 01:37, 30 April 2018 (UTC)

@Useddenim: By "halved track" I meant something like half of   (mSTR yellow~exteal), specifically for situations like   (uehbnvÜSTl) where currently the narrow track has to shift back to the centre even though the icon is paired with   (uehbnvSHI4gr). Now I'm not sure whether this means objects on the track would be halved [edit: they probably wouldn't, since this schema also includes suffixes for that purpose]. Jc86035's alternate account (talk) 15:02, 2 May 2018 (UTC)
Wouldn't ICON~nothing mean “halved icon”, as in   (uBHF~)? Useddenim (talk) 17:48, 3 May 2018 (UTC)
@Useddenim: I thought it would work like that at first, but we might also want to have, for example, a station centred on the half of the line, and it wouldn't make sense for ~HST on its own in a diagram to have half of a station circle; or we might want to extend the system logically for e.g. mINT u~grey~orange with the lines being 150px wide in total (allowing this would in turn require something like a mSHI.2+r u~grey to shift the driver's rightmost two lines back to the middle, and then we would probably have to extend SHI to diagonals). Jc86035's alternate account (talk) 08:15, 4 May 2018 (UTC)

45° junctions[edit]

@Useddenim, Tuvalkin, Epicgenius, Axpde:

Current Proposed
  (ABZq+1) etc. ABZq1
  (ABZq3) etc. ABZq+3

Can we do this? This is primarily because

  • +1 currently doesn't indicate which side of the icon the line from the corner goes to, but +1 in   (ABZg+1) does;
  • ABZg1 is currently a valid name and would be   (STR1) +   (STR), whereas ABZq1 is currently undefined, and if it were made to be   (STRl+1) +   (STRq) the logic wouldn't make much sense (since it would still be coming from the back of the icon).

It's also fairly clear now that

  • the naming rules for 90° ABZs are separate (i.e. g+4/q+4 curves are different; g+r/q+r curves are the same, so logic would be inconsistent anyway) and can be ignored for this;
  • "q" specifically means "rotated 90° anticlockwise" per   (STRfq), so it would be fairly logical to allow +3 to be used here to mean "[down the line, which is now towards the left] from 3".

Jc86035 (talk) 10:50, 29 April 2018 (UTC)

  • I fully Symbol keep vote.svg agree, both with the proposed renamings and with the underlying argument. -- Tuválkin 13:53, 29 April 2018 (UTC)
  • I also Symbol keep vote.svg agree. Are we changing the names for   (ABZq+4) and   (ABZq2)? I should think not - if the rotation is 90 degrees counterclockwise, then the "front" of the   (STRq) is on the left - but I want to know anyway. epicgenius (talk) 14:16, 29 April 2018 (UTC)
    @Epicgenius: No; those would be unchanged under the proposed logic. Jc86035 (talk) 14:20, 29 April 2018 (UTC)
    @Jc86035: Thanks. epicgenius (talk) 14:21, 29 April 2018 (UTC)
  • Symbol keep vote.svg agreed Vunz (talk) 13:20, 30 April 2018 (UTC)
  • Symbol keep vote.svg Mild agree. However, just make sure there isn't a repeat of the CONTl/CONTr debacle. Useddenim (talk) 23:33, 29 April 2018 (UTC)
  • Symbol delete vote.svg Disagree The icons are perpectly named!   (ABZq+1) means track running across (q) and from corner 1 (+1). Your silly "rule" to rotate BSicons in a certain direction makes them uncomprehensible! Please stop your trials to fix things which aren't broken! a×pdeHello! 15:35, 30 April 2018 (UTC)
    @Axpde: How can you say they're already perfectly named? In the context I agree they're not problematic right now (if that's what you mean), but there's no harm in making the names better. There's obviously work to be done even on the ABZ root, given that there are still zigzag and wye icons which are named idiosyncratically.   (ABZ3+1lr) is fairly obviously wrong, since that name for an icon created now would be BSicon .svgBSicon STR3+r.svgBSicon ABZ3+1l.svg . Changing the way that the "q" suffix is defined here is something that would help us in renaming those icons and creating new ones which aren't limited by the current system (for example, that zigzag icon might be called ABZ(3+1)l+r or ABZl3+1r or ABXql+r, and this would build upon the redefinition of "q"). Jc86035's alternate account (talk) 11:30, 2 May 2018 (UTC)
    Didn't claim all BSicons are perfektly named,   (ABZ3+1lr) shoulde be   (ABZr3+1l)! a×pdeHello! 14:30, 2 May 2018 (UTC)

✓ Done Jc86035 (talk) 11:35, 20 May 2018 (UTC)

Flyovers[edit]

@Useddenim, Tuvalkin, Vunz, Epicgenius: Since the duplicates in this category have two different and currently valid naming schemas:

Current Proposed
  (vÜWBl) ✓
  (vÜWBr) ✓
  (exvÜWBg+l) exvÜWBr+r
  (exvÜWBg+r) exvÜWBl+l
  (exvÜWBgl) exvÜWBl+r
  (exvÜWBgr) exvÜWBr+l
  (vÜWBg+l)
  (vÜWBor+r)
vÜWBr+r
  (vÜWBg+r)
  (vÜWBol+l)
vÜWBl+l
  (vÜWBgl)
  (vÜWBol+r)
vÜWBl+r
  (vÜWBgr)
  (vÜWBor+l)
vÜWBr+l
  (vÜWBol+lr) vÜWBl+lr
  (vÜWBor+lr) vÜWBr+lr
  (uvÜWBol+lr) uvÜWBl+lr
  (uvÜWBor+lr) uvÜWBr+lr
Crosses over to left
vÜWBl
Crosses over to right
vÜWBr
No lines through   (vÜWBl)   (vÜWBr)
Left line through +l   (vÜWBl+l)   (vÜWBr+l)
Right line through +r   (vÜWBl+r)   (vÜWBr+r)
Both lines through +lr   (vÜWBl+lr)   (vÜWBr+lr)

The icons are still restricted by the naming pattern to down the page/across the page orientations, although I don't think this is too much of an issue right now. Jc86035 (talk) 12:53, 19 May 2018 (UTC)

  • What’s the problem with across-oriented versions of these?
e.g.:   (vÜWBol+r)  q̿    (vÜWBol+rq)
No problem! -- Tuválkin 00:44, 21 May 2018 (UTC)
@Tuvalkin: I was referring to using 45° and other curves. Jc86035 (talk) 04:54, 21 May 2018 (UTC)
  • Aha, gotcha. We’re cool, then. -- Tuválkin 12:59, 2 June 2018 (UTC)

✓ Done Jc86035 (talk) 12:11, 17 June 2018 (UTC)

Fill icons[edit]

So I just uploaded   (FILL2),   (FILL3), and   (FILL4) (complementing   (FILL)) so that there will be more fill icons. They are based off Wikipedia templates en:w:Template:Maybe, en:w:Template:Yes, and en:w:Template:Operational respectively. Is there a particular naming convention I should have followed? epicgenius (talk) 20:03, 26 May 2018 (UTC)

  • I would have gone with   (FILLy),   (FILLg),   (FILLb) and   (FILLr) (as with coloured roads). Useddenim (talk) 06:37, 27 May 2018 (UTC)
  • @Epicgenius: But why? -- Tuválkin 12:59, 2 June 2018 (UTC)
    • @Tuvalkin: I needed more than one fill icon for en:Template:NYP track map. However, the map no longer uses these icons. Jc86035 updated the local Routemap template so that individual cells may have background colors. epicgenius (talk) 14:45, 2 June 2018 (UTC)
      • (To clarify, I added this functionality about two years ago, although the documentation does not currently make it obvious that the functionality exists, as there is no example diagram which contains the cell formatting. Jc86035's alternate account (talk) 17:14, 2 June 2018 (UTC))

Ideas[edit]

@Useddenim, Tuvalkin:

  1. Since we now have an established model for referring to secondary and auxiliary objects, I thought it might be useful to expand it. Apostrophes (and maybe quote marks) could be used as "prime" marks for icons with more than one auxiliary object, to indicate that a prefix or suffix referring to an auxiliary object refers to the second or third auxiliary object.
    • For example, to fix the suffix ambiguity of using l and r to indicate bridge start/end as well as curves in crossings, treating the two formations as separate objects,   (hSKRZ-G2hlu) could be renamed hSKRZ-G2hua' (not sure about the suffix order right now; I changed it to this ordering from an incorrect ordering because it would alleviate the aforementioned issue). This is not particularly intuitive, but   (KRZhl) would then be just   (KRZha) since there is only one bridge to which a can be applied (it can't be used for the tracks since the K suffix would be needed for it to indicate the start of a track).
    • This could also be used in other icons where there are multiple formations or structures.
    •   (hdKRZ) and   (dKRZmu) should be consistently named. Perhaps a suffix could be applied to indicate that the bridge formation is narrow. n' is a possibility (n on its own would refer to the line across – it's the secondary object, but I don't know if that matters).
  2.   (ABZ3+1lr) and similar icons have a nonstandard naming structure right now. Maybe the grave accent ` (or some other character like the comma) could be used as a separator between regular positional suffixes (e.g. 3+1 in   (STR3+1)) and specific positional suffixes (e.g. +l in   (WSL+l)).
    • ABZ3+1`r+l (or ABZ3+1,r+l), for the aforementioned ABZ3+1lr, would indicate 3+1 to be the "main track", and r and +l to be "curve from back [1] to r" and "curve to front [3] from l".
    • vÜWB2+r`l+r (or vÜWB2+r,l+r), obviously a hypothetical example, would indicate 2 and r to be the tracks' end and start points, with l+r being similar to the curves in   (vÜWBl+r). The real icon would pose some very odd geometry issues, but SHI and ÜST icons could definitely benefit from this.
  3. Currently exSTRq-BHFq is ambiguous. Using the grave accent (or some other character like the comma) in front of prefixes which are used before d's position, to separate the prefixes where d would be, could be a solution to the ambiguity.
    • extBHFq-BHFq indicates that both stations are out of use.
    • t`exBHFq-BHFq (or t,exBHFq-BHFq) would indicate only the upper station to be out of use. (This doesn't necessarily have to be done, but the suffixes being out of order might not be a very clear signifier.)
    • ex`tBHFq-BHFq (or ex,tBHFq-BHFq) would indicate the upper line to be in tunnel.
    • tBHFq-exBHFq indicates that the lower station is out of use, and that both lines are in tunnel.
    • `tBHFq-exBHFq (or ,tBHFq-exBHFq) would indicate the lower line to be out of use, and the upper line to be in tunnel.
  4. Things that have nothing to do with renaming:
    • How are tunnels affected by the ~L/~R/~F/~G suffixes? Are the dashes transformed, or do they line up correctly? A set of misaligned dashes (with connecting icons) would actually be somewhat useful, because then we would be able to have a   (tdSTRq) that doesn't make diagrams look weird.
    • There should be a standardized way to draw unpaired tunnel dashes, like those in   (utPSLa). It would be much easier to keep tSTR~ undefined, really, because having it opens the door to icons like tSHI.01l~ (or something like that) where the line moves from 220px to 225px, and would probably lead to a very unnecessary rabbit hole. However, it would be useful for the "track change" icons, so I would keep the connecting parts at 220px/280px but have the rest of the points at their positions in the at-grade icons.

(Please reply using the indents :#, ::#, …, if using lists within the reply.) Jc86035's alternate account (talk) 11:12, 2 June 2018 (UTC)

  • You’re supposed to be on a break, man!… Okay, I’m “processing” it in the back of my mind. Will comment later. Busy now. -- Tuválkin 13:15, 2 June 2018 (UTC)
    I'd written out most of the ideas beforehand, although it took me longer than I expected to formulate them into coherent and understandable English. Jc86035's alternate account (talk) 14:03, 2 June 2018 (UTC)

Double-stripe tracks[edit]

@Useddenim: Why rename   (mtSTR+1 red+blue)? Using + instead of ~ causes naming conflicts for stations;   (uemBHF). (A character other than ~ should probably be used due to the {{Routemap}} character restrictions, although I don't know what to replace it with.) Jc86035 (talk) 14:26, 29 June 2018 (UTC)

That was a mistake. I stopped renaming the color~colour icons before I got to   (mtBHF red~blue) &   (mtBHF+1 red~blue), but I couldn't undo the change to   (mtSTR+1 red~blue),   (mtSTR3+1 red~blue) &   (mINT-L green~yellow). On the other hand, using ~ as the connector dovetails perfectly with its use for lower-case suffixes: “half of primary object”. Useddenim (talk) 22:11, 29 June 2018 (UTC)
@Useddenim: I've renamed them all back. Jc86035 (talk) 22:17, 29 June 2018 (UTC)

Parallel lines across[edit]

@Useddenim, Tuvalkin, Epicgenius: Following on from the block of text I posted a while ago, do you have a preference for any of these? It should probably be resolved at some point.

  1. Grave accent; ` (or some other character) goes where v would be in cases where the icon name is ambiguous
    •   (`exSTR+ro-STRr)
    • BSicon .svgBSicon -BHFq.svgBSicon exDSTq-.svg (`exDSTq-BHFq) 
  2. Creation of ~q suffix; same as q but it can only apply to all of a parallel lines block and not its components, similarly to the other new tilde suffixes
    •   (vSTRl-exSTRro~q)
    • BSicon .svgBSicon -BHFq.svgBSicon exDSTq-.svg (vBHF-exDST~q) 
  3. Status quo; standard-width icons cannot contain transverse parallel lines with two roots without naming restrictions
    •   (STR+xro-STRr)
    • BSicon .svgBSicon -BHFq.svgBSicon exDSTq-.svg (exDSTq-+-BHFq) 

I think I prefer the first option, since it doesn't necessitate the rotation of curves. —Jc86035 (talk) 16:11, 7 July 2018 (UTC)

I would suggest Option 1, but use ^ (the caret symbol, Shift+6 on US keyboards) as the inverse of v. Useddenim (talk) 00:15, 8 July 2018 (UTC)
@Useddenim: I think using the caret sounds better (I haven't updated my comment to reflect this). Should the caret always be used, or only be used for ambiguous cases, or somewhere in between? I would probably only choose "always" (i.e. ^-STRq) or "as little as possible". Jc86035 (talk) 03:30, 8 July 2018 (UTC)
Apply the KISS principle: therefore, as little as possible/only as necessary. Useddenim (talk) 12:23, 8 July 2018 (UTC)
I suppose Option 1 works as well since it's concise. epicgenius (talk) 12:26, 8 July 2018 (UTC)
[e] [x] ex
vSTRq        
DSTq-BHFq BSicon .svgBSicon -BHFq.svgBSicon DSTq-.svg 
DSTq-BHFq
BSicon .svgBSicon ex-BHFq.svgBSicon DSTq-.svg 
DSTq-exBHFq
BSicon .svgBSicon -BHFq.svgBSicon exDSTq-.svg 
^exDSTq-BHFq
BSicon .svgBSicon -BHFq.svgBSicon exDSTq-.svg 
exDSTq-BHFq
t [et] [xt] ext
tvSTRq        
tDSTq-BHFq BSicon .svgBSicon t-BHFq.svgBSicon tDSTq-.svg 
tDSTq-BHFq
BSicon .svgBSicon ext-BHFq.svgBSicon tDSTq-.svg 
tDSTq-exBHFq
BSicon .svgBSicon t-BHFq.svgBSicon extDSTq-.svg 
t^exDSTq-BHFq
BSicon .svgBSicon ext-BHFq.svgBSicon extDSTq-.svg 
extDSTq-BHFq

@Useddenim, Epicgenius: t^exDSTq-BHFq or texDSTq-BHFq? The suffix order makes the latter distinguishable, although it's still somewhat ambiguous. (Obviously this layout would be incorrect in a real table because of e in e.g. evBHF modifying the station rather than one of the tracks, but you get the idea.) Jc86035 (talk) 13:47, 8 July 2018 (UTC)

Wouldn't the prefix be ext, rather than tex? In any case, I'd rather go with t^ex to avoid confusion. epicgenius (talk) 13:50, 8 July 2018 (UTC)
@Epicgenius: No, the ex only modifies the DST. Compare   (vexBHF-DST) and   (exvBHF-DST). Jc86035 (talk) 13:53, 8 July 2018 (UTC)
OK, I get it now. In your example, it's v (entire icon) plus exBHF (left) plus DST (right) for the first icon; as opposed to exv (entire icon) plus BHF (left) plus DST (right) on the second icon. epicgenius (talk) 13:56, 8 July 2018 (UTC)
Now that I've added visual examples to the table, I endorse this proposal wholeheartedly. In fact, using the ^ now reads (to me) as "up, then down"… Useddenim (talk) 16:12, 8 July 2018 (UTC)

  • (Edit conflict) I must be incredibly stupid but I still cannot understand what the problem is. What’s the in the way of naming vFOOq the 90° anticlockwise rotation of vFOO, for any imaginable (square*) FOO? *(I can see the fundamental difference between these two types of icons in that diagrams are contructed with rows, not columns, but that dosn’t invalidate the overall approach.) -- Tuválkin 14:00, 8 July 2018 (UTC)
    @Tuvalkin: This is actually quite a good point, because now we have @f and @g and we can use those instead of abusing the horizontal parallel lines syntax. However, eliminating the horizontal "shorthand" style would still be more confusing and I would probably not like it, because   (-STRl+4) would become vSTR+1-q. As far as I can tell (correct me if I'm wrong) there was some sort of consensus for doing this, according to Talk:BSicon/Renaming/Archive 5#Parallel lines across, and because we don't have any rotated curves (excluding shifts and the 3-curves which are named as though they are straight tracks) it's probably better to keep the horizontal parallel lines syntax. Jc86035 (talk) 14:29, 8 July 2018 (UTC)

Roads[edit]

@Useddenim, Tuvalkin, Epicgenius: Module:BSicon has informed me, by throwing an error on the 55 files I uploaded with a title containing RR, that I've accidentally created a naming conflict issue by allowing the modifier suffixes to be combined:   (RR) is a valid root, as are   (RG) and   (TRR). Should we do anything about this? There are only about 90 TRR, RG and RR icons combined, so one option would be to rename all of those icons. Jc86035 (talk) 18:54, 11 July 2018 (UTC)

  • The road icons are the ones that should be renamed, in my opinion. -- Tuválkin 21:19, 11 July 2018 (UTC)
@Jc86035: Aside from the fact that this is a case of “You broke it; you fix it”, I’m still trying to figure out what the -~LL and -~RR suffixes are supposed to mean. I think you need to expand the explanatory table to help us all with the compound suffixes that you’re now introducing. But I agree with Tuvalkin that the red and green roads can be renamed; but what would you propose for the Traverser/Transfer table icons? Useddenim (talk) 23:22, 11 July 2018 (UTC)
@Jc86035: Out of curiosity, what do these conflict with? epicgenius (talk) 00:47, 12 July 2018 (UTC)
@Epicgenius, Useddenim:   (hv-STR+1~RR), among others. I did this because the +L/+R suffixes were made redundant by extending the tilde suffixes to ~RR/~LL respectively (same for F/G), and it would be more confusing to have some of the transform suffixes go the wrong way.   (hdSTRr+1-)  (hdSTRr+1-~F)  (hdSTRr+1-~FF). It would already have happened earlier because I renamed the KBF icons to   (uBHF+r@GG) (metro big station on curve from right with station moved back twice) and so on. Jc86035 (talk) 04:55, 12 July 2018 (UTC)
I reused the + suffixes for the old-style formations that are perfectly against the icon edge (leer+hl  (lhSTR+L)). Jc86035 (talk) 05:14, 12 July 2018 (UTC)
TRR could become TRV. RG and RR could use some other arbitrary letter, although A, B, D, E, M, P and Y are taken, and we probably shouldn't use something which is already an affix (A, C, D, F, G, K, L, M, R, S, T, W, X). Alternately, we could change all the roads to use three-character roots to avoid syntactical problems which were bound to come up at some point. Jc86035 (talk) 05:27, 12 July 2018 (UTC)
Suggestion:
Existing   (RD1)   (RP1)   (RP2)   (RP4)
Proposed   (RPH)*
(RA)
  (exRPH)*
(RM)
  (RPB)
(RB)
  (RPR)
(RR)
  (RPG)
(RG)
  (RPWq)
(REq)
  (RPYq)
(RYq)
* H = Highway – Useddenim (talk) 12:20, 12 July 2018 (UTC)
  • I could go with Useddenim's suggestion, since it still uses the root "RP". epicgenius (talk) 12:31, 12 July 2018 (UTC)
@Useddenim: I was actually thinking about renaming RP[1-4] before this, since it's not a logical sequence (RP4 should logically have three dashed lines). [Like this:BSicon .svgBSicon RP4.svgBSicon RP2.svg (RP2RP4) ?Useddenim (talk) 16:52, 12 July 2018 (UTC)] Perhaps
  • RD → RPD
  • RP1 → RPS ("unclassified" / "single")
  • RP2 → RPP ("paved" / "painted")
  • RP4 → RPV ("divided")
and then (3), (3,2) could be optionally used for indicating lane numbers for P and V respectively, and (2,1-1,2) could be used to indicate transitions like   (RP2112). (There's a possibility that someone might want more than nine lanes, although if there's no road in the world which is that wide then I'd be fine with not having the punctuation. However, if we don't want to have some other sort of standard delimiter, the brackets might still be useful to avoid the usual naming conflicts.) Jc86035 (talk) 13:06, 12 July 2018 (UTC)
@Jc86035: I dislike the idea of using parentheses ( ) in icon names because it is two characters whereas all other delimiters are one and also that it’s easy to omit the closing ). Instead, I would suggest a semicolon ;– because we can’t use colons in file names – and commas to separate lane numbers. Then your examples above would become RPP;3, RPV;3,2, etc. Useddenim (talk) 16:52, 12 July 2018 (UTC)
@Useddenim: Another delimiter (` in sections above) would be needed to disambiguate all of the curves. Jc86035 (talk) 16:54, 12 July 2018 (UTC)
@Jc86035: Wouldn't ROOTgeometry;lanes be sufficient? Useddenim (talk) 23:17, 12 July 2018 (UTC)
@Useddenim: I think it would work, although I would want it to be consistent with naming for other icons like   (vÜSTr3+1) and the road crossings where the primary track geometry is indicated at the end of the name. Jc86035 (talk) 04:50, 13 July 2018 (UTC)
Worry about that when (if) it happens. Useddenim (talk) 11:36, 13 July 2018 (UTC)
@Useddenim: But it already exists, doesn't it? Just because   (hSKRZ-G13+1) and   (vÜSTr3+1) are conveniently named doesn't mean we shouldn't sort out the rest of it in a logical way. (It's also somewhat likely that if we figure it out and create a massive table full of nonexistent files that someone is eventually going to try and fill all the cells.) Jc86035 (talk) 04:07, 14 July 2018 (UTC)

ZOLLs and water crossings[edit]

@Newfraferz87: Welcome back. A lot has happened; for example, we now have about ten new suffixes, and the W affix is now supposed to always work like L; i.e.   (WABZgl) and   (hKRZW). This probably makes things more difficult but is more logical. I've renamed e.g.   (hKWZOLLaxe) to TKZOLLWxeo (no conflict with formations a/e because of K prefix).

Thanks :) So the position of the W now follows the orientation of the waterway. However, this implies a conflict with   (hWHSTae),   (hWDSTae) etc., which I named hWZOLLae after (it is now   (TZOLLWo)). Would there be a standardization for the stations as well?   ~ Newfitz Yo! 08:18, 16 July 2018 (UTC)
@Newfraferz87: Yes, but no one's gotten to them (incidentally, I also wrote BSicon/Guide for doing things to a lot of icons). I believe   (hWHSTae) should be hTHSTWae, but as for the others it's not clear to me whether they're actually elevated. There is also a conflict with   (hKRZWaq), which I accidentally batch-renamed without having removed the q. I'm not sure if that icon should be WKRZhr, but I don't want to use that name because the l and r suffixes themselves cause naming conflicts. Jc86035 (talk) 08:27, 16 July 2018 (UTC)

@Useddenim, Tuvalkin: Is it correct to omit the h prefix in   (TZOLLWo), like it is for   (mTBHFo)? Should the formations go around the ZOLL? Jc86035 (talk) 07:53, 16 July 2018 (UTC)

The   (TBHF) prefix+ROOT combination should imply the existence of the elevated structure (but this example doesn't; perhaps it should be renamed to BHFKRZ, similar to   (BHFABZgl+l) etc.). Useddenim (talk) 11:32, 16 July 2018 (UTC)
@Useddenim: (Sorry, I meant to ask if it was correct to replace the h prefix with the o suffix. Which example are you referring to?) Is BHFKRZ necessary? BHFABZ (station around the junction) exists mainly because ABHF means something else (station at or inside the junction), so if T means the same thing for   (TWZOLLu) as it does for   (mTBHFu), then it shouldn't need to be replaced. Jc86035 (talk) 11:39, 16 July 2018 (UTC)

@Useddenim, Tuvalkin, Newfraferz87: Is it possible to reconcile the suffix naming of   (hKZOLLaxe)? It's not really valid right now because of the limitations of the a/e suffixes so I'd probably rename it to something like KSTRxe+lhZOLLae or KZOLLxeo (like   (RBo)). Do you think there's something better? Jc86035 (talk) 13:16, 17 July 2018 (UTC)

Didn't you already find a scheme as in   (TKZOLLWxeo)? ;)
Though honestly I didn't find a good alternative when renaming the first icon from xdnGRENZE+BRÜCKE, but KZOLLxeo seems fine (can't think of any potential conflicts at the moment, though there might well be). The trouble comes if it gets combined with complex bridges like BSicon .svgBSicon hSTRa@g.svgBSicon exKSTRa.svgBSicon lGRENZE.svg  then that would probably really require a combination separating line/bridge & feature.   ~ Newfitz Yo! 13:45, 17 July 2018 (UTC)
@Newfraferz87: If the conflict is resolved, it probably means renaming a few thousand icons, either by replacing the K prefix with some suffix combination, or by replacing a and e with some suffix combinations (probably something like &f/&g/&l/&r). It's doable, and I've renamed a few thousand icons to date, but it would be a bit disruptive and a lot of work just to fix naming conflicts with some icons that don't exist and   (KRZhl). Jc86035 (talk) 16:47, 17 July 2018 (UTC)