From mboxrd@z Thu Jan 1 00:00:00 1970 From: Russell Adams Subject: RFC: Consistent Latex (& html) publishing environment Date: Thu, 18 Nov 2010 16:50:57 -0600 Message-ID: <20101118225057.GB3139@x201> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from [140.186.70.92] (port=55756 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PJDKF-0007HQ-7L for emacs-orgmode@gnu.org; Thu, 18 Nov 2010 17:51:32 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PJDKD-0000MR-Tf for emacs-orgmode@gnu.org; Thu, 18 Nov 2010 17:51:31 -0500 Received: from jack.asmallorange.com ([74.52.119.82]:41238) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PJDKD-0000Kg-Ok for emacs-orgmode@gnu.org; Thu, 18 Nov 2010 17:51:29 -0500 Received: from 206.180.155.43.adsl.hal-pc.org ([206.180.155.43] helo=localhost) by jack.asmallorange.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from ) id 1PJDK7-0002CG-Eo for emacs-orgmode@gnu.org; Thu, 18 Nov 2010 17:51:23 -0500 Content-Disposition: inline List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode I've had difficulties creating a consistent publishing environment, specifically for latex. I was curious how others did their workflow, or any recommendations the group may have. My latex documents are only of minor complexity, including images and the occasional multiple column area, a header and footer. I'm not a Latex expert, but I know enough to tweak my documents to match my expectations. I have tried using the customizable article types (org-export-latex-classes) to provide consistent pre-document latex header segments. Unfortunately I found I need to customize those frequently. Recently I have started using an article type of "none", which is an empty definition. Then I have manually specified each line in a #+LATEX_HEADER line at the beginning of the file. This works great for a single document, but then multiple documents begin to diverge. Then I have to go find the latest document I've created to use as a template, a non-optimal situation. One technique I have used successfully is to use a Makefile to cause my org documents to be compiled to latex, calling out to emacs and then pdflatex (twice for proper TOC) from there. ---------------------------------------------------------------------- .PHONY: all clean #OBJS := $(patsubst %.org, %.pdf, $(wildcard *.org)) OBJS := Target.pdf CRAP := $(patsubst %.org, %.pdf, $(wildcard *.org)) CRAP += $(patsubst %.org, %.aux, $(wildcard *.org)) CRAP += $(patsubst %.org, %.log, $(wildcard *.org)) CRAP += $(patsubst %.org, %.out, $(wildcard *.org)) CRAP += $(patsubst %.org, %.toc, $(wildcard *.org)) all: clean $(OBJS) clean: rm -f $(CRAP) $(OBJS) %.tex: %.org /usr/bin/emacs -nw \ --eval '(setq enable-local-variables :all)' \ $< \ -f org-export-as-latex \ -f save-buffers-kill-emacs %.pdf: %.tex pdflatex $< pdflatex $< ---------------------------------------------------------------------- This is great, but pops up an emacs session. If I run emacs in --batch mode, it won't load my init file and so loses some of my export customizations... So, what are other folks using? Any comments or suggestions? Thanks. ------------------------------------------------------------------ Russell Adams RLAdams@AdamsInfoServ.com PGP Key ID: 0x1160DCB3 http://www.adamsinfoserv.com/ Fingerprint: 1723 D8CA 4280 1EC9 557F 66E8 1154 E018 1160 DCB3