You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
E.g., if https://doi.org/10.1002/1096-9128(200005)12:6%3C375::AID-CPE480%3E3.0.CO;2-M is pasted, we could automatically decode that to https://doi.org/10.1002/1096-9128(200005)12:6<375::AID-CPE480>3.0.CO;2-M before checking for a DOI.
And as I say there, maybe we could special-case %3C followed by %3E in a detected DOI and decode the whole string (even without the https://, since those are almost certainly not going to be the real DOI characters.
The text was updated successfully, but these errors were encountered:
It looks like translation-server already decodes the URL before passing to Zotero.Utilities.cleanDOI(), but maybe we should just teach cleanDOI() to decode strings that look like URLs and also to special-case %3C and %3E for all DOIs. We'll then get this automatically for everything that uses zotero/utilities (desktop, translation-server, web-library, ZoteroBib, maybe some of iOS).
abaevbog
added a commit
to abaevbog/utilities
that referenced
this issue
Sep 6, 2023
https://forums.zotero.org/discussion/comment/439074/#Comment_439074
E.g., if
https://doi.org/10.1002/1096-9128(200005)12:6%3C375::AID-CPE480%3E3.0.CO;2-M
is pasted, we could automatically decode that tohttps://doi.org/10.1002/1096-9128(200005)12:6<375::AID-CPE480>3.0.CO;2-M
before checking for a DOI.And as I say there, maybe we could special-case
%3C
followed by%3E
in a detected DOI and decode the whole string (even without thehttps://
, since those are almost certainly not going to be the real DOI characters.The text was updated successfully, but these errors were encountered: