Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cascadia Code vs Cascadia Mono #36

Open
jsheard opened this issue Jan 21, 2025 · 0 comments
Open

Cascadia Code vs Cascadia Mono #36

jsheard opened this issue Jan 21, 2025 · 0 comments

Comments

@jsheard
Copy link

jsheard commented Jan 21, 2025

The monospace code stack currently uses Cascadia Code on modern Windows, which includes somewhat controversial ligatures for sequences like != and !== that don't directly represent the underlying characters. Some people like them but I'm wary of forcing them on all readers of a website regardless of their preference. AFAICT it's also the only font in the stack which features coding ligatures, making it inconsistent with the rest.

Windows also includes Cascadia Mono, which is the same font but without ligatures. Might it be worth making Mono the default, with a footnote pointing out the alternative Code, or vice versa?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant