lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: \breathe in lily 2.9.14


From: Mats Bengtsson
Subject: Re: \breathe in lily 2.9.14
Date: Fri, 18 Aug 2006 15:53:01 +0200
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.13) Gecko/20060417

This bug is fixed in the latest source code, so you can look forward to
version 2.9.15.

As always, I recommend the latest stable version, 2.8.6, for any serious
work. If you want to use the development version, please send bug
reports to bug-lilypond (but first check if the bug already has been
reported, as in this case).

  /Mats

Simon Dahlbacka wrote:

Running the following file through lily 2.9.14  on winxp

% breathe.ly <http://breathe.ly>
\version "2.9.14"

\relative c' { c c \breathe c c }
% end breathe.ly <http://breathe.ly>

Produces the following output:
D:\Scores\>lilypond --png breathe.ly <http://breathe.ly>
GNU LilyPond 2.9.14
Processing `breathe.ly'
Parsing...
Interpreting music...
warning: Unknown event class breathing-sign-event[1]
Preprocessing graphical objects...
Calculating line breaks... [2]
Drawing systems...
Calculating page breaks...
Layout output to `breathe.ps'...
Converting to PNG...


and the resulting png (or pdf) does not show any signs of a breathing sign, am I missing something obvious?

/Simon

------------------------------------------------------------------------

------------------------------------------------------------------------

_______________________________________________
lilypond-user mailing list
address@hidden
http://lists.gnu.org/mailman/listinfo/lilypond-user

--
=============================================
        Mats Bengtsson
        Signal Processing
        Signals, Sensors and Systems
        Royal Institute of Technology
        SE-100 44  STOCKHOLM
        Sweden
        Phone: (+46) 8 790 8463                         
       Fax:   (+46) 8 790 7260
        Email: address@hidden
        WWW: http://www.s3.kth.se/~mabe
=============================================





reply via email to

[Prev in Thread] Current Thread [Next in Thread]