Max Nikulin writes:
> As you have guessed, It is not my choice, it is interface of ox.el and
> org-element.el.
Indeed. Sorry for my haste: it's the consequences of not read the code
carefully :-)
Of course, your orgia-link-procedure could be extended to more org elements.
I can't think of what kind of scenario that might fit in, but as a proof
of concept I find it really stimulating. E.g:
#+begin_src elisp
(org-export-string-as "<orgia:(verse-block () \"Lorem\\nipsum\\ndolor\")>"
'html t)
#+end_src
#+RESULTS:
: <p>
: <p class="verse">
: Lorem<br />
: ipsum<br />
: dolor</p>
: </p>
#+begin_src elisp
(org-export-string-as "<orgia:(quote-block (:attr_latex
(\":environment foreigndisplayquote :options {greek}\"))
\"Δαρείου καὶ Παρυσάτιδος γίγνονται παῖδες δύο, πρεσβύτερος μὲν
Ἀρταξέρξης, νεώτερος δὲ Κῦρος·\")>" 'latex t)
#+end_src
#+RESULTS:
: \begin{foreigndisplayquote}{greek}
: Δαρείου καὶ Παρυσάτιδος γίγνονται παῖδες δύο, πρεσβύτερος μὲνἈρταξέρξης,
νεώτερος δὲ Κῦρος·
: \end{foreigndisplayquote}
> However if you strongly want to use proper terminology in markup, you
> may try to trade it for +your soul+ compatibility and portability
> issues. The following almost works:
Interesting, thank you.
Yes, it is strange the new line added in `evilatex-emph' ... I have no
idea why that happens.
Best regards,
Juan Manuel
