w3c / w3c/csswg-drafts

[css-fonts] Is "default caseless" matching really required for font names?

Open
#4,652 3 comments 0 reactions 1 assignee View on GitHub

@svgeesus is already working on this.

Since Jul 8, 2020.

css-fonts-4 i18n-tracker Needs Data
Dominant language
Bikeshed
Stars
4.9k
Forks
816
PR merge metrics
PR metrics pending

Description

Per https://drafts.csswg.org/css-fonts-4/#localized-name-matching, font-family names are matched against names in font files using the "default caseless" matching algorithm defined by Unicode.

While the rest of CSS is either only ASCII case-insensitive (matching a-z to A-Z; otherwise case-sensitive) or fully case-sensitive (exact codepoint equality), this algorithm sits in a middle ground, allowing strings like "ſilver" to match "silver".

I expect that this algorithm is required due to legacy constraints with how font names work across platforms, but I'm filing this issue to ensure that's actually the case, and it's not just something somebody thought was reasonable at some point in the past, but could now be swapped out for the simpler ASCII case-insensitive matching.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.