Ihor Radchenko writes:
> Christian Moe <m...@christianmoe.com> 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 integrate it into org mode? >> >> It would be nice to have. >> >> Conceptually, I'd see it as fitting into org-publish, perhaps, rather >> than as an exporter? With org-publish-project-alist as a convenient >> place to set up various options? > > Not really. ox-publish is more about exporting multiple input > .org/non-.org files into outputs. I was thinking in terms of purpose: organizing export of multiple outputs to be published together. It does that with multiple inputs because, as you say, one-to-one export is the option we currently have. > 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 things work as expected with > .odt, which consist of multiple files under the hood). Yes, I suppose the code for multipage export belongs on the ox.el level. And then one would want to be able to use it out of the box without necessarily having to configure a publishing project, just relying on sensible defaults. So I take that back. (There might be some considerations for ox-publish when using multipage/chunked export *inside* a publishing project, e.g. regarding which levels of output to include in a sitemap, but that's for another day.) Yours, Christian
