Hi, Here's a new version that uses :RSS_TITLE. Do you think it's good enough for a first patch? I'll work on the export back-end, but that'll take some more time.
diff --git a/contrib/lisp/ox-rss.el b/contrib/lisp/ox-rss.el index fddaa1d..5617d26 100644 --- a/contrib/lisp/ox-rss.el +++ b/contrib/lisp/ox-rss.el @@ -244,11 +244,12 @@ communication channel." (format-time-string "%a, %d %b %Y %H:%M:%S %z" (org-time-string-to-time pubdate0))))) - (title (replace-regexp-in-string - org-bracket-link-regexp - (lambda (m) (or (match-string 3 m) - (match-string 1 m))) - (org-element-property :raw-value headline))) + (title (or (org-element-property :EXPORT_TITLE headline) + (replace-regexp-in-string + org-bracket-link-regexp + (lambda (m) (or (match-string 3 m) + (match-string 1 m))) + (org-element-property :raw-value headline)))) (publink (or (and hl-perm (concat (or hl-home hl-pdir) hl-perm)) (concat
Cheers, Nico Nicolas Goaziou <m...@nicolasgoaziou.fr> writes: > Hello, > > Nicolas Petton <nico...@petton.fr> writes: > >> I'm a happy user of ox-rss.el, but was annoyed the other day when I >> wanted to export an article with a headline containing markup. > > What problem did you encounter? > >> The problem is that org-rss-headlines uses the raw-value of the headline >> to export the title, which could contain any markup. > > Actually, an export back-end isn't expected to use :raw-value. > > One way to handle this is to create an anonymous export back-end that > strips unwanted objects, or export them differently (e.g., a link is > exported as its description, if any, or its path). See, for example > `org-html--format-toc-headline'. > >> Here's a patch that uses the :EXPORT_TITLE property if present, >> :raw-value if not. > > :EXPORT_TITLE is meant to replace #+TITLE: during a subtree export. > There is ALT_TITLE property, but this is usually used in table of > contents. > > > Regards, -- Nicolas Petton http://nicolas-petton.fr
