Lukas Epple <em...@lukasepple.de> writes: >> What is the motivation behind changing -- to EN DASH? > > This is not really a change. Previously, `org-html-timestamp' would > perform this replacement, but not `org-html-planning' nor > `org-html-clock'. When refactoring the code to use a common function > between these three functions, I decided to move the > `replace-regexp-in-string` into the common `org-html--format-timestamp' > rather than keep this replacement exclusive to `org-html-timestamp'. I > could revert this, but think it's better this way for consistency. > > I've tried to clarify what changed in the updated commit message, too.
Thanks! Just two more comments. > +*** Fancy HTML5 export uses ~<time>~ element for timestamps > +Previously, timestamps would always be rendered inside a ~<span > +class="timestamp">~. Now, if both ~org-html-doctype~ is ~html5~ and > +~org-html-html5-fancy~ is enabled, org will now use the semantically > +appropriate ~<time>~ element. This will also use the ~timestamp~ class, > +but additionally set the ~datetime~ attribute with a machine readable > +variant of the timestamp. The format used for the attribute can be > +customized using ~org-html-datetime-attribute-date-timestamp-format~ > +and ~org-html-datetime-attribute-full-timestamp-format~. 1. You forgot to update the variable names from previous versions of the patch 2. :Now, ..., org will now use:. One "now" can be removed. -- Ihor Radchenko // yantar92, Org mode maintainer, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>
