[email protected] writes:
> It does not work for me. The pdf I get is
>
> 1. Item 1
> (a) Item 1a
> (b) Item 1b
> 2.
> Item 2
> 3. Item 3
Yes, my misunderstanding; I thought that was what you wanted.
> whereas I want
>
> 1. Item 1
> (a) Item 1a
> (b) Item 1b
> 2. Item 2
> 3. Item 3
>
> Note that even if I remove the blank line before 'Item 2' in the org file
> (which fixes the original problem)
The problem seems to be fixed, then.
And I don't think it's a bug that, when a headline is exported as a list
item, any text that follows a blank line after the headline is placed in
a separate paragraph under the numbered/bulleted list item, with the
same indent. That seems like what one would usually want and expect,
since paragraphs are separated by a blank line.
But I would also expect the same behavior without a blank line after the
headline, really, since it is only the text *on* a headline that is part
of a headline. So I'm not really sure why the trick that is convenient
here -- exporting the next line joined with the numbered list item --
works in LateX export at all. It can cause surprises with regard to
punctuation, and it doesn't work in the other backends, e.g.:
#+OPTIONS: H:0 toc:nil
* Item
Here is some text.
** Subitem
Here is some more text.
LaTeX PDF result (note missing punctuation):
1. Item Here is some text.
(a) Subitem Here is some more text.
ASCII text export result (similar to HTML/ODT results):
* 1 Item
Here is some text.
+ 1.1 Subitem
Here is some more text.
This has surely been discussed somewhere before, and the LaTeX behavior
perhaps documented, since headlines beyond the first three outline
levels are exported to LaTeX as lists. Not sure where, though.
Regards,
Christian
