From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Citeproc
Date: Sun, 4 Oct 2020 20:47:47 -0400 (EDT) [thread overview]
Message-ID: <nycvar.YAK.7.78.908.2010042035150.1533@nqv-guvaxcnq> (raw)
In-Reply-To: <c6c73af3-590c-b524-d01e-df999d0513c2@mailbox.org>
> John MacFarlane, the developper of Pandoc, has released a new Citeproc
> that generates citations and bibliographies using CSL style files (CSL=
> citation style language). While it is written in Haskell and while it's
> primarily intended for use with Pandoc, it can also be used in other
> contexts. Provided with a JSON encoded list of references via stdin, it
> can produce formatted output.
The man page of the new citeproc executable, for those who are interested:
https://github.com/jgm/citeproc/blob/master/man/citeproc.1.md
> I know that ConTeXt has its own infrastructure to format bibliographies
> and citations, but, given the enormous amount of available styles in
> CSL, I nevertheless think that this could be a worthwile addition. What
> would be necessary to make such a toll usable with ConTeXt? How
> complicated would that be?
In principle, this should be trivial. Define a new command, say \citeproc[ref], which saves the values of `ref` to a lua table, and at the end of the run, write that lua table to an aux .json file, call citeproc and store output to a new file, and on the second run read from that file. This is essentially how the old bibtex used to work.
Note that this scheme has a few drawbacks: First, it needs to call an external executable, which can be slower than directly reading the bib file via lua. Second, it creates a bunch of extra auxiliary files, which is always annoying. But I do agree that it will provide us with the ability to use the large number CSL styles.
Of course, a better option will be write a CSL processor in Lua, but that is a lot of tedious (but relatively simple) task. I wonder if there is already a CSL processor written in Lua.
Aditya
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2020-10-05 0:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-04 20:58 Citeproc Denis Maier
2020-10-05 0:47 ` Aditya Mahajan [this message]
2020-10-05 12:02 ` Citeproc Hans Hagen
2020-10-05 12:41 ` Citeproc Denis Maier
2020-10-05 19:19 ` Citeproc Aditya Mahajan
2020-10-05 12:55 ` Citeproc Denis Maier
2020-10-05 20:04 ` Citeproc Hans Hagen
2020-10-05 20:26 ` Citeproc Denis Maier
2020-10-06 7:25 ` Citeproc Taco Hoekwater
2020-10-06 8:50 ` Citeproc denis.maier.lists
2020-10-07 10:01 ` Citeproc Hans Hagen
2020-10-07 11:04 ` Citeproc Denis Maier
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=nycvar.YAK.7.78.908.2010042035150.1533@nqv-guvaxcnq \
--to=adityam@umich.edu \
--cc=ntg-context@ntg.nl \
/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).