-
Notifications
You must be signed in to change notification settings - Fork 1
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
Special characters in bib-file encoded incorrectly #2
Comments
So, the "good news" is that this actually is working. The only problem is the Removing that, the document process with or without |
Ah, I see - I thought it was because latex wouldn't recognize the rendered characters, but it's the other way around. I remember having to add the This is an automatically output bib file from paperpile, which gets updated when I add new docs, so I was hoping I wouldn't have to manually remove the |
It must be possible to get the desired work flow. Ideally, one would prevent pandoc from processing the LaTeX here, leaving it to be processed in the resulting |
This seems to be at the
|
@apragsdale -- The following change to the
|
I've been struggling with this for a little while now - my bib file has special characters (say author names with accents or umlauts, etc), which are encoded in the .bib file as follows, for example:
These are usually handled by setting
\usepackage[T1]{fontenc}
in the preamble.However, these get converted to rich text in the bib entries in the auto-generated tex file, and latex fails with Undefined control sequence when it encounters those non-ascii encoded characters in the bib entries.
I can't figure out how to enforce Rmarkdown to not convert characters to rich text. In Rstudio, I've tried Tools -> General options -> Code -> Saving and then setting Default text encoding to ASCII, but did not seem to change the behavior. Any ideas?
The text was updated successfully, but these errors were encountered: