emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Brett Viren <bv@bnl.gov>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Org mode and "shunt" exporters?
Date: Fri, 6 Dec 2013 08:02:24 -0500	[thread overview]
Message-ID: <CAJ51ETo-kk=5MM1b3WASmUCGugfmvaGA8=Us38gZrHH=jo8FXw@mail.gmail.com> (raw)
In-Reply-To: <ir4pppbm46i.fsf@lycastus.phy.bnl.gov>

[-- Attachment #1: Type: text/plain, Size: 2000 bytes --]

that sounds like an interesting approach. xml seems like what you really
want, since looking at the parsetree there is a lot of information (e.g.
attributes, properties, etc...) that would be tricky to generate a fully
representative json scheme.

This page suggests at the bottom you could export to texinfo, and convert
that to docbook:
http://orgmode.org/worg/exporters/ox-overview.html


   - (1) DocBook export, available in previous Org-mode versions, has not
   currently been ported to the new exporter, however the new
ox-texinfobackend can generate DocBook format. Once
   file.texi is created via ox-texinfo, simply execute:

makeinfo --docbook file.texi




John

-----------------------------------
John Kitchin
Associate Professor
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
http://kitchingroup.cheme.cmu.edu



On Thu, Dec 5, 2013 at 3:30 PM, Brett Viren <bv@bnl.gov> wrote:

> Has anyone written any new-style exporter which will produce a common
> markup/data language format like JSON or YAML?  I'm looking for
> something that fully preserves the original org document structure and
> does no semantic interpretation along the way.
>
> What I really want is to parse arbitrary org files in Python.  I've
> looked at the entries at worg's "org-tool" node which do this but they
> seem out of date or make assumptions about what org elements exist or
> their URLs are not loading (NEO).  If any of that's a misrepresentation
> please correct me.
>
> In any case, using org's own exporter to produce JSON or YAML and then
> relying on these format's Python modules for parsing seems like the best
> way to go to let me author in org and process in Python.
>
> I'm not very good with elisp (which is why I want to get org data into
> Python) but I guess I can have a go at making such a "shunt" exporter.
> Before I try, I just wanted to check if someone had this wheel already
> spinning.
>
> Thanks,
> -Brett.
>

[-- Attachment #2: Type: text/html, Size: 2774 bytes --]

  parent reply	other threads:[~2013-12-06 13:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-05 20:30 Org mode and "shunt" exporters? Brett Viren
2013-12-06  2:10 ` Eric Schulte
2013-12-09 17:38   ` Brett Viren
2013-12-09 19:55     ` Nicolas Goaziou
2013-12-13 18:26       ` Brett Viren
2013-12-13 19:05         ` Nicolas Goaziou
2013-12-13 19:29           ` Eric Schulte
2013-12-13 23:06             ` Brett Viren
2013-12-06 13:02 ` John Kitchin [this message]
2013-12-12 16:30   ` Brett Viren
2013-12-12 17:22     ` John Kitchin
2013-12-12 19:24       ` Eric Schulte
2013-12-12 19:50       ` Aaron Ecay
2013-12-12 19:58         ` Matt Price
2013-12-13  2:53           ` John Kitchin
2013-12-13 19:02           ` Brett Viren

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJ51ETo-kk=5MM1b3WASmUCGugfmvaGA8=Us38gZrHH=jo8FXw@mail.gmail.com' \
    --to=jkitchin@andrew.cmu.edu \
    --cc=bv@bnl.gov \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).