You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Below is a comparison of Alegreya Sans (Regular) between the version that was uploaded to FontSquirrel and the latest version from GitHub:
In typographically-minded software, one can correct for this difference by explicitly setting the desired line height. However, not all software provides this level of control, relying solely on the metadata of the font to be correct. And it seems that metadata for the fonts were correct at some point in the past, though the repository here only has data for the new version.
Using the older font version is a temporary workaround, however that means giving up the improvements to the font in the intervening years. Also this same issue occurs with the serif version of Alegreya (perhaps related to huertatipografica/Alegreya#24), but the older submission to FontSquirrel did not include all the weights that are available today.
The text was updated successfully, but these errors were encountered:
Below is a comparison of Alegreya Sans (Regular) between the version that was uploaded to FontSquirrel and the latest version from GitHub:
In typographically-minded software, one can correct for this difference by explicitly setting the desired line height. However, not all software provides this level of control, relying solely on the metadata of the font to be correct. And it seems that metadata for the fonts were correct at some point in the past, though the repository here only has data for the new version.
Using the older font version is a temporary workaround, however that means giving up the improvements to the font in the intervening years. Also this same issue occurs with the serif version of Alegreya (perhaps related to huertatipografica/Alegreya#24), but the older submission to FontSquirrel did not include all the weights that are available today.
The text was updated successfully, but these errors were encountered: