From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Blank page in LaTeX/PDF output
Date: Fri, 28 Feb 2014 22:32:42 -0500 [thread overview]
Message-ID: <87wqgefvad.fsf@gmail.com> (raw)
In-Reply-To: 53113848.2060406@pfdstudio.com
Peter Davis <pfd@pfdstudio.com> writes:
> Attached is a simple file that demonstrates this. As is, it does not
> leave a blank page. But if you remove the num:nil option from the
> second line of this file, you do get a blank page.
>
Not for me: in both cases, I get a blank page 3.
> You (probably) need koma-article class for this. (I didn't install
> anything. It just worked for me.) You don't need the images.
>
You need *some* images in order to compile it. I just replaced all
the image links with
[[./foo.png]]
where foo.png is the emacs logo.
And my koma-article is a copy of the article class, except the document class
is "scrartcl" instead of "article".
> -pd
>
> On 2/28/14, 8:21 PM, Peter Davis wrote:
>>
>> On 2/28/14, 7:38 PM, Nick Dokos wrote:
>>> 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.
>>>
>>
>> Thanks, Nick, but I have confirmed that adding num:nil eliminates
>> the blank page, and removing that re-introduces the blank page. No
>> other changes to the .org file were made. I was wondering if LaTeX
>> has some predisposition to handle numbered section headings
>> differently from unnumbered ones as far as pagination.
>>
>> I'll try to make a simple, clean sample that reproduces it, but it's
>> going to take some trial-and-error testing.
>>
>> -pd
>>
--
Nick
next prev parent reply other threads:[~2014-03-01 3:33 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
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 [this message]
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=87wqgefvad.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).