error opening bib

[icamps]

Hello,

I update my JabRef to v3.1

Now, opening my bibtex database (attached) I got an error message (attached) that I do not know how to solve.

Regards,

Camps

unifal.zip

[oscargus]

Open the file in a text editor. Go to line 1516. See if there's a strange looking line there (missing a comma between fields). If you cannot find it copy +/-5 five lines and paste here.

Look at the end of the file. Seems like the last entry is not ended correctly. Again, paste the last five lines or so here unless you figure out what to fix.

[icamps]

I did that: nothing out of normal.

Here there are:
Lines 1513 to 1525:

@Article{dock_compare2,
Title = {Evaluation of docking programs for predicting binding of Golgi $\alpha$-mannosidase {II} inhibitors: {A} comparison with crystallography},
Author = {Pablo Englebienne and H{'e}l\grave{e}ne Fiaux and Douglas A. Kuntz and Christopher R. Corbeil and Sandrine Gerber-Lemaire and David R. Rose and Nicolas Moitessier},
Journal = {Proteins},
Pages = {160--176},
Volume = {69},
Year = {2007},
File = {dock_compare2.pdf:dock_compare2.pdf:PDF},
Keywords = {docking},
Owner = {icamps},
Timestamp = {2008.11.03}
}

Last lines:
@comment{jabref-meta: selector_publisher:}

@comment{jabref-meta: selector_review:}

@comment{jabref-meta: groupsversion:3;}

[oscargus]

The entry looks OK.

I think it might be the semi-colon at the end, but no idea really... Weird.

[icamps]

I remove the Latex code in H{'e}l\grave{e}ne, and I could open the file with the EOF error only.

[tobiasdiez]

Did you tried removing the last line?

So just to understand you correctly: the file opened without any problems in a previous version of jabref (which one?) and after the upgrade you got these errors, without changing the file. Right?

[icamps]

@tobiasdiez:

Answer: Did you tried removing the last line?
Yes I removed various "last lines", unsuccessfully.

Answer: ...after the upgrade you got these errors, without changing the file. Right?
Yes, that's right.

Just now I fixed the problem manually: create an empty database, copy/paste all my entries, save the new database, and everything is ok.

[tobiasdiez]

Could you pls send me the problematic bib file (and the working one) via email to [email protected] if it does not contain sensitive information? Then I can better investigate this problem.

[icamps]

@tobiasdiez I already sent the files to your email.

[tobiasdiez]

There were two problems with the bib file (wrong format of the accent and not closed brackets in one entry). Thus it is correct that JabRef warns here.

Nonetheless, there is room for improvement: the second warning occurs 1000 lines below the faulty entry. Not sure though to implement a better warning message (it should remember when a field started and then also print this additional information). Track this here or in a new issue?

[icamps]

@tobiasdiez Thank you very much. I will be more careful :)

[tobiasdiez]

@icamps You are welcome. Did you get my email with details how to fix the issues in the bib files?

[icamps]

Yes! I fixed and recovered the entries missed.

Thank you very much.

[]'s,

@mps

On Mon, Jan 11, 2016 at 8:39 PM, Tobias Diez [email protected]
wrote:

@icamps https://github.com/icamps You are welcome. Did you get my email
with details how to fix the issues in the bib files?

—
Reply to this email directly or view it on GitHub
#650 (comment).