Re^2: ORG to POD translator

Well I wouldn't mind if _you_ put it on git-hub! :)

(this already took more time that I wanted to spend)

I once started a thread "[emacs] converting perl regex into elisp regex", that could be of help for understanding the original format definition and parsing for updates in the lisp files.

Those other features you want shouldn't be to difficult to parse, the question is what kind of POD should they produce?

And how is the interface supposed to look like?

If you have an agenda please define it.

Cheers Rolf

Comment on Re^2: ORG to POD translator

Replies are listed 'Best First'.
Re^3: ORG to POD translator by MidLifeXis (Monsignor) on Apr 07, 2011 at 22:33 UTC
The closest thing that I would have for an agenda would be to have a defined format for the org file itself. I would like to see the org community adopt a format for the org file, and a set of core functions (dealing with manipulating files, nodes, and properties) that behave in a defined fashion. Beyond that, it is basically up to the interface / library how it behaves based on the content of the file. Update: It looks like someone else may have some similar thoughts. --MidLifeXis	[reply]
Re^4: ORG to POD translator by LanX (Saint) on Apr 07, 2011 at 22:42 UTC
Thats quite abstract and overwhelming. IMHO formulating concrete use cases and goals is the first step for improvement. Producing POD is pretty concrete, and not far from being sufficiently done. What do you want to produce? Do you want to support all export formats emacs knows? I'm not such a heavy org-mode user like you are, you need to formulate your needs. Cheers Rolf	[reply]
Re^5: ORG to POD translator by MidLifeXis (Monsignor) on Apr 07, 2011 at 22:59 UTC
With this one-off script, no. The script is good at what it does. My comments were only things that jumped out as low-hanging fruit. In fact, beyond those couple of changes, I would probably not make any other changes to this. My goal for processing org-mode files with Perl (not this script) would be as I listed above - manipulating the files, nodes, and properties / drawers. educated_foo stated below, "only org-mode can parse Org". I agree with that mostly. I would love to see the org community stabilize the format, and let org-mode (or Vaporware::Org-mode.pm) respond to the data within that format. The content of the properties and nodes, based on how the configuration is set, determine how the library reacts. This script solves a very focused problem, and I am not suggesting that that scope be broadened, just that some of the edge cases in parsing some of the org-mode files that may be seen get fixed. --MidLifeXis	[reply]
Re^3: ORG to POD translator by MidLifeXis (Monsignor) on Apr 07, 2011 at 23:12 UTC
I see in rereading this that my comment about the source for the emacs regexp was misunderstood. I did not mean to imply that all of the other block types contained in that regexp should be parsed, I was only commenting on the possible formats that a "BEGIN_SRC" block could take. The link to Org::Parser was a reference to the unlinked reference (now linked in a footnote), not an indicator that you should use it in this script. The suggestion for github was to make it more readily able to have patches applied to it. --MidLifeXis	[reply]
Re^4: ORG to POD translator by LanX (Saint) on Apr 08, 2011 at 01:15 UTC
OK, I created my first account on git hub: http://github.com/LanX/org2pod/ lets see were this will lead to. :) I think Org::Parser is already what you want, you might wanna have a look at this conversation: http://thread.gmane.org/gmane.emacs.orgmode/40388 Cheers Rolf	[reply]