public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: 'Stefan Stiene' via pandoc-discuss
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: chapter wise bibliography in docx
Date: Thu, 4 Jan 2018 08:23:19 -0800	[thread overview]
Message-ID: <20180104162319.GB15709@Johns-MacBook-Pro.local> (raw)
In-Reply-To: <2190ca6a-6085-4a46-a5aa-48e2b6cf3d10-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

Pandoc-citeproc doesn't support multiple bibliographies,
sorry.

You could probably work around this by processing the
parts separately. E.g. suppose your chapters are
chap1.tex, chapt2.tex, etc.

    for x in 1 2 3 4; do \
      pandoc chap$x.tex -F pandoc-citeproc \
      --bibliography references.bib -M link-citations \
      --csl ieee.csl -t markdown-citations -o chap$x.md ; \
    done

This gives you chap1.md, chap2.md, etc., with the
bibliographies in Markdown format at the end of each
chapter.  Then stitch these together:

    pandoc chap*.md -o book.docx

+++ 'Stefan Stiene' via pandoc-discuss [Jan 04 18 01:12 ]:
>   Hi,
>   I have a latex file with a bibliography after each chapter. I want to
>   convert this into a docx file but all references go into one
>   bibliography at the end of the document. Is there any chance to
>   generate multiple bibliography sections in docx?
>   I use pandoc 2.0.6 and the pandoc cmd I use is:
>   pandoc -s word_bibtex.tex -o pandoc.docx --metadata
>   bibliography=references.bib --filter pandoc-citeproc --metadata
>   link-citations --csl ieee.csl
>   In latex I use biblatex like described here:
>   https://tex.stackexchange.com/questions/333617/how-to-use-chapterbib-pa
>   ckage-syntax but I'm not bound to this. If any other solution
>   (multibib, chapterbib,...) works with pandoc I can switch.
>   Thanks and Regards
>   Stefan
>
>   --
>   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]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>   To post to this group, send email to
>   [2]pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>   To view this discussion on the web visit
>   [3]https://groups.google.com/d/msgid/pandoc-discuss/2190ca6a-6085-4a46-
>   a5aa-48e2b6cf3d10%40googlegroups.com.
>   For more options, visit [4]https://groups.google.com/d/optout.
>
>References
>
>   1. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>   2. mailto:pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>   3. https://groups.google.com/d/msgid/pandoc-discuss/2190ca6a-6085-4a46-a5aa-48e2b6cf3d10-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
>   4. https://groups.google.com/d/optout


  parent reply	other threads:[~2018-01-04 16:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-04  9:12 'Stefan Stiene' via pandoc-discuss
     [not found] ` <2190ca6a-6085-4a46-a5aa-48e2b6cf3d10-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2018-01-04 13:13   ` James Austin
     [not found]     ` <ff8d25cf-7045-6b08-ce12-7905d1a9ee0c-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-01-04 14:39       ` 'Stefan Stiene' via pandoc-discuss
2018-01-04 16:23   ` John MacFarlane [this message]
2018-01-04 20:17   ` Albert Krewinkel
     [not found]     ` <87fu7lcrak.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2018-01-04 20:19       ` Albert Krewinkel
     [not found]         ` <877esxcr7o.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2018-01-09  7:23           ` 'Stefan Stiene' via pandoc-discuss
     [not found]             ` <5ce48365-f66a-4caa-bbf0-cb8e825e01c7-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2018-01-09  8:47               ` albert.krewinkel-stqabkCVF6SGlKaCpJGLJw
2020-03-15 17:37   ` David Denton

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=20180104162319.GB15709@Johns-MacBook-Pro.local \
    --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).