From: Bastien <bzg@altern.org>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: Re: unnumbered subsections in latex export
Date: Thu, 24 Mar 2011 08:59:26 +0100 [thread overview]
Message-ID: <87bp11dk4h.fsf@gnu.org> (raw)
In-Reply-To: <8162r9hgxm.fsf@gmail.com> (Jambunathan K.'s message of "Wed, 23 Mar 2011 23:12:29 +0530")
Dear all,
I applied the patches too hastily, disregarding some inconsistency they
could introduce between exporters -- sorry for that.
I fully agree with Nick and Thomas (and others who also agreed): Org's
export facilities need some real love and new export features need to be
introduced as complete and as consistent accross exporters as possible.
I hope we'll make progress on this for 7.6.
Here is a list of difficulties:
1. the syntax of the backends vary, and this means that all Org options
are not meaningful in all target formats;
*Example*: #+XSLT is only meaninful for the Docbook export. The
variable `org-export-html-postamble' is only meaningful for the HTML
export. Etc.
2. exporters use various methods to export the file (e.g. the HTML
exporter goes line by line, the LaTeX exporter parses the file and
render each section);
*Example*: users often ask why the LaTeX exporter cannot export a
headline of level 3 right after a headline of level 1: they ask that
because the HTML exporter can do this, while the LaTeX one cannot.
And the LaTeX one cannot because parsing an ill-structured Org buffer
is tricky for it.
3. exporters are maintained by various people: I know the HTML exporter
and the LaTeX one, others know the other exporters, etc.
I need your help do deal with these issues.
The first thing to do is to have a list of annoying inconsistencies that
need to be addressed in priority.
The second thing would be to build a table (somewhere on Worg?) with the
list of options and the way they are taken care by each exporter. Such
a "synoptic view" would help developers know what they can work on, and
users know what they have to expect from options. On the long term, it
would also help make the documentation clearer about all these aspects.
This will at least help with the first difficulty -- and motivate all
people working on the exporters to address the second one. The third
one can be turned into a *chance*: that of having several people working
in the same direction.
So, bare with me on this :)
PS: Also note that I couldn't be as available as I wanted the 10 last
days due to personal problems, but things look better now.
--
Bastien
next prev parent reply other threads:[~2011-03-24 8: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 [this message]
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
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=87bp11dk4h.fsf@gnu.org \
--to=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).