From: Nicolas Goaziou <firstname.lastname@example.org>
To: Jambunathan K <email@example.com>
Cc: firstname.lastname@example.org, Rasmus <email@example.com>
Subject: Re: Participating in Google Summer of Code 2012
Date: Fri, 09 Mar 2012 18:17:41 +0100 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <email@example.com> (Jambunathan K.'s message of "Sun, 04 Mar 2012 15:32:15 +0530")
Jambunathan K <firstname.lastname@example.org> writes:
> Can the org-export driver make listified headings transparent to the
I am reluctant to fake data presented to transcoders. I am even more
reluctant when some information is lost in the process. A back-end might
need to tell the difference between an headline that should be treated
as a list and a regular list. For example some back-end with weak list
concept (limited in the types of objects lists can contain) would rather
not turn headlines into items.
Currently, the exporter API is more oriented towards showing full info,
and giving clues on how to handle it.
> Currently listified headings are handled within org-e-backend-headline
> through first-sibling and last sibling checks and the backends *do
> know* that it is handling a headline in a special way.
> If you have reservations in considering the above request, I believe
> handling of indented tables will be fragmented across plain-list/item
> callbacks and headline callbacks.
This is a back-end specific limitation. I guess it is unavoidable.
Though, if you think about a generic tool that could reduce the amount
of work required, I will include it in org-export.el.
next prev parent reply other threads:[~2012-03-09 17:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-02 8:24 Participating in Google Summer of Code 2012 Bastien
2012-03-02 16:42 ` Eric Schulte
2012-03-04 1:05 ` Rasmus
2012-03-04 9:28 ` Nicolas Goaziou
2012-03-04 10:02 ` Jambunathan K
2012-03-09 17:17 ` Nicolas Goaziou [this message]
2012-03-05 19:10 ` Thorsten
2012-03-02 16:50 ` Jambunathan K
2012-03-02 16:56 ` Eric Schulte
2012-03-02 17:12 ` Jambunathan K
2012-03-04 15:14 ` Alan Schmitt
2012-03-07 18:18 ` Bastien
2012-03-09 1:43 ` Bastien
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).