emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Scott Randby <srandby@gmail.com>
To: emacs-orgmode@gnu.org
Subject: LaTeX Export
Date: Wed, 9 Aug 2017 22:01:27 -0400	[thread overview]
Message-ID: <bd9124f3-a8f3-8c1a-8dc3-68d9960e859b@gmail.com> (raw)

I have a file with a large number of top-level headlines. Each subtree corresponding to a top-level headline is exported to its own PDF file. The subtrees all use the same LaTeX headers except for \hypersetup. Right now, I have to uncomment the \hypersetup manually whenever I export a subtree. I would like to have the export engine automatically recognize which \hypersetup to use instead.

I tried this in the properties associated with a subtree: 

:export_latex_header: \hypersetup{pdfauthor={foo},pdftitle={foo},pdfsubject={foo},pdfkeywords={foo},pdfproducer={foo},pdfcreator={foo}}

Unfortunately, all the other LaTeX headers are unrecognized when I do this. I could put all of the LaTeX headers in the properties of each subtree, but that would make it difficult to make universal changes to the overall style.

Is there some way to do what I want? Something like this?

:export_add_latex_header: \hypersetup{pdfauthor={foo},pdftitle={foo},pdfsubject={foo},pdfkeywords={foo},pdfproducer={foo},pdfcreator={foo}}

Scott Randby

-- 
Scott Randby

srandby@gmail.com

http://srandby.org/

PGP key ID: 0xF2D38A63

Key server: http://pool.sks-keyservers.net/

Key fingerprint: 5418 123E DCD3 7DA0 1770  0BDE 301E E657 F2D3 8A63

             reply	other threads:[~2017-08-10  2:01 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-10  2:01 Scott Randby [this message]
2017-08-10 15:35 ` LaTeX Export Richard Lawrence
2017-08-10 16:03   ` Scott Randby
  -- strict thread matches above, loose matches on Subject: below --
2011-12-31  0:35 LaTeX export York Zhao
2011-12-31  8:09 ` Bastien
2011-12-31 18:07   ` York Zhao
2011-12-31 23:37     ` Steve Hafner
2012-01-01 19:52       ` York Zhao
2010-10-16 18:53 Re: Re: Re: Latex Export chris.m.malone
2010-10-16 19:14 ` Thomas S. Dye
2010-10-16 18:10 chris.m.malone
2010-10-16 18:40 ` Thomas S. Dye
     [not found] <Pine.LNX.4.63.1010161331001.7948@scotty.ess.sunysb.edu>
2010-10-16 17:34 ` chris.m.malone
2010-10-16 17:54   ` Nick Dokos
2010-10-16 14:55 Chris Malone
2010-10-16 21:18 ` Scot Becker
2009-01-05 12:42 LaTeX Export Rasmus Pank Roulund
2009-01-05 15:29 ` Carsten Dominik
2009-01-05 16:10   ` Rasmus Pank Roulund
2009-01-06 12:00     ` Carsten Dominik
2009-01-08 17:48       ` Rasmus Pank Roulund
2009-01-08 21:38         ` Carsten Dominik
2009-02-10 20:46           ` Rasmus Pank Roulund
2009-02-11 10:34             ` Carsten Dominik
2009-02-11 15:56               ` Bernt Hansen
2009-02-11 16:08                 ` Carsten Dominik
2009-02-12 18:25               ` Rasmus Pank Roulund
2009-01-05 15:43 ` Matthew Lundin
2008-12-21 23:12 Latex Export Flávio de Souza
2008-12-22  6:33 ` Carsten Dominik
2008-12-22  8:58   ` Flávio de Souza
2008-10-01 11:16 latex export Johanna Matschke
2008-10-01 12:15 ` Russell Adams
2008-10-10 21:13 ` Carsten Dominik
2007-11-30  3:15 Latex Export Russell Adams
2007-11-30  6:21 ` Giovanni Ridolfi
2007-11-30  7:27   ` Russell Adams
2007-11-30 12:40     ` Bastien
2007-12-01  7:14       ` Russell Adams
2007-12-02 21:04         ` Russell Adams
2007-12-02 21:44           ` Bastien
2007-12-21 22:36             ` Russell Adams
2007-12-21 23:33               ` Bastien
2008-01-09 20:53             ` Russell Adams
2008-01-15 11:26               ` Carsten Dominik
2007-11-02 10:11 LaTeX export Daniel Dehennin
2007-11-02 15:13 ` Bastien
2007-11-02 15:28   ` Daniel Dehennin
2007-11-02 16:05     ` Xiao-Yong Jin
2007-11-02 19:04       ` Bastien
2007-11-02 18:56     ` Bastien
2007-11-02  9:30 Daniel Dehennin
2007-09-28  7:19 Latex Export D. Kapetanakis
2007-09-29 13:23 ` Bastien

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=bd9124f3-a8f3-8c1a-8dc3-68d9960e859b@gmail.com \
    --to=srandby@gmail.com \
    --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).