You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm thinking the more sensible thing might be to have knitcitations write an external bibtex file, and convert its citations into pandoc's format instead, from whence you could then use pandoc (+ the CSL stylesheet) to process and format the references that kniticitations has generated.
would create the citation such as [@Boettiger2013], and bibliography("refs.bib") would generate the output bib file to be used in pandoc. Alternatively, references could be added as a yaml (note that the yaml metadata blocks can be anywhere in the document).
The text was updated successfully, but these errors were encountered:
I like this. Since discovering rmarkdown and it's render function it seems that there's a trend towards using pandoc, which would be consistent with your proposal. This would also allow for an easy workaround in the cases where DOI fails to find the correct reference.
I'm thinking the more sensible thing might be to have knitcitations write an external bibtex file, and convert its citations into pandoc's format instead, from whence you could then use pandoc (+ the CSL stylesheet) to process and format the references that kniticitations has generated.
In this case something like:
would create the citation such as
[@Boettiger2013]
, andbibliography("refs.bib")
would generate the output bib file to be used in pandoc. Alternatively, references could be added as a yaml (note that the yaml metadata blocks can be anywhere in the document).The text was updated successfully, but these errors were encountered: