From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: exporting customized timestamps Date: Wed, 28 Dec 2011 17:29:24 +0100 Message-ID: <87boqpdtug.fsf@altern.org> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([140.186.70.92]:60171) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RguLn-00023k-MU for emacs-orgmode@gnu.org; Sat, 31 Dec 2011 03:31:36 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RguLm-0001CR-DN for emacs-orgmode@gnu.org; Sat, 31 Dec 2011 03:31:35 -0500 Received: from mail-ww0-f49.google.com ([74.125.82.49]:60764) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RguLm-0001CK-92 for emacs-orgmode@gnu.org; Sat, 31 Dec 2011 03:31:34 -0500 Received: by wgbdt11 with SMTP id dt11so19503235wgb.30 for ; Sat, 31 Dec 2011 00:31:33 -0800 (PST) In-Reply-To: (Matt Price's message of "Mon, 29 Aug 2011 10:24:39 -0400") 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: Matt Price Cc: Org Mode Hi Matt, Matt Price writes: > I'm trying to understand timestamps a bit better. I'm exporting my > syllabus to html, using org2blog for my wordpress course site. The > syllabus includes a timestamp at the beginning of each week of the > description. org-time-stamp-custom-formats is set to: > > ("<%m/%d/%Y>" . "<%m/%d/%y %a %H:%M>") > > which is sort of the American standard (sidenote: how do I toggle > between these custom values? I only seem to be able to toggle between > overlaid and not overlaid). > > In Emacs, when I look at my org file, thetimestamp displays just as I > want it to. But on export to HTML, the timestamp returns to the ISO > format ("2011-10-06 Thu"). Is this an inevitable behaviour? For now yes -- the custom format in your Emacs buffer is just an overlay, the real text under this overlay still uses the default format. And the exporter uses this default format. This is the kind of shortcomings that we hope we can solve with the new exporter -- but this needs a lots of rewriting. HTH, -- Bastien