Re: [Translation] Czech xrefs towards Notation Reference

2011-11-20 Thread Francisco Vila
2011/11/20 Jean-Charles Malahieude : > Hallo Pavel! > > As a follow up to > http://lists.gnu.org/archive/html/bug-lilypond/2011-11/msg00549.html > please find enclosed a file listing all @ruser{} that should be corrected as > long as the Notation Reference has not been translated. Thank you, good

Re: Issue 2049 in lilypond: Patch: parser.yy: allow negative numbers as function arguments while keeping postevents operative

2011-11-20 Thread lilypond
Updates: Labels: -Patch-new Patch-review Comment #2 on issue 2049 by pkx1...@gmail.com: Patch: parser.yy: allow negative numbers as function arguments while keeping postevents operative http://code.google.com/p/lilypond/issues/detail?id=2049 Passes make and make check __

Issue 2049 in lilypond: Patch: parser.yy: allow negative numbers as function arguments while keeping postevents operative

2011-11-20 Thread lilypond
Status: New Owner: Labels: Type-Enhancement Patch-new New issue 2049 by d...@gnu.org: Patch: parser.yy: allow negative numbers as function arguments while keeping postevents operative http://code.google.com/p/lilypond/issues/detail?id=2049 parser.yy: allow negative numbers as function ar

[Translation] Czech xrefs towards Notation Reference

2011-11-20 Thread Jean-Charles Malahieude
Hallo Pavel! As a follow up to http://lists.gnu.org/archive/html/bug-lilypond/2011-11/msg00549.html please find enclosed a file listing all @ruser{} that should be corrected as long as the Notation Reference has not been translated. It is the result of git grep -n '@ruser' launched in Docume

Re: Issue 2000 in lilypond: Patch: Fixes NoteColumn vs SpanBar collisions.

2011-11-20 Thread lilypond
Updates: Labels: -Patch-new Patch-review Comment #32 on issue 2000 by pkx1...@gmail.com: Patch: Fixes NoteColumn vs SpanBar collisions. http://code.google.com/p/lilypond/issues/detail?id=2000 Passes make and reg tests attached Attachments: Screenshot.png 66.0 KB Scre

Re: Issue 2043 in lilypond: Patch: Lambaize $ and # in #{ ... #} to make Guile V2 happy.

2011-11-20 Thread lilypond
Comment #8 on issue 2043 by ianhuli...@gmail.com: Patch: Lambaize $ and # in #{ ... #} to make Guile V2 happy. http://code.google.com/p/lilypond/issues/detail?id=2043 Just to summarize the last comment - LGTM. Cheers, Ian ___ bug-lilypond mailing

Re: Issue 1989 in lilypond: Patch: Website: use external $LILYPOND_WEB_MEDIA_GIT

2011-11-20 Thread lilypond
Updates: Status: Verified Labels: -fixed_2_15_16 Comment #6 on issue 1989 by philehol...@gmail.com: Patch: Website: use external $LILYPOND_WEB_MEDIA_GIT http://code.google.com/p/lilypond/issues/detail?id=1989 (No comment was entered for this change.)

Re: Issue 1988 in lilypond: Patch: Rename \markuplines to \markuplist (before running convert-ly)

2011-11-20 Thread lilypond
Updates: Status: Verified Labels: -Patch-push -Fixed_2_15_17 Comment #14 on issue 1988 by philehol...@gmail.com: Patch: Rename \markuplines to \markuplist (before running convert-ly) http://code.google.com/p/lilypond/issues/detail?id=1988 (No comment was entered for this chang

Re: Issue 1987 in lilypond: Patch: Get rid of most of the insane string-tunings API

2011-11-20 Thread lilypond
Updates: Status: Verified Labels: -Fixed_staging Comment #16 on issue 1987 by philehol...@gmail.com: Patch: Get rid of most of the insane string-tunings API http://code.google.com/p/lilypond/issues/detail?id=1987 (No comment was entered for this change.)

Re: Issue 1981 in lilypond: Patch: Adds Scheme function for spring constructor.

2011-11-20 Thread lilypond
Updates: Status: Verified Comment #9 on issue 1981 by philehol...@gmail.com: Patch: Adds Scheme function for spring constructor. http://code.google.com/p/lilypond/issues/detail?id=1981 (No comment was entered for this change.) ___ bug-lily

Re: Issue 1984 in lilypond: Patch: parser.yy: make Scheme and music expressions equivalent as function arguments.

2011-11-20 Thread lilypond
Updates: Status: Verified Comment #6 on issue 1984 by philehol...@gmail.com: Patch: parser.yy: make Scheme and music expressions equivalent as function arguments. http://code.google.com/p/lilypond/issues/detail?id=1984 (No comment was entered for this change.) __

Re: Issue 1982 in lilypond: Patch: Allow more argument types, interpret optional argument predicates syntactically.

2011-11-20 Thread lilypond
Updates: Status: Verified Comment #4 on issue 1982 by philehol...@gmail.com: Patch: Allow more argument types, interpret optional argument predicates syntactically. http://code.google.com/p/lilypond/issues/detail?id=1982 (No comment was entered for this change.)

Re: Issue 1977 in lilypond: BarLine #'bar-extent wrongly documented as internal property

2011-11-20 Thread lilypond
Updates: Status: Verified Comment #8 on issue 1977 by philehol...@gmail.com: BarLine #'bar-extent wrongly documented as internal property http://code.google.com/p/lilypond/issues/detail?id=1977 (No comment was entered for this change.) ___

Re: Issue 2000 in lilypond: Patch: Fixes NoteColumn vs SpanBar collisions.

2011-11-20 Thread m...@apollinemike.com
On Nov 15, 2011, at 11:13 PM, lilyp...@googlecode.com wrote: > Updates: > Labels: -Patch-countdown Patch-push > > Comment #30 on issue 2000 by colinpkc...@gmail.com: Patch: Fixes NoteColumn > vs SpanBar collisions. > http://code.google.com/p/lilypond/issues/detail?id=2000 > > Counted down

Re: Issue 2000 in lilypond: Patch: Fixes NoteColumn vs SpanBar collisions.

2011-11-20 Thread lilypond
Updates: Labels: Patch-new Comment #31 on issue 2000 by mts...@gmail.com: Patch: Fixes NoteColumn vs SpanBar collisions. http://code.google.com/p/lilypond/issues/detail?id=2000#c31 Fixes NoteColumn vs SpanBar collisions. http://codereview.appspot.com/5323062 ___