I agree that when a long markup stretches the measure at the end of a line,
it suggests that there may be better ways of laying out the line breaks.
Perhaps there should be a penalty for stretched measures due to markup in
Lilypond's line breaking algorithm?
Saul
On Sat, Mar 16, 2019, 6:34 PM
Hi edes,
Look at LSR 829. This is exactly your case, and what I was saying, The line
break is such that the very long text is all on one line. I believe this is
the conventional way to handle this.
Andrew
___
lilypond-user mailing list
Hi edes,
Well, if absolute line breaking is not important in your score, you could
always put a break in front of the bar with the long text. In terms of
engraving, which to me is all about clarity for musicians to read, you
don't see many examples of this, as it is indeed hard to read a note
I am now using edition-engraver and page-layout. I am overwhelmed by the
sheer brilliance of this code. Thanks Jan-Peter and Urs and others!
Is there an option to switch off the 'trying...' messages and on on? It's
annoying when using gvim and make as it just causes one to have to quit
'more' and
On 3/16/19, Aaron Hill wrote:
> So, what I ended up doing was rewriting the LyricHyphen stencil
> procedure to use an actual hyphen glyph rather than try to draw
> something. And in the noble pursuit of generalization, the following
> approach supports *any* arbitrary markup.
Nice! I’ve tried
On Mar 16, 2019, at 6:30 AM, Aaron Hill wrote:
> This whole thing started as a way to automate setting the properties of
> LyricHyphen based on the current LyricText font. In my use case, I am
> preparing music for projection, which requires larger font sizes than typical
> for print. The
Am Sa., 16. März 2019 um 13:52 Uhr schrieb Andrew Bernard
:
> There's a convention on this list to just post Minimal Working Exmaples
> (MWE), to make it possible for people to help, rather than full scores.
> Making an MWEW instead of posting a huge chunk is a valuable exercise because
> I
el 2019-03-15 a las 09:44 Urs Liska escribió:
> Markups can't flow beyond the end of a score (horizontally) and widen
> the score if necessary:
>
> \version "2.19.82"
>
> {
>c'1 -"This is a long text that widens the score because it can't
> protrude." c'1
> }
>
> Is there a possibility
HI Yerko, and welcome.
Can I make the politest suggestion? People on the list always object when I
say how I think things should be done, but this file is illegible and
unwieldy, with very, very long lines, making it a really hard slog to help
you. A good practice is to have each bar on one line.
This whole thing started as a way to automate setting the properties of
LyricHyphen based on the current LyricText font. In my use case, I am
preparing music for projection, which requires larger font sizes than
typical for print. The default values for things like length,
thickness, and
Hello All,
I do once more apologize for my silly mistake about apparmor. As
repentance, I have looked into all the issues Federico mention and solved
the issue. In short, you have to create an apparmor profile for
lilypond-wrapper.guile (it's not very hard to do - there are utilties to
assist.)
Hi David,
I made a mistake here - total lack of comprehension on my part. Not taking
the time to study the format of the apparmor profile files, I misunderstood
that the '#" in the '#include' was a comment character that had to be
removed to activate the line. The comment character is '#' but
12 matches
Mail list logo
