Re: new smaller installers to test

On Fri, Feb 12, 2010 at 4:57 PM, Graham Percival wrote: > I've tweaked the list of dirs to remove from > share/ghostscript/Resources.  The resulting files are (on average) 5 > megs smaller.  linux-x86 works here for me. It looks as if this directory contains various character encoding related stu

[PATCH] Support multi-slash and mixed-duration beat repeats

Hi everybody, I've posted a patch on Rietveld which enhances the behaviour of \repeat percent by allowing single-beat repeats to be shown with multiple slashes (if all durations are equal and duration >= semiquaver) or as double-percent glyphs (varying durations). I've moved the handling of the d

Re: Life of a Grob

On Wed, 2010-02-17 at 15:21 -0700, Carl Sorensen wrote: > Joe, > > I stumbled across your "Life of a Grob" feature while I was looking up stuff > on Figured Bass. > > > > I think this would be really good to add to either t

Re: Can't build today's git pull

> "Graham" == Graham Percival writes: Graham> On Thu, Feb 18, 2010 at 09:47:21AM +1100, Peter Chubb wrote: >> ... chmod 755 out/convert-ly >> /usr/src/lilypond/scripts/build/out/help2man out/convert-ly > >> out/convert-ly.1 out/convert-ly:341: Warning: 'as' will become a >> reserved keyword

Re: [PATCH] Change default to NOT ignore bass figures on rests

On Wed, Feb 17, 2010 at 03:51:21PM -0700, Carl Sorensen wrote: > > Changing the default is not that big a deal, I think, as long as it's > documented in NEWS. Documentation/changes.tely > But this may require changes to the documentation as well. I'm not familiar with our figured bass docs, so

Re: Can't build today's git pull

On Thu, Feb 18, 2010 at 09:47:21AM +1100, Peter Chubb wrote: > ... > chmod 755 out/convert-ly > /usr/src/lilypond/scripts/build/out/help2man out/convert-ly > out/convert-ly.1 > out/convert-ly:341: Warning: 'as' will become a reserved keyword in Python 2.6 > File "out/convert-ly", line 341 > e

Re: Can't build today's git pull

2010/2/17 John Mandereau : > Neither can I.  Sorry for top-posting but it seems this error is > unrelated to the one you reported: > > error: cannot find description for property originalMiddleCPosition > (translation) > /home/lilydev/git/lily/master/out/share/lilypond/current/scm/lily.scm > make[

Re: Can't build today's git pull

Neither can I. Sorry for top-posting but it seems this error is unrelated to the one you reported: error: cannot find description for property originalMiddleCPosition (translation) /home/lilydev/git/lily/master/out/share/lilypond/current/scm/lily.scm make[1]: *** [out/internals.texi] Error 1 Ch

Re: [PATCH] Change default to NOT ignore bass figures on rests

On 2/17/10 2:51 PM, "Reinhold Kainhofer" wrote: > Are there any objections to setting ignoreFiguredBassRests to ##f by default? > Bass figures on rests occur every now and then, and they have a well-defined > meaning: They are taken relative to the following bass note... > > I don't don't see

Can't build today's git pull

... chmod 755 out/convert-ly /usr/src/lilypond/scripts/build/out/help2man out/convert-ly > out/convert-ly.1 out/convert-ly:341: Warning: 'as' will become a reserved keyword in Python 2.6 File "out/convert-ly", line 341 except InvalidVersion as ex: ^ SyntaxError: inv

Life of a Grob

Joe, I stumbled across your "Life of a Grob" feature while I was looking up stuff on Figured Bass. I think this would be really good to add to either the CG or the Extending LilyPond manual. Can you tell me what the curren

Re: Issue 659: alternate segno symbol (issue181144)

Hi Marc, LGTM, though I still think this is a lot of effort for a very obscure and little-used symbol. Cheers, Neil http://codereview.appspot.com/181144/diff/5028/4010 File input/regression/bar-line-segno.ly (right): http://codereview.appspot.com/181144/diff/5028/4010#newcode2 input/regressio

[PATCH] Change default to NOT ignore bass figures on rests

Are there any objections to setting ignoreFiguredBassRests to ##f by default? Bass figures on rests occur every now and then, and they have a well-defined meaning: They are taken relative to the following bass note... I don't don't see any reason at all to have this option in the first place. I d

Re: Determining location of the staff lines

On 17 February 2010 16:36, Carl Sorensen wrote: > Yes, arbitrary properties can be added to the context.  Context properties > are stored as scheme alists.  So that is a potential workaround that you > could use now -- store the private data in a context property (which makes > it not private, bu

website translation build: got blah.xy.html files

We're now building the fr and es translations of the website: http://lilypond.org/~graham/website/index.es.html The next steps are: 1) es+fr translators: if you do "make website", you'll see a huge number of warnings. Mostly because you've changed the node names of Changes and Old downloads.

Re: Determining location of the staff lines

On 2/17/10 10:18 AM, "David Kastrup" wrote: > Carl Sorensen writes: > >> Yes, arbitrary properties can be added to the context. Context >> properties are stored as scheme alists. So that is a potential >> workaround that you could use now -- store the private data in a >> context property

Re: Determining location of the staff lines

Carl Sorensen writes: > Yes, arbitrary properties can be added to the context. Context > properties are stored as scheme alists. So that is a potential > workaround that you could use now -- store the private data in a > context property (which makes it not private, but nobody else is using > i

Re: Determining location of the staff lines

On 2/17/10 9:08 AM, "Eric Knapp" wrote: > On Mon, Feb 15, 2010 at 11:54 AM, Carl Sorensen wrote: >> >> >> I think it's not yet possible to do this in a Scheme engraver. >> >> Han-Wen indicated that it could be done here: >> >> http://lists.gnu.org/archive/html/lilypond-devel/2010-01/msg00

Re: Determining location of the staff lines

On Mon, Feb 15, 2010 at 11:54 AM, Carl Sorensen wrote: > > > I think it's not yet possible to do this in a Scheme engraver. > > Han-Wen indicated that it could be done here: > > http://lists.gnu.org/archive/html/lilypond-devel/2010-01/msg00594.html > > But I don't think it's been implemented yet.

Re: [frogs] Da Capos, Codas and Segnos

On 16/02/10 17:20, reinhold [via LilyPond Frogs] wrote: Am Dienstag, 16. Februar 2010 18:07:11 schrieb Ian Hulin: > Kieren MacMillan wrote: > > Hi all, > > > > I've been lurking a bit on this thread, but felt I should comment. > > > > I personally think we need a more general structure than \rep

Re: [frogs] Da Capos, Codas and Segnos

Marc Hohl writes: > David Kastrup schrieb: > >> But the point is that "repeat volta" and "coda" and whatever else in >> the music list should be just interesting for the grob engraver, and >> performer and repeat unfolder and cautionaries and stuff get their >> info from a lower-level primitive d

Re: [frogs] Da Capos, Codas and Segnos

David Kastrup schrieb: Marc Hohl writes: After reading through the other posts, I think that overloading \repeat would not cover *all* possible cases. On the other hand, there should be *one* consistent way of doing any kind of repeats. David's comparison with goto-like structures seems to