[NTG-context] Citeproc-lua

denis.maier at unibe.ch denis.maier at unibe.ch
Sat May 7 12:22:34 CEST 2022


> -----Urspr√ľngliche Nachricht-----
> Von: Hans Hagen <j.hagen at xs4all.nl>
> Gesendet: Samstag, 7. Mai 2022 01:15
> An: Maier, Denis Christian (UB) <denis.maier at unibe.ch>; ntg-context at ntg.nl
> Betreff: Re: AW: [NTG-context] Citeproc-lua
> 
> On 5/7/2022 12:33 AM, denis.maier at unibe.ch wrote:
> >> -----Urspr√ľngliche Nachricht-----
> >> Von: ntg-context <ntg-context-bounces at 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 at ntg.nl>
> >> Cc: Hans Hagen <j.hagen at 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.

I think we're on the same page here. I was just talking about the info about which items have been cited, which pages, prefixes, suffixes, etc. All that stuff that is basically already there...

> 
> > 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.

I see...

> 
> > Using the whole bibliography might give problems with regards to
> disambiguation.
> 
> In what sense? Aren't the 'tags' or id's unique? 

Tags/Ids are unique, for sure. But, if you render a bibliography based on everything in the bib-file, you might end up with 
Doe 2005a
Doe 2005b
etc.
but in the end you'll remove Doe 2005b, so the whole a/b stuff isn't necessary anymore.

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

Yes, looks reasonable.

> 
> 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?

There are some examples on this page https://github.com/jgm/citeproc/blob/master/man/citeproc.1.md
Does that help or do you need to know more?

Anyway, this adds the citeproc executable as a dependency. Maybe they can make that functionality from pandoc proper.

Denis


More information about the ntg-context mailing list