ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Hamid,Idris" <Idris.Hamid@ColoState.EDU>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
Subject: [NTG-context] Re: Applying \sc for smallcaps across styles
Date: Sat, 19 Aug 2023 18:36:26 +0000	[thread overview]
Message-ID: <79b6fb87-414b-47cb-9cd9-9a37540e2423@Spark> (raw)
In-Reply-To: <aaadfddb-2d6e-b6ce-5c2f-9d226ba97187@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 3304 bytes --]

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.

Best wishes
Idris

--
Professor Idris Samawi Hamid
Department of Philosophy
Colorado State University
Fort Collins, CO 80523
On Aug 19, 2023, 9:26 AM -0600, Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>, wrote:

** Caution: EXTERNAL Sender **

Hamid,Idris schrieb am 19.08.2023 um 16:03:
Dear gang,

Consider the following typescript template:

\definefontfeature
  [myfont-tf-sc]
  [mode=node,script=latn,language=dflt,trep=no,
   protrusion=quality,expansion=quality,
   compose=yes,combine=yes,tlig=yes,
   kern=yes,liga=yes,onum=yes,cpsp=yes,smcp=yes, % smcp activie
   trnsl=force]

% synonym mapping
\starttypescript [serif] [myfont] [name]
  \loadfontgoodies[myfontlfg]
  \definefontsynonym [Serif]           [MyFontRegular]    [features=myfont-tf]
  \definefontsynonym [SerifItalic]     [MyFontItalic]     [features=myfont-it]
  \definefontsynonym [SerifBold]       [MyFontBold]       [features=myfont-tf]
  \definefontsynonym [SerifBoldItalic] [MyFontBoldItalic] [features=myfont-it]

  \definefontsynonym [SerifCaps]           [MyFontRegular]    [features=myfont-tf-sc]
  \definefontsynonym [SerifCapsItalic]     [MyFontItalic]     [features=myfont-it-sc]
  \definefontsynonym [SerifCapsBold]       [MyFontBold]       [features=myfont-tf-sc]
  \definefontsynonym [SerifCapsBoldItalic] [MyFontBoldItalic] [features=myfont-it-sc]
\stoptypescript

% font mapping
\starttypescript [serif] [myfont]
  \loadfontgoodies[myfontlfg]
  \definefontsynonym [MyFontRegular]     [file:MyFont-Regular] % [features=myfont-tf]
  \definefontsynonym [MyFontItalic]      [file:MyFont-It]      % [features=myfont-it]
  \definefontsynonym [MyFontBold]        [file:MyFont-Bold]    % [features=myfont-tf]
  \definefontsynonym [MyFontBoldItalic]  [file:MyFont-BoldIt]  % [features=myfont-it]
\stoptypescript

As is well known, \sc selects the small caps only from the Serif font, not from SerifBold etc. But MyFont has smallcaps for every style. So in the typescript we make that explicit and apply the smcp=yes fontfeature to SerifCapsBold etc.

But this does not work: \sc still only applies to Serif or SerifCaps.

Now I can load a goodies file myfontlfg and do something like this:

local smallcaps = {
    smcp = yes,
}

But that does not change the behavior of \sc.

Yes, there is an easy workaround:

\definefontfeature[smallcaps][smcp=yes]
\define\sc{\addff{smallcaps}}

This works for all styles that have the smcp feature, but I don't like having to redefine a system command.

So the questions are:

1) Is there a recommended\better way to get \sc to work across all styles?

\setupbodyfont[pagella]

\starttext

\tf Upright, \it Italic, \bf Bold and \bi Bolditalic

\style[style=smallcaps]{\tf Upright, \it Italic, \bf Bold and \bi Bolditalic}

\tf Upright, \it Italic, \bf Bold and \bi Bolditalic

\setsmallcaps\tf Upright, \it Italic, \bf Bold and \bi Bolditalic

\stoptext


[-- Attachment #1.2: Type: text/html, Size: 5889 bytes --]

[-- Attachment #2: Type: text/plain, Size: 495 bytes --]

___________________________________________________________________________________
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 18:39 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 [this message]
2023-08-19 19:01     ` Wolfgang Schuster
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=79b6fb87-414b-47cb-9cd9-9a37540e2423@Spark \
    --to=idris.hamid@colostate.edu \
    --cc=ntg-context@ntg.nl \
    --cc=wolfgang.schuster.lists@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).