W3C home > Mailing lists > Public > public-css-archive@w3.org > June 2020

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

From: Dave Crossland via GitHub <sysbot+gh@w3.org>
Date: Mon, 15 Jun 2020 10:13:02 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-644037794-1592215980-sysbot+gh@w3.org>
> > they treat `1 CSS px = 1 physical pt`
> 
> Maybe someone else should also test this, but ...
> 
> I don’t think that is even close to true on my Apple devices?

The core issue here is that on the one hand, John Hudson, David Berlow, Eben Sorkin, and presumably all other type designers, are designing opsz masters by looking at them in proofs printed where Points are 1/72 of a physical inch, and setting opsz values appropriately based on that. On the other hand, browsers are all using opsz values directly as CSS px values.

Per your evidence, "12pt" is massively inconsistent everywhere. 

But is a 36 css px square massively inconsistent everywhere when measured on common devices with a ruler? That has certainly been my assumption, but I haven't tested it. 

If this is true, then it seems to me that type designers should carry on designing and calibrating their opsz units for the absolute size of print media, and just let the chips fall where they may with web font rendering; and the OP proposal will be needed for authors who care to get it right.

If it is not true, then I am back to thinking that opsz units ought to be calibrated to that size. 

-- 
GitHub Notification of comment by davelab6
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4430#issuecomment-644037794 using your GitHub account
Received on Monday, 15 June 2020 10:13:03 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 19 October 2021 01:31:27 UTC