From: Brett Viren <bv@bnl.gov>
To: John Kitchin <jkitchin@andrew.cmu.edu>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Org mode and "shunt" exporters?
Date: Thu, 12 Dec 2013 11:30:14 -0500 [thread overview]
Message-ID: <ir4bo0mjall.fsf@lycastus.phy.bnl.gov> (raw)
In-Reply-To: <CAJ51ETo-kk=5MM1b3WASmUCGugfmvaGA8=Us38gZrHH=jo8FXw@mail.gmail.com> (John Kitchin's message of "Fri, 6 Dec 2013 08:02:24 -0500")
[-- Attachment #1: Type: text/plain, Size: 2153 bytes --]
Hi John,
John Kitchin <jkitchin@andrew.cmu.edu> writes:
> 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.
I see from your other thread that you are looking in to this idea of
dumping to JSON. That's great! If you want a tester of your JSON
exporter I'd be very happy to give it a try. If it means I can abandon
my own stumbling around, that would make me even happier.
But, I am still slowly messing with this myself. I plan to next follow
Nicolas's suggestion of simply removing the :parent parameter to get
over the hurdle that the circular object caused me. I think if the
overall structure of the parse tree is preserved in the JSON then
parentage can be restored when it is read back.
I've also thought a bit about schema issues. Regardless of how an "org
schema" might be represented, it would be best if it could be generated
From org instead of hand crafted. This would need a kind of a "meta
export" feature. I've not yet checked to see if there is some facility
in org to exploit to do this. Maybe someone knows?
In the past I've expressed schema descriptions for JSON data in JSON
itself. Internet searches now show this is not a novel approach so I
think there is some fruit to be found pursuing this direction. Or, I
may just be trying too hard to avoid XML....
> 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-texinfo backend can generate DocBook format. Once file.texi is
> created via ox-texinfo, simply execute:
>
> makeinfo --docbook file.texi
Thanks. I did try this but makeinfo failed on the texinfo file that was
produced. I didn't pursue it enough to figure out why or if I was doing
something wrong.
-Brett.
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2013-12-12 16:31 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
2013-12-12 16:30 ` Brett Viren [this message]
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=ir4bo0mjall.fsf@lycastus.phy.bnl.gov \
--to=bv@bnl.gov \
--cc=emacs-orgmode@gnu.org \
--cc=jkitchin@andrew.cmu.edu \
/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).