slurs and ties collide

2004-08-08 Thread Werner LEMBERG
% % slur-tie.ly % % important % % [EMAIL PROTECTED] % \version "2.3.11" \header { texidoc = " Slurs and ties shouldn't collide. " } \score { \relative c' { f'4( e d a' ~| a1 ~ | a4 g f e | d1) } } % EOF == begin 644

minimumVerticalExtent.ly again

2004-08-08 Thread Werner LEMBERG
I just want to report that my bug report w.r.t. minimumVerticalExtent also affects lilypond 2.3.11. This is a really serious issue IMHO. For convenience, I'm repeating it here. Werner == % % minimumVerticalExtent.ly % %

collision of slurs and accidentals

2004-08-08 Thread Werner LEMBERG
% % slur-accidental.ly % % [EMAIL PROTECTED] % \version "2.3.11" \header { texidoc = " Slurs and accidentals shouldn't collide. The example also shows another buglet: The stem length of the third 16th note is too short. " } \score { \relative c' { g'16( f g d! g2. ~ | g1 ~ | g1 ~ | g1)

wrong slur position

2004-08-08 Thread Werner LEMBERG
% % fermata-legato.ly % % [EMAIL PROTECTED] % \version "2.3.11" \header { texidoc = " Slurs shouldn't end over the fermata. " } \score { \relative c' { a'2( f4 a | b e c a | a1\fermata) | } \paper { indent = 0.0\mm linewidth = 70.0\mm } } % EOF ==

2.3.11 SIGSEGV

2004-08-08 Thread Bertalan Fodor
When I run lilypond 2.3.11 (cygwin) except when running with -w, -v or --help (so even with no parameters), I get sigsegv. Compiler: gcc 3.3.1, Guile: 1.6.4 I will try compiling previous versions to find out where the error came in. Here is the stack trace of running 'lilypond': #0 0x6e28c1a2 in

\encoding doesn't work as expected

2004-08-08 Thread Werner LEMBERG
% % encoding.ly % % critical % % [EMAIL PROTECTED] % \version "2.3.11" \encoding "latin1" \header { texidoc = " The `\encoding' command doesn't set the proper encoding vector for data in the \header block. This contradicts the manual which states that `the encoding of the file can be set with `

set-global-staff-size breaks TeX output

2004-08-08 Thread Werner LEMBERG
% % set-global-staff-size.ly % % critical % % [EMAIL PROTECTED] % \version "2.3.11" \header { texidoc = " Calling `set-global-staff-size' breaks `lilypond --format=tex ...'. " } #(set-global-staff-size 13) \score { c'1 } % EOF ===

paper-set-staff-size et al.

2004-08-08 Thread Werner LEMBERG
[lilypond 2.3.11] Three connected bugs: . Coming from older lilypond 2 versions, I still had #(paper-set-staff-size 4) in my \paper block. While this is works fine in 2.2.5, it causes unexpected results in 2.3.11: The command has silently be redefined to just change the size of staf

\bookpaper parameters ignored

2004-08-08 Thread Werner LEMBERG
% % bookpaper.ly % % critical % % [EMAIL PROTECTED] % \version "2.3.11" \header { texidoc = " Parameters in the \bookpaper section seem to be ignored: The German `ß' (0xDF) gets a wrong glyph, neither indentation nor line length is correctly set. " } \book{ \score { c'1^"Baßtuba" } }

missing version info for lilypond-internals.info

2004-08-08 Thread Werner LEMBERG
There should be a version identifier on the top page for `lilypond-internals.info', like This is the internal reference for lilypond version 2.3.11. Werner ___ bug-lilypond mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/