[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [O] Publishing using the new exporter

From: Robert Klein
Subject: Re: [O] Publishing using the new exporter
Date: Sat, 06 Oct 2012 16:52:39 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120825 Thunderbird/15.0

On 10/06/2012 01:17 PM, Nicolas Goaziou wrote:

Another issue I encountered, when publishing(!) to pdf, the resulting
pdfs didn't have any images.  This is probably caused by the images
beind created in :base-directory and the pdf being created in


Eric: Is there any mechanism to force (automatically) Babel code to
generate files in a given publishing directory instead of the current
directory (notwithstanding :dir argument)?

Ideally, I would like to provide publishing-directory as an optional
argument to `org-export-blocks-preprocess', since it is the only
interface between the export engine and Babel.

Any opinion on this?



for pdf publishing I'd rather prefer the tex file also to be created in the base directory and only the pdf appearing in the publishing-directory, if there is a way.

My publishing-directories are often publicly accessible, where I'd rather not accumulate intermediate files.

As a workaround I currently use the base-directory as publishing-directory plus a second project using org-e-publish-attachment to copy the pdfs to their intended location. (I'm using org-e-publish-attachment for images of html files, so why shouldn't I use it for pdfs...

Best regards

reply via email to

[Prev in Thread] Current Thread [Next in Thread]