Misplaced Pages

Revision as of 14:22, 12 November 2008

{{#iferror: Error: Invalid time.

This template is used on approximately 49,000 pages and changes may be widely noticed. Test changes in the template's /sandbox or /testcases subpages, or in your own user subpage. Consider discussing changes on the talk page before implementing them.

This template should only be used internally in other templates.

Description

This template converts a date to one of the standard date formats used on the English Misplaced Pages.

This template should only be used internally in other templates. For formatting dates in articles, see Misplaced Pages's guidelines for formatting dates or an overview of date formatting guidelines.

If you want sortable dates for a table, use {{date table sorting}} instead.

Syntax

This template takes up to two parameters, both of which are optional:

{{date|<date to be formatted>|<date formatting style>}}

• <date to be formatted> is an (optional) date to be formatted.

  If no date is specified, the template emits the current date.
  For example, {{date}} produces {{#iferror: Error: Invalid time.. To avoid emitting the current date if none is input, use Template:fdate.

  If a date is provided, but is not recognized as one, the text is just returned as is. Most dates will however be recognized as such, including all the formats typically used on Misplaced Pages. Numerous variations thereof are also supported, including abbreviated or lower-case month names; ordinal "st", "nd", "rd", "th"; extraneous white space; missing comma, etc.

  Notes:

  • Some dates are converted even if they are not real dates, and some dates are not converted even though they are real dates. See known issues below.
  • Only dates within the range {{#iferror: Error: Invalid time. and {{#iferror: Error: Invalid time. are supported. Dates with two-digit years will have the years from 1970 to 2069. Other dates outside the range 1000–9999 will be treated as if the second parameter were "none".
  • when using month numbers in numeric, the valid formats are MM/DD/YYYY, DD-MM-YYYY, DD.MM.YYYY, YYYY/MM/DD, YYYY-MM-DD, MM/DD/YY, YY-MM-DD, DD.MM.YY, the invalid formats are DD/MM/YYYY, MM-DD-YYYY, MM.DD.YY, YYYY.MM.DD, MM.DD.YYYY, DD-MM-YY, YY/MM/DD, DD/MM/YY, YY.MM.DD

• <date formatting style> controls the date format in which the result is to be emitted. Recognized values for the second parameter are:

  • DMY gives d mmmm yyyy (e.g. {{#iferror: Error: Invalid time.). This is the default format.
  • MDY gives mmmm d, yyyy (e.g. {{#iferror: Error: Invalid time.)
  • YMD gives yyyy mmmm d (e.g. {{#iferror: Error: Invalid time.)
  • ISO gives an ISO 8601 style yyyy-mm-dd (e.g. {{#iferror: Error: Invalid time.)
  • none applies no formatting whatsoever

  If a date to be formatted is provided but no style is specified, the template emits a date in "d month yyyy" format, as it appears (for example) on discussion pages. When no date is specified, then the current date is emitted with no year, either in "d month" format for formatting style DMY, or in "month d" format for formatting styles MDY, YMD and ISO.

  Notes:

  • Although these are the four formats supported by MediaWiki's date autoformatting mechanism, only DMY/lDMY and MDY/lMDY are in accordance with the English language Misplaced Pages's Manual of Style. The use of ISO/lISO (ISO 8601) format within article prose is expressly discouraged by the Manual of Style; this format should only be used in tables, lists, or references.
  • In each case, the result is exactly the same as what would be emitted by MediaWiki's date autoformatting mechanism.However, dates are not manipulated by MediaWiki's date autoformatting mechanism even when linked. This permits dates to have a consistent appearance regardless of whether they are linked or not.
  • Misplaced Pages caches the current version of pages, and the template may display the date that the page was cached, rather than the current date.

Examples

With valid input

Other acceptable input

A wide variety of other input formats are handled correctly by the template:

Invalid input

Input strings that the template cannot format are returned unaltered. This includes strings containing characters such as square brackets, so any links will result in unformatted output.

Known issues

Out-of-range values are "fixed"

• The PHP library, that this template ultimately depends on, converts out-of-range values to the next-best in-range values. As a result, some date-like values that are not actually valid dates get converted anyway. These include...
  • all dates with zero day-of-the-month. Such a "zero-th" day of a month gets converted into the last day of the previous month.For example, {{date|June 0, 2006}} results in {{#iferror: Error: Invalid time..Similarly, {{date|0 January 2006}} becomes {{#iferror: Error: Invalid time..
  • all dates with day-number values that exceed the number of days in the specified month cause the date to be incremented into the next month.For example, {{date|31 November 2008}} results in {{#iferror: Error: Invalid time., since November has only 30 days.Similarly, {{date|February 29, 2007}} results in {{#iferror: Error: Invalid time., since 2007 was not a leap year.Note: Due to a parser peculiarity in the PHP library, 'December 32' and '32 December' are treated differently, and the latter results in an error (which causes this template to emit it unchanged), and only the former "overflows" into the next month.

Non-Gregorian dates are treated as Gregorian

• The PHP library that this template ultimately depends on assumes that all dates, irrespective of context, are Gregorian calendar dates. Consequently:
  • some dates that would be valid in a non-Gregorian context are treated as out-of-range dates and converted to the next-best in-range values. For example, {{date|30 February 1712}} results in {{#iferror: Error: Invalid time. because – even though 30 February 1712 is a valid date in the Swedish calendar – February 1712 had only 29 days in the Gregorian calendar.
  • ten dates are not reformatted. These are 29 February & 1 March of the years 1000, 1100, 1300, 1400, 1500. The cause of this is the same as that of the Swedish 30 February 1712.
  • some dates that would not be valid in some contexts are converted normally. For example, 29 February 1912 or 1 February 1918 are not valid in a Russian context, but perfectly valid in the Gregorian one.

ISO 8601 format not suitable for years before 1583

The ISO 8601 standard requires mutual agreement between those using the format to use years earlier than 1583. Since no agreement has been obtained from our readers, that format should not be used for such years, nor for any date not in the Gregorian calendar.

Output provided for ISO dates when year is missing

The current 2004 version of ISO 8601 does not permit omitting the year, but this template will produce a supposedly ISO output when the year is missing.

Does not provide Microformats

• hCalendar and hCard microformats have various date properties, which are not emitted by this template. Use {{Start date}}, {{End date}}, {{Birth date}} or one of their variants, as necessary, in infoboxes which allow microformat-compatible date templates.

See also

Multiple units of time

Single units of time

Date and time templates made for substitution:

Month:
{{Lmonth}} produces Dec
{{Nmonth}} produces Feb
{{Last month}} produces December 2024
{{Next month}} produces February 2025

Individual templates

• {{Calendar}}
• {{Calendar clock with Misplaced Pages stats}}
• {{Clock}}
• {{Digital clock}}
• {{Digital clock and date}}

Categories of templates

• Category:Time, date and calendar templates
• Category:Date-computing templates
• Category:Date-computing templates based on current time
• Category:ISO date templates
• Category:Calendar templates

• Date conversion templates
• Date-computing templates
• ISO date templates