Re: programming error

2004-09-11 Thread Sean Reed
Hello, (Without the express goal of intentionally searching for these things!) Here's the info concerning the message of a programming error that the terminal output is giving me when I run my .ly file. -Sean -- Sean Reed Hamburg, Germany

tuplet-single

2004-09-11 Thread Erik Sandberg
I added this to bug repository. I think it's a bug, there should be a number over the note IMHO. Object if I'm wrong. %unclear % \version 2.3.14 \header { texidoc = Single tuplets get no number above them, and no warning. They used to produce a number in v1.6 reportedin = 2.2.5 } {\times 2/3

tuplet-overwrite

2004-09-11 Thread Erik Sandberg
Added this. %important % \version 2.3.14 \header {texidoc when tupletSpannerDuration is set, tuplet numbers are printed where there are no tuplets. \reportedin = 2.3.14 } { \set tupletSpannerDuration = #(ly:make-moment 1 4) \times 2/3 {c8 c c} c c c c }

Re: Proposed workaround for apparent ghostscript (= 8.11) bug

2004-09-11 Thread Werner LEMBERG
To recapitulate the issue: When I process a file with ghostscript 8.x (8.13 or 8.14) installed, the horizontal metrics of all characters in the PDF output are messed up and the characters are squished together. The PS file from the same run, however, looks OK, whether I look at it with

Key Sig Negation

2004-09-11 Thread Will Oram
Looking at the output of various things, I see a goof in how key signatures change. One would expect a barline, a key sig negation (ie, # of naturals corresponding to sharps/flats in original sig), then a new key sig. In lily 2.3.15, the key sig negation comes first, THEN the barline, THEN