Skip to content
New issue

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

Inconsistent page numbering format in CMS full-note #1475

Closed
usethe4ce opened this issue Mar 25, 2015 · 5 comments
Closed

Inconsistent page numbering format in CMS full-note #1475

usethe4ce opened this issue Mar 25, 2015 · 5 comments

Comments

@usethe4ce
Copy link

For CMS full-note (similarly, SBL and others), the final page number in a page range is abbreviated differently for the initial full citation using the entire article versus there or subsequently when specific pages are specified. For example:

1 John Smith, "Stuff," Journal of Stuff 1 (2015): 123-45.
2 Smith, "Stuff," 129-131.

Surely the inconsistency in two-digit vs. three-digit formats cannot be right.

@adam3smith
Copy link
Member

When reporting issues here, remember to always specify the reference manager you're using. CSL is used by almost 30 different products now, not all interpreting styles in the same way.

I'm assuming this refers to citeproc-js. There, we currently don't apply the page-range-format (in this case the shortened page numbers required by CMoS) to locators, i.e. specific page ranges for citations. I know we've talked about this in the past, but I don't know why we didn't implement this. @fbennett @rmzelle ?

@rmzelle
Copy link
Member

rmzelle commented Mar 25, 2015

We had some discussion at http://xbiblio-devel.2463403.n2.nabble.com/page-range-format-for-locators-tt7578609.html

The 1.0.1 spec already seems compatible with applying "page-range-format" to locators with the label "page": "page-range-format - Activates expansion or collapsing of page ranges", although it wouldn't hurt to make this explicit.

@adam3smith
Copy link
Member

yeah, I say we clarify the specs "Activates expansion or collapsing of page ranges for page and locator="page"" and ask citeprocs to fix this. Everyone seemed to think it was a good idea.

@rmzelle
Copy link
Member

rmzelle commented Mar 25, 2015

Do we already have a ticket? If not, please create one in "documentation".

@adam3smith
Copy link
Member

closing this since we have a proper ticket.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants