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

JabRef 3.2 corrupts .bib files so they no longer work with LaTeX #1331

Closed
CarinaDSLR opened this issue Apr 30, 2016 · 2 comments
Closed

JabRef 3.2 corrupts .bib files so they no longer work with LaTeX #1331

CarinaDSLR opened this issue Apr 30, 2016 · 2 comments
Labels
status: waiting-for-feedback The submitter or other users need to provide more information about the issue

Comments

@CarinaDSLR
Copy link

CarinaDSLR commented Apr 30, 2016

JabRef version 3.2 on Windows 7

Sorry If I'm doing this wrong, but thought this would be worth reporting.

I recently reset my laptop and installed the newest version of JabRef (3.2). I'm using it to manage my references for citing in LaTeX documents.
Long story short I installed the new JabRef and it started messing up my citations in LateX.
These are some of the error and warning messages I got in LaTeX (editor TeXnicCenter). I checked entires that it couldn't find but found no errors.
warning

Also, although I associated my .bib files with JabRef, the symbol of these files never changed into the usual JabRef one.

What fixed it:
I uninstalled JabRef 3.2, installed version 2.1 and suddenly everything worked fine again, but JabRef 3.2 seems to have somehow corrupted the .bib files I opened with it as version 2.1 can't open them now (I have backups so no harm done).

Jabref 2.1 gives me the following error when I try to open a "corrupted" .bib file:
error

Hope this helps. :/
I've used JabRef as my main reference manager for ages because it's the best no-messing-around ref manager and wouldn't mind updating to the newest edition.

@matthiasgeiger
Copy link
Member

Thanks for your report!

This should not happen - however, the excerpt shown in the first screenshot is correct and should not cause any trouble.

Can you please try the most recent version 3.3.
If the problem persists with this version it would be great if you can upload the corrupt bib file here - or send it me privately for further investigation.

Thanks!

@simonharrer simonharrer added status: waiting-for-feedback The submitter or other users need to provide more information about the issue and removed status: devcall labels May 10, 2016
@stefan-kolb
Copy link
Member

Closing this issue due to inactivity 💤
Please reopen the issue with additional information if the problem persists.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: waiting-for-feedback The submitter or other users need to provide more information about the issue
Projects
None yet
Development

No branches or pull requests

4 participants