From: Henning Hraban Ramm <texml@fiee.net>
To: ntg-context@ntg.nl
Subject: [NTG-context] Re: bibliography questions
Date: Wed, 4 Oct 2023 09:00:22 +0200 [thread overview]
Message-ID: <73bcd036-f32b-b755-53f1-b12e60edcac1@fiee.net> (raw)
In-Reply-To: <09005n33-528n-359p-947s-ppr3r53r97sp@hzvpu.rqh>
Am 03.10.23 um 23:08 schrieb Aditya Mahajan:
> On Tue, 3 Oct 2023, Henning Hraban Ramm wrote:
>
>> For my ConTeXt book, I thought it would make sense, and I would jump through
>> some hoops just to use the system, but
>> – most sources that I want to list are never quoted (method=dataset)
>> – I would need to define my own rendering, e.g. don’t like the handling of
>> names
>> – I need additional fields (custom rendering again)
>> – if I refer to sources, I want a URL or file path in a footnote (custom cite wrapper macro)
>
> When I have to write your own rendering, I find it more convenient to use XML/JSON (or even a lua table) as a starting format.
I don’t understand how a custom rendering relates to the input database?
My bib database is already complete, and I find the format much more
comfortable to write than XML.
Hraban
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2023-10-04 7:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 11:13 [NTG-context] " Henning Hraban Ramm
2023-10-03 0:02 ` [NTG-context] " Alan Braslau via ntg-context
2023-10-03 14:32 ` Henning Hraban Ramm
2023-10-03 21:08 ` Aditya Mahajan
2023-10-04 7:00 ` Henning Hraban Ramm [this message]
2023-10-05 7:05 Rik Kabel
2023-10-05 7:11 ` Rik Kabel
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=73bcd036-f32b-b755-53f1-b12e60edcac1@fiee.net \
--to=texml@fiee.net \
--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).