Orm Finnendahl writes:
> ...
>> With my idea above, we handle the actual page rendering to a custom
>> backend, which can reuse the normal TOC machinery, possibly encapsulated
>> into sub-backend parameters. We can provide any additional info that is
>> necessary within such sub-backend.
>
> It's
Hi,
don't know, I understand what you're after. Questions below.
Am Samstag, den 17. August 2024 um 14:05:07 Uhr (+) schrieb Ihor Radchenko:
>
> Let's try to do it differently:
>
> 1. Introduce a new INFO plist field :multipage-pages - a list of extra
>pages to be exported in addition
Orm Finnendahl writes:
>> I do not feel like :multipage-split-function is supposed to be export
>> _option_. It is more internal. That's why :translate-alist, where the
>> internals like templates and transcoders lie.
>
> That's how I had it before, but I reasoned it is not a transcoding
> functi
Orm Finnendahl writes:
> [...] Let me know how to proceed.
CC: Ihor :)
Rudy
--
"Chop your own wood and it will warm you twice." --- Henry Ford;
Francis Kinloch, 1819; Henry David Thoreau, 1854
Rudolf Adamkovič [he/him]
http://adamkovic.org
Hi,
again thanks for checking.
Am Montag, den 12. August 2024 um 17:10:25 Uhr (+) schrieb Ihor Radchenko:
>
> :multipage-split-function should be added to the :translate-alist I
> think. It should be documented what :multipage-split-function is
> supposed to do in the docstring of `org-exp
Orm Finnendahl writes:
> I made the changes Ihor suggested and made all docstrings compliant
> with checkdoc. Please check whether this is now how you imagined it.
Thanks! I still have comments, but let's not focus on this minor issue
yet.
> Concerning the options stored in the org-page proper
Hi,
I made the changes Ihor suggested and made all docstrings compliant
with checkdoc. Please check whether this is now how you imagined it.
Concerning the options stored in the org-page properties rather than
in info I mentioned in an earlier mail, I found out it actually
doesn't really change
Hi,
OK, got it, I'll check and implement everything tomorrow when I'm back on my
desk...
Am 11. August 2024 15:47:30 MESZ schrieb Ihor Radchenko :
>Orm Finnendahl writes:
>
>>> Also, as a side note, this docstring does not follow docstring
>>> conventions. Try M-x checkdoc
>>
>> I corrected it
Orm Finnendahl writes:
>> Also, as a side note, this docstring does not follow docstring
>> conventions. Try M-x checkdoc
>
> I corrected it adding your suggestion explicitely. Checkdoc doesn't
> complain about this one any more, but complains all over the place
> with other docstrings not writte
Hi,
Am Samstag, den 10. August 2024 um 12:32:12 Uhr (+) schrieb Ihor
Radchenko:
> I do not see it in
>
> > (defvar org-export-multipage-split-functions nil
> > "List of functions applied to the parse tree after it has been
> > split for multipage output. Each function is called with three
>
Orm Finnendahl writes:
> it was easier than I thought, although still nasty:
>
> https://github.com/ormf/org-mode/tree/org-html-multipage
>
> Maybe you can check whether this is along the lines of what you had in
> mind.
>> Also, please mention that `org-export-multipage-split-functions' are
>>
Am Dienstag, den 06. August 2024 um 20:47:22 Uhr (+0200) schrieb Orm Finnendahl:
>
> I factored out org-html-transcode-multipage to
> org-export-transcode-multipage and got rid of
> org-html-transcode-multipage.
Sorry, I meant "I factored out org-html-transcode-org-data to
org-export-transcode-or
Hi Ihor,
it was easier than I thought, although still nasty:
https://github.com/ormf/org-mode/tree/org-html-multipage
Maybe you can check whether this is along the lines of what you had in
mind.
Am Montag, den 05. August 2024 um 18:22:22 Uhr (+) schrieb Ihor Radchenko:
> I am also a bit su
Hi Ihor,
as always much appreciated. I'll look into that and get back. It
might take a bit depending on how complicated it is as I have some
other things on my org list right now, but we'll get there ;-)
Best,
Orm
Am Montag, den 05. August 2024 um 18:22:22 Uhr (+) schrieb Ihor Radchenko:
>
Orm Finnendahl writes:
> attached are the patches for the multipage html export proposal. The
> tgz file contains all commits after branching from the main branch to
> the org-html-multipage branch (see:
> https://github.com/ormf/org-mode/tree/org-html-multipage)
Thanks! Although creating patch
Orm Finnendahl writes:
> html multipage output is fully working now in the org-export
> compliant way sketched by Ihor.
Great!
> There is a small issue with org-export-as from ox.el: On my machine
> applying the :filter-final-output functions to the final output
> strings delete their :output-
Hi,
html multipage output is fully working now in the org-export
compliant way sketched by Ihor.
There is a small issue with org-export-as from ox.el: On my machine
applying the :filter-final-output functions to the final output
strings delete their :output-file Text Property. Below is a comment
Hi Ihor,
that's spot on what I wanted to suggest, thanks!
--
Orm
Am Samstag, den 27. Juli 2024 um 13:01:12 Uhr (+) schrieb Ihor Radchenko:
> Orm Finnendahl writes:
>
> >> 1. You can use :filter-parse-tree in ox-html backend to replace the
> >>original (org-data ...) AST with a list of
Orm Finnendahl writes:
>> 1. You can use :filter-parse-tree in ox-html backend to replace the
>>original (org-data ...) AST with a list of ((org-page ...)
>>(org-page ...) ...) pseudo-elements and populate INFO channel
>>with auxiliary information you now compute in
>>`org-html-pr
Hi,
I can implement everything now with your changes, but not exactly in
the way you propose:
Am Mittwoch, den 24. Juli 2024 um 10:20:16 Uhr (+) schrieb Ihor Radchenko:
> I believe that my changes should allow you to implement multipage export
> in the following way:
>
> 1. You can use :fil
Hi,
Am Donnerstag, den 25. Juli 2024 um 10:04:21 Uhr (+) schrieb Ihor Radchenko:
>
> Do you know the source of the performance problem?
When I last checked it was 4.5 Seconds vs 2.2 Seconds and I assume it
was due to the gc kicking in, but whatever the reason I checked back
and forth between
Orm Finnendahl writes:
> org-export--write-ouput inserts the output string into a temp-buffer
> before writing it to file. When exporting to multipage I found out
> that this imposes a pretty significant performance hit. That's why I
> write the output string directly to file in my own code.
>
>
Hi Ihor,
another thing:
org-export--write-ouput inserts the output string into a temp-buffer
before writing it to file. When exporting to multipage I found out
that this imposes a pretty significant performance hit. That's why I
write the output string directly to file in my own code.
Is it sens
Orm Finnendahl writes:
> Am Mittwoch, den 24. Juli 2024 um 10:20:16 Uhr (+) schrieb Ihor Radchenko:
>>
>> 1. org-data will be transcoded using `org-export-transcode-org-data',
>>which can be overridden by setting org-data transcoders in the
>>individual backends.
>
> Just for clarifi
Hi Ihor,
I studied your proposal and changes in ox.el. It is pretty clear now
and I agree that this is the right way to do it with regards to the
architecture of ox. Thanks for putting in your time.
Am Mittwoch, den 24. Juli 2024 um 10:20:16 Uhr (+) schrieb Ihor Radchenko:
>
> 1. org-data w
Hi Ihor,
thanks a lot for the patches and explanations. Your assessment makes
sense and I agree that we should stick to the current design as much
as possible. I will go ahead and adapt my ox-html.el code the way you
propose and use your patched ox.el for this. It shouldn't take too
much effort a
Orm Finnendahl writes:
> To recapitulate: In my code, org-export-as calls process-multipage in
> the backend. This function:
>
> - collects and adds information necessary for org-multipage to do its
> job, splitting the document into different parts, etc. and
>
> - then calls org-export-data on
Am Dienstag, den 23. Juli 2024 um 17:10:17 Uhr (+) schrieb Ihor Radchenko:
> > 2. If a transcoder for org-data is defined, call that and return nil
> >from org-export-date.
> >
> >Otherwise return the transcoded string.
>
> > 3. In case a string is returned, process it as it is done in
Am Dienstag, den 23. Juli 2024 um 17:13:56 Uhr (+) schrieb Ihor Radchenko:
>
> What I had in mind if using backend-specific :filter-options.
> If a backends needs to enable headline numbering unconditionally, when
> :multipage is used, it can install :filter-options filter that will set
> :sec
Orm Finnendahl writes:
>> If you think that multipage export should use a different set of
>> options, we need to implement it differently.
>
> Is that a semantic problem so we need to implement an option like
> :always-collect-headline-numbering instead of :multipage in
> org-export-numbered-hea
[ Adding the mailing list back to CC ]
Orm Finnendahl writes:
> Let me recapitulate to make sure I understand you completely:
>
> 1. Replace the call to org-export-transcode-page at the end of
>ord-export-as by a call to org-export-data
Yes.
> 2. If a transcoder for org-data is defined, ca
Am Dienstag, den 23. Juli 2024 um 16:20:39 Uhr (+) schrieb Ihor Radchenko:
> Orm Finnendahl writes:
>
> >> `org-export--collect-headline-numbering' is evaluated unconditionally,
> >> regardless of num:t or num:nil settings.
> >
> > Are you sure? org-export--collect-headline-numbering has this
Orm Finnendahl writes:
>> `org-export--collect-headline-numbering' is evaluated unconditionally,
>> regardless of num:t or num:nil settings.
>
> Are you sure? org-export--collect-headline-numbering has this in its
> body:
>
> (org-element-map data 'headline
> (lambda (headline)
> (w
Am Dienstag, den 23. Juli 2024 um 15:01:13 Uhr (+) schrieb Ihor Radchenko:
>
> Multipage export is something I want to see as a part of Org mode.
> I thought that you were aiming for upstream from the very beginning. I
> never opposed that.
Ok, thanks. You're right, I was aiming at that from
tAm Dienstag, den 23. Juli 2024 um 14:19:00 Uhr (+) schrieb Ihor Radchenko:
> Orm Finnendahl writes:
>
> > ... I think printing
> > headline numbers should get handled in the transcoding stage of the
> > backend and not before.
>
> I am confused here.
> What do you mean by "printing"?
I mea
Am Dienstag, den 23. Juli 2024 um 12:52:51 Uhr (+) schrieb Ihor Radchenko:
> Orm Finnendahl writes:
>
> > Thanks also for the info regarding how to contribute. It'd be nice if
> > you could gibe me a go in case you approve the proposal.
>
> May you please elaborate?
Writing documentation an
Orm Finnendahl writes:
>> > - added :multipage case to `org-export-as', calling :process-multipage
>> > callback submitted in info. In the multipage case, org-export-as
>> > returns nil relying on :process-multipage to do the exporting, while
>> > in the single page case it returns the tran
Orm Finnendahl writes:
> ... I think printing
> headline numbers should get handled in the transcoding stage of the
> backend and not before.
I am confused here.
What do you mean by "printing"?
> ... Multipage export behind the scenes is
> completely dependant on headline numbering, even if hea
Orm Finnendahl writes:
> Thanks also for the info regarding how to contribute. It'd be nice if
> you could gibe me a go in case you approve the proposal.
May you please elaborate?
All you need to do is cloning/forking Org mode repository, making edits
there, and sharing the link to your branch.
Hi,
thanks for the quick response!
Am Dienstag, den 23. Juli 2024 um 10:24:54 Uhr (+) schrieb Ihor
Radchenko:
> I will first focus on reviewing changes to ox.el.
>
> > ox.el
> >
> > - added `org-export-collect-tree-info', and
>
> And it is not used anywhere... What is the purpose?
That w
Orm Finnendahl writes:
> I managed to get the proposal for the multipage output done. Please
> review it and let me know what you think/would prefer to change. I'm
> pretty open about it.
>
> You can find it here:
>
> https://github.com/ormf/ox-html-multipage
>
> The code is intended to replace
Hi,
I managed to get the proposal for the multipage output done. Please
review it and let me know what you think/would prefer to change. I'm
pretty open about it.
You can find it here:
https://github.com/ormf/ox-html-multipage
The code is intended to replace ox.el and ox-html.el. The repositor
Hi,
while doing it, I found out it only needs one function call in
org-export-as for splitting, transcoding and writing the
file. Currently it's called :process-multipage, but we can change that
later.
I'll take your advice and use an :export-option for multipage.
--
Orm
Am Samstag, den 13. Ju
Orm Finnendahl writes:
>> This sounds like some kind of extension to :filter-final-output.
>> I think it should also be an ok option.
>
> :filter-final-output functions could be used, but the name is a bit
> misleading. Therefore I'd suggest to extend the
> org-export-filters-alist with :export-f
Hi,
Am Donnerstag, den 11. Juli 2024 um 12:35:21 Uhr (+) schrieb Ihor Radchenko:
> > ok, that's what you mean. I can do this, but don't you think it'd be
> > more consistent with the general layout of ox, if org-export-as uses a
> > callback function to call on each generated string with the f
Orm Finnendahl writes:
> If org-export-as returns just one string, then it will reparse the
> parse tree each time it needs to generate an output string. But as you
> say below, you rather think org-export-as returns a list of strings
> for the multipage case.
Got it now.
>> What I have in mind
Am Dienstag, den 09. Juli 2024 um 18:08:10 Uhr (+) schrieb Ihor Radchenko:
> Orm Finnendahl writes:
> > If toplevel functions like org-export-to-file use org-export-as, than
> > org-export-as should only be concerned with generating the string but
> > not with reparsing.
>
> Sorry, but I do n
Orm Finnendahl writes:
>> >> > - org-html-multipage-front-matter
>> >> >
>> >> > A list to specify pages in front of the headlines of the
>> >> > document. Possible values are 'title, 'title-toc and 'toc. title-toc
>> >> > is a combined page containing the title and the toc. Multiple
>> >>
Am Dienstag, den 09. Juli 2024 um 17:55:51 Uhr (+) schrieb Ihor Radchenko:
>
> To address such situations, we may, for example, allow an alternative
> "multi" version of each export keyword to act specially when multipage
> export is used. Consider that there is an export option #+SAMPLEOPTION
Orm Finnendahl writes:
>> Or we can make `org-export-as' retain INFO channel when returning the
>> output. Then, we can make `org-export-to-file' make use of the INFO
>> channel to decide the file name. This way, there will be no need to
>> decide the file name before running the parsing.
>
> Are
Orm Finnendahl writes:
>> Is there any situation when you need to export the full document
>> vs. multipage to different places?
>
> Actually that is what I'm currently doing (and what I need for my
> publishing chain): The single-page document is not in the html folder
> used for the multipage d
Hi Ihor,
Am Montag, den 08. Juli 2024 um 15:56:48 Uhr (+) schrieb Ihor
Radchenko:
>
> Or we can make `org-export-as' retain INFO channel when returning the
> output. Then, we can make `org-export-to-file' make use of the INFO
> channel to decide the file name. This way, there will be no need
Am Montag, den 08. Juli 2024 um 15:29:47 Uhr (+) schrieb Ihor Radchenko:
> Orm Finnendahl writes:
>
> > For the backend I'm planning to realize the following options
> > (implemented as custom variables, which can be overwritten in the
> > document):
> >
> > - org-html-multipage-export-direct
Orm Finnendahl writes:
>> Yes, roughly like this. Ideally, we should simply modify
>> `org-export-as', but handling output file name may be a bit tricky -
>> it is somewhat awkwardly placed in the current ox.el API (see the
>> discussion in
>> https://list.orgmode.org/orgmode/25393.61240.135445.
Hi,
Am Montag, den 08. Juli 2024 um 15:05:58 Uhr (+) schrieb Ihor Radchenko:
>
> We might also consider adding MULTIPAGE as an additional argument to the
> API function (just like BODY-ONLY, VISIBLE-ONLY, SUBTREEP that we
> already use), but that's probably an implementation idea we may or ma
Orm Finnendahl writes:
> For the backend I'm planning to realize the following options
> (implemented as custom variables, which can be overwritten in the
> document):
>
> - org-html-multipage-export-directory
>
> The directory for the exported files (relative or absolute).
I am wondering abou
Orm Finnendahl writes:
> I'm trying to grasp what you are proposing and have some questions to
> make sure I've understood (please correct me if I'm wrong):
(Just for some context, do not take my ideas as something you must
follow 100% accurately. I am largely brainstorming here. So, feel free
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 pro
Hi Ihor,
I'm trying to grasp what you are proposing and have some questions to
make sure I've understood (please correct me if I'm wrong):
- Your idea is to add an option to the backend definition called
org-export-pages which is a plist containing information about the
way to export the doc
Hi,
this is a report of my current state with the html multipage export
backend: I finished most of the heavy lifting and am currently trying
to integrate it with the old backend into a single file.
For now I plan to use a custom menu-entry ('m') in the export dialog
rather than doing it with an
Am Sonntag, den 07. Juli 2024 um 10:38:08 Uhr (+) schrieb Ihor Radchenko:
> AFAIU, the feature we are discussing here is not about typesetting, but
> about producing multi-file output.
exactly.
--
Orm
Pedro Andres Aranda Gutierrez 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 dis
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 pa
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 functionali
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 \cleardoublepa
Orm Finnendahl writes:
> Sure. I'm not at all familiar with the peculiarities of other output
> backends, but see your point. If you can give any hints or have any
> ideas *how* we could find general rules for separating the subtrees,
> which cover foreseeable use cases, or devise a flexible mech
Hi Ihor,
thanks for your time to study the code and your very valuable input,
much appreciated!
Am Donnerstag, den 04. Juli 2024 um 11:41:35 Uhr (+) schrieb Ihor
Radchenko:
>
> 2. An ability to produce multiple pages from a single part of Org file.
>For example, consider an Org document
Orm Finnendahl writes:
>> I'd rather see this kind of feature being a part of ox.el - an option to
>> export one .org to many smaller files. Currently, we only have an option
>> to export one .org (or part of it) to a single string/file. (And then,
>> ox-odt has to try various kludges to make thi
Hi,
Am Mittwoch, den 03. Juli 2024 um 11:05:39 Uhr (+) schrieb Ihor
Radchenko:
>
> Not really. ox-publish is more about exporting multiple input
> .org/non-.org files into outputs.
>
> I'd rather see this kind of feature being a part of ox.el - an option to
> export one .org to many smaller
Orm Finnendahl writes:
> - Is there widespread interest to fully integrate it into org mode?
Definitely. :)
Rudy
--
"It is no paradox to say that in our most theoretical moods we may be
nearest to our most practical applications." --- Alfred North
Whitehead, 1861-1947
Rudolf Adamkovič [he/h
Ihor Radchenko writes:
> Christian Moe writes:
>
>>> after my clunky publishing chain from org to gitbook with multipage
>>> page output broke down recently I finally decided to tackle adding an
>>> export backend for multipage html output to org-export.
>>>
>>> (... snip ...)
>>>
>>> - Is the
Christian Moe writes:
>> after my clunky publishing chain from org to gitbook with multipage
>> page output broke down recently I finally decided to tackle adding an
>> export backend for multipage html output to org-export.
>>
>> (... snip ...)
>>
>> - Is there widespread interest to fully inte
Orm Finnendahl writes:
> Hi,
>
> after my clunky publishing chain from org to gitbook with multipage
> page output broke down recently I finally decided to tackle adding an
> export backend for multipage html output to org-export.
>
> (... snip ...)
>
> - Is there widespread interest to fully i
Orm Finnendahl writes:
> https://github.com/ormf/ox-html-multipage
Do I understand it right, that this exports a single org file into
multiple HTML files in the html subfolder?
In the interest of making it possible to build upon the code, can you
make the license GPL v2.0 *or later*?
Best wish
74 matches
Mail list logo
