From: jbf via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: jbf <roma83537@gmail.com>
Subject: \placelistofabbreviations in project structure?
Date: Mon, 20 Jun 2022 15:31:40 +1000 [thread overview]
Message-ID: <e61d23e6-a456-31ea-f489-4acdcf236a1a@gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1126 bytes --]
Hi, I wonder what I might be doing wrong for \placelistofabbreviations
not to work in a project. Everything else about \definesysnonyms and
indeed the project is working, but I seem unable to place the list
correctly in the component that is intended to list all abbreviations.
The main environment file for the project contains the definitions. e.g.
\definesynonyms[abbreviation][abbreviations][\infull]
\setupsynonyms[abbreviation][synonymstyle=\em] \abbreviation[adjp]
{adjp.} {adjectival phrase}
All dictionary components (A-Z) call on the main environment file where
the above is defined and give me the correct result if I write \adjp\ or
\infull{adjp} in any one of them.
My MWE below for the (as yet not working) abbreviations component that
contains the placelist command:
\startcomponent 04_abbreviations
\project project_Dictionary
\startchapter[title={Abbreviations}]
\placelistofabbreviations[criterium=all]
\stopchapter
\stopcomponent
According to me that should work, but all I get is the chapter title. I
also tried adding a state=start in case that was needed, but it did nothing.
Julian
[-- Attachment #1.2: Type: text/html, Size: 4645 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 bytes --]
___________________________________________________________________________________
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-06-20 5:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=e61d23e6-a456-31ea-f489-4acdcf236a1a@gmail.com \
--to=ntg-context@ntg.nl \
--cc=roma83537@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).