emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Eric Schulte" <schulte.eric@gmail.com>
To: Wes Hardaker <wjhns209@hardakers.net>
Cc: emacs-orgmode mailing list <emacs-orgmode@gnu.org>,
	Carsten Dominik <carsten.dominik@gmail.com>
Subject: Re: Formal description of Org files
Date: Fri, 15 Apr 2011 11:29:02 -0600	[thread overview]
Message-ID: <877hav8lup.fsf@gmail.com> (raw)
In-Reply-To: <sdfwpj38bt.fsf@wjh.hardakers.net> (Wes Hardaker's message of "Fri, 15 Apr 2011 07:20:06 -0700")

If one goal of such a formal description of Org-mode would be to parse
text Org-mode files into an abstract syntax tree (which is reminiscent
of [1] and [2]) then perhaps we should look at parsers which have
already been applied to other document languages (e.g. tex, html etc...)
or at least support xml output.  If such parsers exist and have been
widely applied, then maybe they could support the exportation of
Org-mode files, or even automate the writing of code for such exporters?

Best -- Eric

Wes Hardaker <wjhns209@hardakers.net> writes:

>>>>>> On Fri, 15 Apr 2011 09:58:09 +0200, Carsten Dominik
> <carsten.dominik@gmail.com> said:
>
> CD> Unfortunately I did not catch the name of the format description
> CD> language that could be used for something, not did I catch the name
> CD> of the person who talked to me.
>
> Another option, besides those mentioned, is probably ABNF.


Footnotes: 
[1]  the effort to unify exporting behind a single parser of Org-mode
     files into an abstract elisp tree

[2]  http://johnmacfarlane.net/pandoc/, which as I recall has an
     Org-mode backend

-- 
Eric Schulte
http://cs.unm.edu/~eschulte/

  reply	other threads:[~2011-04-15 17:29 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-15  7:58 Formal description of Org files Carsten Dominik
2011-04-15  8:54 ` Rainer Stengele
2011-04-15 10:57   ` Carsten Dominik
2011-04-15 11:50     ` Peter Frings
2011-04-15 12:05       ` Carsten Dominik
2011-04-15 15:25         ` Jambunathan K
2011-04-20 11:57           ` Olaf.Hamann
2011-04-15 12:58 ` Christian Egli
2011-04-15 13:42   ` Peter Frings
2011-04-15 13:52     ` Filippo A. Salustri
2011-04-15 14:20 ` Wes Hardaker
2011-04-15 17:29   ` Eric Schulte [this message]
2011-04-15 18:31     ` Nick Dokos
2011-04-20 12:37       ` Olivier Schwander
2011-07-15 18:07         ` Marcelo de Moraes Serpa
2011-07-16 16:56           ` Bastien
2011-07-16 17:09             ` Nick Dokos
2011-07-16 17:12               ` Bastien
2011-07-16 18:00               ` Searching the org list (was: Formal description of Org files) Memnon Anon
2011-07-16 18:21               ` Formal description of Org files suvayu ali
2011-07-16 18:43                 ` Nick Dokos
2011-07-17 23:14             ` Eric Schulte
2011-07-18  9:30               ` Christopher Witte
2011-07-18 23:32               ` Bastien
2011-07-18 21:02             ` Marcelo de Moraes Serpa
2011-07-18 21:03               ` Marcelo de Moraes Serpa
2011-07-18 11:04           ` Nicolas Goaziou
2011-07-18 23:35             ` Bastien
2011-07-19  6:16             ` Jambunathan K
2011-07-24 18:58               ` Bastien
  -- strict thread matches above, loose matches on Subject: below --
2011-04-15 17:13 Rustom Mody
2011-04-15 17:27 ` MidLifeXis at PerlMonks
2014-09-21 12:10 Gustav Wikström
2014-09-21 12:43 ` Nicolas Goaziou
2014-10-02  8:28   ` Samuel Loury
2014-10-02 17:03     ` Nicolas Goaziou
2014-10-04 19:49   ` Gustav Wikström
2014-09-26  8:12 ` Eric S Fraga
2014-09-26 12:53   ` Grant Rettke
2014-09-26 20:51     ` Eric S Fraga
2014-10-04 19:41   ` Gustav Wikström
2014-10-06 14:22     ` Samuel Loury

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=877hav8lup.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=wjhns209@hardakers.net \
    /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).