I've made some changes and created https://github.com/pandoc-ext/multibib/pull/8 for discussion. The changes in the PR work for my use case, but in fact I've decided to stick with the 'original-publisher' approach that I mentioned earlier. I control the necessary bibliography files and this approach doesn't require any changes to documents. I created https://github.com/jgm/pandoc/issues/9077 to suggest a utils.citeproc() 'quiet' flag. On Mon, 11 Sept 2023 at 11:27, William Lupton wrote: > Ah, I took a look and it seems that they are basically the same > (multiple-bibliographies -> multibib in the transition to pandoc-ext) but > their commit histories look different so there's obviously a bit more to it. > > Anyway, multiple-bibliographies avoids the problem by always running > citeproc as a JSON filter (via pandoc --citeproc for recent pandoc > versions) and passing the --quiet flag. > > I guess I'll use multiple-biographies for now, and look into how best to > update pandoc-ext/multibib, which really should be the "official" version. > > Any thoughts from anyone on whether utils.citeproc() could provide a > 'quiet' argument (or equivalent)? > > Thanks! > > On Mon, 11 Sept 2023 at 11:11, Bastien DUMONT > wrote: > >> Actually I meant this filter: >> https://github.com/pandoc/lua-filters/tree/master/multiple-bibliographies >> >> It seems to be an older version of multibib, but I never had the problemm >> you report with it. >> >> Le Monday 11 September 2023 à 10:59:26AM, 'William Lupton' via >> pandoc-discuss a écrit : >> > I'm hitting a (non-fatal but annoying) problem. The multibib filter >> first runs >> > citeproc to generate a list of all citations, then it reruns citeproc >> once for >> > each supplied bibliography file, and this generates warnings for the >> citations >> > in the _other_ bibliography files. >> > >> > For example, the test in the repo works ... but apparently doesn't (and >> it took >> > me a while to realise this)! >> > >> > % make >> > [WARNING] Citeproc: citation Bae not found >> > [WARNING] Citeproc: citation Knu86 not found >> > [WARNING] Citeproc: citation Bel not found >> > [WARNING] Citeproc: citation Nie72 not found >> > >> > I think that the best way to avoid the warnings would be to capture and >> ignore >> > them, but I'd (much) rather do that only for the secondary citeproc >> runs that >> > are _expected_ to output warnings. >> > >> > Is there a way to do this using the existing utils.citeproc() function? >> I tried >> > naively temporarily redefining io.stderr but perhaps that was never >> going to >> > work in the presumably-Haskell utils.citeproc(). >> > >> > Thanks, >> > William >> > >> > On Fri, 8 Sept 2023 at 13:03, William Lupton <[1] >> wlupton-QSt+ys/nuMyEUIsrzH9SikB+6BGkLq7r@public.gmane.org> >> > wrote: >> > >> > Thanks! [2]https://github.com/pandoc-ext/multibib I assume. I'll >> look into >> > it. >> > >> > On Fri, 8 Sept 2023 at 12:53, Bastien DUMONT <[3] >> bastien.dumont-VwIFZPTo/vqsTnJN9+BGXg@public.gmane.org> >> > wrote: >> > >> > I would split my bibliography file in two and use the >> > multiple-bibliographies filter. That's a sometimes irritating >> > limitation of CSL: you can check if a variable is set, but not >> test its >> > value. >> > >> > Le Friday 08 September 2023 à 11:17:57AM, 'William Lupton' via >> > pandoc-discuss a écrit : >> > > Hello, >> > > >> > > I'd like to sort references so a given publisher's ("BBF") >> references >> > are >> > > listed first, and am wondering whether it's possible to >> compare the >> > publisher >> > > variable with "BBF". I tried, but it doesn't seem to work >> (and the >> > CSL spec. >> > > doesn't appear to indicate that you can do this), so I've >> fallen back >> > on using >> > > original-publisher (I'll have to make sure that all the BBF >> > references use this >> > > rather than publisher). This works, but I'd prefer the first >> > approach. Any >> > > suggestions? >> > > >> > > CSL is attached. >> > > >> > > Thanks, >> > > William >> > > >> > > -- >> > > 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][4]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org >> > > To view this discussion on the web visit [2][5]https:// >> > groups.google.com/d/msgid/ >> > > pandoc-discuss/ >> > > CAEe_xxi5Q%2BBhE%2BO2EjfnYZAyF%3D_hr7HMcgKHcNKEYoFiJNSraw%[6] >> > 40mail.gmail.com. >> > > >> > > References: >> > > >> > > [1] mailto:[7]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org >> > > [2] [8]https://groups.google.com/d/msgid/pandoc-discuss/ >> > CAEe_xxi5Q%2BBhE%2BO2EjfnYZAyF%3D_hr7HMcgKHcNKEYoFiJNSraw% >> 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 [9]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org >> > To view this discussion on the web visit [10] >> https://groups.google.com/ >> > d/msgid/pandoc-discuss/ZPsLPLC_YQ-aiL_A%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 [11]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org >> > To view this discussion on the web visit [12] >> https://groups.google.com/d/msgid/ >> > pandoc-discuss/ >> > CAEe_xxgf_LcjS%3DZ%3D482ShAeMvMLdrmfHvYbEfMkVShcEuncROw% >> 40mail.gmail.com. >> > >> > References: >> > >> > [1] mailto:wlupton-QSt+ys/nuMyEUIsrzH9SikB+6BGkLq7r@public.gmane.org >> > [2] https://github.com/pandoc-ext/multibib >> > [3] mailto:bastien.dumont-VwIFZPTo/vqsTnJN9+BGXg@public.gmane.org >> > [4] mailto:pandoc-discuss%2Bunsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org >> > [5] https://groups.google.com/d/msgid/ >> > [6] http://40mail.gmail.com/ >> > [7] mailto:pandoc-discuss%2Bunsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org >> > [8] >> https://groups.google.com/d/msgid/pandoc-discuss/CAEe_xxi5Q%2BBhE%2BO2EjfnYZAyF%3D_hr7HMcgKHcNKEYoFiJNSraw%40mail.gmail.com?utm_medium=email&utm_source=footer >> > [9] mailto:pandoc-discuss%2Bunsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org >> > [10] >> https://groups.google.com/d/msgid/pandoc-discuss/ZPsLPLC_YQ-aiL_A%40localhost >> > [11] mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org >> > [12] >> https://groups.google.com/d/msgid/pandoc-discuss/CAEe_xxgf_LcjS%3DZ%3D482ShAeMvMLdrmfHvYbEfMkVShcEuncROw%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/ZP7nvJBEK7kmVHuU%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_xxg92Yut7LZgw1%2BQrSW9EWxje5jVta6WAppctkfKsCxLDw%40mail.gmail.com.