From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp10.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms9.migadu.com with LMTPS id 2OG3OF8LC2TE4gAASxT56A (envelope-from ) for ; Fri, 10 Mar 2023 11:50:08 +0100 Received: from aspmx1.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp10.migadu.com with LMTPS id KODJN18LC2RMFwEAG6o9tA (envelope-from ) for ; Fri, 10 Mar 2023 11:50:07 +0100 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 94E7E22DAD for ; Fri, 10 Mar 2023 11:50:07 +0100 (CET) Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=W4Rx6oTn; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=posteo.net ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1678445407; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=AbIWCeXcogSlxkD+q4DK6kLJw+wfIDXB0+dLYK4db8w=; b=lDT5wOk901feypTURY6HVT3H/t915xOkVGpaoU6d8hKIJ3UnOpRAcfV4QZP3T+gfhgDXcT zgV5ZwjYTKOodge366S9Ds5WtC3B/zmVSY7V8biPmkCsbTTb5e4X0h0G7MSXFysch7Dcv2 a7ErRSvl/BYvUayjoJjtkp/I9iEh4W0A4gJhAR4jGy4rOJ+SOU9xdBVbitqunrUhQg3u54 4ejtLuOARyN8DiEOnwqs3+yhMz95ByqYNJeihifQ1gfmlYh9R7UlCz1CaB7PDrw2AtS1yR eCzy61ZNF/2Yc+Yv7RvOoBwoTKYkNwpT//cRxnc8Yh1Y1C4WJOqQbhSwGcoabg== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1678445407; a=rsa-sha256; cv=none; b=pnvYBpLE+icIaK+x15GhciHObrRr0M7n2j2Pkr3BA+KXnnvl8nbj70jlMqp5QGjaT24jA9 MKVQJS+1pgG4gAKFmrJbtKQPCYOk3JJi8YokdinqnJEZTmQRF+jF2z1f81zKlnX8Gs0Cl9 UdQJsYwtkjyf6s6umpGs/Bivrkz84ViIocwB8NCCRFGN7gXWczLf3X97Tna06vKN7rESA7 iLY4cjVODr4TyZvCIDubMxI7Y+D5oMyRwhx7L7SErU2Pnx4drniA/BhLmed7pBsR2DPnUE efgqQklJsZ/Voz7M2T17osSXPQj2GcyCuqN1IUaJyiqrLx2Bi/yh5TyWU3KJVQ== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=W4Rx6oTn; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=posteo.net Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1paaJu-0006pX-VE; Fri, 10 Mar 2023 05:49:54 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1paaJs-0006p4-Uo for emacs-orgmode@gnu.org; Fri, 10 Mar 2023 05:49:53 -0500 Received: from mout02.posteo.de ([185.67.36.66]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1paaJr-00007K-9l for emacs-orgmode@gnu.org; Fri, 10 Mar 2023 05:49:52 -0500 Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id 8B9AF2405F1 for ; Fri, 10 Mar 2023 11:49:48 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1678445388; bh=iUz8YGUeCv0YaMpNG7/7FCRx6fyzuc1PcpHPP5AGY4E=; h=From:To:Cc:Subject:Date:From; b=W4Rx6oTni6DOaAhpHechXzGc+d6degiu5K7dab101f8vGrYQgotijOhDMHPDXKi2C jjMHYqsp1nG2BSZStm6v0/Fly847VJZ/+bcbVYPnKhsqpNBnYiv10oBBZk+/rjdC6a 6BpEV4MJ+Ib1w3T4vcL4Q14NpCP9v04bT1Sv/JL/WhCjtqlJv0SQA0Z76NMvuFAkoo YNdVUF3LsG9klYz9u2DIdqGWTFuCY2Wk+TPFtYHsM6CDhWpcDKwTksPeeLf6kcxOAk 9Xz0h8BW3fAAWBo4905U/ogqfQZB9+ZEiQJco/boBPXaPYFjeJdN/fGAS0tZhavPBg QRu5J3N1fFAcQ== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4PY2qv3YQDz6tnY; Fri, 10 Mar 2023 11:49:47 +0100 (CET) From: Ihor Radchenko To: Jean Louis Cc: Max Nikulin , emacs-orgmode@gnu.org Subject: Re: [POLL] Proposed syntax for timestamps with time zone info (was: [FEATURE REQUEST] Timezone support in org-mode datestamps and org-agenda) In-Reply-To: References: <87lelce6iu.fsf@localhost> <87357i9959.fsf@localhost> <877cwse95m.fsf@localhost> <87lekz3qmg.fsf@localhost> Date: Fri, 10 Mar 2023 10:51:18 +0000 Message-ID: <87fsaczxp5.fsf@localhost> MIME-Version: 1.0 Content-Type: text/plain Received-SPF: pass client-ip=185.67.36.66; envelope-from=yantar92@posteo.net; helo=mout02.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 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, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: X-Migadu-Scanner: scn0.migadu.com X-Migadu-Queue-Id: 94E7E22DAD X-Spam-Score: -7.79 X-Migadu-Spam-Score: -7.79 List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: emacs-orgmode-bounces+larch=yhetil.org@gnu.org X-Migadu-Flow: FLOW_IN X-Migadu-Country: US X-TUID: BO7jX/Jb3HOV Jean Louis writes: > Where you Ihor responded with this message: > https://lists.gnu.org/archive/html/emacs-orgmode/2023-02/msg00018.html > >> [2022-11-12 14:00 @UTC+2] >> [2022-11-12 14:00 @UTC-2:30] > >> are also fine within the proposed format. > > I am not sure what did you intend to show, did you intend to tell > that: > > - 2022-11-12 14:00 @UTC+2 means 2022-11-12 12:00 @UTC ? > > In my understanding "@UTC" means "UTC time zone". From above first > examples it is very confusing to use "UTC" as designation plus > positive or negative prefix. > > It is not common to represent it that way. As if there is any > designation for UTC, like "UTC" or "@UTC" or "Z", then there is no > prefix shown, or if any, there will be zero. > > And I said, representing time that way by mixing word "UTC" with > prefix would be confusing, as that practically creates new type of > time representation that is not ordinarily used. I mostly wanted to refer to TZ POSIX variable format, which allows "ABBREVIATION+OFFSET" format. "UTC" is actually ignored there. Further discussion revealed that UTC+2 is, in fact, even confusing. For you and also because POSIX uses reversed symbol convention with +2 in TZ referring to "time 2 hours __before__ UTC time". @UTC+2 is not something we will recommend. It will be technically POSIX-complaint, just as @BLAH-1 would be. Either one does not make much sense. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at