Template talk:Track gauge/Archive 3

Edit proposal (named gauges)
Background: the linked-to name should be recognised (e.g., irish). Recognised names should link too (e.g., scot); abbreviations may be written in long form (e.g., provincial).
 * About Named gauges. Here is an overview list of all names used. See the column edit proposal for proposed edit.

-DePiep (talk) 14:53, 13 February 2013 (UTC),
 * More on prov/indian gauge -DePiep (talk) 15:08, 13 February 2013 (UTC)
 * Changes now are in . They are:

This shows the changes. Any remarks? -DePiep (talk) 22:53, 17 February 2013 (UTC) -DePiep (talk) 22:58, 17 February 2013 (UTC)
 * All named gauges (in first column) are in the template two-way: 1. Recognised as input, and 2. When al=on they are linked to.
 * Links are direct (not redirect).
 * See column "edit proposal", and check "/sandbox" column.
 * (The proposal sandbox is temporally not available - will return soon) -DePiep (talk) 11:05, 18 February 2013 (UTC)
 * It is returned now. -DePiep (talk) 00:33, 20 February 2013 (UTC)

Proposal. With named gauges, like "standard gauge", we have two options. 1. Use name as input: &rarr;
 * I propose to add more names that should be recognised as input: scotch, scottish, victoria, victorian, provincial, irish, indian, iberian, toronto.

2. We can show a link to a gauge page, using on on:
 * &rarr;
 * I propose to add these links for all named gauges: scot and the newly addded names (see 1. above).
 * Also, these links should not be a redirect: prov should nopt lead to Provincial gauge (a Redirect), but directly to Indian gauge.

3. "standard gauge" and "metre gauge" should not be capitalised, it is not a proper name. 4. The names should not wrap (especially not in infoboxes). The space right before the name is always open for wrapping, not an NBSP. (see test table, columns are set extra tight to show this). These proposals are in the table. Changes are notes in the "edit proposal" column. The rightmost column shows the sandbox (test) version. -DePiep (talk) 00:33, 20 February 2013 (UTC) Added: "standard gauge" link in lowercase. -DePiep (talk) 09:57, 20 February 2013 (UTC); adding nowrap note -DePiep (talk) 20:37, 21 February 2013 (UTC) adding metre to be lowercase. -DePiep (talk) 10:28, 22 February 2013 (UTC) add Toronto -DePiep (talk) 11:37, 23 February 2013 (UTC)


 * request: please copy all code from RailGauge/sandbox (this version)into RailGauge.
 * Changes are listed and described above. Basically they are additions to an existing practice (more gauge names). RailGauge/testcases. -DePiep (talk) 11:51, 23 February 2013 (UTC)
 * Pictogram voting question.svg Question: This looks very good, and I was about to update the main template, but I noticed in the diff that 925 gauge would be removed. I couldn't see any mention of that change above - is that intentional, and might it break anything? Best — Mr. Stradivarius  ♪ talk ♪ 06:16, 2 March 2013 (UTC)
 * Good catch. Added, to testcases too (Line 925mm was added after I took the source code to the sandbox). The change now looks like: diff. -DePiep (talk) 11:15, 2 March 2013 (UTC)
 * Ok, Yes check.svg Done. I also wrapped the template in includeonly tags so that the error message doesn't appear on the template page. — Mr. Stradivarius  ♪ talk ♪ 12:15, 2 March 2013 (UTC)
 * Thanks. I'll take a look at the /doc and so. -DePiep (talk) 13:50, 2 March 2013 (UTC)
 * See also Template talk:RailGauge below. Peter Horn User talk 23:03, 9 March 2013 (UTC)

Oddball: 38 inch
✅ See Clifton Rocks Railway. It mentions 38 inch (965 mm). (38" calculates nicely to 965.2 mm indeed). To add? -DePiep (talk) 16:26, 25 February 2013 (UTC)
 * Note to any admin adding this one: please first check edit request . Otherwise the elaborate proposal (sandbox) would be made outdated. -DePiep (talk) 16:28, 25 February 2013 (UTC) Resolved. -DePiep (talk) 13:52, 2 March 2013 (UTC)
 * Make that Peter Horn User talk 19:55, 6 March 2013 (UTC)
 * Already in the sandbox: . Some more changes in there, I'll make a list of the proposals here shortly, to discuss. -DePiep (talk) 21:50, 6 March 2013 (UTC)
 * I think that we need to see if the changes made to sandbox are to be deployed before making these changes or we may start to get things out of step. Keith D (talk) 00:43, 10 March 2013 (UTC)
 * This single change is in the sandbox, and tested with visible results. One can oppose or discuss this single addition below. Please point issues you see. -DePiep (talk) 00:53, 10 March 2013 (UTC)

Another modelling gauge
✅ For P4 gauge. Peter Horn User talk 19:36, 6 March 2013 (UTC)
 * Added to the sandbox: . I will check to put metric first. Formal proposal for all sandbox changes to follow here. -DePiep (talk) 22:09, 6 March 2013 (UTC)
 * I think that we need to see if the changes made to sandbox are to be deployed before making these changes or we may start to get things out of step. Keith D (talk) 00:45, 10 March 2013 (UTC)
 * This single change is in the sandbox, and tested with visible results. One can oppose or discuss this single addition below. Please point issues you see. -DePiep (talk) 00:53, 10 March 2013 (UTC)

14 Proposals
I propose the next changes to the template. All these changes are made in the sandbox, and tested. If we agree in this, I'll prepare an "edit protect" request.

{| class=wikitable ! Topic (links to discussion below) !! Change type !! Gauge input !! Settings input !! Current (RailGauge) !! Proposed (RailGauge/sandbox) !! Note
 * + Proposals
 * + Proposals


 * 38 in
 * New entry
 * Brunel
 * Bosnian
 * Add name for gauge
 * Bosnian
 * See also "Imperial"
 * Imperial
 * Add name for gauge
 * Imperial
 * See also "Bosnian"
 * Spaces in input
 * Input friendly
 * 66in
 * When a gauge is repeated in a section or table: we can prevent mentioning the 2nd measure (the conversion) again. Setting  allows us to use exactly the same RG format without repeating the conversion.
 * rowspan=3 | First measure
 * rowspan=3 | Metric or imp first
 * or.
 * 66in
 * 66in
 * rowspan=2 | Wrap breaks
 * rowspan=2 | Define wrap behaviour
 * Indian
 * rowspan=2 | Wrap breaks (re)defined: 1. Never within a single measure (imp, met) 2. Not within a gauge name 3. Allow before gauge name 4. If, allow after the separator (space or /).
 * Indian
 * Imperial
 * See also "Bosnian"
 * Spaces in input
 * Input friendly
 * 66in
 * When a gauge is repeated in a section or table: we can prevent mentioning the 2nd measure (the conversion) again. Setting  allows us to use exactly the same RG format without repeating the conversion.
 * rowspan=3 | First measure
 * rowspan=3 | Metric or imp first
 * or.
 * 66in
 * 66in
 * rowspan=2 | Wrap breaks
 * rowspan=2 | Define wrap behaviour
 * Indian
 * rowspan=2 | Wrap breaks (re)defined: 1. Never within a single measure (imp, met) 2. Not within a gauge name 3. Allow before gauge name 4. If, allow after the separator (space or /).
 * Indian
 * or.
 * 66in
 * 66in
 * rowspan=2 | Wrap breaks
 * rowspan=2 | Define wrap behaviour
 * Indian
 * rowspan=2 | Wrap breaks (re)defined: 1. Never within a single measure (imp, met) 2. Not within a gauge name 3. Allow before gauge name 4. If, allow after the separator (space or /).
 * Indian
 * 66in
 * rowspan=2 | Wrap breaks
 * rowspan=2 | Define wrap behaviour
 * Indian
 * rowspan=2 | Wrap breaks (re)defined: 1. Never within a single measure (imp, met) 2. Not within a gauge name 3. Allow before gauge name 4. If, allow after the separator (space or /).
 * Indian
 * Indian
 * rowspan=2 | Wrap breaks (re)defined: 1. Never within a single measure (imp, met) 2. Not within a gauge name 3. Allow before gauge name 4. If, allow after the separator (space or /).
 * Indian
 * Indian
 * rowspan=2 | Wrap breaks (re)defined: 1. Never within a single measure (imp, met) 2. Not within a gauge name 3. Allow before gauge name 4. If, allow after the separator (space or /).
 * Indian
 * Indian
 * Indian
 * Indian
 * Indian


 * Easier to link
 * Link to named gauge
 * Indian
 * To give the link to the named gauge,  was needed. Now only   is enough (also by logical sense)
 * Unknown gauge: no error
 * Maintenance friendly
 * allows us to use exactly the same RG format without repeating the conversion.
 * To give the link to the named gauge,  was needed. Now only   is enough (also by logical sense)
 * Unknown gauge: no error
 * Maintenance friendly
 * allows us to use exactly the same RG format without repeating the conversion.
 * allows us to use exactly the same RG format without repeating the conversion.
 * allows us to use exactly the same RG format without repeating the conversion.
 * allows us to use exactly the same RG format without repeating the conversion.


 * First measure Metric or imp first. All gauges have a default sequence defined (not changed). We can force a sequence by setting  or.


 * Wrap breaks Wrap breaks are (re)defined: 1. Never within a single measure (imp, met) 2. Not within a gauge name 3. Allow before gauge name 4. If, allow after the separator (space or /).


 * Easier to link Link to named gauge. To give the link to the named gauge,  was needed. Now only   is enough (also by logical sense)


 * Unknown gauge: no error When an unknown gauge is entered, the red error text" does not appear any more. Input is shown as it is. But the page is still listed in the category. This way, the template can stay on the page, and we catch this unknown gauge (page) for improvement.

-DePiep (talk) 14:56, 9 March 2013 (UTC)
 * Template internals Internally, template workings have changed: 1. Pure measure strings (imp, met) are made just once 2. Then a subtemplate "composes" the whole (sequence, wrappings, separator, etc.) into the output. Added parameters dflt1 and first to handle the sequence. Each entry has an "id" value (the gauge in mm) to help checking and sorting. The testcases should prove that the template works as expected.

Pennsylvania

 * Looks OK but there is (are) one (2) missing, i.e. the Pennsylvania Trolley Gauges of and  Peter Horn User talk 22:31, 9 March 2013 (UTC)
 * I will add the name "Pennsylvania" for 62.25in and 62.5in to the proposal (and tests, to be sure).
 * I understand that Pennsylvania input should be recognised (so not the full P.T.G. name is needed for input). But we can have only one input hit: "Pennsylvania" input will show (I say) the 62.25in output. When asked on both inputs 62.25 and 62.5 input will link to the PTG page. -DePiep (talk) 22:54, 9 March 2013 (UTC)
 * See also Template talk:RailGauge above. Peter Horn User talk 23:07, 9 March 2013 (UTC)
 * Peter, what do you mean by this link? -DePiep (talk) 23:53, 9 March 2013 (UTC)
 * See the demo below. If there is anything wrong, maybe a detail, please write. -DePiep (talk) 23:36, 9 March 2013 (UTC)


 * Done, added.
 * It is just an Xreference. Peter Horn User talk 19:55, 10 March 2013 (UTC)

It is in the /sandbox, so it is part of the proposal. Test pages will be informed and changed later on. -DePiep (talk) 23:36, 9 March 2013 (UTC)
 * By the way, shouldn't it be Pennsylvanian gauge, not Pennsylvania, here? -DePiep (talk) 01:12, 10 March 2013 (UTC)
 * I changed it: Pennsylvanian, like Iberian or Russian. done. -DePiep (talk) 01:24, 10 March 2013 (UTC)
 * Changed target page (the redirect) to be more clear: Pennsylvanian trolley gauge. -DePiep (talk) 17:44, 10 March 2013 (UTC)

Edit protect of 15 March 2013

 * Request: Please copy all code from the RailGauge/sandbox (this version) into the template RailGauge.
 * Background. Changes are described in above. Testcases in: RailGauge/testcases and RailGauge/entry check. -DePiep (talk) 11:27, 15 March 2013 (UTC)
 * Yes check.svg Done. Looks like you've been busy! Thanks as always for your meticulous work. — Mr. Stradivarius  ♪ talk ♪ 00:57, 16 March 2013 (UTC)
 * Thanks. Yes, some nice puzzling and testing to do here. -DePiep (talk) 09:38, 16 March 2013 (UTC)

Add three and do template cleanups
I propose the next 3 additions and an input/output cleanup for the template. All is in the RailGauge/sandbox, a demo overview in railGauge/entry check. If we agree, I'll write the edit request. -DePiep (talk) 23:59, 18 March 2013 (UTC)
 * Add gauge entries (new)
 * Concrete sleeper has 1680mm --> sandbox:
 * Polybahn funicular has 955mm --> sandbox:
 * Menaggio–Porlezza railway has 850mm --> sandbox:


 * Add input options (existing gauges)
 * ussg add 4'8.5" -->
 * 0.25in add 0.25 -->
 * 56in add 56" -->
 * 622mm: add |2ft0.5in|2'0.5" -->
 * 613mm 24.125in: add |2ft0.125in|2'0.125" -->


 * Output change
 * show 0.25 not 0.250 in = -->
 * 3in an up: use fractions ($1/16$) not decimals:


 * 450mm = -->
 * 765mm = -->
 * 860mm = -->
 * 1062mm = -->


 * Remove input options
 * Non-intuitive (uncommon) abbrevs


 * removed: oh vic scot prov (full names are available)
 * Unsupported or confusing input formats:


 * 1537mm 60.5: 5ft1/2in 5'1/2" do not use frac here
 * 622mm: remove 2.5ft|2.5' (confusing)
 * 613mm 24.125in: 2.125ft|2.125' (confusing)
 * 406mm 16in: remove option 1.4ft (confusing)
 * 419mm 16.5in: remove option 1.4.5ft (confusing)


 * Uncommon metric input options
 * Not generally supported input formats (we do not do detailed metres, use mm instead):


 * |0.61|0.61m |0.711|0.711m, |0.76|0.76m, |0.838|0.838m, |0.860|0.860m, |0.95|0.95m, |0.965, |1.473|1.473m, |1.664|1.664m, |1.672|1.672m, |1.676|1.676m, |1.88|1.88m, |1.945|1.945m, |2.14|2.14m


 * Note: Whenever an input option is removed, but used on a page: that page will be listed in the maintenance category (unrecognised gauge).


 * Change input options sequence
 * Basic sequence is: 65in (imperial)
 * or: 1435mm (metric)
 * So changed into this sequence (with no visible effect):

-DePiep (talk) 23:59, 18 March 2013 (UTC)
 * 600mm input seq
 * 1600mm input seq
 * 15in input seq
 * 1100mm input seq
 * Template speed
 * Also: high-usage rail gauges (like sg) are moved to the top, to speed up the template. They are
 * sg, ussg, iberian, russian, metre. -DePiep (talk) 18:32, 24 March 2013 (UTC)

Edit request on 24 March 2013
-DePiep (talk) 11:44, 24 March 2013 (UTC)
 * Request: Please copy all code from RailGauge/sandbox (this version) into RailGauge.
 * Background: Changes are described above. Three entries are added, and a cleanup of input options. Testcases are at RailGauge/entry check.
 * Reopened request after improving sandbox. Adjusted "this version" link. -DePiep (talk) 21:12, 24 March 2013 (UTC)
 * Yes check.svg Done. Thanks as always. The template is awfully slow to load, though - have you considered porting it to Lua? I'm still getting my head round all the various technical aspects, but as I understand it mw.loadData has been provided for cases like this one, and using it should provide a big performance increase. — Mr. Stradivarius  ♪ talk ♪ 08:07, 25 March 2013 (UTC)
 * Thx again. Yes, he's very slow. I'll take a look at your suggestion, that is new to me. -DePiep (talk) 08:49, 25 March 2013 (UTC)

Four uncovered gauges
The next four gauges are not in the template. I propose adding them.
 * 1650 mm in Portet-Saint-Simon–Puigcerdà railway (65 in makes 1651 mm)
 * This gauge could use a source.
 * The Spanish wiki says (es:Latour-de-Carol): Latour-de-Carol hacia Puigcerdá y Barcelona (España). Ancho ibérico (1668mm).
 * Which makes more sense to me. 1650 mm probably an error. -DePiep (talk) 12:53, 17 March 2013 (UTC)

-DePiep (talk) 12:46, 17 March 2013 (UTC) - Added sandbox demo. -DePiep (talk) 21:02, 17 March 2013 (UTC)
 * 1680 mm in Concrete sleeper ($x 23/40$ in makes 1680.4 mm)
 * 955 mm in Polybahn funicular ($x 9/16$ in makes 954.9 mm)
 * 850 mm in Menaggio–Porlezza railway ($1/16$ in makes 850.1 mm)
 * Proposed below. -DePiep (talk) 23:59, 18 March 2013 (UTC)
 * ✅, some time ago (see edit request in next section). -DePiep (talk) 09:19, 16 May 2013 (UTC)

disp=or
I have added  to use "or" as a separater e.g.  → "". J IM ptalk·cont 11:14, 18 April 2013 (UTC)
 * Very good. (By the way, how did you manage this without typo? ;-) -DePiep (talk) 20:46, 18 April 2013 (UTC)

Wikidata proposal
See this proposal for Wikidata. -DePiep (talk) 09:37, 16 May 2013 (UTC)

Yet another "oddball"
For Trams in Leipzig / and for Tram track gauge / instead of 1,458 mm. There is no output...yet. Peter Horn User talk 23:51, 20 June 2013 (UTC)
 * One can write: in that page (I just did).
 * Result: 1,458 mm on the page and a note in Category:Pages with incorrect use of RailGauge template (because it was not recognised by the template). One might follow that category: it shoud be empty but for these pages.
 * What inch measure you propose? -DePiep (talk) 00:07, 21 June 2013 (UTC)
 * Say 1,458 mm make that 9$1/16$ or $x 23/40$ in Peter Horn User talk 00:56, 21 June 2013 (UTC)
 * This one should also be inserted int the list. Peter Horn User talk 01:36, 26 June 2013 (UTC)
 * Yes. I am preparing the changes in RailGauge/sandbox, when testing OK I´ll have them put in the live template. DePiep (talk) 13:38, 27 June 2013 (UTC)

✅ -DePiep (talk) 21:48, 4 July 2013 (UTC)

To be inserted into the list
From Sofia Tramway. Peter Horn User talk 01:04, 21 June 2013 (UTC) Peter Horn User talk 01:08, 21 June 2013 (UTC)
 * Looks like it is already in: &rarr; . -DePiep (talk) 10:02, 21 June 2013 (UTC)
 * ...but it should be changed into: 3 ft $x 9/16$ in (calculates to 1008.8563 mm, correct). It was originally defined in metric, so we should calculate the inches; not a nominal inch measure, if I understand it well. -DePiep (talk) 10:16, 21 June 2013 (UTC)
 * Double check 1009 mm 1009 mm or 1.009 m 1.009 m. So it should be corrected, asap, to 3 ft $1/16$. Peter Horn User talk 00:43, 29 June 2013 (UTC)

✅ -DePiep (talk) 21:49, 4 July 2013 (UTC)

More accurate?
The output of  should perhaps be 62+1/2 in 62+1/2 in say 1587 mm? Peter Horn User talk 01:57, 26 June 2013 (UTC)
 * 1587.50 should be rounded upwards for being 0.50, I'd say. A 0.4999 should go downward. If I am right, then 1588 is OK. -DePiep (talk) 13:12, 27 June 2013 (UTC)
 * Agreed. Peter Horn User talk 18:32, 29 June 2013 (UTC)

❌ -DePiep (talk) 21:51, 4 July 2013 (UTC)

Edit request on 2 July 2013

 * Request: Please copy all code from into.
 * Background: See edit proposals discussions above:.
 * Testcases: See Template:RailGauge/testcases.

DePiep (talk) 13:41, 2 July 2013 (UTC)
 * Done! Plastikspork ―Œ (talk) 21:06, 4 July 2013 (UTC)
 * Thanks. Will take a look at /documentation and maintenance category. -DePiep (talk) 21:39, 4 July 2013 (UTC)

✅ -DePiep (talk) 22:23, 5 July 2013 (UTC)

Clean input: always add unit
We should alway require the input unit (that is: mm, in, m or ft ... in, '.. ' and sometimes m). Any unspecified number ("1.45") should be specified (that is: in, mm etc.).

I'll remove non-dimension input from the template, next edit. Have done so from the big /doc page list. -DePiep (talk) 01:42, 7 July 2013 (UTC)
 * This better be reduced.
 * iconic values can stay (brunel gauge, s.g.).
 * non-confusing integers ("1000" and "34") should stay (for these are used widely)
 * but other decimal values without unit should go. -DePiep (talk) 21:09, 11 July 2013 (UTC)
 * remove 16.5 confusing (in or mm!) Done.
 * remove these fractions from one unit only (imp or met), so that cleanup is easier (don't have to check which unit to add). -DePiep (talk) 14:21, 12 July 2013 (UTC)

✅ in sandbox: rm all metric input options without unit (mm or m). -DePiep (talk) 15:01, 12 July 2013 (UTC)
 * Undone: would give too many pages with errors.

✅: rm all fractioned metric input without unit (like 28.08 and 1.6). -DePiep (talk) 18:34, 12 July 2013 (UTC)

Possible double definitions
Here is a list of gauge definitions from the template list. It looks like they are definitions of the same gauge but with a different value. For each of them, please discuss per pair: are they different (then keep) or are they the same (we merge them into one definition (the disposed definition will be put in a maintenance category so we can edit the article that uses it). -DePiep (talk) 10:27, 16 May 2013 (UTC) -- confusing input options, better require "10.5in"
 * 10.5 mm
 * 10.5 &rarr;
 * 10.5mm &rarr;
 * Sandbox: removed option 10.5. Remaining: 10.5mm, 10.5in, 10.5".
 * 10.5mm &rarr;
 * 10.5in &rarr;

-- are these really different?
 * 0.650 in
 * 0.649in &rarr;
 * 0.650in &rarr;
 * Sandbox: rm 0.649in options & definition. Suspiciously close to 0.650in (0.02 mm), looks like an old rounding variant for the same gauge.

-- is this really a different one, or just a rounding variant?
 * 6.5 mm
 * 6.5mm &rarr;
 * 0.256in &rarr;
 * 0.257in &rarr;
 * Sandbox: removed 0.257in gauge. Most likely a rounding variant for 0.256in.

-- better define 558mm to be 22 in right?
 * 22 in
 * 558mm &rarr;
 * 22in &rarr;
 * Sandbox. Changed: 558mm into 559mm, and being exactly 22in. (so 558mm does not exist here any more).

-- While 34 in = 864 mm, why split them?
 * 860 mm
 * 860 &rarr;
 * 34in &rarr;
 * The diff is 4mm, which is much. So we treat them as different gauges:
 * 34in=864mm (from 863.6mm).
 * Sandbox: added
 * 864mm &rarr;
 * Input 860mm, 34in puts page in the maintenance category, so we can check these pages individually on whether 860mm or 864mm was intended. (After these checks this category could be removed, in a next list version).
 * Todo: check documentation to list 860mm, 864mm, and 34in correctly.
 * Todo: check documentation to list 860mm, 864mm, and 34in correctly.


 * 0.750in
 * Input option 0.750in should also have0.75in
 * Not changed± already in there.


 * 9mm
 * 9mm &rarr;
 * 8.97mm &rarr;
 * Sandbox: not changed, but the pages will be listed in Category:Pages with incorrect use of RailGauge template for individual inspection (are these two the same gauge or not).

-DePiep (talk) 10:27, 16 May 2013 (UTC)
 * Layout and format: list by input. -DePiep (talk) 20:28, 4 June 2013 (UTC)
 * I am editing this in the sandbox (to go into the live template later on). Any input options that are removed, and that are actually used in articles, will then show up in the maintenance category. We can inspect these listed pages individually. -DePiep (talk) 13:32, 27 June 2013 (UTC)

Done in the sandbox. Will check. The tracking category is Category:Pages with incorrect use of RailGauge template. DePiep (talk) 14:56, 27 June 2013 (UTC)

✅ -DePiep (talk) 21:47, 4 July 2013 (UTC)
 * Conclusions after it was processed into the live code: there is no reason to delete an entry. Mostly the minorly differences between gauges are based on true background like scale definitions, or some are not sourced. We must keep them, until either: a. the rounding/error is proven to be the cause of separation, or b. some gauge is not sourced or used. So far, today, I did not meet any of these deletion/merging reasond in these. -DePiep (talk) 21:15, 12 July 2013 (UTC)

Maintenance category changes

 * rm the temporal check things added last time. After maint check, done?
 * Use main other to have only article pages - is already there.
 * Catsort by input value? - is already there. -DePiep (talk) 14:23, 12 July 2013 (UTC)
 * ✅ in the sandbox. No effect from here (temporals will go). -DePiep (talk) 21:23, 12 July 2013 (UTC)

Edit request on 12 July 2013

 * Request: Please put all code from RailGauge/sandbox (this version) into RailGauge.
 * Changes: see this overview. Four entries added, other tweaks. Also Template_talk:RailGauge talk about cleanup confusing input options.
 * Tests: are at RailGauge/testcases. Problem pages will appear in the maintenance category, to be handled individually.

DePiep (talk) 19:12, 12 July 2013 (UTC)
 * Yes check.svg Done. Thanks for the work, as always. — Mr. Stradivarius  ♪ talk ♪ 02:07, 13 July 2013 (UTC)

Gauges we should take an extra look at
Some gauges that should be checked, added or improved in the template list:
 * This list is evolving over time


 * Add:
 * : to add. ScaleSeven, 1:43.5 for Irish gauge. Well sourced. Or 1.447 in (is 36.754 mm. 1.45 in would yield 36.83 mm is too imprecise, so we use 4 sigfig)
 * : to add. ScaleSeven, 1:43.5 for Brunel (GWR) gauge. Well sourced. Or 1.937 inch (is 49.1998 mm. 1.94 in would yield 49.276 mm; too much off so we use 4 sigfig).
 * : to be added. See Pleasure Beach Express and British narrow gauge railways. In mm: 533 mm (yields 20.984 inch so fine enough). See Pleasure Beach Express and British narrow gauge railways. In mm: 533 mm (yields 20.984 inch so fine enough).
 * : to be added. Said to be 2 castilian feet @ 278.6 mm (557.2 mm). See Transport_in_the_Dominican_Republic, and especially Iberian gauge (with talkpage). still needs a source. Imperial: $1/32$ in yields 557.21 mm.
 * Change:
 * : 1.299 inch could be rounded to 1.3 inch within reasonable precision (being 33.02 mm). The mm size is well sourced at ScaleSeven.
 * : should accept 0.47in too.
 * ; same. Check whole list for this feature. Done: no more of these.
 * Trailing zero in output, check correctness (precision suggested): -- --.
 * Delete the zero from 16.5mm and 32mm. Keep in 15.76 (to be 15.75) mm.


 * ; change into 15.75 mm (3mm scale says 101.6 &times; 15.75 = 1.600.2 mm). Keep 0.62(0)in for imperial.
 * Check
 * : check whether this is really different from 1.75in (mentioned above btw).
 * No change. Is the exact 1:32 of s.g. (but nominal set to . See 1 gauge).


 *  and and : all different really?
 * 12 mm is well defined (in three standards!). 0.472 in (imp first) is not used because HO and TT scales are defined in metrics (US, Europe). See HOm, HOn3-1/2 scale, TT scale. 0.470in I could not find any source or usage. We leave 0.470in unchanged until proven superfluous.
 * Change: delete move 0.472in input options for being not the standard ( or: merge them with the 12mm first).


 * : imp first? (Victoria, Victorian, Irish): British empire age, so most likely defined in inches not mm.
 * No change. Sure they were defined in inches (in the 1846 Law for Ireland), but today these countries use metric units. In articles on history, one could swith to imp anyway. See Rail gauge in Australia.


 * : said to be 2 Castilian feet (278.6 mm), could not find source (Iberian said to be 6 C.f.). Check calculations; would be 557 mm; to be added). Transport_in_the_Dominican_Republic, and especially Iberian gauge (+talkpage).
 * Will be added at 557 mm.


 * : could be metrics first because defined in metrics? At least it should recognise metric input 44.45mm. See 1 gauge.
 * No change. Most probably defined in inches (UK 1909).

-DePiep (talk) 15:42, 6 July 2013 (UTC), -DePiep (talk) 16:04, 6 July 2013 (UTC) -DePiep (talk) 16:35, 6 July 2013 (UTC) -DePiep (talk) 18:08, 11 July 2013 (UTC) -- and more.
 * Edits applied to RailGauge/sandbox. See Template:RailGauge/testcases. -DePiep (talk) 18:58, 12 July 2013 (UTC)

✅ via sandbox, testcases and edit request. -DePiep (talk) 14:15, 13 July 2013 (UTC)

Edit request on 28 July 2013

 * request. please put all code from the sandbox into the live template.
 * background: Template_talk:RailGauge
 * tests: see RailGauge/testcases

DePiep (talk) 00:33, 28 July 2013 (UTC)
 * Yes check.svg Done — Mr. Stradivarius  ♪ talk ♪ 02:45, 28 July 2013 (UTC)
 * thanks. -DePiep (talk) 03:13, 28 July 2013 (UTC)

Gauges to be checked

 * RailGauge
 * RailGauge/sandbox
 * RailGauge/testcases

These are rail gauges we should check for improvements.
 * This list may evolve over time


 * Add
 * 1065 mm: : in page Cape gauge, wrt South Africa. To be sourced. Would be (41.929in=) 41.3in. will be $66 5/32$ in being 1065.21 mm. -DePiep (talk) 23:34, 27 July 2013 (UTC)


 * added to sandbox:

✅
 * Delete
 * 0.472in &rarr; : I've recently set this one to give metric first (because it is only defined in metric, see [ScaleSeven]]). Still this is a bad idea, and counter-intuitive. I propose to delete this imperial entry, as it is never defined as such.
 * Deleted from sandbox:

✅ etc.: rm these input options. They are broken metric values, without their unit (m). To prevent confusion, better rm them. (recently all other such input was removed; these slipped through).
 * Change
 * 0.26, 0.75, 1.75 &rarr;


 * Deleted from sandbox:

✅ ✅
 * 1 &rarr; . to produce . Reintoduce "1" for 1m gauge. No fraction. Iconic and named; should not have been deleted last time really.
 * 4.75in &rarr; : metric "121mm" is imprecise: it would calculate back to 4.764in. Better change it to "120.7mm" (for 4.752in).
 * Not changed. Not sure if this is the way to calculate. -DePiep (talk) 22:47, 27 July 2013 (UTC)


 * 7.25in &rarr; : metric "184mm" is imprecise: it would calculate back to 7.2441in. Better change it to "184.2mm" (for 7.252in).
 * Not changed. Not sure if this is the way to calculate. -DePiep (talk) 22:47, 27 July 2013 (UTC)


 * 8.25in &rarr; : metric "210mm" is imprecise: it would calculate back to 8.2677in. Better change it to "209.6mm" (for 8.252in).
 * Not changed. Not sure if this is the way to calculate. -DePiep (talk) 22:47, 27 July 2013 (UTC)

Named gauges have input option(s), Wikipage to link to. There can be a label (not at present; made up example: Victorian broad gauge ).
 * Named gauges check
 * Scottish &rarr; : remove this option, it is named "Scotch gauge".
 * rm "scotish" from sandbox:

✅
 * Victoria, Victorian:&rarr;
 * Link to be labeled: "Victorian broad gauge"? This looks seems to be the commonly used name. (There even exists a Narrow gauge lines of the Victorian Railways).
 * rm Victoria option?
 * did rm "victoria" from sandbox:

✅
 * Toronto: &rarr; . What is the best name? Links to: Toronto streetcar system. Label this: "Toronto streetcar and metro system/gauge" (correct but long), or "Toronto Transit Commission gauge" (nah)?
 * no change, not safe. -DePiep (talk) 00:26, 28 July 2013 (UTC)


 * Units linked?
 * So on shows units linked: . Where would we need that? Maybe a link (or reference) may be needed to detail the definition-issues, yes. But not the unit lnks. I'll have these pages listed, to see whether this link is needed.
 * Note these pages in maintenance category. -DePiep (talk) 00:26, 28 July 2013 (UTC)

✅

-DePiep (talk) 07:40, 13 July 2013 (UTC)
 * Check Category:Pages with incorrect use of RailGauge template.

Edit Request 28 July 2013
The return after the template and before the conditional catergory needs to be removed, as I have done in the sandbox here []. I've added a couple of lines at the bottom of Template:RailGauge/testcases to show the problem and that this solves it. Edgepedia (talk) 05:49, 28 July 2013 (UTC)
 * Yes check.svg Done. Thanks for the fix. — Mr. Stradivarius  ♪ talk ♪ 06:25, 28 July 2013 (UTC)
 * Of course. I missed my check. -DePiep (talk) 14:27, 30 July 2013 (UTC)

Rail gauges to be checked

 * &rarr; checks are linked to RailGauge/sandbox here
 * Overview at RailGauge/testcases


 * Add:
 * 0.472in &rarr;
 * 0.473in &rarr;
 * Currently 12mm in produces . I got the impression that 0.472 in and 0.473 in are also commonly used to describe that same gauge, by inches (see List of rail transport modelling scale standards). Both calculate to the right mm size:
 * 0.472 in => 11.9888 mm
 * 0.473 in => 12.0142 mm
 * I withdraw this proposal. The imperial input (two variants?) is not defining. It is defined by metric, end of topic. Whenever some article requires imperial unit first, the editor can add imp atop the 12mm input. -DePiep (talk) 22:53, 12 August 2013 (UTC)
 * I am confusing myself. TT scale says it is from $37 19/32$ to 1 ft (1:120), so defined in imperial units. But s.g. / 120 is not exactly 12mm (a rounding issue). -DePiep (talk) 13:00, 13 August 2013 (UTC)
 * This should be it: both 0.472in and 0.473in are imperial measures of exact 12mm (12mm itself is rounded from 11.94mm from a scaling). They are not results of scaling by themselves. So they are OK as inputs. Propose to add them. Both lead to the same gauge, to be defined "0.472 in" (because most closest; sources not clear on this detail). -DePiep (talk) 14:12, 26 August 2013 (UTC)
 * ✅ (0.472in added, 0.473in stays)


 * 350mm &rarr; . Decauville in the Netherlands. Source in Dutch. -DePiep (talk) 13:08, 4 August 2013 (UTC)
 * $33 15/32$ in &rarr; 350,04 mm
 * source


 * 410mm &rarr; . See Narrow gauge railways in Germany: Kinderstraßenbahn Frankfurt am Main seems to have it (but it is a redlink and not sourced). -DePiep (talk) 12:21, 3 August 2013 (UTC)
 * $13/32$ in &rarr; 410,37 mm
 * source Kinderstraßenbahn Frankfurt am Main notes a printed source.


 * 550mm &rarr; see Narrow gauge railways in Denmark and Decauville in the Netherlands. Source in Dutch. -DePiep (talk) 13:08, 4 August 2013 (UTC)
 * $9 13/32$ in &rarr; 550,07 mm
 * source
 * source


 * 620mm &rarr; . Decauville in the Netherlands. Source in Dutch. also in Narrow gauge railways in Slovenia. -DePiep (talk) 13:08, 4 August 2013 (UTC)
 * $3 23/32$ in &rarr; 619,92 mm
 * source
 * Check difference (or not) with . -DePiep (talk) 12:21, 5 August 2013 (UTC)


 * 716mm &rarr; . See Narrow gauge railways in Poland - might need source. -DePiep (talk) 16:06, 3 August 2013 (UTC)
 * $3 23/32$ in &rarr; 715,96 mm
 * source Existed until 1923.


 * 791mm &rarr; see Narrow gauge railways in Denmark. Apparently this gauge was used for locomotives. -DePiep (talk) 16:04, 3 August 2013 (UTC)
 * $33 27/32$ in &rarr; 791,37 mm
 * Source: Google translated: In the following book, Østbanen 1879-2004, indicated gauge to 2 ½ feet or 791 mm. Nevertheless acquired Garde in 1866 a used German mine locomotive gauge 785 mm. This difference in gauge targets impossible did not [did not make impossible], however, use of the locomotive, which was in operation on the field all the way to 1921. This is perhaps one of the reasons for the doubts surrounding the runway actual gauge, there are several places specified for both 785 mm (evp have even one such example) and 791 mm. Thus mention Wikipedia [Faxe Jernbane]: "There is no doubt about the route originally used gauge. Figures have admittedly several places in the literature as 791 mm, but in the delivery protocol of train factory Krauss set in 1874, 1907, 1914 and 1927 having delivered locomotives gauge 785 mm. It is somewhat unclear why mentioned one at the track width 791 mm. There should probably be a shift over the years, since Faxe Limestone Quarry around 1970 ordered 2 diesel locomotives in Schöma with a desired track width of 791 mm."
 * So the gauge 791 mm indeed, and 785 mm gauge locomotive(s) was used. The "$21 15/16$ ft" remark is strange ( does not fit; possibly used in a different track?). We can add this one. -DePiep (talk) 11:01, 6 August 2013 (UTC)


 * Named gauge
 * Victorian &rarr; . Weird that this Australian named gauge links to "Irish". Looks like it needs a wikilabel or a redirect page. Also: shouldn't it show the name Victorian broad gauge? -DePiep (talk) 15:04, 4 August 2013 (UTC)
 * This introduces ambiguity: which link to expect with input ? Looks like Victorian should get its own entry by name only ... -- if we maintain her name. -DePiep (talk) 00:09, 5 August 2013 (UTC)
 * We can create something like this: only input victorian produces output " Victorian gauge". Otherwise 1600, Irish will go as was. (Note: this is a data concept change: we use gauge "id=x, first=imp twice) -DePiep (talk) 20:53, 11 August 2013 (UTC)
 * I have split "Victorian" from "Irish, 1600mm" to create the link option Victorian broad gauge.
 * Victorian &rarr;
 * Irish &rarr;
 * I have added the word "broad" because in Australia "broad", "narrow" and "standard" is used to define specific gauges (so "broad gauge" in Australia means 1600mm). We might want to visit Victorian gauge, Irish gauge, Victorian broad gauge for checks. -DePiep (talk) 11:50, 12 August 2013 (UTC)


 * Pennsylvania &rarr;
 * Weird link. Should be Pennsyvanian only. -DePiep (talk) 23:56, 13 August 2013 (UTC)
 * No, keep descriptive name, is better. There is no proper name for this one. -DePiep (talk) 14:14, 26 August 2013 (UTC)


 * Toronto &rarr;
 * Really good name? Check. -DePiep (talk) 23:56, 13 August 2013 (UTC)
 * Keep. Closest. -DePiep (talk) 14:14, 26 August 2013 (UTC)

Edit request on 26 August 2013

 * Edits: Please copy all code from Module:RailGauge/sandbox into Module:RailGauge (diff).
 * Please copy all code from Module:RailGauge/data/sandbox into Module:RailGauge/data (diff).
 * So, the changes are in Module space only.


 * Changes discussed at module code, entry options (data)
 * Tests are in Template:RailGauge/testcases and Module:RailGauge/data/sandbox (/doc, uses internal module check procedure)
 * Adding: Template:RailGauge/format met and Template:RailGauge/format imp are not used in mainspace any more, so their protection could go.

DePiep (talk) 15:28, 26 August 2013 (UTC)
 * All done &mdash; Martin (MSGJ · talk) 13:10, 28 August 2013 (UTC)
 * Thanks. Looks good. -DePiep (talk) 19:56, 28 August 2013 (UTC)

Template usage requested
I have asked for a list of template calls. (from ~11000 pages, so possibly 25000 calls). Bot_requests -DePiep (talk) 21:24, 31 August 2013 (UTC)