export to Harvard/RTF incorrect when name contains (properly escaped) "and"

[timobaumann]

JabRef version 3.2

• I have tested the latest development version from http://builds.jabref.org/master/ and the problem persists (JabRef-5.0-dev--snapshot--2018-11-23--master--742cfce7e.jar)

The export filter interprets all "and"s in name fields as breaking multiple names even when the author is properly escaped with curly braces.

Steps to reproduce the behavior:

1. consider the bibtex

@article{test,
  author = {{Organization for Economic Cooperation and Development}}
}

2. verify that latex+biber properly output "Organization for Economic Cooperation and Development" as author
3. export with Harvard filter and find "Organization for Economic Cooperation & Development".
4. change name to {{Organization for Economic Cooperation and Development and other stuff}} and rejoice at "for Economic Cooperation, O.; Development & other stuff"

Clearly, the export plugin does not honor the double curly braces that should prohibit breaking names.

I haven't found any other way of quoting the "and" to avoid breaking the name into multiple names that are then recombined, either.

[Siedlerchr]

Probably related to the latex to Unicode converter which kills the braces

[github-actions]

This issue has been inactive for half a year. Since JabRef is constantly evolving this issue may not be relevant any longer and it will be closed in two weeks if no further activity occurs.

As part of an effort to ensure that the JabRef team is focusing on important and valid issues, we would like to ask if you could update the issue if it still persists. This could be in the following form:

• If there has been a longer discussion, add a short summary of the most important points as a new comment (if not yet existing).
• Provide further steps or information on how to reproduce this issue.
• Upvote the initial post if you like to see it implemented soon. Votes are not the only metric that we use to determine the requests that are implemented, however, they do factor into our decision-making process.
• If all information is provided and still up-to-date, then just add a short comment that the issue is still relevant.

Thank you for your contribution!

[timobaumann]

the problem persists exactly as before.

[timobaumann]

@Siedlerchr , @github-actions , can you please re-open this? apparently us standard humans can't re-open our own issues in the github tracker... thanks.

[Siedlerchr]

@timobaumann So the problem exists in the latest development version 5.x?