3 ms·
It sounds like the real problem here is that time specifications are fundamentally contextual, and for whatever reason the application either doesn't have enoug
by Terr_ 10y ago
It sounds like the real problem here is that time specifications are fundamentally contextual, and for whatever reason the application either doesn't have enough machine-readable context to work with or doesn't use it.
Even then, it's still not clear-cut enough for computers to guess. Imagine the following facts are presented in this order:
1. "It is a Friday, and I am in London right now."
2. "On Tuesday I have an incredibly important [X o'clock] phone-call with someone here in the London Office."
3. "I am traveling to Prague on Monday and returning on Friday."
As a human, can you tell when the phone-call is? Did the traveler intend wall-clock X "here" in London, or did they mean wall-clock X wherever they'd physically be in the future? If it's that ambiguous to a human, do you want your software to make fancy guesses?
(Bonus: "The Czech Republic is ending their Daylight Savings time this Sunday.")
- pavlov 10y agoLondon and Prague both follow the EU standard dates for DST, so at least there's a minor comfort that you can assume all of EU to switch at the same time. (Of course, after Brexit, who knows -- maybe they'll move DST start and end dates around just because they finally can?)
- dijit 10y agoThere's a 1hr difference between Prague and London. Finland is E.U. and has a 2hr time difference. The EU doesn't mandate a time-zone.
- wolf550e 10y ago'pavlov meant that the entire EU switches to daylight savings time on the same date.
- dijit 10y agoAh I see. And that's been a thing since 1996- it's unlikely Britain would switch to be spiteful as it doesn't add anything for Britain and only adds confusion. But I've been wrong about Britain and the EU before.
- matchagaucho 10y agoGoogle already has a pretty impressive "Where" input field on GCal events, and consistently auto-suggests the correct address for an event. It could also prompt for timezone if Event.GeoTimeZone != CurrentTimeZone ?