From: Rik Kabel <ConTeXt@rik.users.panix.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: [NTG-context] Problem with textstyle
Date: Fri, 17 Nov 2023 22:21:53 -0500 [thread overview]
Message-ID: <3416779e-1fef-40be-b312-d55623511e9a@rik.users.panix.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1080 bytes --]
Hello list,
The following example does not compile, complaining “Missing number,
treated as zero
needed to see a number, look up 'weird error' in the index to The TeXbook”:
\setuphead [chapter]
[
textstyle=cap,
]
\starttext
\startchapter [title={Oops!}]
\input knuth-gpt \par
\stopchapter
\stoptext
Replacing the textstyle /cap/ by any of /bold/, /slanted/, /smallcaps/,
and /italic/ results in a clean compilation but the indicated style is
not applied. Using a style description like /em/, /\em/, /bf/, /\bf/,
/\sc,/ does produce the suggested result. The wiki and mail repository
are full of examples with the former style names.
Using /style=cap/ (which would change the number as well) also results
in a failed compilation, while using /style=bolditalic/ works as it should.
ConTeXt ver: 2023.09.26 18:19 LMTX fmt: 2023.10.9 int: english/english
--
Rik
[-- Attachment #1.2: Type: text/html, Size: 1625 bytes --]
[-- Attachment #2: Type: text/plain, Size: 511 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___________________________________________________________________________________
reply other threads:[~2023-11-18 3:41 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=3416779e-1fef-40be-b312-d55623511e9a@rik.users.panix.com \
--to=context@rik.users.panix.com \
--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).