Re: [csswg-drafts] [css-fonts] Proposal to extend CSS font-optical-sizing (#4430)

> See #614

I think this is highly relevant thread, and I encourage anyone reading this issue who has not read that issue to do so in its entirety! :) 

I myself had not caught up on the latest (2020) comments there, and the [most recent one](https://github.com/w3c/csswg-drafts/issues/614#issuecomment-611217635) proposes:

> On the pages where you need the accurate length ... set a `--unit-scale: 1.07;` (subbing in the real value) property on the `html` element [ with the ratio of css cm to physical cm on your device and then ] instead of `width: 5cm;`, write `width: calc(5cm * var(--unit-scale, 1));`.

This for me is very exciting, is very similar to this proposal :)

> It seems to me, the best one could do in redefining the opsz scale to use 'px' as a unit would be to apply a special definition of that unit as being 1/96 of a physical inch, which I suppose would address what some browsers are doing now while still providing type designers with an absolute size target. 

I think that might be a practical compromise... **-if-** MS was going to stick hard to the idea that `opsz units` should be interpreted as physical units size values. But! :) https://docs.microsoft.com/en-us/typography/opentype/spec/dvaraxistag_opsz says, bold emphasis mine:

> The scale for the Optical size axis is text size in points. For these purposes, the text size is as determined by the document or application for its intended use; **the actual physical size on a display may be different** due to document or application zoom settings or intended viewing distance.

So it seems the existing OpenType 1.8 Spec already acknowledges that "points" is not actually physical points at all, but CSS Points or MS Word Points and so on.



-- 
GitHub Notification of comment by davelab6
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4430#issuecomment-635775151 using your GitHub account

Received on Friday, 29 May 2020 05:53:58 UTC