-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Gulzar: Version 1.000;[57fe3b0]; ttfautohint (v1.8.4) added #4674
Conversation
….4) added * Gulzar Version 1.000;[57fe3b0]; ttfautohint (v1.8.4) taken from the upstream repo https://github.com/simoncozens/Gulzar at commit googlefonts/Gulzar@7f73671.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
U+02BC is not part of GF Latin Core, so add-font is doing something wrong, but I will remove those languages from the METADATA. |
This comment was marked as outdated.
This comment was marked as outdated.
Arabic subset was not detected because we don't have the presentation form glyphs. I'll add it manually to METADATA, as well as crediting two more designers. |
This comment was marked as outdated.
This comment was marked as outdated.
all languages should be removed from metadata.pb (except for Noto), they do that in prod now. (gftools has been upgraded accordingly) |
Fontbakery reportFontbakery version: 0.8.8 [1] Family checksℹ INFO: Check axis ordering on the STAT table. (com.google.fonts/check/STAT/axis_order)
[21] Gulzar-Regular.ttf⚠ WARN: Are there caret positions declared for every ligature? (com.google.fonts/check/ligature_carets)
⚠ WARN: Is there kerning info for non-ligated sequences? (com.google.fonts/check/kerning_for_non_ligated_sequences)
⚠ WARN: METADATA.pb: Designers are listed correctly on the Google Fonts catalog? (com.google.fonts/check/metadata/designer_profiles)
⚠ WARN: Ensure fonts have ScriptLangTags declared on the 'meta' table. (com.google.fonts/check/meta/script_lang_tags)
⚠ WARN: Font contains '.notdef' as its first glyph? (com.google.fonts/check/mandatory_glyphs)
⚠ WARN: Check if each glyph has the recommended amount of contours. (com.google.fonts/check/contour_count)
The following glyphs do not have the recommended number of contours:
[code: contour-count] ⚠ WARN: Ensure dotted circle glyph is present and can attach marks. (com.google.fonts/check/dotted_circle)
⚠ WARN: Font has correct post table version? (com.google.fonts/check/post_table_version)
⚠ WARN: Check mark characters are in GDEF mark glyph class. (com.google.fonts/check/gdef_mark_chars)
⚠ WARN: Do any segments have colinear vectors? (com.google.fonts/check/outline_colinear_vectors)
Use -F or --full-lists to disable shortening of long lists. [code: found-colinear-vectors] ⚠ WARN: Do outlines contain any jaggy segments? (com.google.fonts/check/outline_jaggy_segments)
⚠ WARN: Do outlines contain any semi-vertical or semi-horizontal lines? (com.google.fonts/check/outline_semi_vertical)
ℹ INFO: Does DESCRIPTION file contain a upstream Git repo URL? (com.google.fonts/check/description/git_url)
ℹ INFO: Show hinting filesize impact. (com.google.fonts/check/hinting_impact)
ℹ INFO: EPAR table present in font? (com.google.fonts/check/epar)
ℹ INFO: Is the Grid-fitting and Scan-conversion Procedure ('gasp') table set to optimize rendering? (com.google.fonts/check/gasp)
PPM <= 65535: ℹ INFO: Check for font-v versioning. (com.google.fonts/check/fontv)
ℹ INFO: Check samples can be rendered. (com.google.fonts/check/metadata/can_render_samples)
ℹ INFO: Font contains all required tables? (com.google.fonts/check/required_tables)
ℹ INFO: List all superfamily filepaths (com.google.fonts/check/superfamily/list)
ℹ INFO: Check if OS/2 xAvgCharWidth is correct. (com.google.fonts/check/xavgcharwidth)
Note: The following loglevels were omitted in this report:
|
9a986e6: [gftools-packager] Gulzar: Version 1.000;[57fe3b0]; ttfautohint (v1.8.4) added
closes #4367