To help centralize discussions and keep related topics together, most talk pages of subtemplates and modules redirect here
Template:Track gauge is permanently protected from editing because it is a heavily used or highly visible template. Substantial changes should first be proposed and discussed here on this page. If the proposal is uncontroversial or has been discussed and is supported by consensus, editors may use {{edit template-protected}} to notify an administrator or template editor to make the requested edit. Usually, any contributor may edit the template's documentation to add usage notes or categories.
Any contributor may edit the template's sandbox. Functionality of the template can be checked using test cases.
This template does not require a rating on Wikipedia's content assessment scale. It is of interest to the following WikiProjects:
This template is within the scope of WikiProject Trains, an attempt to build a comprehensive and detailed guide to rail transport on Wikipedia. If you would like to participate, you can visit the project page, where you can join the project and/or contribute to the discussion. See also: WikiProject Trains to do list and the Trains Portal.TrainsWikipedia:WikiProject TrainsTemplate:WikiProject Trainsrail transport
{{Convert|11+1/2|mi|km|0|adj=on}} section (in body)
expct:11+1⁄2-mile (19 km) section
shows: 11+½-mile (19 km) section
That is: the "+" and "½" (fraction character) are unexpected. This also happens within {{Infobox GWR}}.
Research & reproduce: I found that when {{Infobox GWR}} is removed (absent), the output is regular. To reproduce: in Special:ExpandTemplates put the lede (and the {{Convert}} code from body), and check with/without {{Infobox GWR}}.
This is due to the specific template first using this module when the module is wrapping the gauge in a link and is fundamentally this issue. Let me see if I can fix it here. Izno (talk) 15:10, 17 May 2021 (UTC)[reply]
The issue is in formatImp. I think I can do a limited fix though I hate that I must do it the way in question. Let me tweak the sandbox. Izno (talk) 15:17, 17 May 2021 (UTC)[reply]
@Hairy Dude:. OK here. Did you try to Purge the article (=click on clock topright on the page)? (Could be you have an old version in the cache). Anyway, I have made a minor edit, so the article should reload anyway. OK now? -DePiep (talk) 12:55, 24 August 2021 (UTC)[reply]
That was the first thing I tried after I saw the preview was correct. And I also made a minor edit to check. Are you not seeing it? Maybe it's some quirk of the mobile interface. Hairy Dude (talk) 13:04, 24 August 2021 (UTC)[reply]
@Bazza 7 it should not be necessary there. Infoboxes are not impacted by this issue. And actually, sidebars should not be impacted by this issue these days either, as they have special code that goes and finds the relevant tags. Izno (talk) 21:45, 10 February 2025 (UTC)[reply]
The actual issue is that you (general) put {{RailGauge}} inside a link, which is due to a different interaction with the parsing software, see phab:T200704. If you want to link a rail gauge, please use the appropriate option |lk=on. Izno (talk) 21:48, 10 February 2025 (UTC)[reply]
@Izno: Thanks for the explanation. I didn't code that part of the article but came across it in passing. The error appeared in the main article text as well as the info box, which is what made me think the fault still existed. Thanks for correcting the article. Regards, Bazza 7 (talk) 22:08, 10 February 2025 (UTC)[reply]