ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
To: "Hamid,Idris" <Idris.Hamid@ColoState.EDU>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: [NTG-context] Re: Applying \sc for smallcaps across styles
Date: Sat, 19 Aug 2023 21:01:07 +0200	[thread overview]
Message-ID: <cd793e78-2194-bede-4d0c-5af3c4aad1a2@gmail.com> (raw)
In-Reply-To: <79b6fb87-414b-47cb-9cd9-9a37540e2423@Spark>

Hamid,Idris schrieb am 19.08.2023 um 20:36:
> Many thanks. From font-pre.mkiv:
>
> \definealternativestyle [\v!smallcaps] [\setsmallcaps] [\setsmallcaps]
> :
> \unexpanded\def\setsmallcaps{\doaddfeature{f:smallcaps}}
>
> So on the wiki we should say that \sc is a deprecated/legacy command 
> that no longer makes sense in an opentype-features world. New users 
> should no longer use it.

It depends on the font, e.g. Latin Modern still requires \sc because it 
provides a separate file for smallcaps but no smcp feature.

ConTeXt has a command which can be used to check whether the current 
active font provides the smcp feature but the recommended way is to 
choose a font which supports to method (\sc or \setsmallcaps) which is 
used in the document.

Wolfgang

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : https://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2023-08-19 19:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-19 14:03 [NTG-context] " Hamid,Idris
2023-08-19 15:26 ` [NTG-context] " Wolfgang Schuster
2023-08-19 18:36   ` Hamid,Idris
2023-08-19 19:01     ` Wolfgang Schuster [this message]
2023-08-19 19:14       ` Hamid,Idris
2023-08-19 20:17         ` Hamid,Idris
2023-08-19 17:36 ` Pablo Rodriguez
2023-08-19 18:56   ` Hamid,Idris

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=cd793e78-2194-bede-4d0c-5af3c4aad1a2@gmail.com \
    --to=wolfgang.schuster.lists@gmail.com \
    --cc=Idris.Hamid@ColoState.EDU \
    --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).