From: Lawrence Mitchell <wence@gmx.li>
To: emacs-orgmode@gnu.org
Subject: Re: unnumbered subsections in latex export
Date: Wed, 23 Mar 2011 16:25:49 +0000 [thread overview]
Message-ID: <m3vcz9248i.fsf@e4300lm.epcc.ed.ac.uk> (raw)
In-Reply-To: 7864.1300892560@alphaville.dokosmarshall.org
Nick Dokos wrote:
> Bastien <bzg@altern.org> wrote:
>> Hi Nick,
>> Nick Dokos <nicholas.dokos@hp.com> writes:
>>> Suvayu Ali <fatkasuvayu+linux@gmail.com> wrote:
>>>> This works too, but Lawrence's patch makes it much easier and
>>>> probably works for other export formats too. Thanks a lot. :)
>>> No doubt Lawrence's patch can be extended to work for other exports, but
>>> it's not there yet: each exporter would need a change similar to the one
>>> that he made to the LaTeX exporter.
>> Let's handle this change exporter by exporter. The longest trip starts
>> with the first step :)
> Sorry, I sent my previous comment without reading ahead for this. I still
> would like to see some discussion on this, though.
Here it is again:
> This is probably obvious but I thought I'd make it explicit, both for
> future wanderers and for further discussion: application of these
> patches makes the behavior of different exporters potentially
> inconsistent with each other.
You can drop the potentially here!
> IMO, it would be better to accumulate the patches and once all of the
> exporters (or perhaps a critical mass: ascii, odt, docbook are the ones
> I would like to see get patches, but opinions will vary) have patches,
> then apply the whole thing in one commit (together with a documentation
> patch). In the meantime, if anybody needs one of them (hi, Suvayu :-)),
> they could carry it in their local branch.
> Of course, there is no perfect consistency in any case between the exporters,
> but I think at least making the effort to keep them consistent is better
> than letting them diverge and possibly never converge again.
I would agree whole-heartedly with these thoughts. I hadn't
necessarily expected my patches to go in straight away, but
offered them for perusal. However, this requirement may make it
difficult to get new changes into the export system. For
example, I'm uninterested in export to backends other than latex
and html, so I'm only likely to implement a change for those
targets. If no-one else is sufficiently interested in the change
to pick up the ball for other backends, it may never get in.
This is possibly a good thing (divergence of export functionality
and all), but may slow the acceptance of new (useful?) features.
For example, I don't know if the docbook backend explicitly
writes section numbers in, or if the sectioning is left to the
stylesheet. If the latter, can I mark sections as ones that
should be numbered and ones that shouldn't?
On a somewhat tangential note, while grovelling around in the
latex and html backends, it seems to me that the export backends
in general could do with some loving. It seems authors of the
backends are unclear when to use option variables, when to get
the data from the buffer-local options plist and so. This data
is therefore treated inconsistently across backends, sometimes
(plist-get opt-plist :option) is used, sometimes the default
variable org-export-with-option is, sometimes neither are
consulted. I'm not sufficiently excited by the grunt work to do
anything about it, but maybe I should!
Lawrence
--
Lawrence Mitchell <wence@gmx.li>
next prev parent reply other threads:[~2011-03-23 16:26 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 [this message]
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
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=m3vcz9248i.fsf@e4300lm.epcc.ed.ac.uk \
--to=wence@gmx.li \
--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).