emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Thomas S. Dye" <tsd@tsdye.com>
To: Martin Weigele <martin@weigele.de>
Cc: Emacs-orgmode@gnu.org
Subject: Re: Strange behaviour of produced latex-pdf
Date: Wed, 2 Feb 2011 06:38:56 -1000	[thread overview]
Message-ID: <7AF8C964-7DF3-4A99-AA58-681E7A560E5B@tsdye.com> (raw)
In-Reply-To: <201102021230.58132.martin@weigele.de>


On Feb 2, 2011, at 1:30 AM, Martin Weigele wrote:

> Dear all, have encountered the following strange behaviour in  
> producing latex-
> pdf from a standard outline, C-c C-e d . One of many top nodes is  
> seemingly
> arbitrarily not broken down into subnodes. It works fine, however,  
> when
> producing html. Emacs 23.1.1; org-7.4 manually installed; ubuntu  
> 10.04 LTS.
>
> The following declarations are used:
>
> #+TITLE: Blah
> #+LaTeX_CLASS: book
> #+LATEX_HEADER: \usepackage{a5}\usepackage{german}
> #+LANGUAGE: DE
> #+TEXT: Blah
>
> While most top nodes are broken down like
> \chapter{blah}
> \section{blah}
> etc..
>
> ...one chapter is simply not broken down. I have checked the org  
> file with vi,
> there is no evidence that anything is wrong in the orgfile  
> structure. All go
> *chapter
> **section
> ***subsection
>
> etc.
>
> Like others, the unrefined chapter contains only (sub)headlines, no  
> text yet.
> Any ideas?

Aloha Martin,

I don't understand what you mean by "not broken down."  Could you  
provide an example of the LaTeX output?

All the best,
Tom

  reply	other threads:[~2011-02-02 16:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-02 11:30 Strange behaviour of produced latex-pdf Martin Weigele
2011-02-02 16:38 ` Thomas S. Dye [this message]
2011-02-02 22:26   ` Eric S Fraga
2011-02-02 22:53     ` Martin Weigele
2011-02-02 23:06       ` Thomas S. Dye
2011-02-03  0:23         ` Eric S Fraga
2011-02-02 23:44       ` Martin Weigele

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=7AF8C964-7DF3-4A99-AA58-681E7A560E5B@tsdye.com \
    --to=tsd@tsdye.com \
    --cc=Emacs-orgmode@gnu.org \
    --cc=martin@weigele.de \
    /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).