emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: emacs-org list <emacs-orgmode@gnu.org>
Subject: Re: Right way to add special processing to images?
Date: Thu, 12 Jan 2017 20:59:24 +0100	[thread overview]
Message-ID: <87a8awaw2r.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAFyQvY2XSrN4K2VauKNUndGSX_kR7TPAm1E3h58wZFEWg=aSnA@mail.gmail.com> (Kaushal Modi's message of "Thu, 12 Jan 2017 16:53:38 +0000")

Hello,

Kaushal Modi <kaushal.modi@gmail.com> writes:

> I have this elisp function that I run in org-export-before-processing-hook
> that coverts a pdf to png where that png file is already linked in the org
> file. Just that the png file did not exist to begin with; it is converted
> from pdf at the time of exporting. [Code is at the end of this email.]
>
> But for that you work, need to add my special keyword "convertfrompdf t"
> and I chose "#+HEADER" just before the image link to do that.
>

[...]

> So the question is: Is using #+HEADER for this a good idea? Would the org
> devs just a better way to do the same? I basically need to be able to
> control per image link if that linked image foo.png needs to be converted
> from a foo.pdf.

I would simply use a comment with some specific pattern instead of
messing with Org syntax.

For example, I use the following comments

  # © Author "title" licence

just before image links so as to mark them, collect them and build some
special page at the end of a slide with the information.


Regards,

-- 
Nicolas Goaziou

next prev parent reply	other threads:[~2017-01-12 19:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-12 16:53 Right way to add special processing to images? Kaushal Modi
2017-01-12 19:59 ` Nicolas Goaziou [this message]
2017-01-12 20:08   ` Kaushal Modi

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=87a8awaw2r.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=kaushal.modi@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

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).