From: Marcin Borkowski <mbork@wmi.amu.edu.pl>
To: emacs-orgmode@gnu.org
Subject: Re: Using org to create a TOC for a compilation of separate PDF documents
Date: Thu, 23 May 2013 23:48:03 +0200 [thread overview]
Message-ID: <20130523234803.36aa9323@aga-netbook> (raw)
In-Reply-To: <CA+M2ft-Pi227BcOuPuq5NOZJzr00T=4OyGae9bd2G03oCq7Mxg@mail.gmail.com>
Dnia 2013-05-23, o godz. 15:21:56
John Hendy <jw.hendy@gmail.com> napisał(a):
> I have a use case and am not sure if Org would help or not. I've
> downloaded a bunch of technical data sheets on various materials from
> a vendor. I'd like to create a "booklet" of them with a cover page
> table of contents.
>
> I can create the booklet very easily with Stapler (or similar), but am
> not sure on the best way to generate a clickable linked PDF of the
> individual materials contained in the compiled document.[1] What I'm
> not sure on is how to create a table of contents.
>
> Ideally, I could do something like generate a page count of each
> document and then use this to create the page numbers I'd use to
> create links to, which I thought I could do with Org. Even better
> would be to have [back to top] links as well, since this will end up
> being a multi-hundred page booklet (~100 documents of 2-4 pages each).
>
> Any thoughts on this?
>
> Is it easier to just generate a list of files and use Org to "include"
> them somehow via LaTeX instead of using Stapler to combine them?
I'd just use LaTeX's pdfpages package, possibly with hyperref. (If you
encounter any problems, email me - I've done similar things before, so
I guess I could help you.)
> Thanks for any suggestions!
> John
Best,
--
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Adam Mickiewicz University
next prev parent reply other threads:[~2013-05-23 21:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 20:21 Using org to create a TOC for a compilation of separate PDF documents John Hendy
2013-05-23 21:48 ` Marcin Borkowski [this message]
2013-05-24 9:09 ` AW
2013-05-23 22:20 ` Suvayu Ali
2013-05-23 22:31 ` John Hendy
2013-05-24 0:08 ` Rasmus
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=20130523234803.36aa9323@aga-netbook \
--to=mbork@wmi.amu.edu.pl \
--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).