A quick question regarding page range delimiters. I noticed that citeproc-js seems to replace the delimiter even when the style does not define a page-range-format — at least that's my inference, from the test suite, e.g.: the input for test fullstyles_ABdNT is pages "159-181" and the expected result is "159– 181"; the style being tested (associacao-brasileira-de-normas-tecnicas) does not have a page-range-format option.
The spec says that "If the attribute is not set, page ranges are rendered without reformatting." — My understanding of this was that page variable should not be touched at all, but the test case seems to suggest that the delimiter should still be replaced. Did I miss something here? If not (and if replacement is indeed the preferred approach) I think this should be stated explicitly in the spec. Sylvester
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________ xbiblio-devel mailing list xbiblio-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
