From: William Lupton <wlupton-QSt+ys/nuMyEUIsrzH9SikB+6BGkLq7r@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Can citations be sorted by call-number but be labeled with a corresponding increasing integer?
Date: Mon, 24 Jan 2022 12:59:05 +0000 [thread overview]
Message-ID: <CAEe_xxhmuMOj_dkxxKEF5TxbZpR0JpO1qmDtnLvcrR662Z2wnQ@mail.gmail.com> (raw)
In-Reply-To: <Ye6ATiVa/BQBtwrw@localhost>
[-- Attachment #1: Type: text/plain, Size: 8685 bytes --]
Thanks Bastien. Please see below:
On Mon, 24 Jan 2022 at 10:34, Bastien DUMONT <bastien.dumont-VwIFZPTo/vqsTnJN9+BGXg@public.gmane.org>
wrote:
> OK, so have you set instructions for sorting in your CSL file?
> https://docs.citationstyles.org/en/v1.0.2/specification.html#sorting
Yes. Let me share the relevant bits of my csl file:
<citation>
<layout delimiter="; ">
<text variable="title-short" suffix=" "/>
<group prefix="[" suffix="]">
<text variable="locator" suffix="/"/>
<text variable="citation-number"/>
</group>
</layout>
</citation>
<bibliography entry-spacing="0">
<sort>
<key variable="citation-number"/>
</sort>
<layout>
<text variable="citation-number" prefix="[" suffix="]"
display="left-margin"/>
<group delimiter=", " display="right-inline">
<text variable="call-number" text-decoration="underline"/>
<text variable="title" font-style="italic"/>
<text variable="publisher"/>
<date date-parts="year" form="text" variable="issued"/>
<text variable="URL"/>
</group>
</layout>
</bibliography>
> "citation-number" is the "variable that corresponds to the sorted order
> (regardless of sort key)" that you are looking for.
>
Hmm. But is it? In my example (repeated here for simplicity) the markdown
shown below and my CSL gives this (citations sorted by citation-number,
which appears to be 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
Markdown:
---
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
> Le Monday 24 January 2022 à 10:01:21AM, William Lupton a écrit :
> > 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 <[1]
> bastien.dumont-VwIFZPTo/vqsTnJN9+BGXg@public.gmane.org>
> > wrote:
> >
> > I have not tested, but does the CSL 'citation-number' variable
> address your
> > need?
> > [2]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][3]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> > > To view this discussion on the web visit [2][4]
> https://groups.google.com/
> > d/msgid/
> > > pandoc-discuss/
> > > CAEe_xxga_Ow_9OE%2B7JSyDSNo%2B9ePE3CY1LsbpasZsP9SBRak7A%[5]
> > 40mail.gmail.com.
> > >
> > > References:
> > >
> > > [1] mailto:[6]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> > > [2] [7]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 [8]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> > To view this discussion on the web visit [9]
> 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 [10]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> > To view this discussion on the web visit [11]
> https://groups.google.com/d/msgid/
> > pandoc-discuss/
> > CAEe_xxgK%3D6C-7-3XYGpvMMeOL5Rv%3D4e0tp5efEoZb6_j3qCkHA%40mail.gmail.com
> .
> >
> > References:
> >
> > [1] mailto:bastien.dumont-VwIFZPTo/vqsTnJN9+BGXg@public.gmane.org
> > [2]
> https://docs.citationstyles.org/en/v1.0.2/specification.html#toc-entry-92
> > [3] mailto:pandoc-discuss%2Bunsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> > [4] https://groups.google.com/d/msgid/
> > [5] http://40mail.gmail.com/
> > [6] mailto:pandoc-discuss%2Bunsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> > [7]
> https://groups.google.com/d/msgid/pandoc-discuss/CAEe_xxga_Ow_9OE%2B7JSyDSNo%2B9ePE3CY1LsbpasZsP9SBRak7A%40mail.gmail.com?utm_medium=email&utm_source=footer
> > [8] mailto:pandoc-discuss%2Bunsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> > [9]
> https://groups.google.com/d/msgid/pandoc-discuss/YervEDxywP%2BR%2BYIV%40localhost
> > [10] mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> > [11]
> https://groups.google.com/d/msgid/pandoc-discuss/CAEe_xxgK%3D6C-7-3XYGpvMMeOL5Rv%3D4e0tp5efEoZb6_j3qCkHA%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/Ye6ATiVa/BQBtwrw%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_xxhmuMOj_dkxxKEF5TxbZpR0JpO1qmDtnLvcrR662Z2wnQ%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 14418 bytes --]
next prev parent reply other threads:[~2022-01-24 12:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 16:36 William Lupton
[not found] ` <CAEe_xxga_Ow_9OE+7JSyDSNo+9ePE3CY1LsbpasZsP9SBRak7A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-01-21 17:36 ` Bastien DUMONT
2022-01-24 10:01 ` William Lupton
[not found] ` <CAEe_xxgK=6C-7-3XYGpvMMeOL5Rv=4e0tp5efEoZb6_j3qCkHA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-01-24 10:32 ` Bastien DUMONT
2022-01-24 12:59 ` William Lupton [this message]
[not found] ` <CAEe_xxhmuMOj_dkxxKEF5TxbZpR0JpO1qmDtnLvcrR662Z2wnQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-01-24 13:59 ` Bastien DUMONT
2022-01-24 17:17 ` William Lupton
[not found] ` <CAEe_xxgGSPFFcQr0e9mc6A1ZY=WpS=-z8bbEySZaWCPXrfmzrQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-01-24 18:10 ` Bastien DUMONT
2022-01-25 9:49 ` William Lupton
[not found] ` <CAEe_xxiG4+1dbGzmvm_km9=3nEVc_LmCz-zja7MeW3s_W+23Zg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-01-25 10:05 ` Bastien DUMONT
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAEe_xxhmuMOj_dkxxKEF5TxbZpR0JpO1qmDtnLvcrR662Z2wnQ@mail.gmail.com \
--to=wlupton-qst+ys/numyeuisrzh9sikb+6bgklq7r@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).