emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Torsten Wagner <torsten.wagner@gmail.com>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: nicholas.dokos@hp.com, Org Mode Mailing List <emacs-orgmode@gnu.org>
Subject: Re: [babel] create tikz pictures in an floating LaTeX environment
Date: Sat, 8 Oct 2011 23:45:29 +0900	[thread overview]
Message-ID: <CAPaq-gOPRNdt9DqxEO7WGBYC0eKJOggvXqXhMOUdLiFwLLQfkQ@mail.gmail.com> (raw)
In-Reply-To: <8762k0suk3.fsf@gmail.com>

Hi Eric

>> ``:results output silent'' should suppress that I think.
> Nick's solution should work well.  Also, (if you're exporting to LaTeX)
> couldn't you just combine the tikz picture and the wrapping figure
> environment into a single begin_latex block?

Yep Nick solution is working fine. I just wonder what is the order of
execution during export. E.g. if I generate the link to a file as
output and place it directly under the lines to add a picture in
org-mode, I thought the code block would be execute first and the
result would replace the function call. The exporter will find a link
to a picture and export it as usual. This was the reason I thought the
following code should work.

#+CAPTION:    my great picture
#+LABEL:      fig:my_picture
#+srcname: mypicture
#+begin_src latex :file fig/mypicture.pdf :packages '(("" "tikz"))
:border 1em :fit
 \begin{tikzpicture}[line width=1pt,text centered, inner sep = 2]
     \draw[fill=red!50] (0,0) rectangle  ++(5,1);
     \draw[fill=yellow!50] (1,1) rectangle  ++(1,0.25);
     \draw[fill=yellow!50] (3,1) rectangle  ++(1,0.25);
     \draw[fill=green!50] (0.75,1) rectangle  ++(1.5,-0.4);
     \draw[fill=green!50] (2.75,1) rectangle  ++(1.5,-0.4);

or alternatively
#+CAPTION:    my great picture
#+LABEL:      fig:my_picture
#+call: mypicture()

As for putting all figure environment and tikz into one latex-code block.
First of all I thought that :file fig/mypicture.pdf will generate and
process an individual LaTeX file. Thus, I could not use any commands
for the main manuscript right? Sure I could skip the :file command
however, I would prefer to generate each picture as an individual pdf
file. This gives me much more flexibility. I can easily convert them
into any other format and share them individually with co-workers.
Furthermore, many journals are very strict (and minimal) with there
supported LaTeX environment. The tikz package is often not installed
on there machines and the upload process would fail. In addition some
journals require to upload each figure individually. Thus, I am used
already to generate individual pdf-files for each figure and include
them into the manuscript by a simple \includegraphic line.

Thanks for the help


CC. I notice something else regarding to babel. Please see my next post

  parent reply	other threads:[~2011-10-08 14:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-07 14:02 [babel] create tikz pictures in an floating LaTeX environment Torsten Wagner
2011-10-07 14:13 ` Nick Dokos
2011-10-07 15:14   ` Eric Schulte
2011-10-07 21:26     ` Darlan Cavalcante Moreira
2011-10-07 21:44       ` Tom Prince
2011-10-08  6:32       ` Achim Gratz
2011-10-08 14:45     ` Torsten Wagner [this message]
2011-10-08 19:49       ` Eric Schulte
2011-10-09  7:30       ` Christian Moe
2011-10-08 14:29   ` Torsten Wagner

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:

  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=CAPaq-gOPRNdt9DqxEO7WGBYC0eKJOggvXqXhMOUdLiFwLLQfkQ@mail.gmail.com \
    --to=torsten.wagner@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=nicholas.dokos@hp.com \
    --cc=schulte.eric@gmail.com \


* 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


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).