public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Martin Saxer <jmsaxer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Markdown to markdown with bibliography
Date: Tue, 6 Jan 2015 20:09:49 +0100	[thread overview]
Message-ID: <C00464A3-96B6-49C2-806B-9E3D9D9DD8B9@gmail.com> (raw)
In-Reply-To: <20150106183451.GA11781-nFAEphtLEs/fysO+viCLMa55KtNWUUjk@public.gmane.org>

Thanks. I knew you had a solution for this. 

I am still not sure, though, why it has to be `-t markdown-citations` rather than `-t markdown+citations`. Do I switch the extension of to get the citations?

Anyway, problem solved.

Martin

> On 6 Jan 2015, at 19:34, John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org> wrote:
> 
> +++ Martin Saxer [Jan 05 15 23:21 ]:
>>  Is there a way to convert markdown to markdown with citeproc? Using
>>  --filter pandoc-citeproc doesn’t seem to do the trick when the output
>>  format is markdown. I’ve tried piping the output to json and converting
>>  json back to markdown, but that does not work either.
> 
> Try pandoc -t markdown-citations
> 
> (read "-" as "minus")
> 
> -- 
> You received this message because you are subscribed to a topic in the Google Groups "pandoc-discuss" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/pandoc-discuss/FceCdkZpE78/unsubscribe.
> To unsubscribe from this group and all its topics, 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/20150106183451.GA11781%40protagoras.berkeley.edu.
> 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/C00464A3-96B6-49C2-806B-9E3D9D9DD8B9%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


  parent reply	other threads:[~2015-01-06 19:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-06  7:21 Martin Saxer
     [not found] ` <97b23d32-0d2a-4196-b0c3-0c5b8d6fb4f1-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-01-06 18:34   ` John MacFarlane
     [not found]     ` <20150106183451.GA11781-nFAEphtLEs/fysO+viCLMa55KtNWUUjk@public.gmane.org>
2015-01-06 19:09       ` Martin Saxer [this message]
     [not found]         ` <C00464A3-96B6-49C2-806B-9E3D9D9DD8B9-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-01-06 20:10           ` John MacFarlane

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=C00464A3-96B6-49C2-806B-9E3D9D9DD8B9@gmail.com \
    --to=jmsaxer-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).