From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: Bug: export failed when using footnotes inside src blocks [7.7]
Date: Sun, 31 Jul 2011 20:41:05 +0200 [thread overview]
Message-ID: <87mxfuuwce.fsf@Rainer.invalid> (raw)
In-Reply-To: 87zkjwyrlr.fsf@gmail.com
Nicolas Goaziou <n.goaziou@gmail.com> writes:
> _Note to self_ : I really wish we can come up with an exporter that
> exactly matches Org syntax. An element recognized/ignored in Org should
> be identically recognized/ignored during the export process without
> resorting to any trick (à la `org-protected' text property).
Your remark reminded me that I should look at the generic exporter in
contrib. It needs an eval-while-compile wrapped (require 'cl) to
compile and run cleanly. It also doesn't appear to recognize tables (or
those are still copies from the ASCII export?). It looks like it works
line-by-line, which seems a somewhat questionable choice, but then it
was written for Org6.25…
I think it boils down to the question of having a formal org syntax. If
that existed, all exporters (and much of the org core, I guess) could
work on the parse tree (some list structure with lists as elements and
the actual text as their leaf nodes) of the org document.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables
next prev parent reply other threads:[~2011-07-31 18:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-30 8:22 Bug: export failed when using footnotes inside src blocks [7.7] Günter Kolousek
2011-07-30 9:00 ` Nick Dokos
2011-07-30 9:19 ` Jambunathan K
2011-07-30 9:58 ` Nick Dokos
2011-07-30 10:53 ` Jambunathan K
2011-07-30 10:45 ` Nicolas Goaziou
2011-07-30 14:34 ` Günter Kolousek
2011-07-31 18:41 ` Achim Gratz [this message]
2011-07-31 19:12 ` Jambunathan K
2011-08-14 16:29 ` Bastien
2011-08-14 16:25 ` Bastien
2011-08-14 16:54 ` Achim Gratz
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=87mxfuuwce.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--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).