Re: Overlapping articulation

Kamal wrote: The following outputs an "e" with a fermata under it & an "mf" articulation which is touching the fermata in lilypond 2.8.0 while they are output as 2 articulations seperated from each other in 2.6.5. e4_\fermata\mf 1- Why did this change in 2.8.0? Don't know. Maybe some def

serious: chords and ties

% important % [EMAIL PROTECTED] \version "2.9.0" \header { texidoc = " The current tie algorithm doesn't take into account the possibility that only some notes in a chord are tied with other chords. " } \paper { indent = 0\mm line-width = 100\mm } \relative c'' { 1 ~ | ~ | | } ___

Re: Latex-book

How did you install it and on what platform? Do you by chance use Python 2.3 or older? If so, try to upgrade to Python 2.4. /Mats Quoting Stephen Carter <[EMAIL PROTECTED]>: I just installed 2.80. Very impressed with the improvements, but now I get the following when I try to run lilypond-

Latex-book

I just installed 2.80. Very impressed with the improvements, but now I get the following when I try to run lilypond-book: Traceback (most recent call last): File "/usr/local/lilypond/usr/bin/lilypond-book", line 1762, in ? main () File "/usr/local/lilypond/usr/bin/lilypond-book", line 171

lilypond-book output hangs ps2pdf

ps2pdf seems to be hanging on the postscript output from lilypond-book. The directory in which this is happening is . The offending postscript file is allparts.ps, which is produced by saying "make allparts.ps" from allparts.lytex and a bun

Re: Small caps not working

Thanks for that, Geoff. It might be a good idea to (a) note in the documentation that this requires a suitable font (and that the default fonts might not work?); (b) use a working example for the graphic in the regression test. That said, I'm not sure the problem is with the font in my case. I'm

Re: \relative issue

On Tuesday 21 March 2006 13.54, Han-Wen Nienhuys wrote: > Werner LEMBERG wrote: > >> In light of this suprising you and the idea that relative means > >> relative to something I might suggest that there be no default and > >> that not specifying a starting point be an error. > > > > Yep. > > This i

Re: Small caps not working

> Could you clarify for me what is happening with small caps, please? Small caps might not work if the font you're using doesn't come in a small-caps version--it doesn't work for me in WinXP, for example. There's some code in the manual, at the end of 11.2.3, that fakes it. Geoff __

Re: set tupletSpannerDuration causes segfault on Linux GUB 2.8.0

That's a severe bug. However, I assume that what you really wanted was \set tupletSpannerDuration = #(ly:make-moment 1 4) \times 2/3 {c'8 c' c'} or \set tupletSpannerDuration = #(ly:make-moment 2 4) \times 2/3 {c' c' c'} Both of these work correctly. /Mats Quoting Tuukka Verho <[EMAIL

\set tupletSpannerDuration causes segfault on Linux GUB 2.8.0

The following code causes a segmentation fault: \version "2.8.0" { \set tupletSpannerDuration = #(ly:make-moment 1 4) \times 2/3 {c' c' c'} } The compiler output: GNU LilyPond 2.8.0 Processing `testi.ly' Parsing... Interpreting music... [1] Preprocessing graphical objects

Re: Latexism inthe Glossary

should be something like a D superposed with | \markup{ D\translate #(cons -2 0) {"|"} } I think Aurèle Graham Percival wrote: > > On 26-Mar-06, at 1:04 AM, Cameron Horsburgh wrote: > >> In the Music Glossary '1.108 functional harmony' a piece of old latex >> code has crept into the example. >>