From: Neil Smithline <emacs-orgmode@neilsmithline.com>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Google Summer of Code -- 3 Org projects for our first participation!
Date: Fri, 4 May 2012 20:19:31 -0400 [thread overview]
Message-ID: <CAH4vb=1CVMaPVRhYC28tJRoDAhQw2kZTua517PvC0Z_WsT=vOQ@mail.gmail.com> (raw)
In-Reply-To: <87ipgij2k5.fsf@altern.org>
[-- Attachment #1: Type: text/plain, Size: 1314 bytes --]
On Sun, Apr 29, 2012 at 4:22 AM, Bastien <bzg@gnu.org> wrote:
>
> One thing to be aware of: there is an ongoing work by Nicolas to write a
> parser (see org-element.el in contrib/lisp/ from the git repo). It is
> already quite useful -- and used in the new exporters (e.g. org-e-latex.el)
>
> One nice side-effect of having this parser is that we will be able to
> document the syntax of Org files more clearly. Actually, org-element.el
> *is* such a description, but we need to make it widely available as a
> documentation page (on Worg).
>
Bastien,
I've looked at org-element.el and don't really see how it will make writing
other Org Mode to HTML converter easier. org-element.el is, well it's
elisp. Very elispy. No surprise but I'm not sure that it can easily be
converted to another language.
Is Nicolas working from a grammar? I think an Org Mode grammar will make
writing parsers much easier. Perhaps I'm just old-school but I think that
generating an Org Mode to HTML converter in another language would be
dramatically simplified by an Org Mode grammar semantic annotations.
Neil
PS: I've been looking at Org Mode utilities in various languages and none
of them seem to handle any sizable portion of Org Mode to HTML conversion.
It seems that there is little for us to use as a starting point.
[-- Attachment #2: Type: text/html, Size: 1651 bytes --]
next prev parent reply other threads:[~2012-05-05 0:19 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-24 5:55 Google Summer of Code -- 3 Org projects for our first participation! Bastien
2012-04-24 7:17 ` Carsten Dominik
2012-04-24 7:18 ` Ian Barton
2012-04-24 8:12 ` Thorsten
2012-04-26 1:42 ` Neil Smithline
2012-04-26 7:48 ` Thorsten Jolitz
2012-04-28 23:12 ` Neil Smithline
2012-04-26 7:57 ` Bastien
2012-04-28 23:30 ` Neil Smithline
2012-04-29 8:26 ` Bastien
2012-04-29 0:20 ` Neil Smithline
2012-04-29 8:22 ` Bastien
2012-05-05 0:19 ` Neil Smithline [this message]
2012-05-05 5:39 ` Bastien
2012-05-05 10:52 ` Bernt Hansen
2012-05-05 9:36 ` Nicolas Goaziou
2012-05-04 22:37 ` Neil Smithline
2012-05-04 21:04 ` Eric Schulte
2012-04-24 9:54 ` Rasmus
2012-04-24 19:00 ` Achim Gratz
2012-04-24 23:16 ` Rasmus
2012-04-26 8:19 ` Bastien
2012-04-24 11:29 ` Richard Riley
2012-04-24 14:19 ` Andrew Young
2012-05-08 3:42 ` Neil Smithline
2012-05-08 8:06 ` Thorsten Jolitz
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='CAH4vb=1CVMaPVRhYC28tJRoDAhQw2kZTua517PvC0Z_WsT=vOQ@mail.gmail.com' \
--to=emacs-orgmode@neilsmithline.com \
--cc=bzg@gnu.org \
--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).