bibtex export quit working
bibtex export quit work.
for the last year i used the drag and drop function to export single citations to an opened bibtex file. this morning the function quit working. it's also no possible to export the whole library to bibtex. however it's possible to export to other formats.
there is no error message for the drag and drop task. i submitted the error with the code: 904913445
the error message for the library export task in german is as follows:"Ein Fehler ist aufgetreten bei dem Versuch, die ausgewählte Datei zu exportieren."
for the last year i used the drag and drop function to export single citations to an opened bibtex file. this morning the function quit working. it's also no possible to export the whole library to bibtex. however it's possible to export to other formats.
there is no error message for the drag and drop task. i submitted the error with the code: 904913445
the error message for the library export task in german is as follows:"Ein Fehler ist aufgetreten bei dem Versuch, die ausgewählte Datei zu exportieren."
I just installed Zotero stand-alone today on Mac OSX 10.7.5, and was testing the Bibtex export ability. I can use "File->Export Library..." with no problems.
The drag and drop functionality also seems to be working as well.
@zharmad: didn't work for the standalone either.
thx flo
My symptoms : When trying to export from Zotero (either directly or through Zotelo), Iget a truncated file, containing the first headers of the first entry, stopping short of the beginning of actual content, such as (all text surrounded by three stars) :
***
@article{spiegelhalter_bayesian_2002,
title = {***
and, when exporting directly, a message box tells me (IIRC) "Une erreur s'est produite lors de la tentative d'exportation du fichier sélectionné." ("An error happened during the attempt to export the selected file."). I get no error number nor proposition to transmit to Zotero web site.
Could you keep me posted on this ? It's quite annoying, since Zotero is my main bibliographic tool...
I get exactly the same output as the user above, in the form of
@article{authorkey_year
title = {
Due to I am using zotero at work, I am stuck with Firefox 11.0. What can I do to resolve this issue.
BibTex export used to work fine in the last months.
https://github.com/zotero/translators/raw/b7dc1496997391e3bd1411fc7a9e1cd093692730/BibTeX.js
open it with a text editor (notepad, TextEdit) and change the last Updated date to 2013-01-03 03:18:04
and then save the file to the translator directory in the Zotero data folder:
http://www.zotero.org/support/zotero_data#locating_your_zotero_library
, overwriting the existing Bibtex.js file
Thanks for the help!
Replacing the BibTex.js translator with this "older" version was successful. Thank you for the hint !
May I suggest fixing this problem notwithstanding the close expiration of 10.x ESR : I have a feeling that Debian users will be stuck with this version for a long time, and the alternatives available in "experimental" won't install...
Thanks for the help !
I'm pretty sure you can just install a recent FF version from mozilla on debian - it's not like aptitude is the only way to install on debian - and especially as Firefox won't provide any more security updates for the 10. branch when the ESR branch switches to 17 it would seem wise to update your browser anyway.
You could also run Zotero standalone, of course.
If this were a Zotero bug, we'd obviously fix it, but an incompatibility with an outdated browser version is not very attractive to spend (very limited) time on.
I do have the same problem: cannot export bibtex file of the whole library.
Same thing happens using Zotero standalone or FF18 on MacOsX mountain lion.
my report ID is : 709359221
thanks
françois
The whole library, no. :(
I'm wondering whether the problem is something specific to the "Export Library" function, or whether there is a problem with one (or a couple of) specific items.
On a more technical note, I think we might have to drop DOMParser for escaping formatting. I don't see how we can avoid mis-parsing fields with stray < characters (and probably some other characters too). I suggest that in the mean time we revert back to the BibTeX version we had before this was introduced.
I'm working through the BibTeX translator right now, but it will take me hopefully until the end of the week to finish.
Edit: I also noticed that we end up using invalid characters in BibTeX key generation
-> aurimas : I do have 810 articles in my Zotero ... it's a bit difficult to find which one can cause this issue... unless there is a tool to find such entries.