public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Matt Gass <matt.d.gass-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: MMD to PDF with chicago/turabian styled bibliography
Date: Sun, 6 Sep 2020 21:28:52 -0700 (PDT)	[thread overview]
Message-ID: <571d8037-a829-4216-aac8-6fab02b386c9n@googlegroups.com> (raw)


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

I'm having difficulty using pandoc with the latex package 
turabian-formatting <https://www.ctan.org/pkg/turabian-formatting> thesis, 
but some conflict between the pandoc latex template, `pandoc-citeproc`, 
and/or the latex package is clobbering the bibliography:

   1. If I use citeproc, the bibliography is inserted at the end of the 
   main body where the paragraph formatting is not correct for a bibliography.
   2. If I use biblatex and `\printbibliography` command rather than 
   citeproc, the bibliography never appears.
   3. I've also tried to merge the default pandoc latex template with the 
   turabian-formatting template, but citeproc seems determined to place the 
   bibliography at the end of `\mainmatter`.

What is the recommended workflow for creating correctly formatted 
bibliographies in PDF documents using pandoc?

-- 
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/571d8037-a829-4216-aac8-6fab02b386c9n%40googlegroups.com.

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

             reply	other threads:[~2020-09-07  4:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-07  4:28 Matt Gass [this message]
     [not found] ` <571d8037-a829-4216-aac8-6fab02b386c9n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-09-07 12:48   ` Denis Maier
     [not found]     ` <e88ddd38-589f-a806-45cd-b0231e00d9bb-cl+VPiYnx/1AfugRpC6u6w@public.gmane.org>
2020-09-08  2:00       ` Matt Gass
     [not found]         ` <b37916e0-f90f-4c8e-abd9-2fc51d62b992n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-09-08  9:26           ` Denis Maier
     [not found]             ` <0fbbe2cd-3637-0d17-e2dc-9f0215be900a-cl+VPiYnx/1AfugRpC6u6w@public.gmane.org>
2020-09-08 13:45               ` Matt Gass

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=571d8037-a829-4216-aac8-6fab02b386c9n@googlegroups.com \
    --to=matt.d.gass-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).