From: Max Chernoff via ntg-context <ntg-context@ntg.nl>
To: ntg-context <ntg-context@ntg.nl>
Cc: Max Chernoff <tex@maxchernoff.ca>
Subject: [NTG-context] OpenType contextual alternates disabled by default
Date: Tue, 09 Sep 2025 01:34:11 -0600 [thread overview]
Message-ID: <cd88fba4ba6fff68a6e1ad6b27439a672bd15332.camel@maxchernoff.ca> (raw)
Hi Hans,
OpenType contextual alternates ("calt") seem to be disabled by default
in ConTeXt. However, the OpenType spec recommends that this is enabled
by default
https://learn.microsoft.com/en-us/typography/opentype/spec/features_ae#tag-calt
and it's enabled by default in both HTML and HarfBuzz
https://drafts.csswg.org/css-fonts/#default-features
https://harfbuzz.github.io/shaping-opentype-features.html
Changing this default in ConTeXt probably isn't possible due to
backwards compatibility concerns, so this is more of an FYI than a
request for any changes to be made.
Background: this came up in a recent TeX.SE question
https://tex.stackexchange.com/a/750767
where a new user was surprised by ConTeXt's default setting since it
makes some fonts render differently than other programs.
Thanks,
-- Max
___________________________________________________________________________________
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 reply other threads:[~2025-09-09 7:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 7:34 Max Chernoff via ntg-context [this message]
2025-09-09 7:59 ` [NTG-context] Re: OpenType contextual alternates disabled by default Hans Hagen via ntg-context
2025-09-09 20:16 ` Wolfgang Schuster
2025-09-10 6:58 ` Hans Hagen 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=cd88fba4ba6fff68a6e1ad6b27439a672bd15332.camel@maxchernoff.ca \
--to=ntg-context@ntg.nl \
--cc=tex@maxchernoff.ca \
/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).