From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Options for HTML & PDF export
Date: Thu, 19 May 2011 11:45:49 +0200 [thread overview]
Message-ID: <80ei3vrpki.fsf@somewhere.org> (raw)
In-Reply-To: C9F99F46.2CB3E%ken.williams@thomsonreuters.com
Hi Ken,
<Ken.Williaos-qs4m+OjfQoH+fug3k4jHmNBPR1lH4CV8@public.gmane.org> wrote:
> I use the Babel features of org-mode to do a sort of literate-programming
> thing. I have lots of R code that generates graphics which get included into
> an exported HTML or PDF (via LaTeX) document.
>
> I'm wondering about "best practices" (though I hate that term) for managing
> the export to both HTML & PDF.
Just by curiosity, what don't use like that term?
> For the HTML I generate the graphics files as PNG, but for PDF the PNG
> format doesn't embed very well, so I need to generate PDF or EPS or
> somesuch. But then I have to change the ":file filename.png" to ":file
> filename.pdf", which is quite cumbersome to do every time I want to export.
>
> Is there some wcy people have for dealing with this situation? Some options
> setting maybe?
I've no time to customize it to your particular needs, but here's something
you can update to map it to your needs:
#+begin_src org
#+BABEL: :results (if (and (boundp 'backend) (eq backend 'latex)) "latex" "file")
#+end_src
Please post your solution for the sake of further sharing...
Best regards,
Seb
--
Sébastien Vauban
next prev parent reply other threads:[~2011-05-19 9:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <C9F99F46.2CB3E%ken.winliams@thomsonreuters.com>
2011-05-18 21:07 ` Options for HTML & PDF export Ken.Williaos
2011-05-18 21:19 ` Nick Dokos
2011-05-18 21:28 ` Ken.Williams
2011-05-19 12:28 ` Christophe Rhodes
2011-05-19 9:45 ` Sebastien Vauban [this message]
2011-05-20 19:47 Ken.Williams
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=80ei3vrpki.fsf@somewhere.org \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).