From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Hans Hagen <j.hagen@freedom.nl>
Subject: [NTG-context] Re: Inconsistencies with fonts/c2sc feature
Date: Tue, 25 Jun 2024 11:11:09 +0200 [thread overview]
Message-ID: <43cd89e2-10a6-4817-86f1-7931b01e6aa3@freedom.nl> (raw)
In-Reply-To: <4adf4ed6-0c9b-4d0a-bbde-49d26390fae4@edu.surgu.ru>
On 6/24/2024 6:03 PM, Kirill Davidov wrote:
> Greetings,
>
> I have been trying to make font feature sets that allow me to write
> abbreviations in small caps and corporate entity/product/etc names with
> small caps replacing regular ones. I have run into an issue where c2sc
> works as intended on some fonts and not in others. No idea what that's
> about. MWE:
>
> %\definefontfeature [default] [default] [script=latin]
> \definefontfeature [default] [default] [script=cyrillic]
> \definefontfeature [capstosc] [c2sc=yes]
> \definefontfeature [smallcaps] [cpsp=yes, smcp=yes, lowercasing=yes]
>
> \setupbodyfont[stix]
> %\setupbodyfont[newcomputermodern-book]
>
> \starttext
>
> {\language[ru]Моя любимая
> {\feature[+][smallcaps]ОС}---{\feature[+][capstosc]Линукс}.}\crlf
> {\language[en]My favourite {\feature[+][smallcaps]OS} is
> {\feature[+][capstosc]Linux}.}
>
> \stoptext
>
> With STIX Two, c2sc (and smcp) works with any language as long as one
> doesn't select a script in the font features, else it only works with
> the chosen script. With New Computer Modern, it just doesn't work with
> any latin text no matter the script chosen. That is, plain small caps
> work, caps to small caps don't. What could be the reason to it? Is there
> anything I could do to mitigate it?
you can try
\definefontfeature [capstosc] [c2sc=always]
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2024-06-25 9:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-24 16:03 [NTG-context] " Kirill Davidov
2024-06-25 9:11 ` Hans Hagen via ntg-context [this message]
2024-06-25 15:35 ` [NTG-context] " Pablo Rodriguez via ntg-context
2024-06-25 17:53 ` Kirill Davidov
2024-06-25 19:27 ` Pablo Rodriguez via ntg-context
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=43cd89e2-10a6-4817-86f1-7931b01e6aa3@freedom.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@freedom.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).