From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Denis Maier <denis.maier.lists@mailbox.org>,
Aditya Mahajan <adityam@umich.edu>
Subject: Re: Citeproc
Date: Mon, 5 Oct 2020 22:04:59 +0200 [thread overview]
Message-ID: <738d7baf-27c9-1799-4f8b-d0f82fb38472@xs4all.nl> (raw)
In-Reply-To: <416e6b30-0357-73bd-fb7a-0d183585c78a@mailbox.org>
On 10/5/2020 2:55 PM, Denis Maier wrote:
> Am 05.10.2020 um 02:47 schrieb Aditya Mahajan:
>>> 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
> Thanks for adding this.
>>
>>> 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. [...]
>>
>> Note that this scheme has a few drawbacks: [...] But I do agree that
>> it will provide us with the ability to use the large number CSL styles.
> Thanks for outlining what would be needed.
>> 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.
> Yeah, a Lua citeproc would be the best way to go. I contemplated some
> time ago doing this as a learning project, but I have serious doubts I'd
> be able to actually produce something usable by others. There was one
> being developped, but a computer hazard destroyed it somewhere along the
> way Besides, the person who did it told me Lua has somd shortcomings
> that make it a suboptimal tool for this task. But I can't really tell...
if it's an xml spec then using lua makes not that much sense (no gain)
.. just process the xml
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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 20:04 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 ` Citeproc Aditya Mahajan
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 ` Hans Hagen [this message]
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=738d7baf-27c9-1799-4f8b-d0f82fb38472@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=adityam@umich.edu \
--cc=denis.maier.lists@mailbox.org \
--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).