From: Taco Hoekwater <taco@elvenkind.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Citeproc
Date: Tue, 6 Oct 2020 09:25:50 +0200 [thread overview]
Message-ID: <F6858C82-AD3D-451F-88F3-6D16B4BE8FE2@elvenkind.com> (raw)
In-Reply-To: <a68de1ed-7ee4-756d-44c4-e17d6b3594db@mailbox.org>
> On 5 Oct 2020, at 22:26, Denis Maier <denis.maier.lists@mailbox.org> wrote:
>
> Am 05.10.2020 um 22:04 schrieb Hans Hagen:
>> if it's an xml spec then using lua makes not that much sense (no gain) .. just process the xml
> Hmm, but the XML is just a descriptive grammar of how bibliographies and citations should be rendered. As Aditya has pointed out it's quite similar to the role of bst style files for bibtex. So, a citeproc will take a style file (in xml) and apply it to the metadata (based on the items actually cited in a document).
I recall discussing this idea with Bruce D’Arcus a long time ago (somewhere in the early 00-es, maybe).
The CSL files look like XML, but really they are more like a macro processing language. Parsing and interpreting that should not be all that hard, I expect. If I had to do this, I would convert the XML <macro> tags into actual lua functions while parsing the XML. The implied processing language is quite straightforward (unlike the stack-based postfix language in bibtex bst files). I don’t have time right now, but if someone reminds me in two months or so, I might have a go at it.
Best wishes,
Taco
___________________________________________________________________________________
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-06 7:25 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 ` Citeproc Hans Hagen
2020-10-05 20:26 ` Citeproc Denis Maier
2020-10-06 7:25 ` Taco Hoekwater [this message]
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=F6858C82-AD3D-451F-88F3-6D16B4BE8FE2@elvenkind.com \
--to=taco@elvenkind.com \
--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).