emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: tsd@tsdye.com (Thomas S. Dye)
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: LaTeX export of lists
Date: Mon, 25 Jul 2011 06:15:42 -1000	[thread overview]
Message-ID: <m1tyaa2v69.fsf@tsdye.com> (raw)
In-Reply-To: <87mxg2aguo.fsf@gmail.com> (Nicolas Goaziou's message of "Mon, 25 Jul 2011 10:45:35 +0200")

Nicolas Goaziou <n.goaziou@gmail.com> writes:

> Hello,
>
> tsd@tsdye.com (Thomas S. Dye) writes:
>
>> Nicolas Goaziou <n.goaziou@gmail.com> writes:
>>> That raises an interesting question: can a list belong to a paragraph in
>>> Org? According to paragraph-related regexps, it can't, for now. And your
>>> request is more a "LaTeXism" than an "Orgism" (!).
>
>> I probably don't understand your question fully, but it seems obvious to
>> me that a list can either belong to a paragraph or it can be separate.
>> I'm not certain why Org-mode would want to choose one over the other.
>
> It isn't obvious. For example, in HTML, a list within a paragraph
> doesn't even make sense[1].
>
> There's no harm in it, but you're basically faking Org and its LaTeX
> exporter, as lists and paragraphs are two distinct entities[2].
>
> Regards,
>
>
> Footnotes:
>
> [1] You can't have <ul> within <p>, according to
> http://www.w3.org/TR/html401/struct/text.html#h-9.3.1
>
> [2] If you try to `mark-paragraph' in your file, it won't mark both
> the text and the list in one go.

Aloha Nicolas,

Interesting observations.  Thanks.

The relation seems obvious to me because my model comes from printed
works, which commonly include enumerated lists typeset within
paragraphs.  

Perhaps given the limitation of the HTML spec and the structure of
paragraphs in Org-mode it will always be necessary to have the LaTeX
exporter take care of setting lists inside paragraphs.

Thanks again for your help with this.

All the best,
Tom

-- 
T.S. Dye & Colleagues, Archaeologists
735 Bishop St, Suite 315, Honolulu, HI 96813
Tel: 808-529-0866, Fax: 808-529-0884
http://www.tsdye.com

  reply	other threads:[~2011-07-25 16:16 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-24 16:16 LaTeX export of lists Thomas S. Dye
2011-07-24 16:44 ` Nick Dokos
2011-07-24 18:13 ` Nicolas Goaziou
2011-07-24 19:18   ` Thomas S. Dye
2011-07-25  8:45     ` Nicolas Goaziou
2011-07-25 16:15       ` Thomas S. Dye [this message]
2011-08-24 15:11         ` Eric S Fraga
2011-08-24 15:53           ` Nicolas Goaziou
2011-08-24 17:39             ` Thomas S. Dye
2011-08-24 18:59               ` Nicolas Goaziou
2011-08-24 19:45                 ` Thomas S. Dye
2011-08-24 16:40           ` Achim Gratz
2011-08-24 17:08           ` Thomas S. Dye
  -- strict thread matches above, loose matches on Subject: below --
2010-11-28 14:33 Thomas S. Dye
2010-11-28 15:05 ` Nicolas Goaziou
2010-11-28 18:40   ` Thomas S. Dye
2010-11-29  8:43     ` Sébastien Mengin
2010-11-27 22:02 Thomas S. Dye
2010-11-28  6:40 ` Richard Lawrence

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=m1tyaa2v69.fsf@tsdye.com \
    --to=tsd@tsdye.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=n.goaziou@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).