From: Otared Kavian <otared@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Problem with \Caps
Date: Mon, 21 Dec 2020 15:25:08 +0100 [thread overview]
Message-ID: <E570BFD6-983C-4C5B-B313-5548865014DD@gmail.com> (raw)
In-Reply-To: <367de52c-e5ca-7b02-c575-1573676f2977@um.es>
Hi Joaquín,
Actually it depends on the font you are using, but on th eother hand it seems that \Caps is broken in LMTX.
The following gives a correct result in mkiv but results in an error in LMTX:
\setupbodyfont[lucidaot]
\starttext
Test {\sc Test} {\Caps Test}
{\smallcaps Test}
\meaning\Caps
\stoptext
Best regards: Otared
> On 20 Dec 2020, at 18:59, Joaquín Ataz López <jal@um.es> wrote:
>
>
> Good day to everyone. I have a problem that may be very simple to solve, but for which I have not found an answer in the wiki.
>
> Until relatively recently I was using the January 2020 version of ConTeXt Standalone, recently I have updated it to the December 18th version, and when I compile a file that I used to compile well, an error is generated because the \Caps macro is not recognized.
>
> I can't get the desired effect with \sc, it has to be with \Caps.
>
> I have tried to compile it with LMTX but there too is considered that \Caps is an undefined control sequence.
>
>
> --
> Joaquín Ataz López
> Derecho Civil
> Universidad de Murcia
>
> ___________________________________________________________________________________
> 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
___________________________________________________________________________________
prev parent reply other threads:[~2020-12-21 14:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-20 17:59 Joaquín Ataz López
2020-12-21 14:25 ` Otared Kavian [this message]
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=E570BFD6-983C-4C5B-B313-5548865014DD@gmail.com \
--to=otared@gmail.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).