Ciao PMario > I think it should be easy to create a parser for an extended timeline that > could deal with all of those dates.
If its easy to add "Big Date" parsing I'd say its a good idea. Best wishes TT On Saturday, 15 February 2020 19:56:35 UTC+1, PMario wrote: > > On Saturday, February 15, 2020 at 4:14:08 PM UTC+1, Mark S. wrote: >> >> I know I'm probably in the minority, but I think a simple, local-time, >> user-readable date format would be useful. Like 1815-06-18 >> > > hmmm, That would be good enough, if you assume, that everyone lives in a > similar time-zone as you do. But what if I live near the date-line > https://en.wikipedia.org/wiki/International_Date_Line > > IMO there needs to be a marker like UTC or GMT+01 or something similar. So > the rest of the world knows what to do. > > So ext-date-somedate 1815-06-18 (UTC) would be OK for me personally. But > that's only a date in the past of the human history. > > What if I want to express the past in "homo sapiens's history" ... I > thought js extended date with +-270 thousand years would be good. .... but > no: See this article in The Guardian > <https://www.theguardian.com/science/2017/jun/07/oldest-homo-sapiens-bones-ever-found-shake-foundations-of-the-human-story>. > > > > So we need something up to about 2 000 000 years ago. See the second chart > at: https://en.wikipedia.org/wiki/Homo#Names_and_taxonomy > eg: 1.2 Mya 1.2 million years ago. > > But I do want more: What's about the universe > <https://en.wikipedia.org/wiki/Universe>, the age of the earth > <https://en.wikipedia.org/wiki/Age_of_the_Earth>or how long does our sun > live? > > I found Year Symbols <https://en.wikipedia.org/wiki/Year#Symbols>, which > should allow us to solve the problem for really big numbers ;) Especially SI > prefix multipliers > <https://en.wikipedia.org/wiki/Year#SI_prefix_multipliershttps://en.wikipedia.org/wiki/Year%23SI_prefix_multipliers>. > > > > Abbreviations yr and ya > <https://en.wikipedia.org/wiki/Year#Abbreviations_yr_and_ya> may be an > option too. Since they contain a shortcut for years and years *ago*. > > So ext-date-tyranno may be 66 (mya) ... or 66 (Ma) ago. > > I think it should be easy to create a parser for an extended timeline that > could deal with all of those dates. > > - js-extended dates are defined in the specs. years must start with + or - > and have 6 digits. The rest is as known. > - SI prefixes are ka, Ma, Ga, Ta, Pa, Ea > - non-SI are kyr, myr, gyr for years and kya, mya, bya for years ago. > > So if ext-date-my-date-1 would be 1.2 (bya) it should be easy to know, > what I want to say. > > have fun! > mario > > -- 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/b50616ff-c7ec-4359-92e4-f6e9bcc6bc5a%40googlegroups.com.
