From: Rik Kabel via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Rik Kabel <rik@panix.com>
Subject: Re: Citeproc-lua
Date: Fri, 6 May 2022 18:56:19 -0400 [thread overview]
Message-ID: <2389745d-9f18-a065-5f99-67894f61c133@panix.com> (raw)
In-Reply-To: <ff135397-2edb-fa2a-2f93-ab5bcbaeab6f@xs4all.nl>
[-- Attachment #1.1: Type: text/plain, Size: 1767 bytes --]
On 2022-05-06 17:44, Hans Hagen via ntg-context wrote:
> [...]
> A bit like this:
>
> - Convert the whole bibliography database to html using pandoc in the
> preferred cs rendering. That should be fast.
>
> - Use the normal context commands for referencing a citation (the cite
> part is normally easy as there is not much variation in that; if
> needed one can cheat and also pregenerate that). That's then just some
> relatively small plugin mode.
>
> - When placing the bibliography, filter the right entries from that
> html file (easy) using info that got stored in the tuc.
>
> It is also fast. The only depdency then is pandoc but that is widely
> available (irr). But I would need to see an example of that kind of
> out first. We basically treat the (formatted) bibliography as an
> external resource but in some format that we can easily parse (and if
> needed tweak).
>
> Hans
>
This is similar to my strategy today. I create a pandoc markdown file
from my ConTeXt source using a simple script and generate ConTeXt output
containing just the bibliography using pandoc. This output needs some
minor tweaks, again scripted, to do things like replace the space in
/Vol. 999/ with a non-breaking space to keep the following number on the
same line and to convert /\em/ and such to taggable macros that I define
in my environment. The result is ConText source that can be further
edited (if necessary) and inserted where needed/./ I have not extended
it to multiple bibliographies in a single document, although that
should not be difficult.
Another possibility would be for ConTeXt, under control of a flag or
setting, to generate an editable bibliography file that could be
included under control of a second flag or setting.
--
Rik
[-- Attachment #1.2: Type: text/html, Size: 2485 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 bytes --]
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2022-05-06 22:56 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 ` Citeproc-lua Hans Hagen via ntg-context
2022-05-07 10:22 ` Citeproc-lua Denis Maier via ntg-context
2022-05-06 22:56 ` Rik Kabel via ntg-context [this message]
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=2389745d-9f18-a065-5f99-67894f61c133@panix.com \
--to=ntg-context@ntg.nl \
--cc=rik@panix.com \
/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).