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

Importing an entry, that were exported with BibTeXML format failed. #1665

Closed
tschechlovdev opened this issue Aug 2, 2016 · 5 comments
Closed
Labels
bug Confirmed bugs or reports that are very likely to be bugs status: duplicate

Comments

@tschechlovdev
Copy link
Contributor

tschechlovdev commented Aug 2, 2016

JabRef version
JabRef 3.5
windows 8.1 6.3 amd64
Java 1.8.0_25

Steps to reproduce:

  1. Select an entry in JabRef
  2. Go to "File" and then select "Export"
  3. Use "BibTeXML" as export format.
  4. Import the exported entry into a new database

I get hte following warning:
"1. The character reference must end with the ';' delimiter."

And after that no entries were imported.

@tschechlovdev tschechlovdev added the bug Confirmed bugs or reports that are very likely to be bugs label Aug 2, 2016
@tschechlovdev
Copy link
Contributor Author

tschechlovdev commented Aug 2, 2016

I think the reason for this is, that by the authors, the "," gets exported as and &#44. So for example von Hippel, Eric gets exported as von Hippel and &#44 Eric. And then a SAXParser Exception is thrown, because after &#44 is a ';' missing.

@boceckts
Copy link
Contributor

boceckts commented Aug 2, 2016

I think the authors aren't escaped at all because with my test file I also found out that &#45, &#34 and &#39 are not escaped in the authors field. After adding a";" after each of these codes I was able to import my xml file.

@matthiasgeiger
Copy link
Member

I think the field gets generally escaped correctly, but the ; which marks the end of an HTML entity such as , is stripped or interpreted as an delimiter between different authors.

@stefan-kolb
Copy link
Member

Related to #1337?!

@matthiasgeiger
Copy link
Member

Not only related but a duplicate ;-)

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 status: duplicate
Projects
None yet
Development

No branches or pull requests

4 participants