Fix multi-line-fields in LF bibs on Windows

[koppor]

If the .bib file has LF endings, multiline fields will be written using CRLF on Windows. - Should we add the line feed property to the meta data? (And write out accordingly?)

Steps:

• create a bib file with LF line endings and a multi line field (e.g., comment)
• add this file to .gitattributes with eol=lf
• add a test case
• Fix Bibdatabase writer

---

• Refs Improve serialization to fix #4877 jabref#5838
• This will fix https://sourceforge.net/p/jabref/feature-requests/857/
• Keywords: newline, CRLF, CR, new line

[koppor]

I have a LF file on Windows, opened it in JabRef, added a comment and saved it. This is the result:

bibWithUserCommentsAndEntryChange.bib

[koppor]

Aspects:

• Read first 100 bytes to determine the new line character (and store it in memory of JabRef)
• Normalization takes place within the edited entry (this explains the CRLF in 1137631)
• Entries not touched are written as-is (with the existing line endings) this explains the LF in 1102917
• Header is written in OS specific line ending (this explains the CRLF in the first two lines)

[koppor]

Solution strategy:

• determine line ending of the file (or use preference line ending)
• normalize all entries during reading

[koppor]

Pay attention on the "file changed on disk" thing, because when changing the line endings the file on disk changes, too.

[koppor]

This issue also triggers the "External changes" dialog for multiline fields:

File on disk looks good:

[JoKalliauer]

I have a LF file on Windows, opened it in JabRef, added a comment and saved it. This is the result:

@koppor : Could you provide your settings of

• Options -> Preferences -> File -> Newline separator
• Options -> Preferences -> File -> Always reformat BIB file on save and export