- From: jfkthame via GitHub <sysbot+gh@w3.org>
- Date: Fri, 28 Oct 2022 09:11:59 +0000
- To: public-css-archive@w3.org
> Apologies for asking some basic questions. The spec says > > > 'normal' Specifies that kerning is applied > > So for CJK, does `normal` mean 'not-normal'? You could say that, yes. (But remember that the initial value of `font-kerning` is not `normal` but `auto`, which gives the browser scope to "do the right thing" automatically as a default.) > Or does it mean that kerning applies only if the font supports it? Well, that's always part of the picture -- yes, a feature like kerning depends on font support. If the font doesn't define any kerning, then the `font-kerning` property will have no effect. > Is it possible for the browser to kern CJK fonts when no such information is included in the font? In theory (for any font, not just CJK), but I'm not aware of any browser engine that does so. (I believe some desktop publishing software such as InDesign may do things like that.) > (Is there a general case here where we need to be more careful about script-specific assumptions before using values like 'normal'?) Maybe. Though I tend to think of things like `font-kerning` as being quite script-agnostic. The value `normal` doesn't directly mean "do what is normal (for any given script or context)", but rather "use what the font designer specified". (Perhaps it should've been named `always` instead? But then, it wouldn't really mean "always", it'd mean "always, if the font provides it".) -- GitHub Notification of comment by jfkthame Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7958#issuecomment-1294740692 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 28 October 2022 09:12:01 UTC