From: Joseph Johnson <jj892-eicrhRFjby6OECnbzgFItQ@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Question about omitting brackets in citation format
Date: Fri, 24 Sep 2021 07:16:52 -0700 (PDT) [thread overview]
Message-ID: <4910c58b-3d87-4783-a878-cc52191475a2n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1797 bytes --]
Good morning,
First of all, I want to say thank you to John MacFarlane and to everyone
who works on Pandoc. It is a truly wonderful tool.
If you have the chance, I'd be grateful for your advice about a citation
format question. I've only just recently learned that in addition to the
format *[@citekey, pagenum]*, it is possible to omit the surrounding
brackets, thus preventing parentheses from being inserted in citations
within footnotes. If I understand correctly, following the examples in the
User's Guide, it should be possible to write something in a footnote like
"For more information, see *@citekey [pagenum],*" yielding the correct
reference in the footnote without enclosing it in parentheses.
However, whenever I attempt this, the page number remains within brackets
in the outputted file. For example, using the Chicago style and citing page
25, the result would be: "For more information, see *Author, Title (Place:
Publisher, Year) [25]*." This seems to suggest that the page number is not
actually being associated with the citation, and that it is just being
outputted verbatim.
The behavior is consistent when using different CSL stylesheets like MLA,
on both macOS and Linux, using two different versions of Pandoc. I assume
that I've misunderstood something, and would be grateful for advice.
Many thanks for your time, and all my best,
Joe
--
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/4910c58b-3d87-4783-a878-cc52191475a2n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2239 bytes --]
next reply other threads:[~2021-09-24 14:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-24 14:16 Joseph Johnson [this message]
[not found] ` <4910c58b-3d87-4783-a878-cc52191475a2n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-09-24 16:08 ` John MacFarlane
[not found] ` <m2fstu0xdk.fsf-d8241O7hbXoP5tpWdHSM3tPlBySK3R6THiGdP5j34PU@public.gmane.org>
2021-09-24 16:19 ` Bastien DUMONT
2021-09-24 16:47 ` Joseph Johnson
[not found] ` <CAGurDyAboRmdxSjnBg34vf=Gmry_oT4s7TMzKxg9qr=Y_FYOPg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2021-09-24 18:47 ` John MacFarlane
[not found] ` <m21r5d24ld.fsf-d8241O7hbXoP5tpWdHSM3tPlBySK3R6THiGdP5j34PU@public.gmane.org>
2021-09-24 20:06 ` Joseph Johnson
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=4910c58b-3d87-4783-a878-cc52191475a2n@googlegroups.com \
--to=jj892-eicrhrfjby6oecnbzgfitq@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).