emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: "Alan E. Davis" <lngndvs@gmail.com>
Cc: org-mode <emacs-orgmode@gnu.org>
Subject: Re: Exporting org to LaTeX to PDF: headings do not convert to sections
Date: Thu, 21 May 2009 16:27:21 +0200	[thread overview]
Message-ID: <50C05343-0CF2-4E8A-873B-2E040C225789@gmail.com> (raw)
In-Reply-To: <7bef1f890905210650o1a4a66e1t5b87cbc363b44ac5@mail.gmail.com>

Hi Alan,

this is a fundamental limitation in LaTeX

See http://www.tex.ac.uk/cgi-bin/texfaq2html?label=toodeep

The only thing you can do in Org is to increase the number of headline  
levels to the maximum possible:


is I think the maximum you can get.  You cal also create a
LaTeX class with more headline leves and push H even further.
I believe there are some clases which provide at least subsubparagraph.

If you have a good idea how to represent deeper levels in LaTeX, maybe  
can do something clever in the LaTeX exporter.

Besides this, I see no further way out of this problem.


- Carsten

On May 21, 2009, at 3:50 PM, Alan E. Davis wrote:

> An outline, when exported as PDF, shows no sections.  When exporting  
> to LaTeX, the following message is received:
>    ERROR: LaTeX Error: Too deeply nested.
>    --- TeX said ---
>    See the LaTeX manual or LaTeX Companion for explanation.
>    Type  H <return>  for immediate help.
>    ...
>    l.110 \begin{itemize}
>    --- HELP ---
>    There are too many list-making environments nested within one  
> another.
>   How many levels of nesting are permitted may depend upon what  
> computer
>    you are using, but at least four levels are provided, which  
> should be
>    enough.
> When I am able to clear out a couple of levels of /begin{itemize},  
> LaTeX does compile, and produces a file with sections as expected.
> Is there a solution, or something I ought to know?
> I have tried to set some options, like sec:5, in the outline, but to  
> no effect.  In the PDF, instead of sections with numbers, one finds  
> several stars, as though this were an ascii export.
> Thank you for any advice.
> Alan Davis
> It is undesirable to believe a proposition when
> there is no ground whatsoever for supposing it is true.
>     ---- Bertrand Russell
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  reply	other threads:[~2009-05-21 14:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-21 13:50 Exporting org to LaTeX to PDF: headings do not convert to sections Alan E. Davis
2009-05-21 14:27 ` Carsten Dominik [this message]
2009-05-21 14:52   ` Carsten Dominik
2009-05-21 20:14     ` Alan E. Davis
2009-05-21 22:44       ` Carsten Dominik
2009-05-22  8:17         ` Eric S Fraga
2009-05-23  6:26           ` Carsten Dominik
2009-05-23 22:39             ` Alan E. Davis
2009-05-22  1:38       ` Mark Elston

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:

  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=50C05343-0CF2-4E8A-873B-2E040C225789@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=lngndvs@gmail.com \


* 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).