-
Notifications
You must be signed in to change notification settings - Fork 11
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
Add blog post on changes of our .bib serialization #47
Draft
koppor
wants to merge
6
commits into
main
Choose a base branch
from
add-bibtex-file-changes-over-time
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2 tasks
Just found following in the comments /**
* Get display version of an entry field.
* <p>
* BibTeX is case-insensitive therefore there is no difference between: howpublished, HOWPUBLISHED, HowPublished, etc.
* <p>
* There was a long discussion about how JabRef should write the fields. See https://github.com/JabRef/jabref/issues/116
* <p>
* The team decided to do the biblatex way and use lower case for the field names.
*
* @param field The name of the field.
* @return The display version of the field name.
*/ |
ThiloteE
reviewed
Apr 27, 2022
See also links at JabRef/jabref-koppor#75. |
|
3 tasks
|
2 tasks
Large input at JabRef/jabref#10590 (comment) |
Related work: Bibliography prettyprinting and syntax checking |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This blog post reviews the history of JabRef 2.0 to now (JabRef 5.0) writing the bibtex file.
The rendered version can be easily browsed at
https://github.com/JabRef/blog.jabref.org/blob/add-bibtex-file-changes-over-time/_posts/2020-08-20-bibtex-file-changes-over-time.md.