From: Jambunathan K <kjambunathan@gmail.com>
To: emacs-orgmode@gnu.org
Cc: post+orgmodeml@guelker.eu
Subject: Re: Feature request: export form feed as page break
Date: Sun, 22 Oct 2023 11:30:57 +0530 [thread overview]
Message-ID: <f240054f-fa22-4329-b33d-352d8900d0d8@gmail.com> (raw)
In-Reply-To: <87zg0ce6yi.fsf@guelker.eu>
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
This is a fork of the ODT exporter in Emacs Orgmode.
If you are interested, please open an Discussions thread or a Issue on
Github. Outline your requirements, and I will be happy to share a
recipe or improve the ODT exporter.
For those who rely on ODT exporter--I know there aren't many--please
consider switching to my repo.
If you are going to ask for a feature request for ODT exporter in
emacs-orgmode, you can get some lip-service, and low-effort
patches. (TLDR: The ODT exporter in Emacs is a working, but a dead
code.)
If you are going to ask for a feature request from me, you will
actually see patches. (TLDR: I have been at this exporter for well
over 13 years now. See my contribution activity on Github).
As a PSA, I have been working on an experimental ODS export feature in
order to help Uwe Brauer share Org mode tables (with TBLFMs) to ODS
spreadsheet with Excel formulae.
PS: ox-odt fork is a GPL software. (People who insist on licenses and
go crazy about it are commercial minded, or ideological nuts. I am your
neighbour uncle who wants to help you (and interact with you) in an
unstructured setting ...
Jambunathan K.
On 21/10/23 13:12, Marvin Gülker wrote:
> 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
>
next prev parent reply other threads:[~2023-10-22 6:01 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 [this message]
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=f240054f-fa22-4329-b33d-352d8900d0d8@gmail.com \
--to=kjambunathan@gmail.com \
--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).