public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: fiddlosopher <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: All entries in `references` are listed in bibliography, not only the cited ones
Date: Fri, 11 Jun 2021 13:34:26 -0700 (PDT)	[thread overview]
Message-ID: <71de154c-86eb-440f-9abd-2b427a91fa99n@googlegroups.com> (raw)
In-Reply-To: <CRL_E3dQzLfOhyxpbNzi-raNcRKpow0Vs0jXxcjNID3K_nGu9AnbSVOO3MRI3ODFkeKDKUQm8nJssiqoe4GT5E9LC7f78UeR8GDJI2iNtBE=@protonmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2691 bytes --]


It wasn't an intentional change, so please submit a bug report.

On Friday, June 11, 2021 at 5:42:55 AM UTC-7 Nick Bart wrote:

> I’m seeing this, too (using the most recent dev version), and agree in 
> preferring the ‘old’ behaviour.
>
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Friday, June 11, 2021 11:44 AM, Frederik Elwert <frederi...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 
> wrote:
>
> Hello everybody,
>
> when upgrading pandoc in our publication workflow (2.9→2.13), and thus 
> switching from pandoc-citeproc to citeproc, we noticed a change in 
> behaviour:
>
> We are converting all references authors send us to csl-yaml and embedd 
> them within the markdown file through the `references` metadata variable.
>
> Previously, only those entries that were actually cited also got printed 
> in the bibliography. That’s what we expected. Now, with citeproc, we find 
> that *all* entries from the `references` list are printed in the 
> bibliography. This is different from taking the same entries, putting them 
> in an external bibtex file, and include them with the `bibliography` 
> metadata key. If we do that, we get the old behaviour.
>
> So in sum, `references` now behaves like `bibliography` + `nocite: @*`.
>
> Is this the new intended behaviour, or is this a bug/regression?
>
> (For us, the older behaviour worked better, because often authors have 
> additional entries in their bibliography, against the guidelines. The old 
> behaviour made sure we only include those that are actually cited. Now we 
> have to check the references list manually.)
>
> Thanks in advance,
> Frederik
>
>
> --
> 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/12103c9c-602d-4f60-b699-471dcbceb1dfn%40googlegroups.com 
> <https://groups.google.com/d/msgid/pandoc-discuss/12103c9c-602d-4f60-b699-471dcbceb1dfn%40googlegroups.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/71de154c-86eb-440f-9abd-2b427a91fa99n%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 3944 bytes --]

  reply	other threads:[~2021-06-11 20:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-11 11:44 Frederik Elwert
     [not found] ` <12103c9c-602d-4f60-b699-471dcbceb1dfn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-06-11 12:42   ` 'Nick Bart' via pandoc-discuss
2021-06-11 20:34     ` fiddlosopher [this message]
     [not found]       ` <71de154c-86eb-440f-9abd-2b427a91fa99n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-06-12 10:56         ` 'Nick Bart' via pandoc-discuss

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=71de154c-86eb-440f-9abd-2b427a91fa99n@googlegroups.com \
    --to=fiddlosopher-re5jqeeqqe8avxtiumwx3w@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).