Re: Request: lilypond fragment option "notime"

2005-05-01 Thread Han-Wen Nienhuys
Op vr, 29-04-2005 te 20:57 -0700, schreef Graham Percival: > Could "notime" also do > \set Score.timing = ##f > ? > > Currently it just suppresses the time signature, but in most cases > (in the manual) we want to suppress the time signature and set > Score.timing to be false. > done. -- Han-W

Re: Strange programming error

2005-05-01 Thread Herman Grootaers
On Wednesday 27 April 2005 15:53, David Bobroff wrote: > In recent CVS I'm getting this: > > GNU LilyPond 2.5.21 > Processing `/home/david/dean/ode/test.ly' > Parsing... > Interpreting music... [3] > Preprocessing graphical objects... > Calculating line breaks... > programming error: Stem has no ex

remove-first

2005-05-01 Thread Graham Percival
I've just changed the default value of RemoveEmptyVerticalGroup's remove-first to set it to #f. The docs suggest that this is so, and it makes more sense to me that way. (I've also fixed the docs to reflect the fact that you need to set this to #t to remove stuff.) Just warning you about this

Request: lilypond fragment option "notime"

2005-05-01 Thread Graham Percival
Could "notime" also do \set Score.timing = ##f ? Currently it just suppresses the time signature, but in most cases (in the manual) we want to suppress the time signature and set Score.timing to be false. Cheers, - Graham ___ lilypond-devel mailing list

encoding again

2005-05-01 Thread Graham Percival
I'm building 2.5.20 on fink, and I noticed this: --- Writing fonts to music-glossary.fonts.ps LANG= makeinfo --enable-encoding -I ./out --output=out/music-glossary.info out/music-glossary.texi out/music-glossary.texi:7: warning: unrecognized encoding name `utf-8'. mspark:~ gperciva$ makeinf

Re: New manual chapter: Putting it all together

2005-05-01 Thread Erik Sandberg
Another good thing, could be to just let a relatively experienced lily user typeset a piece in practise, and write a pretty detailed document (or log) about how he/she does this. This could be useful as a suggestion of how the entire typesetting procedure can look like. It could also be a way of

Re: Slur combined with acciaccatura shows incorrect slur

2005-05-01 Thread Erik Sandberg
On Sunday 01 May 2005 16.04, Ruud van Silfhout wrote: > Hi guys, > > When converting a piece of music for Mutopia I ran into the follwoing > problem. > I got the warning: "No slur to end" from the following piece of music. > <<{g4( \acciaccatura a16 g8 f g a)}\\{e2.}>> > The slur connects to the a1

Slur combined with acciaccatura shows incorrect slur

2005-05-01 Thread Ruud van Silfhout
Hi guys, When converting a piece of music for Mutopia I ran into the follwoing problem. I got the warning: "No slur to end" from the following piece of music. <<{g4( \acciaccatura a16 g8 f g a)}\\{e2.}>> The slur connects to the a16 instead of the last a. platform: XP machine with cygwin running L

convert-ly patch

2005-05-01 Thread Tom Cato Amundsen
Below is a small patch for convert-ly. I must say I'm impressed with the latest devel releases. Unicode lyrics are great! What kind of problems/missing features can I expect when compiling --without-ghostscript since I only have the old package from debian? 2257c2257 < str = re.sub (r'page