From: Peter Davis <pfd@pfdstudio.com>
To: John Hendy <jw.hendy@gmail.com>
Subject: Re: Blank page in LaTeX/PDF output
Date: Tue, 04 Mar 2014 07:27:54 -0500 [thread overview]
Message-ID: <1393936074.5934.90371709.028FE30D@webmail.messagingengine.com> (raw)
In-Reply-To: <CA+M2ft94iO98w5y-xh1j8rmj0AG9d1TqfdSgcvRAQZmprH=ZRg@mail.gmail.com>
On Mon, Mar 3, 2014, at 10:46 PM, John Hendy wrote:
[snip]
> On Mon, Mar 3, 2014 at 7:13 PM, Peter Davis <pfd@pfdstudio.com> wrote:
> From my fiddling:
> - As-is produces 4 pages, blank 3rd
> - Commenting out the hyperref package does *not* produce a blank 3rd page
> - Using \section* does *not* product a blank 3rd page
Thanks, John. It certainly seems that hyperref is at least partially to
blame here. I'll have to check on what the developers consider a 3rd
party package. hyperref itself loads a bunch of other packages, so it
gets very complicated.
> I added a comment linking to Wikipedia's Linux penguin that I used as
> ./image.png, just to make sure it wasn't possibly related to errors
> related to no image being found.
I first saw the problem when I was using actual images, so I knew it
wasn't that.
> I wondered if it had something to do with the numbered sections being
> treated as links (since hyperref was the culprit package). I fiddled
> with removing \label{sec-n}, but that didn't have an effect. I
> wondered if that was triggering something due to it having links sort
> of "ready" for the TOC even though none is present... no idea!
Seems plausible.
> Anyway, as long as graphicx and hyperref are not considered "3rd
> party," I think you could still submit the report. You may be told
> that since there are overfull hbox and vbox's that it's not their
> problem, but I'd still expect the results to be the same with \section
> vs. \section*, and with[out] hyperref.
Thanks again, John. I'll look into this and report back whatever I find.
Best,
-pd
--
Peter Davis
www.techcurmudgeon.com
www.timebums.com
next prev parent reply other threads:[~2014-03-04 12:42 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
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 [this message]
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=1393936074.5934.90371709.028FE30D@webmail.messagingengine.com \
--to=pfd@pfdstudio.com \
--cc=jw.hendy@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).