Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Generated Key contains 'null' when (corporate) author contains several special words after curly braces #6459

Closed
1 task done
rolandog opened this issue May 10, 2020 · 6 comments · Fixed by #6479
Closed
1 task done
Labels
bug Confirmed bugs or reports that are very likely to be bugs keygenerator

Comments

@rolandog
Copy link

JabRef version JabRef 5.0--2020-03-06--2e6f433 on Ubuntu 19.10

  • I have tested the latest development version from http://builds.jabref.org/master/ and the problem persists (JabRef 5.1--2020-05-08--40f908f on Ubuntu 19.10).

Steps to reproduce the behavior:

  1. Add the attached reference to a database
  2. Check database integrity
  3. Get notified of difference ("BibTex key deviates from generated key")
  4. Go to mentioned key, click "generate key"
  5. The key will now be "nullL2019".

Sample Bibliography

@Online{TSoL2019,
  author    = {{The School of Life}},
  editor    = {Abbot, Jack},
  date      = {2019-10-08},
  title     = {What Is The Secret Of Happiness?},
  url       = {https://youtu.be/sBSwJ6HOBG4},
  urldate   = {2019-11-05},
}
Log File

No events were generated in the event log, even though I followed procedure according to the docs, and I ran both the .deb and Portable versions (the latter I ran with the following options: ./JabRef --console --debug).

This was the output on the terminal:

ERROR StatusLogger Unrecognized format specifier [d]
ERROR StatusLogger Unrecognized conversion specifier [d] starting at position 16 in conversion pattern.
ERROR StatusLogger Unrecognized format specifier [thread]
ERROR StatusLogger Unrecognized conversion specifier [thread] starting at position 25 in conversion pattern.
ERROR StatusLogger Unrecognized format specifier [level]
ERROR StatusLogger Unrecognized conversion specifier [level] starting at position 35 in conversion pattern.
ERROR StatusLogger Unrecognized format specifier [logger]
ERROR StatusLogger Unrecognized conversion specifier [logger] starting at position 47 in conversion pattern.
ERROR StatusLogger Unrecognized format specifier [msg]
ERROR StatusLogger Unrecognized conversion specifier [msg] starting at position 54 in conversion pattern.
ERROR StatusLogger Unrecognized format specifier [n]
ERROR StatusLogger Unrecognized conversion specifier [n] starting at position 56 in conversion pattern.
ERROR StatusLogger Unrecognized format specifier [d]
ERROR StatusLogger Unrecognized conversion specifier [d] starting at position 16 in conversion pattern.
ERROR StatusLogger Unrecognized format specifier [thread]
ERROR StatusLogger Unrecognized conversion specifier [thread] starting at position 25 in conversion pattern.
ERROR StatusLogger Unrecognized format specifier [level]
ERROR StatusLogger Unrecognized conversion specifier [level] starting at position 35 in conversion pattern.
ERROR StatusLogger Unrecognized format specifier [logger]
ERROR StatusLogger Unrecognized conversion specifier [logger] starting at position 47 in conversion pattern.
ERROR StatusLogger Unrecognized format specifier [msg]
ERROR StatusLogger Unrecognized conversion specifier [msg] starting at position 54 in conversion pattern.
ERROR StatusLogger Unrecognized format specifier [n]
ERROR StatusLogger Unrecognized conversion specifier [n] starting at position 56 in conversion pattern.

(java:20862): Gdk-WARNING **: 18:01:46.992: XSetErrorHandler() called with a GDK error trap pushed. Don't do that.
@Siedlerchr
Copy link
Member

Thanks for your report. It would be helpful if you could tell us which key pattern you have defined for the entry type or if you are using the default pattern

@Siedlerchr Siedlerchr added status: waiting-for-feedback The submitter or other users need to provide more information about the issue keygenerator labels May 10, 2020
@rolandog
Copy link
Author

Hi @Siedlerchr ! Thanks for your reply!

I don't think I have modified the defaults;

Screenshot from 2020-05-10 22-43-20

If I click on the 'reset' button on the entry, a value of [auth][year] appears, instead of a blank value... but the behaviour is the same: the entry's generated key still contains null.

This may or may not be helpful, but I noticed that most of the "corporate" authors are not displayed properly; here's a screenshot on how the column is displayed for the author {Commission on Isotopic Abundances and Atomic Weights}:

Screenshot from 2020-05-10 22-50-44

I don't think I have any odd settings on the 'Entry Table' settings:

Screenshot from 2020-05-10 22-48-02

Just to be on the safe side, I reset all my preferences, restarted JabRef, modified the entry's key, re-generated it and got the same results; also the same problem was present with the format of the corporate author's name in the author's column.

Screenshot from 2020-05-10 23-01-51

Tomorrow morning I'll try uninstalling, removing configuration files, and see if there are any different results.

@Siedlerchr Siedlerchr added bug Confirmed bugs or reports that are very likely to be bugs and removed status: waiting-for-feedback The submitter or other users need to provide more information about the issue labels May 10, 2020
@Siedlerchr
Copy link
Member

Thanks for your feedback! Resetting preferences was enough as clarification. Looks really like a bug,

@k3KAW8Pnf7mkmdSMPHz27
Copy link
Sponsor Member

I can take a look at this?

@Siedlerchr
Copy link
Member

@k3KAW8Pnf7mkmdSMPHz27 Sure go ahead

@tobiasdiez
Copy link
Member

Thanks to @k3KAW8Pnf7mkmdSMPHz27 this should be fixed in the latest development version. Could you please check the build from http://builds.jabref.org/master/. Thanks! Please remember to make a backup of your library before trying-out this version.

koppor pushed a commit that referenced this issue Apr 1, 2023
41531558a8 Fix unsigned newspaper articles throughout Chicago 17 (#6486)
7678212826 Create trames.csl (#6479)
0cae26ac85 Update hochschule-fur-soziale-arbeit-fhnw.csl (#6480)
85c4b693a2 Update to UP Harvard Theology & Religion (#6485)
c273aa7e43 Update ieee.csl (#6481)
fe67b80e47 Update open-window.csl (#6367)
f2229705ef Create iainutuban-tarbiyah.csl (#6361)
1867a56a26 Create business-and-human-rights-journal (#6359)
1371dbdf26 Update iso690-author-date-es.csl (#6477)
6953a43efd Update ieee.csl (#6478)
f56d5ef1cc Create czech-journal-of-international-relations.csl (#6453)
678b53f99c Update harvard-stellenbosch-university.csl (#6464)
3074938038 Update ucl-university-college-apa.csl (#6475)
27dab9ea0f Update iso690-author-date-es.csl (#6476)
a8aea63d00 Create elsevier-american-chemical-society.csl (#6342)
f8f290fa63 Update iso690-author-date-es.csl (#6472)
7fdc621eee Update journal-of-neolithic-archaeology (#6466)
7025568e70 Update offa.csl (#6465)
2d69299b19 Create uni-fribourg-theologie.csl (#6473)
8db531a73e Create travail-et-emploi.csl (#6351)
c8b54fc531 Make monash-university-harvard dependent style (#6470)
b95f59ff5c Update journal-of-the-marine-biological-association-of-the-united-kingdom.csl (#6456)
a12b513119 Update universite-du-quebec-a-montreal.csl (#6463)
048e6641e4 Update zeitschrift-fur-geschichtsdidaktik.csl (#6454)
f0d3d7ef15 Update journal-fur-kulturpflanzen-journal-of-cultivated-plants.csl (#6447)
3b814fe048 Update the-accounting-review.csl (#6459)
f24befd580 Update survey-of-ophthalmology.csl from ama.csl to its own independent style (#6460)
c868ab54f6 Create vancouver-alphabetical.csl (#6461)
782e39cfe1 Update american-institute-of-physics.csl (#6457)
a56cf03e3c Fix Chicago Cases & Newspaper sorting (#6458)

git-subtree-dir: buildres/csl/csl-styles
git-subtree-split: 41531558a873b2533f2d17d8d6484c2408174fce
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Confirmed bugs or reports that are very likely to be bugs keygenerator
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

4 participants