Search results
Jump to navigation
Jump to search
- local calendars = { julian = 'Julian', gregorian = 'Gregorian' } local newdate = { _id = uniq, calendar = 'Gregorian', -- default is Gregorian calendar47 KB (7,571 words) - 10:30, 26 May 2020
- Assumes Julian calendar prior to year 1582 and Gregorian calendar thereafter. Accounts for Julian calendar leap years before 1582 and Gregorian leap years44 KB (7,077 words) - 13:46, 2 August 2018
- org/entity/Q1985727 for the proleptic Gregorian calendar or http://www.wikidata.org/wiki/Q11184 for the Julian calendar] if parameter then if parameter ==34 KB (4,990 words) - 22:14, 15 October 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 the752 bytes (141 words) - 14:01, 2 August 2018
- dates(date_parameters_list, COinS_date); -- start temporary Julian / Gregorian calendar uncertainty categorization if COinS_date.inter_cal_cat then add_prop_cat166 KB (23,391 words) - 22:23, 15 October 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
- local function dateToGsd(frame) -- Implement Template:Gregorian serial date. -- Return Gregorian serial date of the given date, or the current date. --26 KB (3,669 words) - 13:47, 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