Please place new discussions at the bottom of the talk page. |
This is the talk page for discussing improvements to the Birth date and age template. |
|
Archives: Index, 1, 2, 3, 4Auto-archiving period: 60 days |
Time Template‑class High‑importance | ||||||||||
|
Template:Birth date and age 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 was considered for deletion on 2007 November 8. The result of the discussion was "keep". |
This template was considered for merging with Template:birth-date and age on 2016 July 24. The result of the discussion was "no consensus". |
Index
|
||||
This page has archives. Sections older than 60 days may be automatically archived by Lowercase sigmabot III when more than 4 sections are present. |
Corbin Braxton (Virginian), has an unknown birth date. The parameter in the info box for date of birth does not allow for "unknown", but it does allow "0000" for a birth year without generating an error message.
But at age of death, the infobox does not allow for 0000, nor unknown, nor unk, so an “Expression error: missing operand” is generated.
Is there a convention to use here? TheVirginiaHistorian (talk) 08:42, 3 January 2017 (UTC)
This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Add date of death March 13th, 2017 173.49.208.203 (talk) 18:44, 13 March 2017 (UTC)
This edit request to Template:Birth date and age and Template:Death date and age has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Could someone add an |infant=yes
parameter? So instead of ((birth date and age|2016|11|28))
and ((death date and age|2017|7|28|2016|8|4))
appearing respectively as 28 November 2016 (age 0) and 28 July 2017 (aged 0), the "0" is replaced with their age in months and days i.e. 28 November 2016 (age 8 months and 3 days) and 28 July 2017 (aged 11 months and 24 days). It would save having to use ((Age for infant)).--Nevé–selbert 19:07, 31 July 2017 (UTC)
|super=yes
parameter for the extremely old, e.g. Jeanne Calment, also.--Nevé–selbert 19:12, 31 July 2017 (UTC)((edit template-protected))
template.Would it be a good idea to have and |infant=yes
parameters? So instead of having to use ((Age for infant)), |super=yes
would display the age of said infant in months and days rather than years. With super-centenarians, |infant=yes
would display their age in years and days, rather than just years. Relisted by Cunard (talk) at 18:42, 15 October 2017 (UTC) per Snuge purveyor's review, "lots of suggestions, none in agreement". --Nevé–selbert 23:29, 14 August 2017 (UTC)
|super=yes
|md=yes
(for months and days) and |yd=yes
(for years and days) instead.--Nevé–selbert 08:07, 16 August 2017 (UTC)By removing theAfter it stops how would moving the BDA info to the regular field be done.
|infant=yes
parameter. This is meant to be a technical proposal aimed at benefiting editors rather than readers. Instead of having to use ((age for infant)) for young royals and the like, or ((age in years and days)) for the oldest people on Earth such as Violet Brown, editors can simply use a parameter to do just what those templates offer. It would probably mean deprecating ((age for infant)), as the new parameter would render that template redundant.--Nevé–selbert 20:14, 15 August 2017 (UTC)((age))
template. It returns ages in years: ((age|2017|8|1))
→ 6; ((age|2017|1|1))
→ 7; ((age|2016|8|1))
→ 7. --Redrose64 🌹 (talk) 19:51, 16 August 2017 (UTC)
|md=yes
and |yd=yes
sounds better.--Nevé–selbert 08:07, 16 August 2017 (UTC)extreme_age_days=no
. Just a thought, not a formal proposal. That way, there's no maintenance when a child turns some magic age, nor when a centenarian reaches that magic point. VanIsaacWScont 03:37, 29 August 2017 (UTC)
extreme_age_days=yes
could force the behaviour at any age. So the absence of that parameter would invoke the predefined age limits (which i am sure someone will eventually will want an override for as well) Agathoclea (talk) 07:30, 29 August 2017 (UTC)|display=md
and |display=yd
, with any other option producing the default output. This will obviate having to code up any error handling, e.g. for invalid input or for conflicting |infant=yes
|super=yes
in the same template, or |md=yes
|yd=yes
in the same template, both of which could happen with the above proposals (the second being more likely, i.e. because someone thinks "if I turn on both options, I'll get years, and months, and days"; avoid any confusion by giving a single parameter with limited and mutually exclusive output options). That's only if we actually want to use down-to-the-day ages for supercentenarians in the first place. — SMcCandlish ☺ ☏ ¢ ≽ʌⱷ҅ᴥⱷʌ≼ 04:49, 30 August 2017 (UTC)|show=md
rather than |display=md
. The modules are used for ((age in years and days)) and ((age in years and months)) but I ran out of energy before proposing wider deployment. The modules have the logic to emulate ((age for infant)) but I haven't done anything with the birth date part of this template. I'm mentioning that because the modules should be used if a merge is wanted. Johnuniq (talk) 05:46, 30 August 2017 (UTC)