From: "Marvin Gülker" <post+orgmodeml@guelker.eu>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Feature request: export form feed as page break
Date: Tue, 24 Oct 2023 08:08:19 +0200 [thread overview]
Message-ID: <87edhkfrm9.fsf@guelker.eu> (raw)
In-Reply-To: <f240054f-fa22-4329-b33d-352d8900d0d8@gmail.com>
Am Sonntag, dem 22. Oktober 2023 schrieb Jambunathan K:
> I am the original author of ox-odt.el.
>
> The page break feature is available as part of
> https://github.com/kjambunathan/org-mode-ox-odt
I took a look at https://github.com/kjambunathan/org-mode-ox-odt/blob/master/notes/SNIPPETS.org#improve-support-for-pagebreaks
and indeed, there is a page break feature, but it seems to be exclusive
to this backend. I would prefer it if the page break feature was part of
org’s actual markup and thus work with all backends, including LaTeX,
without backend-specific markup.
> This is a fork of the ODT exporter in Emacs Orgmode.
I heard of it before; for now I think I want to stick with upstream org.
I do keep an eye on this fork in case I need one of its exclusive
features. Since from a technical point, I am mostly writing pretty
boring pure text documents, it worked out until now mostly.
-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-24 6:44 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
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 [this message]
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=87edhkfrm9.fsf@guelker.eu \
--to=post+orgmodeml@guelker.eu \
--cc=emacs-orgmode@gnu.org \
--cc=kjambunathan@gmail.com \
/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).