Template talk:Birth date text

Merge
One of the critera for TFD is "The template is redundant to a better-designed template". The template Template:Birth date is heavily used and very well designed and accepted. It is being used on a very many articles and is full-protected because of it. This template has poor and confusing syntax. I am nominating it for merging rather than deleting because of the microformatting. I had been under the impression that the birth date and related templates already did that. If they do not, then I propose that it be added to those templates, which will then populate the desired changes across the encyclopedia. Nothing's broken, so there's nothing to be fixed. Let's not reinvent the wheel when we've already got some great templates that are widely used. 70.20.84.9 (talk) 18:38, 14 March 2009 (UTC)


 * Actually, last month this subject was discussed at length amongst Wikipedia's group most interested in dates and numbers and MOSNUM for one does not agree that the older templates are "better designed". In fact, the  consensus opinion was that the family of natural language templates that use,  are preferred to the older templates, and the MOSNUM guidance reflects that.  The family of templates that use natural language dates are also used in a large number of articles and include , ,  and .  The old templates have no facility for understanding plain text dates and a merge would be technically impractical.


 * Any conclusion regarding what happens to Birth-date logically applies to all other natural date templates. They cannot be considered in isolation.  If numeric orientation is the best design for birth dates, is it also acceptable for death date and age?  How about for template  that is used to specify times such as launches of spacecraft?  If not, then should we have natural dates for some date templates and not others?


 * It would be helpful if you provided an example of how the older number templates are better designed, or how the new templates have "poor and confusing syntax" For example, let's take human factors design.  Do you feel that
 * {{ which produces {{Death date and age|2008|12|10|2000|11|23|df=y}}
 * is more user friendly than
 * {{ which also produces {{Death-date and age|10 December 2008|23 November 2000}}


 * Surely not. The numeric orientation is obtuse, error prone, and gets particularly torturous when time of day is added to this interminable heap of numbers.  For example, consider the following wikitext for the time JFK was died, reported as approximately 1pm CST:


 * Besides the ease in coding and understanding the time, note the glaring difference that should be obvious to affeciandos of time.
 * Time zone handling with the old templates requires arcane offsets from UTC. Due due to reliance on obscure ISO encoding rules and non reliance on system support for time calculation, the older start date template is error prone.  In this case, the editor did not make the correct adjustment for it not being daylight savings time.  Time zone adjustment is what the meaning of the -7:00 is, and for Dallas, it is either -6:00 for winter, or -5:00 for summer as explained in the upcoming link.  Actually that's not the only error this hypothetical contributor has made.
 * The old templates have extremely obscure time encoding rules: The base time should be the local time, not UTC time. Even though the editor who made this mistake is a professed microformats enthusiast, this rule was not either not clear to him or he forgot it.  The correct microformat expression of this time with the time zone adjustment as the editor is attempting to do is actually 1963-11-22T13:00-06:00, and the syntax in the wonkey {{tl|start date}} template should be changed to reflect that (for explanation see ISO time zone syntax.  Everyone makes mistakes, even microformats enthusiasts.  So how can we expect content experts, let alone joe average contributor to understand this stuff?  Who is going to spot that error with the syntax in such a unnecessarily complex form?


 * Stop. Compare what the contributor has to do with the new template.  They copy paste from the news account.  "November 22, 1963 1pm CST".  End of story.  Accurate microformat emitted for them without them having to know anything whatsoever about the subject.  The old templates are better designed?  Come now.


 * Besides human factors, there are a number of technical errors and shortcomings having to do with the main purpose for these templates: the emission of microformat information. For example, handling of end date data is not conformant with specifications for dtend values.  I'd be happy to discuss these shortcomings with anyone interested in this level of technical detail.  I think any template writers who examine the template code will quickly see that a merge would be little more than forcing two templates to share the same name with essentially two separate sets of documentation for two distinct syntaxes.


 * After considering the context of these facts, this proposal for merge appears to be ill considered. -J JMesserly (talk) 08:36, 15 March 2009 (UTC)

Violation of delinking prohibition?
(outdent) These changes from birth date to birth-date, etc., would massively delink dates in infoboxes in a non-reversible way. It is in direct violation of Requests for arbitration/Date delinking prohibiting any more date linking or delinking until the case is resolved. 62.147.38.252 (talk) 09:06, 19 March 2009 (UTC)
 * 62.147.38.252 this is mistaken. No delinking is involved.  Here is an example:   Any links present are retained, because the new template unlike the old one supports links if the contributor elected to use a link or template in the right hand parameter. -J JMesserly (talk) 17:27, 19 March 2009 (UTC)

4-digit years
Why does and  require a 4-digit year while  does not. See Eusignius of Antioch as an example. MB 19:28, 26 July 2020 (UTC)

Requested move 15 September 2023

 * The following is a closed discussion of a requested move. Please do not modify it. Subsequent comments should be made in a new section on the talk page. Editors desiring to contest the closing decision should consider a move review after discussing it on the closer's talk page. No further edits should be made to this discussion.

The result of the move request was: moved. (closed by non-admin page mover) – Material  Works  22:17, 22 September 2023 (UTC)

– Very ambiguous with Birth date etc. Ideally, the hyphenated versions would target the spaced versions, but these have around 44k transclusions in total, so I don't think it's worth the effort. C LYDE TALK TO ME/STUFF DONE 17:03, 15 September 2023 (UTC)
 * Template:Birth-date → Template:Birth date text
 * Template:Start-date → Template:Start date text
 * Template:Death-date → Template:Death date text
 * Template:End-date → Template:End date text

The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
 * Support per nom. (Note: Moving these would require a template editor.) SilverLocust 💬 00:16, 22 September 2023 (UTC)