Re: recent modifications to \partcombine

[David Kastrup]

Gilberto Agostinho <address@hidden> writes:

> I see on the documentation that the command \partcombineApartOnce
> isn't listed any more, and that is has been substituted \once
> \partcombineApart.  As much as I think this new command is much more
> logical, wouldn't it be reasonable to still allow the ...Once commands
> in order to maximize backwards compatibility?

<URL:http://www.lilypond.org/doc/v2.18/Documentation/usage/updating-files-with-convert_002dly>

> And by the way, the modification to the documentation is a bit confusing.
> Here is the passage from this page here
> http://lilypond.org/doc/v2.19/Documentation/notation/multiple-voices
>
>> Commands ending in …Once apply only to the next note in the music
>> expression.
>> 
>>     \partcombineApart and \once \partcombineApart keep the notes as two
>> separate voices, even if they can be combined into a chord or unison.
>>     \partcombineChords and \once \partcombineChords combine the notes into
>> a chord.
>>     \partcombineUnisono and \once \partcombineUnisono combine both voices
>> as “unison”.
>>     \partcombineSoloI and \once \partcombineSoloI print only voice one,
>> and mark it as a “Solo”.
>>     \partcombineSoloII or \once \partcombineSoloII print only voice two
>> and mark it as a “Solo”.
>>     \partcombineAutomatic and \once \partcombineAutomatic end the
>> functions of the commands above, and revert back to the standard
>> \partcombine functionality. 
>
> Note how the first phrase still mentions ...Once, but then the new \once
> commands are explained.

That's indeed a documentation bug.  Part of the documentation has been
converted with convert-ly already and that makes it easy to overlook the
accompanying text.  I'll take a look.

-- 
David Kastrup