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
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).
The text was updated successfully, but these errors were encountered:
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.
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?
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).
The text was updated successfully, but these errors were encountered: