Re: Issue 2408 in lilypond: Inconsistent automatic beaming when using multiple tuplets next to each other
Updates: Status: Started Owner: carl.d.s...@gmail.com Comment #1 on issue 2408 by carl.d.s...@gmail.com: Inconsistent automatic beaming when using multiple tuplets next to each other http://code.google.com/p/lilypond/issues/detail?id=2408 Have a patch just about ready to go. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Slurs between different voices
2012/3/16 Xavier Scheuer : > On 16 March 2012 17:44, Francisco Vila wrote: >> >> Thank you. I have tried the \hideNotes trick but does not work because >> a beam is only printed it the initial note is not hidden. > > The code I would have used (maybe a bit tricky). Thank you! You have been credited by this trick. http://repo.or.cz/w/lilypond-ejercicios.git/commitdiff/03ec0209539776b1b45bd758a5d09b6b6c0480ef -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2399 in lilypond: website links to 2.13 docs for 'help us' points to a non-existent page
Updates: Labels: -Fixed_2_13_34 Fixed_2_15_34 Comment #10 on issue 2399 by julien.r...@gmail.com: website links to 2.13 docs for 'help us' points to a non-existent page http://code.google.com/p/lilypond/issues/detail?id=2399 hehe thanks I hard-coded that one in my head ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2399 in lilypond: website links to 2.13 docs for 'help us' points to a non-existent page
Comment #9 on issue 2399 by ma...@gregoriana.sk: website links to 2.13 docs for 'help us' points to a non-existent page http://code.google.com/p/lilypond/issues/detail?id=2399 Typo? Fixed_2_13_34 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2230 in lilypond: add svg regtests
Comment #10 on issue 2230 by julien.r...@gmail.com: add svg regtests http://code.google.com/p/lilypond/issues/detail?id=2230 The problem I have is that one small change in coordinates leads to a full-line diff. Changes to ID could easily get lost. So I need to either filter or weight the different types of changes in the file. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1004 in lilypond: more thought needed for website integration
Comment #2 on issue 1004 by julien.r...@gmail.com: more thought needed for website integration http://code.google.com/p/lilypond/issues/detail?id=1004 Website integration is not perfect, but we no longer have hard-coded version strings in lilypond-texi2html.init after the fix to issue 2399 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2399 in lilypond: website links to 2.13 docs for 'help us' points to a non-existent page
Updates: Status: Fixed Owner: julien.r...@gmail.com Labels: Fixed_2_13_34 Comment #8 on issue 2399 by julien.r...@gmail.com: website links to 2.13 docs for 'help us' points to a non-existent page http://code.google.com/p/lilypond/issues/detail?id=2399 pushed to staging 70adadcf60fa2571d3148115af5d7e96d80d57a5 please update your trusted dir with lilypond-texi2html.init ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2399 in lilypond: website links to 2.13 docs for 'help us' points to a non-existent page
Comment #7 on issue 2399 by julien.r...@gmail.com: website links to 2.13 docs for 'help us' points to a non-existent page http://code.google.com/p/lilypond/issues/detail?id=2399 Issue 2079 has been merged into this issue. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2079 in lilypond: website links to 2.13
Updates: Status: Duplicate Mergedinto: 2399 Comment #3 on issue 2079 by julien.r...@gmail.com: website links to 2.13 http://code.google.com/p/lilypond/issues/detail?id=2079 that suggestion is issue 2212 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2399 in lilypond: website links to 2.13 docs for 'help us' points to a non-existent page
Comment #6 on issue 2399 by gra...@percival-music.ca: website links to 2.13 docs for 'help us' points to a non-existent page http://code.google.com/p/lilypond/issues/detail?id=2399 substitution is fine. Please push directly to staging. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2230 in lilypond: add svg regtests
Comment #9 on issue 2230 by m...@apollinemike.com: add svg regtests http://code.google.com/p/lilypond/issues/detail?id=2230 I vote for only textual comparison. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2399 in lilypond: website links to 2.13 docs for 'help us' points to a non-existent page
Comment #5 on issue 2399 by pkx1...@gmail.com: website links to 2.13 docs for 'help us' points to a non-existent page http://code.google.com/p/lilypond/issues/detail?id=2399 Julien, There was talk in one of the current items open to use 'dev' and 'stable' instead of explicit numbers and link the documents that way. See issue 2079 and issue 2212 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2230 in lilypond: add svg regtests
Comment #8 on issue 2230 by julien.r...@gmail.com: add svg regtests http://code.google.com/p/lilypond/issues/detail?id=2230 What exactly is needed from svg regtests? Do we want only textual comparison of the generated svg files or also png output comparison? ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2399 in lilypond: website links to 2.13 docs for 'help us' points to a non-existent page
Comment #4 on issue 2399 by julien.r...@gmail.com: website links to 2.13
docs for 'help us' points to a non-existent page
http://code.google.com/p/lilypond/issues/detail?id=2399
lilypond-texi2html.init line 1427:
# TODO: very yucky, but will be fixed in issue 1004
if ($web_manual) {
my $only_web = $ENV{ONLY_WEB};
if ($only_web) {
$href = "../../doc/v2.13/Documentation/web/".$href;
}
}
do we want just a substitution at every release or a proper fix?
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Slurs between different voices
On 16 March 2012 17:44, Francisco Vila wrote:
>
> Thank you. I have tried the \hideNotes trick but does not work because
> a beam is only printed it the initial note is not hidden.
The code I would have used (maybe a bit tricky).
Snippet
\version "2.15.30"
\new Staff {
\time 2/4
<<
\new Voice {
\relative g'' {
\voiceOne
s4 g16( f e d |
\stemDown
\once \override Flag #'style = #'no-flag
c'16-|) s16*3
}
}
\new Voice {
\relative g' {
\stemDown
s4 g4 |
c16( d bis c)
}
}
>>
}
End of snippet
Cheers,
Xavier
--
Xavier Scheuer
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Slurs between different voices
2012/3/16 Xavier Scheuer :
> On 16 March 2012 17:30, Francisco Vila wrote:
>>
>> This is not an upright slur from the lowest note, this is a 'downside' slur
>
> Right, I did not consider this case.
> Nice request, then.
>
>> See attached again. How do you do that?
>
> Right now I would use two voices. ;-P
Thank you. I have tried the \hideNotes trick but does not work because
a beam is only printed it the initial note is not hidden.
See
\version "2.15.30"
\new Staff {
<<
\new Voice
\relative f {
\voiceOne 16 % here \voiceTwo is even worse
}
\new Voice
\relative f {
\voiceTwo %\hideNotes %this removes beam!
c''16[ ^(
\unHideNotes d b c] )
}
>>
}
%END
> But with your "be able to start a slur from a specific note of a chord"
> it would be easier, of course.
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Slurs between different voices
On 16 March 2012 17:30, Francisco Vila wrote: > > This is not an upright slur from the lowest note, this is a 'downside' slur Right, I did not consider this case. Nice request, then. > See attached again. How do you do that? Right now I would use two voices. ;-P But with your "be able to start a slur from a specific note of a chord" it would be easier, of course. Cheers, Xavier -- Xavier Scheuer ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Slurs between different voices
2012/3/16 Xavier Scheuer : > For a slur to start from the lowest note > _( This is not an upright slur from the lowest note, this is a 'downside' slur > What would you expect —as graphical output— for a slur starting on > a note *in the middle of a chord*? I cannot represent how it would > look like and I cannot remember having seen such thing (in "normal > chords I mean, this is different from a polyphonic passage)? > ?? See attached again. How do you do that? -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com <>___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Slurs between different voices
On 16 March 2012 16:51, Francisco Vila wrote: > > Also, I had put my hopes in this variant: > > (snip) > > %END > > But not. Might be considered as an issue. But IMHO issue #1316 is by far more confusing for lambda users: I mean, I replied to dozens of e-mail from users on the French (but not only) user mailing list who did not understand why slurs, hairpins, spanners, lyrics do not work when going from inside a << \\ >> construct to outside of it (and vice-versa). And I think solving issue #1316 could "solve" your situation as well. http://code.google.com/p/lilypond/issues/detail?id=1316 Cheers, Xavier -- Xavier Scheuer ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Slurs between different voices
On Fri, Mar 16, 2012 at 04:47:01PM +0100, Francisco Vila wrote:
> 2012/3/16 Francisco Vila :
> > 2012/3/16 Xavier Scheuer :
> >
> >> Simply moving the "Slur_engraver" from Voice level to Staff level does
> >> what you want, IIUC.
> >
> > Thank you! That's what I needed. I'm going to try the other example.
> > If that's so easily doable, please ignore my request.
>
> Well I'd change the title to "be able to start a slur from a specific
> note of a chord". This gives a warning and does not printa a slur. For
> cases like this, maybe still the named slurs have any sense.
>
> \version "2.15.30"
> \new Staff {
> \new Voice \relative f {
> 16 d, b c )
> }
> }
>
There is some documentation here:
http://lilypond.org/doc/v2.14/Documentation/snippets/expressive-marks#creating-slurs-across-voices
Is that what you require?
Cheers,
Colin.
--
Colin Hall
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Slurs between different voices
On 16 March 2012 16:47, Francisco Vila wrote:
>
> Well I'd change the title to "be able to start a slur from a specific
> note of a chord". This gives a warning and does not printa a slur. For
> cases like this, maybe still the named slurs have any sense.
>
> \version "2.15.30"
> \new Staff {
> \new Voice \relative f {
>16 d, b c )
> }
> }
To have a slur from the highest note of the chord use
^(
For a slur to start from the lowest note
_(
What would you expect —as graphical output— for a slur starting on
a note *in the middle of a chord*? I cannot represent how it would
look like and I cannot remember having seen such thing (in "normal
chords I mean, this is different from a polyphonic passage)?
??
Cheers,
Xavier
--
Xavier Scheuer
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Slurs between different voices
2012/3/16 Francisco Vila :
> Well I'd change the title to "be able to start a slur from a specific
> note of a chord". This gives a warning and does not printa a slur. For
> cases like this, maybe still the named slurs have any sense.
>
> \version "2.15.30"
> \new Staff {
> \new Voice \relative f {
> 16 d, b c )
> }
> }
Also, I had put my hopes in this variant:
\version "2.15.30"
\new Staff {
\new Voice \relative f {
<<{c'''16 } \\ {c,16( } >>
d, b c )
}
}
\layout {
\context {
\Voice
\remove "Slur_engraver"
\remove "Slur_performer"
}
\context {
\Staff
\consists "Slur_engraver"
\consists "Slur_performer"
}
}
%END
But not.
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Slurs between different voices
2012/3/16 Francisco Vila :
> 2012/3/16 Xavier Scheuer :
>
>> Simply moving the "Slur_engraver" from Voice level to Staff level does
>> what you want, IIUC.
>
> Thank you! That's what I needed. I'm going to try the other example.
> If that's so easily doable, please ignore my request.
Well I'd change the title to "be able to start a slur from a specific
note of a chord". This gives a warning and does not printa a slur. For
cases like this, maybe still the named slurs have any sense.
\version "2.15.30"
\new Staff {
\new Voice \relative f {
16 d, b c )
}
}
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Slurs between different voices
2012/3/16 Xavier Scheuer : > Simply moving the "Slur_engraver" from Voice level to Staff level does > what you want, IIUC. Thank you! That's what I needed. I'm going to try the other example. If that's so easily doable, please ignore my request. -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Slurs between different voices
On 16 March 2012 13:51, Francisco Vila wrote:
>
> I attach two. Op25-n3 is more obvious. Its code (w/o slur) would be
> something like
>
> \version "2.15.30"
> \new Staff \relative f {
> <<
>\new Voice { \voiceOne d''16 c8. g16 f8. }
>\new Voice { \voiceTwo f8[ f'] c,[ c'] }
> >>
> }
>
>
> A comfortable syntax would be \startSlur #name ... \endSlur #name like in
>
> <<
>\new Voice { \voiceOne d''16 \startSlur #A c8. }
>\new Voice { \voiceTwo f,8[ f'] \endSlur #A }
> >>
>
> A #name would be reusable if the slur has ended in a previous column.
> Otherwise, new names everywhere would be needed.
Hi Francisco,
Simply moving the "Slur_engraver" from Voice level to Staff level does
what you want, IIUC.
Snippet
\version "2.15.33"
\score {
\new Staff {
\time 2/4
<<
\new Voice {
\relative c'' {
\voiceOne
d16( c8. a16( g8.
}
}
\new Voice {
\relative c'' {
\voiceTwo
g8 g') c,,8 c'8)
}
}
>>
}
\layout {
\context {
\Voice
\remove "Slur_engraver"
\remove "Slur_performer"
}
\context {
\Staff
\consists "Slur_engraver"
\consists "Slur_performer"
}
}
}
End of snippet
Cheers,
Xavier
--
Xavier Scheuer
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Slurs between different voices
2012/3/16 Colin Hall :
>
> On Fri, Mar 16, 2012 at 11:06:50AM +0100, Francisco Vila wrote:
>> Hello,
>> I am typesetting some Chopin music. Music from this period uses slurs
>> between different voices all the time. I'd like to file an enhancement
>> request for this, if possible. Thanks.
>
> Thanks for the suggestion. I think it is pretty clear what you are
> requesting, and I agree that it is not supported now.
>
> http://lilypond.org/doc/v2.15/Documentation/notation/expressive-marks-as-curves#slurs
>
> To complete your feature request could you supply some suggestions for
> suitable input syntax? A sample of lilypond source for some Chopin that is
> complete except for the cross-voice slurs might be a good place to start.
>
> Also, so that this request can stand alone, could you send an image showing
> an example of slurs between different voices?
I attach two. Op25-n3 is more obvious. Its code (w/o slur) would be
something like
\version "2.15.30"
\new Staff \relative f {
<<
\new Voice { \voiceOne d''16 c8. g16 f8. }
\new Voice { \voiceTwo f8[ f'] c,[ c'] }
>>
}
A comfortable syntax would be \startSlur #name ... \endSlur #name like in
<<
\new Voice { \voiceOne d''16 \startSlur #A c8. }
\new Voice { \voiceTwo f,8[ f'] \endSlur #A }
>>
A #name would be reusable if the slur has ended in a previous column.
Otherwise, new names everywhere would be needed.
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com
<><>___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Slurs between different voices
On Fri, Mar 16, 2012 at 11:06:50AM +0100, Francisco Vila wrote: > Hello, > I am typesetting some Chopin music. Music from this period uses slurs > between different voices all the time. I'd like to file an enhancement > request for this, if possible. Thanks. Thanks for the suggestion. I think it is pretty clear what you are requesting, and I agree that it is not supported now. http://lilypond.org/doc/v2.15/Documentation/notation/expressive-marks-as-curves#slurs To complete your feature request could you supply some suggestions for suitable input syntax? A sample of lilypond source for some Chopin that is complete except for the cross-voice slurs might be a good place to start. Also, so that this request can stand alone, could you send an image showing an example of slurs between different voices? Cheers, Colin. -- Colin Hall ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Slurs between different voices
Hello, I am typesetting some Chopin music. Music from this period uses slurs between different voices all the time. I'd like to file an enhancement request for this, if possible. Thanks. -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2399 in lilypond: website links to 2.13 docs for 'help us' points to a non-existent page
Updates: Labels: -Type-Documentation Type-Critical Comment #3 on issue 2399 by gra...@percival-music.ca: website links to 2.13 docs for 'help us' points to a non-existent page http://code.google.com/p/lilypond/issues/detail?id=2399 I match your bet, and raise the stakes by pointing out the GOP policy: http://lilypond.org/doc/v2.15/Documentation/contributor/gop_002dprop-8-_002d-issue-priorities Regardless of the obsolete docs under Issues, GOP 8 lists three justifications for Critical issues. IMO this falls under the third. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2399 in lilypond: website links to 2.13 docs for 'help us' points to a non-existent page
Comment #2 on issue 2399 by d...@gnu.org: website links to 2.13 docs for 'help us' points to a non-existent page http://code.google.com/p/lilypond/issues/detail?id=2399 Critical is 'release blocking' (documentation which is what this is) not release-blocking. Star wars fans will rejoice that we have tracker issues written in Yodic. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2400 in lilypond: Dots no longer aligned between voices
Comment #6 on issue 2400 by d...@gnu.org: Dots no longer aligned between voices http://code.google.com/p/lilypond/issues/detail?id=2400 lilyp...@googlecode.com writes: Comment #3 on issue 2400 by k-ohara5...@oco.net: Dots no longer aligned between voices http://code.google.com/p/lilypond/issues/detail?id=2400 My difficulty with adding the example as a regression test, is that I can't say of the two images is the 'correct' one. "correct" only matters where the compilation fails. Others than that, the regtests are for visual comparisons. I could add a test with this music set both ways, with the description being: "The Dot Column can be engraved in either Voice or Staff. The two settings differ in readability and aesthetics, but both should be decipherable." I think it is important to have the default for comparison between versions. The effect of specific tweaks might be nice to look at as additional info, but the important part of the visual comparison is that of the default settings. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Key_signature_engraver unknown
Hello, On 13 March 2012 22:39, Trevor Daniels wrote: > > Eluze, you wrote Tuesday, March 13, 2012 10:22 PM > > >> why is the Time_signature_engraver not called Time_engraver - or what >> rules >> are used in constructing names? > > > I don't know. These names were first devised almost 10 years ago, > well before I discovered LilyPond. But one possibility is because one > often uses "key" and "key signature" interchangeably when talking > loosely, but one never hears "time" as an alternative to "time signature". > > >> I'm not sure about making this an issue… > > > James likes to have issues raised for doc changes, I do only because I can (and do) miss the email requests for doc enhancements - my inbox is full enough as it is trying to keep up with potential snippets and/or general doc improvements. Tracker numbers are cheap. I also tend to batch-fix all the small requests in one 'sitting' this is a much more efficient use of my time. Anyway, this is now pushed to staging. Should be in 2.15.34 http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commit;h=c69a9437979b012b766f94ef4ec45f9c2eac645d -- -- James ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2399 in lilypond: website links to 2.13 docs for 'help us' points to a non-existent page
Updates: Summary: website links to 2.13 docs for 'help us' points to a non-existent page Labels: -Type-Critical Type-Documentation Comment #1 on issue 2399 by pkx1...@gmail.com: website links to 2.13 docs for 'help us' points to a non-existent page http://code.google.com/p/lilypond/issues/detail?id=2399 Critical is 'release blocking' (documentation which is what this is) not release-blocking. See http://lilypond.org/doc/v2.15/Documentation/contributor/issue-classification We have pretty well defined labels ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2388 in lilypond: Doc: using \voiceXXX for direction and placement
Updates: Status: Fixed Labels: -Patch-push Fixed_2_15_34 Comment #11 on issue 2388 by pkx1...@gmail.com: Doc: using \voiceXXX for direction and placement http://code.google.com/p/lilypond/issues/detail?id=2388 committer James Lowe Fri, 16 Mar 2012 07:22:07 + (07:22 +) commit b63f205feabebfd5ed39fdaa57308c4b08eb70b3 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 2410 in lilypond: Doc: Translation NR 5.1.4 - Typo for engraver in Fr/Ja/Es and De docs
Status: Accepted Owner: Labels: Type-Documentation New issue 2410 by pkx1...@gmail.com: Doc: Translation NR 5.1.4 - Typo for engraver in Fr/Ja/Es and De docs http://code.google.com/p/lilypond/issues/detail?id=2410 http://lilypond.org/doc/v2.14/Documentation/notation/modifying-context-plug_002dins First Paragraph. 'Key_signature_engraver' does not exist. Should be 'Key_engraver' Apparent in French/Japanese/Spanish and German changing-defaults.itely Fixed in English - was issue 2394 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2394 in lilypond: use of Key_signature_engraver in 2.15.33 is incorrect should be key_engraver
Updates: Summary: use of Key_signature_engraver in 2.15.33 is incorrect should be key_engraver Status: Fixed Owner: pkx1...@gmail.com Labels: fixed_2_15_34 Comment #1 on issue 2394 by pkx1...@gmail.com: use of Key_signature_engraver in 2.15.33 is incorrect should be key_engraver http://code.google.com/p/lilypond/issues/detail?id=2394 committer James Lowe Fri, 16 Mar 2012 06:56:14 + (06:56 +) commit c69a9437979b012b766f94ef4ec45f9c2eac645d ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
