-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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 JSON author fields with style tags is mishandled #7603
Comments
Clarified title to indicate that style tags ( |
Not a bug: if you want a rendered bibliography in markdown, use |
See jgm/citeproc#63 for the root issue. |
I would think that normally you'd want to handle this sort of thing in the style, rather than by encoding the boldface in the bibliography itself. |
in CSL, |
Regarding the root issue, I am able to use a luascript to replace e.g. |
Manual states that HTML markup tags including
<b>
(bold),<i>
(italic) and a few others may be used in BiBTeX and CSL items: https://pandoc.org/MANUAL.html#specifying-bibliographic-data . This is concordant with CSL specification.However, pandoc mishandles this in at least two different ways, AFAICT.
Problem 1.
When going from CSLJSON -> (Whatever), HTML tags are escaped causing them to appear in the literal output stream.
Example:
Command:
pandoc --citeproc -s -f csljson csl_min.json -o csl.md
When rendering to, say, PDF, the literal
<b>
is inlined because of the escape character which you can see in the Markdown output, above.(Side-note on a separate bug: when the output target is markdown, the standalone,
nocite *
bibliography isn't actually rendered, only the metadata header. In any other target format (PDF, HTML, etc.) the bibliography is rendered.)Problem 2.
If one were to say, edit the markdown to remove the escape characters, pandoc STILL strips out the HTML tag when rendering.
$ sed -e "s/\\\</\</g;" csl.md
The rendered PDF still does not bold the author name.
Thanks in advance for taking a look at this, and thanks as always for Pandoc
The text was updated successfully, but these errors were encountered: