From: "Daniel Goldin" <danielgoldin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Latex exporting
Date: Wed, 6 Aug 2008 21:08:39 -0700 [thread overview]
Message-ID: <d1c140d50808062108k2aa56bd3j3672f8d8abf4eb4e@mail.gmail.com> (raw)
In-Reply-To: <20080806213241.GG24521@thinkpad.adamsinfoserv.com>
[-- Attachment #1.1: Type: text/plain, Size: 4121 bytes --]
Thank you so much for sharing this!
d.
On Wed, Aug 6, 2008 at 2:32 PM, Russell Adams <RLAdams@adamsinfoserv.com>wrote:
> On Tue, Jul 29, 2008 at 06:46:37PM -0500, Russell Adams wrote:
> > I've finally embarked upon a journey of exploration, attempting to
> > publish quality PDF's via org and latex.
> >
>
> As a follow up to my command line tricks, I want to share how to get
> headers and footers into Latex exports.
>
> First, the default latex exporter uses A4 paper, I need letter. To
> change that I use the following in my .emacs to add a custom export
> type, "myarticle".
>
> This includes expanding the default margins via the geometry package,
> and sets up packages I will use later like fancyhdr and lastpage. I
> also include a default footer on my work, which includes the filename
> and date, page numbering, and copyright statement with current year.
>
> ~/.emacs ------------------------------------------------------------
>
> (setq org-export-latex-classes (cons '("myarticle"
> "% BEGIN My Article Defaults
> \\documentclass[10pt,letterpaper]{article}
>
> \\usepackage[letterpaper,includeheadfoot,top=0.5in,bottom=0.5in,left=0.75in,right=0.75in]{geometry}
> \\usepackage[utf8]{inputenc}
> \\usepackage[T1]{fontenc}
> \\usepackage{hyperref}
> \\usepackage{lastpage}
> \\usepackage{fancyhdr}
> \\pagestyle{fancy}
> \\renewcommand{\\headrulewidth}{1pt}
> \\renewcommand{\\footrulewidth}{0.5pt}
>
> % Default footer
> \\fancyfoot[L]{\\small \\jobname \\\\ \\today}
> \\fancyfoot[C]{\\small Page \\thepage\\ of \\pageref{LastPage}}
> \\fancyfoot[R]{\\small \\copyright \\the\\year\\ Me}
> % END My Article Defaults
>
> "
> ("\\section{%s}" . "\\section*{%s}")
> ("\\subsection{%s}" . "\\subsection*{%s}")
> ("\\subsubsection{%s}" . "\\subsubsection*{%s}")
> ("\\paragraph{%s}" . "\\paragraph*{%s}")
> ("\\subparagraph{%s}" . "\\subparagraph*{%s}"))
>
> org-export-latex-classes))
>
> ------------------------------------------------------------
>
> To use this custom type I add this as the first line in my Org file:
>
> #+LaTeX_CLASS: myarticle
>
> Further customization is easy using a local variables block at the end
> of my file.
>
> End of file.org --------------------------------------------------
>
> #+ Local Variables:
> #+ org-export-latex-title-command: ""
> #+ org-export-latex-append-header: "\
> #+ \\usepackage{graphicx}
> #+ \\usepackage{multicol}
> #+ \\geometry{headheight=47pt}
> #+ \\fancyhead[L]{\\LARGE This is the header title}
> #+ \\fancyfoot[L]{\\small Overridden filename\\\\ \\today}
> #+ "
> #+ End:
> ------------------------------------------------------------
>
> Changing the title command means no title page is created, so I must
> make my own. Omitting that line will create the normal title page.
>
> Other packages I include via the append header variable are graphicx
> for PNG support, multicol for two columns, overriding the page header
> height in case I get a warning its too tall, and new headers to
> override the defaults (ie: I want something better than a filename).
>
> I'm exporting to latex via a Makefile, using the command line tricks I
> posted earlier. The Makefile is attached.
>
> I've attached a sample org file and its output PDF using these
> settings, because one of my frustrations learning latex has been the
> lack of finished output for examples. ;]
>
> Enjoy!
>
> ------------------------------------------------------------------
> Russell Adams RLAdams@AdamsInfoServ.com
>
> PGP Key ID: 0x1160DCB3 http://www.adamsinfoserv.com/
>
> Fingerprint: 1723 D8CA 4280 1EC9 557F 66E8 1154 E018 1160 DCB3
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
>
> iEYEARECAAYFAkiaGHkACgkQEVTgGBFg3LPwcQCeJMBRNJhDujh1f8HIt0x+3jY2
> A58AoMjnNFTPvjzU7xYRj+lAtqymxB7J
> =9EH5
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
>
--
Daniel Goldin
213.926.1960
[-- Attachment #1.2: Type: text/html, Size: 5528 bytes --]
[-- Attachment #2: Type: text/plain, Size: 204 bytes --]
_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2008-08-07 4:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 23:46 Latex exporting Russell Adams
2008-08-06 21:32 ` Russell Adams
2008-08-07 4:08 ` Daniel Goldin [this message]
2008-09-10 18:54 ` Frank Dekens
2008-09-10 22:32 ` Russell Adams
2008-09-24 0:52 ` Frank Dekens
2008-09-25 5:42 ` Russell Adams
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=d1c140d50808062108k2aa56bd3j3672f8d8abf4eb4e@mail.gmail.com \
--to=danielgoldin@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).