ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Thomas A. Schmitz via ntg-context" <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
Subject: Re: Trying to get a simple bibliography
Date: Sat, 26 Mar 2022 16:37:03 +0100	[thread overview]
Message-ID: <75AAADCC-2769-4DEA-89EE-D30B10EC08CC@uni-bonn.de> (raw)
In-Reply-To: <CAMwawgNt9nr3pM6C8_V-VavXgF-EUf+1JihdYq+JLF2esebAZA@mail.gmail.com>

Hi Amine,

The bibliography subsystem is rather complex, and Alan, who has worked with Hans on support for APS and APA, wants to do things the right way, which means he wants to code for all corner cases. From my own experience: it is difficult to just copy and modify the existing publ-imp-XXX files; they define a number of clever macros that allow code reuse and consistency, but are not the most straightforward way for a non-programmer (like myself) to proceed. I have found it easier to start from scratch by writing my own publ-imp-custom.{mkiv,lua} files and then add whatever I need, one entry type at a time. That also allows you to understand the ways in which the system works. But of course, it’s less convenient than just changing APA to MLA, as you can in biblatex. ConTeXt has a much smaller user base, so we take somewhat longer. Maybe I should add a wiki article on a basic way to start one’s own custom definitions...

Best

Thomas

> On 26. Mar 2022, at 15:34, A A via ntg-context <ntg-context@ntg.nl> wrote:
> 
> Hi Thomas,
> 
> Yes, I was able to find the appropriate section in the manual, thanks. Please see my answer at SE. 
> 
> I don't think reading the docs is far-fetched by the way. But I think asking on here is also fine.
> 
> I'll consider making a contribution once I get a better grip of how the ConTeXt system is put together.
> 
> Again thanks for your response.
> 
> Regards,
> 
> Amine

___________________________________________________________________________________
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-03-26 15:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-26 12:25 A A via ntg-context
2022-03-26 12:48 ` A A via ntg-context
2022-03-26 13:04   ` A A via ntg-context
2022-03-26 13:51     ` Thomas A. Schmitz via ntg-context
2022-03-26 14:34       ` A A via ntg-context
2022-03-26 15:37         ` Thomas A. Schmitz via ntg-context [this message]
2022-03-26 15:42           ` Denis Maier via ntg-context
2022-03-26 15:58             ` Thomas A. Schmitz via ntg-context
2022-03-26 17:04       ` Henning Hraban Ramm via ntg-context
2022-03-29 14:52         ` Denis Maier via ntg-context
2022-03-27 19:49 ` Jean-Pierre Delange 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=75AAADCC-2769-4DEA-89EE-D30B10EC08CC@uni-bonn.de \
    --to=ntg-context@ntg.nl \
    --cc=thomas.schmitz@uni-bonn.de \
    /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).