- From: Nat McCully via GitHub <sysbot+gh@w3.org>
- Date: Wed, 19 Jun 2019 23:04:17 +0000
- To: public-css-archive@w3.org
> > This was discussed at the most recent OpenType F2F, and there was interest in the font using two distinct low-level physical controls for vertical stretching and horizontal stretching, and the browser/app determining which of those types of stretching to use. > > Important thing to remember is that value of font-stretch property affects font matching. Right now 'wdth' axis is used for this purpose. But if choice of axis will depend on orientation of particular character, then font matching can't be done before character orientation analysis is complete. Note that for Roman fonts, using the 'wdth' axis all the time should be ok -- it is only when characters are upright that the 'vwid' axis would give a better result, when matching other squashed in that dimension, for example, fonts. I am of course speaking out of turn with little knowledge of CJK font matching using that axis... -- GitHub Notification of comment by macnmm Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4044#issuecomment-503778048 using your GitHub account
Received on Wednesday, 19 June 2019 23:04:18 UTC