From: John Kitchin <firstname.lastname@example.org>
To: Jordi Inglada <email@example.com>
Cc: org-mode mailing list <firstname.lastname@example.org>
Subject: Re: org-ref and ODT export
Date: Fri, 27 Mar 2015 09:23:19 -0400 [thread overview]
Message-ID: <email@example.com> (raw)
The markdown file will not contain the bibliography. You have to use
pandoc to get that, e.g. create a bibtex file containing the citations,
and run something like
pandoc --bibliography=test.bib --filter pandoc-citeproc test.md -o
This works on a minimal kind of example for me.
Jordi Inglada writes:
> John Kitchin <firstname.lastname@example.org> wrote:
>> There is no odt support. I am not sure what the best way to do that is,
>> since I don't know how to format the citations in odt. You could try
>> exporting to markdown and then use pandoc to convert to odt. I think the
>> citations export as pandoc citations in markdown export.
> Thank you for your prompt reply.
> I tried the markdown export and, yes, the citations get exported as for instance "[@breimandecisiontrees]", but the markdown file does not contain the reference itself. I don't know markdown, so there is something I am not doing correctly.
> Best wishes,
>> Jordi Inglada writes:
>>> I am a very happy user of your org-ref package, mainly for getting bibtex entries from DOIs, organizing my bibliography and writing papers in LaTeX.
>>> I need to export a document in ODT format and it seems that the
>>> cite:xxx references do not get exported. Is this a missing feature
>>> or is there some specific configuration to set up to make it work?
>>> I have also tried using pandoc to export to Word, but the behavior is the same.
>>> Thanks for your great work.
>>> Best wishes,
>> Professor John Kitchin
>> Doherty Hall A207F
>> Department of Chemical Engineering
>> Carnegie Mellon University
>> Pittsburgh, PA 15213
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
parent reply other threads:[~2015-03-27 13:23 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <email@example.com>]
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.
Code repositories for project(s) associated with this public inbox
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 read-only IMAP folder(s) and NNTP newsgroup(s).