public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: per.review-cl+VPiYnx/1AfugRpC6u6w@public.gmane.org,
	pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Pandoc doesn't define references in PDF output with --biblatex (or --natbib)
Date: Wed, 13 Jun 2018 10:28:12 -0700	[thread overview]
Message-ID: <m2fu1qzjdf.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <20180612214644.GB8444-cl+VPiYnx/1AfugRpC6u6w@public.gmane.org>


pandoc-citeproc wraps the whole bibliography in a Div
element with class "references."

This is currently just ignored by the LaTeX writer,
but you can use a lua filter to insert a custom
environment or some custom commands.

We might think about having the LaTeX writer do
something here by default.  But what?  The most
flexible thing would be inserting the whole thing
into a special environment, but then we'd need to
add something to the default template to make sure
this environment is defined.

per.review-cl+VPiYnx/1AfugRpC6u6w@public.gmane.org writes:

> John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org> [2018-06-12 18:02 +0200]:
>> Pandoc doesn't run bibtex/biber for you when producing
>> a PDF.  If you use pandoc-citeproc, you can get a nice
>> bibliography in PDF output (and maybe that's what you
>> were doing when it worked before), but if you want to use
>> native biblatex, you'll have to produce a .tex file
>> and run latex and biber yourself.
>> 
>> Note:  it's helpful to search closed issues before
>> submitting a report.  You would have found #4105,
>> #1193, #681, #2795, ...
>
> Thanks for the quick answer! I saw the explanation of the --biblatex
> option in the manual, but was so certain I could remember Pandoc doing
> this. Turns my usage of rmarkdown/knitr, which *does* handle this, had
> contaminated my memory (and led me to only look for recent issues).
>
> However, Pandoc(-citeproc)'s implementation of CSL styles still has a
> long way to go in terms of customisation and styling. If the PDF output
> has indented paragraphs, bibliography entries will be styled the same
> way. I've posted a hack to deal with this:
> https://github.com/jgm/pandoc/issues/335#issuecomment-396739093 I don't
> know what you think about including anything like in the LaTeX template?
>
> (I understand that better support for CSL attributes are not a priority,
> but I think it's a problem when something as simple a paragraph
> indentation breaks the styling.)
>
> -- 
> Per
>
> -- 
> 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/20180612214644.GB8444%40mailbox.org.
> For more options, visit https://groups.google.com/d/optout.


  parent reply	other threads:[~2018-06-13 17:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-12 14:50 per.review-cl+VPiYnx/1AfugRpC6u6w
     [not found] ` <20180612145052.GA8444-cl+VPiYnx/1AfugRpC6u6w@public.gmane.org>
2018-06-12 16:01   ` John MacFarlane
     [not found]     ` <yh480ktvq8ngco.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2018-06-12 16:05       ` John MacFarlane
2018-06-12 21:46       ` per.review-cl+VPiYnx/1AfugRpC6u6w
     [not found]         ` <20180612214644.GB8444-cl+VPiYnx/1AfugRpC6u6w@public.gmane.org>
2018-06-13 17:28           ` John MacFarlane [this message]
     [not found]             ` <m2fu1qzjdf.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2018-06-14  9:24               ` 'Nick Bart' via pandoc-discuss

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=m2fu1qzjdf.fsf@johnmacfarlane.net \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    --cc=per.review-cl+VPiYnx/1AfugRpC6u6w@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).