emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Hendy <jw.hendy@gmail.com>
To: Peter Davis <pfd@pfdstudio.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Blank page in LaTeX/PDF output
Date: Sat, 1 Mar 2014 13:19:10 -0600	[thread overview]
Message-ID: <CA+M2ft9c72G1-OAKkUau88hPkdu+Wvq2ukWDu1WF+RG9k5TSeQ@mail.gmail.com> (raw)
In-Reply-To: <5311F34A.7060400@pfdstudio.com>

[-- Attachment #1: Type: text/plain, Size: 2998 bytes --]

I can confirm Peter's results, and also took a stab at improving the
reproducibility. I used his the file provided here, saving as two
different .org files, "numbered-min.org" and "un-numbered-min.org":
- http://lists.gnu.org/archive/html/emacs-orgmode/2014-02/msg01035.html

The only differences between these two lines is in the #+options line.
- numbered-min.org contains #+options: num:t toc:nil
- un-numbered-min.org contains #+options: num:nil toc:nil

I used `emacs -Q`, and then `M-x load-file`, followed by loading this
minimal config:

#+begin_src min-config

;; change to your org path!
(add-to-list 'load-path "~/.elisp/org.git/lisp/")
(add-to-list 'load-path "~/.elisp/org.git/contrib/lisp")

(setq koma-article-class
      '("koma-article"
        "\\documentclass[11pt]{scrartcl}"
        ("\\section{%s}" . "\\section*{%s}")
        ("\\subsection{%s}" . "\\subsection*{%s}")
        ("\\subsubsection{%s}" . "\\subsubsection*{%s}")
        ("\\paragraph{%s}" . "\\paragraph*{%s}")
        ("\\subparagraph{%s}" . "\\subparagraph*{%s}")))

(progn
  (require 'ox-latex)
  (add-to-list 'org-latex-classes koma-article-class t))

#+end_src

Files were exported as usual with `C-c C-e l p` for LaTeX/pdf output.

Here's a pastebin of the result I get from using diff --side-by-side
on the two .tex files when using num:t vs. num:nil in Org:
- http://pastebin.com/wkKYWhb7

The only difference is \section{} vs. \section*{}.

Here's a diff of the latex output:
- http://pastebin.com/vsZH2Hnf

Other than the file names, the only differences are the page numbers
where overfull errors occur. Even the *sizes* of the overfull \hbox
and \vbox errors are identical. In the un-numbered version, the error
references page [2], and in the numbered it mentions pages [2] [3].
(Refer to the pastebin link above to track down any other
discrepancies.)

PDFs from each are attached. For me, 7.8in with numbered sections
results in 3 pages, while 7.9in results in 4 pages with a blank 3rd
page. It's very odd to me that un-numbered would allow 8.5in to not
roll onto the next page, while it actually takes 7.8in to get it to
fit on the numbered version. That's a huge difference, and intuitively
I would have figured we stumbled on some sort of very small boundary
condition, not something that requires a 0.7in difference to fix.

I searched things like "latex page break 'section*' vs section" with
no obvious lead on why the two section styles would be different.
Regarding a bug report, if that's what this is, I just googled "latex
bugs" and got this page as the first hit:
- http://latex-project.org/bugs.html


Best regards,
John


On Sat, Mar 1, 2014 at 8:48 AM, Peter Davis <pfd@pfdstudio.com> wrote:
>
> Here are the two LaTeX files. The only differences, apart from creation
> time, are the the use of \section* instead of \section, so perhaps this is a
> LaTeX bug.
>
> Anyone know how to report that?
>
> -pd
>
> --
> ----
> Peter Davis
> The Tech Curmudgeon
> www.techcurmudgeon.com
>

[-- Attachment #2: numbered-min.pdf --]
[-- Type: application/pdf, Size: 101702 bytes --]

[-- Attachment #3: un-numbered-min.pdf --]
[-- Type: application/pdf, Size: 100870 bytes --]

  reply	other threads:[~2014-03-01 19:19 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 [this message]
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=CA+M2ft9c72G1-OAKkUau88hPkdu+Wvq2ukWDu1WF+RG9k5TSeQ@mail.gmail.com \
    --to=jw.hendy@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=pfd@pfdstudio.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).