Repository navigation
Cascadia Mono shouldn't use contextual alternate for x #285
Description
I was working with a third-party service that provided me with a URL of this form:
https://example.com/1234x5678.png (1 2 3 4 x 5 6 7 8)
I saw this URL in Windows Terminal, which defaults to Cascadia Mono. The way this URL displayed was this:
https://example.com/1234×5678.png
This made me think the third-party service is using × (U+00D7 MULTIPLICATION SIGN) instead of the usual letter x (U+0078 LATIN SMALL LETTER X). This confusion is not something I want from a terminal. In my opinion, the contextual alternate should only be in Cascadia Code.
Here’s a sample (in Word, with ligatures and contextual alternates enabled):
And in Windows Terminal:
Reacted by Alex Yashukov, Andrii Dieiev, Kalle Olavi Niemitalo, Shannon Little and yvvt0379
Activity
DHowett commentedon May 30, 2020
Good catch. Thanks!
aaronbell commentedon Jun 1, 2020
Fair enough :). I don't think, though, that this is a "Code" vs "Mono" thing, though, as the same situation could happen in either case. I'll disable the code entirely for now until we figure out a better way to implement it.
Kwpolska commentedon Jun 1, 2020
Yeah, perhaps getting rid of this feature would be better for both fonts. (Then again, I don’t ever use ligature fonts for programming, precisely because I don’t like being tricked by my fonts, so I can’t answer for Code.)
Make Cascadia Code a variable font w/ 6 named variations (#304)