From: Dan Griswold <dgriswol@rochester.rr.com>
To: Luke Crook <luke@balooga.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: \newpage in HTML export
Date: Wed, 20 Nov 2013 15:10:45 -0500 [thread overview]
Message-ID: <CAGO+QKvcXF1CUuJQd=z9GgfLntQyVOkn+FZ2jtXP5X0cgpOT4Q@mail.gmail.com> (raw)
In-Reply-To: <loom.20131120T194252-12@post.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 473 bytes --]
This works well for me:
#+HTML: <div style="page-break-before: always"> </div>
placed right where you want the page break.
The break will not appear in the browser, but it will when you print.
Dan
On Wed, Nov 20, 2013 at 1:52 PM, Luke Crook <luke@balooga.com> wrote:
> Both "\newpage" and "#+LATEX: \newpage" generate page breaks in Latex.
> However "\newpage" is included verbatim in HTML export.
>
> Should I use "#+LATEX: \newpage" instead?
>
> /Luke
>
>
>
[-- Attachment #2: Type: text/html, Size: 995 bytes --]
next prev parent reply other threads:[~2013-11-20 20:10 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 18:52 \newpage in HTML export Luke Crook
2013-11-20 20:10 ` Dan Griswold [this message]
2013-11-20 21:15 ` Luke Crook
2013-11-20 21:20 ` Russell Adams
2013-11-20 23:36 ` Suvayu Ali
2013-11-21 1:11 ` Eric Abrahamsen
2013-11-21 2:38 ` Jambunathan K
2013-11-21 11:17 ` Suvayu Ali
2013-11-21 14:41 ` Eric Abrahamsen
2013-11-22 7:47 ` [PATCH] " Eric Abrahamsen
2013-11-22 10:24 ` Nicolas Goaziou
2013-11-22 12:50 ` Rüdiger Sonderfeld
2013-11-24 9:31 ` Nicolas Goaziou
2013-11-24 11:05 ` Eric Abrahamsen
2013-11-24 13:58 ` Andreas Leha
2013-12-22 13:49 ` Nicolas Goaziou
2013-12-22 14:08 ` Andreas Leha
2013-12-22 14:20 ` Nicolas Goaziou
2013-12-22 14:28 ` Andreas Leha
2014-01-03 15:39 ` Bastien
2014-01-03 19:29 ` Andreas Leha
2014-01-03 19:50 ` Thomas S. Dye
2014-01-03 20:10 ` Andreas Leha
2014-01-04 10:40 ` Bastien
2014-01-04 12:41 ` Andreas Leha
2014-01-04 14:07 ` Bastien
2014-01-05 20:53 ` Suvayu Ali
2014-01-06 9:42 ` Bastien
2014-01-04 19:47 ` Sebastien Vauban
2014-01-05 6:35 ` Bastien
2014-01-05 9:42 ` Sebastien Vauban
2014-01-05 10:46 ` Bastien
2013-11-24 16:39 ` Christian Moe
2013-11-23 9:28 ` Eric Abrahamsen
2013-11-23 9:28 ` Eric Abrahamsen
2013-11-25 9:55 ` Jambunathan K
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='CAGO+QKvcXF1CUuJQd=z9GgfLntQyVOkn+FZ2jtXP5X0cgpOT4Q@mail.gmail.com' \
--to=dgriswol@rochester.rr.com \
--cc=emacs-orgmode@gnu.org \
--cc=luke@balooga.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).