From: Colin McLear <mclearc-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: citeproc error
Date: Tue, 28 Nov 2023 04:36:36 -0800 (PST) [thread overview]
Message-ID: <b917dd06-8cf6-4609-906c-8ce27e889e59n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1264 bytes --]
I'm having a problem where I cannot build PDFs with citations. I keep
getting this error or similar:
---
-*- mode: compilation; default-directory:
"~/Work/projects/Book-Projects/kant-rationality-book/" -*-
Compilation started at Tue Nov 28 07:26:28 ...
Error producing PDF.
! Undefined control sequence.
<argument> ...and a “soul”. See, e.g., (\citeproc
{ref-allison1996}{Allison
...
l.418 ...ing many of these texts to my attention.}
make: *** [build/pdf/kant-rationality-book.pdf] Error 43
Compilation exited abnormally with code 2 at Tue Nov 28 07:26:35
---
I can compile a pdf without citations with no issues. I have pandoc version
3.1.9. I'm on an M2 macOS Sonoma.
I don't think this is a bug, but I also don't know why it wouldn't render
citations.
--
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/b917dd06-8cf6-4609-906c-8ce27e889e59n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1703 bytes --]
next reply other threads:[~2023-11-28 12:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 12:36 Colin McLear [this message]
[not found] ` <b917dd06-8cf6-4609-906c-8ce27e889e59n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-11-28 17:00 ` John MacFarlane
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=b917dd06-8cf6-4609-906c-8ce27e889e59n@googlegroups.com \
--to=mclearc-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).