Save/save as: file type shows BIBTEX_DB

[tobiasdiez]

JabRef version

5.7 (latest release)

Operating system

GNU / Linux

Details on version and operating system

No response

Checked with the latest development build

• I made a backup of my libraries before testing the latest development version.
• I have tested the latest development version and the problem persists

Steps to reproduce the behaviour

1. Save a new file or use "save as" for an existing bib file
2. The dialog shows then in the file type selector "BIBTEX_DB file". Instead it should show something like "Library (.bib file)"

Appendix

...

Log File

Paste an excerpt of your log file here

[ThiloteE]

There is File > save library as ... > BIBTEX_DB file (*.bib)
There is also File > Export > Save selected as plain BibTeX... > BIBTEX_DB file (*.bib).

I propose to rename to BibTeX/BibLaTeX (*.bib) because this would be similar to how we show other file formats under

• File > Export > Export all entries > ...
• File > Export > Export selected entries > ...
• File > Import > Import into current library > ...
• File > Import > Import into new library > ...

As added bonus, it would spread the knowledge about BibLaTeX, which I think is a good thing because BibTeX is a little outdated and we not only support BibTeX, but also BibLaTeX.

Furthermore, I would propose to rename File > Export > Save selected as plain BibTeX... to File > Export > Save selected as plain BibTeX/BibLaTeX library file. Maybe remove the "plain"? Is there a difference between saving as BibTeX and exporting as BibTeX? Does exporting "plainly" remove some JabRef specific data from the file?

[ThiloteE]

Removing good first issue, because we are still discussing

[tobiasdiez]

Personally, I would strive to make JabRef's UI as independent as possible from the fact that we use Bib(La)TeX under the hood. JabRef's whole point is to abstract away the boring bibtex related things, so why should we remind people that they are still using it? This becomes especially relevant once we have our word addin running, which then hopefully attracts people that have never heard of bibtex before. After using Zotero and Mendeley for a bit, I really don't see anything that they do better then us - so I would like to position JabRef as "a wholesome reference manager that even works well with bibtex" over our current "a niche bibtex manager that is only useful for latex nerds".

So I would always use "Library file" over "BibTeX/BibLaTeX file". It is also shorter, which is nice for the menu.

[ThiloteE]

so you propose to rename RIS (*.ris) also to library file (*.ris)?

[Siedlerchr]

I agree with Thilo. And plain bibtex is bibtex without jabref metdata etc. Mods and RIS etc are also completely different formats. So we should use bibtex as it's the format.

[koppor]

I always position JabRef as tool for BibTeX. Some pro users hesitate to use JabRef if JabRef seems to move away from BibTeX.

Maybe, we need to offer two modes: Entry mode (which is a general mode avoiding BibTeX) and professional mode (which has more "BibTeX" in the UI and is more clear in BibTeX terms).

Maybe, it's "just" a new localization for the UI?

Maybe we should have a strategic call discussing the general direction.

[tobiasdiez]

so you propose to rename RIS (*.ris) also to library file (*.ris)?

If we would use RIS as our main file format, yes. But its a nice Gedankenexperiment: would we put RIS everywhere in our UI if we would use it as our main file format?

[koppor]

My current vote is "BibTeX file" or "BibTeX library file". In all cases, not "DB" and no capital letters.

Context as picture

Note: We have "BIB file" in the preferences:

I personally would like ".bib file", but ".bib file (*.bib)" reads strange at the save dialog.

[morganteg]

I'd like to work on this, please. I express my opinion, as well:
I'd prefer to have "BibTeX library (.bib)" or, in case of multiple supported extensions "BibTeXML (.bibx, .xml)".
This mainly because the user is quickly able to understand the file extension that is going to save. This should improve the UI usability.

[ThiloteE]

Thanks for your continued engagement morgantex :-) Great job with pr 9703

[koppor]

We don't support BibTeXML any more. There should be no leftovers in the code hopefully...

[morganteg]

We don't support BibTeXML any more. There should be no leftovers in the code hopefully...

I found it into the "main" branch. However, I used BibTeXML just as an example of Type with multiple extensions.

[calixtus]

devcall decision:
It should show the DisplayName of BIBTEX_DB consistently throughout the gui.

/src/main/java/org/jabref/logic/util/StandardFileType.java#L21

I think the main issue is in:

jabref/src/main/java/org/jabref/gui/util/FileFilterConverter.java

Lines 29 to 31 in 14c12b1

	public static FileChooser.ExtensionFilter toExtensionFilter(FileType fileType) {
	String description = Localization.lang("%0 file", fileType.toString());
	return new FileChooser.ExtensionFilter(description, fileType.getExtensionsWithAsteriskAndDot());