From: tsd@tsdye.com (Thomas S. Dye)
To: Gunnar Wolf <gwolf@gwolf.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Regarding Babel execution
Date: Tue, 15 Jan 2013 10:15:40 -1000 [thread overview]
Message-ID: <m1obgqyzgz.fsf@tsdye.com> (raw)
In-Reply-To: <20130115185830.GB16515@gwolf.org> (Gunnar Wolf's message of "Tue, 15 Jan 2013 12:58:30 -0600")
Aloha Gunnar Wolf,
Gunnar Wolf <gwolf@gwolf.org> writes:
> Hi,
>
> I recently switched from having several Graphviz files to inlining
> them via Babel in my source Org file. However, I noticed something
> that might either be strange, or might just mean I don't yet
> understand some stuff (as a relative newbie): I usually follow this
> pattern to include my graphics:
>
> #+begin_center
> #+attr_html: height="350"
> #+attr_latex: width=0.5\textwidth
> [[./img/foo.png]]
>
> This is the caption for foo.png
> #+end_center
>
> But if I try to replace this [[./img/foo.png]] with a
> «#+begin_src dot» block, it does not get picked up by Babel (and ends
> up in the generated document as a syntax-highlighted block — So,
> clearly, org-mode understands it's a source block, but Babel ignores
> it).
>
> I currently commented out the #+begin_center and #+end_center
> statements, but I'd really like to have them back. Or, at least, to
> find a more proper way to mark the images (and captions!) as material
> that should be distinguished from the flowing text. Something along
> the lines of the LaTeX «figure» environment.
If you use #+caption:, then the image will be wrapped in a figure
environment when it is exported to latex. See the Org manual at 12.6.5
"Images in LaTeX export."
Here is an example using the a dot source code block and the "new
exporter" which currently resides in contrib/.
#+name: fundamental-model
#+header: :exports results
#+header: :file fundamental-model.pdf
#+BEGIN_SRC dot
graph G
{
graph [margin="0.01"];
d [label = "Dated event", shape ="box"];
t [label = "Target event"];
d -- t [label = "Association", dir = "both", len = 2];
{rank=same; d t;}
}
#+END_SRC
#+CAPTION[The fundamental relationship of a chronological model]: *The fundamental relationship of a chronological model based on radiometric dating.*
#+ATTR_LaTeX: :options "width=232pt" :placement "[ht!]" :comment-include t
#+NAME: fig:fundamental
#+RESULTS: fundamental-model
[[file:fundamental-model.pdf]]
If you use the "old exporter" (which I believe you are using), then you
will need to use LaTeX attributes different than those I've shown, but
you have these working already, so should be in good shape. Also, the
#+caption: syntax is a bit different between the two exporters. For the
old exporter, see the Org manual or
http://orgmode.org/worg/org-tutorials/org-latex-export.html#sec-10-4.
hth,
Tom
--
Thomas S. Dye
http://www.tsdye.com
prev parent reply other threads:[~2013-01-15 20:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 18:58 Regarding Babel execution Gunnar Wolf
2013-01-15 19:54 ` Gunnar Wolf
2013-01-15 20:15 ` Thomas S. Dye [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m1obgqyzgz.fsf@tsdye.com \
--to=tsd@tsdye.com \
--cc=emacs-orgmode@gnu.org \
--cc=gwolf@gwolf.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.