That's what I'm currently using :). It's assigned the values 1, 2, 3 etc. as citations are encountered (please see my example). Thanks, W. On Fri, 21 Jan 2022 at 17:37, Bastien DUMONT wrote: > I have not tested, but does the CSL 'citation-number' variable address > your need? > https://docs.citationstyles.org/en/v1.0.2/specification.html#toc-entry-92 > > Le Friday 21 January 2022 à 04:36:56PM, William Lupton a écrit : > > All, > > > > I've been using citation-number to label and sort citations, which means > that > > citations are presented in the order in which they were cited. > > > > I'd prefer to have citations sorted by call-number but still labeled 1, > 2, 3... > > However, I can't see how to do this: it would apparently require a > numeric > > variable that corresponds to the sorted order (regardless of sort key). > > > > (It seems that, if this isn't possible using standard CSL, it could be > > addressed by asking citeproc to support a non-standard 'sorted-number' > (or > > similar) variable.) > > > > Any ideas? > > > > Thanks, > > William > > > > ---- example ---- > > > > With the markdown shown below, my CSL (which I could supply) gives this > > (citations sorted by order of reference): > > > > [1] RFC 2549, IP over Avian Carriers with Quality of Service, IETF, > 1999 > > [2] RFC 1149, Avian Carriers, IETF, 1990 > > > > ...but I'd like this (citations sorted by call-number): > > > > [1] RFC 1149, Avian Carriers, IETF, 1990 > > [2] RFC 2549, IP over Avian Carriers with Quality of Service, IETF, > 1999 > > > > --- > > title: Reference order illustration > > > > references: > > - id: RFC1149 > > call-number: RFC 1149 > > title: Avian Carriers > > publisher: IETF > > issued: {year: 1990} > > > > - id: RFC2549 > > call-number: RFC 2549 > > title: IP over Avian Carriers with Quality of Service > > publisher: IETF > > issued: {year: 1999} > > ... > > > > # Text > > > > This is RFC 2549 [@RFC2549]. > > > > This is RFC 1149 [@RFC1149]. > > > > # References > > > > -- > > You received this message because you are subscribed to the Google Groups > > "pandoc-discuss" group. > > To unsubscribe from this group and stop receiving emails from it, send > an email > > to [1]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > To view this discussion on the web visit [2] > https://groups.google.com/d/msgid/ > > pandoc-discuss/ > > CAEe_xxga_Ow_9OE%2B7JSyDSNo%2B9ePE3CY1LsbpasZsP9SBRak7A%40mail.gmail.com > . > > > > References: > > > > [1] mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org > > [2] > https://groups.google.com/d/msgid/pandoc-discuss/CAEe_xxga_Ow_9OE%2B7JSyDSNo%2B9ePE3CY1LsbpasZsP9SBRak7A%40mail.gmail.com?utm_medium=email&utm_source=footer > > -- > You received this message because you are subscribed to the Google Groups > "pandoc-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > To view this discussion on the web visit > https://groups.google.com/d/msgid/pandoc-discuss/YervEDxywP%2BR%2BYIV%40localhost > . > -- You received this message because you are subscribed to the Google Groups "pandoc-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/CAEe_xxgK%3D6C-7-3XYGpvMMeOL5Rv%3D4e0tp5efEoZb6_j3qCkHA%40mail.gmail.com.