We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
JabRef version 3.7dev (latest) on Windows 10
Steps to reproduce:
http://www.thinkmind.org/index.php?view=article&articleid=cloud_computing_2013_1_20_20130
&
The text was updated successfully, but these errors were encountered:
Integrity check for url should be disabled generally. At least in biblatex all URL related fields are treated as verbatim
Sorry, something went wrong.
Fixes #1958: Verbatim URL field is no longer checked for HTML encoded…
bfdcfeb
… characters by integrity checks
There is FieldProperty.VERBATIM that can be used as there are more fields which are verbatim in BibLatex.
FieldProperty.VERBATIM
Like this? if (!InternalBibtexFields.getFieldProperties(field.getKey()).contains(FieldProperty.VERBATIM)) {
if (!InternalBibtexFields.getFieldProperties(field.getKey()).contains(FieldProperty.VERBATIM)) {
d8ec439
Fixes JabRef#1958: Verbatim URL field is no longer checked for HTML e…
b3f1414
…ncoded chars (JabRef#1970)
stefan-kolb
No branches or pull requests
JabRef version 3.7dev (latest) on Windows 10
Steps to reproduce:
http://www.thinkmind.org/index.php?view=article&articleid=cloud_computing_2013_1_20_20130
&
inside it, an integrity check violation is shown. But the url is perfectly valid and no integrity check violation should be shown.The text was updated successfully, but these errors were encountered: