Jutta, I have never had to deal with such old dates, but if you primarily just want to assign years, and no need to check or test months of the year, days of the month then rather than use a date field perhaps just have a year field? Basically treat BC as another number in a field. In reality the systems behind different historical calendars, changes in interpretation, leap years ands non leap millennia reduce the accuracy of most date system too far back. To handle this correctly one would need a fit for purpose calendar extension, but if your resolution is only to the year you could just use a number, and perhaps a sequence number if something is known to proceed or follow another in the same year.
Regards Tones On Sunday, 29 November 2020 at 17:54:25 UTC+11 [email protected] wrote: > Hello Eskha, > > yes, thank you, indeed, the minus works for me, too. It is a bit confusing > because it takes the place of the first year digit, so the earliest year > you can do is -999, but that's fine for my purpose. But I still cannot get > the first century AD to work. Any year with two leading zeroes is > interpreted as 19..Is there a trick for that somehow? > > Thanks, > Jutta > > On Saturday, November 28, 2020 at 9:33:25 PM UTC+1 Eskha wrote: > >> Hello Jutta, >> >> What is working for me: I use "Y" format for date and a "-" in front of >> the date (eg -200 for 200 BC). >> >> Best regards, >> >> Eskha >> >> Le samedi 28 novembre 2020 à 20:35:53 UTC+1, [email protected] a >> écrit : >> >>> Hi, >>> >>> I am trying to get the Timelines plugin to work for my project. The >>> problem is, that my novel is set in the time of the early Roman empire, so >>> I need my timeline to be able >>> to display events from around 40 BC to 20 AD. Is there any way to enter >>> dates before the year 0? Also, even for the first 100 years AD it does not >>> work. When my datestring starts with two leading zeros, it always >>> interprets it as 19.. So when I enter a date like >>> 00090917 (which would be the date of the battle in the Teutoburg >>> forest), the timeline wiki renders it as 1909. For the year 0109 it works >>> correctly. >>> >>> Are there any solutions for this? If the date format itself does not >>> allow the dates to be BC, is there a way to use current dates (like, set >>> everything 2000 years in the future) in the date field so that the macro >>> knows how to space and order them and then display a text string with the >>> correct date from another field in the view instead? >>> >>> Thanks, >>> Jutta >>> >> -- 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/24d8f882-29cf-482e-8f45-4eb747963544n%40googlegroups.com.
