From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Neil Smithline <emacs-orgmode@neilsmithline.com>
Cc: Bastien <bzg@gnu.org>, emacs-orgmode@gnu.org
Subject: Re: Google Summer of Code -- 3 Org projects for our first participation!
Date: Sat, 05 May 2012 11:36:59 +0200 [thread overview]
Message-ID: <87wr4r55qc.fsf@gmail.com> (raw)
In-Reply-To: <CAH4vb=1CVMaPVRhYC28tJRoDAhQw2kZTua517PvC0Z_WsT=vOQ@mail.gmail.com> (Neil Smithline's message of "Fri, 4 May 2012 20:19:31 -0400")
Hello,
Neil Smithline <emacs-orgmode@neilsmithline.com> writes:
> 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?
Since org-element can parse 98%[1] of Org syntax, there must be
a grammar defined somewhere. When I started org-element, there was no
structural definition of Org syntax (there wasn't even a full list of
syntactic objects). Now, org-element is the grammar embodied in elisp.
Alas, I have no plan to formalize it. Though, I agree that it would be
a great thing to have in order to implement equivalent parsers in other
languages.
If someone wants to study org-element and extract a formal grammar out
of it, I will gladly help him in the process.
Otherwise, you can use the intermediary representation of an Org
document. org-element can produce the representation and read the
representation to produce an Org document.
#+begin_src emacs-lisp
(org-element-interpret-data
'(org-data
nil
(headline
(:level 1 :title ("It works") :priority ?A :todo-keyword "TODO" :tags ("test"))
(section
nil
(center-block
nil
(paragraph nil "Really"))))))
#+end_src
Thus, you may only need to write converters from that representation to
another syntax (like HTML). That's the purpose of org-export and its
back-ends.
Regards,
[1] I still don't know what to do with "under\_line": there is no
`kludge' object type so far (!).
--
Nicolas Goaziou
next prev parent reply other threads:[~2012-05-05 9:39 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
2012-05-05 5:39 ` Bastien
2012-05-05 10:52 ` Bernt Hansen
2012-05-05 9:36 ` Nicolas Goaziou [this message]
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=87wr4r55qc.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=emacs-orgmode@neilsmithline.com \
/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).