From: nickbart1980-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Footnote with citations and multiple paragraphs using pandoc-citeproc
Date: Sat, 27 Sep 2014 01:47:18 -0700 (PDT) [thread overview]
Message-ID: <2d62aa21-e80c-4169-967e-100f6eb6db26@googlegroups.com> (raw)
In-Reply-To: <20140927041953.GA38502-bi+AKbBUZKbivNSvqvJHCtPlBySK3R6THiGdP5j34PU@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 2339 bytes --]
> A larger solution might be in giving up the ability of pandoc-citeproc to
produce either inline citations or note citations.
I, for one, strongly oppose this idea.
As to some possible workaround for "multiparagraph footnotes": If newlines
instead of paragraph breaks are acceptable, then inserting
space-space-return in the middle of a citation a the spot when you want a
linebreak to appear seems to do the trick, e.g.,
````
Foo [see @item1.
See also @item2].
````
(A backslash followed by a return did not work however when I tried it.)
On Saturday, September 27, 2014 4:20:07 AM UTC, John MacFarlane wrote:
>
> +++ hgv [Sep 26 14 14:43 ]:
> >A larger solution might be in giving up the ability of pandoc-citeproc to
> >produce either inline citations or note citations. I understand how
> useful
> >this is, but if it doesn't actually work for one side of it (notes), I
> >don't see the value. Of course, I only work with Chicago
> note-bibliography,
> >which is where my bias comes from. But it seems to be designed primarily
> >for those who work with Chicago author-date (and other inline styles),
> not
> >really those who use both extensively. But as I'm sure this would entail
> a
> >fair amount of work to just get back to where it is now, I understand the
> >downsides.
>
> 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.
>
> If this question could be answered, perhaps progress could be made.
>
>
--
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 post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/2d62aa21-e80c-4169-967e-100f6eb6db26%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #2: Type: text/html, Size: 3010 bytes --]
next prev parent reply other threads:[~2014-09-27 8:47 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 [this message]
2014-09-30 12:22 ` hgv
2014-09-30 20:54 ` Jesse Rosenthal
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=2d62aa21-e80c-4169-967e-100f6eb6db26@googlegroups.com \
--to=nickbart1980-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).