Hello, Eric Abrahamsen <e...@ericabrahamsen.net> writes:
> I'm not sure the general export engine is going to be of much use, > since XML is so completely flexible, but you'll definitely want to > build it on top of the internal parser. It would be a bad idea not to use the export framework, unless you want to reinvent the wheel (e.g., re-implementing skipping of :noexport: tags). > Luckily, the parser turns an org subtree into a parse tree, and the > function `xml-print' turns a parse tree into XML. They're not quite the > same parse tree, but I guess you'll want to do something like this: > > > #+BEGIN_SRC org > ,* My Great Playlist > ,** The Cold Cold Ground.mp3 > :PROPERTIES: > :OPML_TYPE: song > :OPML_F: Tom Waits - The Cold Cold Ground > :END: > ,** Don't Eat the Yellow Snow.mp3 > :PROPERTIES: > :OPML_TYPE: song > :OPML_F: Frank Zappa - Don't Eat the Yellow Snow > :END: > #+END_SRC > > > | > | > org-element--parse-elements Please use `org-element-parse-buffer' instead. As the two consecutive hyphens suggest, this is an internal function. Regards, -- Nicolas Goaziou