Skip to content

[#4192] Add NanumBarunGothic 1.0#10194

Closed
monolith-jaehoon wants to merge 3 commits intogoogle:mainfrom
monolith-jaehoon:nanumbarungothic
Closed

[#4192] Add NanumBarunGothic 1.0#10194
monolith-jaehoon wants to merge 3 commits intogoogle:mainfrom
monolith-jaehoon:nanumbarungothic

Conversation

@monolith-jaehoon
Copy link

@monolith-jaehoon monolith-jaehoon commented Feb 9, 2026

I’m not sure whether it’s okay for me to open this PR, but I’m submitting it for now.
(about #4192)

@emmamarichal
Copy link
Collaborator

Thank you very much @monolith-jaehoon for your PR and your submission!
We truly appreciate your initiative in preparing this PR and doing your best to follow our specifications.

For font submissions, we usually go through an initial selection process by opening an issue in the repository: https://github.com/google/fonts/issues -> New Issue

I close that PR for now, and I'm waiting for your issue (feel free to ping me), and don't hesitate if you have any questions!
Have a nice day!

@monolith-jaehoon
Copy link
Author

Hi @emmamarichal, this PR is related to issue #4192. Should I open a new issue for the font submission?

@emmamarichal
Copy link
Collaborator

emmamarichal commented Feb 11, 2026

Ah, ok I see. Let me have a look then, I'm re-opening it for now

@emmamarichal emmamarichal reopened this Feb 11, 2026
@emmamarichal
Copy link
Collaborator

I just run fontspector on fonts, for now there are too many issues to merge that PR:

FontSpector report

fontspector version: 1.5.2

Checks with FATAL results

These must be addressed first.

[2] NanumBarunGothicUltraLight.ttf
💥 ERROR Familyname must be unique according to namecheck.fontdata.com (fontdata_namecheck)
💥 ERROR Check font follows the Google Fonts CJK vertical metric schema (googlefonts/cjk_vertical_metrics)
  • 💥 ERROR Error: Error reading font file: the GSUB table is missing
[1] NanumBarunGothic.ttf
💥 ERROR Familyname must be unique according to namecheck.fontdata.com (fontdata_namecheck)
[1] NanumBarunGothicLight.ttf
💥 ERROR Familyname must be unique according to namecheck.fontdata.com (fontdata_namecheck)
[1] NanumBarunGothicBold.ttf
💥 ERROR Familyname must be unique according to namecheck.fontdata.com (fontdata_namecheck)

All other checks

[33] NanumBarunGothicLight.ttf
🔥 FAIL Check name table for empty records. (opentype/name/empty_records)
  • 🔥 FAIL Empty name record found for name ID=COPYRIGHT_NOTICE platform ID=1 encoding ID=3 [code: empty-record]

  • 🔥 FAIL Empty name record found for name ID=FAMILY_NAME platform ID=1 encoding ID=3 [code: empty-record]

  • 🔥 FAIL Empty name record found for name ID=SUBFAMILY_NAME platform ID=1 encoding ID=3 [code: empty-record]

  • 🔥 FAIL Empty name record found for name ID=FULL_NAME platform ID=1 encoding ID=3 [code: empty-record]

  • 🔥 FAIL Empty name record found for name ID=DESIGNER platform ID=1 encoding ID=3 [code: empty-record]

  • 🔥 FAIL Empty name record found for name ID=COMPATIBLE_FULL_NAME platform ID=1 encoding ID=3 [code: empty-record]

  • 🔥 FAIL Empty name record found for name ID=POSTSCRIPT_CID_NAME platform ID=1 encoding ID=3 [code: empty-record]

🔥 FAIL Ensure the font supports case swapping for all its glyphs. (case_mapping)
  • 🔥 FAIL The following glyphs are missing case-swapping counterparts:
Glyph present in the font Missing case-swapping counterpart
U+212B: ANGSTROM SIGN U+00E5: LATIN SMALL LETTER A WITH RING ABOVE
U+0111: LATIN SMALL LETTER D WITH STROKE U+0110: LATIN CAPITAL LETTER D WITH STROKE
🔥 FAIL Does font file include unacceptable control character glyphs? (control_chars)
  • 🔥 FAIL The following unacceptable control characters were identified:
  • U+0001 (cid19326)
  • U+0002 (cid19327)
  • U+0003 (cid19328)
  • U+0004 (cid19329)
  • U+0005 (cid19330)
  • U+0006 (cid19331)
  • U+0007 (cid19332)
  • U+0008 (cid19333)
  • U+0009 (cid19334)
    ... and 20 others [code: unacceptable]
🔥 FAIL Font contains '.notdef' as its first glyph? (mandatory_glyphs)
  • 🔥 FAIL The '.notdef' glyph should contain a drawing, but it is blank. [code: notdef-is-blank]
🔥 FAIL Ensure smart dropout control is enabled in "prep" table instructions. (smart_dropout)
  • 🔥 FAIL The 'prep' table does not contain TrueType instructions enabling smart dropout control. To fix, export the font with autohinting enabled, or run ttfautohint on the font, or run the gftools fix-nonhinting script. [code: lacks-smart-dropout]
🔥 FAIL Are there unwanted tables? (unwanted_tables)
  • 🔥 FAIL Unwanted tables found:
    Table: FFTM Reason: Table contains redundant FontForge timestamp info
    [code: unwanted-tables]
🔥 FAIL Glyph names are all valid? (valid_glyphnames)
  • 🔥 FAIL Glyph 0x0020 is called cid1; must be named 'space'. [code: non-compliant-0020]
🔥 FAIL Whitespace glyphs have ink? (whitespace_ink)
  • 🔥 FAIL The following glyphs have ink; they should be replaced by an empty glyph:
  • cid101 [code: has-ink]
🔥 FAIL Check family name for GF Guide compliance. (googlefonts/name/family_name_compliance)
  • 🔥 FAIL "NanumBarunGothic" is a CamelCased name. To solve this, simply use spaces instead in the font name. [code: camelcase]
🔥 FAIL Checking file is named canonically. (googlefonts/canonical_filename)
  • 🔥 FAIL Expected "NanumBarunGothic-Light.ttf". Got "NanumBarunGothicLight.ttf". [code: bad-filename]
🔥 FAIL Check font follows the Google Fonts CJK vertical metric schema (googlefonts/cjk_vertical_metrics)
  • 🔥 FAIL OS/2 fsSelection bit 7 must be enabled [code: bad-fselection-bit7]

  • 🔥 FAIL OS/2.sTypoAscender is 850; it should be between 884 and 934 [code: bad-OS/2.sTypoAscender]

  • 🔥 FAIL OS/2.sTypoDescender is -300; it should be between -266 and -216 [code: bad-OS/2.sTypoDescender]

  • 🔥 FAIL OS/2.usWinAscent is 850; it should be 838 [code: bad-OS/2.usWinAscent]

  • 🔥 FAIL OS/2.usWinDescent is 299; it should be 283 [code: bad-OS/2.usWinDescent]

  • 🔥 FAIL hhea.descent must match absolute value of OS/2.sTypoDescender [code: descent-mismatch]

  • 🔥 FAIL A BASE table with correct icfb/icft/ideo/romn and idtp baselines should be present [code: missing-BASE-table]

  • 🔥 FAIL A vmtx table should be present [code: missing-vmtx-table]

  • 🔥 FAIL A vhea table should be present [code: missing-vhea-table]

  • ℹ️ INFO Computed BASE table entries:

Baseline Computed
Horizontal icfb -102
Horizontal icft 769
Horizontal ideo -166
Horizontal idtp 833
Horizontal romn 0
Vertical icfb 39
Vertical icft 851
Vertical ideo 0
Vertical idtp 892
Vertical romn 166
🔥 FAIL Check font names are correct (googlefonts/font_names)
  • 🔥 FAIL Font names are incorrect:
Name Current Expected
Family Name NanumBarunGothic Light NanumBarunGothic Light
Subfamily Name Light Regular
Full Name NanumBarunGothic Light NanumBarunGothic Light
Postscript Name NanumBarunGothicLight NanumBarunGothic-Light
Typographic Family Name NanumBarunGothic NanumBarunGothic
Typographic Subfamily Name Light Light
🔥 FAIL Checking OS/2 fsType does not impose restrictions. (googlefonts/fstype)
  • 🔥 FAIL In this font fsType is set to 4 meaning that:
  • The font may be embedded, and temporarily loaded on the remote system, but documents that use it must not be editable.

No such DRM restrictions can be enabled on the Google Fonts collection, so the fsType field must be set to zero (Installable Embedding) instead. [code: drm]

🔥 FAIL Font has all mandatory 'name' table entries? (googlefonts/name/mandatory_entries)
  • 🔥 FAIL Font lacks entry with nameId=1 (FAMILY_NAME) [code: missing-entry]

  • 🔥 FAIL Font lacks entry with nameId=2 (SUBFAMILY_NAME) [code: missing-entry]

  • 🔥 FAIL Font lacks entry with nameId=4 (FULL_NAME) [code: missing-entry]

  • 🔥 FAIL Font lacks entry with nameId=9 (DESIGNER) [code: missing-entry]

⚠️ WARN Check for points out of bounds (opentype/points_out_of_bounds)
  • ⚠️ WARN The following glyphs have coordinates which are out of bounds:
  • cid75 (y=-283, bounds are -280<->738)
  • cid2819 (y=759, bounds are -134<->758)
  • cid2819 (y=759, bounds are -134<->758)
  • cid2820 (y=755, bounds are -117<->754)
  • cid2820 (y=755, bounds are -117<->754)
  • cid2821 (y=759, bounds are -127<->758)
  • cid2821 (y=759, bounds are -127<->758)
  • cid2822 (y=759, bounds are -117<->758)
  • cid2822 (y=759, bounds are -117<->758)
    ... and 500 others

This happens a lot when points are not extremes, which is usually bad. However, fixing this alert by adding points on extremes may do more harm than good, especially with italics, calligraphic-script, handwriting, rounded and other fonts. So it is common to ignore this message. [code: points-out-of-bounds]

⚠️ WARN Checking OS/2 fsSelection value. (opentype/xavgcharwidth)
  • ⚠️ WARN OS/2 xAvgCharWidth is 885 but it should be 912 which corresponds to the average of the widths of all glyphs in the font. This may indicate a problem with the font editor or the font compiler. [code: xAvgCharWidth-wrong]
⚠️ WARN Does the font contain chws and vchw features? (cjk_chws_feature)
⚠️ WARN Check if each glyph has the recommended amount of contours. (contour_count)
  • ⚠️ WARN This check inspects the glyph outlines and detects the total number of contours in each of them. The expected values are
    inferred from the typical amounts of contours observed in a
    large collection of reference font families. The divergences
    listed below may simply indicate a significantly different
    design on some of your glyphs. On the other hand, some of these
    may flag actual bugs in the font such as glyphs mapped to an
    incorrect codepoint. Please consider reviewing the design and
    codepoint assignment of these to make sure they are correct.

    The following glyphs do not have the recommended number of contours:

  • cid61 (U+005C): found 4, expected one of: {1, 5}
  • cid379 (U+3146): found 2, expected one of: {1, 4}
  • cid398 (U+3159): found 3, expected one of: {1, 2, 4}
  • cid399 (U+315A): found 3, expected one of: {1, 4, 2}
  • cid404 (U+315F): found 3, expected one of: {2, 1, 7}
  • cid2381 (U+C384): found 4, expected one of: {7, 3, 2}
  • cid2406 (U+C464): found 3, expected one of: {15, 2, 6}
  • cid2419 (U+C4F0): found 3, expected one of: {5, 2}
  • cid2420 (U+C4F1): found 4, expected one of: {1, 7, 3}
    ... and 36 others [code: contour-count]
⚠️ WARN Ensure files are not too large. (file_size)
  • ⚠️ WARN Font file is 4.92 MB; ideally it should be less than 1.05 MB [code: large-font]
⚠️ WARN Check math signs have the same width. (math_signs_width)
  • ⚠️ WARN The most common width is 892 among a set of 74 math glyphs.
    The following math glyphs have a different width, though:
    width=446: cid31, cid29
    width=583: cid12, cid30 [code: width-outliers]
⚠️ WARN Ensure indic fonts have the Indian Rupee Sign glyph. (rupee)
  • ⚠️ WARN Font is missing the Indian Rupee Sign glyph. Please add a glyph for Indian Rupee Sign (₹) at codepoint U+20B9. [code: missing-rupee]
⚠️ WARN Does the font contain a soft hyphen? (soft_hyphen)
  • ⚠️ WARN This font has a 'Soft Hyphen' character. [code: softhyphen]
⚠️ WARN Check font contains no unreachable glyphs (unreachable_glyphs)
  • ⚠️ WARN The following glyphs could not be reached by codepoint or substitution rules:
  • .null
  • nonmarkingreturn
  • NULL [code: unreachable-glyphs]
⚠️ WARN Font has correct separator glyphs? (googlefonts/separator_glyphs)
  • ⚠️ WARN The following separator glyphs are missing:
  • U+2028
  • U+2029 [code: missing-separator-glyphs]
⚠️ WARN Check the direction of the outermost contour in each glyph (outline_direction)
  • ⚠️ WARN The following glyphs have a counter-clockwise outer contour:
  • cid89 (U+0078) has a counter-clockwise outer contour
  • cid94 (U+007D) has a counter-clockwise outer contour
  • cid1769 (U+B809) has a counter-clockwise outer contour
  • cid1769 (U+B809) has a counter-clockwise outer contour
  • cid1769 (U+B809) has a counter-clockwise outer contour
  • cid1769 (U+B809) has a counter-clockwise outer contour
  • cid2442 (U+C549) has a counter-clockwise outer contour
  • cid2442 (U+C549) has a counter-clockwise outer contour
  • cid2442 (U+C549) has a counter-clockwise outer contour
    ... and 510 others [code: ccw-outer-contour]
⚠️ WARN Do outlines contain any jaggy segments? (outline_jaggy_segments)
  • ⚠️ WARN The following glyphs have jaggy segments:
  • cid261 (U+33C2): Line(Line { p0: (450.0, 464.0), p1: (451.0, 365.0) })/Quad(QuadBez { p0: (451.0, 365.0), p1: (455.0, 387.0), p2: (461.0, 406.5) }) = 10.883572034373836
  • cid262 (U+33D8): Line(Line { p0: (450.0, 464.0), p1: (451.0, 365.0) })/Quad(QuadBez { p0: (451.0, 365.0), p1: (455.0, 387.0), p2: (461.0, 406.5) }) = 10.883572034373836
  • cid482 (U+039C): Line(Line { p0: (590.0, -64.0), p1: (747.0, 615.0) })/Line(Line { p0: (747.0, 615.0), p1: (409.0, -64.0) }) = 13.444437178982044
  • cid506 (U+03BC): Quad(QuadBez { p0: (160.5, 3.0), p1: (150.0, 18.0), p2: (150.0, 31.0) })/Line(Line { p0: (150.0, 31.0), p1: (116.0, -122.0) }) = 12.52880770915152
  • cid518 (U+03C9): Quad(QuadBez { p0: (286.0, 8.0), p1: (275.0, 29.0), p2: (279.0, 53.0) })/Quad(QuadBez { p0: (279.0, 53.0), p1: (272.0, 33.0), p2: (258.0, 14.0) }) = 9.827724011163108
  • cid626 (U+33B9): Line(Line { p0: (429.0, -70.0), p1: (429.0, 558.0) })/Line(Line { p0: (429.0, 558.0), p1: (296.0, -70.0) }) = 11.957611527896637
  • cid626 (U+33B9): Line(Line { p0: (226.0, -70.0), p1: (97.0, 556.0) })/Line(Line { p0: (97.0, 556.0), p1: (97.0, -70.0) }) = 11.643963611577066
  • cid637 (U+33BF): Line(Line { p0: (347.0, -68.0), p1: (347.0, 519.0) })/Line(Line { p0: (347.0, 519.0), p1: (244.0, -68.0) }) = 9.952287964865901
  • cid637 (U+33BF): Line(Line { p0: (186.0, -68.0), p1: (87.0, 514.0) })/Line(Line { p0: (87.0, 514.0), p1: (87.0, -68.0) }) = 9.653786088536501
    ... and 1245 others [code: found-jaggy-segments]
⚠️ WARN Check there are no overlapping path segments (overlapping_path_segments)
  • ⚠️ WARN The following glyphs have overlapping path segments:
  • cid3610 (U+8E47): Quad(QuadBez { p0: (234.0, 140.0), p1: (234.0, 139.0), p2: (235.0, 139.0) }) has the same coordinates as a previous segment.
  • cid3610 (U+8E47): Quad(QuadBez { p0: (235.0, 139.0), p1: (236.0, 138.0), p2: (237.0, 138.0) }) has the same coordinates as a previous segment.
  • cid3706 (U+5553): Quad(QuadBez { p0: (408.0, 252.0), p1: (408.0, 251.0), p2: (408.5, 250.0) }) has the same coordinates as a previous segment.
  • cid3706 (U+5553): Line(Line { p0: (408.0, 249.0), p1: (409.0, 248.0) }) has the same coordinates as a previous segment.
  • cid4264 (U+968A): Line(Line { p0: (348.0, 346.0), p1: (349.0, 345.0) }) has the same coordinates as a previous segment.
  • cid4264 (U+968A): Quad(QuadBez { p0: (349.0, 345.0), p1: (349.0, 344.0), p2: (350.0, 344.0) }) has the same coordinates as a previous segment.
  • cid4404 (U+7C43): Quad(QuadBez { p0: (161.0, 789.0), p1: (161.0, 788.0), p2: (162.0, 788.0) }) has the same coordinates as a previous segment.
  • cid4428 (U+5006): Line(Line { p0: (25.0, 361.0), p1: (24.0, 362.0) }) has the same coordinates as a previous segment.
  • cid4488 (U+F9A7): Line(Line { p0: (34.0, 478.0), p1: (35.0, 479.0) }) has the same coordinates as a previous segment.
    ... and 30 others [code: overlapping-path-segments]
⚠️ WARN Do outlines contain any semi-vertical or semi-horizontal lines? (outline_semi_vertical)
  • ⚠️ WARN The following glyphs have semi-vertical/semi-horizontal lines:
  • cid372 (U+313F): Line(Line { p0: (730.0, 491.0), p1: (727.0, 119.0) })
  • cid372 (U+313F): Line(Line { p0: (514.0, 119.0), p1: (512.0, 493.0) })
  • cid372 (U+313F): Line(Line { p0: (565.0, 494.0), p1: (567.0, 118.0) })
  • cid372 (U+313F): Line(Line { p0: (674.0, 118.0), p1: (677.0, 494.0) })
  • cid1532 (U+B2F9): Line(Line { p0: (69.0, 331.0), p1: (68.0, 734.0) })
  • cid1532 (U+B2F9): Line(Line { p0: (126.0, 683.0), p1: (127.0, 382.0) })
  • cid1727 (U+B768): Line(Line { p0: (785.0, 271.0), p1: (784.0, 53.0) })
  • cid1767 (U+B807): Line(Line { p0: (718.0, 533.0), p1: (544.0, 534.0) })
  • cid1767 (U+B807): Line(Line { p0: (544.0, 586.0), p1: (718.0, 585.0) })
    ... and 1484 others [code: found-semi-vertical]
⚠️ WARN Is the Grid-fitting and Scan-conversion Procedure ('gasp') table set to optimize rendering? (googlefonts/gasp)
  • ℹ️ INFO These are the ppm ranges declared on the gasp table:
PPM <= 8 - Use grayscale rendering
PPM <= 16 - Use grid-fitting
PPM <= 65535 - Use grid-fitting
- Use grayscale rendering
[code: ranges]
  • ⚠️ WARN The gasp table has a range of 8 that may be unneccessary. [code: non-ffff-range]

  • ⚠️ WARN The gasp table has a range of 16 that may be unneccessary. [code: non-ffff-range]

  • ⚠️ WARN The gasp range 0xFFFF value 0x03 should be set to 0x0F. [code: unset-flags]

⚠️ WARN Ensure fonts have ScriptLangTags declared on the 'meta' table. (googlefonts/meta/script_lang_tags)
  • ⚠️ WARN This font file does not have a 'meta' table. [code: lacks-meta-table]
ℹ️ INFO Show hinting filesize impact. (hinting_impact)
  • ℹ️ INFO Hinting filesize impact:
NanumBarunGothicLight.ttf
Dehinted Size 3644144
Hinted Size 4917332
Increase 1273188
Change 34.9 %
ℹ️ INFO Font contains all required tables? (required_tables)
  • ℹ️ INFO This font contains the following optional tables:

    cvt
    fpgm
    loca
    prep
    GPOS
    GSUB
    gasp
    kern [code: optional-tables]

ℹ️ INFO Font has old ttfautohint applied? (googlefonts/old_ttfautohint)
  • ℹ️ INFO Could not detect which version of ttfautohint was used in this font. It is typically specified as a comment in the font version entries of the 'name' table. Such font version strings are currently: Version 1.0.0.3 Build 20140910, Version 1.0.0.3 Build 20140910 [code: version-not-detected]
[1] DESCRIPTION.en_us.html
🔥 FAIL Does DESCRIPTION file contain a upstream Git repo URL? (googlefonts/description/git_url)
  • 🔥 FAIL Please host your font project on a public Git repo (such as GitHub or GitLab) and place a link in the DESCRIPTION.en_us.html file. [code: lacks-git-url]
[33] NanumBarunGothicUltraLight.ttf
🔥 FAIL Check name table for empty records. (opentype/name/empty_records)
  • 🔥 FAIL Empty name record found for name ID=COPYRIGHT_NOTICE platform ID=1 encoding ID=3 [code: empty-record]

  • 🔥 FAIL Empty name record found for name ID=FAMILY_NAME platform ID=1 encoding ID=3 [code: empty-record]

  • 🔥 FAIL Empty name record found for name ID=SUBFAMILY_NAME platform ID=1 encoding ID=3 [code: empty-record]

  • 🔥 FAIL Empty name record found for name ID=FULL_NAME platform ID=1 encoding ID=3 [code: empty-record]

  • 🔥 FAIL Empty name record found for name ID=DESIGNER platform ID=1 encoding ID=3 [code: empty-record]

  • 🔥 FAIL Empty name record found for name ID=COMPATIBLE_FULL_NAME platform ID=1 encoding ID=3 [code: empty-record]

  • 🔥 FAIL Empty name record found for name ID=POSTSCRIPT_CID_NAME platform ID=1 encoding ID=3 [code: empty-record]

🔥 FAIL Ensure the font supports case swapping for all its glyphs. (case_mapping)
  • 🔥 FAIL The following glyphs are missing case-swapping counterparts:
Glyph present in the font Missing case-swapping counterpart
U+0111: LATIN SMALL LETTER D WITH STROKE U+0110: LATIN CAPITAL LETTER D WITH STROKE
U+212B: ANGSTROM SIGN U+00E5: LATIN SMALL LETTER A WITH RING ABOVE
🔥 FAIL Check if each glyph has the recommended amount of contours. (contour_count)
  • 🔥 FAIL The following glyphs have no contours even though they were expected to have some:
  • cid157 [code: no-contour]
  • ⚠️ WARN This check inspects the glyph outlines and detects the total number of contours in each of them. The expected values are
    inferred from the typical amounts of contours observed in a
    large collection of reference font families. The divergences
    listed below may simply indicate a significantly different
    design on some of your glyphs. On the other hand, some of these
    may flag actual bugs in the font such as glyphs mapped to an
    incorrect codepoint. Please consider reviewing the design and
    codepoint assignment of these to make sure they are correct.

    The following glyphs do not have the recommended number of contours:

  • cid61 (U+005C): found 4, expected one of: {1, 5}
  • cid379 (U+3146): found 2, expected one of: {1, 4}
  • cid398 (U+3159): found 3, expected one of: {1, 2, 4}
  • cid399 (U+315A): found 3, expected one of: {1, 4, 2}
  • cid404 (U+315F): found 3, expected one of: {2, 1, 7}
  • cid2381 (U+C384): found 4, expected one of: {7, 3, 2}
  • cid2406 (U+C464): found 3, expected one of: {15, 2, 6}
  • cid2419 (U+C4F0): found 3, expected one of: {5, 2}
  • cid2420 (U+C4F1): found 4, expected one of: {1, 7, 3}
    ... and 36 others [code: contour-count]
🔥 FAIL Does font file include unacceptable control character glyphs? (control_chars)
  • 🔥 FAIL The following unacceptable control characters were identified:
  • U+0001 (cid19326)
  • U+0002 (cid19327)
  • U+0003 (cid19328)
  • U+0004 (cid19329)
  • U+0005 (cid19330)
  • U+0006 (cid19331)
  • U+0007 (cid19332)
  • U+0008 (cid19333)
  • U+0009 (cid19334)
    ... and 20 others [code: unacceptable]
🔥 FAIL Font contains '.notdef' as its first glyph? (mandatory_glyphs)
  • 🔥 FAIL The '.notdef' glyph should contain a drawing, but it is blank. [code: notdef-is-blank]
🔥 FAIL Ensure smart dropout control is enabled in "prep" table instructions. (smart_dropout)
  • 🔥 FAIL The 'prep' table does not contain TrueType instructions enabling smart dropout control. To fix, export the font with autohinting enabled, or run ttfautohint on the font, or run the gftools fix-nonhinting script. [code: lacks-smart-dropout]
🔥 FAIL Are there unwanted tables? (unwanted_tables)
  • 🔥 FAIL Unwanted tables found:
    Table: FFTM Reason: Table contains redundant FontForge timestamp info
    [code: unwanted-tables]
🔥 FAIL Glyph names are all valid? (valid_glyphnames)
  • 🔥 FAIL Glyph 0x0020 is called cid1; must be named 'space'. [code: non-compliant-0020]
🔥 FAIL Whitespace glyphs have ink? (whitespace_ink)
  • 🔥 FAIL The following glyphs have ink; they should be replaced by an empty glyph:
  • cid101 [code: has-ink]
🔥 FAIL Check family name for GF Guide compliance. (googlefonts/name/family_name_compliance)
  • 🔥 FAIL "NanumBarunGothic" is a CamelCased name. To solve this, simply use spaces instead in the font name. [code: camelcase]
🔥 FAIL Checking file is named canonically. (googlefonts/canonical_filename)
  • 🔥 FAIL Expected "NanumBarunGothic-UltraLight.ttf". Got "NanumBarunGothicUltraLight.ttf". [code: bad-filename]
🔥 FAIL Check font names are correct (googlefonts/font_names)
  • 🔥 FAIL Font names are incorrect:
Name Current Expected
Family Name NanumBarunGothic UltraLight NanumBarunGothic UltraLight
Subfamily Name UltraLight Regular
Full Name NanumBarunGothic UltraLight NanumBarunGothic UltraLight Regular
Postscript Name NanumBarunGothicUltraLight NanumBarunGothicUltraLight-Regular
Typographic Family Name NanumBarunGothic 나눔바른고딕
Typographic Subfamily Name UltraLight UltraLight
  • ⚠️ WARN Regular missing from full name [code: lacks-regular]
🔥 FAIL Checking OS/2 fsType does not impose restrictions. (googlefonts/fstype)
  • 🔥 FAIL In this font fsType is set to 4 meaning that:
  • The font may be embedded, and temporarily loaded on the remote system, but documents that use it must not be editable.

No such DRM restrictions can be enabled on the Google Fonts collection, so the fsType field must be set to zero (Installable Embedding) instead. [code: drm]

🔥 FAIL Font has all mandatory 'name' table entries? (googlefonts/name/mandatory_entries)
  • 🔥 FAIL Font lacks entry with nameId=1 (FAMILY_NAME) [code: missing-entry]

  • 🔥 FAIL Font lacks entry with nameId=2 (SUBFAMILY_NAME) [code: missing-entry]

  • 🔥 FAIL Font lacks entry with nameId=4 (FULL_NAME) [code: missing-entry]

  • 🔥 FAIL Font lacks entry with nameId=9 (DESIGNER) [code: missing-entry]

⚠️ WARN Check for points out of bounds (opentype/points_out_of_bounds)
  • ⚠️ WARN The following glyphs have coordinates which are out of bounds:
  • cid75 (y=-281, bounds are -279<->736)
  • cid2819 (y=754, bounds are -132<->753)
  • cid2819 (y=754, bounds are -132<->753)
  • cid2820 (y=754, bounds are -115<->753)
  • cid2820 (y=754, bounds are -115<->753)
  • cid2821 (y=754, bounds are -125<->753)
  • cid2821 (y=754, bounds are -125<->753)
  • cid2822 (y=754, bounds are -115<->753)
  • cid2822 (y=754, bounds are -115<->753)
    ... and 567 others

This happens a lot when points are not extremes, which is usually bad. However, fixing this alert by adding points on extremes may do more harm than good, especially with italics, calligraphic-script, handwriting, rounded and other fonts. So it is common to ignore this message. [code: points-out-of-bounds]

⚠️ WARN Checking OS/2 fsSelection value. (opentype/xavgcharwidth)
  • ⚠️ WARN OS/2 xAvgCharWidth is 885 but it should be 914 which corresponds to the average of the widths of all glyphs in the font. This may indicate a problem with the font editor or the font compiler. [code: xAvgCharWidth-wrong]
⚠️ WARN Does the font contain chws and vchw features? (cjk_chws_feature)
⚠️ WARN Ensure files are not too large. (file_size)
  • ⚠️ WARN Font file is 4.82 MB; ideally it should be less than 1.05 MB [code: large-font]
⚠️ WARN Does GPOS table have kerning information? (gpos_kerning_info)
  • ⚠️ WARN GPOS table lacks kerning information. [code: lacks-kern-info]
⚠️ WARN Check math signs have the same width. (math_signs_width)
  • ⚠️ WARN The most common width is 892 among a set of 74 math glyphs.
    The following math glyphs have a different width, though:
    width=583: cid30, cid12
    width=446: cid29, cid31 [code: width-outliers]
⚠️ WARN Ensure indic fonts have the Indian Rupee Sign glyph. (rupee)
  • ⚠️ WARN Font is missing the Indian Rupee Sign glyph. Please add a glyph for Indian Rupee Sign (₹) at codepoint U+20B9. [code: missing-rupee]
⚠️ WARN Does the font contain a soft hyphen? (soft_hyphen)
  • ⚠️ WARN This font has a 'Soft Hyphen' character. [code: softhyphen]
⚠️ WARN Check font contains no unreachable glyphs (unreachable_glyphs)
  • ⚠️ WARN The following glyphs could not be reached by codepoint or substitution rules:
  • .null
  • nonmarkingreturn
  • NULL [code: unreachable-glyphs]
⚠️ WARN Font has correct separator glyphs? (googlefonts/separator_glyphs)
  • ⚠️ WARN The following separator glyphs are missing:
  • U+2028
  • U+2029 [code: missing-separator-glyphs]
⚠️ WARN Check the direction of the outermost contour in each glyph (outline_direction)
  • ⚠️ WARN The following glyphs have a counter-clockwise outer contour:
  • cid2806 (U+CA4D) has a counter-clockwise outer contour
  • cid2807 (U+CA50) has a counter-clockwise outer contour
  • cid2808 (U+CA54) has a counter-clockwise outer contour
  • cid2810 (U+CA5D) has a counter-clockwise outer contour
  • cid2811 (U+CA5F) has a counter-clockwise outer contour
  • cid2812 (U+CA60) has a counter-clockwise outer contour
  • cid2813 (U+CA61) has a counter-clockwise outer contour
  • cid3003 (U+CEF7) has a counter-clockwise outer contour
  • cid3081 (U+D0B7) has a counter-clockwise outer contour [code: ccw-outer-contour]
⚠️ WARN Do outlines contain any jaggy segments? (outline_jaggy_segments)
  • ⚠️ WARN The following glyphs have jaggy segments:
  • cid155 (U+00A7): Quad(QuadBez { p0: (194.0, 424.5), p1: (204.0, 423.0), p2: (206.0, 422.0) })/Quad(QuadBez { p0: (206.0, 422.0), p1: (133.0, 476.0), p2: (100.0, 517.5) }) = 9.926245506651707
  • cid482 (U+039C): Line(Line { p0: (596.0, -65.0), p1: (753.0, 620.0) })/Line(Line { p0: (753.0, 620.0), p1: (408.0, -65.0) }) = 13.823029509059236
  • cid506 (U+03BC): Quad(QuadBez { p0: (159.0, 2.5), p1: (148.0, 17.0), p2: (148.0, 30.0) })/Line(Line { p0: (148.0, 30.0), p1: (115.0, -122.0) }) = 12.249123419755827
  • cid518 (U+03C9): Quad(QuadBez { p0: (286.0, 8.0), p1: (275.0, 29.0), p2: (279.0, 53.0) })/Quad(QuadBez { p0: (279.0, 53.0), p1: (272.0, 33.0), p2: (258.0, 14.0) }) = 9.827724011163108
  • cid589 (U+3397): Line(Line { p0: (358.0, -77.0), p1: (358.0, 34.0) })/Quad(QuadBez { p0: (358.0, 34.0), p1: (344.0, -30.0), p2: (305.0, -58.0) }) = 12.33908727832618
  • cid589 (U+3397): Quad(QuadBez { p0: (313.0, 431.5), p1: (348.0, 404.0), p2: (358.0, 359.0) })/Line(Line { p0: (358.0, 359.0), p1: (358.0, 677.0) }) = 12.52880770915152
  • cid612 (U+3388): Quad(QuadBez { p0: (500.0, 461.0), p1: (524.0, 442.0), p2: (532.0, 412.0) })/Quad(QuadBez { p0: (532.0, 412.0), p1: (531.0, 420.0), p2: (534.0, 438.0) }) = 7.806400829235733
  • cid612 (U+3388): Quad(QuadBez { p0: (867.5, 414.5), p1: (865.0, 371.0), p2: (861.0, 336.0) })/Line(Line { p0: (861.0, 336.0), p1: (861.0, 337.0) }) = 6.519801751656917
  • cid612 (U+3388): Line(Line { p0: (861.0, 336.0), p1: (861.0, 337.0) })/Quad(QuadBez { p0: (861.0, 337.0), p1: (846.0, 220.0), p2: (812.0, 136.0) }) = 7.3057595333108205
    ... and 1058 others [code: found-jaggy-segments]
⚠️ WARN Check there are no overlapping path segments (overlapping_path_segments)
  • ⚠️ WARN The following glyphs have overlapping path segments:
  • cid3659 (U+938C): Quad(QuadBez { p0: (287.0, 82.0), p1: (287.0, 81.0), p2: (288.0, 81.0) }) has the same coordinates as a previous segment.
  • cid3797 (U+73D9): Quad(QuadBez { p0: (43.0, 70.0), p1: (43.0, 64.0), p2: (45.0, 64.0) }) has the same coordinates as a previous segment.
  • cid4220 (U+64D4): Quad(QuadBez { p0: (692.0, 734.0), p1: (692.0, 733.0), p2: (693.0, 733.0) }) has the same coordinates as a previous segment.
  • cid4332 (U+51AC): Quad(QuadBez { p0: (667.0, 683.0), p1: (666.0, 683.0), p2: (665.0, 682.0) }) has the same coordinates as a previous segment.
  • cid4396 (U+F920): Line(Line { p0: (705.0, 261.0), p1: (212.0, 261.0) }) has the same coordinates as a previous segment.
  • cid4403 (U+F922): Quad(QuadBez { p0: (697.0, 766.0), p1: (697.0, 765.0), p2: (696.0, 764.0) }) has the same coordinates as a previous segment.
  • cid4496 (U+7B2D): Quad(QuadBez { p0: (572.0, -46.0), p1: (571.0, -45.0), p2: (571.0, -45.0) }) has the same coordinates as a previous segment.
  • cid4548 (U+8CDA): Line(Line { p0: (695.0, 268.0), p1: (197.0, 268.0) }) has the same coordinates as a previous segment.
  • cid4548 (U+8CDA): Line(Line { p0: (695.0, 167.0), p1: (197.0, 167.0) }) has the same coordinates as a previous segment.
    ... and 19 others [code: overlapping-path-segments]
⚠️ WARN Do outlines contain any semi-vertical or semi-horizontal lines? (outline_semi_vertical)
  • ⚠️ WARN The following glyphs have semi-vertical/semi-horizontal lines:
  • cid372 (U+313F): Line(Line { p0: (726.0, 499.0), p1: (723.0, 111.0) })
  • cid372 (U+313F): Line(Line { p0: (519.0, 111.0), p1: (517.0, 501.0) })
  • cid372 (U+313F): Line(Line { p0: (556.0, 502.0), p1: (558.0, 110.0) })
  • cid372 (U+313F): Line(Line { p0: (683.0, 110.0), p1: (686.0, 502.0) })
  • cid1198 (U+AD50): Line(Line { p0: (690.0, 657.0), p1: (158.0, 656.0) })
  • cid1536 (U+B300): Line(Line { p0: (562.0, 386.0), p1: (563.0, -106.0) })
  • cid1536 (U+B300): Line(Line { p0: (563.0, 767.0), p1: (562.0, 427.0) })
  • cid1592 (U+B3FC): Line(Line { p0: (744.0, -129.0), p1: (745.0, 357.0) })
  • cid1592 (U+B3FC): Line(Line { p0: (745.0, 397.0), p1: (744.0, 777.0) })
    ... and 1310 others [code: found-semi-vertical]
⚠️ WARN Is the Grid-fitting and Scan-conversion Procedure ('gasp') table set to optimize rendering? (googlefonts/gasp)
  • ℹ️ INFO These are the ppm ranges declared on the gasp table:
PPM <= 8 - Use grayscale rendering
PPM <= 16 - Use grid-fitting
PPM <= 65535 - Use grid-fitting
- Use grayscale rendering
[code: ranges]
  • ⚠️ WARN The gasp table has a range of 8 that may be unneccessary. [code: non-ffff-range]

  • ⚠️ WARN The gasp table has a range of 16 that may be unneccessary. [code: non-ffff-range]

  • ⚠️ WARN The gasp range 0xFFFF value 0x03 should be set to 0x0F. [code: unset-flags]

⚠️ WARN Ensure fonts have ScriptLangTags declared on the 'meta' table. (googlefonts/meta/script_lang_tags)
  • ⚠️ WARN This font file does not have a 'meta' table. [code: lacks-meta-table]
ℹ️ INFO Show hinting filesize impact. (hinting_impact)
  • ℹ️ INFO Hinting filesize impact:
NanumBarunGothicUltraLight.ttf
Dehinted Size 3625112
Hinted Size 4822940
Increase 1197828
Change 33.0 %
ℹ️ INFO Font contains all required tables? (required_tables)
  • ℹ️ INFO This font contains the following optional tables:

    cvt
    fpgm
    loca
    prep
    gasp
    kern [code: optional-tables]

ℹ️ INFO Font has old ttfautohint applied? (googlefonts/old_ttfautohint)
  • ℹ️ INFO Could not detect which version of ttfautohint was used in this font. It is typically specified as a comment in the font version entries of the 'name' table. Such font version strings are currently: Version 1.0.1.0 Build 20150311, Version 1.0.1.0 Build 20150311 [code: version-not-detected]
[2] OFL.txt
🔥 FAIL Check license file has good copyright string. (googlefonts/license/OFL_copyright)
  • 🔥 FAIL First line in license file is:

"copyright (c) 2010, naver corporation (https://www.navercorp.com/) with reserved font name nanum, naver nanum, nanumgothic, naver nanumgothic, nanummyeongjo, naver nanummyeongjo, nanumbrush, naver nanumbrush, nanumpen, naver nanumpen, naver nanumgothiceco, nanumgothiceco, naver nanummyeongjoeco, nanummyeongjoeco, naver nanumgothiclight, nanumgothiclight, nanumbarungothic, naver nanumbarungothic, nanumsquareround, nanumbarunpen, maruburi, nanumsquareneo"

which does not match the expected format, similar to:

"Copyright 2022 The Familyname Project Authors (git url)" [code: bad-format]

⚠️ WARN Check OFL body text is correct. (googlefonts/license/OFL_body_text)

Lines changed:

-This license is copied below, and is also available with a FAQ at:
-https://openfontlicense.org
+This license is copied below, and is also available with a FAQ at: https://openfontlicense.org
+
[code: incorrect-ofl-body-text]

[32] NanumBarunGothic.ttf
🔥 FAIL Check name table for empty records. (opentype/name/empty_records)
  • 🔥 FAIL Empty name record found for name ID=COPYRIGHT_NOTICE platform ID=1 encoding ID=3 [code: empty-record]

  • 🔥 FAIL Empty name record found for name ID=FAMILY_NAME platform ID=1 encoding ID=3 [code: empty-record]

  • 🔥 FAIL Empty name record found for name ID=SUBFAMILY_NAME platform ID=1 encoding ID=3 [code: empty-record]

  • 🔥 FAIL Empty name record found for name ID=FULL_NAME platform ID=1 encoding ID=3 [code: empty-record]

  • 🔥 FAIL Empty name record found for name ID=DESIGNER platform ID=1 encoding ID=3 [code: empty-record]

  • 🔥 FAIL Empty name record found for name ID=POSTSCRIPT_CID_NAME platform ID=1 encoding ID=3 [code: empty-record]

🔥 FAIL Ensure the font supports case swapping for all its glyphs. (case_mapping)
  • 🔥 FAIL The following glyphs are missing case-swapping counterparts:
Glyph present in the font Missing case-swapping counterpart
U+212B: ANGSTROM SIGN U+00E5: LATIN SMALL LETTER A WITH RING ABOVE
U+0111: LATIN SMALL LETTER D WITH STROKE U+0110: LATIN CAPITAL LETTER D WITH STROKE
🔥 FAIL Does font file include unacceptable control character glyphs? (control_chars)
  • 🔥 FAIL The following unacceptable control characters were identified:
  • U+0002 (cid18363)
  • U+0009 (cid18370)
  • U+000A (cid18371) [code: unacceptable]
🔥 FAIL Font contains '.notdef' as its first glyph? (mandatory_glyphs)
  • 🔥 FAIL The '.notdef' glyph should contain a drawing, but it is blank. [code: notdef-is-blank]
🔥 FAIL Ensure smart dropout control is enabled in "prep" table instructions. (smart_dropout)
  • 🔥 FAIL The 'prep' table does not contain TrueType instructions enabling smart dropout control. To fix, export the font with autohinting enabled, or run ttfautohint on the font, or run the gftools fix-nonhinting script. [code: lacks-smart-dropout]
🔥 FAIL Are there unwanted tables? (unwanted_tables)
  • 🔥 FAIL Unwanted tables found:
    Table: FFTM Reason: Table contains redundant FontForge timestamp info
    [code: unwanted-tables]
🔥 FAIL Glyph names are all valid? (valid_glyphnames)
  • 🔥 FAIL Glyph 0x00A0 is called cid18419; must be named 'uni00A0'. [code: non-compliant-00A0]

  • 🔥 FAIL Glyph 0x0020 is called cid1; must be named 'space'. [code: non-compliant-0020]

🔥 FAIL Whitespace glyphs have ink? (whitespace_ink)
  • 🔥 FAIL The following glyphs have ink; they should be replaced by an empty glyph:
  • cid101 [code: has-ink]
🔥 FAIL Space and non-breaking space have the same width? (whitespace_widths)
  • 🔥 FAIL The space glyph named cid1 is 224 font units wide, non-breaking space named (cid18419) is 297 font units wide, and both should be positive and the same. GlyphsApp has "Sidebearing arithmetic" (https://glyphsapp.com/tutorials/spacing) which allows you to set the non-breaking space width to always equal the space width. [code: different-widths]
🔥 FAIL Check family name for GF Guide compliance. (googlefonts/name/family_name_compliance)
  • 🔥 FAIL "NanumBarunGothic" is a CamelCased name. To solve this, simply use spaces instead in the font name. [code: camelcase]
🔥 FAIL Checking file is named canonically. (googlefonts/canonical_filename)
  • 🔥 FAIL Expected "NanumBarunGothic-Regular.ttf". Got "NanumBarunGothic.ttf". [code: bad-filename]
🔥 FAIL Check font follows the Google Fonts CJK vertical metric schema (googlefonts/cjk_vertical_metrics)
  • 🔥 FAIL OS/2 fsSelection bit 7 must be enabled [code: bad-fselection-bit7]

  • 🔥 FAIL OS/2.sTypoAscender is 850; it should be between 881 and 931 [code: bad-OS/2.sTypoAscender]

  • 🔥 FAIL OS/2.sTypoDescender is -300; it should be between -269 and -219 [code: bad-OS/2.sTypoDescender]

  • 🔥 FAIL OS/2.usWinAscent is 850; it should be 838 [code: bad-OS/2.usWinAscent]

  • 🔥 FAIL OS/2.usWinDescent is 300; it should be 287 [code: bad-OS/2.usWinDescent]

  • 🔥 FAIL hhea.descent must match absolute value of OS/2.sTypoDescender [code: descent-mismatch]

  • 🔥 FAIL A BASE table with correct icfb/icft/ideo/romn and idtp baselines should be present [code: missing-BASE-table]

  • 🔥 FAIL A vmtx table should be present [code: missing-vmtx-table]

  • 🔥 FAIL A vhea table should be present [code: missing-vhea-table]

  • ℹ️ INFO Computed BASE table entries:

Baseline Computed
Horizontal icfb -110
Horizontal icft 772
Horizontal ideo -168
Horizontal idtp 831
Horizontal romn 0
Vertical icfb 36
Vertical icft 849
Vertical ideo 0
Vertical idtp 892
Vertical romn 168
🔥 FAIL Check font names are correct (googlefonts/font_names)
  • 🔥 FAIL Font names are incorrect:
Name Current Expected
Family Name NanumBarunGothic NanumBarunGothic
Subfamily Name Regular Regular
Full Name NanumBarunGothic NanumBarunGothic Regular
Postscript Name NanumBarunGothic NanumBarunGothic-Regular
Typographic Family Name NanumBarunGothic 나눔바른고딕
Typographic Subfamily Name Regular Regular
  • ⚠️ WARN Regular missing from full name [code: lacks-regular]
🔥 FAIL Checking OS/2 fsType does not impose restrictions. (googlefonts/fstype)
  • 🔥 FAIL In this font fsType is set to 8 meaning that:
  • The font may be embedded but must only be installed temporarily on other systems.

No such DRM restrictions can be enabled on the Google Fonts collection, so the fsType field must be set to zero (Installable Embedding) instead. [code: drm]

🔥 FAIL Font has all mandatory 'name' table entries? (googlefonts/name/mandatory_entries)
  • 🔥 FAIL Font lacks entry with nameId=1 (FAMILY_NAME) [code: missing-entry]

  • 🔥 FAIL Font lacks entry with nameId=2 (SUBFAMILY_NAME) [code: missing-entry]

  • 🔥 FAIL Font lacks entry with nameId=4 (FULL_NAME) [code: missing-entry]

  • 🔥 FAIL Font lacks entry with nameId=9 (DESIGNER) [code: missing-entry]

⚠️ WARN Check for points out of bounds (opentype/points_out_of_bounds)
  • ⚠️ WARN The following glyphs have coordinates which are out of bounds:
  • cid66 (y=-49, bounds are -48<->532)
  • cid75 (y=-289, bounds are -287<->747)
  • cid85 (y=-48, bounds are -47<->645)
  • cid155 (x=43, bounds are 44<->403)
  • cid199 (x=567, bounds are 333<->565)
  • cid199 (y=807, bounds are 636<->803)
  • cid209 (y=-141, bounds are -134<->731)
  • cid757 (y=-116, bounds are -113<->464)
  • cid757 (x=98, bounds are 105<->777)
    ... and 839 others

This happens a lot when points are not extremes, which is usually bad. However, fixing this alert by adding points on extremes may do more harm than good, especially with italics, calligraphic-script, handwriting, rounded and other fonts. So it is common to ignore this message. [code: points-out-of-bounds]

⚠️ WARN Does the font contain chws and vchw features? (cjk_chws_feature)
⚠️ WARN Check if each glyph has the recommended amount of contours. (contour_count)
  • ⚠️ WARN This check inspects the glyph outlines and detects the total number of contours in each of them. The expected values are
    inferred from the typical amounts of contours observed in a
    large collection of reference font families. The divergences
    listed below may simply indicate a significantly different
    design on some of your glyphs. On the other hand, some of these
    may flag actual bugs in the font such as glyphs mapped to an
    incorrect codepoint. Please consider reviewing the design and
    codepoint assignment of these to make sure they are correct.

    The following glyphs do not have the recommended number of contours:

  • cid61 (U+005C): found 4, expected one of: {1, 5}
  • cid8664 (U+262F): found 2, expected one of: {4}
  • cid8655 (U+E23B): found 4, expected one of: {1, 3, 2}
  • cid8636 (U+E22A): found 4, expected one of: {1, 3, 2}
  • cid8646 (U+E232): found 5, expected one of: {1, 3, 2}
  • cid8668 (U+E247): found 6, expected one of: {1, 2, 3}
  • cid8622 (U+E21F): found 4, expected one of: {1, 2, 3}
  • cid379 (U+3146): found 2, expected one of: {1, 4}
  • cid2381 (U+C384): found 4, expected one of: {7, 3, 2}
    ... and 27 others [code: contour-count]
⚠️ WARN Ensure files are not too large. (file_size)
  • ⚠️ WARN Font file is 4.19 MB; ideally it should be less than 1.05 MB [code: large-font]
⚠️ WARN Check math signs have the same width. (math_signs_width)
  • ⚠️ WARN The most common width is 892 among a set of 72 math glyphs.
    The following math glyphs have a different width, though:
    width=583: cid12, cid30
    width=446: cid29, cid31 [code: width-outliers]
⚠️ WARN Ensure indic fonts have the Indian Rupee Sign glyph. (rupee)
  • ⚠️ WARN Font is missing the Indian Rupee Sign glyph. Please add a glyph for Indian Rupee Sign (₹) at codepoint U+20B9. [code: missing-rupee]
⚠️ WARN Does the font contain a soft hyphen? (soft_hyphen)
  • ⚠️ WARN This font has a 'Soft Hyphen' character. [code: softhyphen]
⚠️ WARN Check font contains no unreachable glyphs (unreachable_glyphs)
  • ⚠️ WARN The following glyphs could not be reached by codepoint or substitution rules:
  • .null
  • nonmarkingreturn [code: unreachable-glyphs]
⚠️ WARN Font has correct separator glyphs? (googlefonts/separator_glyphs)
  • ⚠️ WARN The following separator glyphs are missing:
  • U+2028
  • U+2029 [code: missing-separator-glyphs]
⚠️ WARN Do outlines contain any jaggy segments? (outline_jaggy_segments)
  • ⚠️ WARN The following glyphs have jaggy segments:
  • cid46 (U+004D): Line(Line { p0: (183.0, 572.0), p1: (168.0, 638.0) })/Line(Line { p0: (168.0, 638.0), p1: (169.0, 571.0) }) = 11.949168669020022
  • cid46 (U+004D): Line(Line { p0: (714.0, 571.0), p1: (715.0, 638.0) })/Line(Line { p0: (715.0, 638.0), p1: (699.0, 572.0) }) = 12.771897463624816
  • cid482 (U+039C): Line(Line { p0: (560.0, -71.0), p1: (709.0, 571.0) })/Line(Line { p0: (709.0, 571.0), p1: (413.0, -71.0) }) = 11.686204997056967
  • cid260 (U+2122): Line(Line { p0: (465.0, 625.0), p1: (455.0, 662.0) })/Line(Line { p0: (455.0, 662.0), p1: (456.0, 625.0) }) = 13.575849609332623
  • cid260 (U+2122): Line(Line { p0: (720.0, 625.0), p1: (721.0, 662.0) })/Line(Line { p0: (721.0, 662.0), p1: (711.0, 625.0) }) = 13.575849609332623
  • cid8488 (U+2ACC): Line(Line { p0: (569.0, 209.0), p1: (508.0, 209.0) })/Line(Line { p0: (508.0, 209.0), p1: (535.0, 204.0) }) = 10.491477012331599
  • cid9222 (U+261D): Quad(QuadBez { p0: (382.5, 495.5), p1: (384.0, 452.0), p2: (385.0, 429.0) })/Quad(QuadBez { p0: (385.0, 429.0), p1: (387.0, 452.0), p2: (396.5, 473.0) }) = 7.459293650109428
  • cid9223 (U+261F): Quad(QuadBez { p0: (418.0, 131.0), p1: (409.0, 152.0), p2: (406.0, 175.0) })/Quad(QuadBez { p0: (406.0, 175.0), p1: (405.0, 152.0), p2: (404.0, 108.5) }) = 9.920960893171603
  • cid8664 (U+262F): Quad(QuadBez { p0: (764.5, 241.5), p1: (764.0, 207.0), p2: (754.0, 179.0) })/Quad(QuadBez { p0: (754.0, 179.0), p1: (767.0, 214.0), p2: (771.0, 245.0) }) = 0.7226111557835152
    ... and 220 others [code: found-jaggy-segments]
⚠️ WARN Check there are no overlapping path segments (overlapping_path_segments)
  • ⚠️ WARN The following glyphs have overlapping path segments:
  • cid9272 (U+E44B): Quad(QuadBez { p0: (718.0, 648.0), p1: (720.0, 648.0), p2: (716.5, 647.0) }) has the same coordinates as a previous segment. [code: overlapping-path-segments]
⚠️ WARN Do outlines contain any semi-vertical or semi-horizontal lines? (outline_semi_vertical)
  • ⚠️ WARN The following glyphs have semi-vertical/semi-horizontal lines:
  • cid78 (U+006D): Line(Line { p0: (496.0, 265.0), p1: (495.0, -36.0) })
  • cid244 (U+00B6): Line(Line { p0: (440.0, -157.0), p1: (439.0, 318.0) })
  • cid760 (U+0127): Line(Line { p0: (672.0, 123.0), p1: (671.0, -94.0) })
  • cid472 (U+0392): Line(Line { p0: (324.0, 680.0), p1: (537.0, 679.0) })
  • cid481 (U+039B): Line(Line { p0: (657.0, 671.0), p1: (659.0, -61.0) })
  • cid481 (U+039B): Line(Line { p0: (576.0, -61.0), p1: (577.0, 557.0) })
  • cid487 (U+03A1): Line(Line { p0: (487.0, 242.0), p1: (299.0, 241.0) })
  • cid1037 (U+0420): Line(Line { p0: (210.0, 679.0), p1: (501.0, 678.0) })
  • cid1037 (U+0420): Line(Line { p0: (501.0, 251.0), p1: (291.0, 250.0) })
    ... and 1435 others [code: found-semi-vertical]
⚠️ WARN Is the Grid-fitting and Scan-conversion Procedure ('gasp') table set to optimize rendering? (googlefonts/gasp)
  • ℹ️ INFO These are the ppm ranges declared on the gasp table:

| PPM <= 10 | - Use grayscale rendering |
| | - Use gridfitting with ClearType symmetric smoothing |

- Use smoothing along multiple axes with ClearType®
PPM <= 16 - Use grid-fitting
- Use grayscale rendering
- Use gridfitting with ClearType symmetric smoothing
PPM <= 65535 - Use grid-fitting
- Use grayscale rendering
- Use gridfitting with ClearType symmetric smoothing
- Use smoothing along multiple axes with ClearType®
[code: ranges]
  • ⚠️ WARN The gasp table has a range of 10 that may be unneccessary. [code: non-ffff-range]

  • ⚠️ WARN The gasp table has a range of 16 that may be unneccessary. [code: non-ffff-range]

⚠️ WARN Ensure fonts have ScriptLangTags declared on the 'meta' table. (googlefonts/meta/script_lang_tags)
  • ⚠️ WARN This font file does not have a 'meta' table. [code: lacks-meta-table]
ℹ️ INFO Show hinting filesize impact. (hinting_impact)
  • ℹ️ INFO Hinting filesize impact:
NanumBarunGothic.ttf
Dehinted Size 3423844
Hinted Size 4186060
Increase 762216
Change 22.3 %
ℹ️ INFO Font contains all required tables? (required_tables)
  • ℹ️ INFO This font contains the following optional tables:

    cvt
    fpgm
    loca
    prep
    GPOS
    GSUB
    gasp
    kern [code: optional-tables]

ℹ️ INFO Font has old ttfautohint applied? (googlefonts/old_ttfautohint)
  • ℹ️ INFO Could not detect which version of ttfautohint was used in this font. It is typically specified as a comment in the font version entries of the 'name' table. Such font version strings are currently: Version 1.000 2013 initial release, Version 1.000 2013 initial release [code: version-not-detected]
[16]
🔥 FAIL Fonts have consistent underline thickness? (opentype/family/underline_thickness)
  • 🔥 FAIL Underline thickness is inconsistent. Detected underline thickness values are:
  • NanumBarunGothic.ttf: 58
  • NanumBarunGothicBold.ttf: 58
  • NanumBarunGothicLight.ttf: 25
  • NanumBarunGothicUltraLight.ttf: 25
    [code: inconsistent-underline-thickness]
🔥 FAIL Each font in a family must have the same set of vertical metrics values. (family/vertical_metrics)
  • 🔥 FAIL usWinDescent is not the same across the family:
  • NanumBarunGothic.ttf: 300
  • NanumBarunGothicBold.ttf: 300
  • NanumBarunGothicLight.ttf: 299
  • NanumBarunGothicUltraLight.ttf: 299 [code: usWinDescent-mismatch]
🔥 FAIL METADATA.pb: Check URL on copyright string is the same as in repository_url field. (googlefonts/metadata/consistent_repo_urls)
  • 🔥 FAIL Please add a family.source.repository_url entry. [code: lacks-repo-url]
🔥 FAIL Check METADATA.pb parses correctly (googlefonts/metadata/consistent_with_fonts)
  • 🔥 FAIL METADATA.pb full_name field "NanumBarunGothic" does not match correct full name "". [code: fullname-mismatch]

  • 🔥 FAIL METADATA.pb full_name field "NanumBarunGothic" does not match correct full name "나눔바른고딕". [code: fullname-mismatch]

  • 🔥 FAIL METADATA.pb full_name field "NanumBarunGothic Bold" does not match correct full name "". [code: fullname-mismatch]

  • 🔥 FAIL METADATA.pb full_name field "NanumBarunGothic Bold" does not match correct full name "나눔바른고딕 Bold". [code: fullname-mismatch]

  • 🔥 FAIL METADATA.pb full_name field "NanumBarunGothic Light" does not match correct full name "". [code: fullname-mismatch]

  • 🔥 FAIL METADATA.pb full_name field "NanumBarunGothic Light" does not match correct full name "나눔바른고딕 Light". [code: fullname-mismatch]

  • 🔥 FAIL METADATA.pb full_name field "NanumBarunGothic UltraLight" does not match correct full name "". [code: fullname-mismatch]

  • 🔥 FAIL METADATA.pb full_name field "NanumBarunGothic UltraLight" does not match correct full name "나눔바른고딕 UltraLight". [code: fullname-mismatch]

🔥 FAIL Check METADATA.pb font weights are correct. (googlefonts/metadata/weightclass)
  • 🔥 FAIL OS/2 table has usWeightClass=300, meaning 'Light'.

On METADATA.pb it should be the same, but instead got 300. [code: mismatch]

🔥 FAIL Tofu should not be shown in sample texts. (googlefonts/tofu)
  • 🔥 FAIL The font has the following codepoints needed to render the masthead full sample text for language Acoli, but although the font contained all the base exemplars for the language, tofu will still be produced because the codepoints do not appear in any of the subsets korean, latin:
  • Ŋ (U+014A)
  • ŋ (U+014B) [code: missing-subsetted]
  • 🔥 FAIL The font has the following codepoints needed to render the masthead full sample text for language Bulgarian, but although the font contained all the base exemplars for the language, tofu will still be produced because the codepoints do not appear in any of the subsets korean, latin:
  • С (U+0421)
  • В (U+0412)
  • в (U+0432)
  • с (U+0441) [code: missing-subsetted]
  • 🔥 FAIL The font has the following codepoints needed to render the masthead partial sample text for language Bulgarian, but although the font contained all the base exemplars for the language, tofu will still be produced because the codepoints do not appear in any of the subsets korean, latin:
  • И (U+0418)
  • и (U+0438) [code: missing-subsetted]
  • 🔥 FAIL The font has the following codepoints needed to render the poster lg sample text for language Bulgarian, but although the font contained all the base exemplars for the language, tofu will still be produced because the codepoints do not appear in any of the subsets korean, latin:
  • ч (U+0447)
  • к (U+043A) [code: missing-subsetted]
  • 🔥 FAIL The font has the following codepoints needed to render the poster md sample text for language Bulgarian, but although the font contained all the base exemplars for the language, tofu will still be produced because the codepoints do not appear in any of the subsets korean, latin:
  • о (U+043E)
  • а (U+0430)
  • р (U+0440)
  • х (U+0445) [code: missing-subsetted]
  • 🔥 FAIL The font has the following codepoints needed to render the poster sm sample text for language Bulgarian, but although the font contained all the base exemplars for the language, tofu will still be produced because the codepoints do not appear in any of the subsets korean, latin:
  • ъ (U+044A)
  • з (U+0437)
  • я (U+044F)
  • л (U+043B)
  • п (U+043F)
  • г (U+0433) [code: missing-subsetted]
  • 🔥 FAIL The font has the following codepoints needed to render the specimen 16 sample text for language Bulgarian, but although the font contained all the base exemplars for the language, tofu will still be produced because the codepoints do not appear in any of the subsets korean, latin:
  • н (U+043D)
  • т (U+0442)
  • ж (U+0436)
  • К (U+041A)
  • б (U+0431)
  • м (U+043C)
  • щ (U+0449)
  • й (U+0439)
  • ш (U+0448)
    ... and 3 others [code: missing-subsetted]
  • 🔥 FAIL The font has the following codepoints needed to render the specimen 21 sample text for language Bulgarian, but although the font contained all the base exemplars for the language, tofu will still be produced because the codepoints do not appear in any of the subsets korean, latin:
  • Д (U+0414)
  • ц (U+0446)
  • Н (U+041D) [code: missing-subsetted]
  • 🔥 FAIL The font has the following codepoints needed to render the masthead full sample text for language Xiang Chinese, but although the font contained all the codepoints for the sample text, tofu will still be produced because the codepoints do not appear in any of the subsets korean, latin:
  • 人 (U+4EBA)
  • 而 (U+800C)
  • 生 (U+751F)
  • 自 (U+81EA) [code: missing-subsetted]
  • 🔥 FAIL The font has the following codepoints needed to render the masthead partial sample text for language Xiang Chinese, but although the font contained all the codepoints for the sample text, tofu will still be produced because the codepoints do not appear in any of the subsets korean, latin:
  • 在 (U+5728)
  • 由 (U+7531) [code: missing-subsetted]
  • 🔥 FAIL The font has the following codepoints needed to render the poster sm sample text for language Xiang Chinese, but although the font contained all the codepoints for the sample text, tofu will still be produced because the codepoints do not appear in any of the subsets korean, latin:
  • 和 (U+548C)
  • 等 (U+7B49)
  • 一 (U+4E00)
  • 利 (U+5229)
  • 尊 (U+5C0A)
  • , (U+FF0C)
  • 平 (U+5E73)
  • 上 (U+4E0A)
  • 嚴 (U+56B4)
    ... and 2 others [code: missing-subsetted]
  • 🔥 FAIL The font has the following codepoints needed to render the specimen 16 sample text for language Xiang Chinese, but although the font contained all the codepoints for the sample text, tofu will still be produced because the codepoints do not appear in any of the subsets korean, latin:
  • 得 (U+5F97)
  • 係 (U+4FC2)
  • 性 (U+6027)
  • 兄 (U+5144)
  • 心 (U+5FC3)
  • 關 (U+95DC)
  • 弟 (U+5F1F)
  • 們 (U+5011)
  • 賦 (U+8CE6)
    ... and 12 others [code: missing-subsetted]
  • 🔥 FAIL The font has the following codepoints needed to render the masthead full sample text for language Japanese (Hiragana), but although the font contained all the base exemplars for the language, tofu will still be produced because the codepoints do not appear in any of the subsets korean, latin:
  • て (U+3066)
  • べ (U+3079)
  • す (U+3059)
  • の (U+306E) [code: missing-subsetted]
  • 🔥 FAIL The font has the following codepoints needed to render the masthead partial sample text for language Japanese (Hiragana), but although the font contained all the base exemplars for the language, tofu will still be produced because the codepoints do not appear in any of the subsets korean, latin:
  • げ (U+3052)
  • ん (U+3093)
  • に (U+306B) [code: missing-subsetted]
  • 🔥 FAIL The font has the following codepoints needed to render the poster lg sample text for language Japanese (Hiragana), but although the font contained all the base exemplars for the language, tofu will still be produced because the codepoints do not appear in any of the subsets korean, latin:
  • は (U+306F) [code: missing-subsetted]
  • 🔥 FAIL The font has the following codepoints needed to render the poster md sample text for language Japanese (Hiragana), but although the font contained all the base exemplars for the language, tofu will still be produced because the codepoints do not appear in any of the subsets korean, latin:
  • そ (U+305D)
  • う (U+3046)
  • こ (U+3053)
  • よ (U+3088)
  • く (U+304F)
  • 、 (U+3001)
  • れ (U+308C)
  • い (U+3044)
  • っ (U+3063)
    ... and 1 others [code: missing-subsetted]
  • 🔥 FAIL The font has the following codepoints needed to render the poster sm sample text for language Japanese (Hiragana), but although the font contained all the base exemplars for the language, tofu will still be produced because the codepoints do not appear in any of the subsets korean, latin:
  • ょ (U+3087)
  • き (U+304D)
  • り (U+308A)
  • し (U+3057)
  • さ (U+3055)
  • と (U+3068)
  • ご (U+3054)
  • め (U+3081) [code: missing-subsetted]
  • 🔥 FAIL The font has the following codepoints needed to render the specimen 16 sample text for language Japanese (Hiragana), but although the font contained all the base exemplars for the language, tofu will still be produced because the codepoints do not appear in any of the subsets korean, latin:
  • お (U+304A)
  • た (U+305F)
  • る (U+308B)
  • だ (U+3060)
  • ゆ (U+3086)
  • を (U+3092)
  • ゅ (U+3085)
  • ぼ (U+307C)
  • な (U+306A)
    ... and 33 others [code: missing-subsetted]
  • 🔥 FAIL The font has the following codepoints needed to render the masthead full sample text for language Japanese (Katakana), but although the font contained all the codepoints for the sample text, tofu will still be produced because the codepoints do not appear in any of the subsets korean, latin:
  • ス (U+30B9)
  • ベ (U+30D9)
  • ノ (U+30CE)
  • テ (U+30C6) [code: missing-subsetted]
  • 🔥 FAIL The font has the following codepoints needed to render the masthead partial sample text for language Japanese (Katakana), but although the font contained all the codepoints for the sample text, tofu will still be produced because the codepoints do not appear in any of the subsets korean, latin:
  • ン (U+30F3)
  • ニ (U+30CB)
  • ゲ (U+30B2) [code: missing-subsetted]
  • 🔥 FAIL The font has the following codepoints needed to render the poster lg sample text for language Japanese (Katakana), but although the font contained all the codepoints for the sample text, tofu will still be produced because the codepoints do not appear in any of the subsets korean, latin:
  • ハ (U+30CF) [code: missing-subsetted]
  • 🔥 FAIL The font has the following codepoints needed to render the poster md sample text for language Japanese (Katakana), but although the font contained all the codepoints for the sample text, tofu will still be produced because the codepoints do not appear in any of the subsets korean, latin:
  • ウ (U+30A6)
  • ソ (U+30BD)
  • イ (U+30A4)
  • カ (U+30AB)
  • レ (U+30EC)
  • ッ (U+30C3)
  • ク (U+30AF)
  • コ (U+30B3)
  • ヨ (U+30E8)
    ... and 1 others [code: missing-subsetted]
  • 🔥 FAIL The font has the following codepoints needed to render the poster sm sample text for language Japanese (Katakana), but although the font contained all the codepoints for the sample text, tofu will still be produced because the codepoints do not appear in any of the subsets korean, latin:
  • ゴ (U+30B4)
  • サ (U+30B5)
  • キ (U+30AD)
  • ト (U+30C8)
  • リ (U+30EA)
  • メ (U+30E1)
  • ョ (U+30E7)
  • シ (U+30B7) [code: missing-subsetted]
  • 🔥 FAIL The font has the following codepoints needed to render the specimen 16 sample text for language Japanese (Katakana), but although the font contained all the codepoints for the sample text, tofu will still be produced because the codepoints do not appear in any of the subsets korean, latin:
  • ズ (U+30BA)
  • ガ (U+30AC)
  • チ (U+30C1)
  • タ (U+30BF)
  • ロ (U+30ED)
  • ブ (U+30D6)
  • パ (U+30D1)
  • ミ (U+30DF)
  • モ (U+30E2)
    ... and 33 others [code: missing-subsetted]
  • 🔥 FAIL The font has the following codepoints needed to render the masthead full sample text for language Karachay-Balkar, but although the font contained all the codepoints for the sample text, tofu will still be produced because the codepoints do not appear in any of the subsets korean, latin:
  • Б (U+0411)
  • ю (U+044E)
  • Ю (U+042E)
  • б (U+0431) [code: missing-subsetted]
  • 🔥 FAIL The font has the following codepoints needed to render the masthead partial sample text for language Karachay-Balkar, but although the font contained all the codepoints for the sample text, tofu will still be produced because the codepoints do not appear in any of the subsets korean, latin:
  • т (U+0442)
  • Т (U+0422) [code: missing-subsetted]
  • 🔥 FAIL The font has the following codepoints needed to render the poster lg sample text for language Karachay-Balkar, but although the font contained all the codepoints for the sample text, tofu will still be produced because the codepoints do not appear in any of the subsets korean, latin:
  • ё (U+0451)
  • у (U+0443) [code: missing-subsetted]
  • 🔥 FAIL The font has the following codepoints needed to render the poster sm sample text for language Karachay-Balkar, but although the font contained all the codepoints for the sample text, tofu will still be produced because the codepoints do not appear in any of the subsets korean, latin:
  • а (U+0430)
  • л (U+043B)
  • м (U+043C)
  • д (U+0434) [code: missing-subsetted]
  • 🔥 FAIL The font has the following codepoints needed to render the specimen 16 sample text for language Karachay-Balkar, but although the font contained all the codepoints for the sample text, tofu will still be produced because the codepoints do not appear in any of the subsets korean, latin:
  • э (U+044D)
  • о (U+043E)
  • н (U+043D)
  • р (U+0440)
  • ш (U+0448)
  • х (U+0445)
  • г (U+0433)
  • е (U+0435)
  • ъ (U+044A)
    ... and 6 others [code: missing-subsetted]
  • 🔥 FAIL The font has the following codepoints needed to render the masthead full sample text for language Lingua Franca Nova, but although the font contained all the codepoints for the sample text, tofu will still be produced because the codepoints do not appear in any of the subsets korean, latin:
  • т (U+0442)
  • Т (U+0422)
  • о (U+043E)
  • О (U+041E) [code: missing-subsetted]
  • 🔥 FAIL The font has the following codepoints needed to render the masthead partial sample text for language Lingua Franca Nova, but although the font contained all the codepoints for the sample text, tofu will still be produced because the codepoints do not appear in any of the subsets korean, latin:
  • а (U+0430)
  • А (U+0410) [code: missing-subsetted]
  • 🔥 FAIL The font has the following codepoints needed to render the poster md sample text for language Lingua Franca Nova, but although the font contained all the codepoints for the sample text, tofu will still be produced because the codepoints do not appear in any of the subsets korean, latin:
  • н (U+043D)
  • у (U+0443)
  • м (U+043C)
  • е (U+0435)
  • с (U+0441) [code: missing-subsetted]
  • 🔥 FAIL The font has the following codepoints needed to render the specimen 16 sample text for language Lingua Franca Nova, but although the font contained all the codepoints for the sample text, tofu will still be produced because the codepoints do not appear in any of the subsets korean, latin:
  • к (U+043A)
  • д (U+0434)
  • п (U+043F)
  • б (U+0431)
  • ф (U+0444)
  • и (U+0438)
  • з (U+0437)
  • г (U+0433)
  • л (U+043B)
    ... and 2 others [code: missing-subsetted]
  • 🔥 FAIL The font has the following codepoints needed to render the masthead full sample text for language Southern Min Chinese, but although the font contained all the codepoints for the sample text, tofu will still be produced because the codepoints do not appear in any of the subsets korean, latin:
  • 生 (U+751F)
  • 皆 (U+7686)
  • 人 (U+4EBA)
  • 而 (U+800C) [code: missing-subsetted]
  • 🔥 FAIL The font has the following codepoints needed to render the masthead partial sample text for language Southern Min Chinese, but although the font contained all the codepoints for the sample text, tofu will still be produced because the codepoints do not appear in any of the subsets korean, latin:
  • 自 (U+81EA)
  • 由 (U+7531) [code: missing-subsetted]
  • 🔥 FAIL The font has the following codepoints needed to render the poster sm sample text for language Southern Min Chinese, but although the font contained all the codepoints for the sample text, tofu will still be produced because the codepoints do not appear in any of the subsets korean, latin:
  • 等 (U+7B49)
  • 及 (U+53CA)
  • 上 (U+4E0A)
  • 權 (U+6B0A)
  • 在 (U+5728)
  • 平 (U+5E73)
  • 各 (U+5404)
  • 均 (U+5747)
  • ; (U+FF1B)
    ... and 3 others [code: missing-subsetted]
  • 🔥 FAIL The font has the following codepoints needed to render the specimen 16 sample text for language Southern Min Chinese, but although the font contained all the codepoints for the sample text, tofu will still be produced because the codepoints do not appear in any of the subsets korean, latin:
  • 手 (U+624B)
  • 誠 (U+8AA0)
  • 理 (U+7406)
  • 處 (U+8655)
  • 應 (U+61C9)
  • , (U+FF0C)
  • 有 (U+6709)
  • 相 (U+76F8)
  • 賦 (U+8CE6)
    ... and 9 others [code: missing-subsetted]
  • 🔥 FAIL The font has the following codepoints needed to render the masthead full sample text for language Romanian (Cyrillic), but although the font contained all the codepoints for the sample text, tofu will still be produced because the codepoints do not appear in any of the subsets korean, latin:
  • о (U+043E)
  • Т (U+0422)
  • О (U+041E)
  • т (U+0442) [code: missing-subsetted]
  • 🔥 FAIL The font has the following codepoints needed to render the masthead partial sample text for language Romanian (Cyrillic), but although the font contained all the codepoints for the sample text, tofu will still be produced because the codepoints do not appear in any of the subsets korean, latin:
  • а (U+0430)
  • А (U+0410) [code: missing-subsetted]
  • 🔥 FAIL The font has the following codepoints needed to render the poster lg sample text for language Romanian (Cyrillic), but although the font contained all the codepoints for the sample text, tofu will still be produced because the codepoints do not appear in any of the subsets korean, latin:
  • е (U+0435) [code: missing-subsetted]
  • 🔥 FAIL The font has the following codepoints needed to render the poster sm sample text for language Romanian (Cyrillic), but although the font contained all the codepoints for the sample text, tofu will still be produced because the codepoints do not appear in any of the subsets korean, latin:
  • и (U+0438)
  • ф (U+0444)
  • ц (U+0446)
  • н (U+043D)
  • л (U+043B) [code: missing-subsetted]
  • 🔥 FAIL The font has the following codepoints needed to render the specimen 16 sample text for language Romanian (Cyrillic), but although the font contained all the codepoints for the sample text, tofu will still be produced because the codepoints do not appear in any of the subsets korean, latin:
  • к (U+043A)
  • ь (U+044C)
  • п (U+043F)
  • у (U+0443)
  • Е (U+0415)
  • б (U+0431)
  • э (U+044D)
  • й (U+0439)
  • д (U+0434)
    ... and 7 others [code: missing-subsetted]
  • 🔥 FAIL The font has the following codepoints needed to render the masthead full sample text for language Russian, but although the font contained all the base exemplars for the language, tofu will still be produced because the codepoints do not appear in any of the subsets korean, latin:
  • с (U+0441)
  • В (U+0412)
  • С (U+0421)
  • в (U+0432) [code: missing-subsetted]
  • 🔥 FAIL The font has the following codepoints needed to render the masthead partial sample text for language Russian, but although the font contained all the base exemplars for the language, tofu will still be produced because the codepoints do not appear in any of the subsets korean, latin:
  • е (U+0435)
  • Е (U+0415) [code: missing-subsetted]
  • 🔥 FAIL The font has the following codepoints needed to render the poster md sample text for language Russian, but although the font contained all the base exemplars for the language, tofu will still be produced because the codepoints do not appear in any of the subsets korean, latin:
  • и (U+0438)
  • р (U+0440)
  • я (U+044F)
  • м (U+043C)
  • п (U+043F)
  • н (U+043D)
  • а (U+0430) [code: missing-subsetted]
  • 🔥 FAIL The font has the following codepoints needed to render the poster sm sample text for language Russian, but although the font contained all the base exemplars for the language, tofu will still be produced because the codepoints do not appear in any of the subsets korean, latin:
  • о (U+043E) [code: missing-subsetted]
  • 🔥 FAIL The font has the following codepoints needed to render the specimen 16 sample text for language Russian, but although the font contained all the base exemplars for the language, tofu will still be produced because the codepoints do not appear in any of the subsets korean, latin:
  • щ (U+0449)
  • ю (U+044E)
  • ж (U+0436)
  • л (U+043B)
  • П (U+041F)
  • ь (U+044C)
  • ъ (U+044A)
  • у (U+0443)
  • х (U+0445)
    ... and 11 others [code: missing-subsetted]
  • 🔥 FAIL The font has the following codepoints needed to render the specimen 21 sample text for language Russian, but although the font contained all the base exemplars for the language, tofu will still be produced because the codepoints do not appear in any of the subsets korean, latin:
  • Н (U+041D)
  • Д (U+0414) [code: missing-subsetted]
  • 🔥 FAIL The font has the following codepoints needed to render the specimen 32 sample text for language Russian, but although the font contained all the base exemplars for the language, tofu will still be produced because the codepoints do not appear in any of the subsets korean, latin:
  • К (U+041A) [code: missing-subsetted]
🔥 FAIL Fonts have equal codepoint coverage? (googlefonts/family/equal_codepoint_coverage)
  • 🔥 FAIL Font NanumBarunGothic.ttf has codepoints not present in sibling fonts: U+FA3D, U+FA72, U+FAC3, U+FA9B, U+FA53, U+FA92, U+FA93, U+FA38, U+FABC, U+FA7F, U+FA41, U+90CE, U+FA4A, U+FA57, U+FA63, U+FA7A, U+FA48, U+FAA0, U+FAB8, U+FAC1, U+FA7C, U+FA43, U+FA80, U+FA7D, U+FA5F, U+FA64, U+FA3B, U+FA69, U+FA76, U+FAA5, U+FA30, U+FA9F, U+FA75, U+FA54, U+FAC7, U+FAB4, U+FA9C, U+FA91, U+FABD, U+FAB0, U+FA33, U+FA36, U+FA44, U+FA67, U+FA52, U+FA78, U+FAAA, U+FABA, U+FA90, U+FA34, U+FAA8, U+FAA6, U+FA4C, U+FABF, U+FA5C, U+FA4F, U+FA4E, U+FA60, U+FABE, U+FA74, U+FA3A, U+FA37, U+FACC, U+FA5B, U+FA9A, U+FA77, U+FA50, U+FA9E, U+FACE, U+FA6A, U+FAC8, U+FA5A, U+FA3E, U+FA46, U+FA61, U+FA31, U+FA0C, U+FA51, U+FA68, U+FA40, U+FA4D, U+FA8B, U+FA94, U+FAB2, U+FABB, U+FA8C, U+FA35, U+FA8E, U+FA45, U+FA47, U+FA8D, U+FA32, U+FAB7, U+FAC0, U+FAB9, U+FA55, U+FAB3, U+FA96, U+FA3F, U+FACA, U+FA7E, U+FAA7, U+FA62, U+FA99, U+FA89, U+FAAD, U+FA88, U+FA84, U+FAB6, U+FA56, U+FA58, U+FA4B, U+FA65, U+FA97, U+FAC2, U+FA59 [code: glyphset-diverges]

  • 🔥 FAIL Other fonts have codepoints not present in NanumBarunGothic.ttf: U+0015, U+009E, U+0093, U+0016, U+001D, U+0003, U+008C, U+0096, U+0007, U+0080, U+0017, U+0004, U+0005, U+001A, U+0094, U+009A, U+0081, U+0085, U+0014, U+0091, U+0013, U+008B, U+001B, U+009B, U+008E, U+0082, U+000C, U+0089, U+009F, U+000F, U+0083, U+0092, U+0099, U+0086, U+0001, U+0084, U+0087, U+0010, U+0018, U+009D, U+0012, U+0088, U+0097, U+0019, U+0006, U+0011, U+001F, U+009C, U+0008, U+008A, U+0098, U+0090, U+000B, U+001C, U+001E, U+008D, U+008F, U+0095, U+007F, U+000E [code: glyphset-diverges]

🔥 FAIL Copyright notices match canonical pattern in fonts (googlefonts/font_copyright)
  • 🔥 FAIL NanumBarunGothic.ttf: Name Table entry: Copyright notices should match a pattern similar to:

"Copyright 2020 The Familyname Project Authors (git url)"

But instead we have got:

"copyright (c) 2013 nhn corporation. all rights reserved. font designed by fontrix inc." [code: bad-notice-format]

  • 🔥 FAIL NanumBarunGothic.ttf: Name Table entry: Copyright notices should match a pattern similar to:

"Copyright 2020 The Familyname Project Authors (git url)"

But instead we have got:

"" [code: bad-notice-format]

  • 🔥 FAIL NanumBarunGothic.ttf: Name Table entry: Copyright notices should match a pattern similar to:

"Copyright 2020 The Familyname Project Authors (git url)"

But instead we have got:

"copyright ⓒ 2013 nhn corporation. all rights reserved. font designed by fontrix inc." [code: bad-notice-format]

  • 🔥 FAIL METADATA.pb: Copyright notices should match a pattern similar to:

"Copyright 2020 The Familyname Project Authors (git url)"

But instead we have got:

"copyright ⓒ 2013 nhn corporation. all rights reserved. font designed by fontrix inc." [code: bad-notice-format]

  • 🔥 FAIL Copyright notices differ between name table entries and METADATA.pb. The following entries were found:
  • copyright ⓒ 2013 nhn corporation. all rights reserved. font designed by fontrix inc.: ["NanumBarunGothic.ttf: Name Table entry", "METADATA.pb"]
  • copyright (c) 2013 nhn corporation. all rights reserved. font designed by fontrix inc.: ["NanumBarunGothic.ttf: Name Table entry"]
  • : ["NanumBarunGothic.ttf: Name Table entry"] [code: mismatch]
  • 🔥 FAIL NanumBarunGothicBold.ttf: Name Table entry: Copyright notices should match a pattern similar to:

"Copyright 2020 The Familyname Project Authors (git url)"

But instead we have got:

"copyright (c) 2013 nhn corporation. all rights reserved. font designed by fontrix inc." [code: bad-notice-format]

  • 🔥 FAIL NanumBarunGothicBold.ttf: Name Table entry: Copyright notices should match a pattern similar to:

"Copyright 2020 The Familyname Project Authors (git url)"

But instead we have got:

"" [code: bad-notice-format]

  • 🔥 FAIL NanumBarunGothicBold.ttf: Name Table entry: Copyright notices should match a pattern similar to:

"Copyright 2020 The Familyname Project Authors (git url)"

But instead we have got:

"copyright ⓒ 2013 nhn corporation. all rights reserved. font designed by fontrix inc." [code: bad-notice-format]

  • 🔥 FAIL METADATA.pb: Copyright notices should match a pattern similar to:

"Copyright 2020 The Familyname Project Authors (git url)"

But instead we have got:

"copyright ⓒ 2013 nhn corporation. all rights reserved. font designed by fontrix inc." [code: bad-notice-format]

  • 🔥 FAIL Copyright notices differ between name table entries and METADATA.pb. The following entries were found:
  • copyright (c) 2013 nhn corporation. all rights reserved. font designed by fontrix inc.: ["NanumBarunGothicBold.ttf: Name Table entry"]
  • : ["NanumBarunGothicBold.ttf: Name Table entry"]
  • copyright ⓒ 2013 nhn corporation. all rights reserved. font designed by fontrix inc.: ["NanumBarunGothicBold.ttf: Name Table entry", "METADATA.pb"] [code: mismatch]
  • 🔥 FAIL NanumBarunGothicLight.ttf: Name Table entry: Copyright notices should match a pattern similar to:

"Copyright 2020 The Familyname Project Authors (git url)"

But instead we have got:

"copyright (c) 2014 nhn corporation. all rights reserved. font designed by fontrix inc." [code: bad-notice-format]

  • 🔥 FAIL NanumBarunGothicLight.ttf: Name Table entry: Copyright notices should match a pattern similar to:

"Copyright 2020 The Familyname Project Authors (git url)"

But instead we have got:

"" [code: bad-notice-format]

  • 🔥 FAIL NanumBarunGothicLight.ttf: Name Table entry: Copyright notices should match a pattern similar to:

"Copyright 2020 The Familyname Project Authors (git url)"

But instead we have got:

"copyright (c) 2014 nhn corporation. all rights reserved. font designed by fontrix inc." [code: bad-notice-format]

  • 🔥 FAIL METADATA.pb: Copyright notices should match a pattern similar to:

"Copyright 2020 The Familyname Project Authors (git url)"

But instead we have got:

"copyright (c) 2014 nhn corporation. all rights reserved. font designed by fontrix inc." [code: bad-notice-format]

  • 🔥 FAIL Copyright notices differ between name table entries and METADATA.pb. The following entries were found:
  • copyright (c) 2014 nhn corporation. all rights reserved. font designed by fontrix inc.: ["NanumBarunGothicLight.ttf: Name Table entry", "NanumBarunGothicLight.ttf: Name Table entry", "METADATA.pb"]
  • : ["NanumBarunGothicLight.ttf: Name Table entry"] [code: mismatch]
  • 🔥 FAIL NanumBarunGothicUltraLight.ttf: Name Table entry: Copyright notices should match a pattern similar to:

"Copyright 2020 The Familyname Project Authors (git url)"

But instead we have got:

"copyright (c) 2015 nhn corporation. all rights reserved. font designed by fontrix inc." [code: bad-notice-format]

  • 🔥 FAIL NanumBarunGothicUltraLight.ttf: Name Table entry: Copyright notices should match a pattern similar to:

"Copyright 2020 The Familyname Project Authors (git url)"

But instead we have got:

"" [code: bad-notice-format]

  • 🔥 FAIL NanumBarunGothicUltraLight.ttf: Name Table entry: Copyright notices should match a pattern similar to:

"Copyright 2020 The Familyname Project Authors (git url)"

But instead we have got:

"copyright (c) 2015 nhn corporation. all rights reserved. font designed by fontrix inc." [code: bad-notice-format]

  • 🔥 FAIL METADATA.pb: Copyright notices should match a pattern similar to:

"Copyright 2020 The Familyname Project Authors (git url)"

But instead we have got:

"copyright (c) 2015 nhn corporation. all rights reserved. font designed by fontrix inc." [code: bad-notice-format]

  • 🔥 FAIL Copyright notices differ between name table entries and METADATA.pb. The following entries were found:
  • : ["NanumBarunGothicUltraLight.ttf: Name Table entry"]
  • copyright (c) 2015 nhn corporation. all rights reserved. font designed by fontrix inc.: ["NanumBarunGothicUltraLight.ttf: Name Table entry", "NanumBarunGothicUltraLight.ttf: Name Table entry", "METADATA.pb"] [code: mismatch]
🔥 FAIL Check copyright namerecords match license file. (googlefonts/name/license)
  • 🔥 FAIL License file OFL.txt exists but NameID 13 (LICENSE DESCRIPTION) value on platform 1 is not specified for that.
    Value was: "NHN Corporation"
    Must be changed to "This Font Software is licensed under the SIL Open Font License, Version 1.1. This license is available with a FAQ at: https://openfontlicense.org" [code: wrong]

  • 🔥 FAIL License file OFL.txt exists but NameID 13 (LICENSE DESCRIPTION) value on platform 3 is not specified for that.
    Value was: "NHN Corporation"
    Must be changed to "This Font Software is licensed under the SIL Open Font License, Version 1.1. This license is available with a FAQ at: https://openfontlicense.org" [code: wrong]

  • 🔥 FAIL License file OFL.txt exists but NameID 13 (LICENSE DESCRIPTION) value on platform 1 is not specified for that.
    Value was: "NHN Corporation"
    Must be changed to "This Font Software is licensed under the SIL Open Font License, Version 1.1. This license is available with a FAQ at: https://openfontlicense.org" [code: wrong]

  • 🔥 FAIL License file OFL.txt exists but NameID 13 (LICENSE DESCRIPTION) value on platform 3 is not specified for that.
    Value was: "NHN Corporation"
    Must be changed to "This Font Software is licensed under the SIL Open Font License, Version 1.1. This license is available with a FAQ at: https://openfontlicense.org" [code: wrong]

  • 🔥 FAIL License file OFL.txt exists but NameID 13 (LICENSE DESCRIPTION) value on platform 1 is not specified for that.
    Value was: "NHN Corporation"
    Must be changed to "This Font Software is licensed under the SIL Open Font License, Version 1.1. This license is available with a FAQ at: https://openfontlicense.org" [code: wrong]

  • 🔥 FAIL License file OFL.txt exists but NameID 13 (LICENSE DESCRIPTION) value on platform 3 is not specified for that.
    Value was: "NHN Corporation"
    Must be changed to "This Font Software is licensed under the SIL Open Font License, Version 1.1. This license is available with a FAQ at: https://openfontlicense.org" [code: wrong]

  • 🔥 FAIL License file OFL.txt exists but NameID 13 (LICENSE DESCRIPTION) value on platform 1 is not specified for that.
    Value was: "NHN Corporation"
    Must be changed to "This Font Software is licensed under the SIL Open Font License, Version 1.1. This license is available with a FAQ at: https://openfontlicense.org" [code: wrong]

  • 🔥 FAIL License file OFL.txt exists but NameID 13 (LICENSE DESCRIPTION) value on platform 3 is not specified for that.
    Value was: "NHN Corporation"
    Must be changed to "This Font Software is licensed under the SIL Open Font License, Version 1.1. This license is available with a FAQ at: https://openfontlicense.org" [code: wrong]

🔥 FAIL Check Google Fonts glyph coverage. (googlefonts/glyph_coverage)
  • 🔥 FAIL NanumBarunGothic.ttf missing required codepoints:
  • 0x2212: MINUS SIGN [code: missing-codepoints]
  • 🔥 FAIL NanumBarunGothicBold.ttf missing required codepoints:
  • 0x2212: MINUS SIGN [code: missing-codepoints]
  • 🔥 FAIL NanumBarunGothicLight.ttf missing required codepoints:
  • 0x2212: MINUS SIGN [code: missing-codepoints]
  • 🔥 FAIL NanumBarunGothicUltraLight.ttf missing required codepoints:
  • 0x2212: MINUS SIGN [code: missing-codepoints]
⚠️ WARN Fonts have consistent PANOSE family type? (opentype/family/panose_familytype)
  • ⚠️ WARN PANOSE family type is not the same across this family. In order to fix this, please make sure that the panose.bFamilyType value is the same in the OS/2 table of all of this family's font files.

The following values were found:

  • Latin Text: NanumBarunGothic.ttf
  • Latin Text: NanumBarunGothicBold.ttf
  • Latin Text: NanumBarunGothicLight.ttf
  • Unknown (0): NanumBarunGothicUltraLight.ttf [code: inconsistency]
⚠️ WARN METADATA.pb: Check for primary_script (googlefonts/metadata/primary_script)
  • ⚠️ WARN METADATA.pb: primary_script field should be 'Hang' but is missing. [code: missing-primary-script]

  • ⚠️ WARN METADATA.pb: primary_script field should be 'Hang' but is missing. [code: missing-primary-script]

  • ⚠️ WARN METADATA.pb: primary_script field should be 'Hang' but is missing. [code: missing-primary-script]

  • ⚠️ WARN METADATA.pb: primary_script field should be 'Hang' but is missing. [code: missing-primary-script]

⚠️ WARN METADATA.pb subsets are correct? (googlefonts/metadata/subsets_correct)
  • ⚠️ WARN Please add 'chinese-traditional' to METADATA.pb since more than 50% of its glyphs are supported by this font file. [code: missing-subset]

  • ⚠️ WARN Please add 'cyrillic' to METADATA.pb since more than 50% of its glyphs are supported by this font file. [code: missing-subset]

  • ⚠️ WARN Please add 'chinese-hongkong' to METADATA.pb since more than 50% of its glyphs are supported by this font file. [code: missing-subset]

  • ⚠️ WARN Please add 'japanese' to METADATA.pb since more than 50% of its glyphs are supported by this font file. [code: missing-subset]

  • ⚠️ WARN Please add 'chinese-simplified' to METADATA.pb since more than 50% of its glyphs are supported by this font file. [code: missing-subset]

⚠️ WARN Check for codepoints not covered by METADATA subsets. (googlefonts/metadata/unreachable_subsetting)
  • ⚠️ WARN NanumBarunGothic.ttf: The following codepoints supported by the font are not covered by any subsets defined in the font's metadata file, and will never be served. You can solve this by either manually adding additional subset declarations to METADATA.pb, or by editing the glyphset definitions.
  • U+0002 : try adding symbols
  • U+0009 : try adding symbols
  • U+000A : try adding symbols
  • U+0111 LATIN SMALL LETTER D WITH STROKE: try adding one of: latin-ext, vietnamese
  • U+0126 LATIN CAPITAL LETTER H WITH STROKE: try adding latin-ext
  • U+0127 LATIN SMALL LETTER H WITH STROKE: try adding latin-ext
  • U+0132 LATIN CAPITAL LIGATURE IJ: try adding latin-ext
  • U+0133 LATIN SMALL LIGATURE IJ: try adding latin-ext
  • U+0138 LATIN SMALL LETTER KRA: try adding latin-ext
    ... and 5338 others

Or you can add the above codepoints to one of the subsets supported by the font: korean, latin, menu [code: unreachable-subsetting]

  • ⚠️ WARN NanumBarunGothicBold.ttf: The following codepoints supported by the font are not covered by any subsets defined in the font's metadata file, and will never be served. You can solve this by either manually adding additional subset declarations to METADATA.pb, or by editing the glyphset definitions.
  • U+0002 : try adding symbols
  • U+0009 : try adding symbols
  • U+000A : try adding symbols
  • U+0111 LATIN SMALL LETTER D WITH STROKE: try adding one of: latin-ext, vietnamese
  • U+0126 LATIN CAPITAL LETTER H WITH STROKE: try adding latin-ext
  • U+0127 LATIN SMALL LETTER H WITH STROKE: try adding latin-ext
  • U+0132 LATIN CAPITAL LIGATURE IJ: try adding latin-ext
  • U+0133 LATIN SMALL LIGATURE IJ: try adding latin-ext
  • U+0138 LATIN SMALL LETTER KRA: try adding latin-ext
    ... and 5338 others

Or you can add the above codepoints to one of the subsets supported by the font: korean, latin, menu [code: unreachable-subsetting]

  • ⚠️ WARN NanumBarunGothicLight.ttf: The following codepoints supported by the font are not covered by any subsets defined in the font's metadata file, and will never be served. You can solve this by either manually adding additional subset declarations to METADATA.pb, or by editing the glyphset definitions.
  • U+0001 : try adding symbols
  • U+0002 : try adding symbols
  • U+0003 : try adding symbols
  • U+0004 : try adding symbols
  • U+0005 : try adding symbols
  • U+0006 : try adding symbols
  • U+0007 : try adding symbols
  • U+0008 : try adding symbols
  • U+0009 : try adding symbols
    ... and 5397 others

Or you can add the above codepoints to one of the subsets supported by the font: korean, latin, menu [code: unreachable-subsetting]

  • ⚠️ WARN NanumBarunGothicUltraLight.ttf: The following codepoints supported by the font are not covered by any subsets defined in the font's metadata file, and will never be served. You can solve this by either manually adding additional subset declarations to METADATA.pb, or by editing the glyphset definitions.
  • U+0001 : try adding symbols
  • U+0002 : try adding symbols
  • U+0003 : try adding symbols
  • U+0004 : try adding symbols
  • U+0005 : try adding symbols
  • U+0006 : try adding symbols
  • U+0007 : try adding symbols
  • U+0008 : try adding symbols
  • U+0009 : try adding symbols
    ... and 5397 others

Or you can add the above codepoints to one of the subsets supported by the font: korean, latin, menu [code: unreachable-subsetting]

ℹ️ INFO Check for presence of an ARTICLE.en_us.html file (googlefonts/description/has_article)
  • ℹ️ INFO This font doesn't have an ARTICLE.en_us.html file. [code: missing-article]
ℹ️ INFO Check axis ordering on the STAT table. (googlefonts/STAT/axis_order)
  • ℹ️ INFO All of the fonts lack a STAT table. [code: summary]
[4] METADATA.pb
🔥 FAIL Check font family directory name. (googlefonts/metadata/family_directory_name)
  • 🔥 FAIL Family name on METADATA.pb is "NanumBarunGothic"
    Directory name is "monolith-jaehoon google-fonts nanumbarungothic ofl-nanumbarungothic"
    Expected "nanumbarungothic" [code: bad-directory-name]
🔥 FAIL Check METADATA.pb parses correctly (googlefonts/metadata/validate)
  • 🔥 FAIL METADATA.pb: Mismatch between postScriptName 400 and and weight value (NanumBarunGothic). The name must end with Regular or Italic [code: mismatch]

  • 🔥 FAIL METADATA.pb: Mismatch between postScriptName 600 and and weight value (NanumBarunGothicBold). The name must end with SemiBold or SemiBoldItalic [code: mismatch]

  • 🔥 FAIL METADATA.pb: Mismatch between postScriptName 200 and and weight value (NanumBarunGothicUltraLight). The name must end with ExtraLight or ExtraLightItalic [code: mismatch]

  • ℹ️ INFO Please consider adding a family.minisite_url entry. [code: lacks-minisite-url]

🔥 FAIL METADATA.pb: Copyright notice is the same in all fonts? (googlefonts/metadata/copyright)
  • 🔥 FAIL METADATA.pb: Copyright field value is inconsistent across the family.
    The following copyright values were found:

The following values were found:

  • Copyright ⓒ 2013 NHN Corporation. All rights reserved. Font designed by FONTRIX Inc.: NanumBarunGothic.ttf
  • Copyright ⓒ 2013 NHN Corporation. All rights reserved. Font designed by FONTRIX Inc.: NanumBarunGothicBold.ttf
  • Copyright (c) 2014 NHN Corporation. All rights reserved. Font designed by FONTRIX Inc.: NanumBarunGothicLight.ttf
  • Copyright (c) 2015 NHN Corporation. All rights reserved. Font designed by FONTRIX Inc.: NanumBarunGothicUltraLight.ttf [code: inconsistency]
⚠️ WARN METADATA.pb: Designers are listed correctly on the Google Fonts catalog? (googlefonts/metadata/designer_profiles)
  • ⚠️ WARN It seems that fontrix is still not listed on the designers catalog. Please submit a photo and a link to a webpage where people can learn more about the work of this designer/typefoundry. [code: profile-not-found]
[34] NanumBarunGothicBold.ttf
🔥 FAIL Check name table for empty records. (opentype/name/empty_records)
  • 🔥 FAIL Empty name record found for name ID=COPYRIGHT_NOTICE platform ID=1 encoding ID=3 [code: empty-record]

  • 🔥 FAIL Empty name record found for name ID=FAMILY_NAME platform ID=1 encoding ID=3 [code: empty-record]

  • 🔥 FAIL Empty name record found for name ID=SUBFAMILY_NAME platform ID=1 encoding ID=3 [code: empty-record]

  • 🔥 FAIL Empty name record found for name ID=FULL_NAME platform ID=1 encoding ID=3 [code: empty-record]

  • 🔥 FAIL Empty name record found for name ID=DESIGNER platform ID=1 encoding ID=3 [code: empty-record]

  • 🔥 FAIL Empty name record found for name ID=POSTSCRIPT_CID_NAME platform ID=1 encoding ID=3 [code: empty-record]

🔥 FAIL Ensure the font supports case swapping for all its glyphs. (case_mapping)
  • 🔥 FAIL The following glyphs are missing case-swapping counterparts:
Glyph present in the font Missing case-swapping counterpart
U+212B: ANGSTROM SIGN U+00E5: LATIN SMALL LETTER A WITH RING ABOVE
U+0111: LATIN SMALL LETTER D WITH STROKE U+0110: LATIN CAPITAL LETTER D WITH STROKE
🔥 FAIL Does font file include unacceptable control character glyphs? (control_chars)
  • 🔥 FAIL The following unacceptable control characters were identified:
  • U+0002 (cid18363)
  • U+0009 (cid18370)
  • U+000A (cid18371) [code: unacceptable]
🔥 FAIL Font contains '.notdef' as its first glyph? (mandatory_glyphs)
  • 🔥 FAIL The '.notdef' glyph should contain a drawing, but it is blank. [code: notdef-is-blank]
🔥 FAIL Ensure smart dropout control is enabled in "prep" table instructions. (smart_dropout)
  • 🔥 FAIL The 'prep' table does not contain TrueType instructions enabling smart dropout control. To fix, export the font with autohinting enabled, or run ttfautohint on the font, or run the gftools fix-nonhinting script. [code: lacks-smart-dropout]
🔥 FAIL Are there unwanted tables? (unwanted_tables)
  • 🔥 FAIL Unwanted tables found:
    Table: FFTM Reason: Table contains redundant FontForge timestamp info
    [code: unwanted-tables]
🔥 FAIL Glyph names are all valid? (valid_glyphnames)
  • 🔥 FAIL Glyph 0x00A0 is called cid18419; must be named 'uni00A0'. [code: non-compliant-00A0]

  • 🔥 FAIL Glyph 0x0020 is called cid1; must be named 'space'. [code: non-compliant-0020]

🔥 FAIL Whitespace glyphs have ink? (whitespace_ink)
  • 🔥 FAIL The following glyphs have ink; they should be replaced by an empty glyph:
  • cid101 [code: has-ink]
🔥 FAIL Space and non-breaking space have the same width? (whitespace_widths)
  • 🔥 FAIL The space glyph named cid1 is 224 font units wide, non-breaking space named (cid18419) is 297 font units wide, and both should be positive and the same. GlyphsApp has "Sidebearing arithmetic" (https://glyphsapp.com/tutorials/spacing) which allows you to set the non-breaking space width to always equal the space width. [code: different-widths]
🔥 FAIL Check family name for GF Guide compliance. (googlefonts/name/family_name_compliance)
  • 🔥 FAIL "NanumBarunGothic" is a CamelCased name. To solve this, simply use spaces instead in the font name. [code: camelcase]
🔥 FAIL Checking file is named canonically. (googlefonts/canonical_filename)
  • 🔥 FAIL Expected "NanumBarunGothic-Bold.ttf". Got "NanumBarunGothicBold.ttf". [code: bad-filename]
🔥 FAIL Check font follows the Google Fonts CJK vertical metric schema (googlefonts/cjk_vertical_metrics)
  • 🔥 FAIL OS/2 fsSelection bit 7 must be enabled [code: bad-fselection-bit7]

  • 🔥 FAIL OS/2.sTypoAscender is 850; it should be between 882 and 932 [code: bad-OS/2.sTypoAscender]

  • 🔥 FAIL OS/2.sTypoDescender is -300; it should be between -268 and -218 [code: bad-OS/2.sTypoDescender]

  • 🔥 FAIL OS/2.usWinAscent is 850; it should be 838 [code: bad-OS/2.usWinAscent]

  • 🔥 FAIL OS/2.usWinDescent is 300; it should be 289 [code: bad-OS/2.usWinDescent]

  • 🔥 FAIL hhea.descent must match absolute value of OS/2.sTypoDescender [code: descent-mismatch]

  • 🔥 FAIL A BASE table with correct icfb/icft/ideo/romn and idtp baselines should be present [code: missing-BASE-table]

  • 🔥 FAIL A vmtx table should be present [code: missing-vmtx-table]

  • 🔥 FAIL A vhea table should be present [code: missing-vhea-table]

  • ℹ️ INFO Computed BASE table entries:

Baseline Computed
Horizontal icfb -118
Horizontal icft 782
Horizontal ideo -167
Horizontal idtp 832
Horizontal romn 0
Vertical icfb 28
Vertical icft 859
Vertical ideo 0
Vertical idtp 892
Vertical romn 167
🔥 FAIL Check font names are correct (googlefonts/font_names)
  • 🔥 FAIL Font names are incorrect:
Name Current Expected
Family Name NanumBarunGothic NanumBarunGothic
Subfamily Name Bold Bold
Full Name NanumBarunGothic Bold NanumBarunGothic Bold
Postscript Name NanumBarunGothicBold NanumBarunGothic-Bold
Typographic Family Name NanumBarunGothic 나눔바른고딕
Typographic Subfamily Name Bold Bold
🔥 FAIL Checking OS/2 fsType does not impose restrictions. (googlefonts/fstype)
  • 🔥 FAIL In this font fsType is set to 8 meaning that:
  • The font may be embedded but must only be installed temporarily on other systems.

No such DRM restrictions can be enabled on the Google Fonts collection, so the fsType field must be set to zero (Installable Embedding) instead. [code: drm]

🔥 FAIL Font has all mandatory 'name' table entries? (googlefonts/name/mandatory_entries)
  • 🔥 FAIL Font lacks entry with nameId=1 (FAMILY_NAME) [code: missing-entry]

  • 🔥 FAIL Font lacks entry with nameId=2 (SUBFAMILY_NAME) [code: missing-entry]

  • 🔥 FAIL Font lacks entry with nameId=4 (FULL_NAME) [code: missing-entry]

  • 🔥 FAIL Font lacks entry with nameId=9 (DESIGNER) [code: missing-entry]

🔥 FAIL Check the OS/2 usWeightClass is appropriate for the font's best SubFamily name. (googlefonts/weightclass)
  • 🔥 FAIL Best SubFamily name is 'Bold'. Expected OS/2 usWeightClass is 700, got 600. [code: bad-value]
⚠️ WARN Check for points out of bounds (opentype/points_out_of_bounds)
  • ⚠️ WARN The following glyphs have coordinates which are out of bounds:
  • cid75 (y=-292, bounds are -289<->753)
  • cid95 (y=261, bounds are 262<->457)
  • cid95 (y=458, bounds are 262<->457)
  • cid155 (x=19, bounds are 26<->422)
  • cid199 (x=568, bounds are 322<->567)
  • cid199 (y=619, bounds are 621<->803)
  • cid199 (x=319, bounds are 322<->567)
  • cid199 (y=804, bounds are 621<->803)
  • cid244 (y=740, bounds are -157<->739)
    ... and 733 others

This happens a lot when points are not extremes, which is usually bad. However, fixing this alert by adding points on extremes may do more harm than good, especially with italics, calligraphic-script, handwriting, rounded and other fonts. So it is common to ignore this message. [code: points-out-of-bounds]

⚠️ WARN Does the font contain chws and vchw features? (cjk_chws_feature)
⚠️ WARN Check if each glyph has the recommended amount of contours. (contour_count)
  • ⚠️ WARN This check inspects the glyph outlines and detects the total number of contours in each of them. The expected values are
    inferred from the typical amounts of contours observed in a
    large collection of reference font families. The divergences
    listed below may simply indicate a significantly different
    design on some of your glyphs. On the other hand, some of these
    may flag actual bugs in the font such as glyphs mapped to an
    incorrect codepoint. Please consider reviewing the design and
    codepoint assignment of these to make sure they are correct.

    The following glyphs do not have the recommended number of contours:

  • cid61 (U+005C): found 4, expected one of: {1, 5}
  • cid8664 (U+262F): found 2, expected one of: {4}
  • cid8655 (U+E23B): found 4, expected one of: {1, 3, 2}
  • cid8636 (U+E22A): found 4, expected one of: {1, 3, 2}
  • cid8646 (U+E232): found 5, expected one of: {1, 3, 2}
  • cid8668 (U+E247): found 6, expected one of: {1, 2, 3}
  • cid8622 (U+E21F): found 4, expected one of: {1, 2, 3}
  • cid379 (U+3146): found 2, expected one of: {1, 4}
  • cid2381 (U+C384): found 4, expected one of: {7, 3, 2}
    ... and 27 others [code: contour-count]
⚠️ WARN Ensure files are not too large. (file_size)
  • ⚠️ WARN Font file is 4.42 MB; ideally it should be less than 1.05 MB [code: large-font]
⚠️ WARN Check math signs have the same width. (math_signs_width)
  • ⚠️ WARN The most common width is 892 among a set of 72 math glyphs.
    The following math glyphs have a different width, though:
    width=446: cid31, cid29
    width=583: cid12, cid30 [code: width-outliers]
⚠️ WARN Ensure indic fonts have the Indian Rupee Sign glyph. (rupee)
  • ⚠️ WARN Font is missing the Indian Rupee Sign glyph. Please add a glyph for Indian Rupee Sign (₹) at codepoint U+20B9. [code: missing-rupee]
⚠️ WARN Does the font contain a soft hyphen? (soft_hyphen)
  • ⚠️ WARN This font has a 'Soft Hyphen' character. [code: softhyphen]
⚠️ WARN Check font contains no unreachable glyphs (unreachable_glyphs)
  • ⚠️ WARN The following glyphs could not be reached by codepoint or substitution rules:
  • .null
  • nonmarkingreturn
  • glyph19342
  • glyph19343 [code: unreachable-glyphs]
⚠️ WARN Font has correct separator glyphs? (googlefonts/separator_glyphs)
  • ⚠️ WARN The following separator glyphs are missing:
  • U+2028
  • U+2029 [code: missing-separator-glyphs]
⚠️ WARN Check the direction of the outermost contour in each glyph (outline_direction)
  • ⚠️ WARN The following glyphs have a counter-clockwise outer contour:
  • cid6323 (U+6109) has a counter-clockwise outer contour
  • cid6801 (U+7167) has a counter-clockwise outer contour
  • cid6507 (U+8CC7) has a counter-clockwise outer contour
  • cid6679 (U+942B) has a counter-clockwise outer contour [code: ccw-outer-contour]
⚠️ WARN Do outlines contain any jaggy segments? (outline_jaggy_segments)
  • ⚠️ WARN The following glyphs have jaggy segments:
  • cid46 (U+004D): Line(Line { p0: (208.0, 507.0), p1: (188.0, 589.0) })/Line(Line { p0: (188.0, 589.0), p1: (190.0, 507.0) }) = 12.309779976783398
  • cid46 (U+004D): Line(Line { p0: (690.0, 507.0), p1: (692.0, 589.0) })/Line(Line { p0: (692.0, 589.0), p1: (672.0, 507.0) }) = 12.309779976783398
  • cid260 (U+2122): Line(Line { p0: (477.0, 622.0), p1: (467.0, 659.0) })/Line(Line { p0: (467.0, 659.0), p1: (468.0, 622.0) }) = 13.575849609332623
  • cid260 (U+2122): Line(Line { p0: (712.0, 622.0), p1: (713.0, 659.0) })/Line(Line { p0: (713.0, 659.0), p1: (703.0, 622.0) }) = 13.575849609332623
  • cid9222 (U+261D): Quad(QuadBez { p0: (382.5, 495.5), p1: (384.0, 452.0), p2: (385.0, 429.0) })/Quad(QuadBez { p0: (385.0, 429.0), p1: (387.0, 452.0), p2: (396.5, 473.0) }) = 7.459293650109428
  • cid9223 (U+261F): Quad(QuadBez { p0: (418.0, 131.0), p1: (409.0, 152.0), p2: (406.0, 175.0) })/Quad(QuadBez { p0: (406.0, 175.0), p1: (405.0, 152.0), p2: (404.0, 108.5) }) = 9.920960893171603
  • cid8664 (U+262F): Quad(QuadBez { p0: (764.5, 241.5), p1: (764.0, 207.0), p2: (754.0, 179.0) })/Quad(QuadBez { p0: (754.0, 179.0), p1: (767.0, 214.0), p2: (771.0, 245.0) }) = 0.7226111557835152
  • cid8668 (U+E247): Quad(QuadBez { p0: (697.5, 322.0), p1: (668.0, 306.0), p2: (634.0, 303.0) })/Quad(QuadBez { p0: (634.0, 303.0), p1: (668.0, 300.0), p2: (697.5, 283.5) }) = 10.084902138341826
  • cid8668 (U+E247): Quad(QuadBez { p0: (463.5, 22.5), p1: (449.0, 55.0), p2: (447.0, 93.0) })/Quad(QuadBez { p0: (447.0, 93.0), p1: (444.0, 55.0), p2: (429.0, 22.5) }) = 7.526775962184584
    ... and 761 others [code: found-jaggy-segments]
⚠️ WARN Check there are no overlapping path segments (overlapping_path_segments)
  • ⚠️ WARN The following glyphs have overlapping path segments:
  • cid6090 (U+58C5): Quad(QuadBez { p0: (398.0, 376.0), p1: (408.0, 375.0), p2: (401.0, 379.0) }) has the same coordinates as a previous segment.
  • cid3480 (U+59E6): Quad(QuadBez { p0: (289.0, 456.0), p1: (287.0, 458.0), p2: (286.0, 458.0) }) has the same coordinates as a previous segment.
  • cid5853 (U+6396): Line(Line { p0: (647.0, 413.0), p1: (649.0, 410.0) }) has the same coordinates as a previous segment.
  • cid4583 (U+700F): Quad(QuadBez { p0: (404.0, 556.0), p1: (404.0, 555.0), p2: (405.0, 555.0) }) has the same coordinates as a previous segment.
  • cid4423 (U+840A): Quad(QuadBez { p0: (271.0, 181.0), p1: (271.0, 182.0), p2: (270.0, 182.0) }) has the same coordinates as a previous segment.
  • cid7903 (U+95CA): Quad(QuadBez { p0: (385.0, 316.0), p1: (385.0, 317.0), p2: (384.0, 318.0) }) has the same coordinates as a previous segment.
  • cid7669 (U+965C): Quad(QuadBez { p0: (647.0, 224.0), p1: (647.0, 223.0), p2: (648.0, 222.0) }) has the same coordinates as a previous segment.
  • cid9272 (U+E44B): Quad(QuadBez { p0: (718.5, 648.0), p1: (720.0, 648.0), p2: (716.5, 647.0) }) has the same coordinates as a previous segment. [code: overlapping-path-segments]
⚠️ WARN Do outlines contain any semi-vertical or semi-horizontal lines? (outline_semi_vertical)
  • ⚠️ WARN The following glyphs have semi-vertical/semi-horizontal lines:
  • cid72 (U+0067): Line(Line { p0: (527.0, 521.0), p1: (528.0, 10.0) })
  • cid244 (U+00B6): Line(Line { p0: (470.0, -157.0), p1: (469.0, 311.0) })
  • cid763 (U+0138): Line(Line { p0: (713.0, -91.0), p1: (566.0, -90.0) })
  • cid763 (U+0138): Line(Line { p0: (533.0, 481.0), p1: (681.0, 482.0) })
  • cid471 (U+0391): Line(Line { p0: (377.0, 212.0), p1: (610.0, 211.0) })
  • cid472 (U+0392): Line(Line { p0: (325.0, 696.0), p1: (550.0, 695.0) })
  • cid474 (U+0394): Line(Line { p0: (645.0, 25.0), p1: (646.0, 526.0) })
  • cid1021 (U+0411): Line(Line { p0: (325.0, 383.0), p1: (487.0, 382.0) })
  • cid1021 (U+0411): Line(Line { p0: (503.0, -88.0), p1: (198.0, -87.0) })
    ... and 1374 others [code: found-semi-vertical]
⚠️ WARN Is the Grid-fitting and Scan-conversion Procedure ('gasp') table set to optimize rendering? (googlefonts/gasp)
  • ℹ️ INFO These are the ppm ranges declared on the gasp table:

| PPM <= 10 | - Use grayscale rendering |
| | - Use gridfitting with ClearType symmetric smoothing |

- Use smoothing along multiple axes with ClearType®
PPM <= 16 - Use grid-fitting
- Use grayscale rendering
- Use gridfitting with ClearType symmetric smoothing
PPM <= 65535 - Use grid-fitting
- Use grayscale rendering
- Use gridfitting with ClearType symmetric smoothing
- Use smoothing along multiple axes with ClearType®
[code: ranges]
  • ⚠️ WARN The gasp table has a range of 10 that may be unneccessary. [code: non-ffff-range]

  • ⚠️ WARN The gasp table has a range of 16 that may be unneccessary. [code: non-ffff-range]

⚠️ WARN Ensure fonts have ScriptLangTags declared on the 'meta' table. (googlefonts/meta/script_lang_tags)
  • ⚠️ WARN This font file does not have a 'meta' table. [code: lacks-meta-table]
ℹ️ INFO Show hinting filesize impact. (hinting_impact)
  • ℹ️ INFO Hinting filesize impact:
NanumBarunGothicBold.ttf
Dehinted Size 3475416
Hinted Size 4415956
Increase 940540
Change 27.1 %
ℹ️ INFO Font contains all required tables? (required_tables)
  • ℹ️ INFO This font contains the following optional tables:

    cvt
    fpgm
    loca
    prep
    GPOS
    GSUB
    gasp
    kern [code: optional-tables]

ℹ️ INFO Font has old ttfautohint applied? (googlefonts/old_ttfautohint)
  • ℹ️ INFO Could not detect which version of ttfautohint was used in this font. It is typically specified as a comment in the font version entries of the 'name' table. Such font version strings are currently: Version 1.000 2013 initial release, Version 1.000 2013 initial release [code: version-not-detected]

Summary

💥 ERROR 🔥 FAIL ⚠️ WARN ℹ️ INFO ✅ PASS ⏩ SKIP
5 221 90 22 260 234
1% 34% 14% 3% 40% 36%

@emmamarichal
Copy link
Collaborator

If you interested in updating these, please let us know on the issue once it's ready, I will be happy to review it :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: PR GF

Development

Successfully merging this pull request may close these issues.

2 participants