ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: jethro Reuel via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: jethro Reuel <jthryeboah@gmail.com>
Subject: Re: Command for specifying et al limit
Date: Tue, 27 Sep 2022 13:33:20 +0000	[thread overview]
Message-ID: <68AE15B0-449D-4D9A-9381-09603A86C4C9@gmail.com> (raw)
In-Reply-To: <20220926221342.74ebdbcb@boo.my.domain>

Dear Alan, 

Thanks again for all your help.

Deleting the definebtxrendering[ref] part makes my citations disappear. I get something like:

<bb:2017> says in their paper…

Also, the setupbtx[apa:list]… doesn’t solve my etallimit problem.

Could you test my code and tweak it for me? Can’t find examples of what I want to achieve in the mailing list archives although it seems it should be fairly straightforward. I want something like:

Bronstein et al. says in their paper…

I found the etaldisplay affects the display of the references and I don’t want that. 

Jethro 

> On 27 Sep 2022, at 04:13, Alan Braslau via ntg-context <ntg-context@ntg.nl> wrote:
> 
> On Mon, 26 Sep 2022 21:40:14 -0600
> Alan Braslau via ntg-context <ntg-context@ntg.nl> wrote:
> 
>>> On Sat, 24 Sep 2022 18:57:25 +0000
>>> Jethro Djan via ntg-context <ntg-context@ntg.nl> wrote:
>>> 
>>> \setupbtx[
>>>  dataset=ref,
>>>  etaldisplay = 1,
>>>  etallimit = 1,
>>> ]
>> 
>> Remove extra spaces.
> 
> Sorry,
> 
> Try
> 
> \setupbtx
>  [apa:list]
>  [etaldisplay=1,
>   etallimit=1]
> 
> and drop the 
> 
> \definebtxrendering
>  [ref]
> 
> 
> I have not tested your example, but the bibliography subsystem creates
> many inherited namespaces, so changing parameters in a general
> namespace after inheritance has occurred (in the definitions) has no
> effect.
> 
> Of course, the etaldisplay and etallimits are set to the APA standard
> in the APA definitions.
> 
> Alan
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2022-09-27 13:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-24 18:57 Jethro Djan via ntg-context
2022-09-27  3:40 ` Alan Braslau via ntg-context
2022-09-27  4:13   ` Alan Braslau via ntg-context
2022-09-27 13:33     ` jethro Reuel via ntg-context [this message]
2022-09-28  0:52       ` Alan Braslau 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=68AE15B0-449D-4D9A-9381-09603A86C4C9@gmail.com \
    --to=ntg-context@ntg.nl \
    --cc=jthryeboah@gmail.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).