Werner, 2011/9/9 <lemzw...@googlemail.com>: > I'm not really happy with the MF code: It looks like a direct > translation of PostScript points into MF points. This definitely works > but is quite clumsy. If you look at the design of other LilyPond > glyphs, you can see that all coordinates rely on meta-parameters which > control the appearance. For your glyphs, we have to directly shift > coordinates in case of a change, with a great chance to inadvertently > break important relationships within the glyph shape. > > I would really like to see a `LilyPond approach' for Kievan notes also, > treating the current approach as a temporary solution.
what do you mean by "let's treat this as a temporary solution"? Do you mean that: 1) it can be pushed in this state so that Aleksandr can proceed on getting Kievan notation to work (by adding KievanStaff, KievanVoice and so on), but when support for Kievan notation is established, the metafont code should be rewritten to be more LilyPond-esque, or 2) it cannot be pushed in this state and it must be rewritten before any other work on Kievan notation could be done, or something else? cheers, Janek _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
