From: Matt Lundin <mdl@imapmail.org>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: Bastien <bzg@altern.org>, nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: unnumbered subsections in latex export
Date: Mon, 04 Apr 2011 10:00:18 -0400 [thread overview]
Message-ID: <87aag66rrh.fsf@fastmail.fm> (raw)
In-Reply-To: <877hbernbs.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Fri, 01 Apr 2011 16:41:27 +0100")
Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> Jambunathan K <kjambunathan@gmail.com> writes:
>
> [...]
>
>> I think one of the reasons Org is so popular it is that it is a
>> common-man's swiss army knife and not a elitist samurai sword.
>
> And I think this is a very important analogy. Org does a good job for
> many (very different) tasks. The price is that it does not necessarily
> do some of those tasks as well as could be.
>
> I am happy to put with the rough edges exposed by the exporters because
> of what the whole package provides. Case in point: I submitted a paper
> yesterday which I wrote in org. However, for the submission, once I was
> happy with all the content, I had to tweak the latex to meet the
> journal's format because they provide a style file which requires title,
> author, etc. to come *after* the \begin{document}.
I agree that the org-exporter currently does its job very well. The
astounding utility of org-mode is ample proof of the value of releasing
early; even if the exporter is not as elegant as a modern compiler, it
works. :)
That said, I very much support Nicolas' proposal. Right now, the issue
is not so much the end user's experience as it is the ease of
maintaining and developing the backends. We obviously don't want org to
be as strict as xml --- i.e., the a new export parser should be somewhat
forgiving. But a more abstract approach would make it easier to build
new backends or fix bugs that effect all of the backends. One might even
develop an org backend -- i.e., export functions that take the data
produced by the parser and spit out an Org-mode syntax. One might then
write importers that parse other types of files (mediawiki, markdown,
latex, etc.) and return the data structure expected by org-exp.el. Of
course, this latter possibility may not be necessary, given that pandoc
can already convert to org files. :)
Best,
Matt
next prev parent reply other threads:[~2011-04-04 14:00 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-22 12:10 unnumbered subsections in latex export Suvayu Ali
2011-03-22 12:20 ` Sébastien Vauban
2011-03-22 12:31 ` Suvayu Ali
2011-03-22 12:56 ` Sébastien Vauban
2011-03-22 14:26 ` [PATCH] Allow mixed export of numbered and unnumbered sections in LaTeX Lawrence Mitchell
2011-03-22 22:52 ` Suvayu Ali
2011-03-23 14:04 ` [Accepted] " Bastien Guerry
2011-03-23 14:17 ` [PATCH] " Bastien
2011-03-22 14:35 ` Re: unnumbered subsections in latex export Nick Dokos
2011-03-22 23:08 ` Suvayu Ali
2011-03-22 23:21 ` Nick Dokos
2011-03-23 9:38 ` [PATCH] Allow mixed export of numbered and unnumbered sections in HTML Lawrence Mitchell
2011-03-23 14:05 ` [Accepted] " Bastien Guerry
2011-03-23 14:57 ` Nick Dokos
2011-03-23 15:50 ` Suvayu Ali
2011-03-23 14:18 ` Re: unnumbered subsections in latex export Bastien
2011-03-23 15:02 ` Nick Dokos
2011-03-23 16:25 ` Lawrence Mitchell
2011-03-23 16:42 ` Nick Dokos
2011-03-23 18:17 ` Jambunathan K
2011-03-23 19:00 ` Nick Dokos
2011-03-23 19:18 ` Jambunathan K
2011-03-23 16:29 ` Thomas S. Dye
2011-03-23 17:42 ` Jambunathan K
2011-03-24 7:59 ` Bastien
2011-03-24 18:27 ` Achim Gratz
2011-03-24 19:25 ` Nick Dokos
2011-03-25 1:06 ` Suvayu Ali
2011-04-04 14:39 ` Sébastien Vauban
2011-04-04 17:04 ` Nick Dokos
2011-04-04 20:32 ` Aankhen
2011-04-05 10:16 ` Sébastien Vauban
2011-04-05 19:07 ` Aankhen
2011-04-05 19:27 ` Eric S Fraga
2011-04-05 21:25 ` New features for the exporters? Sébastien Vauban
2011-04-05 21:45 ` Re: unnumbered subsections in latex export Aankhen
2011-04-06 18:49 ` Matt Lundin
2011-04-06 20:19 ` Sébastien Vauban
2011-03-27 11:16 ` Jambunathan K
2011-03-27 11:40 ` Bastien
2011-03-31 21:58 ` Nicolas
2011-04-01 4:34 ` Jambunathan K
2011-04-01 4:41 ` Jambunathan K
2011-04-01 6:29 ` Nick Dokos
2011-04-01 15:41 ` Eric S Fraga
2011-04-04 14:00 ` Matt Lundin [this message]
2011-04-04 14:12 ` Jambunathan K
2011-04-04 16:36 ` Matt Lundin
2011-04-04 17:09 ` Nick Dokos
2011-04-01 7:39 ` Jambunathan K
2011-04-01 18:25 ` 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=87aag66rrh.fsf@fastmail.fm \
--to=mdl@imapmail.org \
--cc=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
--cc=kjambunathan@gmail.com \
--cc=nicholas.dokos@hp.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).