[prev in list] [next in list] [prev in thread] [next in thread] 

List:       lilypond-user
Subject:    Re: Percent repeat problems
From:       Antonio PALAMA' <palama () inwind ! it>
Date:       2002-06-26 18:30:43
Message-ID: 3D1A0853.6050306 () inwind ! it
[Download RAW message or body]

Simon Bailey wrote:

>
>try setting 
>
>\property Score.skipBars = ##t 
>
>in your score. that influences multmeasure rests -- i don't know if it
>will compress percent-repeats but it's worth a try.
>
>for sequential numbers, i think you will have to hard code them - i
>don't know if lilypond supports them or not.
>
>greetings,
>simon.
>
>On Mon, 2002-06-24 at 22:05, Antonio PALAMA' wrote:
>
>>I would like to reduce the default width of the "percent repeat" bars.
>>I tried to figure out which is the Property that controls this parameter
>>but did not find it.
>>
>>I also miss a feature which was available with 1.2.17 but has disappeared
>>with 1.4.X i.e. to have multiple percent repeat bars to be printed as
>>a single bar with a number over it. Will this be restored someday?
>>
>>Another feature which I deem useful is having "percent repeat"
>>bars or multiple bar rests printed in full but with sequential numbers
>>over the bars.
>>
Unfortunately this does not work. What Score.skipBars = ##t does is to force
lilypond to compress multiple bar rests into a single one with a number
over the bar indicating how many bars does the rest last.
In 1.2.17, percent repeats did behave the same way as multimeasure rests and
so did Score.skipBars.

\property  Score.skipBars=1
\repetitions 1*6

produced a percent sign with the number 6 over it.

This does not work any more with 1.4.X.

I hope this will be addressed before or later, I see no reason for which
the two constructs can not coexist.

The problem of reducing the default width of percent repeat measures has
nothing to do with score.skipBars. There must be some other variable
controlling the minimum white space glued on the right and left
of the percent symbol.

Thank you very much for your help anyway,


Ciao,

Antonio Palama'




[prev in list] [next in list] [prev in thread] [next in thread]