Re: Re: multipage html output

Re: Re: multipage html output

[Pedro Andres Aranda Gutierrez]

[-- 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 --]

Re: Re: multipage html output

[Ihor Radchenko]

Pedro Andres Aranda Gutierrez <paaguti@gmail.com> writes:

> O... 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.

AFAIU, the feature we are discussing here is not about typesetting, but
about producing multi-file output.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
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>

Re: Re: multipage html output

[Orm Finnendahl]

Am Sonntag, den 07. Juli 2024 um 10:38:08 Uhr (+0000) schrieb Ihor Radchenko:
> AFAIU, the feature we are discussing here is not about typesetting, but
> about producing multi-file output.

 exactly.

--
Orm

Re: Re: multipage html output

[Pedro Andres Aranda Gutierrez]

[-- Attachment #1: Type: text/plain, Size: 1616 bytes --]

HI,

sorry if I didn't express myself correctly. If we define a marker or
command, #+PAGEBREAK for the sake of an example,
then this can be used to produce split HTML files. In other contexts, for
example LaTeX, text and maybe ODT, this would be
more or typesetting, in the sense that they would produce something (the FF
character for text or the \clearpage command
for LaTeX) that is then shown as the text following the command starting at
the beginning of a new page in the typeset output
(and hence my use of the word 'typesetting').

I assume the visual effect being the same, i.e. a forced beginning at a new
page.

Best, /PA

On Sun, 7 Jul 2024 at 12:36, Ihor Radchenko <yantar92@posteo.net> wrote:

> Pedro Andres Aranda Gutierrez <paaguti@gmail.com> writes:
>
> > O... 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.
>
> AFAIU, the feature we are discussing here is not about typesetting, but
> about producing multi-file output.
>
> --
> Ihor Radchenko // yantar92,
> Org mode contributor,
> 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>
>


-- 
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: 2645 bytes --]