From: "jmuc...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org" <jmuccigr-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Spaces in image filenames
Date: Thu, 6 Jan 2022 15:32:21 -0800 (PST) [thread overview]
Message-ID: <e06ad7a4-019a-4ab7-8224-3b61ea32a07bn@googlegroups.com> (raw)
In-Reply-To: <yh480ktuegzceu.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 2170 bytes --]
Here's an example:
```
~/Pictures/ > pandoc -o Downloads/test.pdf -f markdown
![one](file name.jpg)
Error producing PDF.
! Package pdftex.def Error: File
`/private/var/folders/yl/xd3tsv2x1959s23ts4k1q
t9m0000gr/T/tex2pdf.-a4cc305331e7cf2c/file name.jpg' not found: using draft
set
ting.
See the pdftex.def package documentation for explanation.
Type H <return> for immediate help.
...
l.70 ...T/tex2pdf.-a4cc305331e7cf2c/file name.jpg}
```
If I use the full path to the file, it works fine.
On Thursday, 6 January 2022 at 18:13:33 UTC-5 John MacFarlane wrote:
>
> What exactly do you mean when you say "generate errors"?
>
> "jmuc...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org" <jmuc...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>
> > I feel like I'm missing something obvious, but I've just noticed the
> spaces
> > in image filenames generate errors unless they occur with a full path.
> For
> > example:
> >
> > This works:
> >
> > `![One image](/Users/username/Pictures/file name.jpg)`
> >
> > This doesn't:
> >
> > `![Another image](file name.jpg)`
> >
> > Nor does:
> >
> > `![A third image](./file name.jpg)`
> >
> > I've tried quoting the filename, too.
> >
> > The command I'm using is the following from the directory where the
> files
> > live:
> >
> > `pandoc -o test.pdf test.md -f markdown`
> >
> > --
> > 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-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> > To view this discussion on the web visit
> https://groups.google.com/d/msgid/pandoc-discuss/33416aa7-4f25-41a4-b216-763cd799a90fn%40googlegroups.com
> .
>
--
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/e06ad7a4-019a-4ab7-8224-3b61ea32a07bn%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 3507 bytes --]
next prev parent reply other threads:[~2022-01-06 23:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-06 16:42 jmuc...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
[not found] ` <33416aa7-4f25-41a4-b216-763cd799a90fn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-01-06 23:12 ` John MacFarlane
[not found] ` <yh480ktuegzceu.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2022-01-06 23:32 ` jmuc...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org [this message]
[not found] ` <e06ad7a4-019a-4ab7-8224-3b61ea32a07bn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-01-07 0:01 ` John MacFarlane
[not found] ` <yh480kfsq0za4u.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2022-01-07 0:31 ` jmuc...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
[not found] ` <1c8dd209-5629-4681-a5c3-9d030d99a553n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-01-07 20:00 ` John MacFarlane
[not found] ` <m2y23rb9jv.fsf-jF64zX8BO0+FqBokazbCQ6OPv3vYUT2dxr7GGTnW70NeoWH0uzbU5w@public.gmane.org>
2022-01-08 17:59 ` jmuc...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
[not found] ` <1b058ce9-9019-471d-8470-8fe229dbc988n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-01-15 19:29 ` jmuc...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
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=e06ad7a4-019a-4ab7-8224-3b61ea32a07bn@googlegroups.com \
--to=jmuccigr-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).