Ehoogerbeets

Updated for iLib, and added many new rows for various i18n features. Other libraries slots need to be updated to put the check marks for all these new features.
Traditional "unix time" is defined in C/C++ as a variable of type time_t, which is 32 bits. In that case, it encodes an unsigned number of seconds since midnight Jan 1, 1970 UTC (the start of the epoch), and runs until some time on Jan 19, 2038. (This may cause a Y2038 problem like the Y2K problem we had). 

Most Javascript engines implement a signed 64-bit version of unix time which is the number of milliseconds since midnight Jan 1, 1970 UTC. This type runs from -100 million years to +100 million years from the epoch. Oddly, the 64-bits can encode far longer than that, but they chose to cut it off at +/- 100 million years for some reason. I'm not sure what that reason is. That's still pretty good precision! It can still encode the precise millisecond that all the dinosaurs died 65 million years ago. ;-)