From: Julien Dutant <julien.dutant-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Recursive citeproc with the multibib lua filter
Date: Thu, 23 Feb 2023 06:40:39 -0800 (PST) [thread overview]
Message-ID: <8719e317-4d02-4206-8f84-e6c394b32946n@googlegroups.com> (raw)
In-Reply-To: <473da17f-5a82-4d44-9b83-eb1cf35d43e6n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 2004 bytes --]
Hi,
I'd be interested in developing this feature for Pandoc-ext's multibib and
especially section-bibliographies and multi-bib
(https://github.com/pandoc-ext/section-bibliographies), if Albert is
willing to consider the addition. I've already developed a recursive
bibliography filter:
https://github.com/dialoa/dialectica-filters/tree/main/recursive-citeproc
It's not the most efficient solution for more recent versions of Pandoc
(this was back in 2.6 I think, and my code isn't the most elegant), but it
works.
It was developed for the journal Dialectica, which has citations within the
bibliography. I'm thinking of porting dialectica to Quarto and make use of
section-bibliographies, so I'd be needing that feature anyway.
Against the inclusion of such a feature: citations within bibliography
entries are a Bib(La)Tex only feature, they may disappear as CSL/JSON takes
over.
J
On Monday, February 20, 2023 at 3:01:35 AM UTC Bernardo C. D. A.
Vasconcelos wrote:
> Hello everyone, I hope you are all doing well.
> Basically, this is a case of using the multi bib lua filter
> <https://github.com/pandoc-ext/multibib> with other citations within the
> bibliography. I was wondering if this could be pulled off. For context, one
> of the bibliography files is actually a glossary that could contain other
> citations in the `note` field of the BibTeX entry. Here is a MWE
> <https://www.dropbox.com/s/diiwwjds8kha214/Multibib.zip?dl=1> to
> illustrate what looks like in practice. What do you think?
> Thanks,
> Bernardo
>
--
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/8719e317-4d02-4206-8f84-e6c394b32946n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 3092 bytes --]
next prev parent reply other threads:[~2023-02-23 14:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-20 3:01 Bernardo C. D. A. Vasconcelos
[not found] ` <473da17f-5a82-4d44-9b83-eb1cf35d43e6n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-02-23 14:40 ` Julien Dutant [this message]
[not found] ` <8719e317-4d02-4206-8f84-e6c394b32946n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-03-01 14:15 ` Bernardo C. D. A. Vasconcelos
[not found] ` <2c4287ce-ddf0-40b0-94ac-5d22ab3d5764n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-03-01 15:41 ` Julien Dutant
[not found] ` <edf2de69-c140-4c34-b549-68ee22910146n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-03-01 17:53 ` Bernardo C. D. A. Vasconcelos
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=8719e317-4d02-4206-8f84-e6c394b32946n@googlegroups.com \
--to=julien.dutant-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).