From: Yasushi SHOJI <yasushi.shoji@gmail.com>
To: Alan Schmitt <alan.schmitt@polytechnique.org>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: exporting a big project in multiple files to both pdf and html
Date: Thu, 1 Feb 2018 11:17:27 +0900 [thread overview]
Message-ID: <CAELBRWJ2XY0VAaxRhopgF-O9vEzZ0ABpR+DxrtOBVxjnTv39mw@mail.gmail.com> (raw)
In-Reply-To: <m2wp05hma5.fsf@ren101r.vpn.inria.fr>
Hi,
On Fri, Jan 26, 2018 at 2:37 AM, Alan Schmitt
<alan.schmitt@polytechnique.org> wrote:
> I'm working on a project that is becoming too big to manage as a single
> file, so I'm looking at splitting it in several files. This would also
> have the benefit of generating several smaller html pages instead of a
> single huge one.
Does Org support this? or do you just export each file?
> My question is about pdf export. Is it possible to take a document made
> of multiple org files and generate a single book from it? I'm worried
> that if I use a master org file that includes the other ones, the links
> between chapters would break.
You can just use '#+INCLUDE' construct and Org will take care.
But that will break your follow of exporting html files described above.
How about having two master files, one for html and one for pdf.
In the html-master.org, you use links to connect. And
in the pdf-master.org, you can just #+INCLUDE your files.
It'd be nice if we could tell exporters that we want multiple files from one
org file.
BTW, I don't think we have direct pdf exporter. So, you must be talking about
the latex exporter, right?
--
yashi
next prev parent reply other threads:[~2018-02-01 2:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-25 17:37 exporting a big project in multiple files to both pdf and html Alan Schmitt
2018-02-01 2:17 ` Yasushi SHOJI [this message]
2018-02-01 8:45 ` Alan Schmitt
2018-02-01 11:09 ` Yasushi SHOJI
2018-02-01 12:29 ` Alan Schmitt
2018-02-01 12:56 ` Nicolas Goaziou
2018-02-01 13:47 ` Alan Schmitt
2018-02-02 0:38 ` Yasushi SHOJI
2018-02-02 7:41 ` Alan Schmitt
2018-02-02 9:41 ` Yasushi SHOJI
2018-02-02 13:13 ` Alan Schmitt
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=CAELBRWJ2XY0VAaxRhopgF-O9vEzZ0ABpR+DxrtOBVxjnTv39mw@mail.gmail.com \
--to=yasushi.shoji@gmail.com \
--cc=alan.schmitt@polytechnique.org \
--cc=emacs-orgmode@gnu.org \
/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).