Upgrade StorageChicago - case sensitive order in bibliography
Dear all,
I use a slightly modified chicago author-date style. In the bibliogrpahy, items are shown in alphebetical order, but capitalized names (such as abbreviated organizations) are listed first. This is probably the same in the original Chicago style as well. E.g.:
BMZ. 2010. BLablabla. Bonn / Berlin: BMZ.
comes before
Bechmann, Gotthard, Vitaly Gorokhov, and Nico Stehr. 2009. “Introduction.” In Blablabla, 9–31. Berlin: Ed. Sigma.
There was a similar discussion before (http://forums.zotero.org/discussion/17150/), but unfortunately I didn´t get the information I need out of it - where in the csl code can I change the order of appearance, so it doesn´t matter whether an author is written in capital letters? Is that a simple change or does it require good csl skills (which I don´t have, unfortunately...)
Thank you!
I use a slightly modified chicago author-date style. In the bibliogrpahy, items are shown in alphebetical order, but capitalized names (such as abbreviated organizations) are listed first. This is probably the same in the original Chicago style as well. E.g.:
BMZ. 2010. BLablabla. Bonn / Berlin: BMZ.
comes before
Bechmann, Gotthard, Vitaly Gorokhov, and Nico Stehr. 2009. “Introduction.” In Blablabla, 9–31. Berlin: Ed. Sigma.
There was a similar discussion before (http://forums.zotero.org/discussion/17150/), but unfortunately I didn´t get the information I need out of it - where in the csl code can I change the order of appearance, so it doesn´t matter whether an author is written in capital letters? Is that a simple change or does it require good csl skills (which I don´t have, unfortunately...)
Thank you!
Following those earlier reports, I set the processor up to attempt to avoid using the normal sort comparison method (localeCompare()) because it appeared to be broken in Firefox. (Instead of using human-readable alphabetic values, localeCompare() was just sorting on the numeric value that the computer assigns to each characters, which is, well, wrong.)
The localeCompare() function is apparently still broken, but the alternative I used (to compare strings using a "collation") is not available for some reason, so it's falling back to our old friend localeCompare(). Hence the weird sort results you're getting.
Zotero itself is beyond my jurisdiction, so to speak (I just work on the citation processor), but the collation sort method appears still to be available in Firefox, since code that uses it is still contained in the latest versions of Zotero. There have been some recent changes in the Zotero code for word processor integration, and it's possible that the only problem is that the processor just doesn't have access to the collation object anymore. If that's so, it should be simple to fix.
In any case, you needn't take any steps at your end; just wait a bit for this to be sorted out and all will be well.