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
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
>
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
>
[ 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,
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
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)
>
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
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
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
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
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
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
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
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.
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
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
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
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
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
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.
>
>
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
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
pters 4, 4.8, 5, 5.4 and 6 (two Headline levels combined) and
Chapter 7 (three Headline levels combined) are examples of joined
headlines and the other (sub)chapters are examples, how Chapters
containing body text are handled. It's mainly a matter of style but in
some situations it doesn't
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
>>
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
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
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
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
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
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
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
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
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
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
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
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č
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
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 ...)
>>
>&g
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 w
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
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.
It is done now and mainly working. The backend uses all the
funcionality of the ox html exporter
48 matches
Mail list logo
