Hello, Rasmus <ras...@gmx.us> writes:
> Nicolas Goaziou <m...@nicolasgoaziou.fr> writes: > >>> + (?k . ,(or (plist-get info :keywords) "")) >>> + (?d . ,(or (plist-get info :description) "")) > > So it occurred to me that these should also be exported to proper syntax > so we don't end up with e.g. a raw $ or & in our latex document. Hyperref > will actually handle it, but usually by discarding offending characters. > > However, since they are plain strings something like \alpha will be > exported as $\backslash$lpha. I can kind of get it interpreting using > org-element-parse-secondary-string, but this is not the right > approach. Why isn't it the right approach? > Is there a reason why DESCRIPTION and KEYWORDS can't have formatting? DESCRIPTION could be moved to `org-element-document-properties'. But then, we need to introduce `org-export-with-description', which implies export back-ends have to deal with it somehow (ATM "ox-ascii" ignores it). Another option is to simply remove DESCRIPTION from "ox.el" and let export back-ends in need of it to add it to their definition. However, I don't see why KEYWORDS should accept markup. I also think it should be moved to back-end definitions instead of "ox.el". Regards, -- Nicolas Goaziou
