Re: ORG to POD translator

Cool!

OT: Just as only perl can parse Perl, only org-mode can parse Org -- and Org is always changing. For simple documents, a simple script like this is great; for true Org translation, the way to go would be to export HTML or DocBook and work from there. IMHO, Org::Parser is doing it wrong: it's no longer simple, yet it will never truly parse Org.

Comment on Re: ORG to POD translator

Replies are listed 'Best First'.
Re^2: ORG to POD translator by LanX (Saint) on Apr 12, 2011 at 13:08 UTC
>only org-mode can parse Org -- and Org is always changing. you're so right! I was pondering to migrate the regexes from org.el and org-exp.el when I noticed that emphasizes are allowed to spread 2 lines (actually the number of lines is customizable in "Org Emphasis Regexp Components") `/abc def/` [download] This wasn't clear for me since the fontlock in emacs doesn't always get it right. But it's exported to `<i>abc def</i>` [download] So a clean parser would at least need to read the customizations from emacs! Cheers Rolf	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^2: ORG to POD translator
by LanX (Saint) on Apr 12, 2011 at 13:08 UTC

>only org-mode can parse Org -- and Org is always changing.

you're so right! I was pondering to migrate the regexes from org.el and org-exp.el when I noticed that emphasizes are allowed to spread 2 lines (actually the number of lines is customizable in "Org Emphasis Regexp Components")

/abc
def/
[download]

This wasn't clear for me since the fontlock in emacs doesn't always get it right.

But it's exported to

<i>abc def</i>
[download]

So a clean parser would at least need to read the customizations from emacs!

Cheers Rolf

[reply]
[d/l]
[select]