On 30/05/2023 10:47, Marcin Borkowski wrote:
since I'm going to
call my exporting function in a loop over many elements. I tried
(org-export-with-backend 'html (org-element-at-point (point)))
There is `org-export-string-as', but likely it is not suitable for you.
My guess is that you are going to export headings (blog posts) to
separate html files.
This is /italic/.
can become e.g.
This is <span class="emphasize">italic</span>.
I am curious whether <em> is more friendly to screen readers
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/em
I'm considering writing a custom (derived) export backend, but maybe
that is an overkill? Any ideas?
I just have noticed
(defcustom org-html-text-markup-alist
'((bold . "<b>%s</b>")
(code . "<code>%s</code>")
(italic . "<i>%s</i>")
(strike-through . "<del>%s</del>")
(underline . "<span class=\"underline\">%s</span>")
(verbatim . "<code>%s</code>"))
"Alist of HTML expressions to convert text markup.
You may look into ox-html customizations such as
(:html-doctype "HTML_DOCTYPE" nil org-html-doctype)
(:html-html5-fancy nil "html5-fancy" org-html-html5-fancy)
I have never tried ox-slimhtml:
Laszlo Elo. ox-slimhtml. Mon, 14 Dec 2020 00:48:27 -0500.
https://list.orgmode.org/41d2e10d-bcff-4604-8417-b499514af...@bald.cat
