-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
First pass sample Kern pairs #1
Comments
Kern.pair tendencies Default = 14 pt. Its xtra will = “dxtra” and “lxtra” is local instance’s value. Values given in first chart is approximated scale and at least direction to scale kerns to 6 lxtra adding those scales to the existing scale. 20 other defining designspace locations for wght, wdth, and opsz will then be analyzed as those scalings add up. This approximated scaling makes negative kern values larger, and positive kern values smaller, (which may seem wrong, please confirm;). The value list is not intended to be final as listed, but rather as a guide to the dxtra to lxtra values at first applied to the instances at 6 “sides” of the design space e.g. After analyzing the effects of the rescaling on the kerning those 6 sides. The suggested scaling effects on those sides is in italic The other 20 locations shown in the chart, (as list only for opsz8), then need to be looked at as the scale factors have added up in the design space. Then:
Amstelvar Roman: |
Sorry for the delay here, these are the values I used in the initial version of the script:
|
So the six values in italic that I’ve given above, are guesses intended to be additional scales to the values that you used for those 6, but the opsz value somehow has to be distributed out over OPSZ max’s Intermediates. Let me know thanks |
pinging DJR on last comment above... |
Again, my apologies on the delay...in the past couple days I’ve finally been able to get my brain back into the kerning. I hope I’ve understood your comment above correctly and have manually inserted multiplier values for the italicized masters in your post. When you used "dxtra" it is relative to the default value, when you used "lxtra" it is relative to the value that I had previously calculated. For example, where you wrote These values are currently hard-coded into the script, making it Amstelvar-specific. If there was some systematic logic you used to get these values that could be written into the script, let me know. A sample font is attached here and available on Amstelvar
|
How’s it look? :-)
|
Image shows default at the bottom and use of scaling kerning using XTRA:
Default XTRA/100 = Extreme XTRA/n
Default Kern x n = Extreme Kern
The text was updated successfully, but these errors were encountered: