From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Peter Neilson" Subject: Re: Timezones revisited Date: Wed, 01 Feb 2017 11:14:15 -0500 Message-ID: References: <20170131230346.GV7187@volibear.adamsinfoserv.com> <87shnxuczj.fsf@pellet> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes Content-Transfer-Encoding: Quoted-Printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:55627) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cYxXj-0002S2-77 for emacs-orgmode@gnu.org; Wed, 01 Feb 2017 11:14:00 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cYxXg-0000gX-0W for emacs-orgmode@gnu.org; Wed, 01 Feb 2017 11:13:59 -0500 Received: from pacmmta56.windstream.net ([162.39.147.222]:34789) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cYxXf-0000e8-PY for emacs-orgmode@gnu.org; Wed, 01 Feb 2017 11:13:55 -0500 In-Reply-To: <87shnxuczj.fsf@pellet> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org On Wed, 01 Feb 2017 10:50:24 -0500, Eric Abrahamsen = wrote: > Russell Adams writes: > >> I understand that Org's timestamp format does not include timezone >> information. Making that change would be an impractical modification.= >> >> I'm frequently working with several different timezones and I only >> need to store a time stamp converted to my local time. >> >> Does the time stamp input support some form of timezone input? I >> checked the manual and tried a few methods and they don't appear >> supported. > > If the time stamp format doesn't support timezone info, then the input= > method won't either, unfortunately. I had one of my occasional attacks= > of enthusiasm about this subject recently -- using org-caldav while > you're traveling really exposes the limitations of timezone-unaware > scheduling. > > Would it be completely out of the question to support an optional > timezone marker? From (nth 1 (current-time-zone))? > > <2017-02-01 Wed PST> > > The plumbing for time calculations would be... an adventure. But it > seems like it could be done in a backwards-compatible way. > > E Presumably everyone already knows that the timezones are more complicate= d = than hoi polloi believe? The offsets are not always integer values of = hours. For example, Newfoundland time is UTC=E2=88=9203:30. Additional = complications include daylight saving time and the many historical = versions of timezones. The definition of UTC can remain pretty much = constant, but local-timezone time varies as a function of both location = = and calendar date. Allowing user-defined functions (as simple or as complicated as one = desires) for translation from UTC might be best.