From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.text.pandoc/29180 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: "'Jan' via pandoc-discuss" Newsgroups: gmane.text.pandoc Subject: Re: issue with "see also" of same and different author Date: Sun, 5 Sep 2021 15:16:04 -0700 (PDT) Message-ID: References: Reply-To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_5768_1198887343.1630880164996" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="33752"; mail-complaints-to="usenet@ciao.gmane.io" To: pandoc-discuss Original-X-From: pandoc-discuss+bncBDE3PAE53QFRBJMD2WEQMGQEH3UJRXI-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Mon Sep 06 00:16:08 2021 Return-path: Envelope-to: gtp-pandoc-discuss@m.gmane-mx.org Original-Received: from mail-ot1-f60.google.com ([209.85.210.60]) by ciao.gmane.io with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1mN0Qq-0008Vu-G0 for gtp-pandoc-discuss@m.gmane-mx.org; Mon, 06 Sep 2021 00:16:08 +0200 Original-Received: by mail-ot1-f60.google.com with SMTP id 8-20020a9d0588000000b0051defe13038sf3426278otd.9 for ; Sun, 05 Sep 2021 15:16:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20210112; h=date:from:to:message-id:in-reply-to:references:subject:mime-version :x-original-sender:reply-to:precedence:mailing-list:list-id :list-post:list-help:list-archive:list-subscribe:list-unsubscribe; bh=6U9Uneqzp7iO+it+rbWRB2hN/WbuJ42UJKkCa1WlYyY=; b=OUGevIQUZI2m9/3DBk/61MFMsNMutH8lzUtnctu4hJ6B+RjJBP39spCNHsGmLZWb2h L0FYj5zj7aUxAEKEAf43+UsmQCPzMkkvD+SPg/fty1tNX7EVGGPN49kelBPMnJTPGwQH KGSsMduSyLvOyJ5NGTifWQZUu5V5yb4AmY/UfiMlFKW5aLffl2EHiUWXAhIEc1U4vpMV Itw01qlGDeEDSkpaqHXTODjDpVImkyOkZaPAEeXtW5WF/Cd97TIjJo91SGb+4FNCo0fH prwjIR/RfXXGDkp6MAFzcytbOijoQ+7vucVT6YDZe+u8c0Kp0GdvjSfbeS6hPOcNUnlt +k/Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:message-id:in-reply-to:references :subject:mime-version:x-original-sender:reply-to:precedence :mailing-list:list-id:x-spam-checked-in-group:list-post:list-help :list-archive:list-subscribe:list-unsubscribe; bh=6U9Uneqzp7iO+it+rbWRB2hN/WbuJ42UJKkCa1WlYyY=; b=dybA5e4eXRIbjJOv1Xuulavh+9Nq4K9EjgMIghFaujpsl/t+OLu9a/wlqe1TX64Ena 5oyM2g6FredXfWJmYlPBD6nf8SQeCT+tvl0+uh31Dh319GiiV1M/p+XrdrE0DtbLiezd P95tjU/TcSCVqz2wVNkrnR3slu7OwB0bbmrztyfLleekvMULrGCQj0HHctmm3/0R78+R d526ZijWO2KTbW+9k3JKSpNEvuy1Hhq/AdLTNfRSNTB5q+Cr7WPe6UNAYDjY/6WWaDAg nNZbyNmNkYXItoUTAWtU+Q0e8le1pkJc0pNmODvb+R1Vd8PMrWms7mvZXlUdlf844aNt y/CA== X-Gm-Message-State: AOAM531JBEp+1qDzm19lUZgePbKoeEsGNB5qkpEEGCWaZLZ9i0ktglWY mxPEIyGWMJeTbSyx2h0k27o= X-Google-Smtp-Source: ABdhPJyqVWRuCLpqjt2o5OzBkBsG9E/Nd5ag++jgCAcEYJuxKe+1+7IhGQLYQAuqPr/kU8VGUCqn5g== X-Received: by 2002:a05:6830:2b24:: with SMTP id l36mr8866076otv.25.1630880167468; Sun, 05 Sep 2021 15:16:07 -0700 (PDT) X-BeenThere: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Original-Received: by 2002:a05:6830:907:: with SMTP id v7ls1261593ott.9.gmail; Sun, 05 Sep 2021 15:16:05 -0700 (PDT) X-Received: by 2002:a05:6830:124b:: with SMTP id s11mr8322551otp.90.1630880165561; Sun, 05 Sep 2021 15:16:05 -0700 (PDT) In-Reply-To: X-Original-Sender: jandavidhauck-g/b1ySJe57IN+BqQ9rBEUg@public.gmane.org X-Original-From: Jan Precedence: list Mailing-list: list pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org; contact pandoc-discuss+owners-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org List-ID: X-Google-Group-Id: 1007024079513 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , Xref: news.gmane.io gmane.text.pandoc:29180 Archived-At: ------=_Part_5768_1198887343.1630880164996 Content-Type: multipart/alternative; boundary="----=_Part_5769_510234664.1630880164996" ------=_Part_5769_510234664.1630880164996 Content-Type: text/plain; charset="UTF-8" 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" > 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-discuss+unsubscribe-/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. ------=_Part_5769_510234664.1630880164996 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks so much, John, I opened an issue on github.

=
In the meanwhile, as a workaround, is there a way to disable sor= ting for CMS?  

On Saturday, September 4, 2021 at 10:28:39 P= M 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/31b463a939d4878d4c83= c318976b66d723e70bf5

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,=20
>
> I have a quick question.=20
> I'm processing for Chicago Manual of style author date format.= =20
> pandoc -t docx --csl=3D.pandoc/csl/chicago-author-date.csl =20
>
> I'm using the following syntax=20
> [@Heller:2007i, 10; see also @Gal:1987; @Heller:1989].=20
>
> for a citation that I want to render as
> (Heller 2007, 10; see also Gal 1987; Heller 1989)=20
>
> what it does, it gives me:=20
> (Heller 2007, 10, 1989; see also Gal 1987)=20
>
> So it moves the Heller 1989 up front to join the first citation of= the same=20
> author and then, obviously deletes the author last name. =20
> Is there any way to prevent that (only for this citation)? =20
> As the other Heller citation should come after the "see also&= quot;.
>
> Help much appreciated!
>
> all best
>
> Jan
>
>
>
> --=20
> 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..= .@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/a4c9= 0db8-d468-42c5-b7ac-2162ddc70492n%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups &= quot;pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to pand= oc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@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.
------=_Part_5769_510234664.1630880164996-- ------=_Part_5768_1198887343.1630880164996--