From: "Marvin Gülker" <post+orgmodeml@guelker.eu>
To: emacs-orgmode@gnu.org
Subject: Re: Feature request: export form feed as page break
Date: Sat, 21 Oct 2023 18:27:47 +0200 [thread overview]
Message-ID: <87jzrgx7h2.fsf@guelker.eu> (raw)
In-Reply-To: <020d1a1c-6496-4d26-b481-84aaf43ec763@gmail.com>
Am Samstag, dem 21. Oktober 2023 schrieb Max Nikulin:
> As a workaround you may define an Org macro that expands to
> @@latex:\newpage@@ and appropriate XML element inside @@odt:…@@.
Fair enough, this is possible, but then I have to consider each backend
I may export to and read up on how the respective backend does this. As
it stands, I just do not know how the piece inside @@odt:…@@ would have
to look like. If the decision here is to not add a page break feature to
org, then I will probably go that route, though.
> P.S. I am against using non-printable characters for markup. It might
> be an \... entity for page break inside a paragraph, "#+...:" keyword
> between block-level elements, etc.
I have no strong opinion on that, but I just thought that ^L seems like
a good fit, and I saw it used in Elisp files earlier so I thought it is
common enough to just reuse it.
-MG
--
Dipl.-Jur. M. Gülker | https://mg.guelker.eu | PGP: Siehe Webseite
Passau, Deutschland | kontakt@guelker.eu | O<
next prev parent reply other threads:[~2023-10-21 16:37 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
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 [this message]
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=87jzrgx7h2.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
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).