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...@googlegroups.com.
> 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-/JYPxA39Uh5TLH3MbocFFw@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.