Upgrade StorageFootnote locators: en-dash prevents page-range elision
Zotero 9.0.6 (64-bit), Windows 10. I am using a CSL style with page-range-format=‘minimal’.
For footnote locators, I get different results depending on the range delimiter:
143-144 (hyphen) → 143–4 (correct)
143–144 (U+2013 en-dash) → 143–144 (not elided)
This is reproducible across several resource types. The en-dash is genuine U+2013 (Windows Alt+0150).
I believe this may be related to the earlier discussion here: https://forums.zotero.org/discussion/83460/abbreviations-of-page-number-ranges That discussion identified the same hyphen/en-dash distinction for page ranges (although it likely concerned the item’s Pages field rather than footnote locators). The proposed solution was simply to bypass en-dashes and use hyphens, but I’m not comfortable to do that (my page ranges come and go from various other platforms and I want to ensure correct dashing across all platforms).
Expected: 143–144 should be recognized as a page range and abbreviated to 143–4, just as 143-144 is.
Is this a current citeproc-js/Zotero limitation or a bug in locator handling? Given the prior issue was raised in 2020, is there any progress to resolving this? Thanks.
For footnote locators, I get different results depending on the range delimiter:
143-144 (hyphen) → 143–4 (correct)
143–144 (U+2013 en-dash) → 143–144 (not elided)
This is reproducible across several resource types. The en-dash is genuine U+2013 (Windows Alt+0150).
I believe this may be related to the earlier discussion here: https://forums.zotero.org/discussion/83460/abbreviations-of-page-number-ranges That discussion identified the same hyphen/en-dash distinction for page ranges (although it likely concerned the item’s Pages field rather than footnote locators). The proposed solution was simply to bypass en-dashes and use hyphens, but I’m not comfortable to do that (my page ranges come and go from various other platforms and I want to ensure correct dashing across all platforms).
Expected: 143–144 should be recognized as a page range and abbreviated to 143–4, just as 143-144 is.
Is this a current citeproc-js/Zotero limitation or a bug in locator handling? Given the prior issue was raised in 2020, is there any progress to resolving this? Thanks.
-
adamsmithThis is the exact same issue as reported earlier and is a citeproc-js issue (I'd probably call it a bug though it's not impossible there is some intention behind it to handle another edge case); it comes up very rarely (it's fairly unusual for folks to store en dashes in the pages field and they rarely import as such), so I don't think anyone has ever so much as looked at fixing this to be honest.