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
This issue can be closed with a PR to the source branch that fixes the _config.yml configuration file (if it is at fault, which I suspect it is) so that this warning no longer occurs. OR, an investigation that identifies the root of the warning as system-related (is this caused by me not running the most recent version or compatible versions of ruby or Jekyll?).
The text was updated successfully, but these errors were encountered:
What does use_raw_bibtex_entry: true do for the site?
I found this:
if you want to use {{ ... }} in your BibTeX files (to force uppercase titles for example), then you have to tell Jekyll-Scholar not to interpret this as Liquid templates. This is achieved by putting in your _config.yml file:
on a blog. Is this feature something that should remain, or can we change true to false?
So changing it to false still yields the errors; however, I made the line concerning use_raw_bibtex_entry a comment on my local version and I compared how the bibtex entries on the publications page rendered (paying attention to the brackets and months, which a couple of the github issues mention as not rendering correctly) and I wasn't able to find a difference in the local version.
The double curly braces help to make sure proper nouns remain capitalized as they are in the bibtex. For example {{PhD}} in the bibtex file is never corrected to Phd, PyNE is never corrected to Pyne.
This repository's issues are reserved for feature requests, and bug reports, and questions.
I'm submitting a ...
Expected Behavior
When I build and push the website, I begin in the source branch and use a Rakefile to automate the building and pushing, like so:
I expect that there will be neither errors nor warnings when I do this.
Actual Behavior
I get this warning:
Steps to Reproduce the Problem
Specifications
Version:
Platform:
How can this issue be closed?
This issue can be closed with a PR to the source branch that fixes the _config.yml configuration file (if it is at fault, which I suspect it is) so that this warning no longer occurs. OR, an investigation that identifies the root of the warning as system-related (is this caused by me not running the most recent version or compatible versions of ruby or Jekyll?).
The text was updated successfully, but these errors were encountered: