Handling Fontspector's "codepoints not covered by METADATA subsets"

Daniel Yacob
Daniel Yacob Posts: 22
edited May 19 in Font Technology
Greetings All,

Writing to ask for assistance in tackling this error that appears in Fontspector reports.  The message seems straightforward, but when I make the indicated correction, it makes no impact.  For example:

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+02D8 BREVE: try adding one of: yi, canadian-aboriginal

  Then, adding the following to the  METADATA.pb, and retesting:

subsets: "yi"

the same errors appear, it's like the  METADATA.pb is not being read.  I'd appreciate any suggestions here.

The alternative correction was to edit the glyphset definition, which I believe is referring to the resources here:  https://github.com/googlefonts/glyphsets . I don't know how that would work though, unless I could have local copies that fontspector would read.

thanks!

-Daniel
Tagged:

Answers

  • Simon Cozens
    Simon Cozens Posts: 835
    This isn't really a problem for end users (it relates to the subsetting configuration of the Google Fonts servers), and actually the advice to add a subset purely to make a codepoint get served is frowned upon by the GF engineering team. So this isn't a problem for you to fix; that said, I don't know why the changes don't make the error go away. It should. I'll look into it.

Categories