Skip to content
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

Markdown: bracketed multi-reference citations require semicolon separator #110

Closed
dhimmel opened this issue Apr 7, 2017 · 2 comments
Closed

Comments

@dhimmel
Copy link

dhimmel commented Apr 7, 2017

I'm using pandoc and pandoc-citeproc to automatically generate references and build the bibliography from markdown source. We encountered an issue where multiple references inside brackets do not render properly if they're space-only separated.

For example, the markdown source of [@ref_1 @ref_2 @ref_3] will result in an inline reference of [1] with a bibliography that includes records for 1, 2, & 3.

Everything works if we add a semicolon separator [@ref_1; @ref_2; @ref_3]. This syntax results in the proper inline reference of [1-3].

So not sure if this is the intended behavior (that semicolons are required). However, the behavior of only showing one inline reference but putting all references in the bibliography is odd.

From a simplicity and consistency standpoint, it would be nice to be able to omit these semicolons (assuming that won't break existing functionality).

@lierdakil
Copy link
Owner

Um. Did you mean to file this under https://github.com/jgm/pandoc-citeproc ? Anyway...

FWIW, [@ref_1 @ref_2 @ref_3] is treated as @ref_1 with suffix @ref_2 @ref_3 by Pandoc.
If your csl silently drops reference suffixes, it's not Pandoc's fault.

And yes, semicolons are required as a separator, since reference keys can be surrounded by arbitrary Markdown.

@dhimmel
Copy link
Author

dhimmel commented Apr 7, 2017

Did you mean to file this under jgm/pandoc-citeproc?

@lierdakil indeed. Oops.

Anyways thanks for answering my question. I didn't know about the suffix functionality.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants