As a general note,
Make sure not to mix up UTC and GMT.
UTC is a standard used for storing date-time information.
GMT, however, refers to a timezone in UTC.
The problems in TiddlyWiki stem from storing dates in GMT, so that all
users around the globe have the same date reference when looking at a
tiddler.
In other words, when you look at a plain date value in a tiddler, e.g. via
{{!!modified}} it is not shown in "your time", but simply as plain text.
If you want it to be displayed in your time or *selected compared to your
time* then you first need to have it converted into your time in order for
it to be displayed accordingly, or compared to some other date in local
time you wish to compare some date to, for example. That is why regexp is
not your friend, unless you first manage to translate the date you wish to
compare against to GMT, which more or less just switches what ends of the
puzzle you need to flip so as to solve it.
Practically speaking:
*tiddler-date*: 20161213235959
*query-**date*: 20170101000000
Supposer "tiddler-date" is a date value as stored in a tiddler and
"query-date" is a date value as you happen to make it up so as to say "give
me everything before that date", e.g. via some filter.
Now, suppose that you have no clue about GMT and so "query.date", for you,
is defined as the time you see on your clock. If your use regexp to run
that filter, and you're ass is not sitting on top of a GMT couch, then you
may or may not actually yield the desired result, since you would first
need to figure out what your query date translates to for GMT. Or, put
differently, someone sitting in India looking at your wiki, doing your
exact query, must inevitably get different results... since 0 o clock on
Jan 1 for them isn't 0 o clock on Jan 1 for you.
However, the above assumes that you actually managed to store
"tiddler-date" in some custom "date field"... properly, in GMT. I would
suspect most implementations, including the one where you type that in by
hand, do not respect the convention that the date eventually needs storing
in GMT. Now, this produces a total mess, since you have core dates stored
in GMT and some user defined dates stored in whatever time their clock was
showing when typing. The only way you can fix this, is to somehow
batch.convert the dates stored wrong to GMT and to then store them properly
in GMT, so that standard date fields and custom date fields speak the same
language. Let's just hope and assume, you didn't answer some of your custom
dates while you were in Tokyo and others while you were in Guatemala. Then
you pretty much need to restart with your efforts recording time, or fix
every date manually.
Best wishes,
Tobias.
--
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 post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/7a657a46-992f-4a11-8aee-da1ec3817fdc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
