From mboxrd@z Thu Jan 1 00:00:00 1970 From: Brett Viren Subject: Re: Org mode and "shunt" exporters? Date: Thu, 12 Dec 2013 11:30:14 -0500 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:54560) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vr9AF-0005sv-Tz for emacs-orgmode@gnu.org; Thu, 12 Dec 2013 11:31:08 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Vr9AB-0007Wg-3v for emacs-orgmode@gnu.org; Thu, 12 Dec 2013 11:31:03 -0500 Received: from smtpgw.bnl.gov ([2620:10a:0:3::30]:33192 helo=iron3.sec.bnl.local) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vr9AA-0007Um-Vx for emacs-orgmode@gnu.org; Thu, 12 Dec 2013 11:30:59 -0500 In-Reply-To: (John Kitchin's message of "Fri, 6 Dec 2013 08:02:24 -0500") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: John Kitchin Cc: "emacs-orgmode@gnu.org" --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hi John, John Kitchin 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.=20 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=20org 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:=20 > > 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. =2DBrett. --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlKp5JYACgkQEixH2Z0dKCwBzgCgp11KYaV2zxCOYYOwzyltcfxq pecAnjWCC4B5aGYivt2SFP5FyW4AF93L =NMw7 -----END PGP SIGNATURE----- --=-=-=--