From: <denis.maier-FfwAq0itz3ofv37vnLkPlQ@public.gmane.org>
To: <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: AW: Formatting of "ibid" in v2.11.x
Date: Sun, 15 Nov 2020 16:36:35 +0000 [thread overview]
Message-ID: <6fbe9e68e26342fda7586938e5139882@ub.unibe.ch> (raw)
In-Reply-To: <91253106-0a3e-4139-ab0e-2dbbed3f7been-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Yes, I also think adding a new mode would be a good idea. But I wouldn't want the current syntax to change in backwards incompatible ways, and adding more symbols that are not super evident feels a bit odd. I like the proposal to use classes for this though as that would be extensible.
________________________________________
Von: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> im Auftrag von jcr <ffi.appdev-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Gesendet: Sonntag, 15. November 2020 13:06:50
An: pandoc-discuss
Betreff: Re: Formatting of "ibid" in v2.11.x
This thread helped me to realize that pandoc doesn't have the kind of citations that I use in narrative footnotes. Often I could get what I want, but not always. What I really need in footnotes is the equivalent of a BibLaTeX \cite{}. I don't want AuthorInText, I just want InText. Like Joshua, I don't want to force the author name to be included in the citation. I realize that I can often achieve this by using prefixes and suffixes on a citation instead of making a footnote, but this won't work in all cases. Specifically, it doesn't allow the footnote to have two or more paragraphs. I've also had trouble writing footnotes with citations in multiple sentences: perhaps there's a workaround, but it seemed that there always had to be a semicolon separating citations.
So if both AuthorInText and InText citations are needed, what syntax could be used? One idea would be to take @smith04 as an in-text citation, +@smith04 as an author-in-text citation, and -@smith04 as an authorless in.-text citation. That seems logical to me, but has the disadvantage of changing the meaning of @smith04. Another option would be to use attributes or classes to specify citation types, like [@smith04]{.intext}.
On Wednesday, November 11, 2020 at 9:12:47 PM UTC+1 John MacFarlane wrote:
Joshua <joshu...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> Thanks for such a helpful, prompt reply. I've loved pandoc for a long time,
> but I had no idea the support was this good. You have a superb project here.
>
> After consulting the style guides, it looks like pandoc is keeping with the
> times and I am not. I'm still a bit confused about your response to the
> second issue, though. Suppose I type:
> Blah.^[@AugustineCityGod2008, 72.] Blah.^[Compare to the competing claim in
> @AugustineCityGod2008, 46.]
>
> This then renders:
> [1] Augustine, *City of God*, 72.
> [2] Compare to the rather different claim in Augustine, ibid, 46.
>
> Whereas the behavior I intend:
> [1] Augustine, *City of God*, 72.
> [2] Compare to the rather different claim in ibid, 46.
>
> This is the behavior I achieved before upgrading pandoc, but I do not
> understand the directives I need to give in order to achieve it now. Or
> maybe I simply cannot.
It's usually better just to use inline references; in a note
style they will be automatically converted to notes.
So do this:
Blah [@AugustineCityGod2008, 72]. Blah [Compare to the competing claim in
@AugustineCityGod2008, 46].
This uses regular citations, not author-in-text citations.
Not only will it give you the ibid you want, it will also allow
you to switch easily to an author-date citation style if you
wish.
Pandoc will automatically create the notes and rearrange spacing
and punctuation.
--
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-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org<mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>.
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/91253106-0a3e-4139-ab0e-2dbbed3f7been%40googlegroups.com<https://groups.google.com/d/msgid/pandoc-discuss/91253106-0a3e-4139-ab0e-2dbbed3f7been%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/6fbe9e68e26342fda7586938e5139882%40ub.unibe.ch.
next prev parent reply other threads:[~2020-11-15 16:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-11 16:15 Joshua
[not found] ` <965d161d-db68-439f-acab-c035c89ec0dfn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-11-11 18:01 ` John MacFarlane
[not found] ` <m2wnyrlqn0.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2020-11-11 19:02 ` Joshua
2020-11-11 19:37 ` Denis Maier
[not found] ` <557267e8-3f30-45aa-8b58-50fc6ba71531n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-11-11 19:37 ` 'Denis Maier' via pandoc-discuss
2020-11-11 19:41 ` Denis Maier
[not found] ` <5fac3d7d.1c69fb81.8ceda.81c8SMTPIN_ADDED_MISSING-AJJneosEFeET7FrJB5NJYwC/G2K4zDHf@public.gmane.org>
2020-11-11 19:41 ` 'Denis Maier' via pandoc-discuss
[not found] ` <5fac3e55.1c69fb81.f7f71.1ee3SMTPIN_ADDED_MISSING-AJJneosEFeET7FrJB5NJYwC/G2K4zDHf@public.gmane.org>
2020-11-11 19:57 ` Joshua
2020-11-11 20:12 ` John MacFarlane
[not found] ` <m27dqrirf5.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2020-11-11 20:17 ` Joshua
2020-11-15 12:06 ` jcr
[not found] ` <91253106-0a3e-4139-ab0e-2dbbed3f7been-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-11-15 16:36 ` denis.maier-FfwAq0itz3ofv37vnLkPlQ [this message]
[not found] ` <6fbe9e68e26342fda7586938e5139882-FfwAq0itz3ofv37vnLkPlQ@public.gmane.org>
2020-11-15 19:12 ` AW: " denis.maier-FfwAq0itz3ofv37vnLkPlQ
2020-11-16 16:46 ` John MacFarlane
[not found] ` <CAGOSsdkBbvh4jYQbwK9+Ay3nWFEo_cZ0uFN=w6tDoG76hqQGYg@mail.gmail.com>
[not found] ` <m2k0ul82g7.fsf@MacBook-Pro.hsd1.ca.comcast.net>
[not found] ` <m2k0ul82g7.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2020-11-16 20:37 ` John MacFarlane
[not found] ` <m2ft5982dm.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2020-11-18 10:08 ` Pandoc: Suggestions for latex table generator Gabriel Nützi
[not found] ` <277ee96f-10bd-6db4-3c2f-7ee37527d68b-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-11-19 20:05 ` John MacFarlane
2020-11-19 20:14 ` John MacFarlane
[not found] ` <m2eekp3y0e.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2020-11-19 20:18 ` John MacFarlane
2020-11-22 18:13 ` John MacFarlane
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=6fbe9e68e26342fda7586938e5139882@ub.unibe.ch \
--to=denis.maier-ffwaq0itz3ofv37vnlkplq@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).