public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Dan Parvaz <dparvaz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: References not appearing in output file.
Date: Tue, 6 Jun 2023 14:12:45 -0700 (PDT)	[thread overview]
Message-ID: <9f9a415c-a469-411f-8a8c-ac12d4df0bc9n@googlegroups.com> (raw)
In-Reply-To: <ZH-d4OCzmjVTy1ie@localhost>


[-- Attachment #1.1: Type: text/plain, Size: 2827 bytes --]

D'oh! I knew someone would spot something right away! Many thanks!

On Tuesday, June 6, 2023 at 4:58:14 PM UTC-4 Bastien DUMONT wrote:

> You don't tell pandoc to use citeproc in your command (-C)!
>
> Le Tuesday 06 June 2023 à 01:53:48PM, Dan Parvaz a écrit :
> > 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 [1]pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> > To view this discussion on the web visit [2]
> https://groups.google.com/d/msgid/
> > pandoc-discuss/fb774b5a-2945-4396-b91c-825246bb27f1n%40googlegroups.com.
> > 
> > References:
> > 
> > [1] mailto:pandoc-discus...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> > [2] 
> https://groups.google.com/d/msgid/pandoc-discuss/fb774b5a-2945-4396-b91c-825246bb27f1n%40googlegroups.com?utm_medium=email&utm_source=footer
>
>

-- 
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/9f9a415c-a469-411f-8a8c-ac12d4df0bc9n%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 4629 bytes --]

      reply	other threads:[~2023-06-06 21:12 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
2023-06-06 20:58   ` Bastien DUMONT
2023-06-06 21:12     ` Dan Parvaz [this message]

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=9f9a415c-a469-411f-8a8c-ac12d4df0bc9n@googlegroups.com \
    --to=dparvaz-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).