Skip to content
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

The variable font origin should be Regular #36

Closed
vv-monsalve opened this issue Apr 19, 2024 · 3 comments
Closed

The variable font origin should be Regular #36

vv-monsalve opened this issue Apr 19, 2024 · 3 comments
Assignees

Comments

@vv-monsalve
Copy link
Collaborator

@simoncozens, the following Fail is reported for Playwrite ES Deco, but it is caused by the fact that the current font origin is Thin and should be Regular, for all the fonts.

🔥 FAIL Combined length of family and style must not exceed 32 characters.

This check ensures that the length of name table entries is not
too long, as this causes problems in some environments.

Original proposal: fonttools/fontbakery#1488
See also: fonttools/fontbakery#2179

  • 🔥 FAIL

    Variable font instance name 'Playwrite ES Deco Thin ExtraLight' formed by space-separated concatenation of font family name (nameID 1) and instance subfamily nameID 285 exceeds 32 characters.

This has been found to cause shaping issues for some accented letters in Microsoft Word on Windows 10 and 11.

[code: instance-too-long]
@simoncozens
Copy link
Collaborator

Looks like @casasin removed the "Variable Font Origin" custom parameter in the last commit.

@casasin I am going to avoid touching the sources now - there should be a custom parameter "Variable Font Origin" with value "Reg 00 Short Slow" in the main font info; please put it back!

@simoncozens simoncozens assigned casasin and unassigned simoncozens Apr 19, 2024
@casasin
Copy link
Collaborator

casasin commented Apr 19, 2024

It seems with the last upd

Looks like @casasin removed the "Variable Font Origin" custom parameter in the last commit.

Not really. I'll talk with the designers to assure nothing else gets touched than whatever is updated.

@casasin
Copy link
Collaborator

casasin commented Apr 19, 2024

This has been fixed.

@casasin casasin closed this as completed Apr 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants