From mboxrd@z Thu Jan 1 00:00:00 1970 From: Russell Adams Subject: Re: Time-zone in dates Date: Wed, 8 Jul 2015 11:16:46 -0500 Message-ID: <20150708161646.GP3703@cardamom.adamsinfoserv.com> References: <20150626195749.GG5090@fjo-extia-HPdeb> <87zj3iodr4.fsf@ucl.ac.uk> <87egkugfjw.fsf@pierrot.dokosmarshall.org> <878ub1zlzy.fsf@delle7240.chemeng.ucl.ac.uk> <87lhf1i68s.fsf@alphaville.usersys.redhat.com> <87fv581jfv.fsf@ucl.ac.uk> <874mlo9l6k.fsf@ucl.ac.uk> <20150707172707.GK3703@cardamom.adamsinfoserv.com> <20150708155954.GS6137@geta> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:42642) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZCs1l-0007Sp-IL for emacs-orgmode@gnu.org; Wed, 08 Jul 2015 12:16:54 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZCs1g-0007mG-Hq for emacs-orgmode@gnu.org; Wed, 08 Jul 2015 12:16:53 -0400 Received: from kefka.asoshared.com ([65.99.237.198]:31039) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZCs1g-0007lv-Cu for emacs-orgmode@gnu.org; Wed, 08 Jul 2015 12:16:48 -0400 Content-Disposition: inline In-Reply-To: <20150708155954.GS6137@geta> 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-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Cc: Michael Brand On Wed, Jul 08, 2015 at 10:59:54AM -0500, Don Armstrong wrote: > The relative timezone of the observer is important, though, because > that's how you enter the information, and it's often the most logical > way to display the information. If you just store UTC there's no way to > regenerate that. I'd suggest that the relative timezone of the observer is normally the same, and if it should differ a display override sounds appropriate. > Though all of that said, just storing UTC is significantly easier, and > while I'd love to see a complete implementation, an incomplete > implementation which could be expanded to become complete would be a > great advance. I think the question is would supporting timezones be difficult to add? Then would you store the time in UTC only, or support a full timestamp that included timezone? Finally when being displayed they can use the user's $TZ by default, and maybe a suffix of @ TZ inside the date syntax? ------------------------------------------------------------------ Russell Adams RLAdams@AdamsInfoServ.com PGP Key ID: 0x1160DCB3 http://www.adamsinfoserv.com/ Fingerprint: 1723 D8CA 4280 1EC9 557F 66E8 1154 E018 1160 DCB3