From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
To: orm.finnendahl@selma.hfmdk-frankfurt.de
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: Re: multipage html output
Date: Sun, 7 Jul 2024 07:39:05 +0200 [thread overview]
Message-ID: <CAO48Bk9_OYYgkGMyPCJenda89i=WfOfacHkQ+JYHBLiU3fUQxg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2275 bytes --]
Hi Oorm
thanks for the lengthy answer.
>Hi,
>
>Am Samstag, den 06. Juli 2024 um 07:47:43 Uhr (+0200) schrieb Pedro Andres
Aranda Gutierrez:
>> Sorry for bumping in, I've been more off than on in the last couple of
>> weeks...
>> Just a stupid question: have you considered any marker to force a page
>> break?
>> That would make this functionality portable to other exporters like
LaTeX,
>> where
>> you can force a page break with \clearpage or \cleardoublepage.
>
> although this is of course possible, currently I'm not planning to
>implement it.
>
>Regarding html export I see some problems with that idea:
>
>1. It would either open a new can of worms if this page would be added
> to the toc with all sorts of ensuing problems like naming, etc. and
> getting out of sync with the Latex document's toc.
OK, right, didn't think about it that way... Because this functionality
would be more about typesetting than about anything else. When you export a
doc to LaTeX, you barely
care about the TOC, because that is generated "behind the scenes" from
headings only.
>or
>
>2. Those additinal pages don't get added to the toc and are only
> reachable by navigation elements, which I consider suboptimal (and
> you'd still have to name them).
But that's exactly what this is about... In LaTeX is would go unnoticed by
the exported,
and maybe to export to plain text you would add a form feed (^L, or FF) and
increment the page number. I suspect that for ODT there is something to
force this too.
>
>In any case, currently I'm facing many problems concerning the
>glorious hairy details and am glad if I can sort them out in a way
>that they are general enough to be added to ox. Adding additional
>engines to handle page breaks the way you envision should then be
>feasible without reinventing the wheel.
>
Thanks for your view... maybe the design of this feature involves creating
a #+PAGE: directive that is translated to a NOP when exporting to HTML and
to whatever it needs for other exporters,
Best, /PA
--
Fragen sind nicht da, um beantwortet zu werden,
Fragen sind da um gestellt zu werden
Georg Kreisler
Headaches with a Juju log:
unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should run
a leader-deposed hook here, but we can't yet
[-- Attachment #2: Type: text/html, Size: 2989 bytes --]
next reply other threads:[~2024-07-07 5:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-07 5:39 Pedro Andres Aranda Gutierrez [this message]
2024-07-07 10:38 ` Re: multipage html output Ihor Radchenko
2024-07-07 10:39 ` Orm Finnendahl
2024-07-08 5:15 ` Pedro Andres Aranda Gutierrez
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='CAO48Bk9_OYYgkGMyPCJenda89i=WfOfacHkQ+JYHBLiU3fUQxg@mail.gmail.com' \
--to=paaguti@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=orm.finnendahl@selma.hfmdk-frankfurt.de \
/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).