From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp10.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms5.migadu.com with LMTPS id 6OX3Fq3VyGPVUAAAbAwnHQ (envelope-from ) for ; Thu, 19 Jan 2023 06:31:25 +0100 Received: from aspmx1.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp10.migadu.com with LMTPS id YF8lFq3VyGMgSQAAG6o9tA (envelope-from ) for ; Thu, 19 Jan 2023 06:31:25 +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 8AAA6110E9 for ; Thu, 19 Jan 2023 06:31:24 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pINVJ-0005HW-Hk; Thu, 19 Jan 2023 00:30:25 -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 1pINVI-0005H7-Au for emacs-orgmode@gnu.org; Thu, 19 Jan 2023 00:30:24 -0500 Received: from stw1.rcdrun.com ([217.170.207.13]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pINVG-00038U-Ly for emacs-orgmode@gnu.org; Thu, 19 Jan 2023 00:30:24 -0500 Received: from localhost ([::ffff:197.239.7.243]) (AUTH: PLAIN admin, TLS: TLS1.3,256bits,ECDHE_RSA_AES_256_GCM_SHA384) by stw1.rcdrun.com with ESMTPSA id 0000000000103951.0000000063C8D571.000077C0; Wed, 18 Jan 2023 22:30:24 -0700 Date: Thu, 19 Jan 2023 08:29:21 +0300 From: Jean Louis To: Tim Cross Cc: Ihor Radchenko , Daryl Manning , rjhorn@alum.mit.edu, emacs-orgmode@gnu.org Subject: Re: [FEATURE REQUEST] Timezone support in org-mode datestamps and org-agenda Message-ID: Mail-Followup-To: Tim Cross , Ihor Radchenko , Daryl Manning , rjhorn@alum.mit.edu, emacs-orgmode@gnu.org References: <87cz7ejmgu.fsf@localhost> <63c66048.630a0220.427bf.a5f6@mx.google.com> <87r0vtiks0.fsf@localhost> <63c671c0.a70a0220.61aa5.56b8@mx.google.com> <87fsc88aq9.fsf@localhost> <63c7dd3d.170a0220.6b4d6.f84f@mx.google.com> <877cxk6oeu.fsf@localhost> <63c86454.170a0220.80970.652d@mx.google.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline In-Reply-To: <63c86454.170a0220.80970.652d@mx.google.com> User-Agent: Mutt/2.2.9+54 (af2080d) (2022-11-21) Received-SPF: pass client-ip=217.170.207.13; envelope-from=bugs@gnu.support; helo=stw1.rcdrun.com X-Spam_score_int: -17 X-Spam_score: -1.8 X-Spam_bar: - X-Spam_report: (-1.8 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_SBL=0.141, SPF_HELO_PASS=-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.29 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: 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-Country: US X-Migadu-Flow: FLOW_IN ARC-Seal: i=1; s=key1; d=yhetil.org; t=1674106285; a=rsa-sha256; cv=none; b=Wsp2f05j8bODXnQLpAOvexWoz3otBSWFwwYpqFJqM3iFks/w2kNRaDqsPGS1t7cK/XMwI8 meJpx3sZ0yigXwrt4Jn0E93bVKurOMOu2+b0kFbsJy52a7HcpavRBBXaXfZpABUeOt1/G8 ftiZTIRbtLXUz3Pb8JAq9nr+oQObpqEnC08fNIZemtF4xzGea9OIndUCBmG2HK15m0l1iq TkrK1+OvZUITNQSNV1vV9VFMT9DE2szBf0DNblbTzxORjNIzUCNhw7b6ClrY34IJkqyX3C msILG49uQ1yWTDDwmxCdmvwM1t/GHI6FZeRhR/z/rpwVdEty32hKNVVOeAVmAw== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=none; dmarc=none; 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" ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1674106285; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post; bh=RWP0eUoIyuY/Z1OUYHan+XL6OTLTJMr3LtJmsuhKQc8=; b=cxngYses+GBHkpHcfofejrMqwLGQAkeE2igngyshbrhF3kzF72QodElnlAbQoWqkDqhRms k2Gc8bMHCSNpXDpcbyldYk3mSlezHPA9Q/OoMoWtdQz7i512zCAxUXzm5cZPwoG8P5708U zhdv9idzevdtCE0TVRxMvp9P/v+DvWcCHFsJLr732zbkbWvp59QIgXS0tkVe4aHNYV1Zqr jaszvmpRCFowfHkvx/TKmPxR6fwZTkcIO5PLTsujMks4sIpFqJtpZqcO7K1jdDoRcURvmq SSNm29zeL7M8EtFnTzVfGgNc/ueoS+qPuDP5A9Bv01V/W0QjUu6kfrXBEH//zw== X-Spam-Score: -3.23 X-Migadu-Queue-Id: 8AAA6110E9 Authentication-Results: aspmx1.migadu.com; dkim=none; dmarc=none; 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" X-Migadu-Scanner: scn0.migadu.com X-Migadu-Spam-Score: -3.23 X-TUID: yoqwTxM/K136 * Tim Cross [2023-01-19 00:31]: > The problem is with meeting 2 and the assumption there is a definitive > timezone for the meeting. > > Consider this scenario. I have a meeting with two other people. We are > all in different timezone. What is the timezone of the meeting? Org in this state can't handle such things. A person in any timezone shall be able to see that time in his local time zone if we speak of distant meetings, and in case of face to face meetings, that person shall have computer aid to show him the meeting time in any time zone that user is located, during travel and upon arrival to face to face meeting. User is supposed to be assisted by computer. And not to assist to computer, or to get troubles from computer. - Time zone shall be more or less recognizable by city and country. - User addresses in the address book shall be part of every computer system - It is natural and common sense to know addresses of people one wants to meet - By using location of person one wants to meet, computer has got enough information for representation of the time zone - By sharing appointment record to user in other time zone, that user would see it in his time zone, or by choice in original time zone of the meeting place A record of time, shall have two attributes, the UTC time and the time zone to be displayed. By using system time zone setting, Org file time zone settings, heading time zone settings or time stamp time zone setting, any export of Org shall contain (by user's option) the desired representation of time stamps. Function of sharing of meetings shall ask local user: - is user in different time zone? And then by choice of the user's location, the time representation shall be prepared in such way that both parties understand each other. That is really not in the sphere of Org where there is not even a decent address book available. Just re-write the time by hand for your friend at other part of the world, write the timestamp in his time zone and your time zone, and problem solved. It is supposed to be text. It is not God. -- Jean Take action in Free Software Foundation campaigns: https://www.fsf.org/campaigns In support of Richard M. Stallman https://stallmansupport.org/