Put Robert’s script in the same directory as the SFD font file because that makes the command line stuff a little easier.Įdit: create also a folder named “json” in this directory! If you have an existing SMuFL font, load it first in FontForge and proceed as described above. Create your own SMuFl font or find a SMuFl font that does not have a json file.Īfter you created your font save the FontForge SFD file, preferably with a name that does not have any spaces in it. You will have to copy the whole code in a text editor and save it as: “generate_font_metadata.py” You can find the last version of FontForge here: FontForge Open Source Font Editor He gave me a comprehensive step by step explanation on how to use the Robert Piechaud script.īefore I write the steps down here are the necessary things you must do before you can run the script. Piechaud script.īTW I now realized that the Bravura json file contains 32152 lines of code for the “glyphBBoxes” metadata and as far as I understand these metadata are only for Finale and they are of no use for Dorico!Ĭonsidering that the whole Bravura json file has 43481 lines I find it quite amazing:ģ2152 lines for Finale and 11329 for Dorico!įor the sake of completeness I write down the last results.Ībraham Lee from Music Type Foundry was so kind to help me. I now must learn to understand what all the Metadata do for the font and what is the difference between an empty json file and one with all metadata.Īnd I still was not able to run the R. Of course “myfont” must be installed as any other font and the json file must be in the right folder at the right place. At least it will allow Dorico to recognize the font. Writing the following four lines in a text editor and saving them as “myfont.json” will work as a so to say default or empty metadata file for the font “myfont”. I just created my first json file from scratchĪs written in the SMuFl specification ( ) only the “fontName” and the “fontVersion” are mandatory for the metadata file.
0 Comments
Leave a Reply. |