public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: LaTeX and citation inside a footnote
Date: Sun, 11 Jun 2017 21:41:22 +0200	[thread overview]
Message-ID: <20170611194122.GB14604@Johns-MBP.home> (raw)
In-Reply-To: <977df2ef-6b75-41e9-9511-48a746184a45-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

It sounds too special-purpose to think about modifying
pandoc.  Remember, the primary purpose of the citation
syntax is to support pandoc-citeproc, not to generate
LaTeX/bibtex citations.  BibLaTeX is very expressive, and
there's no way we'll ever match that.  But maybe you could
explain better the difference between \cite and \autocite in
this context?

+++ Lyndon Drake [Jun 11 17 06:26 ]:
>   Yes, that would work, but what I need is \cite{} as the first one,
>   followed by \autocite{}. What Pandoc gives is \textcite{}… \autocite{}.
>   That produces a different result in SBL (or any Chicago-based footnote)
>   BibLaTeX style. At the moment, as far as I can tell, there's no way to
>   get Pandoc to generate a \cite{} command, which is what I need.
>   For some BibLaTeX the choice between \textcite{} and \autocite{} is
>   sufficient to cover most use cases. But for the SBL style, it's very
>   difficult to write without access to at least \cite{} as well, and I'm
>   wondering whether you'd consider adding some syntax to allow \cite{} to
>   be called.
>   Does that make more sense?
>   On Sunday, June 11, 2017 at 9:27:11 AM UTC+1, John MacFarlane wrote:
>
>     I'm not sure I follow exactly.  But if you want two
>     \autocites, rather than a \textcite and an \autocite,
>     can't you just do this?
>         ^[[@Gross:1997]. Fensham blah blah [@Fensham:1982]]
>     +++ Lyndon Drake [Jun 10 17 01:03 ]:
>     >   Hi,
>     >   I realised that the question of \cite has come up before, but I
>     have a
>     >   case that's quite common in my field and wondered what the best
>     >   solution is. When writing with the SBL style guide, it's not
>     uncommon
>     >   to want to generate a footnote like this one:
>     >   5. Carl D. Gross, “Is There Any Interest in Nehemiah 5,” Scand.
>     >   J.OldTestam. 11 (1997): 270–78, doi:10.1080/ 09018329708585120.
>     Fensham
>     >   translates as “Everyone of you imposes a burden (loan) on his
>     brother,”
>     >   but gives no philological commentary on this, perhaps because he
>     reads
>     >   the whole episode as being primarily about slavery rather than
>     debt
>     >   (Fensham, The Books of Ezra and Nehemiah, 192).
>     >   Because footnotes are so common, this approach to summarising a
>     >   parenthetical issue is also very common. In author-date citation
>     styles
>     >   (which I used to use for other work) you'd get the citation in
>     the main
>     >   paragraph body, and then a separate footnote, and hence no
>     problems.
>     >   In LaTeX, the desired result can be generated by
>     >   \cite{Gross:1997}. Fensham blah blah
>     \autocite[192]{Fensham1982}.
>     >   I don't know how to get the same effect from Pandoc. The problem
>     is
>     >   that the following:
>     >   ^[@Gross:1997. Fensham blah blah [@Fensham:1982]]
>     >   turns the first into \textcite{}, which in the SBL style is set
>     as:
>     >   Gross ("Is there…" …)
>     >   Which is what \textcite is supposed to do. \autocite{} produces
>     instead
>     >   (Gross, "Is there…" …), which also seems the best option — it
>     parallels
>     >   what one wants with \autocite in a non-footnote paragraph.
>     >   Is there any chance of altering the syntax slightly to allow
>     other
>     >   options in the conversion to LaTeX? What I'd really like is the
>     ability
>     >   to generate \cite{}, which would also be useful in other cases
>     (e.g.
>     >   one is writing a sentence in footnote text such as "For a
>     bibliography,
>     >   see Fensham, blah bah, 1982." where one does not want
>     \parencite{}).
>     >   Or if anyone can suggest a workaround I'm open to ideas.
>     >   Best,
>     >   Lyndon
>     >
>     >   --
>     >   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][1]pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>     >   To post to this group, send email to
>     >   [2][2]pandoc-...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>     >   To view this discussion on the web visit
>     >   [3][3]https://groups.google.com/d/msgid/pandoc-discuss/
>     9bbfc142-2a0a-4f4d-
>     >   b79f-0a6a103e654e%[4]40googlegroups.com.
>     >   For more options, visit [4][5]https://groups.google.com/
>     d/optout.
>     >
>     >References
>     >
>     >   1. mailto:[6]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>     >   2. mailto:[7]pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>     >   3. [8]https://groups.google.com/d/msgid/pandoc-discuss/9bbfc142-
>     2a0a-4f4d-b79f-0a6a103e654e-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=
>     email&utm_source=footer
>     >   4. [9]https://groups.google.com/d/optout
>
>   --
>   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 [10]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>   To post to this group, send email to
>   [11]pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>   To view this discussion on the web visit
>   [12]https://groups.google.com/d/msgid/pandoc-discuss/977df2ef-6b75-41e9
>   -9511-48a746184a45%40googlegroups.com.
>   For more options, visit [13]https://groups.google.com/d/optout.
>
>References
>
>   1. javascript:/
>   2. javascript:/
>   3. https://groups.google.com/d/msgid/pandoc-discuss/9bbfc142-2a0a-4f4d-
>   4. http://40googlegroups.com/
>   5. https://groups.google.com/d/optout
>   6. javascript:/
>   7. javascript:/
>   8. https://groups.google.com/d/msgid/pandoc-discuss/9bbfc142-2a0a-4f4d-b79f-0a6a103e654e-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
>   9. https://groups.google.com/d/optout
>  10. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>  11. mailto:pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>  12. https://groups.google.com/d/msgid/pandoc-discuss/977df2ef-6b75-41e9-9511-48a746184a45-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
>  13. https://groups.google.com/d/optout

-- 
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/20170611194122.GB14604%40Johns-MBP.home.
For more options, visit https://groups.google.com/d/optout.


      parent reply	other threads:[~2017-06-11 19:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-10  8:03 Lyndon Drake
     [not found] ` <9bbfc142-2a0a-4f4d-b79f-0a6a103e654e-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-06-11  8:26   ` John MacFarlane
     [not found]     ` <20170611082654.GA95963-l/d5Ua9yGnxXsXJlQylH7w@public.gmane.org>
2017-06-11 13:26       ` Lyndon Drake
     [not found]         ` <977df2ef-6b75-41e9-9511-48a746184a45-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-06-11 19:41           ` John MacFarlane [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=20170611194122.GB14604@Johns-MBP.home \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@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).