Nick Dokos <ndo...@gmail.com> writes:
> Eric S Fraga <e.fr...@ucl.ac.uk> writes:
>
>> Mirko Vukovic <mirko.vuko...@gmail.com> writes:
>>
>> [...]
>>
>>> Hi Eric,
>>>
>>> Thanks for the note. As it stands now, I cannot
>>> customize these two variables to do what I want, as they accept the
>>> whole time-steamp as argument. I will enter the dates manually
>>> in the org file for now.
>>
>> I thought as much.
>>
>> Looking through the code, some of the functions for outputting the time
>> stamps make use of org-translate-time which does allow some
>> customisation of how the dates and times are written out, along the
>> lines of what you were looking at for DATE entries. Check the
>> documentation for that function. But it could be I've misunderstood the
>> code...
>
> Based on Eric's hint, I followed org-translate-time's docstring (and
> references therein) and I came up with this which seems to work (in the
> sense that the dates look like <2014/02/03 Monday> when exported,
> which agrees with the specified format):
>
> #+STARTUP: customtime
>
> * foo
> <2014-02-03 Mon>
>
> # Local Variables:
> # org-time-stamp-custom-formats: ("<%Y/%m/%d %A>" . "<%Y/%m/%d %A %H:%M>")
> # End:
>
> However, the angle brackets seem to be required.
You could use a filter to get rid of the angle brackets for instance
org-export-filter-timestamp-functions. There's also parse-time-string
together with the relevant DATE-formatting variables that can be used
to recast the appearance of time.
—Rasmus
--
Dung makes an excellent fertilizer
