From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Dokos Subject: Re: Time-zone in dates Date: Tue, 30 Jun 2015 11:08:19 -0400 Message-ID: <87lhf1i68s.fsf@alphaville.usersys.redhat.com> References: <87zj3moadx.fsf@gmail.com> <87zj3mv9rb.fsf@ucl.ac.uk> <87ioaav72g.fsf@ucl.ac.uk> <87y4j6tgyn.fsf@nicolasgoaziou.fr> <20150626195749.GG5090@fjo-extia-HPdeb> <87zj3iodr4.fsf@ucl.ac.uk> <87egkugfjw.fsf@pierrot.dokosmarshall.org> <878ub1zlzy.fsf@delle7240.chemeng.ucl.ac.uk> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:32865) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z9x9F-0002rG-6X for emacs-orgmode@gnu.org; Tue, 30 Jun 2015 11:08:34 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Z9x9B-0005l5-1E for emacs-orgmode@gnu.org; Tue, 30 Jun 2015 11:08:33 -0400 Received: from plane.gmane.org ([80.91.229.3]:53169) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z9x9A-0005ks-R1 for emacs-orgmode@gnu.org; Tue, 30 Jun 2015 11:08:28 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Z9x99-0003Lk-1g for emacs-orgmode@gnu.org; Tue, 30 Jun 2015 17:08:27 +0200 Received: from nat-pool-bos-t.redhat.com ([66.187.233.206]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 30 Jun 2015 17:08:27 +0200 Received: from ndokos by nat-pool-bos-t.redhat.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 30 Jun 2015 17:08:27 +0200 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 Eric S Fraga writes: > On Monday, 29 Jun 2015 at 21:17, Nick Dokos wrote: >> The only reliable way of doing that is to use UTC as the "internal" >> representation and translate to/from local time on external >> display/input *only*. In the case of org mode, the "internal" >> representation is user-visible, so that can cause confusion and some >> head-scratching. But *any* other method is going to be a nightmare >> (damhikt). > > This may be the correct approach although I worry about losing > information by only storing UTC. Whether this information loss is > important or not is difficult to predict. It may be of ephemeral > importance only. In what way are you losing information?