-
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
Noto Serif HK: Version 2.001-H2 added #5535
Conversation
Fontbakery reportFontbakery version: 0.8.11a3 [1] Family checksℹ INFO: Check axis ordering on the STAT table. (com.google.fonts/check/STAT/axis_order)
[31] NotoSerifHK[wght].ttf💔 ERROR: Check samples can be rendered. (com.google.fonts/check/metadata/can_render_samples)
🔥 FAIL: Check Google Fonts glyph coverage. (com.google.fonts/check/glyph_coverage)
Use -F or --full-lists to disable shortening of long lists. [code: missing-codepoints] 🔥 FAIL: Check for METADATA subsets with zero support. (com.google.fonts/check/metadata/unsupported_subsets)
🔥 FAIL: Check license file has good copyright string. (com.google.fonts/check/license/OFL_copyright)
"copyright 2014-2021 adobe (http://www.adobe.com/), with reserved font name 'source'" which does not match the expected format, similar to: "Copyright 2022 The Familyname Project Authors (git url)" [code: bad-format] 🔥 FAIL: Ensure files are not too large. (com.google.fonts/check/file_size)
🔥 FAIL: Copyright notices match canonical pattern in METADATA.pb (com.google.fonts/check/metadata/valid_copyright)
🔥 FAIL: Copyright notices match canonical pattern in fonts (com.google.fonts/check/font_copyright)
🔥 FAIL: Copyright field for this font on METADATA.pb matches all copyright notice entries on the name table ? (com.google.fonts/check/metadata/nameid/copyright)
🔥 FAIL: Check if the vertical metrics of a CJK family are similar to the same family hosted on Google Fonts. (com.google.fonts/check/cjk_vertical_metrics_regressions)
🔥 FAIL: METADATA.pb: Designers are listed correctly on the Google Fonts catalog? (com.google.fonts/check/metadata/designer_profiles)
🔥 FAIL: Ensure dotted circle glyph is present and can attach marks. (com.google.fonts/check/dotted_circle)
⚠ WARN: License URL matches License text on name table? (com.google.fonts/check/name/license_url)
⚠ WARN: METADATA.pb: Fontfamily is listed on Google Fonts API? (com.google.fonts/check/metadata/listed_on_gfonts)
⚠ WARN: Copyright notice on METADATA.pb should not contain 'Reserved Font Name'. (com.google.fonts/check/metadata/reserved_font_name)
⚠ 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: Combined length of family and style must not exceed 27 characters. (com.google.fonts/check/name/family_and_style_max_length)
Please take a look at the conversation at fonttools/fontbakery#2179 in order to understand the reasoning behind these name table records max-length criteria. [code: too-long] ⚠ WARN: A static fonts directory with at least two fonts must accompany variable fonts (com.google.fonts/check/repo/vf_has_static_fonts)
⚠ WARN: Ensure fonts have ScriptLangTags declared on the 'meta' table. (com.google.fonts/check/meta/script_lang_tags)
⚠ WARN: Check font contains no unreachable glyphs (com.google.fonts/check/unreachable_glyphs)
Use -F or --full-lists to disable shortening of long lists. ⚠ WARN: Does the font contain chws and vchw features? (com.google.fonts/check/cjk_chws_feature)
⚠ WARN: Detect any interpolation issues in the font. (com.google.fonts/check/interpolation_issues)
⚠ 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)
ℹ INFO: Show hinting filesize impact. (com.google.fonts/check/hinting_impact)
ℹ INFO: Font has old ttfautohint applied? (com.google.fonts/check/old_ttfautohint)
ℹ 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: Font contains all required tables? (com.google.fonts/check/required_tables)
ℹ INFO: List all superfamily filepaths (com.google.fonts/check/superfamily/list)
Summary
Note: The following loglevels were omitted in this report:
|
@simoncozens Noto Sans HK supports |
Looks like linespacing has increased Enregistrement.de.l.ecran.2022-11-16.a.12.33.04.mov |
Linespacing issue is deliberate. Noto CJK statics from upstream have ascent=1160,descent=-288 but the upstream VFs have ascent=1000,descent=-200. As we are now updating Noto Sans CJK from static to VF, we are hotfixing the VFs to have compatible vertical metrics with the static versions. But Noto Serif CJK was originally added as a VF before we knew about the static/VF metrics difference, so it was onboarded with the tighter VF metrics. I think it's better to hotfix the metrics here as well, so that Serif and Sans have compatible metrics. |
Please hold this one for now. There was another (slight) vertical metrics problem as I made the metrics compatible with the old sans, not from the old serif. |
Shouldn't it be similar to new Sans, so the entire CJK family has the same v-metrics? |
I don't think so. Upstream deliberately has slightly different metrics for Sans and Serif, and they always have had it like this. I don't know why (@punchcutter?) but my plan was to try to avoid regressions between Serif 1.0 and 2.0 by keeping the metrics the same. |
At the time I'm not sure it was considered. Same for a lot of other things like variable fonts which didn't exist in the current state when this project was started. The CJK have always been a little odd and don't conform to all the new Noto rules that have evolved over the years. |
Metadata change here is different to the Sans versions; not sure why...