Mathematics Template‑class | |||||||
|
|
|
This page has archives. Sections older than 90 days may be automatically archived by Lowercase sigmabot III when more than 4 sections are present. |
HI MSGJ, as the last user to make changes to this template, would the code be able to be modified so that ((Ordinal|=1))
could produce =1st. Know how pesky equal signs are in code but it would be great if this could be done. Cheers – Ianblair23 (talk) 07:19, 15 August 2017 (UTC)
((#invoke:Ordinal|ordinal|((=))1))
outputs =1st. Abjiklam (talk) 15:35, 20 December 2017 (UTC)This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
I've rewritten this template as a module at Module:Ordinal. I've tested it at Template:Ordinal/sandbox and Template:Ordinal/testcases and it doesn't seem to break, but I would like some input from others before I make any changes to the main template. Can someone confirm that the module doesn't break and can replace the current template? Abjiklam (talk) 15:02, 20 December 2017 (UTC)
This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Since rewriting as a Module, the substitution feature doesn't work. I don't know why. Or am I using it incorrectly?
((subst:Ordinal|13))
((#invoke:Ordinal|ordinal))
—GoldRingChip 13:12, 6 February 2018 (UTC)
((#invoke:Ordinal|ordinal|13))
- which gives 13th, or more generally ((#invoke:Ordinal|ordinal|(({1))))}
I've reopened the TPER with a fix at the sandbox. ∰Bellezzasolo✡ Discuss 15:56, 24 February 2018 (UTC)
I'd like this template to better handle inputs that are already ordinals. For instance, ((Ordinal)) should just spit back out 47th
, not 47thth
. This would help make templates more flexible in case a user accidentally enters an ordinal when they should've just gone with the numeral. Would anyone be able to help implement that? ((u|Sdkb)) talk 22:14, 24 January 2022 (UTC)
((ordinal|((cardinal|#))))
. ((u|Sdkb)) talk 22:18, 24 January 2022 (UTC)second
, have the same issue. ((u|Sdkb)) talk 22:22, 24 January 2022 (UTC)