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

corrupt BibTeXML export #1337

Closed
thomaszumbrunn opened this issue May 2, 2016 · 7 comments · Fixed by #2017
Closed

corrupt BibTeXML export #1337

thomaszumbrunn opened this issue May 2, 2016 · 7 comments · Fixed by #2017
Assignees
Labels
bug Confirmed bugs or reports that are very likely to be bugs
Milestone

Comments

@thomaszumbrunn
Copy link

JabRef version 3.3
(the issue is still present in 3.4dev--snapshot--2016-05-01--master--71eca69)

Steps to reproduce:

  1. Export a BibTeX file with "File > Export" to BibTeXML format.

An author field entry of the form

Burri, Emanuel and Beglinger, Christoph and von Felten, Stefanie and Lehmann, Frank Serge

is exported to

<bibtex:author>Burri&#44 and Emanuel and Beglinger&#44 and Christoph and von Felten&#44 and Stefanie and Lehmann&#44 and Frank Serge</bibtex:author>

instead of (as in version 3.2)

<bibtex:author>Burri&#44; Emanuel and Beglinger&#44; Christoph and von Felten&#44; Stefanie and Lehmann&#44; Frank Serge</bibtex:author>
@simonharrer simonharrer added the bug Confirmed bugs or reports that are very likely to be bugs label May 2, 2016
@koppor
Copy link
Member

koppor commented May 2, 2016

Nice to see that someone is using BibTeXML. We are discussing its future at #938. What is your usecase of BibTeXML?

I feel that the author field of BibTeXML is underspecified. Maybe the ideas of docbook (http://www.docbook.org/tdg/en/html/author.html) or biblatex, which (as default) distinguishes between prefix,family,suffix,given. - If xml elements such as given-name were used, one could improve XSLT scripts to provide different output formats.

@thomaszumbrunn
Copy link
Author

To me, the use of BibTeXML is not imperative. In the usecase at hand, I export a JabRef library to BibTeXML and process it with XSLT to generate XHTML. I'm happy with any other XML dialect.

@tobiasdiez
Copy link
Member

@koppor Something for the @JabRef/stupro ?

@stefan-kolb
Copy link
Member

Isn't this an author parser problem?

@tschechlovdev
Copy link
Contributor

I will rewrite the exporter with jaxb, since the importer is already written with jaxb. This should also fix the bug.

@koppor
Copy link
Member

koppor commented Sep 23, 2016

@thomaszumbrunn Please use a development build from http://builds.jabref.org/master
The fix will be included in the next release.

@thomaszumbrunn
Copy link
Author

Thanks a lot. Works like a charm.

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

Successfully merging a pull request may close this issue.

7 participants