Hello,
Arun Isaac writes:
> Subject: [PATCH] ox-rss: Encode characters to their XML entities
>
> * contrib/lisp/ox-rss.el (org-rss-build-channel-info, org-rss-headline):
> Encode disallowed characters in `title' to their XML entities
>
> The `title' field is user
> I think my patch introduces a bug in `org-rss-build-channel-info'. I'll
> fix this and send a new patch soon.
I didn't realize (plist-get info :title) returns a list, and not a
string. I have now fixed the bug. Please find attached a new patch.
signature.asc
Description: PGP signature
> Please find attached the patch.
I think my patch introduces a bug in `org-rss-build-channel-info'. I'll
fix this and send a new patch soon.
signature.asc
Description: PGP signature
>> I can provide a patch for this.
Please find attached the patch.
> Since "ox-rss.el" loads "ox-html", could you re-use code in the latter?
I think even ox-html could benefit from using an XML/HTML generation
library that can convert s-expressions to XML/HTML. xml.el has
`xml-parse-region'
Hello,
Arun Isaac writes:
> I can provide a patch for this.
Thank you.
> But, do I use an external library like xmlgen
> (https://github.com/philjackson/xmlgen), or do I write my own find and
> replace functions like those in ox-html?
Since "ox-rss.el" loads
The ox-rss exporter does not replace characters (such as < , > , etc.)
by their corresponding XML entities ( , , etc.) in the
field of the generated XML.
For example, the following org file, when exported, will produce invalid
XML where the field still contains the disallowed "<" character.