Upgrade StorageRIS page numbers / SP EP
Hej,
when importing from certain pages (e.g. http://bit.ly/ban4EV) one will see that they don't use a minus for the page ranges. They will use an en dash like this 687–689 or a space is put before and after the minus.
This causes a problem when exporting to RIS: According to the standard the starting page is filed in field SP and the last page in field EP. When Zotero cannot detect the delimiter it just exports the whole string, e.g. "687–689" in both fields. Unfortunately Zotero will only detect the page range of a minus without spaces is used e.g. "687-689".
How can I contribute to fix this problem?
Thanks :-)
when importing from certain pages (e.g. http://bit.ly/ban4EV) one will see that they don't use a minus for the page ranges. They will use an en dash like this 687–689 or a space is put before and after the minus.
This causes a problem when exporting to RIS: According to the standard the starting page is filed in field SP and the last page in field EP. When Zotero cannot detect the delimiter it just exports the whole string, e.g. "687–689" in both fields. Unfortunately Zotero will only detect the page range of a minus without spaces is used e.g. "687-689".
How can I contribute to fix this problem?
Thanks :-)
-
kenparkNo ideas? How can I file a bug on this project?
-
ajlyonThis does seem like a bug. Would it be better to change the translator for affected sites to convert en-dash delimited page numbers, or to change the Zotero RIS translator? I personally think it'd be better to change the translators, since there's no reason I can think of to maintain delimiter inconsistency within the database.
-
kenparkI second that. But I would keep the en-dash as the delimiter the from xx-yy is what the en-dash is for, right?
-
dstillmanAdded support for en dashes and intervening spaces in the latest dev build.