From: Denis Maier via ntg-context <ntg-context@ntg.nl>
To: <ntg-context@ntg.nl>
Cc: denis.maier@unibe.ch
Subject: Re: Short forms and abbreviations in bibliography
Date: Mon, 9 Aug 2021 08:12:12 +0000 [thread overview]
Message-ID: <20888f8e8c0c4d6982a360ee587ecbe7@unibe.ch> (raw)
In-Reply-To: <0924E179-F1D2-4B05-9D16-C3075A216E2A@fiee.net>
> -----Ursprüngliche Nachricht-----
> Von: ntg-context <ntg-context-bounces@ntg.nl> Im Auftrag von Henning
> Hraban Ramm via ntg-context
> Gesendet: Samstag, 7. August 2021 22:40
> An: mailing list for ConTeXt users <ntg-context@ntg.nl>
> Cc: Henning Hraban Ramm <texml@fiee.net>
> Betreff: Re: [NTG-context] Short forms and abbreviations in bibliography
>
>
>
> > Am 07.08.2021 um 21:53 schrieb Joey McCollum via ntg-context <ntg-
> context@ntg.nl>:
> >
> > A separate list of abbreviations would then list "LSAWS" alongside "Linguistic
> Studies in Ancient West Semitic" (and likewise for other journal/series
> abbreviations).
>
> Regarding abbreviations have a look at
> https://wiki.contextgarden.net/Command/definesynonyms
>
> It should be as easy as
>
> \abbreviation{LSAWS}{Linguistic Studies in Ancient West Semitic}
>
> The full name of \quote{LSAWS} is \infull{LSAWS}.
>
> \placelistofabbreviations
>
>
> I had a case where mostly abbreviations were used in the text but the full name
> should appear in the index.
> I can provide the setup (including Lua functions), if it might help you.
>
>
> Can’t help with bibliographies, sorry.
SBL is a tricky beast anyway. There were some discussions regarding implementing Chicago Manual of Style a couple of weeks ago. Develelopments on that front could also be useful for SBL. Don't know what came out of this though.
Denis
>
> Hraban
> ________________________________________________________________
> ___________________
> 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
> ________________________________________________________________
> ___________________
___________________________________________________________________________________
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-08-09 8:12 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 [this message]
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
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=20888f8e8c0c4d6982a360ee587ecbe7@unibe.ch \
--to=ntg-context@ntg.nl \
--cc=denis.maier@unibe.ch \
/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).