emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Blank page in LaTeX/PDF output
Date: Fri, 28 Feb 2014 19:38:40 -0500	[thread overview]
Message-ID: <874n3ihhwv.fsf@gmail.com> (raw)
In-Reply-To: 5310C6DF.70501@pfdstudio.com

Peter Davis <pfd@pfdstudio.com> writes:

> On 2/28/14, 12:03 PM, John Hendy wrote:
>> On Fri, Feb 28, 2014 at 10:59 AM, Peter Davis <pfd@pfdstudio.com> wrote:
>>> I'm writing a short paper containing tables, images, etc., but I'm getting a
>>> blank page in the PDF output. That is, it's completely blank *except* for
>>> the page number.
>>>
>>> Any suggestions on how to trouble-shoot or fix this?
>> Probably related to image/table float placement. I've had an image on
>> one page trigger a blank page after it, and if your options or the
>> size of the image on the next place won't fit on a single page, it
>> might be skipping that blank one entirely and moving along to the
>> next.
>>
>> Is it possible to share the document, or could you try to copy that
>> .org file, remove the contents of p. 1-4 and 8-9, and then share the
>> .org file that generates pages 5, 6 (blank), and 7?
>
> Thanks, John. I figured it has something to do with LaTeX float
> behavior, but I'm trying to understand how to control it through
> org-mode. I'm attaching a small sample that reproduces the problem.
>
> Thanks!
> -pd

John is correct, I think, although latex's behavior in leaving an empty
page does not make much sense to me. Nevertheless, when I reduce
the height of the last image to less than about 7.85 inches, the empty
page goes away. AFAICT, num: and toc: settings do not affect this
behavior.

-- 
Nick

  parent reply	other threads:[~2014-03-01  0:39 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-28 16:59 Blank page in LaTeX/PDF output Peter Davis
2014-02-28 17:03 ` John Hendy
2014-02-28 17:26   ` Peter Davis
2014-02-28 17:36     ` Peter Davis
2014-02-28 17:37     ` John Hendy
2014-02-28 18:19       ` Peter Davis
2014-02-28 18:32         ` Peter Davis
2014-03-01  0:38     ` Nick Dokos [this message]
2014-03-01  1:21       ` Peter Davis
2014-03-01  1:27         ` John Hendy
2014-03-01 13:01           ` Nick Dokos
2014-03-01  1:30         ` Peter Davis
2014-03-01  3:32           ` Nick Dokos
2014-03-01  3:39             ` Peter Davis
2014-03-01  5:27               ` John Hendy
2014-03-01 12:47                 ` Nick Dokos
2014-03-01 14:48                   ` Peter Davis
2014-03-01 19:19                     ` John Hendy
2014-03-04  0:51                       ` Peter Davis
2014-03-04  1:08                         ` John Hendy
2014-03-04  1:13                           ` Peter Davis
2014-03-04  3:46                             ` John Hendy
2014-03-04 12:27                               ` Peter Davis
2014-03-01 14:42         ` Nick Dokos

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=874n3ihhwv.fsf@gmail.com \
    --to=ndokos@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).