how to include graphics in pdf output

how to include graphics in pdf output

[Christopher W. Ryan]

I am running org mode 7.7 on Win XP. I hope to export a document to pdf,
and I'd like to include an image in it. The image is a file called
DataLoggerImage.jpg; it resides in the same directory as my org file.

These are the first three lines of my org file:

#+OPTIONS:   todo:nil toc:nil tags:nil
#+LATEX_HEADER: \usepackage[margin=1in]{geometry}
#+LATEX_HEADER: \usepackage{graphicx}


I have tried the following code to include a figure (tried both
approaches simultaneously, and the second one alone, neither with success):

\begin{figure}\centering
\includegraphics{DataLoggerImage}
\caption{Temperature and humidity data logger}\label{datalogger}
\end{figure}

#+CAPTION: Temperature and humidity data logger
#+LABEL:   datalogger
[[./DataLoggerImage.jpg]]

The figure does not appear in the resulting pdf.  Any advice as to what
I am doing wrong?

Thanks.

--Chris
-- 
Christopher W. Ryan, MD
SUNY Upstate Medical University Clinical Campus at Binghamton
425 Robinson Street, Binghamton, NY  13904
cryanatbinghamtondotedu

"Observation is a more powerful force than you could possibly reckon.
The invisible, the overlooked, and the unobserved are the most in danger
of reaching the end of the spectrum. They lose the last of their light.
From there, anything can happen . . ."  [God, in "Joan of Arcadia,"
episode entitled, "The Uncertainty Principle."]

Re: how to include graphics in pdf output

[Nick Dokos]

Christopher W. Ryan <cryan@binghamton.edu> wrote:

> I am running org mode 7.7 on Win XP. I hope to export a document to pdf,
> and I'd like to include an image in it. The image is a file called
> DataLoggerImage.jpg; it resides in the same directory as my org file.
> 
> These are the first three lines of my org file:
> 
> #+OPTIONS:   todo:nil toc:nil tags:nil
> #+LATEX_HEADER: \usepackage[margin=1in]{geometry}
> #+LATEX_HEADER: \usepackage{graphicx}
> 
> 
> I have tried the following code to include a figure (tried both
> approaches simultaneously, and the second one alone, neither with success):
> 
Not sure what you mean here: did you just add the latex code into your org file
as is?

> \begin{figure}\centering
> \includegraphics{DataLoggerImage}
> \caption{Temperature and humidity data logger}\label{datalogger}
> \end{figure}
> 
> #+CAPTION: Temperature and humidity data logger
> #+LABEL:   datalogger
> [[./DataLoggerImage.jpg]]
> 
> The figure does not appear in the resulting pdf.  Any advice as to what
> I am doing wrong?
> 

Can you post your org file and the tex file that's produced on export?

Thanks,
Nick

Re: how to include graphics in pdf output

[suvayu ali]

On Mon, Mar 19, 2012 at 20:53, Nick Dokos <nicholas.dokos@hp.com> wrote:
>> [[./DataLoggerImage.jpg]]
>>
>> The figure does not appear in the resulting pdf.  Any advice as to what
>> I am doing wrong?
>>
>
> Can you post your org file and the tex file that's produced on export?
>

Is the above correct syntax? Shouldn't it be as shown below?

[[file:./DataLoggerImage.jpg]]

-- 
Suvayu

Open source is the future. It sets us free.

Re: how to include graphics in pdf output

[Nick Dokos]

suvayu ali <fatkasuvayu+linux@gmail.com> wrote:

> On Mon, Mar 19, 2012 at 20:53, Nick Dokos <nicholas.dokos@hp.com> wrote:
> >> [[./DataLoggerImage.jpg]]
> >>
> >> The figure does not appear in the resulting pdf.  Any advice as to what
> >> I am doing wrong?
> >>
> >
> > Can you post your org file and the tex file that's produced on export?
> >
> 
> Is the above correct syntax? Shouldn't it be as shown below?
> 
> [[file:./DataLoggerImage.jpg]]
> 

I had the same reaction at first, but I tried it and the pdf export went
through without a hitch in either case. I'm not sure whether that's intended
behavior or an accident though.

Nick

Re: how to include graphics in pdf output

[Christopher W. Ryan]

[-- Attachment #1: Type: text/plain, Size: 1164 bytes --]

I've attached a small org file that reproduces my problem with getting 
images to export to pdf. I've also attached the resulting .tex file.

I think my issue may have something to do with my misunderstanding of 
inline tasks, since if I put my org code for inclusion of the image 
elsewhere in the org file, under its own 2nd level heading (2 stars) 
then it exports fine. The narrative text in the attached org file 
explains my observations in more detail.

Thanks.

--Chris Ryan

Nick Dokos wrote:
> suvayu ali<fatkasuvayu+linux@gmail.com>  wrote:
>
>> On Mon, Mar 19, 2012 at 20:53, Nick Dokos<nicholas.dokos@hp.com>  wrote:
>>>> [[./DataLoggerImage.jpg]]
>>>>
>>>> The figure does not appear in the resulting pdf.  Any advice as to what
>>>> I am doing wrong?
>>>>
>>>
>>> Can you post your org file and the tex file that's produced on export?
>>>
>>
>> Is the above correct syntax? Shouldn't it be as shown below?
>>
>> [[file:./DataLoggerImage.jpg]]
>>
>
> I had the same reaction at first, but I tried it and the pdf export went
> through without a hitch in either case. I'm not sure whether that's intended
> behavior or an accident though.
>
> Nick
>
>

[-- Attachment #2: WhereIsImage.org --]
[-- Type: text/plain, Size: 1148 bytes --]

#+OPTIONS:   todo:nil toc:nil tags:nil
#+LATEX_HEADER: \usepackage[margin=1in]{geometry}
#+LATEX_HEADER: \usepackage{graphicx}


* I guess I don't understand enough about Org's hierarchical trees yet

** Study design

Here's what we'll do.

As patients of home care agencies, the subjects will all be considered homebound by definition. Subjects with cognitive impairment or psychiatric illness sufficiently severe to make them unable to consent to the study will not be eligible.
****** TODO notice how "end" on next line is expandable
****** END
Somehow this text is under, hierarchically-speaking, the END statement of this inline task.

So it does not show up in the final pdf

****** TODO there is text >>and the image file<< inside "end"
****** END

Neither does this paragraph.

Neither does this image, which must also be under the END statement of the inline task

#+CAPTION: Temperature and humidity data logger
#+LABEL:   datalogger
[[./DataLoggerImage.jpg]]

** But if I start a new 2-star heading

and put the image here, it works fine.

#+CAPTION: Temperature and humidity data logger
#+LABEL:   datalogger
[[./DataLoggerImage.jpg]]


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: WhereIsImage.tex --]
[-- Type: text/x-tex; name="WhereIsImage.tex", Size: 1253 bytes --]

% Created 2012-03-20 Tue 00:04
\documentclass[11pt]{article}
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{fixltx2e}
\usepackage{graphicx}
\usepackage{longtable}
\usepackage{float}
\usepackage{wrapfig}
\usepackage{soul}
\usepackage{textcomp}
\usepackage{marvosym}
\usepackage{wasysym}
\usepackage{latexsym}
\usepackage{amssymb}
\usepackage{hyperref}
\tolerance=1000
\usepackage[margin=1in]{geometry}
\usepackage{graphicx}
\providecommand{\alert}[1]{\textbf{#1}}

\title{WhereIsImage}
\author{Chris Ryan}
\date{\today}

\begin{document}

\maketitle



\section{I guess I don't understand enough about Org's hierarchical trees yet}
\label{sec-1}
\subsection{Study design}
\label{sec-1-1}


Here's what we'll do.

As patients of home care agencies, the subjects will all be considered homebound by definition. Subjects with cognitive impairment or psychiatric illness sufficiently severe to make them unable to consent to the study will not be eligible.
\subsection{But if I start a new 2-star heading}
\label{sec-1-2}


and put the image here, it works fine.

\begin{figure}[htb]
\centering
\includegraphics[width=10em]{./DataLoggerImage.jpg}
\caption{\label{datalogger}Temperature and humidity data logger}
\end{figure}

\end{document}

Re: how to include graphics in pdf output

[Nick Dokos]

Christopher W. Ryan <cryan@binghamton.edu> wrote:

> I've attached a small org file that reproduces my problem with getting
> images to export to pdf. I've also attached the resulting .tex file.
> 
> I think my issue may have something to do with my misunderstanding of
> inline tasks, since if I put my org code for inclusion of the image
> elsewhere in the org file, under its own 2nd level heading (2 stars)
> then it exports fine. The narrative text in the attached org file
> explains my observations in more detail.
> 

> #+OPTIONS:   todo:nil toc:nil tags:nil
> #+LATEX_HEADER: \usepackage[margin=1in]{geometry}
> #+LATEX_HEADER: \usepackage{graphicx}
> 
> 
> * I guess I don't understand enough about Org's hierarchical trees yet
> 
> ** Study design
> 
> Here's what we'll do.
> 
> As patients of home care agencies, the subjects will all be considered homebound by definition. Subjects with cognitive impairment or psychiatric illness sufficiently severe to make them unable to consent to the study will not be eligible.
> ****** TODO notice how "end" on next line is expandable
> ****** END
> Somehow this text is under, hierarchically-speaking, the END statement of this inline task.
> 
> So it does not show up in the final pdf
> 
> ****** TODO there is text >>and the image file<< inside "end"
> ****** END
> 
> Neither does this paragraph.
> 
> Neither does this image, which must also be under the END statement of the inline task
> 
> #+CAPTION: Temperature and humidity data logger
> #+LABEL:   datalogger
> [[./DataLoggerImage.jpg]]
> 
> ** But if I start a new 2-star heading
> 
> and put the image here, it works fine.
> 
> #+CAPTION: Temperature and humidity data logger
> #+LABEL:   datalogger
> [[./DataLoggerImage.jpg]]
> 

What is the value of org-inlinetask-min-level? If it's the default 15,
then you just haven't formatted the inline tasks correctly (not enough
stars)- did you use C-c C-x t to insert them?  I used that to
insert the inline tasks and I got the following org file which exports
correctly afaict:

--8<---------------cut here---------------start------------->8---
#+OPTIONS:   todo:nil toc:nil tags:nil
#+LATEX_HEADER: \usepackage[margin=1in]{geometry}
#+LATEX_HEADER: \usepackage{graphicx}


* I guess I don't understand enough about Org's hierarchical trees yet

** Study design

Here's what we'll do.

As patients of home care agencies, the subjects will all be considered homebound by definition. Subjects with cognitive impairment or psychiatric illness sufficiently severe to make them unable to consent to the study will not be eligible.
*************** TODO notice how "end" on next line is expandable 
*************** END
Somehow this text is under, hierarchically-speaking, the END statement of this inline task.

So it does not show up in the final pdf

*************** TODO there is text >>and the image file<< inside "end" 
*************** END
Neither does this paragraph.

Neither does this image, which must also be under the END statement of the inline task

#+CAPTION: foo
#+LABEL:   foo
[[./DataLoggerImage.jpg]]

** But if I start a new 2-star heading

and put the image here, it works fine.

#+CAPTION: bar
#+LABEL:   bar
[[./DataLoggerImage.jpg]]
--8<---------------cut here---------------end--------------->8---

Nick

Re: how to include graphics in pdf output

[Christopher W. Ryan]

Nick Dokos wrote:
> Christopher W. Ryan<cryan@binghamton.edu>  wrote:
>
>> I've attached a small org file that reproduces my problem with getting
>> images to export to pdf. I've also attached the resulting .tex file.
>>
>> I think my issue may have something to do with my misunderstanding of
>> inline tasks, since if I put my org code for inclusion of the image
>> elsewhere in the org file, under its own 2nd level heading (2 stars)
>> then it exports fine. The narrative text in the attached org file
>> explains my observations in more detail.
>>
>
>> #+OPTIONS:   todo:nil toc:nil tags:nil
>> #+LATEX_HEADER: \usepackage[margin=1in]{geometry}
>> #+LATEX_HEADER: \usepackage{graphicx}
>>
>>
>> * I guess I don't understand enough about Org's hierarchical trees yet
>>
>> ** Study design
>>
>> Here's what we'll do.
>>
>> As patients of home care agencies, the subjects will all be considered homebound by definition. Subjects with cognitive impairment or psychiatric illness sufficiently severe to make them unable to consent to the study will not be eligible.
>> ****** TODO notice how "end" on next line is expandable
>> ****** END
>> Somehow this text is under, hierarchically-speaking, the END statement of this inline task.
>>
>> So it does not show up in the final pdf
>>
>> ****** TODO there is text>>and the image file<<  inside "end"
>> ****** END
>>
>> Neither does this paragraph.
>>
>> Neither does this image, which must also be under the END statement of the inline task
>>
>> #+CAPTION: Temperature and humidity data logger
>> #+LABEL:   datalogger
>> [[./DataLoggerImage.jpg]]
>>
>> ** But if I start a new 2-star heading
>>
>> and put the image here, it works fine.
>>
>> #+CAPTION: Temperature and humidity data logger
>> #+LABEL:   datalogger
>> [[./DataLoggerImage.jpg]]
>>
>
> What is the value of org-inlinetask-min-level? If it's the default 15,
> then you just haven't formatted the inline tasks correctly (not enough
> stars)- did you use C-c C-x t to insert them?  I used that to
> insert the inline tasks and I got the following org file which exports
> correctly afaict:
>
> --8<---------------cut here---------------start------------->8---
> #+OPTIONS:   todo:nil toc:nil tags:nil
> #+LATEX_HEADER: \usepackage[margin=1in]{geometry}
> #+LATEX_HEADER: \usepackage{graphicx}
>
>
> * I guess I don't understand enough about Org's hierarchical trees yet
>
> ** Study design
>
> Here's what we'll do.
>
> As patients of home care agencies, the subjects will all be considered homebound by definition. Subjects with cognitive impairment or psychiatric illness sufficiently severe to make them unable to consent to the study will not be eligible.
> *************** TODO notice how "end" on next line is expandable
> *************** END
> Somehow this text is under, hierarchically-speaking, the END statement of this inline task.
>
> So it does not show up in the final pdf
>
> *************** TODO there is text>>and the image file<<  inside "end"
> *************** END
> Neither does this paragraph.
>
> Neither does this image, which must also be under the END statement of the inline task
>
> #+CAPTION: foo
> #+LABEL:   foo
> [[./DataLoggerImage.jpg]]
>
> ** But if I start a new 2-star heading
>
> and put the image here, it works fine.
>
> #+CAPTION: bar
> #+LABEL:   bar
> [[./DataLoggerImage.jpg]]
> --8<---------------cut here---------------end--------------->8---
>
> Nick


Well, I'm making some progress.

org-inlinetask-min-level = 15

I had previousl simply typed in an arbitrary number of stars by hand, 
for my inline tasks. If I use C-c C-x t to insert one, then figures and 
text subsequent to it do appear in the final pdf as desired.  If I type 
in 15 stars by hand, emacs recognizes this also as an inline task 
(judging by the syntax highlighting) and figures following it are again 
exported correctly.

However, in both cases, the inline tasks themselves also appear in the 
final pdf. I was trying to avoid that, and I though todo:nil in 
#+OPTIONS would accomplish that objective, but it did not.  Is there a 
way to not export inline tasks?

Here are the modifications to the small reproducible file I started with:

#+OPTIONS:   todo:nil toc:nil tags:nil
#+LATEX_HEADER: \usepackage[margin=1in]{geometry}
#+LATEX_HEADER: \usepackage{graphicx}


* I guess I don't understand enough about Org's hierarchical trees yet

** Study design

Here's what we'll do.

Blah blah blah

*************** TODO I'd like this not to appear in pdf
*************** END
So now this text here appears in the pdf, as desired. But I'd like the 
inline task above not to appear in the pdf. I though todo:nil would 
prevent it from appearing, but it did not.


*************** TODO figure will follow this todo
*************** END
This line appears in the pdf too. Unfortunately, so does the inline task 
above it.

And the image shows up; its first appearance.


#+CAPTION: foo
#+LABEL:   foo
[[./DataLoggerImage.jpg]]

** But if I start a new 2-star heading

and put the image here, it works fine.  Second appearance of the image.

#+CAPTION: bar
#+LABEL:   bar
[[./DataLoggerImage.jpg]]


*************** TODO entered via C-c C-x t
*************** END

************** TODO just 14 stars typed by hand, and a figure after
                this should be the third figure in the pdf
                figure doesn't appear, nor does this text
************** END

#+CAPTION: bar
#+LABEL:   bar
[[./DataLoggerImage.jpg]]



Thanks.
--Chris

Re: how to include graphics in pdf output

[Sebastien Vauban]

Hi Christopher,

"Christopher W. Ryan" wrote:
> However, in both cases, the inline tasks themselves also appear in the 
> final pdf. I was trying to avoid that, and I though todo:nil in 
> #+OPTIONS would accomplish that objective, but it did not.  Is there a 
> way to not export inline tasks?
>
> Here are the modifications to the small reproducible file I started with:
>
> #+OPTIONS:   todo:nil toc:nil tags:nil
> #+LATEX_HEADER: \usepackage[margin=1in]{geometry}
> #+LATEX_HEADER: \usepackage{graphicx}
>
>
> * I guess I don't understand enough about Org's hierarchical trees yet
>
> ** Study design
>
> Here's what we'll do.
>
> Blah blah blah
>
> *************** TODO I'd like this not to appear in pdf
> *************** END
> So now this text here appears in the pdf, as desired. But I'd like the 
> inline task above not to appear in the pdf. I though todo:nil would 
> prevent it from appearing, but it did not.

An inline task is almost a normal headline, hence you can put a tag such as
"noexport" on it, and have the inline task not exported.

Best regards,
  Seb

-- 
Sebastien Vauban

Re: how to include graphics in pdf output

[John Hendy]

On Wed, Mar 21, 2012 at 4:54 AM, Sebastien Vauban
<wxhgmqzgwmuf@spammotel.com> wrote:
> Hi Christopher,
>
> "Christopher W. Ryan" wrote:
>> However, in both cases, the inline tasks themselves also appear in the
>> final pdf. I was trying to avoid that, and I though todo:nil in
>> #+OPTIONS would accomplish that objective, but it did not.  Is there a
>> way to not export inline tasks?
>>
>> Here are the modifications to the small reproducible file I started with:
>>
>> #+OPTIONS:   todo:nil toc:nil tags:nil
>> #+LATEX_HEADER: \usepackage[margin=1in]{geometry}
>> #+LATEX_HEADER: \usepackage{graphicx}
>>
>>
>> * I guess I don't understand enough about Org's hierarchical trees yet
>>
>> ** Study design
>>
>> Here's what we'll do.
>>
>> Blah blah blah
>>
>> *************** TODO I'd like this not to appear in pdf
>> *************** END
>> So now this text here appears in the pdf, as desired. But I'd like the
>> inline task above not to appear in the pdf. I though todo:nil would
>> prevent it from appearing, but it did not.
>
> An inline task is almost a normal headline, hence you can put a tag such as
> "noexport" on it, and have the inline task not exported.

Also,

,----- M-x help RET v RET org-inlinetask-export -----
| org-inlinetask-export is a variable defined in `org-inlinetask.el'.
| Its value is t
|
| Documentation:
| Non-nil means export inline tasks.
| When nil, they will not be exported.
|
| You can customize this variable.
`-----

Best regards,
John


>
> Best regards,
>  Seb
>
> --
> Sebastien Vauban
>
>

Re: how to include graphics in pdf output

[Christopher W. Ryan]

John Hendy wrote:
> On Wed, Mar 21, 2012 at 4:54 AM, Sebastien Vauban
> <wxhgmqzgwmuf@spammotel.com> wrote:
>> Hi Christopher,
>>
>> "Christopher W. Ryan" wrote:
>>> However, in both cases, the inline tasks themselves also appear in the
>>> final pdf. I was trying to avoid that, and I though todo:nil in
>>> #+OPTIONS would accomplish that objective, but it did not.  Is there a
>>> way to not export inline tasks?
>>>
.....
.....


>> An inline task is almost a normal headline, hence you can put a tag such as
>> "noexport" on it, and have the inline task not exported.
> 
> Also,
> 
> ,----- M-x help RET v RET org-inlinetask-export -----
> | org-inlinetask-export is a variable defined in `org-inlinetask.el'.
> | Its value is t
> |
> | Documentation:
> | Non-nil means export inline tasks.
> | When nil, they will not be exported.
> |
> | You can customize this variable.
> `-----
> 
> Best regards,
> John
> 
> 
>>
>> Best regards,
>>  Seb
>>
>> --
>> Sebastien Vauban
>>
>>
> 

Excellent! Thanks everyone.

--Chris

Christopher W. Ryan, MD
SUNY Upstate Medical University Clinical Campus at Binghamton
425 Robinson Street, Binghamton, NY  13904
cryanatbinghamtondotedu

"Observation is a more powerful force than you could possibly reckon.
The invisible, the overlooked, and the unobserved are the most in danger
of reaching the end of the spectrum. They lose the last of their light.
From there, anything can happen . . ."  [God, in "Joan of Arcadia,"
episode entitled, "The Uncertainty Principle."]