From: Carsten Dominik <dominik@uva.nl>
To: Frank Chang <frank.nevermind@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [WISH] LaTeX Export: Expand link abbreviations first before exporting LaTeX links
Date: Sat, 5 Jul 2008 08:07:44 -0700 [thread overview]
Message-ID: <439CC308-A466-4B01-BE71-16F900F95B3E@uva.nl> (raw)
In-Reply-To: <loom.20080704T112208-568@post.gmane.org>
Fixed, thanks.
- Carsten
On Jul 4, 2008, at 4:25 AM, Frank Chang wrote:
> Hi, Carsten
>
> Thank you for fixing the tag problem in headline.
> It's really amazing that the problem can be fixed so quick (just few
> hours)!
>
> Now I have another problem:)
>
> Since I put all image files in one directory called, for example, ~/
> notes/img.
> And I want it to be a link abbreviation,
>
> #+LINK: image file:~/notes/img/
>
> so the image link will be easy to write:
>
> [[image:demo.jpg]]
>
> and also easy to maintain.
>
> But when I export the file, LaTeX exporter doesn't take it as a
> valid image link
> (\includegraphics[...]{~/notes/img/demo.jpg}).
>
> In function org-export-latex-links(), it seems that only the links
> beginning
> with 'file:' can be valid image links, and the link abbreviations
> are not
> replaced first.
>
> So is it possible to expand link abbreviations first before
> exporting LaTeX
> links (maybe apply the function org-link-expand-abbrev() in org.el)?
>
>
> Thanks.
>
>
> Best regards,
> Frank
>
>
>
>
> _______________________________________________
> 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
prev parent reply other threads:[~2008-07-05 15:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-04 11:25 [WISH] LaTeX Export: Expand link abbreviations first before exporting LaTeX links Frank Chang
2008-07-05 15:07 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=439CC308-A466-4B01-BE71-16F900F95B3E@uva.nl \
--to=dominik@uva.nl \
--cc=emacs-orgmode@gnu.org \
--cc=frank.nevermind@gmail.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 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.