From: Jesse Rosenthal <jrosenthal-4GNroTWusrE@public.gmane.org>
To: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>,
pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Footnote with citations and multiple paragraphs using pandoc-citeproc
Date: Tue, 30 Sep 2014 16:54:29 -0400 [thread overview]
Message-ID: <87egus4ynu.fsf@jhu.edu> (raw)
In-Reply-To: <20140927041953.GA38502-bi+AKbBUZKbivNSvqvJHCtPlBySK3R6THiGdP5j34PU@public.gmane.org>
John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org> writes:
> The question is this: in footnote styles, how SHOULD a citation that
> appears inside a note be formatted? Clearly not as a footnote, but
> unfortunately beyond that the style won't give us guidance. Should
> it be a separate sentence? In parentheses? In brackets? These are
> all stylistic variations, but the style can't help us here because
> it's a note style.
Flipping through books from a number of presses with footnote styles on
my desk, the following seems to be the rule:
1. A footnote containing only the citation should be identical to an
@-citation. I.e, in a footnote style:
foo.[^1]
[^1]: [@dickens:dorrit, p. 15]
==
foo [@dickens:dorrit, p. 15]
2. A footnote containing the citation mixed in with other text should
be separated from that text by a period. So
foo. [^1]
[^1]: "Blah blah blah" [@dickens:dorrit, p. 15].
==
foo. [^1]
[^1]: "Blah blah blah." Charles Dickens, _Little Dorrit_,
ed. Stephen Wall and Helen Small (New York: Penguin,
1998), 15.
(or whatever) depending on the style.
3. Anything else should be integrated into the text without
being set off by a period.
I would propose the following heuristic for distinguishing between (2) and
(3): if the citation is followed by a period, it should be set off by a
period, as in (2); if it isn't punctuation is left to the author.
next prev parent reply other threads:[~2014-09-30 20:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-26 18:50 hgv
[not found] ` <cf5b21a4-0495-47bc-872f-091626a4ef0a-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2014-09-26 20:09 ` Andrew Dunning
[not found] ` <3FDE0D22-3F5C-4471-9451-CD0FA4E96531-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-09-26 21:03 ` John MacFarlane
[not found] ` <20140926210311.GB20437-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
2014-09-26 21:43 ` hgv
[not found] ` <246e0391-eb53-40d3-bb59-dc1c97d94ebb-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2014-09-27 4:19 ` John MacFarlane
[not found] ` <20140927041953.GA38502-bi+AKbBUZKbivNSvqvJHCtPlBySK3R6THiGdP5j34PU@public.gmane.org>
2014-09-27 8:47 ` nickbart1980-Re5JQEeQqe8AvxtiuMwx3w
2014-09-30 12:22 ` hgv
2014-09-30 20:54 ` Jesse Rosenthal [this message]
2014-10-01 0:14 ` Bruce D'Arcus
[not found] ` <945be504-882b-46e8-b653-e373d579008b-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2014-10-01 1:55 ` Frank Bennett
[not found] ` <d62aab34-b6d9-4aa9-a961-0534e601987b-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2014-10-01 20:11 ` Bruce D'Arcus
[not found] ` <fe3c108a-8702-42f7-9309-fe3386f40b7b-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-02-01 20:44 ` hgv
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=87egus4ynu.fsf@jhu.edu \
--to=jrosenthal-4gnrotwusre@public.gmane.org \
--cc=jgm-TVLZxgkOlNX2fBVCVOL8/A@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).