Some people use conditionals to sort items based on hard-coded cs:text
strings, e.g. to separate journal articles from books in the
bibliography.

Rintze

On Tue, Mar 12, 2013 at 5:15 PM, Frank Bennett <[email protected]> wrote:
> On Wed, Mar 13, 2013 at 12:28 AM, Bruce D'Arcus <[email protected]> wrote:
>> On labels and sorting, isn't this a general issue, such that we might want
>> to ignore any non-variable text content? E.g. the issue becomes apparent
>> with names, but is not logically limited to it?
>
> But mightn't affixes and cs:text contain things meant to be
> significant to the sort. I'm not sure.
>
>>
>> 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

------------------------------------------------------------------------------
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