public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Stephen Eglen <stephen.eglen-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: graphicspath for finding images
Date: Thu, 30 Mar 2023 12:00:40 -0700 (PDT)	[thread overview]
Message-ID: <580a17da-f1d9-4340-8054-d9787a0410d3n@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1290 bytes --]

One thing I like about tex is that it allows you to set a search path (via 
\graphicspath{PATH1:PATH2}  or TEXINPUTS variable) to look for images if 
they cannot be found in the current directory.  

e.g. if I have some markdown like

![alt text](foo.png "title of image")

then if foo.png is not in the working directory, tex will go looking in the 
graphicspath to find it.  (It may rely on the kpsewhich tool which caches 
the location of files, I'm not sure.)

How best could I get a similar functionality when converting from markdown 
e.g. to html?

I'm partly being lazy as I prefer my source files to look tidy with just 
the filename, without the full path, as often the full path could be tucked 
away somewhere else on my home directory. 

Would this be where I woud look to using a pandoc filter to e.g. subsitute 
'foo.png' with the output from 'kpsewhich foo.png'?

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/580a17da-f1d9-4340-8054-d9787a0410d3n%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 1739 bytes --]

             reply	other threads:[~2023-03-30 19:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-30 19:00 Stephen Eglen [this message]
     [not found] ` <580a17da-f1d9-4340-8054-d9787a0410d3n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-03-30 19:22   ` John MacFarlane

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=580a17da-f1d9-4340-8054-d9787a0410d3n@googlegroups.com \
    --to=stephen.eglen-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    /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.
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 NNTP newsgroup(s).