emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Arne <freyberger.arne@cox.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: Inline images in latex
Date: Tue, 23 Jun 2009 06:15:44 +0200	[thread overview]
Message-ID: <99B1B7A2-62F5-43E2-9A70-4B33C9AEB76B@gmail.com> (raw)
In-Reply-To: <loom.20090622T175250-63@post.gmane.org>


On Jun 22, 2009, at 8:38 PM, Arne wrote:

> Arne <freyberger.arne <at> cox.net> writes:
>>
>> I am not able to get the inline images including in the exported  
>> latex output.
>> The raw latex contains an \href{}{} instead of \includegraphics.  I  
>> have
>> verified that pdflatex is the latex to pdf process
>> and the the appropriate image
>> file extensions are in the org-export-latex-inline-image-extensions.
>
> Carsten,
> I've tracked it down to an underscore in the filename.  Almost all  
> my filenames
> have an underscore in them, a habit I should probably break.   The  
> first
> command works where as the second line results in an "href".
>
>  [[./data/linacE.jpg]]      # works, results in \includegraphics
>
>  [[./data/linac_energy.jpg]]   # does not work, results in \href
>
> The jpg files are identical.
>
> If this is easy to fix, that'd be great, otherwise I move to bumpy  
> names.

This was a bug, fixed now.  Thanks!

- Carsten

>
> Thanks for a great tool!
> Arne
>
>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

      reply	other threads:[~2009-06-23  4:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-21 19:39 Inline images in latex Arne
2009-06-22 18:38 ` Arne
2009-06-23  4:15   ` Carsten Dominik [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

  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=99B1B7A2-62F5-43E2-9A70-4B33C9AEB76B@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=freyberger.arne@cox.net \
    /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).