-
Notifications
You must be signed in to change notification settings - Fork 791
[css-fonts-4] all-small-caps vs unicameral scripts #11640
Copy link
Copy link
Open
Labels
css-fonts-4Current WorkCurrent Worki18n-hlreqHebrew language enablementHebrew language enablementi18n-ilreqIndic language enablementIndic language enablementi18n-jlreqJapanese language enablementJapanese language enablementi18n-trackerGroup bringing to attention of Internationalization, or tracked by i18n but not needing response.Group bringing to attention of Internationalization, or tracked by i18n but not needing response.
Metadata
Metadata
Assignees
Labels
css-fonts-4Current WorkCurrent Worki18n-hlreqHebrew language enablementHebrew language enablementi18n-ilreqIndic language enablementIndic language enablementi18n-jlreqJapanese language enablementJapanese language enablementi18n-trackerGroup bringing to attention of Internationalization, or tracked by i18n but not needing response.Group bringing to attention of Internationalization, or tracked by i18n but not needing response.
Type
Fields
Give feedbackNo fields configured for issues without a type.
WebKit recently got a bug filed against our
all-small-capsimplementation complaining that we are synthesizing small-caps for unicameral scripts (Japanese, specifically). The reporter pointed to Firefox as having the right behavior. Opening this issue to ask a few questions, particularly to @jfkthame:small-capsis unquestionably the right behavior, but forall-small-caps, where the idea is to get all the letters and symbols to match, is this the right behavior? It would create distinct sizes for glyphs belonging to bicameral vs unicameral scripts.