From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@xs4all.nl>, Alan BRASLAU <alan.braslau@comcast.net>
Subject: Re: Short forms and abbreviations in bibliography
Date: Fri, 8 Oct 2021 13:38:32 +0200 [thread overview]
Message-ID: <19a4940d-f76f-ae88-6bbf-42f1627da373@xs4all.nl> (raw)
In-Reply-To: <CAGxRUG_NpXfUMvTju71cah7HSxyCL63XfAtT=AeThSn8wwQMjw@mail.gmail.com>
On 10/7/2021 6:38 AM, Joey McCollum via ntg-context wrote:
> A concise solution that I found would work was to define a "shorthand"
> citation alternative and just print the shorthand with that:
>
> ```
> % Shorthand citation setup
> \startsetups btx:sbl:cite:shorthand
> \begingroup
> \def\currentbtxcategory{\btxfield{category}}
> \texdefinition{btx:sbl:inline:shorthand}
> \endgroup
> \removeunwantedspaces
> \removepunctuation
> \stopsetups
>
> ...
>
> \expanded{\abbreviation[\currentbtxtag]{\textcite[alternative=shorthand,lefttext=,righttext=][\currentbtxtag]}{\textcite[alternative=listsubcite,lefttext=,righttext=][\currentbtxtag]}}
> ```
>
> Again, this works, although I'm still not sure why
> invoking \texdefinition{btx:sbl:inline:shorthand} directly doesn't.
I leave it to Alan to comment on this as he's the bib guru
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2021-10-08 11:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-07 19:53 Joey McCollum via ntg-context
2021-08-07 20:40 ` Henning Hraban Ramm via ntg-context
2021-08-09 8:12 ` Denis Maier via ntg-context
2021-08-09 12:55 ` Joey McCollum via ntg-context
2021-08-22 22:11 ` Joey McCollum via ntg-context
2021-10-06 16:35 ` Joey McCollum via ntg-context
2021-10-06 18:35 ` Joey McCollum via ntg-context
2021-10-06 19:05 ` Joey McCollum via ntg-context
2021-10-06 21:58 ` Joey McCollum via ntg-context
2021-10-07 4:38 ` Joey McCollum via ntg-context
2021-10-08 11:38 ` Hans Hagen via ntg-context [this message]
2021-10-11 14:24 ` Joey McCollum 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=19a4940d-f76f-ae88-6bbf-42f1627da373@xs4all.nl \
--to=ntg-context@ntg.nl \
--cc=alan.braslau@comcast.net \
--cc=j.hagen@xs4all.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).