- From: Laurence Penney via GitHub <sysbot+gh@w3.org>
- Date: Sat, 15 May 2021 21:18:41 +0000
- To: public-css-archive@w3.org
> I wish we were aiming for defining intended arc minutes in the eye. We are aiming towards that. Device makers already fix the true length of 1px in their browsers using predicted reading distance as the key metric (with adjustments for actual pixel size to preserve sharpness), hence roughly constant arc minutes per px across devices. The proposal before us lets us tune this existing automation with custom formulae for opsz, in particular in case the 1px:1opsz ratio benefits from some adjustment (it probably does!). I’d love this thing to move forward so that device makers and practising web typographers can set opsz’d type on real websites and measure reading experiences in ways that were not possible before, working with fonts including [several](https://fonts.google.com/specimen/Literata) [high quality](https://fonts.google.com/specimen/Fraunces) [variable opsz](https://adobe-fonts.github.io/source-serif/) fonts that have recently been published with libre licenses. Researchers can use actual reading distance and true px size as additional signals in their font-optical-sizing formulae. This proposal is not a panacea. It’s a significant step towards a panacea, and — with use — will help us define that panacea better. -- GitHub Notification of comment by Lorp Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4430#issuecomment-841726977 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 15 May 2021 21:18:43 UTC