markdown - How to avoid automatic appended file extensions to directory links when converting to pdf using pandoc? -

I am writing the company's internal documents in R. MarkDown and am compiling using Rostudio weaving. I am trying to add a link to point to a directory:

  [testdir] (file: //// c: / test /)  

(It's following the notification being described)

When I compile it in html, I get the following link.

  & lt; A href = "file: / /// C: / test /" & gt; Testdir & lt; / A & gt;  

And it works as expected in Internet Explorer. However, when I try to convert from RDDDO directly to PDF, an unwanted PDF extension is added to the link. I tried to disintegrate this problem and it seems that this change is happening within Pandok.

Code>

The link in the latex output file looks like this:

  \ href {file: /// c: / test}} {testdir}  

So far everything is good. However, when I convert latex output to pdf in pandoc,

  & gt; Pandoc -f latex -t latex-o test.pdf test.tex  

has been added on a .pdf extension link. Here is the copy / paste of the PDF link output:

/c:/test/.pdf

Is there a way to avoid this unwanted attachment?

Maybe I'm asking too much pandokas, but I thought it would be appropriate to ask RSTIDIO after writing such useful IDE to write my dynamic documents. As you said, the .exe file pandoc generated is okay.

Therefore, the problem really happens with latex, especially the hyperph package in which

had problems with two possible solutions. To prevent being hyperphrased and adding a file extension, try:

  [testdir] (file: /// c: / test /.)  

or use Context instead of latex:

  $ pandoc -t context-testing. MD-o test.tex & amp; Amp; Reference test.tex