From: John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: --biblatex and suppress-bibliography
Date: Thu, 12 Oct 2023 09:56:49 -0700 [thread overview]
Message-ID: <7748A3B8-2AFB-413B-9E84-BA643C873CB3@gmail.com> (raw)
In-Reply-To: <66ba712f-f7bd-4ed8-87c0-a768d3c50fa6n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
That's true; this only affects use with citeproc. I'm not even sure how to make this happen with biblatex.
> On Oct 12, 2023, at 1:01 AM, Bruno Grenet <bruno.grenet-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> Dear all,
>
> It seems to me that the metadata field suppress-bibliography has no effect when using the command-line option --biblatex. A minimal working example:
>
> ---
> references:
> - author:
> - family: Cooley
> given: James W.
> - family: Tukey
> given: John W.
> container-title: Mathematics of computation
> doi: 10.1090/S0025-5718-1965-0178586-1
> id: CooleyTukey1965
> issue: 90
> issued: 1965
> page: 297-301
> title: An Algorithm for the Machine Calculation of Complex Fourier Series
> type: article-journal
> volume: 19
> ---
> This is a citation [@CooleyTukey1965].
>
> Then I can use either
>
> pandoc MWE.md -s --biblatex -o MWE.tex
>
> or
>
> pandoc MWE.md -s --metadata=suppress-bibliography --biblatex -o MWE.tex
>
> and I get in both case the same result, that is the document is finishing with a \printbibliography.
>
> Am I missing something? Thanks!
>
>
> --
> 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/66ba712f-f7bd-4ed8-87c0-a768d3c50fa6n%40googlegroups.com.
next prev parent reply other threads:[~2023-10-12 16:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 8:01 Bruno Grenet
[not found] ` <66ba712f-f7bd-4ed8-87c0-a768d3c50fa6n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-10-12 16:56 ` John MacFarlane [this message]
[not found] ` <7748A3B8-2AFB-413B-9E84-BA643C873CB3-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-10-12 18:20 ` Bruno Grenet
[not found] ` <8be5ad50-3e06-41ff-9f8b-0f57b8b46c54n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-10-12 18:31 ` John MacFarlane
[not found] ` <DF2A033B-C3DD-4804-8EF0-48D528C3BFC9-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-10-12 18:55 ` Bruno Grenet
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=7748A3B8-2AFB-413B-9E84-BA643C873CB3@gmail.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).