Spaces in image filenames

Spaces in image filenames

[jmuc...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org]

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

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-discuss+unsubscribe-/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.

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

Re: Spaces in image filenames

[John MacFarlane]

What exactly do you mean when you say "generate errors"?

"jmuc...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org" <jmuccigr-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-discuss+unsubscribe-/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.

Re: Spaces in image filenames

[jmuc...-Re5JQEeQqe8AvxtiuMwx3w@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 --]

Re: Spaces in image filenames

[John MacFarlane]

Here's the root of the issue:

 % pandoc -t native
![moon](La Lune.jpg)
[ Para
    [ Image
        ( "" , [] , [] ) [ Str "moon" ] ( "La%20Lune.jpg" , "fig:" )
    ]
]

As you see, the markdown reader converts the space to %20 in the
image path.  This is fine for HTML but when pandoc tries to
create a PDF, it causes problems.  I need to explore further,
but I'm convinced that's it, because if you try `-f native`
with the above, it fails, but replacing %20 with a space,
it then succeeds.


"jmuc...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org" <jmuccigr-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:

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

Re: Spaces in image filenames

[jmuc...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org]

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

I can see that, but I'm not sure why giving the entire path removes the 
problem.

If it helps, I don't think this was a problem before (though I couldn't say 
for sure or which what version).

On Thursday, 6 January 2022 at 19:02:16 UTC-5 John MacFarlane wrote:

>
> Here's the root of the issue:
>
> % pandoc -t native
> ![moon](La Lune.jpg)
> [ Para
> [ Image
> ( "" , [] , [] ) [ Str "moon" ] ( "La%20Lune.jpg" , "fig:" )
> ]
> ]
>
> As you see, the markdown reader converts the space to %20 in the
> image path. This is fine for HTML but when pandoc tries to
> create a PDF, it causes problems. I need to explore further,
> but I'm convinced that's it, because if you try `-f native`
> with the above, it fails, but replacing %20 with a space,
> it then succeeds.
>
>
> "jmuc...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org" <jmuc...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>
> > 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-discus...-/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
> .
>

-- 
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/1c8dd209-5629-4681-a5c3-9d030d99a553n%40googlegroups.com.

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

Re: Spaces in image filenames

[John MacFarlane]

I don't know, actually.  This should be an issue on the tracker,
if there isn't one already.

"jmuc...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org" <jmuccigr-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:

> I can see that, but I'm not sure why giving the entire path removes the 
> problem.
>
> If it helps, I don't think this was a problem before (though I couldn't say 
> for sure or which what version).
>
> On Thursday, 6 January 2022 at 19:02:16 UTC-5 John MacFarlane wrote:
>
>>
>> Here's the root of the issue:
>>
>> % pandoc -t native
>> ![moon](La Lune.jpg)
>> [ Para
>> [ Image
>> ( "" , [] , [] ) [ Str "moon" ] ( "La%20Lune.jpg" , "fig:" )
>> ]
>> ]
>>
>> As you see, the markdown reader converts the space to %20 in the
>> image path. This is fine for HTML but when pandoc tries to
>> create a PDF, it causes problems. I need to explore further,
>> but I'm convinced that's it, because if you try `-f native`
>> with the above, it fails, but replacing %20 with a space,
>> it then succeeds.
>>
>>
>> "jmuc...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org" <jmuc...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>>
>> > 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-discus...-/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
>> .
>>
>
> -- 
> 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/1c8dd209-5629-4681-a5c3-9d030d99a553n%40googlegroups.com.

Re: Spaces in image filenames

[jmuc...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org]

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

Filed an issue on GitHub.

On Friday, 7 January 2022 at 15:00:52 UTC-5 John MacFarlane wrote:

>
> I don't know, actually. This should be an issue on the tracker,
> if there isn't one already.
>
> "jmuc...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org" <jmuc...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>
> > I can see that, but I'm not sure why giving the entire path removes the 
> > problem.
> >
> > If it helps, I don't think this was a problem before (though I couldn't 
> say 
> > for sure or which what version).
> >
> > On Thursday, 6 January 2022 at 19:02:16 UTC-5 John MacFarlane wrote:
> >
> >>
> >> Here's the root of the issue:
> >>
> >> % pandoc -t native
> >> ![moon](La Lune.jpg)
> >> [ Para
> >> [ Image
> >> ( "" , [] , [] ) [ Str "moon" ] ( "La%20Lune.jpg" , "fig:" )
> >> ]
> >> ]
> >>
> >> As you see, the markdown reader converts the space to %20 in the
> >> image path. This is fine for HTML but when pandoc tries to
> >> create a PDF, it causes problems. I need to explore further,
> >> but I'm convinced that's it, because if you try `-f native`
> >> with the above, it fails, but replacing %20 with a space,
> >> it then succeeds.
> >>
> >>
> >> "jmuc...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org" <jmuc...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> >>
> >> > 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-discus...-/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
> >> .
> >>
> >
> > -- 
> > 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/1c8dd209-5629-4681-a5c3-9d030d99a553n%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/1b058ce9-9019-471d-8470-8fe229dbc988n%40googlegroups.com.

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

Re: Spaces in image filenames

[jmuc...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org]

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

This is now working for me with v. 2.17. Thanks.

On Saturday, 8 January 2022 at 12:59:52 UTC-5 jmuc...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org wrote:

> Filed an issue on GitHub.
>
> On Friday, 7 January 2022 at 15:00:52 UTC-5 John MacFarlane wrote:
>
>>
>> I don't know, actually. This should be an issue on the tracker,
>> if there isn't one already.
>>
>> "jmuc...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org" <jmuc...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>>
>> > I can see that, but I'm not sure why giving the entire path removes the 
>> > problem.
>> >
>> > If it helps, I don't think this was a problem before (though I couldn't 
>> say 
>> > for sure or which what version).
>> >
>> > On Thursday, 6 January 2022 at 19:02:16 UTC-5 John MacFarlane wrote:
>> >
>> >>
>> >> Here's the root of the issue:
>> >>
>> >> % pandoc -t native
>> >> ![moon](La Lune.jpg)
>> >> [ Para
>> >> [ Image
>> >> ( "" , [] , [] ) [ Str "moon" ] ( "La%20Lune.jpg" , "fig:" )
>> >> ]
>> >> ]
>> >>
>> >> As you see, the markdown reader converts the space to %20 in the
>> >> image path. This is fine for HTML but when pandoc tries to
>> >> create a PDF, it causes problems. I need to explore further,
>> >> but I'm convinced that's it, because if you try `-f native`
>> >> with the above, it fails, but replacing %20 with a space,
>> >> it then succeeds.
>> >>
>> >>
>> >> "jmuc...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org" <jmuc...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>> >>
>> >> > 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-discus...-/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
>> >> .
>> >>
>> >
>> > -- 
>> > 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/1c8dd209-5629-4681-a5c3-9d030d99a553n%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/245e71f3-0afc-48d4-8d16-fcbe2e677e2bn%40googlegroups.com.

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