At Fri, 11 Mar 2011 10:10:08 +0100, Daniel Clemente wrote: > > > I tracked down this problem to this commit: > > > 163cd58ffd6461c98a96b1b63a3cf082b2825a52 is the first bad commit > commit 163cd58ffd6461c98a96b1b63a3cf082b2825a52 > Author: David Maus > Date: Fri Jan 14 06:37:52 2011 +0100 > > Handle timestamps after handling links Thanks for tracking this down. I just pushed two commits that should fix the problem. The first reverts commit ca69b556241ae904c5f291c98a6453f4ce830557 Author: Jason Dunsmore Date: Tue Feb 1 17:46:57 2011 +0100 Fix bug when exporing inactive timestamps. * org-html.el (org-html-handle-time-stamps): fix bug when exporing inactive timestamps. This commit addressed the problem introduced by 163cd58ffd6461c98a96b1b63a3cf082b2825a52 but in a way that is incompatible with the "right" fix. My faulty commit not just changed the order of handling links and handling timestamps but also prevented the left angle bracket of an active timestamp from beeing protected from conversion to a HTML character entity (i.e. <). The (hopefully) final fix moves expanding character entities after handling links and timestamps. Best, -- David -- OpenPGP... 0x99ADB83B5A4478E6 Jabber.... dmjena@jabber.org Email..... dmaus@ictsoc.de