LilyPond stores font information here:
/Applications/LilyPond.app/Contents/Resources/share/lilypond/current/fonts
LilyPond does not appear to install these custom fonts in the usual places in the filesystem such that other applications, like Illustrator and InDesign, can find them.
The LilyPond
/fonts
folder contains three subfolders: /otf
, /svg
and /type1
.If you use Apple's FontBook application to load the custom LilyPond fonts, those fonts in
/otf
will load perfectly. But the fonts in /svg
and /type1
will not load at all.The fonts in
/svg
duplicate the fonts in /otf
and so probably aren't necessary under any circumstances to load with FontBook.The fonts in
/type1
are unique and, therefore, probably are necessary. The fonts end in .pfa
and FontBook will not recognize them. The solution is to download FontForge and use FontForge to convert these .pfa
fonts to .otf
fonts. The FontForge UI requires the X11 client, which was available in the Utilities subfolder in my Applications folder without recourse to install discs for the MacBook. Double-click to start the X11 server before double-clicking to start FontForge. Then use FontForge to Open each .pfa
by hand, and then Generate each .pfa
as an .oft
. Generate is apparently FontForge's term for convert or save-as. The process is tedious but works.The resulting 33 new
.otf
fonts load correctly under FontBook.I would publish the zipped file of the complete set of all 46 custom LilyPond fonts as
.otf
here, but I can't figure out how to get Blogger to let me upload a nonimage, nonvideo file.
No comments:
Post a Comment