From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: 'Jan' via pandoc-discuss
<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>,
pandoc-discuss
<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: issue with "see also" of same and different author
Date: Mon, 06 Sep 2021 11:40:13 -0700 [thread overview]
Message-ID: <m235qhk0oi.fsf@MacBook-Pro-2.hsd1.ca.comcast.net> (raw)
In-Reply-To: <56afe475-1c44-4a9d-9b48-8f6f30608030n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
I've just pushed a change to citeproc that allows reordering with
collapsing, but not across the boundary of a citation with a
prefix or suffix. This should give good results.
"'Jan' via pandoc-discuss" <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
writes:
> Thanks so much for looking into this.
>
> I was thinking about another possibility: Is there perhaps a way to
> disable sorting, but keep the collapsing?
> So that in cases where in a string of citations the same author appears
> with multiple consecutive citations, the repeated author names are omitted,
> but if they appear in a string of citations but not consecutively, they are
> kept? Does that make sense?
>
>
>
>
>
>
> On Monday, September 6, 2021 at 9:37:00 AM UTC-7 John MacFarlane wrote:
>
>>
>> As I noted on the issue, citeproc already does include code
>> blocking sorting that rearranges prefixes, but this seems not
>> to work in the case where there is also collapsing (of citations
>> by same author). I have to look into why. Disabling collapsing
>> in your style could thus be one workaround, though it would mean
>> that you didn't get collapsing elsewhere.
>>
>>
>>
>> "'Jan' via pandoc-discuss" <pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
>> writes:
>>
>> > Thanks so much, John, I opened an issue on github.
>> >
>> > In the meanwhile, as a workaround, is there a way to disable sorting for
>> > CMS?
>> >
>> > On Saturday, September 4, 2021 at 10:28:39 PM UTC-7 John MacFarlane
>> wrote:
>> >
>> >>
>> >> The issue won't arise if you use a style that doesn't sort
>> >> citations, obviously, but that may not be an option here.
>> >>
>> >> I have a vague memory that this issue has come up before
>> >> in pandoc-citeproc or in CSL, and that there was some solution.
>> >>
>> >> Yes: https://github.com/jgm/pandoc-citeproc/issues/292
>> >>
>> >> Here is the fix I implemented in pandoc-citeproc:
>> >>
>> >>
>> >>
>> https://github.com/jgm/pandoc-citeproc/commit/31b463a939d4878d4c83c318976b66d723e70bf5
>> >>
>> >> It's not in the CSL spec, so maybe it's not appropriate to
>> >> modify citeproc to behave this way, but it sure is tempting.
>> >> So if you feel like putting up a bug report on jgm/citeproc
>> >> with links to the URLs mentioned above, please go ahead.
>> >>
>> >>
>> >> "'Jan' via pandoc-discuss" <pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
>> >> writes:
>> >>
>> >> > Hi all,
>> >> >
>> >> > I have a quick question.
>> >> > I'm processing for Chicago Manual of style author date format.
>> >> > pandoc -t docx --csl=.pandoc/csl/chicago-author-date.csl
>> >> >
>> >> > I'm using the following syntax
>> >> > [@Heller:2007i, 10; see also @Gal:1987; @Heller:1989].
>> >> >
>> >> > for a citation that I want to render as
>> >> > (Heller 2007, 10; see also Gal 1987; Heller 1989)
>> >> >
>> >> > what it does, it gives me:
>> >> > (Heller 2007, 10, 1989; see also Gal 1987)
>> >> >
>> >> > So it moves the Heller 1989 up front to join the first citation of
>> the
>> >> same
>> >> > author and then, obviously deletes the author last name.
>> >> > Is there any way to prevent that (only for this citation)?
>> >> > As the other Heller citation should come after the "see also".
>> >> >
>> >> > Help much appreciated!
>> >> >
>> >> > all best
>> >> >
>> >> > Jan
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > 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-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>> >> > To view this discussion on the web visit
>> >>
>> https://groups.google.com/d/msgid/pandoc-discuss/a4c90db8-d468-42c5-b7ac-2162ddc70492n%40googlegroups.com
>> >> .
>> >>
>> >
>> > --
>> > 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-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>> > To view this discussion on the web visit
>> https://groups.google.com/d/msgid/pandoc-discuss/e721f4fa-f560-4ffc-a9a7-2749db068bc6n%40googlegroups.com
>> .
>>
>
> --
> 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/56afe475-1c44-4a9d-9b48-8f6f30608030n%40googlegroups.com.
prev parent reply other threads:[~2021-09-06 18:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-05 2:07 'Jan' via pandoc-discuss
[not found] ` <a4c90db8-d468-42c5-b7ac-2162ddc70492n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-09-05 5:28 ` John MacFarlane
[not found] ` <m2k0jvlhfr.fsf-jF64zX8BO0+FqBokazbCQ6OPv3vYUT2dxr7GGTnW70NeoWH0uzbU5w@public.gmane.org>
2021-09-05 22:16 ` 'Jan' via pandoc-discuss
[not found] ` <e721f4fa-f560-4ffc-a9a7-2749db068bc6n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-09-06 16:36 ` John MacFarlane
[not found] ` <m2mtopk6eb.fsf-jF64zX8BO0+FqBokazbCQ6OPv3vYUT2dxr7GGTnW70NeoWH0uzbU5w@public.gmane.org>
2021-09-06 18:00 ` 'Jan' via pandoc-discuss
[not found] ` <56afe475-1c44-4a9d-9b48-8f6f30608030n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-09-06 18:40 ` John MacFarlane [this message]
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=m235qhk0oi.fsf@MacBook-Pro-2.hsd1.ca.comcast.net \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@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).