From: Ihor Radchenko <yantar92@posteo.net>
To: "Marvin Gülker" <post+orgmodeml@guelker.eu>
Cc: emacs-orgmode@gnu.org
Subject: Re: Feature request: export form feed as page break
Date: Sat, 21 Oct 2023 09:19:44 +0000 [thread overview]
Message-ID: <87v8b0tjrj.fsf@localhost> (raw)
In-Reply-To: <87zg0ce6yi.fsf@guelker.eu>
Marvin Gülker <post+orgmodeml@guelker.eu> writes:
> ....
> 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.
See https://list.orgmode.org/orgmode/87mtamjrft.fsf@localhost/
In general, adding page breaks can make sense. The main concern is that
the location of page breaks may or may not be export
backend-independent. In certain scenarios, you may need to put page
breaks in one place for odt export, but in other place in LaTeX export
(for example, when page size is different in these two cases).
Below are some of my personal notes on this topic:
Page breaks is one of the common typographical settings people do use.
- In LaTeX, this is easy to achieve simply putting =\clearpage=
- However, in exports like odt, the page break may be tricky and involve direct xml - not great
https://list.orgmode.org/orgmode/87leq49bu0.fsf_-_@posteo.net/
- Page breaks even make sense in text files (ASCII or even directly in Org)
https://list.orgmode.org/orgmode/87mtamjrft.fsf@localhost
- Page breaks are directly supported by Emacs (filling), alongside with hard-newlines
https://list.orgmode.org/orgmode/875yhiyxnb.fsf@localhost
We may as well add a new element to Org that marks page breaks.
+ Page break should be an object as page breaks do not necessarily split paragraphs
+ People also want page breaks to precede certain elements (most importantly, headlines)
+ This is somewhat unrelated issue though -- too complex just for a single syntax element
+ It would be more productive to introduce generalized syntax to prepend actual Org elements during export
- page breaks location is very much backend-dependent; typographic detail
https://list.orgmode.org/orgmode/875yhiyxnb.fsf@localhost
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-10-21 9:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-21 7:42 Feature request: export form feed as page break Marvin Gülker
2023-10-21 9:19 ` Ihor Radchenko [this message]
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=87v8b0tjrj.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=post+orgmodeml@guelker.eu \
/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).