Pedro Andres Aranda Gutierrez <[email protected]> writes:
> {{{clp}}} is shorter and comfier to write than \clearpage (at least
> for me TM)...
> The other one is for me to highlight things that are LaTeX (as opposed
> to pure Org).
> Just a question like ... would it make sense to have an org construct for
> this?
Here is a project I have locally:
******* SOMEDAY #project Add page break element to Org syntax
:COMMON:EMACS:project:SOMEDAY:
:PROPERTIES:
:CREATED: [2022-09-29 Thu 09:11]
:ORG-TIME-BALANCE-MULTIPLIER: -0.5
:CATEGORY: OrgPageBreak
:END:
:LOGBOOK:
- State "SOMEDAY" from "HOLD" [2023-08-04 Fri 15:13]
- State "HOLD" from "NEXT" [2022-10-21 Fri 17:12]
- Refiled on [2022-09-29 Thu 09:23]
CLOCK: [2022-09-29 Thu 09:11]--[2022-09-29 Thu 09:20] => 0:09
:END:
# A short summary about the project.
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
[[id:ML-Org-mode-<maciaschain@posteonet>2022-explicit-page-breaks-763][Manuel
Macías [ML:Org mode] (2022) Explicit page breaks (was: Create in Org a
bilingual book with facing pages)]]
- Page breaks even make sense in text files (ASCII or even directly in Org)
[[id:ML-Org-mode-<yantar92@gmailcom>2022-should-page-break-2af][Ihor
Radchenko [ML:Org mode] (2022) Should page break (^L) work as paragraph element
separator and be included into Org syntax? (was: [BUG] org-fill-paragraph
doesn't handle ^L correctly [9.5.4 (release_9.5.4-19-g4dff42 @
/home/matt/Code/emacs/lisp/org/)])]]
- Page breaks are directly supported by Emacs (filling), alongside with
hard-newlines
[[id:ML-Org-mode-<yantar92@gmailcom>2022-re-fr-support-322][Ihor Radchenko
[ML:Org mode] (2022) Re: FR: support hard-newlines [9.5.5 (release_9.5.5
/home/viz/lib/ports/emacs/lisp/org/)]]]
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
[[id:ML-Org-mode-<maciaschain@posteonet>2022-re-explicit-page-breaks-d8e][Manuel
Macías [ML:Org mode] (2022) Re: Explicit page breaks]]
+ sometimes, the page breaks are really backend-independent though
For example, when the document is a question/answer sheet and the
answers are to be on a different page _all the time_.
[[id:ML-Org-mode-<yantar92@posteonet>2023-re-feature-request-ff6][Ihor
Radchenko [ML:Org mode] (2023) Re: Feature request: export form feed as page
break]]
- The markup for page breaks might be something like an entity or/and keyword
(for inter-paragraph)
- Supporting ^L has downsides and some applications either do not
display it or complain when it is copied
[[id:ML-Org-mode-<manikulin@gmailcom>2023-re-feature-request-296][Max Nikulin
[ML:Org mode]
(2023) Re: Feature request: export form feed as page break]]
--
Ihor Radchenko // yantar92,
Org mode maintainer,
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>
