public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John Carter Wood <johannes.c.holz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Citation problems, pandoc-citeproc?
Date: Mon, 28 Oct 2019 12:36:00 -0700 (PDT)	[thread overview]
Message-ID: <ca929a75-92e6-40c8-9c90-b670adc5a2f4@googlegroups.com> (raw)
In-Reply-To: <m2tv7s69e2.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>


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

Many thanks for your reply. I have looked back through the documentation 
and found the relevant section, which I seem to have overlooked.

I was convinced it had once been different, but as you say, looking back I 
see that it wasn't. Sorry, my error. 

I have done some experimentation, and it seems that within a *footnote* 
(so, using ^[text]), adding a period between references is not a problem. I 
*think* that when I was first learning to use pandoc/markdown (about two 
years ago), I ran into the problem that citations within footnotes weren't 
cooperating very well with those simply in brackets with regard to 
recognising where "ibid" would be appropriate. At least I recall such 
problems. 

As a result I had -- through whatever method -- discovered the method that 
I described above and stuck with it. Now that I'm updating my setup to a 
new machine I discovered that it didn't work any more. 

Although it is curious that was working for me for a while. 

So: using the explicit footnote format would be the right way to add 
multiple references in sentences (so separated by periods) in a note? This 
is common in the humanities. 

I suppose the best advice is "read the manual". :-)

Thanks again for your help! Much appreciated.  


On Monday, October 28, 2019 at 6:57:25 PM UTC+1, John MacFarlane wrote:
>
>
> I'm not sure why it would have worked with an earlier version. 
> However, the documentation specifies that citations in a citation 
> group need to be separated by semicolons. 
>
> So [@item1; see also @item2]. 
>
> That has been the documented behavior since the beginning. 
>
> John Carter Wood <johann...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org <javascript:>> writes: 
>
> > Hello, 
> > 
> > I've been using a Pandoc setup combined with Zotero and markdown 
> > successfully for a couple of years. But new versions of this set-up, 
> using 
> > a later version of Pandoc, have been having problems: in references 
> > (footnotes) that use periods, subsequent reference keys are not 
> converted 
> > into full references: they remain in the key format 
> > "@authorname_titleword_year". 
> > 
> > (The formatting of the quotation marks is correct: I'm in Germany.) 
> > 
> > Here is a sample markdown text. 
> > 
> > [image: Markdown_citation.jpg] 
> > 
> > 
> > 
> > Using this text works fine using pandoc 1.19.2.1/pandoc-citeproc 0.10.4 
> All 
> > references are converted. (The issue comes up in footnote 3.) 
> > 
> > [image: earlier_pandoc_version.jpg] 
> > 
> > 
> > 
> > However, using the *exact same* markdown text and .bib file, running 
> pandoc 
> > 2.2.1/pandoc-citeproc 0.14.3.1, the second citation in footnote three 
> does 
> > not convert. 
> > 
> > [image: later_pandoc_version.jpg] 
> > 
> > 
> > When I remove the period, it works. But I have several documents that 
> have 
> > this kind of citation, and I don't want to have to go back and change 
> them 
> > all. Moreover, this kind of extensive footnote with citations is normal 
> in 
> > my field (history). 
> > 
> > Am I doing something wrong? or has something changed with different 
> > versions? 
> > 
> > I appreciate any help. And I'm happy to provide any info if I've 
> forgotten 
> > something. 
> > 
> > 
> > -- 
> > 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-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:>. 
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/pandoc-discuss/ab2a282c-b491-4b78-86e4-526a37170e8c%40googlegroups.com. 
>
>

-- 
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/ca929a75-92e6-40c8-9c90-b670adc5a2f4%40googlegroups.com.

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

      parent reply	other threads:[~2019-10-28 19:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-26 19:10 John Carter Wood
     [not found] ` <ab2a282c-b491-4b78-86e4-526a37170e8c-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-10-28 17:57   ` John MacFarlane
     [not found]     ` <m2tv7s69e2.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-10-28 19:36       ` John Carter Wood [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=ca929a75-92e6-40c8-9c90-b670adc5a2f4@googlegroups.com \
    --to=johannes.c.holz-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).