- From: Andrew Hankinson <andrew.hankinson@gmail.com>
- Date: Wed, 17 Jan 2018 19:13:04 +0000
- To: Glenn Linderman <v+smufl@g.nevcal.com>
- Cc: public-music-notation-contrib@w3.org
There are JSON metadata files that give the names, codepoints, and groups that glyphs belong to: https://github.com/w3c/smufl/tree/gh-pages/metadata It makes it easier to build sites like the SMuFL browser, which is what I suspect Peter is doing. http://edirom.de/smufl-browser/index -Andrew > On 17 Jan 2018, at 19:00, Glenn Linderman <v+smufl@g.nevcal.com> wrote: > > On 1/17/2018 1:40 AM, Peter Stadler wrote: >> Dear all, >> I’m looking for releases of the SMuFL metadata json files. I’m especially interested in the latest stable 1.2(?) version. At https://github.com/w3c/smufl there are no releases at all (as there had been at https://github.com/steinbergmedia/smufl). >> My best guess is, that the official 1.2 version is from 2016-04-25 (as it states at https://w3c.github.io/smufl/gitbook/index.html); hence this would be commit https://github.com/w3c/smufl/commit/c20330a858a6297ed5da45491a9c177531190a7c? >> Could this be tagged accordingly? Additionally, the reference at https://w3c.github.io/smufl/gitbook/specification/ranges.html should be updated to point at the new GitHub release page (my suggestion). >> Many thanks for all the work >> and all the best >> Peter > > I didn't follow your links, but aren't SMuFL metadata a specification for font creators to follow, to provide data about their fonts that adhere to the SMuFL specification? In other words, I don't think there would be a SMuFL metadata file, but there should be a Bravura metadata file, and a metadata file for each other SMuFL-compliant font that is developed. > >
Received on Wednesday, 17 January 2018 19:13:30 UTC