From: John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: References not appearing in output file.
Date: Tue, 6 Jun 2023 13:57:59 -0700 [thread overview]
Message-ID: <67129CE3-C4F4-4D75-80F9-6A24F682DA03@gmail.com> (raw)
In-Reply-To: <fb774b5a-2945-4396-b91c-825246bb27f1n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Try adding --citeproc
> On Jun 6, 2023, at 1:53 PM, Dan Parvaz <dparvaz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> I know I must be missing something elementary -- but none of the guides I've looked at have said this was a possibility. Here's a very short piece:
>
> % Lorem
>
> # Nunc convallis, massa eu
>
> Eu, luctus quis, risus. Suspendisse [@stokoe_sign_1960] faucibus orci et nunc. Nullam vehicular fermentum risus. Fusce felis nibh, dignissim vulputate, ultrices quis, lobortis et, arcu. Duis aliquam libero non diam.
>
> Vestibulum placerat tincidunt tortor. Ut vehicula ligula quis lectus. In eget velit. Quisque vel risus. Mauris pede. Nullam ornare sapien sit amet nisl.
> Cras.
>
> # References
>
> And the equally short .bib file:
>
> @article{stokoe_sign_1960,
> title = {Sign {Language} {Structure}: {An} {Outline} of the {Visual} {Communication} {Systems} of the {American} {Deaf}},
> number = {8},
> journal = {Studies in Linguistics},
> series = {Occasional Papers},
> author = {Stokoe, William C., Jr.},
> year = {1960},
> }
>
> But running the following line...
> pandoc phon2.md --bibliography cites2.bib -s -o phon.rtf
>
> ... does not insert the citation, nor does it include it in the references. I was given to believe it was just that simple. Was I simple for believing that?
>
> Many thanks in advance,
>
> -Dan.
>
> --
> 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/fb774b5a-2945-4396-b91c-825246bb27f1n%40googlegroups.com.
next prev parent reply other threads:[~2023-06-06 20:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 20:53 Dan Parvaz
[not found] ` <fb774b5a-2945-4396-b91c-825246bb27f1n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-06-06 20:57 ` John MacFarlane [this message]
2023-06-06 20:58 ` Bastien DUMONT
2023-06-06 21:12 ` Dan Parvaz
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=67129CE3-C4F4-4D75-80F9-6A24F682DA03@gmail.com \
--to=fiddlosopher-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).