[OT] Time zones, etc (was A GNU COBOL status update)
[OT] Time zones, etc (was A GNU COBOL status update)
Posted Nov 19, 2023 21:32 UTC (Sun) by NYKevin (subscriber, #129325)In reply to: [OT] Time zones, etc (was A GNU COBOL status update) by rgmoore
Parent article: A GNU COBOL status update
If it had been implemented, the World Calendar would have introduced a three-day weekend beginning on Saturday, December 30* and ending on Sunday, January 1, with the middle day being called "Worldsday" and having no day of the week (or month, for that matter). In leap years, another intercalary day is inserted between Saturday, June 30, and Sunday, July 1. The calendar has the same number of days as the Gregorian calendar and uses the same leap year formula, so there would be no need to add or subtract days in order to switch to it (as was done with the Gregorian reform).
If you want something more standard and widely-supported, you could use the ISO 8601 week-numbering year, which always has a whole number of weeks, but usually does not agree with the Gregorian calendar as to the nth day of the year. The week-numbering year works by labeling whichever week contains the first Thursday in January (according to the Gregorian calendar) as "week 1," and then numbering weeks consecutively until you get to "week 1" of the following year. This means that, for example, if a year begins on Wednesday (according to the Gregorian Calendar), then the week-numbering calendar says it begins on December 30 (the preceding Monday). If a year begins on Monday, then both calendars agree on the beginning of the year, and the nth day of the year, but they will disagree as to when it ends. Because the week-numbering year defines its starting point relative to the Gregorian calendar, it cannot fall too far "out of sync," and periodically makes up for the lost days by having 53 weeks in a year. No individual year is closely aligned with the tropical year, but in the long run, the discrepancies cancel out.
Unfortunately, there's probably no good way to combine these types of reform: You can either have a year that follows the tropical year, as the Gregorian and World calendars are, or you can have a whole number of weeks, as the ISO week-numbering year does, but you can't do both.
* The calendar shortens December to 30 days, as part of a broader reform intended to produce more consistent month durations and four equal quarters.
Posted Nov 20, 2023 17:15 UTC (Mon)
by Wol (subscriber, #4433)
[Link]
It mildly annoys me when Easter is called "a moveable feast". It isn't, it's the first Sunday of the first month of the New Year. Just not our modern Gregorian New Year.
I gather the old Roman Calendar only had ten months, and was also a lunar calendar. It started roughly on the Spring Equinox, ran ten months to end roughly on the Winter Solstice, and then the calendar stopped for Winter until the new calendar started on the next spring equinox.
(Easter - with certain ecclesiastical fixes - is defined as the "first Sunday after the first full moon after the Spring Equinox". So if New Year's Day is the Spring Equinox - which it sort of was, I'm not sure if it was the 21st or 25th March, the first moonth was the first "full moon to full moon" of the year. Passover has approximately the same definition, but Passover has nothing to do with Sunday, and if Passover falls on a Sunday, Easter is the following Sunday. I think that only happens if Passover falls on a full moon.)
Cheers,
[OT] Time zones, etc (was A GNU COBOL status update)
Wol