From: Nigel King <nigel@nigelking.me.uk>
To: Hans Hagen <j.hagen@xs4all.nl>
Cc: Context News Group <ntg-context@ntg.nl>
Subject: Re: \infull not working
Date: Wed, 18 Nov 2020 15:12:45 +0000 [thread overview]
Message-ID: <02FE5FC9-A80E-48AC-8682-B71BB2C58BBD@nigelking.me.uk> (raw)
In-Reply-To: <1cf4f277-c2ea-b311-9ba6-6446333f8f2e@xs4all.nl>
[-- Attachment #1.1: Type: text/plain, Size: 2070 bytes --]
Thanks Hans for your very prompt reply.
I placed
\overloadmode\plusfour
at the beginning of the file
The example now compiles.
However the command \infull{Ch} now results in CH in small capitals.
Is there something I have misunderstood?
Thanks
Nigel
On 18 Nov 2020, at 14:19, Hans Hagen <j.hagen@xs4all.nl> wrote:
On 11/18/2020 1:35 PM, Nigel King wrote:
> Dear Group,
> Thanks for your excellent work.
> I have just got a new computer and installed Context as I normally do. Unfortunately there appears to be a bug, unless I have done something wrong. \infull appears not to be working. I have used the following test file which is from the wiki but split the line with \infull{Ch} in two to be certain.
> \definesynonyms[test][tests][\infull]
> \setupsynonyms[test][criterium=all]
> \test{ITU}{International Telecommunication Union}
> \test{MID}{Maritime Identification Digit}
> \test{Ch}{Switzerland}
> \starttext
> The \ITU\ is an
> organisation in \infull{Ch}
> \subject{Short is nice}
> \placelistoftests
> \stoptext
> The log message has this in it.
> tex error > tex error on line 12 in file /Users/nki001/OneDrive/MyDocuments/Context/NGAForIreland/test.tex: Undefined control sequence
fixed in next upload ... but ... on my machine, where I run with
\overloadmode\plusfour % error, \plusthree is warning only
i then will get:
csname overload > fatal error, protection level 4, control sequence 'infull', properties 'frozen instance protected', file './oeps.tex', line 4
because \infull is already used by the predefine abbreviations instance
no problem if you don't use that feature
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl <http://www.pragma-ade.nl/> | www.pragma-pod.nl <http://www.pragma-pod.nl/>
-----------------------------------------------------------------
[-- Attachment #1.2: Type: text/html, Size: 17517 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
___________________________________________________________________________________
next prev parent reply other threads:[~2020-11-18 15:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 12:35 Nigel King
2020-11-18 14:19 ` Hans Hagen
2020-11-18 15:12 ` Nigel King [this message]
2020-11-18 15:49 ` Hans Hagen
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=02FE5FC9-A80E-48AC-8682-B71BB2C58BBD@nigelking.me.uk \
--to=nigel@nigelking.me.uk \
--cc=j.hagen@xs4all.nl \
--cc=ntg-context@ntg.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).