search

TypeNetwork / variable-fonts-info-site

A brochure website to demonstrate the benefits of variable fonts
https://variablefonts.typenetwork.com
Apache License 2.0
36 stars 12 forks source link

Brochure wide linespacing rules #71

Open dberlow opened 5 years ago

dberlow commented 5 years ago

Started in issue 68, Making this a separate issue for broader comment:

  1. A lot of the examples I have made for specimens in the brochure are done in typetools
  2. i don’t have complete control over linespacing in type tools. Each tagged text type is a seperate block, as opposed to being continuous. (Not the issue though)
  3. The effectiveness of style selection in quality composition depends on their general proximity, a big part of which is proper linespacing if it exists between the selected styles. So, e.g. Effectively Using a black condensed big, bold dub and lighter text, successively down a page, depends on systematically good linespacing among them, besides for each style.
  4. So, for this brochure, no matter what condition the linespacing of one of my example specimens may be, I’d like to have global use of the linespacing outlined here for 64 character columns and sizes, to be used, improved, expanded, and exceptions made where better. 48ac4c40-bda8-49d7-8bb9-18229da86850

I understand that Chris worked out a formula for linespacing changes over column width, and that needs to please be added to this issue.

... Thanks

ghost commented 5 years ago

I will apply this to all Amstelvar examples. What to do for examples showing a font that doesn't have YOPQ? Use a stand-in value like 100?

Also do you have any adjustments to make to the algorithm? The current values look quite tightly spaced to my eye, but then I am not an expert :)

dberlow commented 5 years ago

I do have adjustments to make at the bottom end.

For a fallback yopq value, I’d just return to 120% of size at 64-chars wide, 12pt, Shrinking to 100% at 72 point.

On Mar 6, 2019, at 12:24 PM, Chris Lewis notifications@github.com wrote:

I will apply this to all Amstelvar examples. What to do for examples showing a font that doesn't have YOPQ? Use a stand-in value like 100?

Also do you have any adjustments to make to the algorithm? The current values look quite tightly spaced to my eye, but then I am not an expert :)

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

ghost commented 5 years ago

I believe this is working now. Looking at e.g. optical size in body text you see the line heights changing (though only at 12pt and below?).