ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: denis.maier@unibe.ch, ntg-context@ntg.nl
Cc: Hans Hagen <j.hagen@xs4all.nl>
Subject: Re: Citeproc-lua
Date: Sat, 7 May 2022 01:15:23 +0200	[thread overview]
Message-ID: <eaf7e57f-a189-992d-cd61-803bc11a91dc@xs4all.nl> (raw)
In-Reply-To: <99eb81340ebb44a2a6221bde7ac4da38@unibe.ch>

On 5/7/2022 12:33 AM, denis.maier@unibe.ch wrote:
>> -----Ursprüngliche Nachricht-----
>> Von: ntg-context <ntg-context-bounces@ntg.nl> Im Auftrag von Hans Hagen
>> via ntg-context
>> Gesendet: Freitag, 6. Mai 2022 23:45
>> An: Denis Maier via ntg-context <ntg-context@ntg.nl>
>> Cc: Hans Hagen <j.hagen@xs4all.nl>
>> Betreff: Re: [NTG-context] Citeproc-lua
>>
>> [...]
>>
>> For the record: i don't think you should write something to the tuc file that
>> doesn't come from context itself because you can mess it up (also
>> performaance wise).
> 
> Really? But what about that stuff? Anyway, even better if the data coming from context itself can be used.

A bibliography is just about (cross) referencing data. If that data 
comes from elsewhere it can best kept indepdendent. One can of course 
store some reference but why the data if it is not used in some special 
way.

> Of course you could have another file (just like a bib file
>> is independent). One problem could be that you need to make some extra
>> installation to make it work as we're not going to add all kind of code to the
>> distribution (we tend to go smaller) and someone needs to maintain that
>> moduie then because users depend in it working.
>>
>> Did you look into what pandoc provides? It might be easier to take that
>> output and include it. Some kind of html? That's easy to render.
> 
> Pandoc can output context as well, so we can just take that.

Sure, but some parseble format might be better if one wants control over 
rendering. Basically we're talking about some pseudo formatted 
bibliography entry with some unique tag as reference.

> Using the whole bibliography might give problems with regards to disambiguation.

In what sense? Aren't the 'tags' or id's unique? Anyway, one can

- let \cite write some refe to soem file
- that file gets pandoc'd to a bibliography list
- that then gets included

if that list is in some parsable format (like html width classes) we can 
easily pick up info (if needed) and do nmore

> So, that would work a bit like Aditya's filter module: https://github.com/adityam/filter
> Right?

sort of

> Another option would be to just use pandoc's citeproc directly, as described here: https://github.com/jgm/citeproc/blob/master/man/citeproc.1.md
> 
> We'd have to pass a list of citations as a JSON object to that citeproc and use the results.
> The results will include citations as well as the bibliography (all as JSON, content can be HTML formatted).
we can handle json indeed, so hwo does such a json look like? can you 
make an example?

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
___________________________________________________________________________________

  reply	other threads:[~2022-05-06 23:15 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     ` Citeproc-lua Aditya Mahajan via ntg-context
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         ` Hans Hagen via ntg-context [this message]
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=eaf7e57f-a189-992d-cd61-803bc11a91dc@xs4all.nl \
    --to=ntg-context@ntg.nl \
    --cc=denis.maier@unibe.ch \
    --cc=j.hagen@xs4all.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).