Backslashes with latex

[andrewthad]

If we have the following as example_in.markdown:

Description
===========

This is Drew's custom line with a \thingslashchar in it.

And then we run this:

pandoc -s example_in.markdown -o example_out.tex

We get a latex document as example_out.tex. Here is the relevant section:

... 
\begin{document}

\section{Description}\label{description}

This is Drew's custom line with a \thingslashchar in it.

\end{document}
...

This latex is invalid. It seems like the backslash should be escaped in the latex output. In my actual use case, this is causing problems when people put in windows paths. My solution so far has just been to require wrapping them in backticks.

[jgm]

Pandoc passes through things that look like LaTeX
commands. You can either backslash-escape the backslash
(i.e. \\thingslashchar) or disable the raw latex pass-through
extension:

pandoc -f markdown-raw_tex -t latex

+++ Andrew Martin [Mar 15 16 08:35 ]:

If we have the following as example_in.markdown:

Description

This is Drew's custom line with a \thingslashchar in it.

And then we run this:
pandoc -s example_in.markdown -o example_out.tex

We get a latex document as example_out.tex. Here is the relevant
section:
...
\begin{document}

\section{Description}\label{description}

This is Drew's custom line with a \thingslashchar in it.

\end{document}
...

This latex is invalid. It seems like the backslash should be escaped in
the latex output. In my actual use case, this is causing problems when
people put in windows paths. My solution so far has just been to
require wrapping them in backticks.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
[1]#2790

References

1. Backslashes with latex #2790

[andrewthad]

Thanks. That resolves my issue.

[jdhao]

I have also met this issue #4200. But in my case, the error message is not undefined command but utf-8 related issue, which is rather misleading.

After properly dealing with backslash issues, the error message disappeared and I can compile the markdown file successfully to pdf now.