emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Bastien <bzg@altern.org>
Cc: Josiah Schwab <jschwab@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Ordered List (Alphabetical) and HTML Export
Date: Mon, 01 Jul 2013 13:49:43 +0200	[thread overview]
Message-ID: <87wqpaqz3c.fsf@gmail.com> (raw)
In-Reply-To: <8738rymvrk.fsf@bzg.ath.cx> (Bastien's message of "Mon, 01 Jul 2013 12:15:11 +0200")

Bastien <bzg@altern.org> writes:

> Given that Org allows alphabetical list, the OP question is
> natural and will come back.

Of course it will. And it had been discussed when the feature was
introduced. I don't mind discussing it again, but there's nothing new on
the table. I thought it had a FAQ entry: I was wrong.

> There is no clue in Org that alphabetical lists are just visual clues.

The manual is one clue. Quoting section "2.7 Plain lists"

   Org knows ordered lists, unordered lists, and description lists.
   * _Unordered_ list items start with '-', '+', or '*'(1) as bullets.
   * _Ordered_ list items start with a numeral followed by either a
     period or a right parenthesis(2), such as '1.' or '1)'(3).  If you
     want a list to start with a different value (e.g., 20), start the
     text of the item with '[@20]'(4).  Those constructs can be used in
     any item of the list in order to enforce a particular numbering.
   * _Description_ list items are unordered list items, and contain the
     separator ' :: ' to distinguish the description _term_ from the
     description.

"Alphabetical list" is only a footnote in this paragraph and clearly not
a type on its own. Merely a convenience.

> I see no harm in supporting more flexibility where we can.

Only where it makes sense: this is not Org's job to replace CSS. Org is
about structure, not appearance.

Also, I do see harm. Introducing a "feature" in one major back-end means
updating other major back-ends, for the sake of consistency. LaTeX (as
in "pdflatex") already does a good job to produce item markers. It is
also configurable. Enforcing it is almost certainly a bad idea anyway.

Let's think about it. If user has a non-nil
`org-list-allow-alphabetical' and don't use them, should we make sure
that items are _never_ alphabetical in the output (i.e. always numbers)?
Also, what if users start asking for roman numbers as item markers?
Greek letters? Of course, Org doesn't provide them in the buffer, but
doesn't it sound silly to offer alphabetical lists only when so many
other types are supported by the targeted languages? Shouldn't back-ends
do the extra step in that direction?

We must draw a clear line between what Org should and shouldn't do. IMO,
this patch is on the wrong side of the line.

> Let me know what you think,

I think the same as I did way back when we introduced this. I don't like
alphabetical lists and I don't think we should offer more support for
them. I would be happier if there was less possible bullets in Org
syntax. This probably won't happen, but I see no reason to make the
situation worse.


Regards,

-- 
Nicolas Goaziou

  parent reply	other threads:[~2013-07-01 11:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-30 18:57 Ordered List (Alphabetical) and HTML Export Josiah Schwab
2013-06-30 21:45 ` Bastien
2013-07-01  9:42   ` Nicolas Goaziou
2013-07-01 10:15     ` Bastien
2013-07-01 10:21       ` Bastien
2013-07-01 10:49         ` Sebastien Vauban
2013-07-01 11:49       ` Nicolas Goaziou [this message]
2013-07-01 12:54         ` Bastien
2013-07-01 13:49           ` Nicolas Goaziou
2013-07-01 14:13             ` Jambunathan K
2013-07-01 14:19             ` Bastien
2013-07-01 14:32             ` Bastien
2013-07-01 14:29         ` Carsten Dominik

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=87wqpaqz3c.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=bzg@altern.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=jschwab@gmail.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).