- From: Johannes Neumeier via GitHub <sysbot+gh@w3.org>
- Date: Mon, 25 Mar 2024 07:55:50 +0000
- To: public-css-archive@w3.org
@AmeliaBR Note that the VF spec allows arbitrary axes and convention is to uppercase those arbitrary tags (e.g. "CRSV"), as opposed to lower casing [registered axes’ tags](https://learn.microsoft.com/en-us/typography/opentype/spec/dvaraxisreg). A CSS spec should probably pertain only to registered axes and their ranges so `ital` (0 – 1) and `slnt` (-90 – 90). [Adapter](https://rosettatype.com/AdapterPE) would be one more variable font with both axes, albeit `ital` is a defacto binary one (e.g. note the "a" changing on `ital = 1`). Mind you cursive forms also apply to other scripts, e.g. Adapter supports this also for some Cyrillic, and it is perfectly thinkable to have meaning for Greek, Arabic, and many other scripts. If **simplification** is the goal one could argue `font-style: italic` should instruct the font to use absolute maximum values for`ital` and `slnt`, any of which are found present. This is _very often_ the intent of the design, meaning for a font with: - only `ital` / cursive shapes but no slant this works, - only `slnt` and no italic shapes this works, and - both `ital` and `slnt` activating both is _likely_ also what the designer wants for the "italic" (the above mentioned Rosalinde and Cursive do this based on `slnt` implicitly, and Adapter’s _static_ italic fonts do this) (Mind you, font vendors can choose to implement axes in a way that they implicitly trigger another, so say a VF might be instructed to show `ital = 1` cursive glyph shapes if `slnt > x` via opentype features. You *could* argue that activating `ital` for given `slnt` values is up to the font vendor, but even here even this sample of three fonts yields three different implementations, stemming surely from the ambiguity of this very issue.) If **control** is the goal, my suggestion from the previous post is applicable, at the expense of complexity. -- GitHub Notification of comment by kontur Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3125#issuecomment-2017412513 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 25 March 2024 07:55:51 UTC