Graphical Java application for managing BibTeX and biblatex (.bib) databases
MIT License
Bot releases are visible (Hide)
-j CITATIONKEY
. koppor#540
[camelN]
. Equivalent to the first N words of the [camel]
pattern.langid
which is important for hyphenation and casing in LaTeX. #10868
DOICheck
, if activated forum#4084
Cites
are now on the left and Cited by
on the right #10572
aux
file can now also be generated if some citations are not found library. #10775
cites
and related
relationships, as well as all fields from the CFF specification. #10993
file
-field. #11083
@electronic
and @online
entry types to the Office XMl would duplicate the field title
#10807
CommentsTab
was not properly formatted when the defaultOwner
contained capital or special letters. #10870
File -> Close library
menu item was not disabled when no library was open. #10948
[authIniN]
. #11087
Published by github-actions[bot] 10 months ago
Published by github-actions[bot] 12 months ago
[@key1,@key2]
) when pushing to external applications. #10133
biblatex
mode, the integrity check for journal titles now also checks the field journal
.listrefs
, tablerefs
, tablerefsabsbib
, now use the ISO date format in the footer #10383.file
, url
, ...). #10419
comment
for notes (instead of `review). #10478
.pkg
for the first installation as it updates all necessary files for the extension #10308
misc
for certain ISBN numbers #10348
journaltitle
is now also respected for showing the journal information. #10397
Published by github-actions[bot] about 1 year ago
$\backslash$
in file paths (as exported by Mendeley). forum#3470
note
field and moves it to the url
and urldate
field respectively. koppor#216
Journal
and ISSN
fields in the entry editor. #6189
Add Group
dialog to use the most recently selected group hierarchical context. #9141
logs
or backups
.log.txt
now contains an entry if a BibTeX entry could not be parsed.log.txt
now contains debug messages. Debugging needs to be enabled explicitly. #9678
log.txt
does not contain entries for non-found files during PDF indexing. #9678
COMPUTERNAME
/HOSTNAME
) first. #9910
revised
. #9536
.sav
file upon successful write. #9675
[authIniN]
: JabRef uses +
to indicate an overflow. Example: [authIni2]
produces A+
(instead of AB
) for Aachen and Berlin and Chemnitz
. #9703
remove_unicode_ligatures
is now called replace_unicode_ligatures
. #9890
--exportMatches
flag does not create an output bib file. #9581
\
, the combination \}
was treated as plain }
. #9668
[authors]
, [authshort]
, [authorsAlpha]
, [authIniN]
, [authEtAl]
, [auth.etal]
to handle and others
properly. koppor#626
[edtrN_M]
returned the wrong editor. #9946
Published by github-actions[bot] almost 2 years ago
JABREF_
prefix, and in PGSQL we moved tables in jabref
schema. We added VersionDBStructure
variable in METADATA
table to indicate current version of structure, this variable is needed for automatic migration. #9312
.deb
file now works on plain debian again. #9472
Published by calixtus almost 2 years ago
fjournal
(in @article
) for abbreviation and unabbreviation functionalities. #321
comment
of the corresponding entry #9025
.bak
and temporary writing files now .sav
..bib
file in the user data dir (instead of a single .sav
(now: .bak
) file in the directory of the .bib
file).bib
file.study.yml
. JabRef just ignores this data. #9124
<
characters.Published by calixtus about 2 years ago
$home/.cache/jabref/logs/version
, Windows: %APPDATA%\..\Local\harawata\jabref\version\logs
, Mac: Users/.../Library/Logs/jabref/version
Legislation
, Legadminmaterial
, Jurisdiction
, Constitution
and Legal
#8931
file
field.% Encoding: UTF-8
header, it is kept during writing (and not removed). #8964
Published by calixtus over 2 years ago
$
(by adding a backslash in front). #8673
crossref
field. #7378
file
field in the entry editor. #8659
pages
field would cause an exception and preventing the citation style to display. #8381, citeproc-java
XSL_FO
, ASCIIDOC
, and RTF
as these have not been working since a long time and are no longer supported in the external library used for processing the styles. #7378
Published by Siedlerchr almost 3 years ago
#
chars. By default String resolving is only activated for a couple of standard fields. The list of fields can be modified in the preferences. #7010, #7102, #8303
#
chars in certain fields would be interpreted as BibTeX strings #7010, #7102, #8303
Published by Siedlerchr almost 3 years ago
.bib
file ("library") was saved successfully, a notification is shown-importToOpen
instead of passing the bibtex via -importBibtex
. #7374, JabRef Browser Ext #274
File
to Import and Export
. #7935
UTF8
, the % Encoding
marker is not written anymore.bib
file has the same line endings #390
.bib
file always has a final line break.bib
file keeps the newline separator of the loaded .bib
fileLibrary > Preamble
, Library > Citation key pattern
and Library > String constants dialogs
#8264
log4j2
to tinylog
#8007
Aux file
on Edit group
doesn't support relative sub-directories path to import. #7719.NegativeArraySizeException
should not occur #8231 #8265
Published by koppor over 3 years ago
Inventor
if the bibtex entry type is patent
#7830
label
to the corresponding bibtex field endnote-label
forum#2734
timestamp
is migrated to creationdate
. In case one configured "udpate timestampe", it is migrated to modificationdate
. koppor#130
MonthAcessed
instead of the two digit number #7354
python3
interpreter via the shebang to dynamically use the systems default Python. Related to JabRef-Browser-Extension #177
Month
instead of the two digit number forum#2685
school
or institution
would be printed twice in the HTML Export forum#2634
file
fields could not be handled on Windows. #7359
urldate
was not exported to the corresponding fields YearAccessed
, MonthAccessed
, DayAccessed
in MS Office XML #7354
.bib
files #7265
report
in EndNote was imported as article
forum#2734
publisher
in EndNote was not imported in JabRef forum#2734
Published by koppor almost 4 years ago
bibtexkey
as citationkey
which was started in JabRef 5.1..sav
file was not deleted upon exiting JabRef. #6109
Published by koppor about 4 years ago
v1
) in the eprint
field. forum#1941
.sav
file without changes, there is no dialog asking for acceptance of changes anymore.-
) was reported as illegal BibTeX key #6295
abstract
and comment
were declared as multiline fields. Other fields can now be configured in the preferences using "Do not wrap the following fields when saving" 4373
default
was at the end of the layout section #6303
\textbackslash
appeared at the end of the abstract.External programs / Open PDF
section in the preferences, as the default application to open PDFs is now set in the Manage external file types
dialog. #6130
.bib.bak
file should be generated upon save. It is now always enabled. Documentation at https://docs.jabref.org/general/autosave. #6092
Published by koppor over 4 years ago
In the User Survey 2015, the user interface was ranked as one of the most important aspects where JabRef needed improvement.
We’ve heard your feedback and are excited to announce that JabRef 5.0 brings in the long-overdue user interface update.
We worked closely together with user interface experts to create an intuitive environment for your literature references.
The result is a completely redesigned UI, with a wealth of new features and functionalities that make your work easier and more effective. Of course, we wanted the new UI to focus on individual user customization, so you can make your JabRef truly your own and more convient to your workflow. For example, JabRef now offers a dark theme and we layed the foundation to support custom themes in future.
We didn't stop at reworking the user interface, but also introduced a couple of new features:
And many more! In total, there are over 100 changes since our last offical release!
With the release of the 5.0 we switched to a new build system which bundles the Java runtime together with JabRef.
This means that problems with other installed or outdated Java versions on the system are a problem of the past.
For the installation we now offer self-containing .deb
and .rpm
files for Linux users in addtion to the usual installer for Windows.
We also offer a portable zip version of JabRef which also includes all necessary files to run JabRef.
No installed Java version required.
You can get it from FOSShub.
Please report any other issues that you encounter in our bug tracker (in case it was not already reported before).
Since Jabref 5.0 is a major release, you should be aware that not all features are fully compatible with older version of JabRef. We worked hard to migrate all existing features to the new version. The only currently known issue is the "global search": The search bar doesn't remember the search string accross all tabs. We also have some performance issues with large databases, but are working on it.
Remember that JabRef 4.0 changed the groups format. See http://blog.jabref.org/#october-04-2017-%E2%80%93-jabref-4-0 for details.
The JabRef Developers would like to give special thanks to all new and old contributors. Since 4.0 we are very happy to see so many new contributors opening pull requests and making translations.
Special thanks goes to two temporary contributors who have significantly contributed to this release. You rock!
We also want to thank all universities including JabRef in their academic teaching.
Finally, we want to thank all the users who are constantly testing the latest snapshots and giving feedback!
Published by tobiasdiez almost 5 years ago
We are proud to announce the release of the first beta of JabRef 5.0 just in time for Christmas! 🚀 🎄
Since the alpha release of Jabref 5.0 we continued fixing bugs and addressed many usability issues.
In total, more than 40 major bugs have been fixed so that JabRef is now more stable and performs better than the previously released alpha.
As usually, the Changelog contains a detailed list of all changes.
Our Linux users will surely be happy that we finally offer deb and rpm packages as well as a portable edition, and that we now completly support the X11 primary selection (typically used by the middle mouse key).
After feedback on the new integrated preview next to the entry editor on the alpha version, we added an an option to show the preview as an extra tab in the entry editor (instead of in a split view).
One major feature of the upcoming 5.0 release is the "Dark Theme" which has been improved since the alpha 5.0. The "Dark Theme" can be enabled in the preferences under the tab "Appearance".
We also would like to thank all of our various contributors, translators, testers and donors! This helps us a lot!
With the release of the 5.0-beta we switched to a new native Java build system which allows us to bundle a custom Java runtime together with JabRef.
This means that problems with other installed or outdated java versions on the system are a problem of the past. This also means it's no longer possible to start JabRef directly from the jar.
For the installation we now offer self-containing .deb
and .rpm
files for Linux users and in addtion to the usual installer for Windows.
We also offer a portable zip version of JabRef which also includes all necessary files to run JabRef.
No installed Java version required.
Currently the following major issues are known:
Please report any other issues that you encounter in our bug tracker (in case it was not already reported before).
You can get it from FOSShub.
Published by koppor about 5 years ago
It's finally here 🎉 🙌 ❤️. After over a year of work, we proudly present the first alpha version of JabRef 5.0.
Thanks to our annual developer meetup JabCon, we were able to finally push things forward and put together the first release.
The UI of JabRef is now entirely transformed to JavaFX. Apart from that, we could include a lot of new great features. Especially, due to our Google Summer of Code student @davidemdot, we have a new feature to display where your references are used inside your LaTeX files.
We are looking forward to your thoughts on the next major version of JabRef! Note that this release is an alpha version, which means that the respective features are by no means finalized. Parts of the interface will be reworked to improve the usability.
! IMPORTANT !: This release requires JAVA 11! For Windows it's already included in the installer. For Linux and mac you probably need to install it.
If you want to reward our efforts and support us, we greatly appreciate any donations that e.g. enable us to meet in person and make such great things happen. See https://donations.jabref.org for more info on how to foster our work.
Published by stefan-kolb over 6 years ago
Bugfix release.
An overview of all new features and fixes can be found as usual in the changelog at GitHub.
Published by stefan-kolb over 6 years ago
We are proud to release JabRef 4.3!
Unfortunately, JabRef binaries are still not digitally signed any more.
However, we will release a signed version shortly.
Read our blog to know the reasons.
In the meantime, please check the installations instructions for your Operating System (especially macOs), in case JabRef cannot be started.
An overview of all new features and fixes can be found as usual in the changelog at GitHub.
Published by stefan-kolb over 6 years ago
We are proud to release JabRef 4.2!
This version fixes a lot of bugs of version 4.1.
Unfortunately, JabRef binaries are still not digitally signed any more.
However, we will release a signed version shortly.
Read our blog to know the reasons.
In the meantime, please check the installations instructions for your Operating System (especially macOs), in case JabRef cannot be started.
An overview of all new features and fixes can be found as usual in the changelog at GitHub.
Published by LinusDietz almost 7 years ago
After more than two months of hard work, we are proud to release JabRef 4.1!
Since then we primarily focused on performance and memory issues, but were also able to add new features.
Furthermore, the release also attracted some new contributors from the community and we are proud to see 12 new contributors since the last release.
We are thankful for that and enjoy seeing the JabRef community growing!
Unfortunately, JabRef binaries are not digitally signed any more.
We are working in a fix, but this will take some weeks to months.
Read our blog to know the reasons.
In the meantime, please check the installations instructions for your Operating System (especially MacOs), in case JabRef cannot be started.
We wish all JabRef users Happy Holidays and a Happy New Year!
An overview of all new features and fixes can be found as usual in the changelog at GitHub.