From: <Ken.Williams@thomsonreuters.com>
To: emacs-orgmode@gnu.org
Subject: Re: Options for HTML & PDF export
Date: Fri, 20 May 2011 14:47:37 -0500 [thread overview]
Message-ID: <C9FC2F89.2CC59%ken.williams@thomsonreuters.com> (raw)
Sebastien Vauban <wxhgmqzgwmuf@...> writes:
>
> <Ken.Williams@...> wrote:
> > [...]
> > 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?
I'm not sure - I just hear it used a lot as sort of a "trump card" when
someone wants to impress someone else with how great their methods are, or
if they want to squash someone else's "non-compliant" tool usage.
In this case though, I'm perfectly willing to be impressed with someone's
method. =)
> 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
Thanks Seb, I'll try working with that. I haven't ever done any Lisp
stuff in org-mode, so I may be a little bit lost here, but I'll experiment
a bit.
Is there somewhere in the orgmode manual that talks about where Lisp can
be embedded in documents for interpolation like this? I hadn't seen that
kind of thing before.
>
> Please post your solution for the sake of further sharing...
Definitely will if I find something useful!
--
Ken Williams
Senior Research Scientist
Thomson Reuters
http://labs.thomsonreuters.com
next reply other threads:[~2011-05-20 19:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 19:47 Ken.Williams [this message]
[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
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=C9FC2F89.2CC59%ken.williams@thomsonreuters.com \
--to=ken.williams@thomsonreuters.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).