#1173 Inconsistent empty line in the database file

next release

In the current JabRef 2.10b, when I add an entry via the builtin Google Scholar search, it is saved in a continuous block without empty lines, like e.g.

  Title                    = {Fingerprint pore extraction based on Marker controlled Watershed Segmentation},
  Author                   = {Malathi, S and Maheswari, S Uma and Meena, C},
  Booktitle                = {Computer and Automation Engineering (ICCAE), 2010 The 2nd International Conference on},
  Year                     = {2010},
  Organization             = {IEEE},
  Pages                    = {337--340},
  Volume                   = {3},
  File                     = {:Pores\\Malathi Maheswari Meena 2010 - Fingerprint pore extraction based on Marker controlled Watershed Segmentation.pdf:PDF},
  Url                      = {http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=5451426}

However, when I continue editing, saving and loading the file, under some circumstances (I have not found out yet) an empty line gets introduced between the "Volume" and "File" lines.
This is annoying, because we are version controlling the file with Git and it causes unnecessary noise when looking at the diffs.

So either the empty line should never be generated, or always.


  • Oliver Kopp

    Oliver Kopp - 2015-05-20

    This is related to bug #1260

  • Oliver Kopp

    Oliver Kopp - 2015-05-20

    This is the new feature of JabRef 2.10. See Changelog.

    • Changed serialization of BibTeX entries:
      • First, the required, then the optional and then all other fields are written.
        Thereby, fields are now ordered by name. Except the title, which is written first.
      • The second word in of the BibTeX type is capitalized. E.g., Inproceedings got InProceedings
      • Configurable: Start field contents in same column. Enabled by default.
      • Configurable: Use camel case for field names (e.g., "HowPublished" instead of "howpublished"). Enabled by default.
      • If no field name is given, then "UNKNOWN" is used. For instance, " = {X}" gets " UNKNOWN = {X}".

    In version 2.11 beta 2, we offer a quick hack to go back to the old 2.9.2 behavior, which is somehow incomplete. See https://github.com/JabRef/jabref/pull/10#issuecomment-43582135

  • Robert Pollak

    Robert Pollak - 2015-05-21

    The bug is not the additional line in the new 2.10 format. The bug is that adding an entry via the builtin Google Scholar search does not directly create the correct format.


Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.

No, thanks