From: Carsten Dominik <carsten.dominik@gmail.com>
To: "Alan E. Davis" <lngndvs@gmail.com>
Cc: org-mode <emacs-orgmode@gnu.org>,
Carsten Dominik <dominik@science.uva.nl>
Subject: Re: Exporting org to LaTeX to PDF: headings do not convert to sections
Date: Fri, 22 May 2009 00:44:53 +0200 [thread overview]
Message-ID: <14B4D147-56B5-42F4-A2D0-05AABE808E54@gmail.com> (raw)
In-Reply-To: <7bef1f890905211314p4f14e44fj57aac5d339578a28@mail.gmail.com>
On May 21, 2009, at 10:14 PM, Alan E. Davis wrote:
> Thank you for the response.
>
>
> On May 21, 2009, at 4:27 PM, Carsten Dominik wrote:
>
> The only thing you can do in Org is to increase the number of
> headline levels to the maximum possible:
>
> #+OPTION H:5
>
> This doesn't work for me.
Typo:
#+OPTIONS: H:5
>
>
> 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 we
> can do something clever in the LaTeX exporter.
>
> ??????
>
>
>
>
> I just realize that your question provides the answer to a question
> I had for a long time: Why did Bastien implement lower
> levels in the LaTeX export as {description} lists instead of
> {itemize} lists. Now I know the answer: Because the number of levels
> in a description list is not limited.
>
> I recently changed Bastien's code to use itemize instead, for
> consistence with HTML export. Fortunately I left the old code
> in, with a customization option. Please try:
>
> (setq org-export-latex-low-level 'description)
>
> So far, this doesn't solve my problem. Should I then use
> description lists for all outline entries?
No. This should just take your
******** headline
and export it as a description list item. Works just fine in my tests
here.
>
>
> I don't understand why I do not see "section" or "subsection", and
> the sections often come out with bare stars. Is this also because
> the number of levels has been exceeded?
No, this must be a different bug, which I cannot reproduce. Example
file???
- Carsten
>
> Thank you again. This is the first limitation of LaTeX I have not
> seen an immediate way around.
>
>
>
> Alan
>
next prev parent reply other threads:[~2009-05-21 22:45 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
2009-05-21 14:52 ` Carsten Dominik
2009-05-21 20:14 ` Alan E. Davis
2009-05-21 22:44 ` Carsten Dominik [this message]
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:
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=14B4D147-56B5-42F4-A2D0-05AABE808E54@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=dominik@science.uva.nl \
--cc=emacs-orgmode@gnu.org \
--cc=lngndvs@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).