From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Carsten Dominik Newsgroups: gmane.emacs.devel Subject: Re: ISO dates, correction on Org documentation Date: Mon, 21 Sep 2009 18:07:07 +0100 Message-ID: <0F4E72E8-3028-44EF-B185-6845C338D835@gmail.com> References: <87iqfglscc.fsf@gmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 (Apple Message framework v936) Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1253552939 23770 80.91.229.12 (21 Sep 2009 17:08:59 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 21 Sep 2009 17:08:59 +0000 (UTC) Cc: emacs-devel@gnu.org To: =?ISO-8859-1?Q?Vincent_Bela=EFche?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Sep 21 19:08:52 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1MpmME-00017a-3U for ged-emacs-devel@m.gmane.org; Mon, 21 Sep 2009 19:07:22 +0200 Original-Received: from localhost ([127.0.0.1]:59852 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MpmMD-00016V-DU for ged-emacs-devel@m.gmane.org; Mon, 21 Sep 2009 13:07:21 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MpmM8-00016Q-BC for emacs-devel@gnu.org; Mon, 21 Sep 2009 13:07:16 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MpmM7-000169-Sb for emacs-devel@gnu.org; Mon, 21 Sep 2009 13:07:16 -0400 Original-Received: from [199.232.76.173] (port=45112 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MpmM7-000162-IM for emacs-devel@gnu.org; Mon, 21 Sep 2009 13:07:15 -0400 Original-Received: from ey-out-1920.google.com ([74.125.78.144]:38244) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MpmM7-0001fB-0J for emacs-devel@gnu.org; Mon, 21 Sep 2009 13:07:15 -0400 Original-Received: by ey-out-1920.google.com with SMTP id 3so1246238eyh.34 for ; Mon, 21 Sep 2009 10:07:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:cc:message-id:from:to :in-reply-to:content-type:content-transfer-encoding:mime-version :subject:date:references:x-mailer; bh=nXnLZm8G8w9orRrhiAatsZFad/8eECUY0FmOtdQFP7k=; b=vORhQUoj+xN2BWetGQreiYkQN2SYaYCmU+yqmfmwXC9grjwJDiDzUY+mV6rTkf7agY QIkmTvtN7qiYFXYCAoj2Mgq8AeY/yoN52rlaLUh6ZLTMuLCMhCwKMgAquqyuhTO1PBUG InS6eblBCv4uPQPqkF9Kj+Zkt993gD/IMkQSk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=cc:message-id:from:to:in-reply-to:content-type :content-transfer-encoding:mime-version:subject:date:references :x-mailer; b=BpHEjk/gaH7KdmxMc1+8Si4L95F84gIaHRq8YAuoiykc0DuOCEJ4EebqqjcmpcFaaG OtL7Tu4c3NsFJt3fG5o3ipNxQ11CZWHXxhb/HExpnApN04kiOYWpBJ5/GSPrnJJNtxPh G1QJ6Ihe7ghjOxYfzQyVxmeLzymRCM+BTTYhM= Original-Received: by 10.216.86.83 with SMTP id v61mr1305406wee.80.1253552831681; Mon, 21 Sep 2009 10:07:11 -0700 (PDT) Original-Received: from Unknown-00-1e-52-73-1c-07.home (host86-165-15-58.range86-165.btcentralplus.com [86.165.15.58]) by mx.google.com with ESMTPS id 7sm2415533eyg.8.2009.09.21.10.07.09 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 21 Sep 2009 10:07:10 -0700 (PDT) In-Reply-To: <87iqfglscc.fsf@gmail.com> X-Mailer: Apple Mail (2.936) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:115497 Archived-At: I have now added the patch to my development version, it will make it into Emacs when I next update there, in about 2 weeks. - Carsten On Sep 18, 2009, at 6:44 AM, Vincent Bela=EFche wrote: > Hello Dominik, > > The Org mode documentation says that Org mode uses ISO time > stamps. Although Org mode date/time format is inspired by ISO, it is =20= > not > fully compliant, see for instance http://fr.wikipedia.org/wiki/=20 > ISO_8601 > on ISO date and time format. > > I corrected the documentation and attached a patch. > > FYI, in ISO date/time format looks like this: > > 2009-09-18T07:16 > > while Org mode is like that > > <2009-09-18 ven. 07:16> > > (this timestamp was generated by `C-c .' on my machine, `ven.' means > `Fri' in French). > > Intervals and are supported by ISO, with a `/' separator, while org =20= > uses > a `-' separator which is ambiguous in ISO (+ or - are used for the =20 > time > zone). > > ISO also supports intervals specified with a duration with the `P' > seperator, such intervals may be defined relative to begin date or > end date > > ISO also supports repetitions with the `R' separator, while Org uses a > `+' separator. > > If ever you want to implement ISO 8601 format into Org, I suggests =20 > that > ISO8601 timesamps/time interval are encapsulated into `' =20 > where > the leading `I' would help Org to disambiguate from native Org mode > format (although in case where `T', `P' or `R' is used, it is possible > to guess it's an ISO format. > > So the example I gave would be: > > > > There could also be some relaxed ISO using an `i' prefix like this: > > > > where the day short name (eg. `ven.') is shown between backets, as =20 > it is > cool to have this information. Relaxed ISO would just strip _anything_ > between brackets before interpreting the timestamp, so it would be =20 > quite > robust to locale stuff (like `ven.' instead of `Fri'). > > Very best regards, > > Vincent. > > PS: I may contribute on this, if you wish. > > > *** org.texi.old Fri Sep 11 19:30:09 2009 > --- org.texi Fri Sep 18 04:59:29 2009 > *************** > *** 4831,4844 **** > @cindex deadlines > @cindex scheduling > > ! A timestamp is a specification of a date (possibly with a time or =20= > a range > ! of times) in a special format, either @samp{<2003-09-16 Tue>} or > @samp{<2003-09-16 Tue 09:39>} or @samp{<2003-09-16 Tue > ! 12:00-12:30>}@footnote{This is the standard ISO date/time format. =20= > To > ! use an alternative format, see @ref{Custom time format}.}. A =20 > timestamp > ! can appear anywhere in the headline or body of an Org tree entry. =20= > Its > ! presence causes entries to be shown on specific dates in the agenda > ! (@pxref{Weekly/daily agenda}). We distinguish: > > @table @var > @item Plain timestamp; Event; Appointment > --- 4831,4844 ---- > @cindex deadlines > @cindex scheduling > > ! A timestamp is a specification of a date (possibly with a time or =20= > a range of > ! times) in a special format, either @samp{<2003-09-16 Tue>} or > @samp{<2003-09-16 Tue 09:39>} or @samp{<2003-09-16 Tue > ! 12:00-12:30>}@footnote{This format is inspired by the standard ISO =20= > 8601 > ! date/time format. To use an alternative format, see @ref{Custom =20 > time > ! format}.}. A timestamp can appear anywhere in the headline or =20 > body of an Org > ! tree entry. Its presence causes entries to be shown on specific =20 > dates in the > ! agenda (@pxref{Weekly/daily agenda}). We distinguish: > > @table @var > @item Plain timestamp; Event; Appointment > *************** > *** 4985,4992 **** > @cindex time, reading in minibuffer > > @vindex org-read-date-prefer-future > ! When Org mode prompts for a date/time, the default is shown as an =20= > ISO > ! date, and the prompt therefore seems to ask for an ISO date. But it > will in fact accept any string containing some date and/or time > information, and it is really smart about interpreting your input. =20= > You > can, for example, use @kbd{C-y} to paste a (possibly multi-line) =20 > string > --- 4985,4993 ---- > @cindex time, reading in minibuffer > > @vindex org-read-date-prefer-future > ! When Org mode prompts for a date/time, the default value is shown =20= > in default > ! date/time format which looks like an ISO date, and the prompt =20 > therefore seems > ! to ask for a date/time in this format. But it > will in fact accept any string containing some date and/or time > information, and it is really smart about interpreting your input. =20= > You > can, for example, use @kbd{C-y} to paste a (possibly multi-line) =20 > string