emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: "Marvin Gülker" <post+orgmodeml@guelker.eu>
To: emacs-orgmode@gnu.org
Subject: Feature request: export form feed as page break
Date: Sat, 21 Oct 2023 09:42:33 +0200	[thread overview]
Message-ID: <87zg0ce6yi.fsf@guelker.eu> (raw)

Dear list,

I am creating training material for the education of German law
students, which usually consists of a case story on one or two pages,
followed by a page break after which a proposal for resolving the case
is provided. The structure is like this because usually I provide the
case story before the meeting, where I work out a solution with the
students, and afterwards I want to provide them with complete material,
while still having everything contained in one file.

With org, I can easily export to LaTeX and thereby to PDF, and it works
quite nicely. However, for the page break I always need to write a
literal \newpage into the document, which does work, but only in LaTeX.
Since I am the only one using org/LaTeX at my chair, I have to convert
these documents to DOCX (using the ODT exporter) when a collegue wants
an editable version of them. As a LaTeX command, \newpage does not work
when exporting to ODT. I thus open the exported document manually after
the export and insert the page break using LibreOffice.

To ease this process, I would like to request that the ASCII control
character U+000C FORM FEED (displayed by emacs as ^L and also known as
`\f' in C string notation) is recognised by exporters and translated to
the corresponding page break command, that is, in LaTeX \newpage and in
ODT to the XML that makes LibreOffice start a new page. For HTML, it
could be exported as <div style="clear: both; page-break-after:
always"/></div> or similar, and for exporters which have no notion of
pages, it could just be copied over to the exported document as-is.

  -MG

-- 
Dipl.-Jur. M. Gülker | https://mg.guelker.eu | PGP: Siehe Webseite
Passau, Deutschland  | kontakt@guelker.eu    | O<

next             reply	other threads:[~2023-10-21  8:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-21  7:42 Marvin Gülker [this message]
2023-10-21  9:19 ` Feature request: export form feed as page break Ihor Radchenko
2023-10-21 14:43   ` Max Nikulin
2023-10-22  8:54     ` Ihor Radchenko
2023-10-21 16:33   ` Marvin Gülker
2023-10-22  8:58     ` Ihor Radchenko
2023-10-21 14:26 ` Max Nikulin
2023-10-21 16:27   ` Marvin Gülker
2023-10-22  9:00   ` Ihor Radchenko
2023-10-23 10:37     ` Max Nikulin
2023-10-22  6:00 ` Jambunathan K
2023-10-22 12:55   ` Uwe Brauer
2023-10-24  6:08   ` Marvin Gülker
2024-01-07  7:23   ` Timothy
2024-01-07 12:57     ` Ihor Radchenko

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=87zg0ce6yi.fsf@guelker.eu \
    --to=post+orgmodeml@guelker.eu \
    --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

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).