Slashdot Mirror

Oops! My bad. The converter is fixed now . Had to use javascript's getUTCFullYear instead of getFullYear. It apparently makes a difference when months and days are at their origin like your 2014-01-01 0:0:0 example. Thanks for reporting the bug! Here's a jsfiddle to demonstrate the difference.

Lunas: Yeah, that might be a good idea. However, I think naming them 'Lunas' might give people the impression that this is a lunar calendar, and that would be bad because it definitely doesn't accurately tract the cycles of the moon in any way shape or form. The calendar currently only uses the term Luna in the datemod section in order to define L = 28 days because M = 60 seconds. Hmmm... Good thought though.

Choice of year schronization:
seasons: I've heard people say that the equinox is a more stable constant so it definitely has that going for it. The solstice was chosen because it is the darkest point (but only in the northern hemisphere). The new moon is at the darkest point and so is the day. I'm not completely convinced that the terran computational calendar should break with that standard, but maybe, the equinox would definitely be a more neutral location. But if we are staying on the side of neutrality then which equinox?
january 1: If you're going to create a whole new calendar, I feel like keeping with a January 1st start date would be very confusing because you might expect the date to be a UTC date when it's totally not at all the same. But there'd be lots of confusion in ANY case. I know that TAI/UTC/UNIX uses January 1st, but besides that, do you know of any good reason to use January 1st as a start date other than convention?

Thanks again.

'designator' just means things like UTC (which you should be familiar with). The terran computational calendar designator is generally TC (unless you're using a year base, but I'll keep it simple in this reply).

'datemods' might take a little used to, but they DEFINITELY can be used to represent local timezones as well as daylight savings time. They can even represent timezone offsets that are defined in a number of minutes instead of hours.
PST (Pacific Standard Time), an offset of -8:00 in UTC is a +8H datemod in TC
PDT (Pacific DaylightSaving Time), an offset of -7:00 in UTC is a +7H datemod
NPT (Nepal Time), an offset of +5:45 in UTC is both a -345M and a -5H45M datemod
And while timezone abbreviation can be useful for know where dates originate from, they are often confusing. Would you ever want to memorize the offset of all the above timezone abbreviations? With offsets and datemods, you don't have to do that, you just have to realize how far away from greenwich someone is.

In terms of delimiters, the acceptable delimiters are space, plus, comma, minus, dot, slash, colon, underscore ( +,-./:_) (UTF8 hex codes 20, 2b, 2c, 2d, 2e, 2f, 3a, 5f) So please feel to write the terran computational date in which ever way you're most comfortable with using those delimiters: 44/5/21 4:46:17 TC+7H, 44-5-21 4:46:17 TC+7H, 44.5.21,4.46.17 TC+7H.

'designator' just means things like UTC (which you should be familiar with). The terran computational calendar designator is generally TC (unless you're using a year base, but I'll keep it simple in this reply).

'datemods' might take a little used to, but they DEFINITELY can be used to represent local timezones as well as daylight savings time. They can even represent timezone offsets that are defined in a number of minutes instead of hours.
PST (Pacific Standard Time), an offset of -8:00 in UTC is a +8H datemod in TC
PDT (Pacific DaylightSaving Time), an offset of -7:00 in UTC is a +7H datemod
NPT (Nepal Time), an offset of +5:45 in UTC is both a -345M and a -5H45M datemod
And while timezone abbreviation can be useful for know where dates originate from, they are often confusing. Would you ever want to memorize the offset of all the above timezone abbreviations? With offsets and datemods, you don't have to do that, you just have to realize how far away from greenwich someone is.

In terms of delimiters, the acceptable delimiters are space, plus, comma, minus, dot, slash, colon, underscore ( +,-./:_) (UTF8 hex codes 20, 2b, 2c, 2d, 2e, 2f, 3a, 5f) So please feel to write the terran computational date in which ever way you're most comfortable with using those delimiters: 44/5/21 4:46:17 TC+7H, 44-5-21 4:46:17 TC+7H, 44.5.21,4.46.17 TC+7H.

'designator' just means things like UTC (which you should be familiar with). The terran computational calendar designator is generally TC (unless you're using a year base, but I'll keep it simple in this reply).

'datemods' might take a little used to, but they DEFINITELY can be used to represent local timezones as well as daylight savings time. They can even represent timezone offsets that are defined in a number of minutes instead of hours.
PST (Pacific Standard Time), an offset of -8:00 in UTC is a +8H datemod in TC
PDT (Pacific DaylightSaving Time), an offset of -7:00 in UTC is a +7H datemod
NPT (Nepal Time), an offset of +5:45 in UTC is both a -345M and a -5H45M datemod
And while timezone abbreviation can be useful for know where dates originate from, they are often confusing. Would you ever want to memorize the offset of all the above timezone abbreviations? With offsets and datemods, you don't have to do that, you just have to realize how far away from greenwich someone is.

In terms of delimiters, the acceptable delimiters are space, plus, comma, minus, dot, slash, colon, underscore ( +,-./:_) (UTF8 hex codes 20, 2b, 2c, 2d, 2e, 2f, 3a, 5f) So please feel to write the terran computational date in which ever way you're most comfortable with using those delimiters: 44/5/21 4:46:17 TC+7H, 44-5-21 4:46:17 TC+7H, 44.5.21,4.46.17 TC+7H.

'designator' just means things like UTC (which you should be familiar with). The terran computational calendar designator is generally TC (unless you're using a year base, but I'll keep it simple in this reply).

'datemods' might take a little used to, but they DEFINITELY can be used to represent local timezones as well as daylight savings time. They can even represent timezone offsets that are defined in a number of minutes instead of hours.
PST (Pacific Standard Time), an offset of -8:00 in UTC is a +8H datemod in TC
PDT (Pacific DaylightSaving Time), an offset of -7:00 in UTC is a +7H datemod
NPT (Nepal Time), an offset of +5:45 in UTC is both a -345M and a -5H45M datemod
And while timezone abbreviation can be useful for know where dates originate from, they are often confusing. Would you ever want to memorize the offset of all the above timezone abbreviations? With offsets and datemods, you don't have to do that, you just have to realize how far away from greenwich someone is.

In terms of delimiters, the acceptable delimiters are space, plus, comma, minus, dot, slash, colon, underscore ( +,-./:_) (UTF8 hex codes 20, 2b, 2c, 2d, 2e, 2f, 3a, 5f) So please feel to write the terran computational date in which ever way you're most comfortable with using those delimiters: 44/5/21 4:46:17 TC+7H, 44-5-21 4:46:17 TC+7H, 44.5.21,4.46.17 TC+7H.

'designator' just means things like UTC (which you should be familiar with). The terran computational calendar designator is generally TC (unless you're using a year base, but I'll keep it simple in this reply).

'datemods' might take a little used to, but they DEFINITELY can be used to represent local timezones as well as daylight savings time. They can even represent timezone offsets that are defined in a number of minutes instead of hours.
PST (Pacific Standard Time), an offset of -8:00 in UTC is a +8H datemod in TC
PDT (Pacific DaylightSaving Time), an offset of -7:00 in UTC is a +7H datemod
NPT (Nepal Time), an offset of +5:45 in UTC is both a -345M and a -5H45M datemod
And while timezone abbreviation can be useful for know where dates originate from, they are often confusing. Would you ever want to memorize the offset of all the above timezone abbreviations? With offsets and datemods, you don't have to do that, you just have to realize how far away from greenwich someone is.

In terms of delimiters, the acceptable delimiters are space, plus, comma, minus, dot, slash, colon, underscore ( +,-./:_) (UTF8 hex codes 20, 2b, 2c, 2d, 2e, 2f, 3a, 5f) So please feel to write the terran computational date in which ever way you're most comfortable with using those delimiters: 44/5/21 4:46:17 TC+7H, 44-5-21 4:46:17 TC+7H, 44.5.21,4.46.17 TC+7H.

'designator' just means things like UTC (which you should be familiar with). The terran computational calendar designator is generally TC (unless you're using a year base, but I'll keep it simple in this reply).

'datemods' might take a little used to, but they DEFINITELY can be used to represent local timezones as well as daylight savings time. They can even represent timezone offsets that are defined in a number of minutes instead of hours.
PST (Pacific Standard Time), an offset of -8:00 in UTC is a +8H datemod in TC
PDT (Pacific DaylightSaving Time), an offset of -7:00 in UTC is a +7H datemod
NPT (Nepal Time), an offset of +5:45 in UTC is both a -345M and a -5H45M datemod
And while timezone abbreviation can be useful for know where dates originate from, they are often confusing. Would you ever want to memorize the offset of all the above timezone abbreviations? With offsets and datemods, you don't have to do that, you just have to realize how far away from greenwich someone is.

In terms of delimiters, the acceptable delimiters are space, plus, comma, minus, dot, slash, colon, underscore ( +,-./:_) (UTF8 hex codes 20, 2b, 2c, 2d, 2e, 2f, 3a, 5f) So please feel to write the terran computational date in which ever way you're most comfortable with using those delimiters: 44/5/21 4:46:17 TC+7H, 44-5-21 4:46:17 TC+7H, 44.5.21,4.46.17 TC+7H.