It looks like the processor in Papers has the same issue. It would be fairly easy to properly support the page range format. I suppose it makes sense that it should?
Charles On May 16, 2013, at 5:22 AM, Sebastian Karcher <[email protected]> wrote: > Hi everyone, > we got a question over at Zotero on page-range-format and locators. > Currently, citeproc-js doesn't apply the page range format to > locators, even if the locators _are_ a page range. > https://forums.zotero.org/discussion/29455/page-range/#Item_5 > > I wanted to check > a) how this is done in the other implementations (Andrea, Sylvester, Charles?) > b) ask what the preferred way of handling this is so that we can > include it in the specs. > > Thoughts? > > -- > Sebastian Karcher > Ph.D. Candidate > Department of Political Science > Northwestern University > > ------------------------------------------------------------------------------ > AlienVault Unified Security Management (USM) platform delivers complete > security visibility with the essential security capabilities. Easily and > efficiently configure, manage, and operate all of your security controls > from a single console and one unified framework. Download a free trial. > http://p.sf.net/sfu/alienvault_d2d > _______________________________________________ > xbiblio-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/xbiblio-devel -- Charles Parnot [email protected] twitter: @cparnot http://mekentosj.com ------------------------------------------------------------------------------ AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d _______________________________________________ xbiblio-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
