From: A A <amine.aboufirass-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: citation cross reference suffixes not appearing in resulting PDF file.
Date: Fri, 3 Mar 2023 13:48:51 +0100 [thread overview]
Message-ID: <CAMwawgMp+wQW8UwFbO8uunDjskfGvNknOCnCYkrMycWS+UBvtw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1199 bytes --]
Why won’t thecitation suffix appear in the PDF from the markdown below?
---
biblio-style: numeric
csl: mathematics-in-engineering.csl
geometry:
- margin=2cm
fontsize: 12pt
references:
- type: document
id: DevGuide
author: 'Computer Simulation Ltd.'
issued:
date-parts:
- - 2021
title: 'Development Guide'
language: en-GB
---
Hello world @DevGuide [p. 33]
\newpage
# References
I’m compiling with the following:
pandoc -s --no-check-certificate --citeproc -H deeplists.tex --from
markdown --to latex test.md -o test.tex
latexmk -pdflatex test.tex
Where deeplists.tex is similar to what is shown in this
<https://github.com/jgm/pandoc/issues/2922> issue and should have no impact
on what I’m doing here.
--
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/CAMwawgMp%2BwQW8UwFbO8uunDjskfGvNknOCnCYkrMycWS%2BUBvtw%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 4517 bytes --]
next reply other threads:[~2023-03-03 12:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-03 12:48 A A [this message]
[not found] ` <CAMwawgMp+wQW8UwFbO8uunDjskfGvNknOCnCYkrMycWS+UBvtw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-03-04 17:11 ` Ian Cornelius
[not found] ` <91da7ece-b97d-47f9-a7c3-037b14401173n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-03-05 6:14 ` A A
[not found] ` <CAMwawgNLZ+3vsrrS2d2huuDVOUbzbbujQR2F36jcrVdvhZb13g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-03-05 15:07 ` Ian Cornelius
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=CAMwawgMp+wQW8UwFbO8uunDjskfGvNknOCnCYkrMycWS+UBvtw@mail.gmail.com \
--to=amine.aboufirass-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).