Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

URL with encoded html characters is shown as a violation regarding the integrity check #1958

Closed
simonharrer opened this issue Sep 12, 2016 · 3 comments
Assignees
Labels
[outdated] type: bug Confirmed bugs or reports that are very likely to be bugs
Milestone

Comments

@simonharrer
Copy link
Contributor

JabRef version 3.7dev (latest) on Windows 10

Steps to reproduce:

  1. Have an entry with url field http://www.thinkmind.org/index.php?view=article&articleid=cloud_computing_2013_1_20_20130
  2. Check integrity
  3. As url has & inside it, an integrity check violation is shown. But the url is perfectly valid and no integrity check violation should be shown.
@Siedlerchr
Copy link
Member

Integrity check for url should be disabled generally. At least in biblatex all URL related fields are treated as verbatim

@stefan-kolb stefan-kolb self-assigned this Sep 13, 2016
@stefan-kolb stefan-kolb added this to the v3.7 milestone Sep 13, 2016
@stefan-kolb stefan-kolb added the [outdated] type: bug Confirmed bugs or reports that are very likely to be bugs label Sep 13, 2016
stefan-kolb added a commit that referenced this issue Sep 13, 2016
@oscargus
Copy link
Contributor

There is FieldProperty.VERBATIM that can be used as there are more fields which are verbatim in BibLatex.

@stefan-kolb
Copy link
Member

Like this? if (!InternalBibtexFields.getFieldProperties(field.getKey()).contains(FieldProperty.VERBATIM)) {

@koppor koppor closed this as completed in d8ec439 Sep 13, 2016
zesaro pushed a commit to zesaro/jabref that referenced this issue Nov 22, 2016
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
[outdated] type: bug Confirmed bugs or reports that are very likely to be bugs
Projects
None yet
Development

No branches or pull requests

4 participants