-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pandoc-crossref not working #33
Comments
By comparison, when using plain pandoc from command line pandoc -F pandoc-crossref test.md -o test.tex the latex output is correct \includegraphics[width=0.1\textwidth,height=\textheight]{some_image.png} as is the generated pdf when setting |
I got another hint from my experiments: Adding |
Hey there! Forgive my delay in responding. I've been mercifully, but inconveniently, a little unplugged from GitHub lately. My gut suspicion is that the root of your issue lies in Pandown's CriticMarkup support, which is a super unsophisticated bundle of regex copypasta I grabbed from their repos and don't fully understand myself. CriticMarkup processing is (or ought to be) disabled by default, though, so I'm going to take a deeper look tonight. In the meantime, there's a setting called {
"preprocess_critic": false
} It should be at the first level of your settings JSON, rather than nested in It'd also be a big help in reproducing the bug if you could drop any applicable config files in this thread or in a gist. Thanks for being so patient! |
I am really thankful for all your advice (also the direct response via e-mail)! I will give an overview of what I did to solve everything shortly. |
I have an issue using pandoc-crossref (http://lierdakil.github.io/pandoc-crossref/) as a filter. It can be added using
"filter": "pandoc-crossref"
or"filter": ["pandoc-crossref"]
in the pandoc-config.json. However, there seems to be some preprocessing that escapes some of the crossref syntax. A simple example would be using an image in Markdown with crossref-specific options:which includes the image but escapes the curly braces, so crossref cannot interpret them any more as parameters. This is visible when doing latex output, where the output is as follows:
I suspect something with citations to get in the way, because the documentation warns about the order of applying citeproc and crossref (first crossref, then citeproc). I do not understand the pandown codebase yet, otherwise I would open a pull request.
The text was updated successfully, but these errors were encountered: