[smufl-discuss] Re: JSON

[Laurent Pugin]

Thanks for your prompt reply. It would indeed be useful to have a
suite of scripts for this.

I am using FontForge, and I have a script for generating the bounding
boxes. I'd be happy to share it too, but it needs to be documented and
also it does not generate anchor data, so I am not sure how useful it
can be. I haven't made use of anchor data yet. Where does it get
actually inserted? In the font itself for each glyph that needs any?
Or are they provided in your internal tool?

Laurent

On Fri, Dec 12, 2014 at 10:15 AM, Daniel Spreadbury
<[hidden email]> wrote:

> Laurent wrote:
>
>>I am looking at generating smufl json files for a font. What is the
>>best way to proceed? Are they any tools available for this? Thanks
>>for any recommendation.
>
> As far as I know, there aren't yet any scripts available to help with this.
>
> We haven't published the scripts we use to work on Bravura, because they are not fully useful on their own: we have an internally developed tool to manage revisions to SMuFL and, consequently, to Bravura, which holds some of the key data (glyph names, stylistic sets, and so on). To populate the anchors and bounding box structures in the JSON, we run a Python script in FontLab that iterates over all of the glyphs, recording their bbox and the positions of any anchors (which is how things like the coordinates for stem connection points, cut-outs in accidentals, and so on, make their way into the JSON).
>
> The output of this script is then loaded into our internal tool, which can then combine that data with the data it already holds about the engraving defaults and stylistic sets included in the font, and produce a combined JSON file with all of the recommended metadata in it.
>
> If you're using FontLab, you might get some use out of the script we use to generate bbox and anchor data, and we would be happy to share it if so, but it won't help you with the engraving defaults and stylistic sets information.
>
> Both Glyphs and FontForge also have quite sophisticated scripting APIs, by the looks of it, so you may well be able to write a script to pull out the necessary information from your font via scripting.
>
> I think it would certainly be beneficial to have a suite of scripts to help font developers generate the JSON metadata they need. Ben and I will think about how best to publish the scripts we have developed for FontLab, and perhaps if you are using another font editor, you might consider contributing any scripts you come up with to the community.
>
> Thanks,
>
> Daniel
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> Steinberg Media Technologies GmbH, Frankenstrasse 18b, D-20097 Hamburg, Germany
> Phone: [phone] | Fax: [phone] | www.steinberg.net
> President: Andreas Stelling | Managing Director: Hiroshi Sasaki, Hirofumi Osawa
> Registration Court: Hamburg HRB 86534
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>
> #############################################################
> This message is sent to you because you are subscribed to
>   the mailing list <[hidden email]>.
> To unsubscribe, E-mail to: <[hidden email]>
> To switch to the DIGEST mode, E-mail to <[hidden email]>
> To switch to the INDEX mode, E-mail to <[hidden email]>
> Send administrative queries to  <[hidden email]>
>

#############################################################
This message is sent to you because you are subscribed to
  the mailing list <[hidden email]>.
To unsubscribe, E-mail to: <[hidden email]>
To switch to the DIGEST mode, E-mail to <[hidden email]>
To switch to the INDEX mode, E-mail to <[hidden email]>
Send administrative queries to  <[hidden email]>