From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-orgmode@gnu.org
Subject: Re: \newpage in HTML export
Date: Thu, 21 Nov 2013 08:11:50 +0700 [thread overview]
Message-ID: <87r4aav9rd.fsf@ericabrahamsen.net> (raw)
In-Reply-To: 20131120233629.GD19844@kuru.dyndns-at-home.com
Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:
> On Wed, Nov 20, 2013 at 03:20:02PM -0600, Russell Adams wrote:
>> On Wed, Nov 20, 2013 at 09:15:43PM +0000, Luke Crook wrote:
>> >
>> > That works. But that means I need both #+HTML: and #+Latex: for the same
>> > thing. \newpage should convert as appropriate depending on the export.
>> >
>> > So, \newpage should translate to the HTML equivalent on HTML export, and the
>> > Latex equivalent on Latex export.
>> >
>> > It only works correctly on Latex export
>>
>> \newpage is a Latex command, and so you need the #+Latex: prefix if
>> you're exporting to multiple formats. That will prevent it from
>> happening.
>
> To add a historical comment, eventhough Org claims to be backend
> neutral, it treats LaTeX preferencially in practice. e.g. many common
> LaTeX commands/macros are "understood" by Org.
>
> Just follow what Russel said, put them both where you need a pagebreak.
> Try this:
>
> #+MACRO: pagebreak @@latex:\newpage@@ @@html:<div style="page-break-before: always"> </div>@@
>
> {{{pagebreak}}}
>
> Hope this helps,
Emacs already has the concept of the page-delimiter (defaults to ^L),
for page-related commands. I once floated the idea of making a
page-break a full org element, that could be handled differently by
different backends. I think I made it sound too complicated, though.
Anyway, that's still a possibility.
next prev parent reply other threads:[~2013-11-21 1: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
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 [this message]
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=87r4aav9rd.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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).