Pandoc unable to access remote shares on Windows?

Pandoc unable to access remote shares on Windows?

[Anton Shepelev]

Hello, all

Being loth to store non-source files in version con-
trol, I have decided to keep my  reference  document
in  a  Windows share. But Pandoc seems unable to ac-
cess the remote path. When I invoke it with

   --reference-doc=\\SRV3\\BinRes\Pandoc\style.docx

it terminates with the error:

   pandoc: \\SRV3\\BinRes\Pandoc\style.docx:
   openBinaryFile: does not exist (No such file or directory)

So I am forced to copy the style.docx locally in the
build batch file:

   copy \\SRV3\\BinRes\Pandoc\style.docx .

   pandoc -f markdown -t docx ^
    --reference-doc=style.docx -N ^
    intdb.md -o intdb.docx

   del style.docx

It  works,  but copying all remote resources locally
just to make them accessible to Pandoc is ugly.   Is
there  a better solution?  Why is it that `copy' can
access the remote path and Pandoc cannot?

-- 
Please, do not forward replies to the list to my e-mail.

Re: Pandoc unable to access remote shares on Windows?

[John MacFarlane]

Possibly relevant issue
https://github.com/jgm/pandoc/issues/5127
Try with forward slashes!

Anton Shepelev <anton.txt-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:

> Hello, all
>
> Being loth to store non-source files in version con-
> trol, I have decided to keep my  reference  document
> in  a  Windows share. But Pandoc seems unable to ac-
> cess the remote path. When I invoke it with
>
>    --reference-doc=\\SRV3\\BinRes\Pandoc\style.docx
>
> it terminates with the error:
>
>    pandoc: \\SRV3\\BinRes\Pandoc\style.docx:
>    openBinaryFile: does not exist (No such file or directory)
>
> So I am forced to copy the style.docx locally in the
> build batch file:
>
>    copy \\SRV3\\BinRes\Pandoc\style.docx .
>
>    pandoc -f markdown -t docx ^
>     --reference-doc=style.docx -N ^
>     intdb.md -o intdb.docx
>
>    del style.docx
>
> It  works,  but copying all remote resources locally
> just to make them accessible to Pandoc is ugly.   Is
> there  a better solution?  Why is it that `copy' can
> access the remote path and Pandoc cannot?
>
> -- 
> Please, do not forward replies to the list to my e-mail.
>
> -- 
> 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/20200811181415.89ccef3a90a15783ceb1c261%40gmail.com.

Re: Pandoc unable to access remote shares on Windows?

[Anton Shepelev]

John MacFarlane to Anton Shepelev:

> > But  Pandoc  seems  unable  to access the remote
> > path. When I invoke it with
> >
> >    --reference-doc=\\SRV3\BinRes\Pandoc\style.docx
> >
> > it terminates with the error:
> >
> >    pandoc: \\SRV3\BinRes\Pandoc\style.docx:
> >    openBinaryFile: does not exist (No such file or directory)
>
> Possibly relevant issue
> https://github.com/jgm/pandoc/issues/5127
> Try with forward slashes!

No, it not a relevant issue -- it is  the  self-same
issue.   Thanks for the reference.  I failed to make
it work with forward slashes,  but  the  "long"  UNC
format has helped:

   --reference-doc=\\?\UNC\SRV3\BinRes\Pandoc\style.docx

Whereas  it is very non-standard syntax for Windows,
it is worth  documenting  in  the  platform-specific
section of the manual. But supporting native Windows
syntax would be even better :-)

Re: Pandoc unable to access remote shares on Windows?

[John MacFarlane]

Anton Shepelev <anton.txt-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:

>> >    pandoc: \\SRV3\BinRes\Pandoc\style.docx:
>> >    openBinaryFile: does not exist (No such file or directory)
>>
>> Possibly relevant issue
>> https://github.com/jgm/pandoc/issues/5127
>> Try with forward slashes!
>
> No, it not a relevant issue -- it is  the  self-same
> issue.   Thanks for the reference.  I failed to make
> it work with forward slashes,  but  the  "long"  UNC
> format has helped:
>
>    --reference-doc=\\?\UNC\SRV3\BinRes\Pandoc\style.docx
>
> Whereas  it is very non-standard syntax for Windows,
> it is worth  documenting  in  the  platform-specific
> section of the manual. But supporting native Windows
> syntax would be even better :-)

I had thought we had resolved it in the linked issue.
Glancing at the discussion there, it looks like code
was added that normalizes \\SRV3... to \\?\UNC\SRV3...
In T.P.App.CommandLineOptions.

But I see that it isn't applied everywhere it should be.
In particular, not to --reference-doc.

I'll re-open the issue with a note.