New Spanish PO file for 'lilypond' (version 2.15.41)

Hello, gentle maintainer. This is a message from the Translation Project robot. A revised PO file for textual domain 'lilypond' has been submitted by the Spanish team of translators. The file is available at: http://translationproject.org/latest/lilypond/es.po (We can arrange things so tha

Re: Regression test rater

- Original Message - From: "Phil Holmes" To: "Janek Warchol" Cc: "Devel" ; "LilyPond User Group" Sent: Monday, July 09, 2012 5:45 PM Subject: Re: Regression test rater - Original Message - From: "Janek Warchol" To: "Phil Holmes" Cc: "LilyPond User Group" ; "Devel" Se

Re: Adds support for cross-staff-stems (issue 6344092)

- Original Message - From: To: Cc: ; Sent: Monday, July 09, 2012 10:38 PM Subject: Re: Adds support for cross-staff-stems (issue 6344092) I don't think all these functions should be in ly/music-functions-init.ly, but I don't know the best place for them. Someone more familiar with t

Re: Issue 2648 in lilypond: Repeat Dots and Staff Size in 2.15.41

lilyp...@googlecode.com writes: > Updates: > Labels: -Type-Ugly Type-Critical > > Comment #2 on issue 2648 by > tdaniels...@gmail.com: Repeat Dots and > Staff Size in 2.15.41 > http://code.google.com/p/lilypond/issues/detail?id=2648 > > This bug first appeared in 2.15.40, so is a critical re

Re: Issue 2648 in lilypond: Repeat Dots and Staff Size in 2.15.41

David Kastrup wrote Tuesday, July 10, 2012 12:21 PM >> tdaniels...@gmail.com: Repeat Dots and >> Staff Size in 2.15.41 >> http://code.google.com/p/lilypond/issues/detail?id=2648 >> >> This bug first appeared in 2.15.40, so is a critical regression. > > I mean, we have too few categories for regr

Re: Issue 2648 in lilypond: Repeat Dots and Staff Size in 2.15.41

"Trevor Daniels" writes: > David Kastrup wrote Tuesday, July 10, 2012 12:21 PM > >>> tdaniels...@gmail.com: Repeat Dots and >>> Staff Size in 2.15.41 >>> http://code.google.com/p/lilypond/issues/detail?id=2648 >>> >>> This bug first appeared in 2.15.40, so is a critical regression. >> >> I mean,

Re: line_count fixes (issue 6211047)

http://codereview.appspot.com/6211047/diff/20001/lily/bar-line.cc File lily/bar-line.cc (right): http://codereview.appspot.com/6211047/diff/20001/lily/bar-line.cc#newcode151 lily/bar-line.cc:151: Real const gap_to_find = (1.0 + 3 * staffline) / staff_space; Pál, see new issue 2648 on the tracker

Re: Issue 2648 in lilypond: Repeat Dots and Staff Size in 2.15.41

David Kastrup wrote Tuesday, July 10, 2012 1:19 PM > "Trevor Daniels" writes: > >> We have the technology to identify the commits that introduce bugs >> fairly easily. Perhaps once the first release candidate is made we >> simply say any commit that introduced a critical regression bug after

Re: Issue 2648 in lilypond: Repeat Dots and Staff Size in 2.15.41

"Trevor Daniels" writes: > David Kastrup wrote Tuesday, July 10, 2012 1:19 PM > > >> "Trevor Daniels" writes: >> >>> We have the technology to identify the commits that introduce bugs >>> fairly easily. Perhaps once the first release candidate is made we >>> simply say any commit that introduc

Re: Regression test rater

Phil Holmes wrote Tuesday, July 10, 2012 12:03 PM > Kind-of fixed. The way the files are presented is aimed at ensuring no-one > rates a regtest more than once, and that they get the least-rated files > presented to them in a random order. The only way I seem to be able to get > this to work

Re: line_count fixes (issue 6211047)

hi Keith, 2012/7/10 : > > http://codereview.appspot.com/6211047/diff/20001/lily/bar-line.cc > File lily/bar-line.cc (right): > > http://codereview.appspot.com/6211047/diff/20001/lily/bar-line.cc#newcode151 > lily/bar-line.cc:151: Real const gap_to_find = (1.0 + 3 * staffline) / > staff_space; > P

Re: Issue 2648 in lilypond: Repeat Dots and Staff Size in 2.15.41

David Kastrup wrote Tuesday, July 10, 2012 4:33 PM > "Trevor Daniels" writes: > >> David Kastrup wrote Tuesday, July 10, 2012 1:19 PM >> >> >>> "Trevor Daniels" writes: >>> We have the technology to identify the commits that introduce bugs fairly easily. Perhaps once the first rel

Simultaneous headword

Could a docs person have a look at http://lsr.dsi.unimi.it/LSR/Snippet?id=825 and let me know if you think there's far too many linebreaks? Our general rule is one bar per line? -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.o

Re: Issue 2648 in lilypond: Repeat Dots and Staff Size in 2.15.41

"Trevor Daniels" writes: > David Kastrup wrote Tuesday, July 10, 2012 4:33 PM > >> "Trevor Daniels" writes: >> >>> David Kastrup wrote Tuesday, July 10, 2012 1:19 PM >>> >>> "Trevor Daniels" writes: > We have the technology to identify the commits that introduce bugs > fairl

Re: Simultaneous headword

On Tue, Jul 10, 2012 at 05:18:26PM +0100, Phil Holmes wrote: > Could a docs person have a look at > > http://lsr.dsi.unimi.it/LSR/Snippet?id=825 > > and let me know if you think there's far too many linebreaks? Our > general rule is one bar per line? Yes, and yes. If there's a special reason t

clear policy discussions (was: Issue 2648 in lilypond: Repeat Dots and Staff Size in 2.15.41)

On Tue, Jul 10, 2012 at 01:21:38PM +0200, David Kastrup wrote: > I mean, we have too few categories for regressions. I can see the > following: -snip- > My personal opinion is that My personal opinion is that we should not discuss major policy changes in the middle of a thread about dots and staf

Re: clear policy discussions

Graham Percival writes: > On Tue, Jul 10, 2012 at 01:21:38PM +0200, David Kastrup wrote: >> I mean, we have too few categories for regressions. I can see the >> following: > -snip- >> My personal opinion is that > > My personal opinion is that we should not discuss major policy > changes in the

Re: utf-8-strings

Summary: (1) The code from my initial post is not suitable, because of concerns about guilev2. (2) The code using the regexp library does not work with windows so far (perhaps never). Is there any other approach to make string->string-list work? Should I make a patch containing the new list-join-d

Re: clear policy discussions

On Tue, Jul 10, 2012 at 09:06:10PM +0200, David Kastrup wrote: > Graham Percival writes: > > > My personal opinion is that we should not discuss major policy > > changes in the middle of a thread about dots and staff sizes. > > It was in the course of changing the status to "Critical". That was

Re: utf-8-strings

Hi Harm, On Tue, Jul 10, 2012 at 3:07 PM, Thomas Morley < thomasmorle...@googlemail.com> wrote: > > (2) The code using the regexp library does not work with windows so > far (perhaps never). > Unfortunately, I'm still having no luck with Windows XP. (@David Kastrup: thank you for your suggestion

Re: 2 - Stable releases and roadmap (radical change)

Graham Percival wrote Tuesday, June 26, 2012 9:55 PM > *** Summary > > Let’s drop the “any unintended change” thing, and go totally with > the regression tests. Tests pass? We can make a stable release. > Also, let’s have an official roadmap. Rather than discussing each point separately below I

Re: clear policy discussions

Graham Percival writes: > On Tue, Jul 10, 2012 at 09:06:10PM +0200, David Kastrup wrote: >> Graham Percival writes: >> >> > My personal opinion is that we should not discuss major policy >> > changes in the middle of a thread about dots and staff sizes. >> >> It was in the course of changing t

Re: utf-8-strings

David Nalesnik writes: > Hi Harm, > > On Tue, Jul 10, 2012 at 3:07 PM, Thomas Morley > wrote: > > > (2) The code using the regexp library does not work with windows > so > far (perhaps never). > > > Unfortunately, I'm still having no luck with Windows XP. (@David > Kastrup: than

Re: clear policy discussions

On Tue, Jul 10, 2012 at 11:51:11PM +0200, David Kastrup wrote: > Graham Percival writes: I'll only address "meta-discussion" points here. > > What about the next one? Phil has been learning how to do it, and I > > certainly won't call *him* a trained monkey... but his expertise is > > documen

PATCH: Countdown to 20120712

For 21:00 MDT Thursday, July 12th (a bit late in case my cello teacher gets forceful about the Vivaldi!) Build: Issue 2634 : aclocal.m4 incorrectly remove parts of python-cflags output - R 6374046

Get texidoc translations out of snippets source files (issue 6351083)

http://codereview.appspot.com/6351083/diff/1/Documentation/contributor/lsr-work.itexi File Documentation/contributor/lsr-work.itexi (right): http://codereview.appspot.com/6351083/diff/1/Documentation/contributor/lsr-work.itexi#newcode209 Documentation/contributor/lsr-work.itexi:209: e.g. 2011-12

error while running make check (g++ 4.7.0): missing include of unistd.h

I wanted to run regression tests and compare before and after a change. However, I obtained the error given below after make -j8 CPU_COUNT=8 check I suspect this is because I am compiling with gcc/g++ 4.7.0 (coming with Fedora 17) and its release notes say: "Avoid polluting the global namespace an

Re: bug with 2.15.39 fixed with 2.15.42: good job but no reg test

> Add only the new test file, but check carefully that `make test` succeeds > with the new test included, and take care that the header is correct > and that no errors are generated, so that `make doc` will also succeed. patch proposed. I saw that the error was only in 3/4. But in the proposed tes

Add documentation for ly:one-line-breaking. (issue 6353081)

LGTM, apart from one minor change http://codereview.appspot.com/6353081/diff/1/Documentation/notation/spacing.itely File Documentation/notation/spacing.itely (right): http://codereview.appspot.com/6353081/diff/1/Documentation/notation/spacing.itely#newcode906 Documentation/notation/spacing.itel

Re: Doc: document \on-the-fly (2579) (issue 6347062)

Patch pushed 91ca3dbe2cd40f8eedce48ee02c7c98a2ec89413 http://codereview.appspot.com/6347062/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Doc: more comprehensive documentation of layout block (2560) (issue 6354085)

Patch pushed 73255e50558a62841500aa947ff7cad28636d144 http://codereview.appspot.com/6354085/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel