Anek Gujarati: Version 1.003 added

[yanone]

7cbcf26: [gftools-packager] Anek Gujarati: Version 1.003 added

• Anek Gujarati Version 1.003 taken from the upstream repo https://github.com/EkType/Anek at commit EkType/Anek@634384a.

269dfee: [gftools-packager] ofl/anekgujarati remove METADATA "source". #2587

[gf-bot]

Fontbakery report

Fontbakery version: 0.8.6

[10] AnekGujarati[wdth,wght].ttf

🔥 FAIL: Does DESCRIPTION file contain broken links?

• com.google.fonts/check/description/broken_links

--- Rationale ---
The snippet of HTML in the DESCRIPTION.en_us.html file is added to the font
family webpage on the Google Fonts website. For that reason, all hyperlinks in
it must be properly working.

• 🔥 FAIL The following links are broken in the DESCRIPTION file:
  /?query=Anek [code: broken-links]

🔥 FAIL: DESCRIPTION.en_us.html must have less than 2000 bytes.

• com.google.fonts/check/description/max_length

--- Rationale ---
The fonts.google.com catalog specimen pages 2016 to 2020 were placed in a narrow
area of the page.
That meant a maximum limit of 1,000 characters was good, so that the narrow
column did not extent that section of the page to be too long.
But with the "v4" redesign of 2020, the specimen pages allow for longer texts
without upsetting the balance of the page.
So currently the limit before warning is 2,000 characters.

• 🔥 FAIL DESCRIPTION.en_us.html must have size smaller than 2000 bytes. [code: too-long]

🔥 FAIL: Check `Google Fonts Latin Core` glyph coverage.

• com.google.fonts/check/glyph_coverage

--- Rationale ---
Google Fonts expects that fonts in its collection support at least the minimal
set of characters defined in the `GF-latin-core` glyph-set.

• 🔥 FAIL Missing required codepoints:

  • 0x02BB (MODIFIER LETTER TURNED COMMA)

  • 0x02BC (MODIFIER LETTER APOSTROPHE)

  • 0x2002 (EN SPACE)

  • 0x2032 (PRIME)

  • 0x2033 (DOUBLE PRIME)

  • 0x2122 (TRADE MARK SIGN)

  • 0x2191 (UPWARDS ARROW)

  • 0x2193 (DOWNWARDS ARROW)

  • 0xFEFF (ZERO WIDTH NO-BREAK SPACE)

  • And 0xFFFD (REPLACEMENT CHARACTER)
    [code: missing-codepoints]

⚠ WARN: DESCRIPTION.en_us.html should end in a linebreak.

• com.google.fonts/check/description/eof_linebreak

--- Rationale ---
Some older text-handling tools sometimes misbehave if the last line of data in a
text file is not terminated with a newline character (also known as '\n').
We know that this is a very small detail, but for the sake of keeping all
DESCRIPTION.en_us.html files uniformly formatted throughout the GFonts
collection, we chose to adopt the practice of placing this final linebreak char
on them.

• ⚠ WARN The last characther on DESCRIPTION.en_us.html is not a line-break. Please add it. [code: missing-eof-linebreak]

⚠ WARN: Ensure files are not too large.

• com.google.fonts/check/file_size

--- Rationale ---
Serving extremely large font files on Google Fonts causes usability issues. This
check ensures that file sizes are reasonable.

• ⚠ WARN Font file is 1.5Mb; ideally it should be less than 1.0Mb [code: large-font]

⚠ WARN: Is there kerning info for non-ligated sequences?

• com.google.fonts/check/kerning_for_non_ligated_sequences

--- Rationale ---
Fonts with ligatures should have kerning on the corresponding non-ligated
sequences for text where ligatures aren't used (eg
https://github.com/impallari/Raleway/issues/14).

• ⚠ WARN GPOS table lacks kerning info for the following non-ligated sequences:

  • f + f
  • f + i
  • i + f
  • f + l
  • l + f
  • i + l

  [code: lacks-kern-info]

⚠ WARN: A static fonts directory with at least two fonts must accompany variable fonts

• com.google.fonts/check/repo/vf_has_static_fonts

--- Rationale ---
Variable font family directories kept in the google/fonts git repo may include a
static/ subdir containing static fonts.
These files are meant to be served for users that still lack support for
variable fonts in their web browsers.

• ⚠ WARN Please consider adding a subdirectory called "static/" and including in it static font files. [code: missing]

⚠ WARN: Ensure fonts have ScriptLangTags declared on the 'meta' table.

• com.google.fonts/check/meta/script_lang_tags

--- Rationale ---
The OpenType 'meta' table originated at Apple. Microsoft added it to OT with
just two DataMap records:
- dlng: comma-separated ScriptLangTags that indicate which scripts, or languages
and scripts, with possible variants, the font is designed for
- slng: comma-separated ScriptLangTags that indicate which scripts, or languages
and scripts, with possible variants, the font supports
The slng structure is intended to describe which languages and scripts the font
overall supports. For example, a Traditional Chinese font that also contains
Latin characters, can indicate Hant,Latn, showing that it supports Hant, the
Traditional Chinese variant of the Hani script, and it also supports the Latn
script
The dlng structure is far more interesting. A font may contain various glyphs,
but only a particular subset of the glyphs may be truly "leading" in the design,
while other glyphs may have been included for technical reasons. Such a
Traditional Chinese font could only list Hant there, showing that it’s designed
for Traditional Chinese, but the font would omit Latn, because the developers
don’t think the font is really recommended for purely Latin-script use.
The tags used in the structures can comprise just script, or also language and
script. For example, if a font has Bulgarian Cyrillic alternates in the locl
feature for the cyrl BGR OT languagesystem, it could also indicate in dlng
explicitly that it supports bul-Cyrl. (Note that the scripts and languages in
meta use the ISO language and script codes, not the OpenType ones).
This check ensures that the font has the meta table containing the slng and dlng
structures.
All families in the Google Fonts collection should contain the 'meta' table.
Windows 10 already uses it when deciding on which fonts to fall back to. The
Google Fonts API and also other environments could use the data for smarter
filtering. Most importantly, those entries should be added to the Noto fonts.
In the font making process, some environments store this data in external files
already. But the meta table provides a convenient way to store this inside the
font file, so some tools may add the data, and unrelated tools may read this
data. This makes the solution much more portable and universal.

• ⚠ WARN This font file does not have a 'meta' table. [code: lacks-meta-table]

⚠ WARN: Check font contains no unreachable glyphs

• com.google.fonts/check/unreachable_glyphs

--- Rationale ---
Glyphs are either accessible directly through Unicode codepoints or through
substitution rules. Any glyphs not accessible by either of these means are
redundant and serve only to increase the font's file size.

• ⚠ WARN The following glyphs could not be reached by codepoint or substitution rules:
  • LaHalf_alt2.gj
  • Chandrabindu1.gj
  • seven.subs
  • four.subs
  • zero.subs
  • five.subs
  • nine.subs
  • question_alt
  • NULL
  • tildecomb.narrow
  • And 8 more.

Use -F or --full-lists to disable shortening of long lists.
[code: unreachable-glyphs]

⚠ WARN: Are there any misaligned on-curve points?

• [com.google.fonts/check/outline_alignment_miss](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/<Section: Outline Correctness Checks>.html#com.google.fonts/check/outline_alignment_miss)

--- Rationale ---
This check heuristically looks for on-curve points which are close to, but do
not sit on, significant boundary coordinates. For example, a point which has a
Y-coordinate of 1 or -1 might be a misplaced baseline point. As well as the
baseline, here we also check for points near the x-height (but only for lower
case Latin letters), cap-height, ascender and descender Y coordinates.
Not all such misaligned curve points are a mistake, and sometimes the design may
call for points in locations near the boundaries. As this check is liable to
generate significant numbers of false positives, it will pass if there are more
than 100 reported misalignments.

• ⚠ WARN The following glyphs have on-curve points which have potentially incorrect y coordinates:
  • ampersand (U+0026): X=768.0,Y=1279.5 (should be at cap-height 1278?)
  • ampersand (U+0026): X=707.5,Y=1.0 (should be at baseline 0?)
  • six (U+0036): X=795.0,Y=1277.0 (should be at cap-height 1278?)
  • eight (U+0038): X=343.0,Y=-1.5 (should be at baseline 0?)
  • eight (U+0038): X=782.0,Y=-0.5 (should be at baseline 0?)
  • c (U+0063): X=678.5,Y=1.0 (should be at baseline 0?)
  • e (U+0065): X=746.5,Y=0.5 (should be at baseline 0?)
  • f (U+0066): X=337.0,Y=979.0 (should be at x-height 978?)
  • s (U+0073): X=233.0,Y=1.5 (should be at baseline 0?)
  • s (U+0073): X=636.0,Y=977.0 (should be at x-height 978?) and 48 more.

Use -F or --full-lists to disable shortening of long lists. [code: found-misalignments]

Summary

💔 ERROR	🔥 FAIL	⚠ WARN	💤 SKIP	ℹ INFO	🍞 PASS	🔎 DEBUG
0	3	7	51	9	152	0
0%	1%	3%	23%	4%	68%	0%

Note: The following loglevels were omitted in this report:

• SKIP
• INFO
• PASS
• DEBUG