From: Bastien <bzg@altern.org>
To: nicholas.dokos@hp.com
Cc: Richard Stanton <stanton@haas.berkeley.edu>,
"emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>,
Jambunathan K <kjambunathan@gmail.com>
Subject: Re: Extra space between list items in HTML export
Date: Tue, 18 Sep 2012 16:34:52 +0200 [thread overview]
Message-ID: <878vc71jsj.fsf@bzg.ath.cx> (raw)
In-Reply-To: <12349.1347324720@alphaville.americas.hpqcorp.net> (Nick Dokos's message of "Mon, 10 Sep 2012 20:52:00 -0400")
Nick Dokos <nicholas.dokos@hp.com> writes:
> With Richard's example[fn:1] and the new exporter, we get different
> behavior with HTML and latex (without the num: option or with num:t):
>
> o the second list is unordered in HTML, but enumerated in latex.
>
> o we get third level section numbers decorating the list entries in HTML,
> but not in latex.
>
> Somebody needs to decide what the behavior should be, but then *every*
> exporter should behave the same way wrt that set of options.
I think headings that are lower than the n level in "#+OPTION h:n"
should be replaced by enumarated list when num:t and by unordered list
items when num:nil.
If we all agree, let's move toward this.
Thanks,
--
Bastien
next prev parent reply other threads:[~2012-09-18 14:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-10 21:23 Extra space between list items in HTML export Richard Stanton
2012-09-10 21:37 ` Nick Dokos
2012-09-10 22:39 ` Richard Stanton
2012-09-10 23:31 ` Jambunathan K
2012-09-10 23:39 ` Richard Stanton
2012-09-10 23:45 ` Jambunathan K
2012-09-10 23:47 ` Richard Stanton
2012-09-11 0:52 ` Nick Dokos
2012-09-11 7:30 ` Jambunathan K
2012-09-11 8:00 ` Nick Dokos
2012-09-18 7:26 ` Bastien
2012-09-18 14:34 ` Bastien [this message]
2012-09-18 13:26 ` Bastien
2012-09-18 16:13 ` Richard Stanton
2012-09-19 6:53 ` Bastien
2012-09-19 16:01 ` Richard Stanton
2012-09-19 16:45 ` Bastien
2012-09-19 20:55 ` Richard Stanton
2012-09-18 13:25 ` Bastien
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=878vc71jsj.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
--cc=kjambunathan@gmail.com \
--cc=nicholas.dokos@hp.com \
--cc=stanton@haas.berkeley.edu \
/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).