Re: [csswg-drafts] [css-fonts-4] [varfont] Italic & Oblique benefit from not including a <number>

The Working Group just discussed `Italic & Oblique benefit from not including a <number>`, and agreed to the following:

* `RESOLVED: Close the issue no-change, fantasai to write a comment for opentype spec authors`

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> Topic: Italic &amp; Oblique benefit from not including a &lt;number><br>
&lt;fantasai> github: https://github.com/w3c/csswg-drafts/issues/519<br>
&lt;frremy> chris_: I read the entire issue, and didn't understand what the issue was about<br>
&lt;frremy> myles: I think the proposal is relative to variable fonts<br>
&lt;frremy> myles: You started being able to say "oblique 30deg"<br>
&lt;frremy> myles: Would prefer this not to be allowed<br>
&lt;frremy> chris_: why? you can still not define it if you dont want<br>
&lt;frremy> fantasai: otherwise you get the value defined in the spec<br>
&lt;fantasai> fantasai: not a value taken from the font<br>
&lt;frremy> myles: if you specify "oblique 0" you get roman<br>
&lt;frremy> myles: but with variable fonts, but you could make a 0deg oblique<br>
&lt;frremy> fantasai: is there a field that says what the preferred oblique angle is?<br>
&lt;frremy> myles: there is the concept of named instances<br>
&lt;frremy> myles: you can say then "oblique" is this set of values<br>
&lt;frremy> chris_: but the names are not standardized<br>
&lt;frremy> myles: right, this isn't formal enough for us to rely on<br>
&lt;frremy> myles: there might be one in there with italic, but there might be many<br>
&lt;frremy> chris_: and it could  be localized<br>
&lt;frremy> chris_: so let's not do this<br>
&lt;frremy> chris_: proposal is to close no action<br>
&lt;frremy> myles: I agree<br>
&lt;frremy> fantasai: and add a comment that if the font authors add some field for a value<br>
&lt;frremy> fantasai: otherwise we will not do anything<br>
&lt;fantasai> s/font authors/Opentype spec/<br>
&lt;fantasai> s/value/value then we can consider using that instead of 14/<br>
&lt;frremy> RESOLVED: Close the issue no-change, fantasai to write a comment for opentype spec authors<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/519#issuecomment-402011546 using your GitHub account

Received on Tuesday, 3 July 2018 04:43:41 UTC