Thanks Eric for all the investigations, that's interesting. I'm in the UK and, it seems for me, that the 'break point' for the date is 2 December 1847. Back to then everything seems to be fine but go to 1 December 1847 and the date displayed is a day earlier, so 30 November 1847 in this case. I don't see a problem at 18 November 1883 when standardized time zones introduced in the USA. I'm not sure what this means!
I'll update my project with the new timer tiddlers shortly. Take care, Anthony On Wednesday, 21 October 2020 at 08:18:41 UTC+1 Eric Shulman wrote: > On Tuesday, October 20, 2020 at 11:50:38 PM UTC-7, Eric Shulman wrote: >> >> For accurate dates, regardless of local timezone, add "12" to the end of >> the date; e.g. "1883111812", which specifies a *time* of "12 noon". >> Because timezones range from UTC-1200 to UTC+1200, the resulting computed >> date will be correct by avoiding the effect of the >> localtime timezone offset that shifts the time back (or forward) by up to >> 12 hours. >> > > Update to http://TiddlyTools.com/timer.html > > The Calendar code for getevents_timeline() and getevents_timeline_annual() > have been adjusted to handle dates that have more than 8 digits > (they now ignore any excess digits). This allows the "timezone hack" > described above to be used without impacting the automatic generation > of events for "annual" and "range" timelines. > > -e > > > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/2aa45e89-ce35-4515-ab83-b14154092859n%40googlegroups.com.
