Width axis range

[davelab6]

The width axis range is current 75% to 125% of regular; but this may be true of the opsz-def, but it is not true of the opsz-max, which gets much wider and much much narrower than those percentages.

Therefore I recommend we range the MSFT wdth axis to the opsz-max proportions, so that the user's sense of what the range of the typeface is - extreme-o - is surfaced

[dberlow]

Oh thanks. I've been wondering what to do about the spec, when it comes to Extremo.

I took some notes in preparation for describing the issue to DJR, who is writing a script to do a full parametric survey regardless fo the designspace file's needs,

They are rather sketchy looking but standards-ominous if you can read them.

Default xopq 192 + xtra 734 = 926, no big deal.

Heaviest, Widest, Largest size,

(opszmax wdthmax wghtmax), xopq 600 + xtra 500 = 1100

Lightest, Narrowest, Largest size,

(opszmax wdthmin wghtmin). xopq 6 + xtra 38 = 44

So the range of how we measure width is 144/1000ths to 1100/1000ths

Width axis at opsz max.

926/100 = 1100/x = 118%, of the default.

926/100 = 144/x = 15.5%, of the default.

Opsz 14 Default Weight space = 3/1000, 96/1000, 300/1000

So I can make widths accurate % and still have to measure all the wght values, but can I go up to 1100, 1400, 1500? on the OS/2 weight scale?

On Thu, Sep 19, 2019 at 6:35 PM Dave Crossland notifications@github.com wrote:

The width axis range is current 75% to 125% of regular; but this may be true of the opsz-def, but it is not true of the opsz-max, which gets much wider and much much narrower than those percentages.

Therefore I recommend we range the MSFT wdth axis to the opsz-max proportions, so that the user's sense of what the range of the typeface is

• extreme-o - is surfaced

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/TypeNetwork/Roboto-Extremo/issues/54?email_source=notifications&email_token=AAO5VDRK72PXLPWUULYADT3QKP5BVA5CNFSM4IYQXHW2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HMRHQFA, or mute the thread https://github.com/notifications/unsubscribe-auth/AAO5VDWXY2ZF2DU3BP5L4SLQKP5BVANCNFSM4IYQXHWQ .

[davelab6]

No. MS Weight's valid range is 1 to 1000 ( https://docs.microsoft.com/en-us/typography/opentype/spec/dvaraxistag_wght says, "Valid numeric range: Values must be in the range 1 to 1000.")

MS Width's valid range starts at 1 ( https://docs.microsoft.com/en-us/typography/opentype/spec/dvaraxistag_wdth says, "Valid numeric range: Values must be strictly greater than zero.") and the 'scale interpretation' is that "values can be interpreted as a percentage of whatever the font designer considers “normal width” for that font design," and the required value is "100 is required."

[dberlow]

Enclosed shows style upon which wdth will be based. Edited design space file and remake to follow.

Extremo wdth re%.pdf

[dberlow]

SO, the designspace file is updated to these values please regenerate.

Thanks.

DC, this is the measures and math on the default wght, opsz max, width axes.

OPSZ MAX, WGHT default wdth-min, = 202 (xtra) wdth-def, = 800 (xtra) wdth-max, = 1210 (xtra),

800/100=202/x = 25.25% 800/100=1210/x = 151.25%

wdth-min = 25 wdth-def, = 100 wdth-max, = 151

[dberlow]

OPSZ MAX, WGHT default wdth-min, = 202 (xtra) wdth-def, = 800 (xtra) wdth-max, = 1210 (xtra),

800/100=202/x = 25.25% 800/100=1210/x = 151.25%

wdth-min = 25 wdth-def, = 100 wdth-max, = 151