From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id 2G0NIEqH1V9LXwAA0tVLHw (envelope-from ) for ; Sun, 13 Dec 2020 03:15:22 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1 with LMTPS id EP+xG0qH1V9oBQAAbx9fmQ (envelope-from ) for ; Sun, 13 Dec 2020 03:15:22 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 786329402A7 for ; Sun, 13 Dec 2020 03:15:21 +0000 (UTC) Received: from localhost ([::1]:44630 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1koHqy-0000sH-Du for larch@yhetil.org; Sat, 12 Dec 2020 22:15:20 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:60648) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1koHqQ-0000re-Qm for emacs-orgmode@gnu.org; Sat, 12 Dec 2020 22:14:47 -0500 Received: from mail-wr1-x42c.google.com ([2a00:1450:4864:20::42c]:38245) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1koHqP-0005P8-8j for emacs-orgmode@gnu.org; Sat, 12 Dec 2020 22:14:46 -0500 Received: by mail-wr1-x42c.google.com with SMTP id r7so12962526wrc.5 for ; Sat, 12 Dec 2020 19:14:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=9abk2m87iKaNmDzQmDW/cxqO3WBeN5MCQasxOHapYvw=; b=GUFOD9dmdw2dDSbh1AGFYHdHzRULnFM7XqH3ikY91aUzMNUpCFz7xe1Dal9PSNrxfz 49P6FzFtUn1c8Up77wHrMZQNdeHiw4H3K++j5eY3g5pdUQtrmf5t2v9xmOtjKrk4TSyC RKeOOcLHuQSGtBwLB/uFzfI7VbbuCAW6N1IOwZIR3A6SJQozMKx3jhpMY9CkvwCSH6kQ 1Y809+QuzHiG3oUjGM3ZosCnR1yPcNmuXFFEbZWawtfpNqg5Geve2BTv4oZUqCHlJyjj 64LuGKrGc+QxOIL2mvyZE0/H8ayrliE0EcnJboGEVSed6EsKJB8QApzyzk9yBf3LY3Yj cHdw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=9abk2m87iKaNmDzQmDW/cxqO3WBeN5MCQasxOHapYvw=; b=PDKTkzmh6VMzF4DoDFjj1HukFlEm5UqOo37nWH0o09e2B3ReNJ7TJxGSVXGfA/3S2P DS9dLbQ9u49YGzGP5XzipY7M0kOfwzVte77py7yjPnsmpcqd4T0WLX9HOZjBQV/SLU9Z bYOfnapiiq/18Z3Z4jiiQBlhUlFtJS+GVaGDBuQmg1yx3xZAJw+1XEu7DxFXmluqkuaR UMZYCqNF2e/tx8RgCeB3PQBCxNOZaHwCenOfM3R+tKx8Zv3xxrrZj7yRmNTkh03WGzlG ix6WFv3NxQ4EOir2Phxpk+9VPNbYOVQPY3OAs92iB99S3lhRwGGEtnHjeBmPjkwfYFxV 98jA== X-Gm-Message-State: AOAM5332Hxs2hZfFgadysmsV/IPWUQ7/1r2COLYywcGxt2MNCRe49MWk TSiEM1PtZFB579fXuv2zUlvdfyFQ+c2JYMR8UFY= X-Google-Smtp-Source: ABdhPJxCeEC92tlbcR4fj08uNj3EFV2GAnwLphwG9EasymSgwJQig9JBZqTqvSFnLlKb3MzR1MwwoxMSqFmXhgXxKzE= X-Received: by 2002:adf:e98b:: with SMTP id h11mr17861958wrm.21.1607829282839; Sat, 12 Dec 2020 19:14:42 -0800 (PST) MIME-Version: 1.0 References: <87wnxrjjl2.fsf@gmail.com> <87lfe5ju0t.fsf@gmail.com> <871rfuvdh9.fsf@gmail.com> In-Reply-To: <871rfuvdh9.fsf@gmail.com> From: "Alan E. Davis" Date: Sat, 12 Dec 2020 19:14:32 -0800 Message-ID: Subject: Re: org-table change time from UTC to other timezones To: Tim Cross Content-Type: multipart/alternative; boundary="00000000000043606b05b64fed6c" Received-SPF: pass client-ip=2a00:1450:4864:20::42c; envelope-from=lngndvs@gmail.com; helo=mail-wr1-x42c.google.com X-Spam_score_int: -12 X-Spam_score: -1.3 X-Spam_bar: - X-Spam_report: (-1.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=0.342, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: org-mode Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: "Emacs-orgmode" X-Migadu-Flow: FLOW_IN X-Migadu-Spam-Score: -3.00 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20161025 header.b=GUFOD9dm; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (aspmx1.migadu.com: domain of emacs-orgmode-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=emacs-orgmode-bounces@gnu.org X-Migadu-Queue-Id: 786329402A7 X-Spam-Score: -3.00 X-Migadu-Scanner: scn1.migadu.com X-TUID: rqVij1ABVLCu --00000000000043606b05b64fed6c Content-Type: text/plain; charset="UTF-8" Thank for the ideas. The 'date' command examples look interesting. I think R would not be too unwieldy as a hammer here. My use case is a humble one: just take a several clock times in HH:MM format (utc) and adjust to another timezone by adding or subtracting the relevant number of hours. The day of week is not important; i will have to deal with it. I did imagine a conditional subtraction by adding of subtracting 24:00 as needed. Much thanks for the advice. Alan On Sat, Dec 12, 2020, 15:00 Tim Cross wrote: > > Maxim Nikulin writes: > > > 2020-12-12 Alan E. Davis wrote: > >> > >> Thank for the clear explanation. My little problem seems to require a > >> super steam hammer. Your insights are most helpful. > > > > In my opinion, org mode is too rigid in respect to timestamp format. > > Sometimes I would prefer to specify timestamps with timezone. > > > > Well known example of idiosyncrasy of particular applications. > > Timestamps in xls files are represented by floating point numbers, > > namely days since 1 Jan 1900, fractional part is time. Unfortunately > > 1900 is not a leap year, so to avoid unnecessary complications of code > > and keep memory footprint small, on Macs epoch starts in 1904, on > > windows year 1900 has Feb, 29... > > Although there are likely some dark corners where bugs can be found, I > think you could probably add timezone data to org timestamps by changing > the default format strings. Org also uses an 'internal' 'time' value to > represent timestamps which are then converted to the required format > using these format strings. > > What is possibly missing is an easy way to specify a time zone when > creating a timestamp. I suspect it will default to whatever the local > system tz is and I don't think there is any convenient way to change tz > values like there is for the other timestamp components. > > -- > Tim Cross > > --00000000000043606b05b64fed6c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thank for the ideas.=C2=A0 The 'date' command exa= mples look interesting.=C2=A0=C2=A0

I think R would not be too unwieldy as a hammer here.=C2=A0 My use ca= se=C2=A0 is a humble one: just take a several clock times in HH:MM format (= utc) and adjust to=C2=A0=C2=A0another timezone by adding or subtracting the= relevant number of hours.=C2=A0 The day of week is not important; i will h= ave to deal with it.=C2=A0 I did imagine a conditional subtraction by addin= g of subtracting 24:00 as needed.=C2=A0=C2=A0

Much thanks for the advice.=C2=A0=C2=A0

Alan=C2=A0



On Sat, Dec = 12, 2020, 15:00 Tim Cross <theo= philusx@gmail.com> wrote:
Maxim Nikulin <manikulin@gmail.com> writes:

> 2020-12-12 Alan E. Davis wrote:
>>
>> Thank for the clear explanation.=C2=A0 My little problem seems to = require a
>> super steam hammer.=C2=A0 Your insights are most helpful.
>
> In my opinion, org mode is too rigid in respect to timestamp format. > Sometimes I would prefer to specify timestamps with timezone.
>
> Well known example of idiosyncrasy of particular applications.
> Timestamps in xls files are represented by floating point numbers,
> namely days since 1 Jan 1900, fractional part is time. Unfortunately > 1900 is not a leap year, so to avoid unnecessary complications of code=
> and keep memory footprint small, on Macs epoch starts in 1904, on
> windows year 1900 has Feb, 29...

Although there are likely some dark corners where bugs can be found, I
think you could probably add timezone data to org timestamps by changing the default format strings. Org also uses an 'internal' 'time&#= 39; value to
represent timestamps which are then converted to the required format
using these format strings.

What is possibly missing is an easy way to specify a time zone when
creating a timestamp. I suspect it will default to whatever the local
system tz is and I don't think there is any convenient way to change tz=
values like there is for the other timestamp components.

--
Tim Cross

--00000000000043606b05b64fed6c--