Nicolas Goaziou <m...@nicolasgoaziou.fr> writes:
>> 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? 'Cause usually org-export-data gives you the right value automatically. Anyway, I don't mind using org-element-parse-secondary-string. >> 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. I don't oppose that. > 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". Keywords should also be printed in the document as well IMO, e.g. after the abstract. An example of where you need markup: σ-algebra. —Rasmus -- Slowly unravels in a ball of yarn and the devil collects it
