[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: \markup placement (Was: Re: collision barline with accidental)

From: Mats Bengtsson
Subject: Re: \markup placement (Was: Re: collision barline with accidental)
Date: Tue, 21 Aug 2007 12:50:58 +0200
User-agent: Thunderbird (X11/20070716)

The positioning has nothing to do with if you use ^\markup{c} or ^"c".
I the 2.11.x version, the text scripts are placed on several lines if they don't
fit on the same line with the default note spacing.
You can change this with the \fatText macro (see the definition in
ly/ if you want to include the setting in \neumeDemoLayout)
so that the note spacing is increased to make room for the text scripts.


Juergen Reuter wrote:
Hi all,

while you are at it (I mean, the placement/spacing code, though I am not sure if this is anyhow related)...

I noticed that in Manual Sect. ("Gregorian square neumes ligatures") the placement of the letters in the neumes table changes from almost each version of the lily 2.11.x series to the next release: sometimes, the letters appear above the glyph, sometimes below, sometimes they are stacked upon each other, sometimes they appear in a horizontal row, with these flavors mixing even within the same version of lily... Is this intended behavior? (N.B.: In lily 2.10.29, the letters are placed consistently above the glyphs and in horizontal rows.)

Btw., I do not mind where the letters actually appear, as long as the placement is somewhat consistent and it gets clear that each letter is associated with a glyph. Maybe the letters should not be typeset with the \markup command, as it is currently done?


lilypond-devel mailing list

        Mats Bengtsson
        Signal Processing
        Signals, Sensors and Systems
        Royal Institute of Technology
        SE-100 44  STOCKHOLM
        Phone: (+46) 8 790 8463                         
       Fax:   (+46) 8 790 7260
        Email: address@hidden

reply via email to

[Prev in Thread] Current Thread [Next in Thread]