On 10/11/13 13:34, David Kastrup wrote:
James writes:
David,
On 10 November 2013 10:29, David Kastrup wrote:
James writes:
I'll make a patch.
I'm not sure how the process will work (from my own point of view anyway)
as Patchy only tests against master and we've split of 2.18, so I'll
2013/11/10 David Kastrup
> > In the Documentation all the examples of NullVoice use \lyricsto. I don't
> > know if there's a specific reason.
>
> Because \addlyrics _only_ works with Voice lyrics?
oh, I see
I'll change it to a Documentation issue, it's worth repeating it there
explicitly (NR
Federico Bruni writes:
> 2013/11/10 Pavel Roskin
>
>> Hello!
>>
>> Using \addlyrics instead of \new Lyrics makes NullVoice appear in the
>> printable output.
>>
>> Lilypond produces output with two dots for this input (screenshot
>> attached):
>>
>> \version "2.17.29"
>> soprano = { e'4. }
>> ve
2013/11/10 Pavel Roskin
> Hello!
>
> Using \addlyrics instead of \new Lyrics makes NullVoice appear in the
> printable output.
>
> Lilypond produces output with two dots for this input (screenshot
> attached):
>
> \version "2.17.29"
> soprano = { e'4. }
> verse = \lyricmode { La }
> \score {
>
While updating the translation, I spot a missing comma between the short
and the long option, in Documentation/usage/external.itely:
@item -nd --no-articulation-directions
do not convert directions (@code{^}, @code{_} or @code{-}) for
articulations, dynamics, etc.
Of course, no need to create an
