Update build script to output Product and Beta versions

[sberlow]

Production quality give font build the acceptable limits for each axes within design space

Rude Entire design space

[davelab6]

What this means is: Update the build script to output 2 versions:

1. a "Product quality" or "clean" version that clips the primary parametric axis (XOPQ, YOPQ, XTRA, YTRA) to more acceptable limits, so that each axes within design space can't make unruly instances.

2. a "Beta quality" or "rude" version that does not do that, so that the primary parametric axes allow for users to experiment with the entire design space, despite that this risks them venturing into areas of the space where the 'wild' instance can be found.

Where to clip is yet to be defined by @dberlow but that will happen in due course, and the build script work can begin on a simple basis (eg halve their range.)

[sberlow]

@petrvanblokland @asaumierdemers @djrrb Can you chime in on this?

[djrrb]

Not sure precisely what you want comments on at this moment, but once the bounds of the "clean" space are determined, the clipping process should be semi-automatable.

I think it will involve interpolating each master with the default to whatever extreme is acceptable, and then assigning this new interpolation as the master in a parallel designspace. (Maybe new masters will also be necessary, depending?)

[sberlow]

met with @djrrb and @cjdunn They will be workin on this in over the next few days

[dberlow]

I think we are still working on the approval of the 144 pt, after which, the intent was to define some intermediates in the opsz axis to take care of the large imbalance between min (8 pt) to default, (12) vs default to 144 pt, opsz max. then, wdth and wght were to be defined for the opsz range, a narrower range of both wdth and wght for the small end of opsz, and a larger range of wdth and wght for the large end of ops. with concern for each step in opsz between the default and the max. Then, that describes the various mins and max the parametric axes can go, in any part of the registered design space, and the safe range of each parametric axis can then be plotted, each axis abbreviated to the range that works, per opsz, and then you are safe spaced.

Is that what they are doing?

On Tue, Mar 27, 2018 at 2:01 PM, Sam Berlow notifications@github.com wrote:

met with @djrrb https://github.com/djrrb and @cjdunn https://github.com/cjdunn They will be workin on this in over the next few days

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/TypeNetwork/Roboto-Delta/issues/27#issuecomment-376619178, or mute the thread https://github.com/notifications/unsubscribe-auth/AB3ajsg-BYMt3pLAHLnYTruYhYsEsQa6ks5tin6DgaJpZM4Sq9vz .

[sberlow]

This script is for building a pair fonts. One with a more limited space and the full space is for testing. And a second with the entire space.

I will review this list with @davelab6 @cjdunn and @djrrb And we will get this done...

approval of the 144 pt, after which, the intent was to define some intermediates in the opsz axis to take care of the large imbalance between min (8 pt) to default, (12) vs default to 144 pt, opsz max. then, wdth and wght were to be defined for the opsz range, a narrower range of both wdth and wght for the small end of opsz, and a larger range of wdth and wght for the large end of ops. with concern for each step in opsz between the default and the max. Then, that describes the various mins and max the parametric axes can go, in any part of the registered design space, and the safe range of each parametric axis can then be plotted, each axis abbreviated to the range that works, per opsz, and then you are safe spaced.

[sberlow]

This no longer relevant closing