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

allow column (and potentially other) ranges in bibliography #102

Open
denismaier opened this issue Jun 9, 2020 · 3 comments
Open

allow column (and potentially other) ranges in bibliography #102

denismaier opened this issue Jun 9, 2020 · 3 comments
Labels

Comments

@denismaier
Copy link
Member

There is a documented need for other ranges than page ranges in bibliographies: zotero/zotero-bits#62


The current proposal per @bwiernik:

Change page to have a type just like locator. All types that are valid for locator can be valid for page. If no type is supplied, assume that the type is "page".

Then, also adopt citeproc-js's system for multiple locator/page types by permitting a comma-delimited list with multiple locators differentiated by their label or abbreviation.

So, for example, to cite an item with a page and a column, it would be entered in page as:
"page": "123, col. 2"

or:
"page": "page 123, column 2"

The processor is expected to split such lists into an array and apply formatting rules separately to each element according to its type (e.g., APA rules want "Chapter" but short labels for other types).

@bwiernik
Copy link
Member

bwiernik commented Jun 9, 2020

We could probably simplify this down to “page may be a comma-delimited list of label-value pairs. A single value without a label is assumed to be a page number.”

That would keep it a flat variable and just involve a processor extension.

@bdarcus
Copy link
Member

bdarcus commented Jun 22, 2020

We could probably simplify this down to “page may be a comma-delimited list of label-value pairs. A single value without a label is assumed to be a page number.”

That would keep it a flat variable and just involve a processor extension.

I think this would be my preference. It's similar to what pandoc does for locators in general.

If this is the path, let's move this to documentation?

@denismaier
Copy link
Member Author

Good.

@bdarcus bdarcus transferred this issue from citation-style-language/schema Jun 27, 2020
@bdarcus bdarcus added the 1.1 label Jun 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants