Hello,
I have two issues.
Consider the following contents of a .bib file:
% Encoding: UTF-8
@Article{abcdef,
author = {F1 L1 and F2 L2},
year = {1999},
title = {Silent storage venues require pension},
journal = {Famous journal},
volume = {123},
pages = {1--100},
number = {1},
publisher = {The Publisher},
}
@Comment{jabref-meta: databaseType:bibtex;}
@Comment{jabref-meta: saveOrderConfig:specified;author;false;year;false;title;false;}
On Linux (JabRef 3.8.2 linux 5.15.0-53-generic amd64 Java 11.0.17), opening this file and generating the bibkey with keypattern being
[authorsAlpha:lower][shortyear][title:abbr][journal:abbr][volume][number][firstpage][lastpage]
generates key : ff99SsvrpFj12311100
Although the above version information in Linux seems rather old, I installed this by using the jabref_5.7_amd64.deb package available at JabRef download latest version
Repeating the same exercise on Windows Jabref (JabRef 5.7–2022-08-05–73c111c Windows 10 10.0 amd64 Java 18.0.2 JavaFX 18.0.1+2)
generates key : ff99SSVRPFj12311100
(note different capitalization on abbreviation of article title.) This is causing my main latex document to not cite this article.
Furthermore, on saving this in Windows, I obtain the following ordering of entries in the .bib file: author, journal, number, pages, title, volume, year and publisher.
Note the difference in this saved order between Linux and Windows. This is causing me issues in git version control where unnecessarily, the same entry is flagged as having changed when in reality it has not – the file has just been saved differently by Linux and Windows Jabref.
Is there a way to fix both these issues so that Linux Jabref and Windows Jabref perform identically?
Thank you.