What's the syntax of the s/u/d? Should it always be the first character in the glyph name? In feta-bolletjes.mf, I see:
fet_beginchar("Whole Crossed notehead", "s0cross", "wholecrossedhead") (i.e. "s" as first character before duration), but also: fet_beginchar("Half Crossed notehead", "1scross", "halfcrossedhead") (i.e. after the duration). Similarly, in parmesan-heads.mf, after your change, I currently see: fet_beginchar("Mensural maxima notehead", "-s3mensural", "mensuralmaximahead"); (i.e. "s" after "-"), but also: fet_beginchar("Mensural longa notehead", "s-2mensural", "mensurallongahead"); (i.e. "s" before "-"). So, what's the intended syntax? Greetings, Jürgen On Sun, 28 Nov 2004, Han-Wen Nienhuys wrote: > [EMAIL PROTECTED] writes: > > > > > > On Sat, 27 Nov 2004, Erik Sandberg wrote: > > > > > On Friday 26 November 2004 23.11, Juergen Reuter wrote: > > > > Hi! > > > > > > > > Hmmh, it seems something changed between 2.5.1 and 2.5.2 such that > > > > ligatures are (once again) broken, see e.g. manual, sections 5.16.10.1 > > > > and > > > > 5.16.11: some heads of the ligatures are missing. Maybe someone changed > > > > something relevant in the parser? > > > > > > Did you rebuild your fonts? (try make clean;make or similar) > > > > > > > I just looked at the documentation for 2.5.2 on the lilypond website. > > Maybe Han-Wen did not rebuild the fonts. However, I am pretty sure he > > did, because otherwise the neumes table in section 5.16.10.2 (Gregorian > > square neumes ligatures) would also have been messed up; but the table > > looks fine. Hence, I guess it's not a font problem, but rather a problem > > of the engravers catching the right music events, which may be related to > > some recent change in the parser (just a guess). > > The note heads were changed to include s (Symmetrical), u > (upstem) and d (downstem) in the glyphname. Can you check if I forgot > some of the ancient ones? > > > -- > > Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen > _______________________________________________ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel