From: Pablo Rodriguez via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Pablo Rodriguez <oinos@gmx.es>
Subject: [NTG-context] Re: Inconsistencies with fonts/c2sc feature
Date: Tue, 25 Jun 2024 17:35:56 +0200 [thread overview]
Message-ID: <9ce1c93b-74b1-4562-8e15-274d870ce24a@gmx.es> (raw)
In-Reply-To: <4adf4ed6-0c9b-4d0a-bbde-49d26390fae4@edu.surgu.ru>
On 6/24/24 18:03, Kirill Davidov wrote:
>
> 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.
Hi Kirill,
\definefontfeature [default] [default] [script=auto] may help there.
> With New Computer Modern, it just doesn't work with any latin text no
> matter the script chosen.
I have tested
https://mirrors.ctan.org/fonts/newcomputermodern/otf/NewCM10-Book.otf
(released less than 10 days ago) and there is no c2sc for the Latin script.
I have used FontForge and tested metrics (Metrics > New Metrics Window
[Ctrl+K on my computer]).
> That is, plain small caps work, caps to small caps don't.
I’m afraid to say that the c2sc in the font seems to be a mess (to me at
least).
> What could be the reason to it? Is there anything I could do to
> mitigate it?
The following sample works for me (excluding Greek glyphs).
script=auto, if you need to set the script (automatically).
c2sc=always, if you need Greek c2sc.
lowercasing=yes, since the smcp feature works for Latin glyphs.
In a minimal sample:
\definefontfeature [default] [default] [script=auto]
\definefontfeature[allsc][c2sc=yes, smcp=yes,
lowercasing=yes]
\setupbodyfont[stix]
\starttext
\startbuffer
{\language[ru]Моя любимая
{\feature[+][allsc]ОС}---{\feature[+][allsc]Линукс}.}\crlf
{\language[en]My favourite {\feature[+][allsc]OS} is
{\feature[+][allsc]Linux}.}
{\feature[+][allsc]Λινυξẞ.}
\stopbuffer
\getbuffer
\setupbodyfont[newcomputermodern-book]
\getbuffer
\stoptext
___________________________________________________________________________________
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 15:37 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 ` [NTG-context] " Hans Hagen via ntg-context
2024-06-25 15:35 ` Pablo Rodriguez via ntg-context [this message]
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=9ce1c93b-74b1-4562-8e15-274d870ce24a@gmx.es \
--to=ntg-context@ntg.nl \
--cc=oinos@gmx.es \
/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).