When saving a reference with only one entry in the author field (e.g. a corporate author like {Google}) KBibTeX adds a comma at the end of the field expecting a second name. This eventually leads to an error when building the bibliography. These commas seem to be added at every save and need to be removed automatically afterward. Reproducible: Always Steps to Reproduce: 1. open *.bib file containing e.g.: @standard{IEC2005windTurbines, author = {IEC}} 2. save with KBibTex 3. the entry turned into: @standard{IEC2005windTurbines, author = {IEC,}} N.B.: this is not obvious when just looking at the source code in KBibTex, but the comma can be seen when opening the bib file in a text editor. Actual Results: The entry is changed to: @standard{IEC2005windTurbines, author = {IEC,}} Expected Results: The entry should be (without comma): @standard{IEC2005windTurbines, author = {IEC}}
I cannot reproduce this bug, so more information is required. To confirm how to reproduce it, your approach was as follows: 1. Start KBibTeX 2. Create a new, fresh file 3. Add a single entry as document above with an author field as its only content 4. Save as some .bib file When saving a bib file for the first time or when calling Save As, there is a dialog where you can control certain settings (lower/upper case keywords, etc). Which settings did you use? Can you reproduce your problem using the master version from Git? Can you reproduce your bug on another machine or with another or a fresh (temporary) user account?
Created attachment 88831 [details] erroneous bib file
Thanks for the quick reply! I've played with it a bit more, and actually you are right: it's not so easy to reproduce. I had a bib file from JabRef, that i opened with KBibTex. That's where i got the problems. If i start a new file i do not reproduce the error, either. Not with a new entry, and not if i copy the erroneous ones into the new file. Strange. Attached i send you an excerpt of my file, which produced the error. The extra comma appears in the last entry, BladedTheory2012. Interestingly, if I copy all my library into a new file it's working. There must have been something wired with that old file? Are there some hidden saving settings? But never mind . It's working now. And sorry for the confusion.
> I've played with it a bit more, and actually you are right: it's not so easy > to reproduce. > I had a bib file from JabRef, that i opened with KBibTex. That's where i got > the problems. If i start a new file i do not reproduce the error, either. > Not with a new entry, and not if i copy the erroneous ones into the new > file. Strange. So, there is a problem with files coming from JabRef. Can you please attach a file from JabRef that does cause problems in KBibTeX, but that was never saved in KBibTeX?
here you go. The comma will be added in the last entry (BladedTheory2012) once you save this in KBibTex. N.B.: the problem appears only with this file. I can't reproduce it even when generating a new file in JabRef and opening that in KBibTex.
Created attachment 88837 [details] erroneous bib file - never saved
Thomas, does comment #5, provide the requested information? Please change the bug status or add a comment.
(In reply to manuel from comment #5) > here you go. The comma will be added in the last entry (BladedTheory2012) > once you save this in KBibTex. > > N.B.: the problem appears only with this file. I can't reproduce it even > when generating a new file in JabRef and opening that in KBibTex. (In reply to Christoph Feck from comment #7) > Thomas, does comment #5, provide the requested information? Please change > the bug status or add a comment. Ok, I tried the attached .bib file. Before saving, the last entry looks like this: @Manual{BladedTheory2012, Title = {Bladed Theory Manual, Version 4.3}, Author = {Bladed}, Organization = {Garrad Hassan \& Partners Ltd.}, Year = {2012}, Institution = {Garrad Hassan \& Partners Ltd}, Owner = {mfluck}, Timestamp = {2013.10.08} } After saving: @manual{BladedTheory2012, author = {Bladed}, institution = {Garrad Hassan \& Partners Ltd}, organization = {Garrad Hassan \& Partners Ltd.}, owner = {mfluck}, timestamp = {2013.10.08}, title = {Bladed Theory Manual, Version 4.3}, year = {2012} } So, no problem here. The next possible reason I can see is a corrupted KBibTeX configuration file. manuel, you can test a few things: (a) Create a new account on your system, without any configuration files. Open and save the file to see if the problem can be still reproduced. (b) Move ~/.kde4/share/config/kbibtexrc to a safe location, open and save the file. (c) Show the output of grep personNameFormatting ~/.kde4/share/config/kbibtexrc
ok i have a) moved to a new account; problem still the same. b) Move ~/.kde4/share/config/kbibtexrc to a backup folder, opened and saved it. -> now ~/.kde4/share/config/kbibtexrc does not exist anymore; can't grep anything in it. c1) opened KBibTeX -> new ~/.kde4/share/config/kbibtexrc created. c2) grep personNameFormatting ~/.kde4/share/config/kbibtexrc finds no matches. (also no matches in the old file)
but don't worry too much. If it's only me having this problem i can also use JabRef, which is working just fine.
(In reply to manuel from comment #9) > ok i have > a) moved to a new account; problem still the same. > b) Move ~/.kde4/share/config/kbibtexrc to a backup folder, opened and saved > it. > -> now ~/.kde4/share/config/kbibtexrc does not exist anymore; can't grep > anything in it. > c1) opened KBibTeX -> new ~/.kde4/share/config/kbibtexrc created. > c2) grep personNameFormatting ~/.kde4/share/config/kbibtexrc finds no > matches. > (also no matches in the old file) Sorry, my instructions were a little bit confusing. I did not mean it as a sequence (a to c), but as a list of alternatives to try out, reverting to the original state (e.g. restoring kbibtexrc as it was) after each test. So, for the grep command, did your original kbibtex contain a line containing personNameFormatting? However, as you said that the same problem exist for you on a fresh account without any existing configuration, the bug may not be related to configuration issues ... Can you please test the most recent master version from git?
(In reply to manuel from comment #10) > but don't worry too much. If it's only me having this problem i can also use > JabRef, which is working just fine. (1) we don't know if you are the only one, you are only the first to report the problem, and (2) having you using JabRef is not acceptable for me ;-)
(In reply to manuel from comment #10) > but don't worry too much. If it's only me having this problem i can also use > JabRef, which is working just fine. Does the problem in KBibTeX still exist for you?
Thanks for checking back, Thomas. The problem actually does not exist anymore! Seems like I can switch over to KBibTeX now. Thanks again!