Re: Chordmode breaks in 2.10 and 2.11

2007-02-15 Thread Brett Duncan
Graham Percival wrote: Brett Duncan wrote: A little more experimenting reveals a few more things - if I specify PNG for the output instead of the default PDF, there are no errors and the PNG image is fine. That makes sense; it's ghostscript that's broken. If I specify Postscript for the outp

Re: Chordmode breaks in 2.10 and 2.11

2007-02-15 Thread Graham Percival
Brett Duncan wrote: A little more experimenting reveals a few more things - if I specify PNG for the output instead of the default PDF, there are no errors and the PNG image is fine. That makes sense; it's ghostscript that's broken. If I specify Postscript for the output, the resulting PS fil

Re: convert-ly broken on Mac OS X in 2.10 and 2.11

2007-02-15 Thread Chris Sawer
Graham Percival wrote: Chris Sawer wrote: I get an error when attempting to run convert-ly from the latest LilyPond 2.10 and 2.11 builds. This is on Mac OS X version 10.4.8 on Intel. It appears to have been broken between 2.1[01].13 and 2.1[01].14. It works ok with 2.11.17 on 10.4.8 here. I

Re: Convert-ly doesn't convert some ancient-font stuff

2007-02-15 Thread Han-Wen Nienhuys
Graham Percival escreveu: > Laura Conrad wrote: >> >> This is two bugs, but the file is pretty simple. If you really >> want >> >> two different files, I'll split it. >> >> Graham> Are those exhaustive lists of things that convert-ly >> should do? >> >> It's an exhaustive list of what

Re: Convert-ly doesn't convert some ancient-font stuff

2007-02-15 Thread Han-Wen Nienhuys
Graham Percival escreveu: > Laura Conrad wrote: >> This is two bugs, but the file is pretty simple. If you really want >> two different files, I'll split it. > > Are those exhaustive lists of things that convert-ly should do? And do > you know when exactly the changes occured? If you can tell m

Re: Weird beam-slope

2007-02-15 Thread Han-Wen Nienhuys
Rune Zedeler escreveu: >> (not topposting) > > If beams are force-stretched to the middle staff-line I think they > should be horizontal. In all cases current behaviour, where the 2nd beam > starts below the 1st beam even though the pitches are higher, must be > wrong. > > \version "2.11.18" > {

programming error with triplets and \change Staff

2007-02-15 Thread René Brandenburger
Hi, when i process the following snippet, i get a programming error --- 8< --- snip --- >8 --- \version "2.11.17" \layout { ragged-right = ##t} \include "italiano.ly" \context PianoStaff << \new Staff = "up" \relative do'{ \time 3/8 \key mib \major \clef violin

Issue 299 in project lilypond

2007-02-15 Thread codesite-noreply
Issue 299: extender sticking out to the right http://code.google.com/p/lilypond/issues/detail?id=299 Comment #1 by gpermus: Lyric syllables aren't a bug -- see 5.7 and 7.3 However, the extender line shouldn't extend beyond the staff. \score{ { \relative c' { \override Score.PaperColumn #'keep

Issue 299 in project lilypond

2007-02-15 Thread codesite-noreply
Issue 299: lyrics sticking out to the right http://code.google.com/p/lilypond/issues/detail?id=299 New issue report by lemzwerg: \version "2.11.18" \header { texidoc = " Neither lyrics syllables nor lyrics extender lines and hyphens must stick out to the right. Below you can find a counterexamp