JabRef version
5.11 (latest release)
Operating system
macOS
Details on version and operating system
MacOS 13.6 (22G120)
Checked with the latest development build (copy version output from About dialog)
Steps to reproduce the behaviour
Casing of custom field names is inconsistent in several different ways as described below. I believe these inconsistencies may have been introduced with #9993, at least partly.
In the Details pane, casing does not respect the bibtex file in contrary to what is declared in this comment
- Create a new custom field in the
biblatex source tab
- Make the field name upper case, e.g.
Newfield
- Save, close and reopen file
- Observe that in the
Other fields tab the newfield field name is lowercased, as it is in the BibTeX file. In fact, lowercase has been enforced and saved into file!
- Observe that built-in BibTeX fields such as
Author or Title are always uppercase in the UI and always lowercase in the BibTeX file.
Now, there is a way to make custom fields appear uppercase, but
In the Details pane, built-in tabs such as Required fields or Optional fields only partially respect JabRef preferences
- Go to
Preferences > Entry types and choose the type of your test BibTeX entry, e.g. "Book"
- Create a custom field
Newfield (uppercase) within that entry type, also make one of the existing built-in fields such as Author lowercase
- Export preferences into an
xml file
- Quit and start JabRef anew
- In the
Details pane, observe that both Newfield and Author are uppercase, although one would expect author to become lowercase
- In the
xml file, observe that author is lowercase while Newfield is uppercase
- In the
xml file, observe that built-in field names are all lowercase, while Newfield is uppercase. Newfield becomes lowercase when done so through preferences.
- JabRef enforces the built-in field names to appear always uppercase in the UI and always lowercase in files, both
xml prefs and BibTeX bib sources.
In the Details pane, custom tabs do not respect anything, neither BibTeX source, nor preferences.
- Go to
Preferences > Entry Editor and create a custom tab such as Fields:author;newfield
- Observe that no matter what,
author always appears uppercase and newfield always appears lowercase.
Summary
Currently, it is not possible to have a consistent casing across the Details pane and a BibTeX file:
- Built-in field names are always lowercase
- Custom field names can be made both, but not in custom tabs
- Lowercase is enforced in
bib files
- Lowercase is almost exclusively enforced in
xml preferences file - only custom fields can be saved uppercase in jabref-entrytype fields, though not in customTabFields fields.
Appendix
The below screenshots should illustrate what is written above.
Preferences > Entry types

Required fields tab

Custom Fields tab

biblatex source tab

test.bib opened in another editor

JabRef version
5.11 (latest release)
Operating system
macOS
Details on version and operating system
MacOS 13.6 (22G120)
Checked with the latest development build (copy version output from About dialog)
Steps to reproduce the behaviour
Casing of custom field names is inconsistent in several different ways as described below. I believe these inconsistencies may have been introduced with #9993, at least partly.
In the
Detailspane, casing does not respect the bibtex file in contrary to what is declared in this commentbiblatex sourcetabNewfieldOther fieldstab thenewfieldfield name is lowercased, as it is in the BibTeX file. In fact, lowercase has been enforced and saved into file!AuthororTitleare always uppercase in the UI and always lowercase in the BibTeX file.Now, there is a way to make custom fields appear uppercase, but
In the
Details pane, built-in tabs such asRequired fieldsorOptional fieldsonly partially respect JabRef preferencesPreferences > Entry typesand choose the type of your test BibTeX entry, e.g. "Book"Newfield(uppercase) within that entry type, also make one of the existing built-in fields such asAuthorlowercasexmlfileDetails pane, observe that bothNewfieldandAuthorare uppercase, although one would expectauthorto become lowercasexmlfile, observe thatauthoris lowercase whileNewfieldis uppercasexmlfile, observe that built-in field names are all lowercase, whileNewfieldis uppercase.Newfieldbecomes lowercase when done so through preferences.xmlprefs and BibTeXbibsources.In the
Details pane, custom tabs do not respect anything, neither BibTeX source, nor preferences.Preferences > Entry Editorand create a custom tab such asFields:author;newfieldauthoralways appears uppercase andnewfieldalways appears lowercase.Summary
Currently, it is not possible to have a consistent casing across the Details pane and a BibTeX file:
bibfilesxmlpreferences file - only custom fields can be saved uppercase injabref-entrytypefields, though not incustomTabFieldsfields.Appendix
The below screenshots should illustrate what is written above.
Preferences > Entry typesRequired fieldstabCustom
Fieldstabbiblatex sourcetabtest.bibopened in another editor