Re: Dorico release and tutorials

[Urs Liska]

Am 19.10.2016 um 16:14 schrieb Gilles:
> Hi.
>
> On Wed, 19 Oct 2016 09:47:01 -0400, Kieren MacMillan wrote:
>> Hi Gilles,
>>
>>> Unforced breaks can depend on previous margin settings,
>>> possibly making the numbering wrong when the user reruns
>>> the compilation with different settings.
>>
>> Of course that *can* happen… but it doesn’t have to. In all my
>> scores, once the layout is fixed, I no longer *ever* let Lilypond make
>> layout choices: I turn off auto-breaking and manually force-break all
>> lines and pages, i.e., page numbers in my scores never change [after
>> that point].
>>
>>>> Why “rather”? Why not “in addition to”?
>>>
>>> Because (I guess that) the former will not likely produce
>>> the expected output, particularly when there are many pages.
>>> Unless you mean that the typesetting should only rely on
>>> forced breaks.
>>
>> No… I’m saying I don’t understand why there cannot be options — then
>> users (like me) who control breaks completely can do one thing, and
>> those who don’t can do another.
>>
>> That’s one of my favourite philosophical features about Lilypond: it
>> so often allows the user to choose, offering many parameters for
>> adjustment (with reasonable defaults).
>
> I think that we say the same thing: the feature would work
> reliably only when the user specify all page breaks.

I think that *if* a score requires differently-sized sections it's
pretty common that you'll end up with manual breaks. So t option should
be there, as an alternative.
Of course such a feature could also be useful to apply to "the current
page", so you'll write an explicit break followed by the command. That
way it would be independent from the actual page number.

>
> Best,
> Gilles
>
>>
>> Cheers,
>> Kieren.
>
>
> _______________________________________________
> lilypond-user mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/lilypond-user