Re: Pandoc unable to access remote shares on Windows?

[John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>]

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.