Search results
Jump to navigation
Jump to search
- as well as by name or abbreviation (e.g., "August" or "Aug"). The Gregorian calendar is assumed, with no special support provided for dual dating or the752 bytes (141 words) - 14:01, 2 August 2018
- number as well as by name or abbreviation (e.g. "August" or "Aug"). The Gregorian calendar is assumed, with no special support provided for dual dating or the824 bytes (248 words) - 14:16, 2 August 2018
- This template has no provision to deal with a date in a non-Gregorian calendar. Also, ISO 8601 requires mutual agreement among those exchanging information674 bytes (94 words) - 00:00, 6 January 2018
- to be in the Gregorian calendar. Thus this template should not be used for a date stated in any other calendar, such as the Julian calendar.1 KB (54 words) - 14:16, 2 August 2018
- to be in the Gregorian calendar. Thus this template should not be used for a date stated in any other calendar, such as the Julian calendar.559 bytes (48 words) - 14:17, 2 August 2018
- This template has no provision to deal with a date in a non-Gregorian calendar. Also, ISO 8601 requires mutual agreement among those exchanging information771 bytes (172 words) - 00:00, 6 January 2018
- as well as by name or abbreviation (e.g., "August" or "Aug"). The Gregorian calendar is assumed, with no special support provided for dual dating or the2 KB (128 words) - 14:01, 2 August 2018
- Template:Death date/doc (section Range, Calendar)Since the data is emitted in the ISO 8601 format, the calendar must be the Gregorian calendar; the first acceptable year is 1583, the last acceptable3 KB (369 words) - 14:17, 2 August 2018
- Since the data is emitted in the ISO 8601 format, the calendar must be the Gregorian calendar; the first acceptable year is 1583, the last acceptable841 bytes (374 words) - 14:16, 2 August 2018
- number as well as by name or abbreviation (e.g. "August" or "Aug"). The Gregorian calendar is assumed, with no special support provided for dual dating or the5 KB (242 words) - 14:17, 2 August 2018
- This template has no provision to deal with a date in a non-Gregorian calendar. Also, ISO 8601 requires mutual agreement among those exchanging information2 KB (599 words) - 00:00, 6 January 2018
- throughout time be expressed in the same calendar (the ISO8601 standard specifies this as gregorian), so julian calendar format dates cannot properly be used1 KB (547 words) - 14:16, 2 August 2018
- throughout time be expressed in the same calendar (the ISO8601 standard specifies this as gregorian), so julian calendar format dates cannot properly be used9 KB (541 words) - 14:17, 2 August 2018
- 8601 standard requires the Gregorian calendar, this template should not be used if the date is given in the Julian calendar. For further information, visit8 KB (910 words) - 21:30, 5 January 2018
- 8601 standard requires the Gregorian calendar, this template should not be used if the date is given in the Julian calendar. For further information, visit121 bytes (939 words) - 11:39, 2 August 2018
- Template:End-date (category Templates generating hCalendars)applications via microformat encoding. Gregorian calendar dates are required. Display in Julian or Chinese calendar date is possible using parameter 2. ISO86012 KB (634 words) - 14:16, 2 August 2018
- applications via microformat encoding. Gregorian calendar dates are required. Display in Julian or Chinese calendar date is possible using parameter 2. ISO86019 KB (625 words) - 14:16, 2 August 2018
- Template:Start-date (category Templates generating hCalendars)applications via microformat encoding. Gregorian calendar dates are required. Display in Julian or Chinese calendar date is possible using parameter 2. ISO86012 KB (634 words) - 14:16, 2 August 2018
- Template:Birth-date (category Templates generating hCalendars)applications via microformat encoding. Gregorian calendar dates are required. Display in Julian or Chinese calendar date is possible using parameter 2. ISO86012 KB (634 words) - 14:16, 2 August 2018
- This template has no provision to deal with a date in a non-Gregorian calendar. Also, ISO 8601 requires mutual agreement among those exchanging information11 KB (593 words) - 00:00, 6 January 2018
- paragraph emit metadata indicating the date is in the Gregorian calendar; if the date is in the Julian calendar, do not use these templates, just write the date61 KB (1,438 words) - 11:39, 2 August 2018
- paragraph emit metadata indicating the date is in the Gregorian calendar; if the date is in the Julian calendar, do not use these templates, just write the date11 KB (1,440 words) - 11:39, 2 August 2018
- 1. parm 1 (optional) bce If birth date is BC, set to "b". – (optional) gregorian If Julian date is used, this parameter is required. The date provided is6 KB (194 words) - 14:17, 2 August 2018
- 1. parm 1 (optional) bce If birth date is BC, set to "b". – (optional) gregorian If Julian date is used, this parameter is required. The date provided is709 bytes (200 words) - 14:16, 2 August 2018