On 6/16/11 6:02 PM, "Aleksandr Andreev" <aleksandr.andr...@gmail.com> wrote:
>>> Replacing the feta font is doable, but not trivial. > > Is there anywhere I can read about how the Feta font is set up? The > font I have is part of our proposal to encode the Kievan glyphs in > Unicode, so it would need to be converted to the format that Feta > uses. Is there a detailed description of this format somewhere? Not really. The Feta font is created from metafont sources, which are found in the mf/ directory of lilypond. New glyphs can be added in the files whose names have no font size embedded, like feta-noteheads.mf. New classes of glyphs can be added by adding new files, like feta-kievan.mf. This is a relatively straightforward process. The font files are created from the .mf files by mf2pt1 and fontforge, IIUC. The Feta font uses code points that are not available for standard Unicode assignment,so LilyPond doesn't use standard code points. Instead, LilyPond uses glyph names to access the glyphs. The unicode code points for glyphs can change between builds. The simplest way to get glyphs into Feta is to write metafont code for the glyphs and add that code to the files in the mf/ directory. I have not looked carefully at how the gonville font is substituted for the the Feta font. Hope this helps, Carl _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
