-
Notifications
You must be signed in to change notification settings - Fork 524
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
CSL handing indent does not seem to be working #290
Comments
The |
I think this is from the pandoc default latex template This is for pandoc-citeproc to work when a
This has been in Pandoc only since 2.8 and later, so it won't work by default in RStudio IDE has it comes with pandoc 2.7.3. You need to install a more recent version. We will assume this is the issue you encountered. If even after upgrading, you still have the issue, please reopen. |
This old thread has been automatically locked. If you think you have found something related to this, please open a new issue by following the issue guide (https://yihui.org/issue/), and link to this old issue if necessary. |
A number of rticles formats seem to provide support for hanging indent of CSL/pandoc-citeproc formatted references, but either I do not understand how it is supposed to be used or it is not working as intended. For example, the
plos_article
format includes the following code intemplate.tex
:Given this code, I would expect that adding to the YAML header:
would cause the references to be formatted with a handing indent. However, this does not seem to work because the references are not sandwiched in the appropriate environment in the TeX output:
Am I not understanding how this is supposed to be used or is this not implemented appropriately?
Thanks and I apologize if I am misunderstanding something.
By filing an issue to this repo, I promise that
xfun::session_info('rticles')
. I have upgraded all my packages to their latest versions (e.g., R, RStudio, and R packages), and also tried the development version:remotes::install_github('rstudio/rticles')
.I understand that my issue may be closed if I don't fulfill my promises.
The text was updated successfully, but these errors were encountered: