Include font metadata

[w0ng]

Include font metadata

[judgej]

Putting all the metadata files into a single JSON array is the easy bit:

cat ofl/*/METADATA.json | awk 'BEGIN {print "["} {if (p=="}" && $0=="{") {print ",{"; next;}} {p=$0} {print} END {print "]"}'

That produces a single JSON file containing all the metadata records.

[judgej]

Passsing that combined metadata through a few lines of PHP to extract just the font names and categories, we end up with this, which is not currently available through any Google API:

[excessively long text snipped out - see below]

[Ivoz]

@judgej gists are useful for chucking a document like that json file into without making a long comment.

[judgej]

Good point. gists are one of the many things on my list of "more stuff I need to know how to use".

Here is the file (not in a gist) in a WP plugin:

https://github.com/academe/google-webfonts-for-woo-framework/blob/master/google-fonts-for-woo-framework/category-groups.json

My aim there will be to allow fonts to be filtered by category within the plugin, so a way to keep up-to-date with the font/category lists would be required for that. I'm sure Google will add it to their APIs one day, but it's no there yet.

For now I'm updating a local copy of the massive hg repo, using awk to combine all the metadata files, then PHP to pull out the font names and categories. Will probably put that all up on a website at some point.

But anyway - I can see many other uses for the meatadata, and it does all squeeze into a single 500kbyte JSON file, and I think it would be very useful here without getting in the way. If you don't want to add it, then I do have my own scripts running, so I'll leave it with you :-)

[w0ng]

Retaining original directory structure as the hg repo from now on, so metadata files and licenses are together with their fonts.