From: Robert Goldman <rpgoldman@sift.info>
To: nicholas.dokos@hp.com
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: Having problem with latex export of image file
Date: Tue, 15 Mar 2011 08:48:47 -0500 [thread overview]
Message-ID: <4D7F6E3F.6030709@sift.info> (raw)
In-Reply-To: <4306.1300165488@alphaville.dokosmarshall.org>
X-TagToolbar-Keys: D20110315084847273
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
On 3/15/11 Mar 15 -12:04 AM, Nick Dokos wrote:
> Robert Goldman <rpgoldman@sift.info> wrote:
>
>> I have the following in my org file:
>>
>> #+CAPTION: Sample (partial) plan graph.
>> #+LABEL: fig:sampleGraph
>> #+ATTR_LaTeX: width=.9\textwidth
>> [[plan-with-tc-start.pdf]]
>>
>> which I believe should give me a figure. However, when I run this
>> through the latex export I get the following instead:
>>
>> \hyperref[plan-with-tc-start.pdf]{plan-with-tc-start.pdf}
>>
>> I pushed "pdf" onto image-file-name-extensions but that doesn't seem to
>> make any difference.
>>
>> I figure there's something simple I'm doing wrong, but I can't figure
>> out what that is.
>>
>> Thanks for any advice!
>>
>
> Try
>
> [[./plan-with-tc-start.pdf]]
Thanks. That did fix it. Question: what's the rule about file names
here? Is it that there must be a non-empty directory part? Or
something else?
A second question: is there any way to set image file extensions /on a
per-file basis/? It seems to me, for example, to be quite likely that
in some files PDF should be treated as images (since I use pdflatex, pdf
seems like the best choice for images), whereas in others maybe not...
But it seems like image-file-name-extensions is not something that is
expected to be buffer-local....
best,
r
next prev parent reply other threads:[~2011-03-15 13:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-15 3:48 Having problem with latex export of image file Robert Goldman
2011-03-15 5:04 ` Nick Dokos
2011-03-15 13:48 ` Robert Goldman [this message]
2011-03-15 14:39 ` Nick Dokos
2011-03-15 15:30 ` Nick Dokos
2011-03-17 9:35 ` Bastien
2011-03-19 21:58 ` Robert Goldman
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=4D7F6E3F.6030709@sift.info \
--to=rpgoldman@sift.info \
--cc=emacs-orgmode@gnu.org \
--cc=nicholas.dokos@hp.com \
/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).