ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan via ntg-context <ntg-context@ntg.nl>
To: Denis Maier via ntg-context <ntg-context@ntg.nl>
Cc: Aditya Mahajan <adityam@umich.edu>
Subject: Re: Citeproc-lua
Date: Fri, 6 May 2022 17:09:49 -0400 (EDT)	[thread overview]
Message-ID: <nycvar.YAK.7.78.908.2205061706490.213641@nqv-guvaxcnq> (raw)
In-Reply-To: <b542dfd93bd644f3bdeeec4f8efcc3c1@unibe.ch>



On Fri, 6 May 2022, Denis Maier via ntg-context wrote:

> Hi,
> thanks for your assessment. Indeed, that looks very promising.
> 
> I've now had a chance to look at this a bit more too.  Not that I understand that stuff in detail, but anyway...
> 
> I also have the impression that extending citeproc-formats.lua should be the easiest part. As an aside, I think the HTML is in there because that is needed for the test suite, but for ConTeXt we should be able to copy the LaTeX mapping and tweak a few things here and there.
>
> The LaTeX package is hard to understand, at least if you're not used to the "new" latex3 programming syntax and style. I also can only guess what that stuff does. But as you say this is rather isolated from the citeproc processing, so I guess the main task would be to come up with an equivalent ConTeXt module that writes the citations to the tuc file, calls the citeproc engine, and uses the results for the output. Right? (I.e., AFAICS, everything that lives under https://github.com/zepinglee/citeproc-lua/tree/main/citeproc should pretty much just work, while https://github.com/zepinglee/citeproc-lua/tree/main/latex must be adapted.)

Does citeproc-lua/biblatex support using CSL files (https://citationstyles.org/). IMO, that is currently the biggest limitation of the context bib module that only a few citation styles are supported. Developing a new citation style is relatively easy but a lot of work. Being able to use CSL will simplify things (from the point of view of the user) a lot.

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
___________________________________________________________________________________

  reply	other threads:[~2022-05-06 21:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-03 20:00 Citeproc-lua Denis Maier via ntg-context
2022-05-06 12:57 ` Citeproc-lua Taco Hoekwater via ntg-context
2022-05-06 13:20   ` Citeproc-lua Hans Hagen via ntg-context
2022-05-06 21:02   ` Citeproc-lua Denis Maier via ntg-context
2022-05-06 21:09     ` Aditya Mahajan via ntg-context [this message]
2022-05-06 21:26       ` Citeproc-lua Hans Hagen via ntg-context
2022-05-06 21:44     ` Citeproc-lua Hans Hagen via ntg-context
2022-05-06 22:04       ` Citeproc-lua Denis Maier via ntg-context
2022-05-06 22:33       ` Citeproc-lua Denis Maier via ntg-context
2022-05-06 23:15         ` Citeproc-lua Hans Hagen via ntg-context
2022-05-07 10:22           ` Citeproc-lua Denis Maier via ntg-context
2022-05-06 22:56       ` Citeproc-lua Rik Kabel via ntg-context

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.2205061706490.213641@nqv-guvaxcnq \
    --to=ntg-context@ntg.nl \
    --cc=adityam@umich.edu \
    /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).