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

Add blog post on changes of our .bib serialization #47

Draft
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

koppor
Copy link
Member

@koppor koppor commented Aug 18, 2020

This blog post reviews the history of JabRef 2.0 to now (JabRef 5.0) writing the bibtex file.

  • What is currently missing is the layout of multiline fields. Maybe, this is not that important...

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.

@koppor koppor marked this pull request as draft August 18, 2020 22:13
@koppor
Copy link
Member Author

koppor commented Nov 22, 2021

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.
     */

@koppor
Copy link
Member Author

koppor commented Jun 13, 2022

See also links at JabRef/jabref-koppor#75.

@koppor koppor changed the base branch from gh-pages to main April 1, 2023 10:14
@koppor
Copy link
Member Author

koppor commented May 4, 2023

  • Information about group serialization should also be included here (refs No user info about changing bib-format in 4.0 jabref#3251).
  • While working on it, it should be checked if JabRef issues a warning about changing the semantic content of the bib file without any notice. If not, think about implementing it
  • Check if the blog post contains words about that we keep "old serialization" if the entry did not change

Refs JabRef/user-documentation#227

@koppor
Copy link
Member Author

koppor commented May 16, 2023

@koppor
Copy link
Member Author

koppor commented Nov 2, 2023

Large input at JabRef/jabref#10590 (comment)

@koppor
Copy link
Member Author

koppor commented Nov 8, 2023

Related work:

Bibliography prettyprinting and syntax checking
PDF [published in TUGboat 14(3) 222, October (1993) and 14(4) 395--419, December (1993)]

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

Successfully merging this pull request may close these issues.

2 participants