Re: Text at linebreaks

[Phil Holmes]

----- Original Message ----- 
From: "Graham Percival" <address@hidden>
To: "Phil Holmes" <address@hidden>
Cc: <address@hidden>
Sent: Friday, January 07, 2011 10:08 AM
Subject: Re: Text at linebreaks


> On Fri, Jan 07, 2011 at 09:48:09AM -0000, Phil Holmes wrote:
> > to avoid this, at the penalty of performance.  I now have these 2
> > lines in my Lily source the whole time.  However, I've just tried
> > compiling a 500 bar, 30 page, 19 voice piece of music and compared
> > the processor time with and without those lines. 485.6 seconds with
> > them, 484.6 seconds with - a whole 0.2%.  So there's really no
> > performance penalty to speak of.
>
> How many markups and \mark do you have?  I mean, did you add a
> whole bunch of them to the score?  Also, how long are they?  Were
> they all short "espr." or did you have some
> "this is an artifically long text script" in there?  I would
> imagine that the latter would cause more problems for the musical
> layout, and thus would impact performance more.
>
> Cheers,
> - Graham

It was just a normal score - the Finale of Act I of The Gondoliers.  And 
this is part of the point - it may be that you can construct a test file 
that would impact performance more, but why bother?  On a normal score with 
performers names, tempo indications, etc., as textual markings, there's 
essentially no performance hit.  However, the annoyance of the text flowing 
over the end of a line plus the research to fix it plus the recompile taking 
500 times longer than the actual hit means this should be changed.  We don't 
allow notes to collide as a matter of course to save time, with a note in 
the Learning manual that you can move all the notes.  Why do we allow 
something worse to happen with text?

--
Phil Holmes