emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: SW <sabrewolfy@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Broken LaTeX export
Date: Wed, 30 May 2012 09:45:30 +0000 (UTC)	[thread overview]
Message-ID: <loom.20120530T113943-420@post.gmane.org> (raw)
In-Reply-To: 20684.1338368935@alphaville

Nick Dokos <nicholas.dokos <at> hp.com> writes:

> Interesting: it seems to be a latex bug of some sort, but I haven't had
> time to play with it too much yet. I'm trying things like modifying the
> tex file slightly and seeing if the empty page(s)/overfull page(s)
> persist.  So far, it seems that all the packages that org includes are
> innocent: I took them all out and the strangeness persists.

I shortened the document by moving "\end{document}" around to try to find the
problem. In some cases, the document rendered correctly. I think this is related
to having to many "section" type headings in LaTeX with no content.

To test this, I added:

\usepackage[english]{babel}
\usepackage{blindtext}

And then used "M-x replace-string" to replace "\subs" with "\blindtext^q^j\subs"
to enter a lots of text into the document. It now renders correctly, with the
end of the document back to where it should be.

However, this is a work-around, not a solution, as part of the appeal of
org-mode and the LaTeX export is to be able to work with and generate outlines
and structures of documents first, before adding all the content.

  parent reply	other threads:[~2012-05-30  9:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-29 12:59 Broken LaTeX export SW
2012-05-29 16:01 ` Nick Dokos
2012-05-29 16:57   ` SW
2012-05-30  9:08     ` Nick Dokos
2012-05-30  9:16       ` SW
2012-05-30 17:46         ` Achim Gratz
2012-05-30  9:45       ` SW [this message]
2012-06-01  7:42         ` Eric S Fraga
2012-07-04 12:41           ` SW
2012-05-30 10:51       ` SW

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=loom.20120530T113943-420@post.gmane.org \
    --to=sabrewolfy@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /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).