From: Giovanni Giorgi <jj@gioorgi.com>
To: Bastien <bzg@altern.org>
Cc: charlesweb@optusnet.com.au, Emacs orgmode <emacs-orgmode@gnu.org>,
Eric Schulte <eric.schulte@gmx.com>
Subject: Re: [ANN] Org Mode parser v0.0.1 for NodeJs
Date: Mon, 12 Dec 2011 22:19:57 +0100 [thread overview]
Message-ID: <5B803A95-6626-4C1D-A302-DB9FCC19FDA1@gioorgi.com> (raw)
In-Reply-To: <87wra2u230.fsf@gnu.org>
Hi,
sorry for my late response.
I have little time right now, but I think org-mode could be integrated.
The current node.js org-mode parser is not designed to take care of the content of a paragraph (for instance it will not be able to detect numbered lists), and I fear this is its major weak point.
But for the rest, I have done some tests and the parser is quite robust.
Please grab the last version from npm, it has a good set of unit tests
On 12/dic/2011, at 00.21, Bastien wrote:
> Eric Schulte <eric.schulte@gmx.com> writes:
>
>> This is the first I've seen of substance.io, it looks very interesting.
>> I wonder how similar the substance document data structure is to the new
>> org-parse data structure, and if it would be difficult or rewarding to
>> write a translator between the two.
>
> I wonder the same -- I guess we'll all have more insight when we try
> writing new exporter with the new export engine. Just though it was
> good to throw this reference early enough...
>
> --
> Bastien
prev parent reply other threads:[~2011-12-12 21:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-04 21:34 [ANN] Org Mode parser v0.0.1 for NodeJs Giovanni Giorgi
2011-10-05 1:43 ` Marcelo de Moraes Serpa
2011-10-05 15:21 ` Chris Malone
2011-10-05 15:56 ` Giovanni Giorgi
2011-10-06 14:57 ` Eric Schulte
2011-10-29 10:46 ` Bastien
2011-12-11 13:41 ` Bastien
2011-12-11 18:04 ` Eric Schulte
2011-12-11 23:21 ` Bastien
2011-12-12 21:19 ` Giovanni Giorgi [this message]
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=5B803A95-6626-4C1D-A302-DB9FCC19FDA1@gioorgi.com \
--to=jj@gioorgi.com \
--cc=bzg@altern.org \
--cc=charlesweb@optusnet.com.au \
--cc=emacs-orgmode@gnu.org \
--cc=eric.schulte@gmx.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).