From: "'Mike' via pandoc-discuss" <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Use pandoc-citeproc to convert isi to JSON to .wos?
Date: Fri, 16 Aug 2019 08:40:36 -0700 (PDT) [thread overview]
Message-ID: <6dfd9056-1a64-4e1e-a210-f33a5ebe7480@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 905 bytes --]
I'm trying to figure out if and, if possible, how to use pandoc-proc to
convert .ris files to .isi (or .wos) format using JSON or YAML as an
intermediate form. ("Why would I want to do this?", you ask. Well, I've
got a pipeline for processing .isi files to generate a custom BiBTeX format
and pdf file name.).
I'm using a Ubuntu 18.04 machine running pandoc-citeproc 0.14.4
If not, is there any easy way to do this. I find lots of isi to <whatever>
but nothing in the other direction.
--
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 view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/6dfd9056-1a64-4e1e-a210-f33a5ebe7480%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1339 bytes --]
next reply other threads:[~2019-08-16 15:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-16 15:40 'Mike' via pandoc-discuss [this message]
[not found] ` <6dfd9056-1a64-4e1e-a210-f33a5ebe7480-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-08-16 16:47 ` John MacFarlane
[not found] ` <m2d0h5kqgf.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-08-16 18:29 ` 'Mike' 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=6dfd9056-1a64-4e1e-a210-f33a5ebe7480@googlegroups.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).