#857 Allow to set the newline character of the bib file

Next full release

When saving a bib file, JabRef appears to use the platform-dependent newline (EOL) character, i.e. \r\n on Windows an \n on Mac/Linux.

When sharing a bibtex database in a VCS repository among different operating systems (which is very appealing because JabRef is OS independent, and everything is stored inside the bib file), this is inconvenient because the diffs are completely useless (diff says that every single line has changed).

I suggest to either:

  • stick to a fixed EOL handling which is used on every OS, or
  • add an option to use a user-defined EOL character, overriding the OS default one.


  • Oliver Kopp

    Oliver Kopp - 2014-03-21
    • status: open --> pending
    • assigned_to: Oliver Kopp
  • Oliver Kopp

    Oliver Kopp - 2014-03-21

    JabRef's architecture doesn't allow for a per-database setting. I quickly added the feature to configure it globally at Options>Preferences>File>"Newline separator". Will be available in the next release.

  • Michael Helmling

    Thank you for addressing this request so quickly! :)

    So the strategy "guess EOL mode when reading the file and keep it that way" is not possible as well, I assume?

  • Oliver Kopp

    Oliver Kopp - 2014-03-21

    Sorry, that strategy is currently not possible. It would cost approx. 20 hours to implement that. Too many side effects have to be considered.

  • Michael Helmling

    Okay, I was just curious. A global option should be sufficient in most of the cases!

  • Jan-Philip Gehrcke


    this feature is super critical for many cross-platform work flows. It is implemented, but still not released. Can we please have a release with it? Would be quite awesome! ;)


  • fdar

    fdar - 2015-07-23
    • Labels: --> tocategorize
  • fdar

    fdar - 2015-08-06
    • labels: tocategorize --> EntryRecord, Sharing
    • status: pending --> open

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

Sign up for the SourceForge newsletter:

No, thanks