public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: "'Nick Bart' via pandoc-discuss" <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
To: "pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org"
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Pandoc doesn't define references in PDF output with --biblatex (or --natbib)
Date: Thu, 14 Jun 2018 05:24:57 -0400	[thread overview]
Message-ID: <Qg6kaM969Hyzb8mp4AWqajN8RTCullV-EevCrKIItI4aZRBOWydJ--tFaW69q744i99DiydmIKeIvthe8iFIu7ghAjZ4STy8dyi9FAmSs1U=@protonmail.com> (raw)
In-Reply-To: <m2fu1qzjdf.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>

I have been using a Haskell filter for years now (see https://github.com/njbart/pandoc-tools/blob/master/addRefEnvItem.hs) to replace the Div element with class "references" by a LaTeX "references" environment, and to prepend "\item" to each block.

(Traditionally, both bibtex and biblatex use such itemized lists for the references section, and LaTeX itself uses this internally for "quote" and many other environments -- so using "\item" is nothing particularly unusual.)

I’m defining the LaTeX "references" environment in the template as follows:

\newenvironment{references} {\list{}{%
    \leftmargin1.5em%
    \itemindent-\leftmargin%
$if(indent)$
    \itemsep0ex%
$else$
    \itemsep\parsep%
$endif$
    \parsep0pt%
    \setlength{\topsep}{0pt}
    \setlength{\partopsep}{0pt}
    }}
    {\endlist}

I think it’d be great if the LaTeX writer could do this by default.

Note that my definition always creates a hanging indent. It might be useful if pandoc set a "hanging" (or "csl-hanging-indent") variable that could be evaluated in LaTeX (and possibly other) templates.

As to the other CSL "Whitespace" options (see http://docs.citationstyles.org/en/1.0.1/specification.html#whitespace), "line-spacing" and "entry-spacing" could be made to be set via a variable, too. I tend to think this could be made to work for "second-field-align", too, though I’m not sure at the moment how exactly the list environment would have to look like to make this somewhat table-like alignment possible.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

On June 13, 2018 5:28 PM, John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org> wrote:

> 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.
>
> --
>
> 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/m2fu1qzjdf.fsf%40johnmacfarlane.net.
>
> For more options, visit 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/Qg6kaM969Hyzb8mp4AWqajN8RTCullV-EevCrKIItI4aZRBOWydJ--tFaW69q744i99DiydmIKeIvthe8iFIu7ghAjZ4STy8dyi9FAmSs1U%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.


      parent reply	other threads:[~2018-06-14  9:24 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
     [not found]             ` <m2fu1qzjdf.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2018-06-14  9:24               ` 'Nick Bart' via pandoc-discuss [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='Qg6kaM969Hyzb8mp4AWqajN8RTCullV-EevCrKIItI4aZRBOWydJ--tFaW69q744i99DiydmIKeIvthe8iFIu7ghAjZ4STy8dyi9FAmSs1U=@protonmail.com' \
    --to=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).