Open semente opened 3 years ago
this is a very interesting issue. I think this might have been caused by the fact that the title needs to be captured when it's not formatted by ox-html
so it can go within the head's <title></title>
tag. Maybe the title should be treated like the post.html
property. If it contains org-mode, it should probably be unsafe by default. I feel like it'd be more consistent.
What do you think? It'd be a breaking change, but we'd get a more consistent behavior on escaping.
Yea, agree. What you suggest is more consistent. #+SUBTITLE
and #+DESCRIPTION
are also Org export keywords and should behave the same as #+TITLE
as well, I guess.
And perhaps post.html
should be renamed to post.content
too.
Let's say I have the following title in a post:
I would to render it in HTML when using
{{ post.title }}
. Maybe have ahtml
template filter to do this org-to-html conversion:{{ post.title|html }}
(which could be "|safe" by default).Currently I can use
#+TITLE: This is the <i>title</i>
and{{ post.title|safe }}
just fine but if I, let's say, try to publish this same Org file to PDF using org-publish I won't have the desired results.