> But mightn't affixes and cs:text contain things meant to be
> significant to the sort. I'm not sure.
>
> For affixes I'd be inclined to say no, but as an example for non-variable
cs:text mattering, consider sort-keys constructed using text value... (as
e.g. for sorting by types).
I didn't check if we have any on the repository, but see e.g.
http://blogs.eui.eu/zotero/sort-a-bibliography-by-type.html as well as
several forum threads.



> >
> > On Mar 12, 2013 9:45 AM, "Rintze Zelle" <[email protected]> wrote:
> >>
> >> Two related issues were raised on the Zotero forums:
> >>
> >> http://forums.zotero.org/discussion/25637/
> >>
> >> 1) Should name variable labels be ignored for sorting?
> >>
> >> Previously, citeproc-js included the labels in the sort keys, which
> >> would give results like
> >>
> >> Pollitt, C. and Bouckaert, G. (2004)
> >> Pollitt, C. and Bouckaert, G. (eds.) (1995)
> >>
> >> when sorting on the author macro and ascending on date of issue. The
> >> consensus of the thread seems to be that it is preferable to ignore
> >> the labels instead for sorting, so we would get
> >>
> >> Pollitt, C. and Bouckaert, G. (eds.) (1995)
> >> Pollitt, C. and Bouckaert, G. (2004)
> >>
> >> 2) Should name variable labels be ignored when applying subsequent
> >> author substitution?
> >>
> >> Previously, citeproc-js would produce
> >>
> >> Jones, Jim. 2011a. *A Title*. Location: Publisher.
> >> ———. 2011b. *C Title*. Location: Publisher.
> >> Jones, Jim, ed. 2011c. *B Title*. Location: Publisher.
> >>
> >> with subsequent-author-substitute active. The Zotero thread consensus
> >> seems to be that it would be preferable to get
> >>
> >> Jones, Jim. 2011a. *A Title*. Location: Publisher.
> >> ———. 2011b. *C Title*. Location: Publisher.
> >> ———, ed. 2011c. *B Title*. Location: Publisher.
> >>
> >> ---
> >>
> >> Unless anybody objects within the next few days to either of these
> >> proposed changes I'll modify the CSL specification accordingly.
> >>
> >> Rintze
> >>
> >>
> >>
> ------------------------------------------------------------------------------
> >> Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
> >> Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the
> >> endpoint security space. For insight on selecting the right partner to
> >> tackle endpoint security challenges, access the full report.
> >> http://p.sf.net/sfu/symantec-dev2dev
> >> _______________________________________________
> >> xbiblio-devel mailing list
> >> [email protected]
> >> https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
> >
> >
> >
> ------------------------------------------------------------------------------
> > Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
> > Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the
> > endpoint security space. For insight on selecting the right partner to
> > tackle endpoint security challenges, access the full report.
> > http://p.sf.net/sfu/symantec-dev2dev
> > _______________________________________________
> > xbiblio-devel mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
> >
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_mar
> _______________________________________________
> xbiblio-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
>



-- 
Sebastian Karcher
Ph.D. Candidate
Department of Political Science
Northwestern University
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
_______________________________________________
xbiblio-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xbiblio-devel

Reply via email to