This is out/lilypond-web.info, produced by makeinfo version 4.11 from
out/web.texi.

Copyright (C) 2009 by the authors.

     Permission is granted to copy, distribute and/or modify this
     document under the terms of the GNU Free Documentation License,
     Version 1.1 or any later version published by the Free Software
     Foundation; with no Invariant Sections.  A copy of the license is
     included in the section entitled "GNU Free Documentation License".


File: lilypond-web.info,  Node: Top,  Next: Introduction,  Up: (dir)

LilyPond... music notation for everyone
***************************************

LilyPond
========

... music notation for everyone

What is LilyPond?
-----------------

LilyPond is an open-source music engraving program, devoted to
producing the highest-quality sheet music possible.  This free software
brings the aesthetics of traditionally engraved music to computer
printouts.

   Read more in our *note Introduction::!

New Website!  _October 3, 2009_
...............................

As you can see, we have a new website design.  Many thanks to texi2html
and CSS for being so flexible!

LilyPond Report #16.  _September 6, 2009_
.........................................

The LilyPond Report is back! This short, informal opinion column is
about the LilyPond project: its team, its world, its community.  Read
issue 16 (http://news.lilynet.net/The-LilyPond-Report-16) now!

   (*note Old news::)

Quick links
-----------

Stable
......

*note Download 2.12.2: Download.

   *note Manuals 2.12.2: Manuals.

Unstable
........

*note Download 2.13.9: Development.

   *note Manuals 2.13.9: Development.

* Menu:

* Introduction::     Start here to creating sheet music.
* Download::         Get LilyPond.
* Manuals::          Read The Fine Manuals (RTFM).
* Community::        Contact other users.


File: lilypond-web.info,  Node: Introduction,  Next: Download,  Prev: Top,  Up: Top

Introduction
************

Our Goal
--------

The inspiration for LilyPond came when two musicians became annoyed
with the bland and boring look of computer-printed sheet music.  All
musicians prefer reading beautiful music, so why couldn't programmers
write software to produce better printed parts?

   This software just does that: it prints music in the best traditions
of classical engraving with minimum fuss.  Don't waste time on tuning
spacing, moving around symbols, or shaping slurs.  Impress friends and
colleagues with sharp sheet music!

Why use LilyPond?
-----------------

   * *note Features::: What can LilyPond do?

   * *note Examples::: I want to see some music!

   * *note Freedom::: LilyPond is Free Software.

   * *note Background::: Our computational aesthetics.


Who uses it?
------------

   * *note Productions::: Real-life use of LilyPond.

   * *note Testimonials::: What do people say?


Why not use LilyPond?
---------------------

   * *note Text input::: You write music as _text_?!

   * *note Alternate input::: Other ways of working with LilyPond.


* Menu:

* Features::                    What can LilyPond do?
* Examples::                    I want to see some music!
* Freedom::                     Freedom and the GPL.
* Background::                  Computational aesthetics.
* Productions::                 Real-life use of LilyPond.
* Testimonials::                What do people say about it?
* Text input::                  You write music as text?!
* Alternate input::             Other ways of working with LilyPond.


File: lilypond-web.info,  Node: Features,  Next: Examples,  Up: Introduction

Features
========

Maybe draw inspiration from `http://lilypond.org/web/about/features' and
`http://lilypond.org/web/switch/tour' and
`http://lilypond.org/web/switch/advantages'

Why switch to LilyPond?
-----------------------

Excellent classical engraving
.............................

The point of using LilyPond is to produce elegant sheet music that is
easy to read.  LilyPond's developer community has spent thousands of
hours developing powerful music engraving software that results in
beautifully engraved music.  All of LilyPond's style settings, font
designs and algorithms have been inspired by the finest hand-engraved
music.  LilyPond output has the same strong, balanced and elegant look
as the best-engraved classical scores.  This is further explained in
our *note Essay::.

Less fiddling
.............

Spend less time with tweaking the output; LilyPond gets the formatting
correct right from the start.  It determines spacing by itself, and
breaks lines and pages to provide a tight and uniform layout.  Clashes
between lyrics, notes, and chords are resolved and slurs and beams are
sloped, automatically!

Text-based input
................

LilyPond takes ASCII input, which you can produce in your favorite text
editor, quickly and comfortably.  No more futzing with the mouse.  The
input contains all the information, so there is no need to remember
complex command sequences.  Simply save an input for later reference.

Accessibility
.............

Text-based input also makes score-writing possible for users with
severe physical disabilities.  Dexterity-impaired users who are unable
to type or control a computer mouse can use speech-recognition software
to edit LilyPond files.  Even users who are totally blind can use
screen-reading software to write LilyPond files - an impossible task in
graphical-based score-writing programs.

Mix music and text
..................

Put fragments of music into texts without cutting and pasting pictures.
Integrate music into LaTeX or HTML seamlessly, or add music to
OpenOffice.org with ooolilypond.

Free software
.............

LilyPond can be downloaded free of charge! Yep - It's free.  Get it
from the download page.

   It's also free (as in "speech") software. It comes with source code,
and permission to change and copy it. So, are you irritated by a bug,
or yearning for a feature? Simply add it yourself, or pay someone else
to do it.

Extensible design
.................

All settings can be changed to suit your personal typographical taste.
If that still is not enough, there is always the built-in scripting
language, a dialect of the powerful language LISP. Settings, variables
and functions are all documented in the comprehensive program reference
manual.

Excellent support
.................

LilyPond runs on all popular platforms: Linux, MacOS X, and Windows.
LilyPond comes with extensive documentation and hundreds of example
files.  There is an active user community answering questions on the
Lilypond user mailing list, while the development team makes sure that
problems are solved quickly.

Where now?
----------

Still not convinced?  Look at some neat *note Examples::.  If you've
already decided to try LilyPond, first read about our *note Text
input::.


File: lilypond-web.info,  Node: Examples,  Next: Freedom,  Prev: Features,  Up: Introduction

Examples
========

Lilypond is a powerful and flexible tool for engraving tasks of all
kinds. Please browse our gallery of examples and be inspired!

Classical Music
...............

This organ work by J.S. Bach is a fairly typical engraving project in
Lilypond.

Complex Notation
................

This example from _Goyescas_ by Enrique Granados shows some of the more
advanced features of typesetting, including kneed beams, cross-staff
stems, and voice-follow lines.

Early Music
...........

Lilypond also supports various types of ancient notation, such as this
passage of Gregorian chant.

Modern Music
............

Contemporary composers find Lilypond well-suited to displaying unusual
notation. Here is an excerpt from Trevor Baca's _Cáry_, for
unaccompanied bass flute.

Efficient, flexible creation of performance materials
.....................................................

Various performance materials can be created from the same source code.
This is an excerpt of Nicolas Sceaux's (http://nicolas.sceaux.free.fr/)
engraving of Handel's _Giulio Cesare_, in full score, piano-vocal
reduction, and a violin part.

Tablature
.........

Lilypond supports tablature notation, which can be customized to suit
any instrument that reads from tablature.  The tablature staff is
generated automatically from notes entered for the 5-line staff.

Schenker Graphs
...............

Standard output can be modified heavily. Here someone has created an
impressive Schenkerian analysis.

Vocal Music
...........

Lilypond is excellent for vocal music of all kinds, from sacred hymns
to opera. Here is a medieval motet with slightly unusual requirements.
The tenor voice is written in a different meter than the others, but
must line up as if it were in the same meter.  Lilypond handles this
most elegantly. Note also the incipits with Vaticana style clefs, the
slashed stems indicating plicated notes, and the ligature braces above
certain groups of notes.

Educational Applications
........................

Lilypond is perfectly suited for educational purposes as well.  Here is
an example of a simple counterpoint exercise.

Popular Music
.............

It is simple to create pop lead sheets with melody, lyrics, chord
names, and fretboards. In this example you see some of the predefined
fretboard diagrams, but these can be heavily customized to suit nearly
any situation.

Large Projects
..............

Lilypond is excellent for large projects like operas or works for full
symphony orchestra, as well.  In addition, the text-based input
provides greater accessibility - this example was contributed by Hu
Haipeng, a blind composer.

Where now?
----------

Still not convinced?  LilyPond is Free software, granting you *note
Freedom::.  If you've already decided to try LilyPond, first read about
our *note Text input::.


File: lilypond-web.info,  Node: Freedom,  Next: Background,  Prev: Examples,  Up: Introduction

Freedom
=======

Free Software
-------------

GNU (http://www.gnu.org/) LilyPond is written and maintained by a
community of enthusiasts.  It is published under the *note GNU General
Public License: GPL. and the *note GNU Free Documentation License: FDL,
giving everybody the freedom to fix, modify, and extend the program.
Creating beautiful music should not require hundreds of dollars of
software!

What are the benefits to users?
-------------------------------

   * No cost: download and try it out!  What do you have to lose?

   * Sharing: if you like the program, give a copy to your friends,
     teachers, students, and colleagues!

   * Source available: if you are curious about how LilyPond creates
     some notation, you can see exactly how it is done.

   * Extendible: you can add features, fix bugs, and change the
     functionality.  If you are not a programmer, you can hire somebody
     to do those tasks.

     This may not seem appealing to casual musicians, but the ability
     to extend software can be highly valuable to serious composers,
     companies, and academics.

   * Future safety: if a commercial company goes bankrupt, what happens
     to any electronic music which depends on their products?  This is
     not a concern with LilyPond; even if the entire development team
     quits (extremely unlikely), the program will still be legally
     available for copying, modifications, and distribution.


Why do LilyPond developers "give away" their work for free?
-----------------------------------------------------------

Most of us view LilyPond development as a hobby or volunteer work.  So
this question is really asking "why do people volunteer"?

   * Fun: working towards a goal can be enjoyable, especially when you
     work as a team!

   * Shared goals: we all want beautiful sheet music, but few people
     have the expertise (and nobody has the time!), to create a program
     which can handle all situations.  By working together - one person
     improves the automatic beaming code, another person improves the
     shape of slurs, and a third person writes documentation explaining
     how to use these features - we can achieve our goal with only a
     fraction of the individual effort.

   * "Gift culture": the Free Software (or "Open Source") movement has
     created many great software projects, such as GNU/Linux
     (http://kernel.org/), Mozilla Firefox
     (http://www.getfirefox.com/), and Battle for Wesnoth
     (http://www.wesnoth.org/).  Having benefitted from these projects,
     some developers want to "give back" to the community.

   * Work experience: contributing to open-source projects is a great
     way to practice programming, documentation writing, or design.
     This experience has helped some developers gain job offers or
     scholarships.


Where now?
----------

Still not convinced?  Read our extensive essay about our engraving
philosophy in *note Background::.  If you've already decided to try
LilyPond, first read about our *note Text input::.


File: lilypond-web.info,  Node: Background,  Next: Productions,  Prev: Freedom,  Up: Introduction

Background
==========

Background essay
----------------

We have an extensive essay describing computational aesthetics: the art
of creating beauty with a computer.

   If you just want a quick introduction to LilyPond, the essay might
be too much material to read.  If you would like to read it now, please
progress to *note Essay::.

Where now?
----------

Still not convinced?  Read about some of our users' *note Productions::
and sheet music.  If you've already decided to try LilyPond, first read
about our *note Text input::.


File: lilypond-web.info,  Node: Productions,  Next: Testimonials,  Prev: Background,  Up: Introduction

Productions
===========

Concerts
--------

Lilypond engravings have been used for performances around the world.
Some highlights:

   * _Affaire Étrangère_, an opera by Valentin Villenave, with
     libretto by Lewis Trondheim, premiered February 1, 2009, by
     L'Opéra Montpellier (http://www.orchestre-montpellier.com/).

   * Mercury Baroque (http://www.mercurybaroque.org/02/02109.aspx)'s
     performance of Lully's _Armide_, May 15-16, 2009, in Houston,
     Texas (engraving by Nicolas Sceaux
     (http://nicolas.sceaux.free.fr/)).

   * Instrumental excerpts from Rameau's _Hippolyte et Aricie_ at St.
     James's Church in Manhattan, May 8, 2009, by Frederick Renz and
     his ensemble Early Music New York (http://www.earlymusicny.org/)
     (engraving by Nicolas Sceaux).


Published sheet music
---------------------

   * Mutopia Project (http://www.mutopiaproject.org/index.html), over
     1500 pieces of classical sheet music for free download, and the
     main showcase of LilyPond scores.

   * Adoro Music Publishing (http://www.adoromusicpub.com/),
     high-quality scores of sacred music, available for immediate
     download or in traditional paper format.

   * The Shady Lane Publishing (http://theshadylanepublishing.com/), a
     "micro musical publishing house" whose goal is to promote a new
     form of musical economy closer to the musicians and music lovers.


Where now?
----------

Still not convinced?  Read some of our users' *note Testimonials::.  If
you've already decided to try LilyPond, first read about our *note Text
input::.


File: lilypond-web.info,  Node: Testimonials,  Next: Text input,  Prev: Productions,  Up: Introduction

Testimonials
============

Carter Brey (http://nyphil.org/meet/orchestra/index.cfm?page=profile&personNum=7), Principal Cellist, New York Philharmonic
...........................................................................................................................

"... I've written a couple of encore pieces for solo cello which I've
printed with LilyPond and which I'm going to submit to Schirmer for
publication. I'll bet their engraved version wouldn't look half as
sharp as mine!"

Orm Finnendahl (http://icem-www.folkwang-hochschule.de/~finnendahl/), professor of Composition, Musikhochschule Freiburg
........................................................................................................................

"Although I don't know [LilyPond] very well yet, I'm **very* impressed.
I used the program to input a motet of Josquin Desprez in mensural
notation and there's no doubt that lilypond outscores all other
notation programs easily concerning speed, ease of use and look!"

Darius Blasband, composer (Brussels, Belgium)
.............................................

"[..after the first orchestra rehearsal] I got numerous compliments
about the quality of the scores. Even more importantly, while Lilypond
provides numerous hacks to improve the way its scores look, what the
orchestra got from me is basically the raw, untouched output."

Kieren MacMillan, composer (Toronto, Canada)
............................................

"thanks and kudos to the development team for their incredible work.
I've never seen anything approaching the output that I get from
Lilypond - I'm totally confident that my music publishing needs will be
fulfilled beyond my expectations using this great application. [..]
basically untweaked Lilypond output [..] looks better than most recent
`professional' publications I've compared it to (q.v., just about any
Warner Bros. score, and even many of the most recent by `the old
houses'). [..]"

   "Beat that, Finale/Sibelius/Igor/whatever!!!"

Chris Cannam, lead programmer of the RoseGarden (http://www.rosegardenmusic.com/) project.
..........................................................................................

"Lilypond is obviously the zillion-ton gorilla [of great music
typesetting]."

Chris Snyder, Adoro Music Publishing (http://www.adoromusicpub.com/)
....................................................................

"The way that music is entered for LilyPond causes me to think in a
more musical way - there have been times when I've been stumped as to
how to tell Lily to engrave something, only to realize that even if I
did get it exactly as the composer wanted, the music would be confusing
to read.  LilyPond makes it much easier for me to work in my dual
editor+engraver role."

   "I've been using LilyPond exclusively for my fledgling music
publishing business. Virtually without exception, every composer has
been blown away by the quality of the engraving when presented with the
proofs of their music about to be published. I deserve some of the
credit for this - I spend a lot of time tweaking output, especially
ties (mainly in chords) - but LilyPond gives me an excellent starting
point, a very intuitive interface, and the ability to modify absolutely
anything if I want to take the time. I'm convinced that no commercial
product can come close."

David Bobroff, Bass Trombone, Iceland Symphony Orchestra
........................................................

"I think Lilypond is great [..] The more I learn about LilyPond the
more I like it!"

Vaylor Trucks, Electric guitar player (Yes, related to (http://www.allmanbrothersband.com/modules.php?op=modload&name=userpage&file=content&page_id=12))
........................................................................................................................................................

"I am super impressed with LilyPond [..]"

   "THIS IS THE BEST PROGRAM EVER!!!"

   "Thank you all SO MUCH for your hard work and dedication!"

Nicolas Sceaux (http://nicolas.sceaux.free.fr/), Mutopia (http://www.mutopiaproject.org/) contributor
.....................................................................................................

"I had a kind of hate-passion relationship with it. Passion because the
first score I saw was so amazing! The description of LilyPond lies
about its beautifulness, it is too modest! [..] as LilyPond is getting
always better, and as I look closer how things are done in scheme, I
have less and less frustrations. Anyway, what I mean is: thank you for
providing LilyPond, it is really good."

Werner Lemberg (http://www.troff.org/whoswho.html#werner), Conductor at the Theatre in Koblenz, Germany and distinguished GNU Hacker.
.....................................................................................................................................

"Anyway, LilyPond does an amazingly good job!"

Paul Davis, developer of JACK (http://jackaudio.org/) and Ardour (http://www.ardour.org/).
..........................................................................................

"I think [LilyPond is] an incredible program, and it produces
wonderful, wonderful output. when i read an interview about it last
year, i was raving to several friends of mine about its potential."

Where now?
----------

Read about our *note Text input::.


File: lilypond-web.info,  Node: Text input,  Next: Alternate input,  Prev: Testimonials,  Up: Introduction

Text input
==========

"Compiling" Music
-----------------

LilyPond is a _compiled_ system: it is run on a text file containing
the notes.  The resulting output is viewed on-screen or printed.  In
some ways, LilyPond is more similar to a programming language than
graphical score editing software.

   You do not write music by dragging notes from a graphical toolbar
and placing them on a dynamically refreshing score; you write music by
typing text.  This text is interpreted (or "compiled") by LilyPond,
which produces beautifully engraved sheet music.

   People accustomed to graphical user interfaces might need to learn a
new way of working, but the results are definitely worth it!

          Note: We present a quick overview of our text input - it's not
          as complicated as it sounds!  Don't worry about understanding
          every detail in these examples; our beginner documentation
          covers everything at a much more gradual pace.

It's as simple as A B C
.......................

Notes are encoded with letters and numbers.  Special commands are
entered with backslashes.

   Alterations are made with different names: add `-is' for sharp, and
`-es' for flat (these are Dutch note names, other languages are
available).  LilyPond figures out where to put accidentals.

Pop music
.........

Put chords and lyrics together to get a lead sheet:

Orchestral parts
................

The input file contains the notes of piece.  Score and parts can be
made from a single input file.  So, changing a note always affects both
parts and score.  To share the notes, the music is assigned to a
variable:

   This variable is then used in a single part (here transposed, with
condensed multi rests):

   The same variable is used in the full score (here in concert pitch):

Beginner Documentation
......................

We realize that many users find this way of entering music a bit odd.
For this reason, we have written extensive documentation to help new
users, beginning with *note Learning::.

   Please read the Learning Manual before complaining about bugs!  New
users occasionally believe that LilyPond is not working correctly, when
in fact it is working precisely as designed.

Easier editing environments
...........................

LilyPond is primarily concerned with producing top-quality engraved
sheet music; creating a Graphical User Interface (GUI) would distract
us from this goal.  However, there are other projects aimed at making
it easier to create LilyPond input files.

   Some editing environments include syntax highlighting, automatic
command completion, and pre-made templates.  Other programs actually
provide a GUI which allows direct manipulation of a graphical score.
For more information, see our documentation about *note Alternate
input::.

Where now?
----------

You are now ready to *note Download LilyPond: Download.  Still not
convinced?  Read about easier editing environments in *note Alternate
input::.


File: lilypond-web.info,  Node: Alternate input,  Prev: Text input,  Up: Introduction

Alternate input
===============

Graphical environment: Denemo
-----------------------------

`http://denemo.org'

   Denemo is graphical editor which generates LilyPond source code and
also allows audio playback.  It is currently in development and
generates code for older versions of LilyPond (V2.8.7).  It allows
users to view the LilyPond source code in parallel to the graphical
view.

Mixed environment: LilyPondTool
-------------------------------

`http://lilypondtool.organum.hu'

   Created as a plugin for the jEdit (http://www.jedit.org) text editor,
LilyPondTool is one of the most feature-rich text-based tool for
editing LilyPond scores.  Its features include a Document Wizard with
lyrics support to set up documents easier, and embedded PDF viewer with
advanced point-and-click support.

Mixed environment: Frescobaldi
------------------------------

`http://www.frescobaldi.org'

   Frescobaldi is a dedicated LilyPond music and text editor with
built-in PDF previewer, a powerful score wizard and many editing
features.  It is built on top of the KDE4 libraries and runs currently
on all flavours of Linux and other UNIX-like operating systems.

Text environment: Emacs and Vim
-------------------------------

`http://FIXME'

   Emacs is a text editor with language-sensitive capabilities for many
different computer languages.  Emacs is a highly extensible editor and
can be used as an Integrated Development Environment.  There is a
`lilypond mode' which supplies the language definitions for working
with Lilypond source files.

   Vim is a minimal text editor and is an extension of the older Unix
`vi' editor.  It is also extensible and configurable.

   As a general rule, if you are not already familiar with emacs or
vim, then you would probably prefer to use a different editor for
writing LilyPond input files.

Other
-----

Mixed environment: LilyKDE
..........................

`http://lilykde.googlecode.com/'

   LilyKDE is a plugin for KDE's text editor Kate
(http://kate-editor.org/).  It has a powerful Score Wizard to quickly
setup a LilyPond document and an embedded PDF viewer.

   LilyKDE can use Rumor (http://www.volny.cz/smilauer/rumor/), so
music can entered by playing on a MIDI keyboard.

   Other features are lyric hyphenation and running LilyPond on
multiple files at once from within the KDE file manager.

Text environment: TexShop
.........................

`http://www.uoregon.edu/~koch/texshop'

   The TexShop editor for MacOS X can be extended to run LilyPond,
`lilypond-book' and `convert-ly' from within the editor, using the
extensions available at
`http://www.dimi.uniud.it/vitacolo/freesoftware.html#desktoppub'.

Other programs can export LilyPond code
---------------------------------------

Graphical environments:
.......................

   * NoteEdit (http://noteedit.berlios.de) which imports MusicXML
     (http://www.musicxml.com/xml.html)

   * Rosegarden (http://www.rosegardenmusic.com), which imports MIDI

   * NtEd
     (http://vsr.informatik.tu-chemnitz.de/staff/jan/nted/nted.xhtml),
     has experimental export for LilyPond.

   * TuxGuitar (http://www.tuxguitar.com.ar/), can export to LilyPond.

   * MuseScore (http://musescore.org) can export to LilyPond.

   * Canorus (http://canorus.org) can also export to LilyPond, but is
     still beta-software. Testers welcome though.

Command Line Tools:
...................

   * Rumor (http://www.volny.cz/smilauer/rumor/rumor.html), a realtime
     monophonic MIDI to LilyPond converter.

   * lyqi (http://nicolas.sceaux.free.fr/lilypond/lyqi.html), an Emacs
     major mode.

   * xml2ly (http://www.nongnu.org/xml2ly/), which imports MusicXML
     (http://www.musicxml.com/xml.html)

   * FOMUS (http://common-lisp.net/project/fomus/), a LISP library to
     generate music notation

Where now?
----------

You are now ready to *note Download LilyPond: Download.

   Still not convinced?  Many composers, musicians, and conductors have
learned how to write music in our input format.  Experienced users even
report that they can enter a full score in LilyPond faster than with a
piano keyboard or mouse+GUI!  Perhaps you would like to review the
*note Features::, *note Examples::, or the *note Freedom:: that
LilyPond provides, or read about users' *note Productions:: and *note
Testimonials::.  In addition, our approach to the computational
aesthetics of classical engraving is explained in our *note
Background::.

Legalese
--------

All logos and product images are copyright and trademark acknowledged.

   Tux the Linux Penguin was created by lewing@isc.tamu.edu
(mailto:lewing@isc.tamu.edu) with the Gnu Image Manipulation Program
(http://www.isc.tamu.edu/~lewing/gimp/).

   The FreeBSD logo is a registered trademark of The FreeBSD Foundation
(http://www.freebsd.org/).

   The "X image" is not a registered trademark.  It was created by
Nihonjoe (http://en.wikipedia.org/wiki/User:Nihonjoe) and CyberSkull
(http://en.wikipedia.org/wiki/User:CyberSkull), and placed under the
GNU Free Documentation License version 1.2 or later.  We found the
image on this Wikipedia Commons page
(http://commons.wikimedia.org/wiki/File:Mac_OS_X_Userbox_X.png).

   The "four colored rectangles image" is not a registered trademark.
It was created by Rohitbd (http://en.wikipedia.org/wiki/User:Rohitbd)
and placed under the GNU Free Documentation License version 1.2.  We
found the image on this Wikipedia Commons page
(http://commons.wikimedia.org/wiki/Category:Microsoft_Windows_logos).


File: lilypond-web.info,  Node: Download,  Next: Manuals,  Prev: Introduction,  Up: Top

Download
********

Downloads for LilyPond 2.12.2
=============================

          Note: LilyPond is a *text-based* music engraver; it is more
          similar to a programming language than a graphical score
          editing program.  Before downloading LilyPond, please read
          about our *note Text input::.

For users
---------

   * *note  : Unix.  *note Unix (Linux and FreeBSD): Unix.

   * *note : MacOS X.  *note MacOS X: MacOS X.

   * *note : Windows.  *note Microsoft Windows: Windows.


For developers
--------------

   * *note Source::: for packagers

   * *note Old downloads::: old versions

   * *note Development::: latest unstable version


Software License
----------------

LilyPond is published under the *note GNU General Public License: GPL.

Sponsors
--------

Many thanks to Virgina Tech (http://www.vt.edu/) and linuxaudio.org
(http://www.linuxaudio.org/) for sponsoring our bandwidth.

Legalese
--------

All logos and product images are copyright and trademark acknowledged.

   Tux the Linux Penguin was created by lewing@isc.tamu.edu
(mailto:lewing@isc.tamu.edu) with the Gnu Image Manipulation Program
(http://www.isc.tamu.edu/~lewing/gimp/).

   The FreeBSD logo is a registered trademark of The FreeBSD Foundation
(http://www.freebsd.org/).

   The "X image" is not a registered trademark.  It was created by
Nihonjoe (http://en.wikipedia.org/wiki/User:Nihonjoe) and CyberSkull
(http://en.wikipedia.org/wiki/User:CyberSkull), and placed under the
GNU Free Documentation License version 1.2 or later.  We found the
image on this Wikipedia Commons page
(http://commons.wikimedia.org/wiki/File:Mac_OS_X_Userbox_X.png).

   The "four colored rectangles image" is not a registered trademark.
It was created by Rohitbd (http://en.wikipedia.org/wiki/User:Rohitbd)
and placed under the GNU Free Documentation License version 1.2.  We
found the image on this Wikipedia Commons page
(http://commons.wikimedia.org/wiki/Category:Microsoft_Windows_logos).

* Menu:

* Unix::
* MacOS X::
* Windows::
* Source::
* Old downloads::
* GPL::


File: lilypond-web.info,  Node: Unix,  Next: MacOS X,  Up: Download

Unix
====

Generic Packages or Distribution-Specific Packages?
---------------------------------------------------

Many distributions include LilyPond in their normal package system.
These versions are easier to install and uninstall than the generic
packages, but they may be older.  If you wish to use our generic
packages, please uninstall the official version from your system using
the normal package manager for your distribution.  See your
distribution's documentation about how to use their package manager.

Generic Packages
----------------

Download
........

   *  Linux x86: LilyPond 2.12.2-1
     (http://download.linuxaudio.org/lilypond/binaries/linux-x86/lilypond-2.12.2-1.linux-x86.sh)
     (if in doubt, use this)

   *  Linux 64: LilyPond 2.12.2-1
     (http://download.linuxaudio.org/lilypond/binaries/linux-64/lilypond-2.12.2-1.linux-64.sh)

   *  Linux PPC: LilyPond 2.12.2-1
     (http://download.linuxaudio.org/lilypond/binaries/linux-ppc/lilypond-2.12.2-1.linux-ppc.sh)

   *  FreeBSD i386: LilyPond 2.12.2-1
     (http://download.linuxaudio.org/lilypond/binaries/freebsd-x86/lilypond-2.12.2-1.freebsd-x86.sh)

   *  FreeBSD amd64: LilyPond 2.12.2-1
     (http://download.linuxaudio.org/lilypond/binaries/freebsd-x86/lilypond-2.12.2-1.freebsd-64.sh)


Install
.......

In the shell, type:

     cd PATH-TO-DOWNLOAD-DIRECTORY
     sh lilypond-2.12.2-OS-TYPE.sh

Uninstall
.........

In the shell, type:

     uninstall-lilypond

Distribution-specific Packages
------------------------------

Please use your distribution's package manager to install or upgrade to
these versions.

   *  Fedora: LilyPond 2.12.0
     (https://admin.fedoraproject.org/pkgdb/packages/name/lilypond)

   *  Ubuntu: LilyPond 2.12.1
     (https://launchpad.net/ubuntu/+source/lilypond)

   *  Slackware: LilyPond 2.12.1
     (http://www.johannes-schoepfer.de/lilypond/)

   *  Debian: LilyPond 2.10.33
     (http://packages.debian.org/search?keywords=lilypond)

   *  openSUSE: LilyPond 2.10.33
     (http://opensuse.org/?fixme=urg-no-lilypond-package-page)


Legalese
--------

All logos and product images are copyright and trademark acknowledged.

   Tux the Linux Penguin was created by lewing@isc.tamu.edu
(mailto:lewing@isc.tamu.edu) with the Gnu Image Manipulation Program
(http://www.isc.tamu.edu/~lewing/gimp/).

   The FreeBSD logo is a registered trademark of The FreeBSD Foundation
(http://www.freebsd.org/).


File: lilypond-web.info,  Node: MacOS X,  Next: Windows,  Prev: Unix,  Up: Download

MacOS X
=======

Packages
--------

Download
........

   *  MacOS X x86: LilyPond 2.12.2-1
     (http://download.linuxaudio.org/lilypond/binaries/darwin-x86/lilypond-2.12.2-1.darwin-x86.tar.bz2)
     For Intel chips (if in doubt, use this).

   *  MacOS X PPC: LilyPond 2.12.2-1
     (http://download.linuxaudio.org/lilypond/binaries/darwin-ppc/lilypond-2.12.2-1.darwin-ppc.tar.bz2)
     For G3 and G4 CPUs (old Apple computers).


Install
.......

Double-click the downloaded file, then drag it to wherever you want.

Uninstall
.........

Delete the LilyPond.app folder.

Running on the command-line
---------------------------

          Note: If you are happy with the GUI, then please ignore these
          instructions.

MacOS X on the command line
...........................

The most convenient way to run lilypond scripts is by setting up
"helper" scripts of your own.

  1. Create a directory to store these scripts,

          mkdir -p ~/bin
          cd ~/bin

  2. Create a file called `lilypond' which contains

          exec DIR/LilyPond.app/Contents/Resources/bin/lilypond "$@"

               Note: DIR will generally be `/Applications/'

  3. Create similar files `lilypond-book', `convert-ly', and any other
     scripts you wish to use, by replacing the `bin/lilypond' with
     `bin/convert-ly' (or other program name).

  4. Make the file executable,

          chmod u+x lilypond

  5. Now, add this directory to your path.  Modify (or create) a file
     called `.profile' in your home directory such that it contains

          export PATH=$PATH:~/bin

     This file should end with a blank line.


Invoking individual scripts
...........................

The scripts -- such as `lilypond-book', `convert-ly', `abc2ly', and
even `lilypond' itself -- are included inside the `.app' file for
MacOS X.

   Scripts can also be run from the command line by invoking them
directly:

     PATH/TO/LilyPond.app/Contents/Resources/bin/lilypond

   The same is true for all other scripts in that directory, such as
`lilypond-book' and `convert-ly'.

Legalese
--------

All logos and product images are copyright and trademark acknowledged.

   The "X image" is not a registered trademark.  It was created by
Nihonjoe (http://en.wikipedia.org/wiki/User:Nihonjoe) and CyberSkull
(http://en.wikipedia.org/wiki/User:CyberSkull), and placed under the
GNU Free Documentation License version 1.2 or later.  We found the
image on this Wikipedia Commons page
(http://commons.wikimedia.org/wiki/File:Mac_OS_X_Userbox_X.png).


File: lilypond-web.info,  Node: Windows,  Next: Source,  Prev: MacOS X,  Up: Download

Windows
=======

Packages
--------

Download
........

   *  Windows: LilyPond 2.12.2-1
     (http://download.linuxaudio.org/lilypond/binaries/mingw/lilypond-2.12.2-1.mingw.exe)
     For Windows ME, NT, 2000, XP, and Vista.


Install
.......

  1. Locate the downloaded file and double-click on it to start the
     installer. You will be presented a window titled "Open File -
     Security Warning", click on Run to continue.

  2. You will be presented the License Agreement; read this carefully,
     and click on the Next button if you accept it.

  3. Preferably leave the destination folder to the default, else
     browse to choose a different location, and click on the Next
     button.

  4. Next is the Installation Options window, leave the three options
     checked, as you will want to have all of these installed. Click on
     the Next button.

  5. Installation now commences, wait a minute or less for installation
     to complete. There is a Show Details button that when clicked on
     will show all the files installed and where, nothing you
     necessarily need to look at. Click on the Finish button.

  6. Lilypond is now installed.


Uninstall
.........

There are two uninstallation routes -

  1. Choose Uninstall from the Lilypond menu from the start menu

  2. Open your Install/Uninstall Applications on the Control Panel,
     scroll down to Lilypond and click on the Uninstall buttom.


Running on the command-line
---------------------------

          Note: If you are happy with the GUI, then please ignore these
          instructions.

Legalese
--------

All logos and product images are copyright and trademark acknowledged.

   The "four colored rectangles image" is not a registered trademark.
It was created by Rohitbd (http://en.wikipedia.org/wiki/User:Rohitbd)
and placed under the GNU Free Documentation License version 1.2.  We
found the image on this Wikipedia Commons page
(http://commons.wikimedia.org/wiki/Category:Microsoft_Windows_logos).


File: lilypond-web.info,  Node: Source,  Next: Old downloads,  Prev: Windows,  Up: Download

Source
======

          Note: We *do not* recommend that you attempt to build
          LilyPond yourself; almost all user needs are better met with
          the pre-built version.

Source tarball
--------------

lilypond-2.12.2.tar.gz
(http://download.linuxaudio.org/lilypond/sources/v2.12/lilypond-2.12.2.tar.gz)

   For an extensive listing of all versions (old and new), see our
download site (http://download.linuxaudio.org/lilypond/binaries/).

Compiling instructions
----------------------

Instructions are listed in *note Compiling LilyPond:
(lilypond-contributor)Compiling LilyPond.


File: lilypond-web.info,  Node: Old downloads,  Next: GPL,  Prev: Source,  Up: Download

Old downloads
=============

All versions
------------

For an extensive listing of all versions (old and new), see our
download site (http://download.linuxaudio.org/lilypond/binaries/).


File: lilypond-web.info,  Node: GPL,  Prev: Old downloads,  Up: Download

GPL
===

Software license
----------------

GNU LilyPond is published under the GNU General Public License.  An
introduction to this license, and our reasons for choosing it, is given
in *note Freedom::.

GNU General Public License
--------------------------

                        Version 3, 29 June 2007

     Copyright (C) 2007 Free Software Foundation, Inc. `http://fsf.org/'

     Everyone is permitted to copy and distribute verbatim copies of this
     license document, but changing it is not allowed.

Preamble
========

The GNU General Public License is a free, copyleft license for software
and other kinds of works.

   The licenses for most software and other practical works are designed
to take away your freedom to share and change the works.  By contrast,
the GNU General Public License is intended to guarantee your freedom to
share and change all versions of a program--to make sure it remains
free software for all its users.  We, the Free Software Foundation, use
the GNU General Public License for most of our software; it applies
also to any other work released this way by its authors.  You can apply
it to your programs, too.

   When we speak of free software, we are referring to freedom, not
price.  Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
them if you wish), that you receive source code or can get it if you
want it, that you can change the software or use pieces of it in new
free programs, and that you know you can do these things.

   To protect your rights, we need to prevent others from denying you
these rights or asking you to surrender the rights.  Therefore, you
have certain responsibilities if you distribute copies of the software,
or if you modify it: responsibilities to respect the freedom of others.

   For example, if you distribute copies of such a program, whether
gratis or for a fee, you must pass on to the recipients the same
freedoms that you received.  You must make sure that they, too, receive
or can get the source code.  And you must show them these terms so they
know their rights.

   Developers that use the GNU GPL protect your rights with two steps:
(1) assert copyright on the software, and (2) offer you this License
giving you legal permission to copy, distribute and/or modify it.

   For the developers' and authors' protection, the GPL clearly explains
that there is no warranty for this free software.  For both users' and
authors' sake, the GPL requires that modified versions be marked as
changed, so that their problems will not be attributed erroneously to
authors of previous versions.

   Some devices are designed to deny users access to install or run
modified versions of the software inside them, although the
manufacturer can do so.  This is fundamentally incompatible with the
aim of protecting users' freedom to change the software.  The
systematic pattern of such abuse occurs in the area of products for
individuals to use, which is precisely where it is most unacceptable.
Therefore, we have designed this version of the GPL to prohibit the
practice for those products.  If such problems arise substantially in
other domains, we stand ready to extend this provision to those domains
in future versions of the GPL, as needed to protect the freedom of
users.

   Finally, every program is threatened constantly by software patents.
States should not allow patents to restrict development and use of
software on general-purpose computers, but in those that do, we wish to
avoid the special danger that patents applied to a free program could
make it effectively proprietary.  To prevent this, the GPL assures that
patents cannot be used to render the program non-free.

   The precise terms and conditions for copying, distribution and
modification follow.

TERMS AND CONDITIONS
====================

  0. Definitions.

     "This License" refers to version 3 of the GNU General Public
     License.

     "Copyright" also means copyright-like laws that apply to other
     kinds of works, such as semiconductor masks.

     "The Program" refers to any copyrightable work licensed under this
     License.  Each licensee is addressed as "you".  "Licensees" and
     "recipients" may be individuals or organizations.

     To "modify" a work means to copy from or adapt all or part of the
     work in a fashion requiring copyright permission, other than the
     making of an exact copy.  The resulting work is called a "modified
     version" of the earlier work or a work "based on" the earlier work.

     A "covered work" means either the unmodified Program or a work
     based on the Program.

     To "propagate" a work means to do anything with it that, without
     permission, would make you directly or secondarily liable for
     infringement under applicable copyright law, except executing it
     on a computer or modifying a private copy.  Propagation includes
     copying, distribution (with or without modification), making
     available to the public, and in some countries other activities as
     well.

     To "convey" a work means any kind of propagation that enables other
     parties to make or receive copies.  Mere interaction with a user
     through a computer network, with no transfer of a copy, is not
     conveying.

     An interactive user interface displays "Appropriate Legal Notices"
     to the extent that it includes a convenient and prominently visible
     feature that (1) displays an appropriate copyright notice, and (2)
     tells the user that there is no warranty for the work (except to
     the extent that warranties are provided), that licensees may
     convey the work under this License, and how to view a copy of this
     License.  If the interface presents a list of user commands or
     options, such as a menu, a prominent item in the list meets this
     criterion.

  1. Source Code.

     The "source code" for a work means the preferred form of the work
     for making modifications to it.  "Object code" means any
     non-source form of a work.

     A "Standard Interface" means an interface that either is an
     official standard defined by a recognized standards body, or, in
     the case of interfaces specified for a particular programming
     language, one that is widely used among developers working in that
     language.

     The "System Libraries" of an executable work include anything,
     other than the work as a whole, that (a) is included in the normal
     form of packaging a Major Component, but which is not part of that
     Major Component, and (b) serves only to enable use of the work
     with that Major Component, or to implement a Standard Interface
     for which an implementation is available to the public in source
     code form.  A "Major Component", in this context, means a major
     essential component (kernel, window system, and so on) of the
     specific operating system (if any) on which the executable work
     runs, or a compiler used to produce the work, or an object code
     interpreter used to run it.

     The "Corresponding Source" for a work in object code form means all
     the source code needed to generate, install, and (for an executable
     work) run the object code and to modify the work, including
     scripts to control those activities.  However, it does not include
     the work's System Libraries, or general-purpose tools or generally
     available free programs which are used unmodified in performing
     those activities but which are not part of the work.  For example,
     Corresponding Source includes interface definition files
     associated with source files for the work, and the source code for
     shared libraries and dynamically linked subprograms that the work
     is specifically designed to require, such as by intimate data
     communication or control flow between those subprograms and other
     parts of the work.

     The Corresponding Source need not include anything that users can
     regenerate automatically from other parts of the Corresponding
     Source.

     The Corresponding Source for a work in source code form is that
     same work.

  2. Basic Permissions.

     All rights granted under this License are granted for the term of
     copyright on the Program, and are irrevocable provided the stated
     conditions are met.  This License explicitly affirms your unlimited
     permission to run the unmodified Program.  The output from running
     a covered work is covered by this License only if the output,
     given its content, constitutes a covered work.  This License
     acknowledges your rights of fair use or other equivalent, as
     provided by copyright law.

     You may make, run and propagate covered works that you do not
     convey, without conditions so long as your license otherwise
     remains in force.  You may convey covered works to others for the
     sole purpose of having them make modifications exclusively for
     you, or provide you with facilities for running those works,
     provided that you comply with the terms of this License in
     conveying all material for which you do not control copyright.
     Those thus making or running the covered works for you must do so
     exclusively on your behalf, under your direction and control, on
     terms that prohibit them from making any copies of your
     copyrighted material outside their relationship with you.

     Conveying under any other circumstances is permitted solely under
     the conditions stated below.  Sublicensing is not allowed; section
     10 makes it unnecessary.

  3. Protecting Users' Legal Rights From Anti-Circumvention Law.

     No covered work shall be deemed part of an effective technological
     measure under any applicable law fulfilling obligations under
     article 11 of the WIPO copyright treaty adopted on 20 December
     1996, or similar laws prohibiting or restricting circumvention of
     such measures.

     When you convey a covered work, you waive any legal power to forbid
     circumvention of technological measures to the extent such
     circumvention is effected by exercising rights under this License
     with respect to the covered work, and you disclaim any intention
     to limit operation or modification of the work as a means of
     enforcing, against the work's users, your or third parties' legal
     rights to forbid circumvention of technological measures.

  4. Conveying Verbatim Copies.

     You may convey verbatim copies of the Program's source code as you
     receive it, in any medium, provided that you conspicuously and
     appropriately publish on each copy an appropriate copyright notice;
     keep intact all notices stating that this License and any
     non-permissive terms added in accord with section 7 apply to the
     code; keep intact all notices of the absence of any warranty; and
     give all recipients a copy of this License along with the Program.

     You may charge any price or no price for each copy that you convey,
     and you may offer support or warranty protection for a fee.

  5. Conveying Modified Source Versions.

     You may convey a work based on the Program, or the modifications to
     produce it from the Program, in the form of source code under the
     terms of section 4, provided that you also meet all of these
     conditions:

       a. The work must carry prominent notices stating that you
          modified it, and giving a relevant date.

       b. The work must carry prominent notices stating that it is
          released under this License and any conditions added under
          section 7.  This requirement modifies the requirement in
          section 4 to "keep intact all notices".

       c. You must license the entire work, as a whole, under this
          License to anyone who comes into possession of a copy.  This
          License will therefore apply, along with any applicable
          section 7 additional terms, to the whole of the work, and all
          its parts, regardless of how they are packaged.  This License
          gives no permission to license the work in any other way, but
          it does not invalidate such permission if you have separately
          received it.

       d. If the work has interactive user interfaces, each must display
          Appropriate Legal Notices; however, if the Program has
          interactive interfaces that do not display Appropriate Legal
          Notices, your work need not make them do so.

     A compilation of a covered work with other separate and independent
     works, which are not by their nature extensions of the covered
     work, and which are not combined with it such as to form a larger
     program, in or on a volume of a storage or distribution medium, is
     called an "aggregate" if the compilation and its resulting
     copyright are not used to limit the access or legal rights of the
     compilation's users beyond what the individual works permit.
     Inclusion of a covered work in an aggregate does not cause this
     License to apply to the other parts of the aggregate.

  6. Conveying Non-Source Forms.

     You may convey a covered work in object code form under the terms
     of sections 4 and 5, provided that you also convey the
     machine-readable Corresponding Source under the terms of this
     License, in one of these ways:

       a. Convey the object code in, or embodied in, a physical product
          (including a physical distribution medium), accompanied by the
          Corresponding Source fixed on a durable physical medium
          customarily used for software interchange.

       b. Convey the object code in, or embodied in, a physical product
          (including a physical distribution medium), accompanied by a
          written offer, valid for at least three years and valid for
          as long as you offer spare parts or customer support for that
          product model, to give anyone who possesses the object code
          either (1) a copy of the Corresponding Source for all the
          software in the product that is covered by this License, on a
          durable physical medium customarily used for software
          interchange, for a price no more than your reasonable cost of
          physically performing this conveying of source, or (2) access
          to copy the Corresponding Source from a network server at no
          charge.

       c. Convey individual copies of the object code with a copy of
          the written offer to provide the Corresponding Source.  This
          alternative is allowed only occasionally and noncommercially,
          and only if you received the object code with such an offer,
          in accord with subsection 6b.

       d. Convey the object code by offering access from a designated
          place (gratis or for a charge), and offer equivalent access
          to the Corresponding Source in the same way through the same
          place at no further charge.  You need not require recipients
          to copy the Corresponding Source along with the object code.
          If the place to copy the object code is a network server, the
          Corresponding Source may be on a different server (operated
          by you or a third party) that supports equivalent copying
          facilities, provided you maintain clear directions next to
          the object code saying where to find the Corresponding Source.
          Regardless of what server hosts the Corresponding Source, you
          remain obligated to ensure that it is available for as long
          as needed to satisfy these requirements.

       e. Convey the object code using peer-to-peer transmission,
          provided you inform other peers where the object code and
          Corresponding Source of the work are being offered to the
          general public at no charge under subsection 6d.


     A separable portion of the object code, whose source code is
     excluded from the Corresponding Source as a System Library, need
     not be included in conveying the object code work.

     A "User Product" is either (1) a "consumer product", which means
     any tangible personal property which is normally used for personal,
     family, or household purposes, or (2) anything designed or sold for
     incorporation into a dwelling.  In determining whether a product
     is a consumer product, doubtful cases shall be resolved in favor of
     coverage.  For a particular product received by a particular user,
     "normally used" refers to a typical or common use of that class of
     product, regardless of the status of the particular user or of the
     way in which the particular user actually uses, or expects or is
     expected to use, the product.  A product is a consumer product
     regardless of whether the product has substantial commercial,
     industrial or non-consumer uses, unless such uses represent the
     only significant mode of use of the product.

     "Installation Information" for a User Product means any methods,
     procedures, authorization keys, or other information required to
     install and execute modified versions of a covered work in that
     User Product from a modified version of its Corresponding Source.
     The information must suffice to ensure that the continued
     functioning of the modified object code is in no case prevented or
     interfered with solely because modification has been made.

     If you convey an object code work under this section in, or with,
     or specifically for use in, a User Product, and the conveying
     occurs as part of a transaction in which the right of possession
     and use of the User Product is transferred to the recipient in
     perpetuity or for a fixed term (regardless of how the transaction
     is characterized), the Corresponding Source conveyed under this
     section must be accompanied by the Installation Information.  But
     this requirement does not apply if neither you nor any third party
     retains the ability to install modified object code on the User
     Product (for example, the work has been installed in ROM).

     The requirement to provide Installation Information does not
     include a requirement to continue to provide support service,
     warranty, or updates for a work that has been modified or
     installed by the recipient, or for the User Product in which it
     has been modified or installed.  Access to a network may be denied
     when the modification itself materially and adversely affects the
     operation of the network or violates the rules and protocols for
     communication across the network.

     Corresponding Source conveyed, and Installation Information
     provided, in accord with this section must be in a format that is
     publicly documented (and with an implementation available to the
     public in source code form), and must require no special password
     or key for unpacking, reading or copying.

  7. Additional Terms.

     "Additional permissions" are terms that supplement the terms of
     this License by making exceptions from one or more of its
     conditions.  Additional permissions that are applicable to the
     entire Program shall be treated as though they were included in
     this License, to the extent that they are valid under applicable
     law.  If additional permissions apply only to part of the Program,
     that part may be used separately under those permissions, but the
     entire Program remains governed by this License without regard to
     the additional permissions.

     When you convey a copy of a covered work, you may at your option
     remove any additional permissions from that copy, or from any part
     of it.  (Additional permissions may be written to require their own
     removal in certain cases when you modify the work.)  You may place
     additional permissions on material, added by you to a covered work,
     for which you have or can give appropriate copyright permission.

     Notwithstanding any other provision of this License, for material
     you add to a covered work, you may (if authorized by the copyright
     holders of that material) supplement the terms of this License
     with terms:

       a. Disclaiming warranty or limiting liability differently from
          the terms of sections 15 and 16 of this License; or

       b. Requiring preservation of specified reasonable legal notices
          or author attributions in that material or in the Appropriate
          Legal Notices displayed by works containing it; or

       c. Prohibiting misrepresentation of the origin of that material,
          or requiring that modified versions of such material be
          marked in reasonable ways as different from the original
          version; or

       d. Limiting the use for publicity purposes of names of licensors
          or authors of the material; or

       e. Declining to grant rights under trademark law for use of some
          trade names, trademarks, or service marks; or

       f. Requiring indemnification of licensors and authors of that
          material by anyone who conveys the material (or modified
          versions of it) with contractual assumptions of liability to
          the recipient, for any liability that these contractual
          assumptions directly impose on those licensors and authors.

     All other non-permissive additional terms are considered "further
     restrictions" within the meaning of section 10.  If the Program as
     you received it, or any part of it, contains a notice stating that
     it is governed by this License along with a term that is a further
     restriction, you may remove that term.  If a license document
     contains a further restriction but permits relicensing or
     conveying under this License, you may add to a covered work
     material governed by the terms of that license document, provided
     that the further restriction does not survive such relicensing or
     conveying.

     If you add terms to a covered work in accord with this section, you
     must place, in the relevant source files, a statement of the
     additional terms that apply to those files, or a notice indicating
     where to find the applicable terms.

     Additional terms, permissive or non-permissive, may be stated in
     the form of a separately written license, or stated as exceptions;
     the above requirements apply either way.

  8. Termination.

     You may not propagate or modify a covered work except as expressly
     provided under this License.  Any attempt otherwise to propagate or
     modify it is void, and will automatically terminate your rights
     under this License (including any patent licenses granted under
     the third paragraph of section 11).

     However, if you cease all violation of this License, then your
     license from a particular copyright holder is reinstated (a)
     provisionally, unless and until the copyright holder explicitly
     and finally terminates your license, and (b) permanently, if the
     copyright holder fails to notify you of the violation by some
     reasonable means prior to 60 days after the cessation.

     Moreover, your license from a particular copyright holder is
     reinstated permanently if the copyright holder notifies you of the
     violation by some reasonable means, this is the first time you have
     received notice of violation of this License (for any work) from
     that copyright holder, and you cure the violation prior to 30 days
     after your receipt of the notice.

     Termination of your rights under this section does not terminate
     the licenses of parties who have received copies or rights from
     you under this License.  If your rights have been terminated and
     not permanently reinstated, you do not qualify to receive new
     licenses for the same material under section 10.

  9. Acceptance Not Required for Having Copies.

     You are not required to accept this License in order to receive or
     run a copy of the Program.  Ancillary propagation of a covered work
     occurring solely as a consequence of using peer-to-peer
     transmission to receive a copy likewise does not require
     acceptance.  However, nothing other than this License grants you
     permission to propagate or modify any covered work.  These actions
     infringe copyright if you do not accept this License.  Therefore,
     by modifying or propagating a covered work, you indicate your
     acceptance of this License to do so.

 10. Automatic Licensing of Downstream Recipients.

     Each time you convey a covered work, the recipient automatically
     receives a license from the original licensors, to run, modify and
     propagate that work, subject to this License.  You are not
     responsible for enforcing compliance by third parties with this
     License.

     An "entity transaction" is a transaction transferring control of an
     organization, or substantially all assets of one, or subdividing an
     organization, or merging organizations.  If propagation of a
     covered work results from an entity transaction, each party to that
     transaction who receives a copy of the work also receives whatever
     licenses to the work the party's predecessor in interest had or
     could give under the previous paragraph, plus a right to
     possession of the Corresponding Source of the work from the
     predecessor in interest, if the predecessor has it or can get it
     with reasonable efforts.

     You may not impose any further restrictions on the exercise of the
     rights granted or affirmed under this License.  For example, you
     may not impose a license fee, royalty, or other charge for
     exercise of rights granted under this License, and you may not
     initiate litigation (including a cross-claim or counterclaim in a
     lawsuit) alleging that any patent claim is infringed by making,
     using, selling, offering for sale, or importing the Program or any
     portion of it.

 11. Patents.

     A "contributor" is a copyright holder who authorizes use under this
     License of the Program or a work on which the Program is based.
     The work thus licensed is called the contributor's "contributor
     version".

     A contributor's "essential patent claims" are all patent claims
     owned or controlled by the contributor, whether already acquired or
     hereafter acquired, that would be infringed by some manner,
     permitted by this License, of making, using, or selling its
     contributor version, but do not include claims that would be
     infringed only as a consequence of further modification of the
     contributor version.  For purposes of this definition, "control"
     includes the right to grant patent sublicenses in a manner
     consistent with the requirements of this License.

     Each contributor grants you a non-exclusive, worldwide,
     royalty-free patent license under the contributor's essential
     patent claims, to make, use, sell, offer for sale, import and
     otherwise run, modify and propagate the contents of its
     contributor version.

     In the following three paragraphs, a "patent license" is any
     express agreement or commitment, however denominated, not to
     enforce a patent (such as an express permission to practice a
     patent or covenant not to sue for patent infringement).  To
     "grant" such a patent license to a party means to make such an
     agreement or commitment not to enforce a patent against the party.

     If you convey a covered work, knowingly relying on a patent
     license, and the Corresponding Source of the work is not available
     for anyone to copy, free of charge and under the terms of this
     License, through a publicly available network server or other
     readily accessible means, then you must either (1) cause the
     Corresponding Source to be so available, or (2) arrange to deprive
     yourself of the benefit of the patent license for this particular
     work, or (3) arrange, in a manner consistent with the requirements
     of this License, to extend the patent license to downstream
     recipients.  "Knowingly relying" means you have actual knowledge
     that, but for the patent license, your conveying the covered work
     in a country, or your recipient's use of the covered work in a
     country, would infringe one or more identifiable patents in that
     country that you have reason to believe are valid.

     If, pursuant to or in connection with a single transaction or
     arrangement, you convey, or propagate by procuring conveyance of, a
     covered work, and grant a patent license to some of the parties
     receiving the covered work authorizing them to use, propagate,
     modify or convey a specific copy of the covered work, then the
     patent license you grant is automatically extended to all
     recipients of the covered work and works based on it.

     A patent license is "discriminatory" if it does not include within
     the scope of its coverage, prohibits the exercise of, or is
     conditioned on the non-exercise of one or more of the rights that
     are specifically granted under this License.  You may not convey a
     covered work if you are a party to an arrangement with a third
     party that is in the business of distributing software, under
     which you make payment to the third party based on the extent of
     your activity of conveying the work, and under which the third
     party grants, to any of the parties who would receive the covered
     work from you, a discriminatory patent license (a) in connection
     with copies of the covered work conveyed by you (or copies made
     from those copies), or (b) primarily for and in connection with
     specific products or compilations that contain the covered work,
     unless you entered into that arrangement, or that patent license
     was granted, prior to 28 March 2007.

     Nothing in this License shall be construed as excluding or limiting
     any implied license or other defenses to infringement that may
     otherwise be available to you under applicable patent law.

 12. No Surrender of Others' Freedom.

     If conditions are imposed on you (whether by court order,
     agreement or otherwise) that contradict the conditions of this
     License, they do not excuse you from the conditions of this
     License.  If you cannot convey a covered work so as to satisfy
     simultaneously your obligations under this License and any other
     pertinent obligations, then as a consequence you may not convey it
     at all.  For example, if you agree to terms that obligate you to
     collect a royalty for further conveying from those to whom you
     convey the Program, the only way you could satisfy both those
     terms and this License would be to refrain entirely from conveying
     the Program.

 13. Use with the GNU Affero General Public License.

     Notwithstanding any other provision of this License, you have
     permission to link or combine any covered work with a work licensed
     under version 3 of the GNU Affero General Public License into a
     single combined work, and to convey the resulting work.  The terms
     of this License will continue to apply to the part which is the
     covered work, but the special requirements of the GNU Affero
     General Public License, section 13, concerning interaction through
     a network will apply to the combination as such.

 14. Revised Versions of this License.

     The Free Software Foundation may publish revised and/or new
     versions of the GNU General Public License from time to time.
     Such new versions will be similar in spirit to the present
     version, but may differ in detail to address new problems or
     concerns.

     Each version is given a distinguishing version number.  If the
     Program specifies that a certain numbered version of the GNU
     General Public License "or any later version" applies to it, you
     have the option of following the terms and conditions either of
     that numbered version or of any later version published by the
     Free Software Foundation.  If the Program does not specify a
     version number of the GNU General Public License, you may choose
     any version ever published by the Free Software Foundation.

     If the Program specifies that a proxy can decide which future
     versions of the GNU General Public License can be used, that
     proxy's public statement of acceptance of a version permanently
     authorizes you to choose that version for the Program.

     Later license versions may give you additional or different
     permissions.  However, no additional obligations are imposed on any
     author or copyright holder as a result of your choosing to follow a
     later version.

 15. Disclaimer of Warranty.

     THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
     APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE
     COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS"
     WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED,
     INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
     MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE
     RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.
     SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL
     NECESSARY SERVICING, REPAIR OR CORRECTION.

 16. Limitation of Liability.

     IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
     WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES
     AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU
     FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
     CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE
     THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA
     BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
     PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
     PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF
     THE POSSIBILITY OF SUCH DAMAGES.

 17. Interpretation of Sections 15 and 16.

     If the disclaimer of warranty and limitation of liability provided
     above cannot be given local legal effect according to their terms,
     reviewing courts shall apply local law that most closely
     approximates an absolute waiver of all civil liability in
     connection with the Program, unless a warranty or assumption of
     liability accompanies a copy of the Program in return for a fee.


END OF TERMS AND CONDITIONS
===========================

How to Apply These Terms to Your New Programs
=============================================

If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.

   To do so, attach the following notices to the program.  It is safest
to attach them to the start of each source file to most effectively
state the exclusion of warranty; and each file should have at least the
"copyright" line and a pointer to where the full notice is found.

     ONE LINE TO GIVE THE PROGRAM'S NAME AND A BRIEF IDEA OF WHAT IT DOES.
     Copyright (C) YEAR NAME OF AUTHOR

     This program is free software: you can redistribute it and/or modify
     it under the terms of the GNU General Public License as published by
     the Free Software Foundation, either version 3 of the License, or (at
     your option) any later version.

     This program is distributed in the hope that it will be useful, but
     WITHOUT ANY WARRANTY; without even the implied warranty of
     MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
     General Public License for more details.

     You should have received a copy of the GNU General Public License
     along with this program.  If not, see `http://www.gnu.org/licenses/'.

   Also add information on how to contact you by electronic and paper
mail.

   If the program does terminal interaction, make it output a short
notice like this when it starts in an interactive mode:

     PROGRAM Copyright (C) YEAR NAME OF AUTHOR
     This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
     This is free software, and you are welcome to redistribute it
     under certain conditions; type `show c' for details.

   The hypothetical commands `show w' and `show c' should show the
appropriate parts of the General Public License.  Of course, your
program's commands might be different; for a GUI interface, you would
use an "about box".

   You should also get your employer (if you work as a programmer) or
school, if any, to sign a "copyright disclaimer" for the program, if
necessary.  For more information on this, and how to apply and follow
the GNU GPL, see `http://www.gnu.org/licenses/'.

   The GNU General Public License does not permit incorporating your
program into proprietary programs.  If your program is a subroutine
library, you may consider it more useful to permit linking proprietary
applications with the library.  If this is what you want to do, use the
GNU Lesser General Public License instead of this License.  But first,
please read `http://www.gnu.org/philosophy/why-not-lgpl.html'.


File: lilypond-web.info,  Node: Manuals,  Next: Community,  Prev: Download,  Up: Top

Manuals
*******

Documentation for LilyPond 2.13.9
=================================

Introduction
------------

   * *note Text input::: LilyPond is a *text-based* music engraver.  If
     you are not familiar with this concept, please read this now!

   * *note Learning::: a "must-read" gentle introduction to LilyPond.

   * *note Glossary::: _(optional reading)_ explains musical terms and
     gives translations for users unfamiliar with English musical terms.

   * *note Essay::: _(optional reading)_ background information about
     the engraving process and the aesthetics of 19th century music
     engraving.


Regular use
-----------

   * *note Notation::: the main portion of the documentation; provides
     detailed information about creating notation.

   * *note Usage::: discusses the actual programs and operating
     system-specific issues.

   * *note Snippets::: short tricks, tips, and examples.


Infrequent Use
--------------

   * *note Web::: this document.

   * *note FAQ::: links to the answers of Frequently Asked Questions.

   * *note Changes::: updates since the last major version.

   * *note Extend::: programming fancy tweaks in LilyPond.

   * *note Internals::: information about LilyPond's internal
     structures, which is required for constructing tweaks.


Other material
--------------

   * *note Translated::: translation status for non-English readers.

   * *note All::: quick links, downloadable manuals, and old manuals.

   * *note Development::: manuals for the unstable version.

   * *note FDL::: these manuals are published under the GNU Free
     Documentation License.


* Menu:

* Learning::             Learning.
* Glossary::              Glossary.
* Essay::                       Essay.
* Notation::          Reference.
* Usage::           Usage.
* Snippets::                Snippets.
* Web::                      Web.
* FAQ::                         FAQ.
* Changes::                     NEWS.
* Extend::         Programming.
* Internals::         Internals.
* Translated::          Translation.
* All::                 All manuals.
* FDL::                     Licence.


File: lilypond-web.info,  Node: Learning,  Next: Glossary,  Up: Manuals

Learning
========

Learning manual
---------------

This book explains how to begin learning LilyPond, as well as
explaining some key concepts in easy terms.  You should read these
chapters in a linear fashion.

   There is a paragraph *See also* at the end of each section, which
contains cross-references to other sections: you should not follow
these cross-references at first reading.  When you have read all of the
manual, you may want to read some sections again and follow those
cross-references for more information.

Read it
-------

   * *note Top: (lilypond-learning)Top.: read this manual in the same
     format as this one.


All formats
-----------

   * Learning (split HTML) (../learning/index.html): the manual is
     split between many HTML pages.
     _(small download for each page)_

   * Learning (big HTML) (../learning-big-page.html): read this manual
     as one huge HTML page.
     _(large single download, 1.5 Mb)_

   * learning.pdf (../learning.pdf): download as a PDF file.
     _(large single download, 3 Mb)_



File: lilypond-web.info,  Node: Glossary,  Next: Essay,  Prev: Learning,  Up: Manuals

Glossary
========

Glossary
--------

This explains musical terms, and includes translations to various
languages.  If you are not familiar with music notation or music
terminology (especially if you are a non-native English speaker), it is
highly advisable to consult the glossary.

Read it
-------

   * *note Music glossary: (music-glossary)Top.: read this manual in
     the same format as this one.


All formats
-----------

   * Glossary (split HTML) (../music-glossary/index.html): the manual
     is split between many HTML pages.
     _(small download for each page)_

   * Glossay (big HTML) (../music-glossary-big-page.html): read this
     manual as one huge HTML page.
     _(large single download, 1 mb)_

   * glossary.pdf (../music-glossary.pdf): download as a PDF file.
     _(large single download, 1.5 Mb)_



File: lilypond-web.info,  Node: Essay,  Next: Notation,  Prev: Glossary,  Up: Manuals

Essay
=====

Essay
-----

This book gives a brief history of music typography, followed by an
examination of LilyPond's engraving techniques.  A comparison between
LilyPond and other music engraving systems is given.

          Note: The detailed typographical examples are easier to
          analyze in the PDF version due to its higher resolution.

Read it
-------

   * *note Essay: (lilypond-essay)Top.: read this manual in the same
     format as this one.


All formats
-----------

   * Essay (split HTML) (../essay/index.html): the manual is split
     between many HTML pages.
     _(small download for each page)_

   * Essay (big HTML) (../essay-big-page.html): read this manual as one
     huge HTML page.
     _(large single download, 2 Mb)_

   * essay.pdf (../essay.pdf): download as a PDF file.
     _(large single download, 2.5 Mb)_



File: lilypond-web.info,  Node: Notation,  Next: Usage,  Prev: Essay,  Up: Manuals

Notation
========

Notation reference
------------------

This book explains all the LilyPond commands which produce notation.

          Note: The Notation reference assumes that the reader knows
          basic material covered in the Learning manual and is familiar
          with the English musical terms presented in the Musical
          Glossary.

Read it
-------

   * *note Notation: (lilypond-notation)Top.: read this manual in the
     same format as this one.


All formats
-----------

   * Notation (split HTML) (../notation/index.html): the manual is
     split between many HTML pages.
     _(small download for each page)_

   * Notation (big HTML) (../notation-big-page.html): read this manual
     as one huge HTML page.
     _(large single download, 7 Mb)_

   * notation.pdf (../notation.pdf): download as a PDF file.
     _(large single download, 18 Mb)_



File: lilypond-web.info,  Node: Usage,  Next: Snippets,  Prev: Notation,  Up: Manuals

Usage
=====

Usage manual
------------

This book explains how to execute the programs, how to integrate
LilyPond notation with other programs, and suggests "best practices"
for efficient use.  It is recommended reading before attempting any
large projects.

Read it
-------

   * *note Usage: (lilypond-usage)Top.: read this manual in the same
     format as this one.


All formats
-----------

   * Usage (split HTML) (../usage/index.html): the manual is split
     between many HTML pages.
     _(small download for each page)_

   * Usage (big HTML) (../usage-big-page.html): read this manual as one
     huge HTML page.
     _(large single download, 300 kb)_

   * usage.pdf (../usage.pdf): download as a PDF file.
     _(large single download, 400 kb)_



File: lilypond-web.info,  Node: Snippets,  Next: Web,  Prev: Usage,  Up: Manuals

Snippets
========

Snippets
--------

This shows a selected set of LilyPond snippets from the LilyPond
Snippet Repository (http://lsr.dsi.unimi.it) (LSR).  All the snippets
are in the public domain.

   Please note that this document is not an exact subset of LSR.  LSR
is running a stable LilyPond version, so any snippet which demonstrates
new features of a development version must be added separately.  These
are stored in `input/new/' in the LilyPond source tree.

   The list of snippets for each subsection of the Notation are also
linked from the *See also* portion.

Read it
-------

   * *note Snippets: (lilypond-snippets)Top.: read this manual in the
     same format as this one.


All formats
-----------

   * Snippets (split HTML) (../snippets/index.html): the manual is
     split between many HTML pages.
     _(small download for each page)_

   * Snippets (big HTML) (../snippets-big-page.html): read this manual
     as one huge HTML page.
     _(large single download, 2.5 Mb)_

   * snippets.pdf (../snippets.pdf): download as a PDF file.
     _(large single download, 8 Mb)_



File: lilypond-web.info,  Node: Web,  Next: FAQ,  Prev: Snippets,  Up: Manuals

Web
===

Web
---

This manual supplies general information about LilyPond.  It also
contains information about various community forums, bug reporting, and
development.

Read it
-------

   * *note Web: ()Top.General Information: read this manual in the same
     format as this one.


All formats
-----------

   * Web (split HTML) (../web/index.html): the manual is split between
     many HTML pages.
     _(small download for each page)_

   * Web (big HTML) (../web-big-page.html): read this manual as one
     huge HTML page.
     _(large single download, 1 Mb)_

   * web.pdf (../web.pdf): download as a PDF file.
     _(large single download, 2 Mb)_



File: lilypond-web.info,  Node: FAQ,  Next: Changes,  Prev: Web,  Up: Manuals

FAQ
===

Introductory questions
----------------------

Where are the graphical canvas, menus, and toolbars?
....................................................

LilyPond requires you to write music as text.  Please read about our
*note Text input::.

There's a lot of documentation!  Do I need to read it?
......................................................

You need to read the *note Learning manual: Learning.  As for the rest
of documentation, you only need to read the sections which discuss the
notation that you wish to create.

That's still a lot of reading!  Is it worth it?
...............................................

Please decide for yourself; the reasons why you might want to use
LilyPond are given in the *note Introduction::.

Usage questions
---------------

Something isn't working!  How do I fix it?
..........................................

This is explained in *note Troubleshooting:
(lilypond-usage)Troubleshooting.

Why do you change the syntax?
.............................

This is explained in *note Why does the syntax change?:
(lilypond-usage)Why does the syntax change?.


File: lilypond-web.info,  Node: Changes,  Next: Extend,  Prev: FAQ,  Up: Manuals

Changes
=======

Changes
-------

This is a summary of important changes and new features in LilyPond
since the previous stable version.

Read it
-------

   * *note Changes: (lilypond-changes)Top.: read this manual in the
     same format as this one.


All formats
-----------

   * Changes (split HTML) (../changes/index.html): the manual is split
     between many HTML pages.
     _(small download for each page)_

   * Changes (big HTML) (../changes-big-page.html): read this manual as
     one huge HTML page.
     _(large single download, 6 kb)_

   * changes.pdf (../changes.pdf): download as a PDF file.
     _(small single download, 200 kb)_



File: lilypond-web.info,  Node: Extend,  Next: Internals,  Prev: Changes,  Up: Manuals

Extend
======

Extend LilyPond
---------------

This manual explains how to write extensions to LilyPond.

Read it
-------

   * *note Extend: (lilypond-extending)Top.: read this manual in the
     same format as this one.


All formats
-----------

   * Extend (split HTML) (../extending/index.html): the manual is split
     between many HTML pages.
     _(small download for each page)_

   * Extend (big HTML) (../extending-big-page.html): read this manual
     as one huge HTML page.
     _(large single download, 200 kb)_

   * extending.pdf (../extending.pdf): download as a PDF file.
     _(large single download, 400 kb)_



File: lilypond-web.info,  Node: Internals,  Next: Translated,  Prev: Extend,  Up: Manuals

Internals
=========

Internals reference
-------------------

This is a set of heavily cross linked HTML pages which document the
nitty-gritty details of each and every LilyPond class, object, and
function.  It is produced directly from the formatting definitions in
the source code.

   Almost all formatting functionality that is used internally is
available directly to the user.  For example, most variables that
control thickness values, distances, etc., can be changed in input
files.  There are a huge number of formatting options, and all of them
are described in this document.  Each section of the Notation Reference
has a See also subsection, which refers to the generated documentation.
In the HTML document, these subsections have clickable links.

Read it
-------

     *note Internals: (lilypond-internals)Top.: read this manual in the
     same format as this one.


All formats
-----------

   * Internals (split HTML) (../internals/index.html): the manual is
     split between many HTML pages.
     _(small download for each page)_

   * Internals (big HTML) (../internals-big-page.html): read this
     manual as one huge HTML page.
     _(large single download, 2.5 Mb)_

   * internals.pdf (../internals.pdf): download as a PDF file.
     _(large single download, 2.8 Mb)_



File: lilypond-web.info,  Node: Translated,  Next: All,  Prev: Internals,  Up: Manuals

Translated
==========

Translation status
------------------

TODO: clean up / prettify

   `../translations.html'.


File: lilypond-web.info,  Node: All,  Next: FDL,  Prev: Translated,  Up: Manuals

All
===

Documentation quick links
=========================

Links to other formats of these manuals can be found in *note Manuals::.

Introduction
------------

   * *note Top: (lilypond-learning)Top.: a "must-read" gentle
     introduction to LilyPond.

   * *note Glossary: (music-glossary)Top.: _(optional reading)_
     explains musical terms and gives translations for users unfamiliar
     with English musical terms.

   * *note Essay: (lilypond-essay)Top.: _(optional reading)_ background
     information about the engraving process and the aesthetics of 19th
     century music engraving.


Regular use
-----------

   * *note Notation: (lilypond-notation)Top.: the main portion of the
     documentation; provides detailed information about creating
     notation.

   * *note Usage: (lilypond-usage)Top.: discusses the actual programs
     and operation system-specific issues.

   * *note Snippets: (lilypond-snippets)Top.: short tricks, tips, and
     examples.


Infrequent Use
--------------

   * *note FAQ::: links to answers of Frequently Asked Questions.

   * *note Changes: (lilypond-changes)Top.: updates since the last
     major version.

   * *note Extend: (lilypond-extending)Top.: programming fancy tweaks
     in LilyPond.

   * *note Internals: (lilypond-internals)Top.: information about
     LilyPond's internal structures, which is required for constructing
     tweaks.


Downloadable versions
---------------------

   * html-split zip

   * html-big zip

   * pdf zip

   * info zip maybe?!?!


Previous stable versions
------------------------

   * LilyPond 2.12 Documentation
     (http://lilypond.org/doc/v2.12/Documentation/)

   * LilyPond 2.10 Documentation
     (http://lilypond.org/doc/v2.10/Documentation/)

   * LilyPond 2.8 Documentation
     (http://lilypond.org/doc/v2.8/Documentation/)



File: lilypond-web.info,  Node: FDL,  Prev: All,  Up: Manuals

FDL
===

Documentation license
---------------------

The documentation for GNU LilyPond is published under the GNU Free
Documentation License.  An introduction to this license, and our
reasons for choosing it, is given in *note Freedom::.

GNU Free Documentation License 1.1
----------------------------------

                     Version 1.3, 3 November 2008

     Copyright (C) 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc.
     `http://fsf.org/'

     Everyone is permitted to copy and distribute verbatim copies
     of this license document, but changing it is not allowed.

  0. PREAMBLE

     The purpose of this License is to make a manual, textbook, or other
     functional and useful document "free" in the sense of freedom: to
     assure everyone the effective freedom to copy and redistribute it,
     with or without modifying it, either commercially or
     noncommercially.  Secondarily, this License preserves for the
     author and publisher a way to get credit for their work, while not
     being considered responsible for modifications made by others.

     This License is a kind of "copyleft", which means that derivative
     works of the document must themselves be free in the same sense.
     It complements the GNU General Public License, which is a copyleft
     license designed for free software.

     We have designed this License in order to use it for manuals for
     free software, because free software needs free documentation: a
     free program should come with manuals providing the same freedoms
     that the software does.  But this License is not limited to
     software manuals; it can be used for any textual work, regardless
     of subject matter or whether it is published as a printed book.
     We recommend this License principally for works whose purpose is
     instruction or reference.

  1. APPLICABILITY AND DEFINITIONS

     This License applies to any manual or other work, in any medium,
     that contains a notice placed by the copyright holder saying it
     can be distributed under the terms of this License.  Such a notice
     grants a world-wide, royalty-free license, unlimited in duration,
     to use that work under the conditions stated herein.  The
     "Document", below, refers to any such manual or work.  Any member
     of the public is a licensee, and is addressed as "you".  You
     accept the license if you copy, modify or distribute the work in a
     way requiring permission under copyright law.

     A "Modified Version" of the Document means any work containing the
     Document or a portion of it, either copied verbatim, or with
     modifications and/or translated into another language.

     A "Secondary Section" is a named appendix or a front-matter section
     of the Document that deals exclusively with the relationship of the
     publishers or authors of the Document to the Document's overall
     subject (or to related matters) and contains nothing that could
     fall directly within that overall subject.  (Thus, if the Document
     is in part a textbook of mathematics, a Secondary Section may not
     explain any mathematics.)  The relationship could be a matter of
     historical connection with the subject or with related matters, or
     of legal, commercial, philosophical, ethical or political position
     regarding them.

     The "Invariant Sections" are certain Secondary Sections whose
     titles are designated, as being those of Invariant Sections, in
     the notice that says that the Document is released under this
     License.  If a section does not fit the above definition of
     Secondary then it is not allowed to be designated as Invariant.
     The Document may contain zero Invariant Sections.  If the Document
     does not identify any Invariant Sections then there are none.

     The "Cover Texts" are certain short passages of text that are
     listed, as Front-Cover Texts or Back-Cover Texts, in the notice
     that says that the Document is released under this License.  A
     Front-Cover Text may be at most 5 words, and a Back-Cover Text may
     be at most 25 words.

     A "Transparent" copy of the Document means a machine-readable copy,
     represented in a format whose specification is available to the
     general public, that is suitable for revising the document
     straightforwardly with generic text editors or (for images
     composed of pixels) generic paint programs or (for drawings) some
     widely available drawing editor, and that is suitable for input to
     text formatters or for automatic translation to a variety of
     formats suitable for input to text formatters.  A copy made in an
     otherwise Transparent file format whose markup, or absence of
     markup, has been arranged to thwart or discourage subsequent
     modification by readers is not Transparent.  An image format is
     not Transparent if used for any substantial amount of text.  A
     copy that is not "Transparent" is called "Opaque".

     Examples of suitable formats for Transparent copies include plain
     ASCII without markup, Texinfo input format, LaTeX input format,
     SGML or XML using a publicly available DTD, and
     standard-conforming simple HTML, PostScript or PDF designed for
     human modification.  Examples of transparent image formats include
     PNG, XCF and JPG.  Opaque formats include proprietary formats that
     can be read and edited only by proprietary word processors, SGML or
     XML for which the DTD and/or processing tools are not generally
     available, and the machine-generated HTML, PostScript or PDF
     produced by some word processors for output purposes only.

     The "Title Page" means, for a printed book, the title page itself,
     plus such following pages as are needed to hold, legibly, the
     material this License requires to appear in the title page.  For
     works in formats which do not have any title page as such, "Title
     Page" means the text near the most prominent appearance of the
     work's title, preceding the beginning of the body of the text.

     The "publisher" means any person or entity that distributes copies
     of the Document to the public.

     A section "Entitled XYZ" means a named subunit of the Document
     whose title either is precisely XYZ or contains XYZ in parentheses
     following text that translates XYZ in another language.  (Here XYZ
     stands for a specific section name mentioned below, such as
     "Acknowledgements", "Dedications", "Endorsements", or "History".)
     To "Preserve the Title" of such a section when you modify the
     Document means that it remains a section "Entitled XYZ" according
     to this definition.

     The Document may include Warranty Disclaimers next to the notice
     which states that this License applies to the Document.  These
     Warranty Disclaimers are considered to be included by reference in
     this License, but only as regards disclaiming warranties: any other
     implication that these Warranty Disclaimers may have is void and
     has no effect on the meaning of this License.

  2. VERBATIM COPYING

     You may copy and distribute the Document in any medium, either
     commercially or noncommercially, provided that this License, the
     copyright notices, and the license notice saying this License
     applies to the Document are reproduced in all copies, and that you
     add no other conditions whatsoever to those of this License.  You
     may not use technical measures to obstruct or control the reading
     or further copying of the copies you make or distribute.  However,
     you may accept compensation in exchange for copies.  If you
     distribute a large enough number of copies you must also follow
     the conditions in section 3.

     You may also lend copies, under the same conditions stated above,
     and you may publicly display copies.

  3. COPYING IN QUANTITY

     If you publish printed copies (or copies in media that commonly
     have printed covers) of the Document, numbering more than 100, and
     the Document's license notice requires Cover Texts, you must
     enclose the copies in covers that carry, clearly and legibly, all
     these Cover Texts: Front-Cover Texts on the front cover, and
     Back-Cover Texts on the back cover.  Both covers must also clearly
     and legibly identify you as the publisher of these copies.  The
     front cover must present the full title with all words of the
     title equally prominent and visible.  You may add other material
     on the covers in addition.  Copying with changes limited to the
     covers, as long as they preserve the title of the Document and
     satisfy these conditions, can be treated as verbatim copying in
     other respects.

     If the required texts for either cover are too voluminous to fit
     legibly, you should put the first ones listed (as many as fit
     reasonably) on the actual cover, and continue the rest onto
     adjacent pages.

     If you publish or distribute Opaque copies of the Document
     numbering more than 100, you must either include a
     machine-readable Transparent copy along with each Opaque copy, or
     state in or with each Opaque copy a computer-network location from
     which the general network-using public has access to download
     using public-standard network protocols a complete Transparent
     copy of the Document, free of added material.  If you use the
     latter option, you must take reasonably prudent steps, when you
     begin distribution of Opaque copies in quantity, to ensure that
     this Transparent copy will remain thus accessible at the stated
     location until at least one year after the last time you
     distribute an Opaque copy (directly or through your agents or
     retailers) of that edition to the public.

     It is requested, but not required, that you contact the authors of
     the Document well before redistributing any large number of
     copies, to give them a chance to provide you with an updated
     version of the Document.

  4. MODIFICATIONS

     You may copy and distribute a Modified Version of the Document
     under the conditions of sections 2 and 3 above, provided that you
     release the Modified Version under precisely this License, with
     the Modified Version filling the role of the Document, thus
     licensing distribution and modification of the Modified Version to
     whoever possesses a copy of it.  In addition, you must do these
     things in the Modified Version:

       A. Use in the Title Page (and on the covers, if any) a title
          distinct from that of the Document, and from those of
          previous versions (which should, if there were any, be listed
          in the History section of the Document).  You may use the
          same title as a previous version if the original publisher of
          that version gives permission.

       B. List on the Title Page, as authors, one or more persons or
          entities responsible for authorship of the modifications in
          the Modified Version, together with at least five of the
          principal authors of the Document (all of its principal
          authors, if it has fewer than five), unless they release you
          from this requirement.

       C. State on the Title page the name of the publisher of the
          Modified Version, as the publisher.

       D. Preserve all the copyright notices of the Document.

       E. Add an appropriate copyright notice for your modifications
          adjacent to the other copyright notices.

       F. Include, immediately after the copyright notices, a license
          notice giving the public permission to use the Modified
          Version under the terms of this License, in the form shown in
          the Addendum below.

       G. Preserve in that license notice the full lists of Invariant
          Sections and required Cover Texts given in the Document's
          license notice.

       H. Include an unaltered copy of this License.

       I. Preserve the section Entitled "History", Preserve its Title,
          and add to it an item stating at least the title, year, new
          authors, and publisher of the Modified Version as given on
          the Title Page.  If there is no section Entitled "History" in
          the Document, create one stating the title, year, authors,
          and publisher of the Document as given on its Title Page,
          then add an item describing the Modified Version as stated in
          the previous sentence.

       J. Preserve the network location, if any, given in the Document
          for public access to a Transparent copy of the Document, and
          likewise the network locations given in the Document for
          previous versions it was based on.  These may be placed in
          the "History" section.  You may omit a network location for a
          work that was published at least four years before the
          Document itself, or if the original publisher of the version
          it refers to gives permission.

       K. For any section Entitled "Acknowledgements" or "Dedications",
          Preserve the Title of the section, and preserve in the
          section all the substance and tone of each of the contributor
          acknowledgements and/or dedications given therein.

       L. Preserve all the Invariant Sections of the Document,
          unaltered in their text and in their titles.  Section numbers
          or the equivalent are not considered part of the section
          titles.

       M. Delete any section Entitled "Endorsements".  Such a section
          may not be included in the Modified Version.

       N. Do not retitle any existing section to be Entitled
          "Endorsements" or to conflict in title with any Invariant
          Section.

       O. Preserve any Warranty Disclaimers.

     If the Modified Version includes new front-matter sections or
     appendices that qualify as Secondary Sections and contain no
     material copied from the Document, you may at your option
     designate some or all of these sections as invariant.  To do this,
     add their titles to the list of Invariant Sections in the Modified
     Version's license notice.  These titles must be distinct from any
     other section titles.

     You may add a section Entitled "Endorsements", provided it contains
     nothing but endorsements of your Modified Version by various
     parties--for example, statements of peer review or that the text
     has been approved by an organization as the authoritative
     definition of a standard.

     You may add a passage of up to five words as a Front-Cover Text,
     and a passage of up to 25 words as a Back-Cover Text, to the end
     of the list of Cover Texts in the Modified Version.  Only one
     passage of Front-Cover Text and one of Back-Cover Text may be
     added by (or through arrangements made by) any one entity.  If the
     Document already includes a cover text for the same cover,
     previously added by you or by arrangement made by the same entity
     you are acting on behalf of, you may not add another; but you may
     replace the old one, on explicit permission from the previous
     publisher that added the old one.

     The author(s) and publisher(s) of the Document do not by this
     License give permission to use their names for publicity for or to
     assert or imply endorsement of any Modified Version.

  5. COMBINING DOCUMENTS

     You may combine the Document with other documents released under
     this License, under the terms defined in section 4 above for
     modified versions, provided that you include in the combination
     all of the Invariant Sections of all of the original documents,
     unmodified, and list them all as Invariant Sections of your
     combined work in its license notice, and that you preserve all
     their Warranty Disclaimers.

     The combined work need only contain one copy of this License, and
     multiple identical Invariant Sections may be replaced with a single
     copy.  If there are multiple Invariant Sections with the same name
     but different contents, make the title of each such section unique
     by adding at the end of it, in parentheses, the name of the
     original author or publisher of that section if known, or else a
     unique number.  Make the same adjustment to the section titles in
     the list of Invariant Sections in the license notice of the
     combined work.

     In the combination, you must combine any sections Entitled
     "History" in the various original documents, forming one section
     Entitled "History"; likewise combine any sections Entitled
     "Acknowledgements", and any sections Entitled "Dedications".  You
     must delete all sections Entitled "Endorsements."

  6. COLLECTIONS OF DOCUMENTS

     You may make a collection consisting of the Document and other
     documents released under this License, and replace the individual
     copies of this License in the various documents with a single copy
     that is included in the collection, provided that you follow the
     rules of this License for verbatim copying of each of the
     documents in all other respects.

     You may extract a single document from such a collection, and
     distribute it individually under this License, provided you insert
     a copy of this License into the extracted document, and follow
     this License in all other respects regarding verbatim copying of
     that document.

  7. AGGREGATION WITH INDEPENDENT WORKS

     A compilation of the Document or its derivatives with other
     separate and independent documents or works, in or on a volume of
     a storage or distribution medium, is called an "aggregate" if the
     copyright resulting from the compilation is not used to limit the
     legal rights of the compilation's users beyond what the individual
     works permit.  When the Document is included in an aggregate, this
     License does not apply to the other works in the aggregate which
     are not themselves derivative works of the Document.

     If the Cover Text requirement of section 3 is applicable to these
     copies of the Document, then if the Document is less than one half
     of the entire aggregate, the Document's Cover Texts may be placed
     on covers that bracket the Document within the aggregate, or the
     electronic equivalent of covers if the Document is in electronic
     form.  Otherwise they must appear on printed covers that bracket
     the whole aggregate.

  8. TRANSLATION

     Translation is considered a kind of modification, so you may
     distribute translations of the Document under the terms of section
     4.  Replacing Invariant Sections with translations requires special
     permission from their copyright holders, but you may include
     translations of some or all Invariant Sections in addition to the
     original versions of these Invariant Sections.  You may include a
     translation of this License, and all the license notices in the
     Document, and any Warranty Disclaimers, provided that you also
     include the original English version of this License and the
     original versions of those notices and disclaimers.  In case of a
     disagreement between the translation and the original version of
     this License or a notice or disclaimer, the original version will
     prevail.

     If a section in the Document is Entitled "Acknowledgements",
     "Dedications", or "History", the requirement (section 4) to
     Preserve its Title (section 1) will typically require changing the
     actual title.

  9. TERMINATION

     You may not copy, modify, sublicense, or distribute the Document
     except as expressly provided under this License.  Any attempt
     otherwise to copy, modify, sublicense, or distribute it is void,
     and will automatically terminate your rights under this License.

     However, if you cease all violation of this License, then your
     license from a particular copyright holder is reinstated (a)
     provisionally, unless and until the copyright holder explicitly
     and finally terminates your license, and (b) permanently, if the
     copyright holder fails to notify you of the violation by some
     reasonable means prior to 60 days after the cessation.

     Moreover, your license from a particular copyright holder is
     reinstated permanently if the copyright holder notifies you of the
     violation by some reasonable means, this is the first time you have
     received notice of violation of this License (for any work) from
     that copyright holder, and you cure the violation prior to 30 days
     after your receipt of the notice.

     Termination of your rights under this section does not terminate
     the licenses of parties who have received copies or rights from
     you under this License.  If your rights have been terminated and
     not permanently reinstated, receipt of a copy of some or all of
     the same material does not give you any rights to use it.

 10. FUTURE REVISIONS OF THIS LICENSE

     The Free Software Foundation may publish new, revised versions of
     the GNU Free Documentation License from time to time.  Such new
     versions will be similar in spirit to the present version, but may
     differ in detail to address new problems or concerns.  See
     `http://www.gnu.org/copyleft/'.

     Each version of the License is given a distinguishing version
     number.  If the Document specifies that a particular numbered
     version of this License "or any later version" applies to it, you
     have the option of following the terms and conditions either of
     that specified version or of any later version that has been
     published (not as a draft) by the Free Software Foundation.  If
     the Document does not specify a version number of this License,
     you may choose any version ever published (not as a draft) by the
     Free Software Foundation.  If the Document specifies that a proxy
     can decide which future versions of this License can be used, that
     proxy's public statement of acceptance of a version permanently
     authorizes you to choose that version for the Document.

 11. RELICENSING

     "Massive Multiauthor Collaboration Site" (or "MMC Site") means any
     World Wide Web server that publishes copyrightable works and also
     provides prominent facilities for anybody to edit those works.  A
     public wiki that anybody can edit is an example of such a server.
     A "Massive Multiauthor Collaboration" (or "MMC") contained in the
     site means any set of copyrightable works thus published on the MMC
     site.

     "CC-BY-SA" means the Creative Commons Attribution-Share Alike 3.0
     license published by Creative Commons Corporation, a not-for-profit
     corporation with a principal place of business in San Francisco,
     California, as well as future copyleft versions of that license
     published by that same organization.

     "Incorporate" means to publish or republish a Document, in whole or
     in part, as part of another Document.

     An MMC is "eligible for relicensing" if it is licensed under this
     License, and if all works that were first published under this
     License somewhere other than this MMC, and subsequently
     incorporated in whole or in part into the MMC, (1) had no cover
     texts or invariant sections, and (2) were thus incorporated prior
     to November 1, 2008.

     The operator of an MMC Site may republish an MMC contained in the
     site under CC-BY-SA on the same site at any time before August 1,
     2009, provided the MMC is eligible for relicensing.


ADDENDUM: How to use this License for your documents
====================================================

To use this License in a document you have written, include a copy of
the License in the document and put the following copyright and license
notices just after the title page:

       Copyright (C)  YEAR  YOUR NAME.
       Permission is granted to copy, distribute and/or modify this document
       under the terms of the GNU Free Documentation License, Version 1.3
       or any later version published by the Free Software Foundation;
       with no Invariant Sections, no Front-Cover Texts, and no Back-Cover
       Texts.  A copy of the license is included in the section entitled ``GNU
       Free Documentation License''.

   If you have Invariant Sections, Front-Cover Texts and Back-Cover
Texts, replace the "with...Texts." line with this:

         with the Invariant Sections being LIST THEIR TITLES, with
         the Front-Cover Texts being LIST, and with the Back-Cover Texts
         being LIST.

   If you have Invariant Sections without Cover Texts, or some other
combination of the three, merge those two alternatives to suit the
situation.

   If your document contains nontrivial examples of program code, we
recommend releasing these examples in parallel under your choice of
free software license, such as the GNU General Public License, to
permit their use in free software.


File: lilypond-web.info,  Node: Community,  Prev: Manuals,  Up: Top

Community
*********

Interacting with the community
------------------------------

   * *note Contact::: get help, discuss, and keep in touch!

   * *note Tiny examples::: these are _highly_ recommended when
     discussing LilyPond.

   * *note Bug reports::: something went wrong.


Making LilyPond better
----------------------

   * *note Help us::: your assistance is requested.

   * *note Development::: for contributors and testers.

   * *note Authors::: the people who made LilyPond what it is today.


Miscellaneous
-------------

   * *note Publications::: what we wrote, and have had written about us.

   * *note Old news::: an archive.


* Menu:

* Contact::
* Tiny examples::
* Bug reports::
* Help us::
* Development::
* Authors::
* Publications::
* Old news::


File: lilypond-web.info,  Node: Contact,  Next: Tiny examples,  Up: Community

Contact
=======

User Discussions and Help
-------------------------

User mailing list: `lilypond-user@gnu.org'
..........................................

This mailing list is the main place for users to discuss and help each
other.

     lilypond-user subscribe and info
     (http://mail.gnu.org/mailman/listinfo/lilypond-user)

     user archive1 (http://mail.gnu.org/archive/html/lilypond-user/)
     archive2 (http://www.mail-archive.com/lilypond-user@gnu.org/)
     archive3 (http://dir.gmane.org/gmane.comp.gnu.lilypond.general)

     send to lilypond-user with gmane
     (http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.general)

          Note: When asking questions, please use *note Tiny examples::!

IRC
...

Some level of support is provided on our IRC channel,

     #lilypond@irc.freenode.net (irc://irc.freenode.net/lilypond)

   This channel has no public archive, so any question that may be
useful for others would better be posted to one of the mailing lists.

Other languages
...............

     Spanish yahoo group (http://es.groups.yahoo.com/group/lilypond-es)

     German forum (http://www.lilypondforum.de/)

     Portugese group (http://groups.google.com/group/lilypond-brasil)

     French mailing list
     (http://lists.gnu.org/mailman/listinfo/lilypond-user-fr)

     Dutch forum (http://www.lilypondforum.nl/)

Stay Informed
-------------

LilyPond Report
...............

The easiest way to keep touch is by reading our community newsletter,
the LilyPond Report (http://news.lilynet.net/).

Releases mailing list: `info-lilypond@gnu.org'
..............................................

This mailing list is a low-volume, read-only list which receives
notifications of new releases.

     info-lilypond subscribe and info
     (http://lists.gnu.org/mailman/listinfo/info-lilypond)

     info archive1 (http://mail.gnu.org/archive/html/info-lilypond/)
     archive2 (http://www.mail-archive.com/info-lilypond@gnu.org/)
     archive3 (http://dir.gmane.org/gmane.comp.gnu.lilypond.announce)


Developer Discussion
--------------------

Developer mailing list: `lilypond-devel@gnu.org'
................................................

Most developer discussion takes place on this list.  Patches should be
sent here.

     lilypond-devel subscribe and info
     (http://mail.gnu.org/mailman/listinfo/lilypond-devel)

     devel archive1 (http://mail.gnu.org/archive/html/lilypond-devel/)
     archive2 (http://www.mail-archive.com/lilypond-devel@gnu.org/)
     archive3 (http://dir.gmane.org/gmane.comp.gnu.lilypond.devel)

     send to lilypond-devel with gmane
     (http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.devel)

Bug mailing list: `bug-lilypond@gnu.org'
........................................

Bug-specific discussion takes place here.

     bug-lilypond subscribe and info
     (http://mail.gnu.org/mailman/listinfo/bug-lilypond)

     bug archive1 (http://mail.gnu.org/archive/html/bug-lilypond/)
     archive2 (http://www.mail-archive.com/bug-lilypond@gnu.org/)
     archive3 (http://dir.gmane.org/gmane.comp.gnu.lilypond.bugs)


          Note: Before sending a message to the bug list, please read
          our guidelines for *note Bug reports::.


File: lilypond-web.info,  Node: Tiny examples,  Next: Bug reports,  Prev: Contact,  Up: Community

Tiny examples
=============

What are "Tiny examples"?
-------------------------

A tiny example is an example from which nothing can be removed.

Why create them?
----------------

   * The simpler the example is, the quicker potential helpers can
     understand it and help you.

   * A simple example demonstrates that you have put effort towards
     solving the problem yourself.  When people send huge portions of
     input, it looks like they don't care how if we help them or not.

   * Creating a tiny example forces you to understand what is
     happening.  Many false problem reports can be avoided by
     attempting to create a tiny example; if you cannot replicate a
     "bug" in a tiny example, then the problem was probably an
     insufficient understanding of LilyPond, not an actual bug!


How do I create them?
---------------------

   * Include the \version number.

   * Make it small!  Examples about spacing or page layout might
     require many bars of music, but most issues can be reproduced
     using only a single measure.

   * When trying to create an example, try commenting out
     (`%' or `%{ ... %}') sections of your file.  If you can comment
     something while still demonstrating the main idea, then remove the
     commented-material!

   * Avoid using complicated notes, keys, or time signatures, unless
     the bug is about the behavior of those items.

   * Do not use `\override' or `\set' commands unless the bug is about
     those particular commands.



File: lilypond-web.info,  Node: Bug reports,  Next: Help us,  Prev: Tiny examples,  Up: Community

Bug reports
===========

Step 1: Known bugs
------------------

If you have input that results in a crash or an erroneous output, then
that is a bug.  There is a list of current bugs on our google bug
tracker,

     `http://code.google.com/p/lilypond/issues/list'

          Note: Please *DO NOT* add bug reports directly to the bug
          tracker.  Once an issue has been added to the tracker, feel
          free to add more information to that report.

Step 2: Creating a bug report
-----------------------------

If you have discovered a bug which is not listed, please help us by
creating a bug report.

          Note: We only accept bug reports in the form of *note Tiny
          examples::.  We have very limited resources to deal with bug
          reports, so any non-minimal example will be rejected.  Almost
          every bug can be demonstrated in four notes or less!

   Here is an example of a good bug report:

     %% the octavation command doesn't
     %% change the output at all!

     \version "2.10.0"
     \paper{ ragged-right=##t }
     \relative c''' {
       c1
       #(set-octavation 1)
       c1
     }

Step 3: Sending a bug report
----------------------------

Once you have verified that the issue is not already known and created
a bug report, please send it to us!

   Unfortunately there is a strict "no top-posting" check on the bug
list, which is often incorrectly triggered by lilypond files.  To avoid
this, please add

     > I'm not top posting.

(you must include the `>' ) to the top of your bug report.

   Post with the gmane lilypond.bugs interface
(http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.bugs), or
send an email to bug-lilypond@gnu.org (mailto:bug-lilypond@gnu.prg).

   Once your bug has been sent to the list, our Bug Meister will
examine the report.  He may ask you for more information, or may add
the report to the tracker and let you know what the issue number is.

   You may mark the bug so that you automatically receive emails when
any activity on the bug occurs.  This requires you have a google
account.


File: lilypond-web.info,  Node: Help us,  Next: Development,  Prev: Bug reports,  Up: Community

Help us
=======

We need you!
------------

The LilyPond development team is quite small; we really want to get
more people involved.  Please consider helping your fellow LilyPond
users by contributing to development!

   Even working on small tasks can have a big impact: taking care of
them let experienced developers work on advanced tasks, instead of
spending time on those simple tasks.

Simple tasks
------------

   * Mailing list support: answer questions from fellow users.

   * Bug reporting: help users create proper *note Bug reports::, and
     aid the Bug Team in handling *note Issues:
     (lilypond-contributor)Issues.

   * Documentation: small changes can be proposed by following the
     guidelines for *note Documentation suggestions:
     (lilypond-contributor)Documentation suggestions.

   * LilyPond Snippet Repository (LSR): create and fix snippets.  See *note
     Adding and editing snippets: (lilypond-contributor)Adding and
     editing snippets.

   * Discussions, reviews, and testing: the developers often ask for
     feedback about new documentation, potential syntax changes, and
     testing new features.  Please contribute to these discussions!


Moderate tasks
--------------

          Note: These jobs generally require that you have the program
          and documentation source files, but do not require a full
          development environment.  See *note Starting with git:
          (lilypond-contributor)Starting with git.

   * Documentation: see *note Documentation work:
     (lilypond-contributor)Documentation work, and *note Building
     documentation without compiling LilyPond:
     (lilypond-contributor)Building documentation without compiling
     LilyPond.

   * Website: the website is built from the normal documentation
     source.  See the info about documentation, and also *note Website
     work: (lilypond-contributor)Website work.

   * Translations: see *note Translating the documentation:
     (lilypond-contributor)Translating the documentation, and *note
     Translating the website: (lilypond-contributor)Translating the
     website.


Complex tasks
-------------

          Note: These jobs generally require that you have the source
          code and can compile LilyPond.  See *note Starting with git:
          (lilypond-contributor)Starting with git, and *note Compiling
          LilyPond: (lilypond-contributor)Compiling LilyPond.

We suggest that new contributors using Windows use a virtual machine to
run _lilybuntu_.  See *note Using a Virtual Machine to Compile
LilyPond: (lilypond-contributor)Using a Virtual Machine to Compile
LilyPond.

   * Bugfixes, new features: the best way to begin is to join the
     Frogs, and read *note Programming work:
     (lilypond-contributor)Programming work.


Projects
--------

Frogs
.....

Website and mailist: `http://frogs.lilynet.net'

   The Frogs are ordinary LilyPond users who have chosen to get
involved in their favorite software's development.  Fixing bugs,
implementing new features, documenting the source code: there's a lot
to be done, but most importantly: this is a chance for everyone to
learn more about LilyPond, about Free Software, about programming...
and to have fun.  If you're curious about any of it, then the word is:
_Join the Frogs!_

Grand LilyPond Input Syntax Standardization
...........................................

Website and mailist: TODO

   GLISS will stabilize the (non-tweak) input syntax for the upcoming
LilyPond 3.0.  After updating to 3.0, the input syntax for untweaked
music will remain stable for the foreseeable future.

   We will have an extensive discussion period to determine the final
input specification.

Grand Organizing Project
........................

Website and mailist: TODO

   GOP is our big recruiting drive for new contributors.


File: lilypond-web.info,  Node: Development,  Next: Authors,  Prev: Help us,  Up: Community

Development
===========

Development materials for LilyPond 2.13.9
=========================================

          Note: These are _unstable development_ versions.  If you have
          the slightest doubt about how to use or install LilyPond, we
          urge you to use the stable *note Download::, and read the
          stable *note Manuals::.

Release numbers
---------------

There are two sets of releases for LilyPond: stable releases, and
unstable development releases.  Stable versions have an even-numbered
`minor' version number (e.g., 2.8, 2.10, 2.12).  Development versions
have an odd-numbered `minor' version number (e.g., 2.7, 2.9, 2.11).

Download
--------

Instructions for git and compiling are in the Contributor's Guide.

     lilypond git repository
     (http://git.sv.gnu.org/gitweb/?p=lilypond.git)

   Documentation writers and testers will generally want to download
the latest binary:

     Linux x86: LilyPond 2.13.9-1
     (http://download.linuxaudio.org/lilypond/binaries/linux-x86/lilypond-2.13.9-1.linux-x86.sh)

     Linux 64: LilyPond 2.13.9-1
     (http://download.linuxaudio.org/lilypond/binaries/linux-64/lilypond-2.13.9-1.linux-64.sh)

     Linux PPC: LilyPond 2.13.9-1
     (http://download.linuxaudio.org/lilypond/binaries/linux-ppc/lilypond-2.13.9-1.linux-ppc.sh)

     FreeBSD i386: LilyPond 2.13.9-1
     (http://download.linuxaudio.org/lilypond/binaries/freebsd-x86/lilypond-2.13.9-1.freebsd-x86.sh)

     FreeBSD amd64: LilyPond 2.13.9-1
     (http://download.linuxaudio.org/lilypond/binaries/freebsd-x86/lilypond-2.13.9-1.freebsd-64.sh)

     MacOS X x86: LilyPond 2.13.9-1
     (http://download.linuxaudio.org/lilypond/binaries/darwin-x86/lilypond-2.13.9-1.darwin-x86.tar.bz2)

     MacOS X PPC: LilyPond 2.13.9-1
     (http://download.linuxaudio.org/lilypond/binaries/darwin-ppc/lilypond-2.13.9-1.darwin-ppc.tar.bz2)

     Windows: LilyPond 2.13.9-1
     (http://download.linuxaudio.org/lilypond/binaries/mingw/lilypond-2.13.9-1.mingw.exe)

     lilypond-2.13.9.tar.gz
     (http://download.linuxaudio.org/lilypond/sources/v2.13/lilypond-2.13.9.tar.gz)


Manuals
-------

Commented out pending a real fix

Contributor's Guide
-------------------

LilyPond development is a fairly complicated matter.  LilyPond is a
large, (mostly) stable project.  In order to help new contributors, and
to keep the whole system (mostly) stable, we have written a manual for
contributors.

   This manual is not intended to be read sequentially; new contributors
should only read the sections which are relevant to them.  For more
information about different jobs, see *note Help us::.

   * Contributor's guide (split HTML) (../contributor/index.html): the
     manual is split between many HTML pages.
     _(small download for each page)_

   * Contributor's guide (big HTML) (../contributor-big-page.html):
     read this manual as one huge HTML page.
     _(large single download, 500 kb)_

   * contributor.pdf (../contributor.pdf): download as a PDF file.
     _(large single download, 2.8 Mb)_


Frogs: new contributors
-----------------------

The Frogs are a collection of new contributors being mentored in how to
"eat" (fix) bugs and add new features to LilyPond.  Programmers
unfamiliar with LilyPond are encouraged to send patches to the Frogs
first for initial discussion and encouragement.

   Website and mailist: `http://frogs.lilynet.net'

Regression tests
----------------

   * Regression tests (../../input/regression/collated-files.html):
     This release's tests.  (also in pdf
     (../input/regression/collated-files.pdf))

   * MusicXML Regression tests
     (../../input/regression/musicxml/collated-files.html): This
     release's MusicXML tests.  (also in pdf
     (../input/regression/musicxml/collated-files.pdf))

   * Archive of regression tests (http://lilypond.org/test):
     Comparisons between versions.



File: lilypond-web.info,  Node: Authors,  Next: Publications,  Prev: Development,  Up: Community

Authors
=======

Current Development Team
------------------------

   * Mats Bengtsson: <mats.bengtsson@ee.kth.se>,
     `http://www.s3.kth.se/~mabe/', Support guru

   * Trevor Daniels: Assistant documentation editor

   * John Mandereau: <john.mandereau@free.fr>, Translation meister

   * Patrick McCarty: Core developer

   * Joe Neeman: Core developer

   * Han-Wen Nienhuys: <hanwen@xs4all.nl>,
     `http://www.xs4all.nl/~hanwen/', Main author

   * Jan Nieuwenhuizen: <janneke@gnu.org>,
     `http://www.xs4all.nl/~jantien/', Main author

   * Graham Percival: `http://percival-music.ca', Project manager,
     Documentation Editor

   * Nicolas Sceaux: Core developer

   * Carl Sorensen: <c_sorensen@byu.edu>, Core developer, Frog meister

   * Valentin Villenave: LSR editor and Bug meister


Previous Development Team Positions
-----------------------------------

   * Pedro Kroeger: Build meister

   * Graham Percival: `http://percival-music.ca', Bug meister, Grand
     Documentation Project leader

   * Erik Sandberg: Bug meister


Current Contributors
--------------------

Programming
...........

   * Frédéric Bron: Frog

   * Hajo Dezelski: Frog

   * Andrew Hawryluk: Frog

   * Ian Hulin: Frog

   * Marek Klein: Frog

   * Kieren MacMillan: Frog

   * Andrew Wilson: Frog


Font
....

Documentation
.............

   * Jonathan Kulp: Clean-ups in documentation

   * James Lowe: Minor editing

   * Ralph Palmer: Documentation indexing

   * Patrick Schmidt: CSS improvements


Support
.......

   * James E. Bailey: Bug meister


Translation
...........

   * Jean-Charles Malahieude: <lolyfan@wanadoo.fr>, French translation
     of messages, website and documentation

   * Till Rettig: German translation

   * Yoshiki Sawada: Japanese translation

   * Francisco Vila: Spanish translation


Previous Contributors
---------------------

Programming
...........

   * Erlend Aasland: Color support, tablature improvements, trivial
     `\mark' stuff, al-niente hairpins

   * Maximilian Albert:

   * Guido Amoruso:

   * Kristof Bastiaensen:

   * Pal Benko: <benkop@freestart.hu>, Ancient notation

   * Juliusz Chroboczek: <jch@pps.jussieu.fr>, Type42 code

   * Angelo Contardi:

   * David Feuer: <david.feuer@gmail.com>, PS output code refactoring

   * Bertalan Fodor:

   * Mathieu Giraud:

   * Yuval Harel:

   * Christian Hitz:

   * Bernard Hurley: <bernard@fong-hurley.org.uk>, X11 color

   * Yoshinobu Ishizaki:

   * Chris Jackson: <chris@fluffhouse.org.uk>, Piano pedals, directed
     arpeggios

   * David Jedlinsky:

   * Heikki Junes: <heikki.junes@hut.fi>, Fine tuning for quarter tones
     in midi output

   * Reinhold Kainhofer: <reinhold@kainhofer.com>,
     `http://reinhold.kainhofer.com', Musicxml2ly development, various
     features and fixes

   * Michael Krause: <m.krause@tu-harburg.de>, Breathing signs

   * Jean-Baptiste Lamy: <jiba@tuxfamily.org>, Tablature support

   * Werner Lemberg: <wl@gnu.org>, TeX glue code

   * Jonatan Liljedahl:

   * Peter Lutek:

   * Hendrik Maryns:

   * Joe Neeman: <joeneeman@gmail.com>, Constrained line breaking

   * Matthias Neeracher:

   * Han-Wen Nienhuys: <hanwen@xs4all.nl>,
     `http://www.xs4all.nl/~hanwen/', Main author

   * Jan Nieuwenhuizen: <janneke@gnu.org>,
     `http://www.xs4all.nl/~jantien/', Main author

   * Tatsuya Ono:

   * Lisa Opus Goldstein:

   * Guy Gascoigne-Piggford:

   * Niel Puttock:

   * Jürgen Reuter: <reuter_j@web.de>, `http://www.juergen-reuter.de',
     Ancient notation support (Mensural and Gregorian chant) ambitus,
     clusters

   * Stan Sanderson: Regression Checker

   * Erik Sandberg:

   * Edward Sanford Sutton:

   * Nicolas Sceaux: <nicolas.sceaux@free.fr>, Scheme macros, `\markup'
     syntax

   * Andreas Scherer:

   * Johannes Schindelin:

   * Kim Shrier:

   * Vicente Solsona Della:

   * David Svoboda:

   * Sebastiano Vigna:

   * Arno Waschk:

   * Michael Welsh Duggan:

   * John Williams:

   * Milan Zamazal:

   * Carl Sorensen: <c_sorensen@byu.edu>, Fret diagrams

   * Rune Zedeler: Auto-accidental code, zigzag glissandi, rest
     bugfixes, minimum fret, `subdivideBeams'.


Font
....

   * Tom Cato Amundsen: <tca@gnu.org>, Accordion symbols

   * Chris Jackson: <chris@fluffhouse.org.uk>, Arpeggio arrow

   * Han-Wen Nienhuys: <hanwen@xs4all.nl>,
     `http://www.xs4all.nl/~hanwen/', Main author

   * Jan Nieuwenhuizen: <janneke@gnu.org>,
     `http://www.xs4all.nl/~jantien/', Main author

   * Jürgen Reuter: <reuter_j@web.de>, `http://www.juergen-reuter.de',
     Ancient notation font Exact Type1 font outlines for feta,
     feta-alphabet

   * Arno Waschk: <arno@arnowaschk.de>, "Espressivo" mark

   * Rune Zedeler: 16th and shorter rests


Documentation
.............

   * Erlend Aasland:

   * Trevor Bača: Inspirational headwords

   * Alard de Boer: Formatting

   * Mats Bengtsson: <mats.bengtsson@ee.kth.se>,
     `http://www.s3.kth.se/~mabe/', Example files, documentation

   * Jay Hamilton: NR work

   * Andrew Hawryluk: NR work

   * Joseph Harfouch: NR work

   * Cameron Horsburgh: Formatting and editing

   * Geoff Horton: Formatting and editing

   * Heikki Junes: <heikki.junes@hut.fi>, Clean-ups in documentation
     and example files

   * Reinhold Kainhofer: Technical aid

   * Kurt Kroon: Glossary, updates and NR work

   * Jonathan Kulp: Clean-ups in documentation

   * Dave Luttinen: Formatting and editing

   * Patrick McCarty: NR work

   * John Mandereau: <john.mandereau@free.fr>, Internationalization

   * Christian Mondrup: <scancm@biobase.dk>, Glossary

   * Han-Wen Nienhuys: <hanwen@xs4all.nl>,
     `http://www.xs4all.nl/~hanwen/', Main author

   * Jan Nieuwenhuizen: <janneke@gnu.org>,
     `http://www.xs4all.nl/~jantien/', Main author

   * Eyolf Østrem: NR work

   * Ralph Palmer: Documentation indexing

   * François Pinard: <pinard@iro.umontreal.ca>,
     `http://pinard.progiciels-bpi.ca/', Parts of
     Documentation/user/glossary*, started internationalization stuff

   * Niel Puttock: Snippet editor and technical aid

   * Eduardo Vieira: NR work

   * Francisco Vila: NR work

   * Michael Rasmussen: Formatting

   * Till Rettig: NR work

   * Carl Sorensen: NR work

   * Rune Zedeler: Schumann example


Support
.......

   * Anthony Fok: <foka@debian.org>, Debian package: `debian/*'

   * Chris Jackson: <chris@fluffhouse.org.uk>, Emacs mode indentation

   * Heikki Junes: <heikki.junes@hut.fi>, Major emacs and vim-mode
     updates

   * David Svoboda: <svoboda@cmu.edu>, What-beat emacs module


Translation
...........

   * Frédéric Chiasson: French documentation translation

   * Abel Cheung:

   * David González: Spanish glossary translation

   * Nicolas Grandclaude: <ngclaude@123mail.org>, French documentation
     translation

   * Damien Heurtebise:

   * Matthieu Jacquot:

   * Bjoern Jacke: <bjoern.jacke@gmx.de>, German glossary translation

   * Neil Jerram: <nj104@cus.cam.ac.uk>, Glossary translation

   * Heikki Junes: <heikki.junes@hut.fi>, Finnish translation

   * Nicolas Klutchnikoff:

   * Tineke de Munnik: <tdm@dds.nl>, Dutch website translation

   * Jean-Charles Malahieude: <lolyfan@wanadoo.fr>, French translation
     of messages, website and documentation

   * John Mandereau: <john.mandereau@free.fr>, French translation of
     messages, website and documentation

   * Tineke de Munnik: <tdm@dds.nl>, Dutch website translation

   * Steven Michael Murphy:

   * Gauvain Pocentek: <gauvainpocentek@yahoo.fr>, French website
     translation

   * Till Rettig: German translation

   * Ludovic Sardain: <ludovicsardain@gmail.com>, French documentation
     translation

   * Yoshiki Sawada: Japanese translation

   * Clytie Siddall:

   * August S. Sigov: <august@infran.ru>, Russian translation

   * Roland Stigge:

   * Francisco Vila: Spanish translation

   * Olcay Yıldırım:



File: lilypond-web.info,  Node: Publications,  Next: Old news,  Prev: Authors,  Up: Community

Publications
============

What we wrote
-------------

   * Han-Wen Nienhuys, _LilyPond, Automated music formatting and the
     Art of Shipping_.  Forum Internacional Software Livre 2006
     (FISL7.0) (PDF 1095k
     (http://lilypond.org/web/images/FISL7-slides.pdf))

   * Erik Sandberg, _Separating input language and formatter in GNU
     Lilypond_. Master's Thesis, Uppsala University, Department of
     Information Technology March 2006.  (PDF 750k
     (http://lilypond.org/web/images/thesis-erik-sandberg.pdf))

   * Han-Wen Nienhuys and Jan Nieuwenhuizen, _LilyPond, a system for
     automated music engraving_.  Proceedings of the XIV Colloquium on
     Musical Informatics (XIV CIM 2003), Firenze, Italy, May 2003.
     (PDF 95k (http://lilypond.org/web/images/xivcim.pdf))


What others wrote
-----------------

   * September 2009

     The German LinuxUser magazine wrote an article about lilypond
     (http://www.linux-community.de/Internal/Artikel/Print-Artikel/LinuxUser/2009/10/Digitaler-Notenschluessel).

   * February 2008

     In articles on his personal site
     (http://www.musicbyandrew.ca/finale-lilypond-1.html), Andrew
     Hawryluk compares Finale and LilyPond in general terms, and
     evaluates in detail engraving capabilities of both pieces of
     software.  The second article is an instructive analysis of
     Rachmaninoff's Piano Prelude 6 engraving, including comparisons
     with a reference hand-engraved edition.

   * December 2005

     Linux journal cover Linux Journal publishes an article titled Make
     Stunning Schenker Graphs with GNU LilyPond
     (http://www.linuxjournal.com/article/8364).  It is a in-depth but
     hands-on feature article with crisp LilyPond graphics.  Author
     Kris Shaffer remarks “GNU Lilypond generates beautiful graphics
     that make commercial alternatives seem second-rate.”

   * August 20, 2005

     The Belgian newspaper De Standaard investigates what drives Free
     Software authors in an article titled Delen van KENNIS zonder
     WINSTBEJAG
     (http://www.standaard.be/Artikel/Detail.aspx?artikelId=G42H5GD6)
     (Non-profit sharing of knowlegde) in its `DS2 bijlage'.  LilyPond
     is used as an example and the article is interspersed with quotes
     from an `email interview' with Jan Nieuwenhuizen. This marks
     LilyPond's first appearance in mainstream printed press.

   * June 2005

     A French article on the LilyPond 2.6 release appeared on
     linuxfr.org (http://linuxfr.org/2005/06/27/19210.html).

   * October 2004

     The editors of Computer!Totaal, a Dutch computer magazine,
     describe LilyPond
     (http://lilypond.org/web/images/computer-totaal.jpeg) in the
     October 2004 issue as: "Wonderful free (open source) software [..]
     The sheet music produced by LilyPond is exceptionally pretty [..]
     a very powerful system that can do almost anything."

   * July, August 2004

     Dave Phillips wrote an introductory article for Linux Journal At
     the sounding edge: LilyPond, parts one
     (http://www.linuxjournal.com/article/7657) and two
     (http://www.linuxjournal.com/article/7719).

   * March 2004

     Chris Cannam interviewed Han-Wen Nienhuys and Jan Nieuwenhuizen on
     linuxmusician.com (site now defunct). This interview was also
     reviewed in a slashdot story
     (http://slashdot.org/article.pl?sid=04/03/13/2054227&tid=).

   * February 2004

     Jazz singer Gail Selkirk writes about Diving into LilyPond
     (http://www.songbirdofswing.com/editorial_page/lilypond/).  "...
     you can make lead sheets or full orchestral parts, and the results
     can be stunning."  Computer Music Special
     (http://www.computermusic.co.uk/), issue CMS06.



File: lilypond-web.info,  Node: Old news,  Prev: Publications,  Up: Community

Old news
========

New Website!  _October 3, 2009_
...............................

As you can see, we have a new website design.  Many thanks to texi2html
and CSS for being so flexible!

LilyPond Report #16.  _September 6, 2009_
.........................................

The LilyPond Report is back! This short, informal opinion column is
about the LilyPond project: its team, its world, its community.  Read
issue 16 (http://news.lilynet.net/The-LilyPond-Report-16) now!

LilyPond 2.13.3.  _July 2, 2009_
................................

This unstable release contains working menus in OSX 10.5; many thanks
to Christian Hitz for fixing this long-standing problem!  This release
also contains numerous other bugfixes and features such as ties with
variable thickness, partially dashed slurs, and eyeglasses.
We are planning another 2.12 release in the next week or two, which
will include the menu fixes for OSX 10.5.  Normal users may wish to
wait for this release rather than using an unstable release.
*note Changes::, *note Development::.

A LilyPond weboldala magyarul.  _May 22, 2009_
..............................................

Elkészült a lilypond.org nagy részének magyar fordítása a LilyPond
honosítási projekt első lépéseként. A projekt célja a LilyPond
szabad kottaszedő szoftver minél széleskörűbben elérhetővé
tétele a magyar felhasználók számára a teljes weboldal és
dokumentáció lefordítása révén. A teljes dokumentáció
lefordításához közreműködőket keresünk. Ha részt vennél a
honosításban, küldj egy e-mailt a `harmathdenes AT gmail.com' címre!
<p align="right">Harmath Dénes, a LilyPond honosítási projekt
vezetője

The LilyPond Report #15.  _May 18, 2009_
........................................

The _LilyPond Report_ is a short, informal opinion column about the
LilyPond project: its team, its world, its community.  Follow this link
(http://news.lilynet.net/The-LilyPond-Report-15) to read the full
issue...

The LilyPond Report #14.  _April 13, 2009_
..........................................

The _LilyPond Report_ is back, on a new website!  This short, informal,
weekly opinion column is about the LilyPond project: its team, its
world, its community.  Follow this link
(http://news.lilynet.net/The-LilyPond-Report-14) to read the full
issue...

LilyPond 2.12.2 and 2.13.0 — _March 21, 2009_
...............................................

As a very belated announcement, the stable version of LilyPond is now
2.12.2, and the next development version has begun with 2.13.0.

LilyPond 2.12.0 "Rune" — _December 27, 2008_
..............................................

A new stable release of LilyPond is available.
Announcement (announce-v2.12), *note Changes::, *note Download::.

LilyPond 2.11.65 — Release Candidate.  _December 2, 2008_
...........................................................

This release has improvements to MusicXML import, contributed by
Reinhold Kainhofer, and adds support for splitting a book in several
book parts, contributed by Nicolas Sceaux.  Nested contexts of the same
type are now allowed with any depth, and overriding nested properties
can be done with list syntax, thanks to Neil Puttock.  This is
hopefully the last Release Candidate before stable release 2.12, so you
are welcome to test this release if you can to report new issues.
Bugfixes
(http://code.google.com/p/lilypond/issues/list?can=1&amp;q=fixed_2_11_65&amp;colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Changes::, *note Old downloads::.

LilyPond 2.11.64.  _November 18, 2008_
......................................

LilyPond 2.11.64 is available. MusicXML import has been improved,
including church modes support, and a few bugs in the compilation and
documentation building processes are fixed.  The three documentation
manuals are now fully translated in Spanish, thanks to Francisco Vila.
The font cache problem in Windows binaries which used to cause
excessive slowness should be fixed.
*note Changes::, *note Old downloads::.

LilyPond 2.11.63.  _October 29, 2008_
.....................................

LilyPond 2.11.63 is available. This release has lots of updates to the
documentation and translations.  *note Old downloads::.

LilyPond 2.11.62 &ndash; Release Candidate.  _October 11, 2008_
...............................................................

LilyPond 2.11.62 is available. This is is one of the last releases
before 2.12, so testing it is encouraged. In addition to a bugfix in
`\tempo' command, this release has lot of updates to Spanish and German
documentation translations, and the stylesheet for HTML documentation
has been improved.
Bugfixes
(http://code.google.com/p/lilypond/issues/list?can=1&amp;q=fixed_2_11_62&amp;colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Old downloads::.

LilyPond 2.11.61 available.  _October 1, 2008_
..............................................

LilyPond 2.11.61 has been released. It has updates to documentation
translations, and a new automatic accidentals style (teaching) has been
added.
Bugfixes
(http://code.google.com/p/lilypond/issues/list?can=1&amp;q=fixed_2_11_61&amp;colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Changes::, *note Old downloads::.

LilyPond 2.11.60 available.  _September 25, 2008_
.................................................

LilyPond 2.11.60 has been released. A new style of double repeat bar
line has been added, and `printallheaders' variable in score block has
been renamed to `print-all-headers'.  *note Old downloads::.

LilyPond 2.11.59 available.  _September 20, 2008_
.................................................

Release 2.11.59 is out. LilyPond now uses 64 bit integers for rational
numbers, which allows typesetting more complex polymetric music.  This
release also has updates to German and Spanish translations of the
documentation.  *note Old downloads::.

LilyPond 2.11.58 available.  _September 13, 2008_
.................................................

LilyPond 2.11.58 is a beta release, which means the next stable release
is expected in a few weeks.  This release is also special, as it
includes code which supports more flexible automatic accidentals rules,
written several months ago by Rune Zedeler, deceased since then.  All
the development team express their condolences to his family and his
friends.  Besides this, automatic beaming has been improved by Carl
Sorensen, support for creating stem flags in a new style has been
contributed by Reinhold Kainhofer, and a few bugs have been fixed.
Bugfixes
(http://code.google.com/p/lilypond/issues/list?can=1&amp;q=fixed_2_11_58&amp;colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Changes::, *note Old downloads::.

LilyPond 2.11.57 available.  _August 27, 2008_
..............................................

LilyPond 2.11.57 is out.  This release adds support for harp pedal
diagrams, contributed by Reinhold Kainhofer, and some changes in markup
command names have been made.
*note Changes::, *note Old downloads::.

LilyPond 2.11.56 available.  _August 17, 2008_
..............................................

LilyPond 2.11.56 is out.  This release features transposable fret
diagrams, contributed by Carl Sorensen.  Translations status pages are
now available from the documentation start page.  Two predefined
commands `\pointAndClickOn', `\pointAndClickOff' have also been added.
*note Changes::, *note Old downloads::.

LilyPond 2.11.55 available.  _August 6, 2008_
.............................................

LilyPond 2.11.55 is out.  This release fixes several bugs, and for
octavation brackets `set-octavation' has been replaced by a more
user-friendly command, `\ottava'.  Bugfixes
(http://code.google.com/p/lilypond/issues/list?can=1&amp;q=fixed_2_11_55&amp;colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Old downloads::.

LilyPond 2.11.54 available.  _July 30, 2008_
............................................

LilyPond 2.11.54 is out.  This release fixes a bug in tie formatting
following a line break, and changes the behavior of `short-indent' so
that short instrument names are no longer indented in the margin.
Bugfixes
(http://code.google.com/p/lilypond/issues/list?can=1&amp;q=fixed_2_11_54&amp;colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Old downloads::.

LilyPond 2.11.53 available.  _July 23, 2008_
............................................

LilyPond 2.11.53 is out.  This release fixes a lot of bugs.
Bugfixes
(http://code.google.com/p/lilypond/issues/list?can=1&amp;q=fixed_2_11_53&amp;colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Old downloads::.

LilyPond 2.11.52 available.  _July 14, 2008_
............................................

Release 2.11.52 fixes wrong offset of a bar number when it follows a
breath mark, and syntax changes made in recent development releases are
now fully listed on the News page.  *note Changes::, Bugfixes
(http://code.google.com/p/lilypond/issues/list?can=1&amp;q=fixed_2_11_52&amp;colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Old downloads::.

LilyPond 2.11.51 available.  _July 8, 2008_
...........................................

Release 2.11.51 has a couple of bugfixes, and a lot of changes in
predefined command names.  Fret diagrams formatting has been improved
by Carl Sorensen, it is now controlled by `fret-diagram-details'
property.  Bugfixes
(http://code.google.com/p/lilypond/issues/list?can=1&amp;q=fixed_2_11_51&amp;colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Old downloads::.

LilyPond 2.11.50 available.  _July 2, 2008_
...........................................

Release 2.11.50 adds support for metronome marks with text, and
backslashed numbers for figured bass, contributed by Reinhold Kainhofer.
Bugfixes
(http://code.google.com/p/lilypond/issues/list?can=1&amp;q=fixed_2_11_50&amp;colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Old downloads::.

The LilyPond Report #13.  _June 23, 2008_
.........................................

This short, informal, weekly opinion column is about the LilyPond
project: its team, its world, its community.  Follow this link
(http://valentin.villenave.info/The-LilyPond-Report-13) to read the
full issue...

The LilyPond Report #12.  _June 16, 2008_
.........................................

This short, informal, weekly opinion column is about the LilyPond
project: its team, its world, its community.  Follow this link
(http://valentin.villenave.info/The-LilyPond-Report-12) to read the
full issue...

LilyPond 2.11.49 released.  _June 12, 2008_
...........................................

LilyPond 2.11.49 is out.  It fixes a number of bugs, including bugs in
beams formatting.
Bugfixes
(http://code.google.com/p/lilypond/issues/list?can=1&amp;q=fixed_2_11_49&amp;colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Old downloads::.

LilyPond 2.11.48 released.  _June 9, 2008_
..........................................

LilyPond 2.11.48 is out.  This release fixes a few bugs, and
`\compressMusic' has been renamed to `\scaleDurations'.
Bugfixes
(http://code.google.com/p/lilypond/issues/list?can=1&amp;q=fixed_2_11_48&amp;colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Old downloads::.

The LilyPond Report #11.  _June 9, 2008_
........................................

This short, informal, weekly opinion column is about the LilyPond
project: its team, its world, its community.  Follow this link
(http://valentin.villenave.info/The-LilyPond-Report-11) to read the
full issue...

The LilyPond Report #10.  _June 2, 2008_
........................................

Welcome to this special tenth issue of the _LilyPond Report_, entirely
dedicated to Algorithmic Composition systems.
Follow this link
(http://valentin.villenave.info/The-LilyPond-Report-10) to read the
full issue...

LilyPond 2.11.47 released.  _May 28, 2008_
..........................................

LilyPond now allows all text context properties to be markups, except
in `\lyricmode'.  This release also fixes regression tests maintenance
for developers.  Bugfixes
(http://code.google.com/p/lilypond/issues/list?can=1&amp;q=fixed_2_11_47&amp;colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Old downloads::.

LilyPond 2.11.46 available.  _May 22, 2008_
...........................................

Release 2.11.46 fixes a lot of bugs and includes a rewrite of dynamics
engravers.  Support for slur-shaped arpeggios has been added.  *note
Changes::, Bugfixes
(http://code.google.com/p/lilypond/issues/list?can=1&amp;q=fixed_2_11_46&amp;colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Old downloads::.

RSS feed - _May 21, 2008_
.........................

A RSS feed is now available on lilypond.org.  It contains all news
announced on the web site start page: releases, LilyPond report, new
translations of the site and publications.  Feed URL
(http://lilypond.org/web/lilypond-rss-feed.xml).  The info mailing list
(see *note Contact::) is still used to announce releases and special
events.

The LilyPond Report #9.  _May 05, 2008_
.......................................

Welcome to this ninth issue of the _LilyPond Report_!
This short, informal, weekly opinion column is about the LilyPond
project: its team, its world, its community.  Follow this link
(http://valentin.villenave.info/The-LilyPond-Report-9) to read the full
issue...

LilyPond 2.11.45 available.  _April 26, 2008_
.............................................

Release 2.11.45 fixes a couple of bugs in the formatting engine.
`lilypond-book' has been improved, with better performance, a bugfix
about included files, and more flexibility for preprocessing documents
with LaTeX variants. Support for enclosing text in a rounded box has
been contributed by Valentin Villenave.  *note Changes::, Bugfixes
(http://code.google.com/p/lilypond/issues/list?can=1&amp;q=fixed_2_11_45&amp;colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Old downloads::.

LilyPond 2.11.44 available.  _April 14, 2008_
.............................................

Release 2.11.44 is available. Support for figured bass and chord names
has been added to the MusicXML converter. Bugfixes
(http://code.google.com/p/lilypond/issues/list?can=1&amp;q=fixed_2_11_44&amp;colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Old downloads::.

lilypond.org日本語訳 (lilypond.org Japanese translation).  _2008年4月8日 (April 4, 2008)_
................................................................................................

Lilypond.orgのいくつかのページの日本語訳が出来ました。

LilyPond 2.11.43 available.  _March 31, 2008_
.............................................

Release 2.11.43 has been available since March 27. It fixes a couple of
formatting bugs, and the font cache problem with MS-Windows binaries
which caused excessive slowness has been fixed. Bugfixes
(http://code.google.com/p/lilypond/issues/list?can=1&amp;q=fixed_2_11_43&amp;colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Old downloads::.

LilyPond 2.11.42 available.  _March 9, 2008_
............................................

Release 2.11.42 is out. It fixes some formatting and spacing bugs.
(Bugfixes
(http://code.google.com/p/lilypond/issues/list?can=1&amp;q=fixed_2_11_42&amp;colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Old downloads::)

Comparison of music engraving with Finale and LilyPond.  _February 25, 2008_
............................................................................

In three articles, Andrew Hawryluk compares Finale and LilyPond in
general terms, and evaluates in detail engraving capabilities of both
pieces of software.  The second article is an instructive analysis of
Rachmaninoff's Piano Prelude 6 engraving, including comparisons with a
reference hand-engraved edition.  Read the articles
(http://www.musicbyandrew.ca/finale-lilypond-1.html).

LilyPond 2.11.41 available.  _February 25, 2008_
................................................

Release 2.11.41 is available. It has a few bugfixes, updated program
messages in French, German, Spanish and Vietnamese, and updates to the
MusicXML converter. (Bugfixes
(http://code.google.com/p/lilypond/issues/list?can=1&amp;q=fixed_2_11_41&amp;colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Old downloads::)

LilyPond 2.11.37 available.  _January 3, 2008_
..............................................

Release 2.11.37 is available. It has a few bugfixes, and documentation
changes. (*note Old downloads::)

LilyPond 2.11.36 available.  _December 13, 2007_
................................................

Release 2.11.36 is now available. It has many bugfixes, updates for
MusicXML import, and it includes major documentation changes from Grand
Documentation Project. (Bugfixes
(http://code.google.com/p/lilypond/issues/list?can=1&amp;q=fixed_2_11_36&amp;colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Old downloads::)

LilyPond 2.11.33 and 2.10.33 available.  _September 20, 2007_
.............................................................

Release 2.11.33 is now available.  (Bugfixes 2.10
(http://code.google.com/p/lilypond/issues/list?can=1&amp;q=fixed_2_10_33&amp;colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
Bugfixes 2.11
(http://code.google.com/p/lilypond/issues/list?can=1&amp;q=fixed_2_11_33&amp;colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Old downloads::)

LilyPond 2.11.32 available.  _September 2, 2007_
................................................

Release 2.11.32 is now available.  (Bugfixes
(http://code.google.com/p/lilypond/issues/list?can=1&amp;q=fixed_2_11_32&amp;colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Old downloads::)

LilyPond 2.11.31 available.  _August 31, 2007_
..............................................

Release 2.11.31 is now available. It has more bugfixes, updates for
MusicXML import and lots of updates for the translations.  (Bugfixes
(http://code.google.com/p/lilypond/issues/list?can=1&amp;q=fixed_2_11_31&amp;colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Old downloads::)

LilyPond 2.11.30 available.  _August 20, 2007_
..............................................

Release 2.11.30 is now available. It has various bugfixes among others
in the new spacing code, MusicXML import and lots of updates for the
translations.  (Bugfixes
(http://code.google.com/p/lilypond/issues/list?can=1&amp;q=fixed_2_11_30&amp;colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Old downloads::)

LilyPond 2.10.29 and 2.11.29 available.  _August 11, 2007_
..........................................................

Release 2.11.29 is now available. 2.10.29 has a few small fixes.
2.11.29 has several bugfixes, among others in the new spacing code, and
lots of updates for the translations.  (Bugfixes 2.10
(http://code.google.com/p/lilypond/issues/list?can=1&amp;q=fixed_2_10_29&amp;colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
Bugfixes 2.11
(http://code.google.com/p/lilypond/issues/list?can=1&amp;q=fixed_2_11_29&amp;colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Old downloads::)

LilyPond 2.11.28 for FreeBSD x86_64.  _August 10, 2007_
.......................................................

Release 2.11.28 is now available as a binary installer for FreeBSD
x86_64.  Download the installer
(http://lilypond.org/download/binaries/freebsd-64/lilypond-2.11.28-1.freebsd-64.sh)
and do _sh lilypond-2.11.28-1.freebsd-64.sh_ in a command window.

LilyPond 2.11.28 available - _July 25, 2007_
............................................

Release 2.11.28 has several updates to the manual and its translations,
an plethora of bugfixes and a complete cleanup of the spacing engine
code.  (Bugfixes 2.11
(http://code.google.com/p/lilypond/issues/list?can=1&amp;q=fixed_2_11_28&amp;colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Old downloads::)

LilyPond 2.11.26 available - _June 8, 2007_
...........................................

Release 2.11.26 supports page markers, eg. for use in
tables-of-contents.  In addition, it fixes a number of bugs. Enjoy!
(Bugfixes 2.11
(http://code.google.com/p/lilypond/issues/list?can=1&amp;q=fixed_2_11_26&amp;colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Old downloads::)

LilyPond 2.10.25 and 2.11.25 available - _May 20, 2007_
.......................................................

Release 2.11.25 has support for toplevel page breaking commands, and
page breaking as a whole has been sped up significantly. Enjoy!
(Bugfixes 2.11
(http://code.google.com/p/lilypond/issues/list?can=1&amp;q=fixed_2_11_25&amp;colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
Bugfixes 2.10
(http://code.google.com/p/lilypond/issues/list?can=1&amp;q=fixed_2_10_25&amp;colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Old downloads::)

LilyPond 2.10.23 and 2.11.23 available - _May 1, 2007_
......................................................

This has lots of bugfixes.  (Bugfixes 2.11
(http://code.google.com/p/lilypond/issues/list?can=1&amp;q=fixed_2_11_23&amp;colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
Bugfixes 2.10
(http://code.google.com/p/lilypond/issues/list?can=1&amp;q=fixed_2_10_23&amp;colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Old downloads::)

&Uuml;bersetzung der Dokumentation - _10. April 2007_
.....................................................

Die Kapitel 1-5 (der Abschnitt für Anf&auml;nger) des
LilyPond-Benutzerhandbuchs sind auf deutsch &uuml;bersetzt &mdash; sie
sind erh&auml;ltlich f&uuml;r die *note Changes:: online und *note Old
downloads::.

LilyPond 2.11.22 available - _April 10, 2007_
.............................................

This release has updates of the dot collision code.  (Bugfixes
(http://code.google.com/p/lilypond/issues/list?can=1&amp;q=fixed_2_11_22&amp;colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Changes::, *note Old downloads::)

LilyPond 2.11.21 available - _March 24, 2007_
.............................................

This release has some documentation updates.  (Bugfixes
(http://code.google.com/p/lilypond/issues/list?can=1&amp;q=fixed_2_11_21&amp;colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Changes::, *note Old downloads::)

Traduction de la documentation en fran&ccedil;ais - _25 f&eacute;vrier 2007_
............................................................................

Les chapitres 1 &agrave; 4 et 6 du manuel de l'utilisateur sont
d&eacute;sormais traduits, et disponibles en ligne &mdash; version 2.10
(@DOC@v2.10/Documentation/user/lilypond/index.fr.html), version 2.11
(@DOC@v2.11/Documentation/user/lilypond/index.fr.html).  Les
traductions sont &eacute;galement incluses dans la documentation
t&eacute;l&eacute;chargeable (install).

LilyPond 2.10.20 and 2.11.20 available - _February 25, 2007_
............................................................

This release fixes many bugs.  (Bugfixes 2.11
(http://code.google.com/p/lilypond/issues/list?can=1&amp;q=fixed_2_11_20&amp;colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
Bugfixes 2.10
(http://code.google.com/p/lilypond/issues/list?can=1&amp;q=fixed_2_10_20&amp;colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Changes::, *note Old downloads::)

LilyPond 2.10.19 and 2.11.19 available - _February 18, 2007_
............................................................

This release fixes many bugs.  (Bugfixes 2.11
(http://code.google.com/p/lilypond/issues/list?can=1&amp;q=fixed_2_11_19&amp;colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
Bugfixes 2.10
(http://code.google.com/p/lilypond/issues/list?can=1&amp;q=fixed_2_10_19&amp;colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Changes::, *note Old downloads::)

LilyPond 2.11.18 available - _February 12, 2007_
................................................

This release fixes still more bugs, and included singing support
through festival contributed by Milan Zamazal. (Bugfixes 2.11
(http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_18&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Changes::, *note Old downloads::)

LilyPond  2.11.17 available - _February 9, 2007_
................................................

This release fixes still more bugs.  (Bugfixes 2.11
(http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_17&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Changes::, *note Old downloads::)

LilyPond 2.10.16 and 2.11.16 available - _February 4, 2007_
...........................................................

This release fixes many bugs.  (Bugfixes 2.11
(http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_16&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
Bugfixes 2.10
(http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_16&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Changes::, *note Old downloads::)

LilyPond 2.10.15 and 2.11.15 available - _February 1, 2007_
...........................................................

This release will stretch piano staves on a system-by-system basis and
add a few glyphs: a black harmonic note head and the slashed mirrored
flat.  (Bugfixes 2.11
(http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_15&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
Bugfixes 2.10
(http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_15&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Changes::, *note Old downloads::)

LilyPond 2.10.14 and 2.11.14 available - _January 26, 2007_
...........................................................

This release has a rewrite of the line-spanner code, responsible for
among other glissandi and text-crescendos, making them more flexible.
(Bugfixes
(http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_14&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Changes::, *note Old downloads::)

LilyPond 2.10.13 and 2.11.13 available - _January 17, 2007_
...........................................................

This release fixes a few minor but irritating bugs. In addition, the
2.11 release has updates of the tutorial.  (Bugfixes
(http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_13&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Changes::, *note Old downloads::)

LilyPond 2.11.12 available - _January 17, 2007_
...............................................

This release fixes lots of bugs. In particular, the tie formatting has
been further improved, and memory usage has been improved enormously.
(Bugfixes
(http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_12&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Changes::, *note Old downloads::)

LilyPond 2.10.12 available - _January 17, 2007_
...............................................

This release mirrors 2.11.12. Notably, it has the same memory usage
improvements.  (Bugfixes
(http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_12&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Changes::, *note Old downloads::)

LilyPond 2.10.11 available - _January 12, 2007_
...............................................

This release mostly has the same fixes as 2.11.11.  (Bugfixes
(http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_11&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Changes::, *note Old downloads::)

LilyPond 2.11.11 available - _January 11, 2007_
...............................................

This release has further fixes for popular bugs. Timing of the MIDI
output won't get confused by tuplets and grace notes anymore. Some fat
has also been trimmed of the skyline code performance.  (Bugfixes
(http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_11&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Changes::, *note Old downloads::)

LilyPond 2.11.10 available - _January 8, 2007_
..............................................

LilyPond 2.11.10 has further review of the test-suite, performance and
code coverage. This brought to light several problems that were fixed.
Notably, 2.11.10 fixes lots of regressions in optical correction
spacing and MIDI dynamics.  Also, this version is 20 to 50 % faster
than previous 2.11 releases. (Bugfixes
(http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_10&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Changes::, *note Old downloads::)

LilyPond 2.10.10 available - _January 8, 2007_
..............................................

This release fixes several popular bugs, among others: MIDI files that
go silent after (de)crescendi, and tuplets problems with quoting and
part-combining (Bugfixes
(http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_10&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Changes::, *note Old downloads::)

LilyPond 2.11.9 and 2.10.9 available - _January 3, 2007_
........................................................

This release has a couple of bugfixes, and &mdash;in 2.11.9&mdash
further improvements in the regression test suite (Bugfixes
(http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_9&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Changes::, *note Old downloads::)

LilyPond 2.11.8 and 2.10.8 available - _January 3, 2007_
........................................................

New! Improved! With even more bugfixes!  (Bugfixes
(http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_8&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Changes::, *note Old downloads::)

`lilypond.org' auf deutsch - _31. Dezember 2006_
................................................

Die LilyPond-Webseiten sind jetzt auch auf deutsch &uuml;bersetzt!

`lilypond.org' en español - _December 29, 2006_
................................................

¡Ya está disponible la versión en español del sitio web de LilyPond!

LilyPond 2.11.7 and 2.10.7 available - _January 1, 2007_
........................................................

New! Improved! With even more bugfixes!  (Bugfixes
(http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_7&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Changes::, *note Old downloads::)

LilyPond 2.11.6 available - _December 30, 2006_
...............................................

This release supports arbitrary fractional alterations, allowing music
with different microtonal conventions to be typeset.  (Bugfixes
(http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_6&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Changes::, *note Old downloads::)

LilyPond 2.10.6 available - _December 30, 2006_
...............................................

New! Improved! With even more bugfixes!  (Bugfixes
(http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_6&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Changes::, *note Old downloads::)

LilyPond 2.11.5 available - _December 24, 2006_
...............................................

These releases complete the translation infrastructure for
Documentation.  (Bugfixes
(http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_5&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Changes::, *note Old downloads::)

LilyPond 2.10.5 available - _December 24, 2006_
...............................................

New! Improved! With even more bugfixes!  (Bugfixes
(http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_5&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Changes::, *note Old downloads::)

LilyPond 2.11.4 available - _December 21, 2006_
...............................................

The vertical spacing improvements that were introduced in 2.11.0 now
work within a system as well as between systems.  (Bugfixes
(http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_4&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Changes::, *note Old downloads::)

LilyPond 2.11.3 available - _December 19, 2006_
...............................................

This release has graphical test results
(http://lilypond.org/doc/v2.11/compare-v2.10.3/index.html) and several
website build improvements.  (Bugfixes
(http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_3&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Changes::, *note Old downloads::)

LilyPond 2.10.3 available - _December 19, 2006_
...............................................

This release fixes several bugs.  (Bugfixes
(http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_3&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Old downloads::)

LinuxPPC binaries available! - _December 19, 2006_
..................................................

From now on, our GUB binary builds include support for Linux/PPC.
(*note Old downloads::)

Traduction du tutoriel en fran&ccedil;ais.  _December 13, 2006_
...............................................................

Fruit du travail d'une &eacute;quipe de traducteurs, le tutoriel en
fran&ccedil;ais est maintenant disponible en ligne. Version 2.10
(@DOC@v2.10/Documentation/user/lilypond/Tutorial.fr.html), Version 2.11
(@DOC@v2.11/Documentation/user/lilypond/Tutorial.fr.html).

LilyPond 2.11.2 available - _December 12, 2006_
...............................................

This release supports glissandi and harmonics in tablature.  (Bugfixes
(http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_2&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Changes::, *note Old downloads::)

LilyPond 2.10.2 available - _December 12, 2006_
...............................................

A new stable release of LilyPond is available.  (Bugfixes
(http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_2&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Old downloads::)

LilyPond 2.11.1 available - _December 4, 2006_
..............................................

This release has improved support for horizontal spacing.  (Bugfixes
(http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_1&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Changes::, *note Old downloads::)

LilyPond 2.10.1 available - _December 3, 2006_
..............................................

A new stable release of LilyPond is available.  (Bugfixes
(http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_1&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Old downloads::)

LilyPond 2.11.0 available - _November 27, 2006_
...............................................

This release has improved support for vertical spacing.  (*note
Changes::, *note Old downloads::)

LilyPond 2.10.0 available - _November 11, 2006_
...............................................

A new stable release of LilyPond is available.  (Announcement
(announce-v2.10.html), *note Changes::, *note Old downloads::)

GIT repository online - _November 11, 2006_
...........................................

LilyPond development has moved over its source code to GIT
(http://git.or.cz), the fast version control system. Check out our
repository at gnu.org
(http://git.sv.gnu.org/gitweb/?p=lilypond.git;a=summary).

LilyPond 2.9.29 available - _November 5, 2006_
..............................................

This release has many more bugfixes.  (Bugfixes
(http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_9_29&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Old downloads::)

LilyPond 2.9.28 available - _November 3, 2006_
..............................................

This release has many more bugfixes.  (Bugfixes
(http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_9_28&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Old downloads::)

LilyPond 2.9.27 available - _October 28, 2006_
..............................................

This release has a new `FretBoards' context, and some further bugfixes.
(*note Changes::, Bugfixes
(http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_9_27&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Old downloads::)

Music streams thesis available - _October 21, 2006_
...................................................

The last months, Erik Sandberg has been overhauling the internals of
Lily. This change introduces a new intermediate format, Music Streams,
which will make it easier get music data out of LilyPond. A copy of the
thesis is now available from lilypond.org (*note Publications::).

LilyPond 2.9.26 available - _October 20, 2006_
..............................................

This release has further bugfixes.   (Bugfixes
(http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_9_26&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Old downloads::)

LilyPond 2.9.25 available - _October 18, 2006_
..............................................

This release has more bugfixes; from now on, binaries are also
available for x86/64.  (Bugfixes
(http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_9_25&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Old downloads::)

LilyPond 2.9.24 available - _October 15, 2006_
..............................................

This release has support for right hand guitar fingerings, and offers
some bugfixes.  (*note Changes::, Bugfixes
(http://code.google.com/p/lilypond/issues/list?can=1&q=fixed2924&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary),
*note Old downloads::)

LilyPond 2.9.23 available - _October 12, 2006_
..............................................

This release cuts fragments of EPS directly from your finished score,
and makes it easier to insert ties into lyrics. (*note Changes::, *note
Old downloads::)

LilyPond 2.9.22 available - _October 9, 2006_
.............................................

Test this release candidate for LilyPond 2.10!  (*note Old downloads::)

LilyPond 2.9.21 available - _October 4, 2006_
.............................................

Test this release candidate for LilyPond 2.10!  (*note Old downloads::)

LilyPond 2.9.20 available - _October 3, 2006_
.............................................

Test this release candidate for LilyPond 2.10!  (*note Old downloads::)

LilyPond 2.9.17 available - _September 2, 2006_
...............................................

This release fixes many bugs. Among others, MacOS X QuickTime now
honors tempo changes are in the MIDI output.  (*note Changes::, *note
Old downloads::)

LilyPond 2.9.16 available - _August 25, 2006_
.............................................

In this release, chords may be partially tied and lyric extenders have
tunable padding. Moreover, many bugs were fixed (*note Changes::, *note
Old downloads::)

LilyPond 2.9.15 available - _August 20, 2006_
.............................................

This releases fixes many bugs in the 2.9.14 release.  (*note Old
downloads::)

LilyPond 2.8.6 available - _August 8, 2006_
...........................................

This release contains a few minor bugfixes; the source tarball is also
available.  (*note Old downloads::)

LilyPond 2.9.14 available - _August 4, 2006_
............................................

This release supports instrument name changes, dotted barlines and
better spacing for floating grace notes. In addition, it contains
ongoing work by Erik Sandberg to extend the interpretation phase with
stream support.  (*note Changes::, *note Old downloads::)

LilyPond 2.9.13 available - _July 23, 2006_
...........................................

This release supports doits and falls, and more tuning options for
grace note spacing and tuplet brackets.  (*note Changes::, *note Old
downloads::)

LilyPond 2.9.12 available - _July 18, 2006_
...........................................

This release supports pdftex for lilypond-book, and uses PdfTeX for
generating manuals, so page numbers and references are now clickable.
(*note Changes::, *note Old downloads::)

LilyPond 2.9.11 available - _July 12, 2006_
...........................................

This release wraps improvements of the last two weeks.  As a new
feature, it supports tunable tuplet number formatting for nested
tuplets.  (*note Changes::, *note Old downloads::)

LilyPond 2.9.10 available - _June 15, 2006_
...........................................

This releases fixes a couple of  bugs in 2.9.9.  (*note Changes::,
*note Old downloads::)

LilyPond 2.9.9 available - _June 15, 2006_
..........................................

This releases fixes many bugs in 2.9.8 and earlier.  (*note Changes::,
*note Old downloads::)

LilyPond 2.9.8 available - _June 6, 2006_
.........................................

2.9.8 has support for different spacing sections within a single score,
and better infrastructure for automated regression testing.  (*note
Changes::, *note Old downloads::)

LilyPond 2.8.4 available - _June 4, 2006_
.........................................

2.8.4 fixes some minor bugs, and includes a backport of the
infrastructure for automated regression testing.  (*note Old
downloads::)

First test results available - _June 4, 2006_
.............................................

After a week of frantic tweaking, the first automated testing results
are available.  You can now see in full glory
(http://lilypond.org/doc/v2.9/compare-v2.8.4/index.html) what features
are broken in the development release

LilyPond 2.9.7 available - _May 30, 2006_
.........................................

2.9.7 has improvements in the formatting for figured bass, and includes
a new framework for detecting bugs earlier, which will make the
development releases even better

LilyPond 2.9.6 available - _May 24, 2006_
.........................................

This release has new features in beam formatting: beams may now be put
on single stems, and obey the `beatGrouping' property.  MusicXML
converter.  (*note Changes::, *note Old downloads::)

New essay pages! - _May 22, 2006_
.................................

The _Automated Engraving_ essay has been updated with material from the
FISL (http://fisl.softwarelivre.org) talk, with pages on modeling
notation (about/automated-engraving/problem-statement) and algorithms
for esthetics (about/automated-engraving/scoring-esthetics). Happy
reading!

LilyPond 2.9.5 available - _May 17, 2006_
.........................................

This release supports object rotation, hairpins with circled tips,
hairpins that run to barlines before notes and improvements in the
MusicXML converter.  (*note Changes::, *note Old downloads::)

LilyPond 2.9.4 available - _May 12, 2006_
.........................................

This release has support for feathered beaming, and note head styles in
the markup `\note' command. In addition, it has a lot of updates of the
manual and a clean up of the spring spacer.  (*note Changes::, *note
Old downloads::)

LilyPond 2.8.2 available - _May 12, 2006_
.........................................

This release has fixes for minor bugs and compilation issues.  (*note
Old downloads::)

LilyPond 2.9.3 is out! - _May 7, 2006_
......................................

This new release has lots of updates of the manual, courtesy Graham and
the contributors of the mailing. It handles formatting for ties in
arpegiated chords better (feature sponsored by Steve Doonan), it has al
niente hairpins, courtesy of Erlend Aasland, and some cleanups of the
PostScript output, courtesy David Feuer. (*note Changes::, *note Old
downloads::)

FISL7.0 slides available - _April 22, 2006_
...........................................

The slides for Han-Wen's talk at FISL 7 (http://fisl.softwarelivre.org)
are now online.  (*note Publications::)

LilyPond 2.8.1 is out! - _April 3, 2006_
........................................

Important bugfixes include CJK font handling and a Darwin/x86 port.
(*note Changes::, *note Old downloads::)

LilyPond 2.9.1 is out! - _April 3, 2006_
........................................

It's mostly a bugfix release, and it's almoste the same as 2.8.1. This
release mainly fixes problems with CJK font loading.  (*note Changes::,
*note Old downloads::)

LilyPond on MacOS X/Intel - _March 31, 2006_
............................................

LilyPond now also runs on Intel based macs, offering a 400% speedup
over the emulated PowerPC binaries.  (*note Old downloads::)

LilyPond 2.8.0 is out! - _March 22, 2006_
.........................................

Version 2.8 is here! Read the release announcement
(announce-v2.8.html).  (*note Changes::, *note Old downloads::)

LilyPond 2.7.39 is out - _March 17, 2006_
.........................................

This release has even more bug fixes. Please test before 2.8 is
released. (*note Changes::, *note Old downloads::)

LilyPond 2.7.38 is out - _March 12, 2006_
.........................................

This is likely to be the last release candidate before we release 2.8,
so report any bugs that you might find. New attractions include:
lilypond postscript files now work with GSView, cut & pasting lily code
from PDF files should now work, and spacing fixes for multi-measure
rests.  (*note Changes::, *note Old downloads::)

LilyPond 2.7.37 is out - _March 4, 2006_
........................................

This release has more bug fixes. Please help us by testing it!  (*note
Changes::, *note Old downloads::)

LilyPond 2.7.36 is out - _February 24, 2006_
............................................

This is another release candidate for 2.8. It has lots of bug fixes and
polishes to the documentation.  It also contains support for creating
ties that are only on their right side connected to note heads, which
is handy for repeats (feature sponsored by Steve Doonan).  The
documentation suite can now be downloaded as a separate tarball from
lilypond.org. (*note Changes::, *note Old downloads::)

LilyPond 2.7.35 is out - _February 19, 2006_
............................................

This release has lots of bugs fixes. The plan is to release 2.8 at the
end of this month, so bug reports are *very* welcome. By definition a
bug is release critical if it wasn't present in version 2.6. (*note
Changes::, *note Old downloads::)

LilyPond 2.7.34 is out - _February 16, 2006_
............................................

This release has a bunch of bugfixes, and new features. Newly created
contexts may also be named with `\new Voice = "alto"'. Thicknesses of
tie and slurs may be tuned separately for the endings and the middle
part. (*note Changes::, *note Old downloads::)

LilyPond 2.7.33 is out - _February 10, 2006_
............................................

Items directly connected with a music input element may be
parenthesized, for example,

{
  c4 -\parenthesize -.
  <d \parenthesize fis a>
}

   This feature was sponsored by Ramana Kumar. (*note Changes::, *note
Old downloads::)

LilyPond 2.7.32 is out - _February 7, 2006_
...........................................

This release contains some syntax changes: words inside the \paper and
\layout block are henceforth written with dashes, for instance:


{
  \layout {
    ragged-right = ##t
  }
}

   Furthermore, in this release, we have dropped some legacy code from
our library. Now, lily uses standard C++ strings and the STL vector.
(*note Changes::, *note Old downloads::)

LilyPond 2.7.31 is out - _February 2, 2006_
...........................................

This release fixes a load of bugs, and has some internal cleanups.
Exported C++ members are now named ly:class-name::function-name in
Scheme instead of Class_name::function_name. We are now using C++
vectors and strings instead of our own. The Linux/FreeBSD builds now
include wrappers for Python scripts too, so you can run convert-ly and
midi2ly.  (*note Changes::, *note Old downloads::)

LilyPond 2.7.30 is out - _January 30, 2006_
...........................................

This release has a few bug fixes, like the solfa note head shape and
collisions, the \epsfile command, and in getting No. ligature in normal
words. (*note Changes::, *note Old downloads::)

LilyPond 2.7.29 is out - _January 27, 2006_
...........................................

This release has the following new features. Alignments of staves may
be tuned per system (feature sponsored by Trevor Baca), individual
systems may be positioned manually (feature sponsored by Trevor Baca
and Nicolas Sceaux), a linebreaking configuration can now be saved as a
`.ly' file automatically. This allows vertical alignments to be
stretched to fit pages in a second formatting run (feature sponsored by
Trevor Baca and Nicolas Sceaux). (*note Changes::, *note Old
downloads::)

LilyPond 2.7.28 is out - _January 22, 2006_
...........................................

This release contains numerous small fixes that were already in our GUB
binaries. In addition, it has further polish for formatting of tied
chords. Theses improvements were sponsored by Steve Doonan. (*note
Changes::, *note Old downloads::)

LilyPond 2.7.27, release 4 - _January 13, 2006_
...............................................

The fourth release of our Grand Unified Binary for 2.7.27 is available.
This release uses Pango 1.11.1, which has support for ligatures and
kerning. Enjoy!  (*note Old downloads::)

LilyPond 2.7.27, release 3 - _January 12, 2006_
...............................................

The third release of our Grand Unified Binaries is available.  This
release fixes external font-support, the decompression flag for Linux.
Also, we have support for *FreeBSD* as well!  Jump to the *note Old
downloads:: get them!

LilyPond 2.7.27 binaries are out - _January 7, 2006_
....................................................

Starting with 2.7.26, the development team has been working on the
installers. We're proud to announce another version of these: they are
now available for Linux/x86
(http://lilypond.org/download/binaries/linux-x86/lilypond-2.7.27-1.linux.sh),
MacOS X
(http://lilypond.org/download/binaries/MacOS/lilypond-2.7.27-2.zip) and
Windows
(http://lilypond.org/download/binaries/mingw/lilypond-2.7.27-2.exe).

LilyPond 2.7.27 is out - _January 7, 2006_
..........................................

This release allows you to switch staff lines on and off individually
(feature sponsored by Andrea Valle). (*note Changes::, *note Old
downloads::)

Linux Journal article - _January 2006_
......................................

Linux Journal publishes an article on _Make Stunning Schenker Graphs
with GNU LilyPond_ (http://www.linuxjournal.com/article/8364).  It is a
in-depth but hands-on feature article with crisp LilyPond graphics.
Author Kris Shaffer remarks &ldquo;GNU Lilypond generates beautiful
graphics that make commercial alternatives seem second-rate.&rdquo;
This article is now available on-line
(http://www.linuxjournal.com/article/8583).

New binaries for LilyPond 2.7.26 - _January 4, 2006_
....................................................

The Development team has been working around the clock to improve to
fix the first wave bugs reported by you.  The new results for MacOS and
Windows are up on the *note Old downloads:: page. Let us know how you
fare!

LilyPond 2.7.26 is out - _December 31, 2005_
............................................

This release has an improvement in the MusicXML importer (feature
sponsored by Mark vd Borre's Music Academy): now, staves and voices are
also setup, so you can readily run LilyPond on the .ly output.  The
important occasion for this release is our new build environment: we
have completely revamped it, which means that binaries for all
platforms (including MacOS, Windows, Linux/x86, but probably FreeBSD
too) will be more quickly available for download.  A happy 2006 from
the LilyPond Development Team!  (*note Changes::, *note Old downloads::)

LilyPond 2.7.25 is out - _December 24, 2005_
............................................

This release has various bugfixes. Also, stems on the center line now
have their directions interpolated to minimize the number of direction
changes (feature sponsored by Basil Crow and Mike Rolish). (*note
Changes::, *note Old downloads::)

LilyPond 2.7.24 is out - _December 20, 2005_
............................................

This release fixes a couple of bugs, but more importantly, slurs now
avoid TupletNumbers, and tuplet numbers may enter the staff (feature
sponsored by Trent Johnston), tuplet brackets and numbers are
implemented as separate grobs, TupletBracket and TupletNumber (rewrite
sponsored by Trent Johnston), string arguments for music functions may
be specified without # marks. This allows syntactical constructs (like
\clef and \bar) to be expressed in generic music functions. (*note
Changes::, *note Old downloads::)

LilyPond 2.7.23 is out - _December 19, 2005_
............................................

This release has the following new features:
   * Ties in chords are also formatted using score based formatting.
     This reduces the number of collisions for ties in chords (feature
     sponsored by Steve Doonan).

   * With the \tweak music function, layout objects that are directly
     connected to input may be tuned easily (feature sponsored by Sean
     Reed and Bertalan Fodor).

   * Generic music functions may now also be used on articulations and
     chord elements (feature sponsored by Sean Reed and Bertalan Fodor).

   * Better support for MusicXML, more options for spacing Lyrics; it
     is now possible to separately specify minimum distances for normal
     and hyphenated syllables (features sponsored by Mark van den Borre
     and Bertalan Fodor.
   (*note Changes::, *note Old downloads::)

LilyPond 2.7.22 is out - _December 9, 2005_
...........................................

This release has better support for MusicXML: it also supports ties,
beams and editorial accidentals. It also has more options for spacing
Lyrics; it is now possible to separately specify minimum distances for
normal and hyphenated syllables. These features were sponsored by Mark
van den Borre and Bertalan Fodor. (*note Changes::, *note Old
downloads::)

LilyPond 2.7.21 is out - _December 5, 2005_
...........................................

Saint Nicholas brings you ... a MusicXML (http://www.musicxml.org/)
convertor for LilyPond!  The convertor is basic, but working. Check out
the LilyPond Software Design
(http://www.lilypond-design.com/sponsor/open-features.html#inputfilter)
pages for MusicXML features that can be sponsored.

LilyPond 2.7.20 is out - _December 2, 2005_
...........................................

This release contains the following improvements: Texts set in a
TrueType font are now kerned. Using the TeX no longer requires linking
or dynamically opening the kpathsea library, making the backend more
easily usable on various systems (feature sponsored by Christian Ebert
of Black Trash Productions). (*note Changes::, *note Old downloads::)

LilyPond 2.6.5 is out - _December 1, 2005_
..........................................

This release updates the bugreporting address and reorganizes the
documentation tree. (*note Old downloads::)

LilyPond 2.7.19 is out - _November 26, 2005_
............................................

This version contains a few bugfixes, and now allows the type of
brackets in system start bracket hierarchies to be specified. Also, the
horizontal alignment of rehearsal marks may be changed: marks can be
put on key signatures, clefs, time signatures, etc. (*note Changes::,
*note Old downloads::)

LilyPond 2.7.18 is out - _November 21, 2005_
............................................

This version features nestable system start delimiters, like bracket,
brace. It also adds "square" line bracket (feature sponsored by Trevor
Baca). It also has refactored routines for tie formatting. This will
make it easier to get better tie formatting for chords (feature
sponsored by Steve Doonan). It also has a few bug fixes. (*note
Changes::, *note Old downloads::)

LilyPond 2.7.17 is out - _November 17, 2005_
............................................

This version has refactored routines for tie formatting. This will make
it easier to get better tie formatting for chords (feature sponsored by
Steve Doonan). It also has a few bug fixes. (*note Changes::, *note Old
downloads::)

LilyPond 2.7.16 is out - _November 11, 2005_
............................................

This release fixes a large number of bugs. Please upgrade before
reporting bugs in the 2.7 series. (*note Changes::, *note Old
downloads::)

LilyPond 2.7.15 is out - _November 3, 2005_
...........................................

This release has another massive cleanup of the backend.  Each grob
property may also be a "grob closure". This means that it is possible
to combine functions. Calculation of extent and offset of grob is now
controlled via the `X-extent', `Y-extent', `X-offset' and `Y-offset'
properties. (*note Changes::, *note Old downloads::)

LilyPond 2.7.14 is out - _October 23, 2005_
...........................................

This release has more cleanup in the layout-engine. Now, properties
that have Procedure values are thought to be procedures that compute
said property, i.e.


\override Beam #'direction = #(lambda (grob)
(if (> (random 10) 5) UP DOWN))

 will set  a random direction for beams. (*note Changes::, *note Old
downloads::)

LilyPond 2.7.13 is out - _October 18, 2005_
...........................................

This release features slashed numerals, plus signs and interruptible
extender lines for figured bass. Merging of Figured bass lines has been
made switchable with the figuredBassCenterContinuations property. For
each grob, a subproperty in `callbacks' property defines the procedure
which computes it. This is major internal cleanup, which also provides
advanced tweakability for power users. (*note Changes::, *note Old
downloads::)

LilyPond 2.6.4 is out - _October 11, 2005_
..........................................

This release fixes a few minor problems with the stable series. (*note
Changes::, *note Old downloads::)

LilyPond 2.7.12 is out - _October 07, 2005_
...........................................

It features more annotations for the page layout engine and some more
sponsored features. Beamlets may stick out of the side of beams
(feature sponsored by Trevor Baca); new support for figured bass with
support for continuation lines and tuning of figures, brackets, and
alignments (feature sponsored by Trent Johnston); vertical alignments
of staves can now be tuned easily for individual systems (feature
sponsored by Nicolas Sceaux). (*note Changes::, *note Old downloads::)

LilyPond 2.7.11 is out - _October 02, 2005_
...........................................

Vertical spacing for page layout can now be tuned for each system
individually (feature sponsored by Trevor Baca and Nicolas Sceaux). The
slope of a stem-tremolo may be set manually (feature sponsored by Sven
Axelsson). There are a number of cleanups in the handling and
representation of systems, among other features and bug fixes. (*note
Changes::, *note Old downloads::)

LilyPond 2.7.10 is out - _September 13, 2005_
.............................................

This version adds proper support for "laissez vibrer ties", just enter
\laissezVibrer after a chord. This feature was sponsored by Henrik
Frisk. It also has a couple of minor bugfixes. (*note Changes::, *note
Old downloads::)

LilyPond 2.7.9 is out - _September 5, 2005_
...........................................

This is mainly a bugfix release. (*note Changes::, *note Old
downloads::)

Traduction fran&ccedil;aise du site - _September 03, 2005_
..........................................................

Grâce à l'équipe des traducteurs (about/thanks#website), de
nombreuses pages du site sont maintenant disponibles en fran&ccedil;ais,
notamment l'essai sur la gravure musicale
(about/automated-engraving/index.fr.html).

LilyPond 2.7.8 is out - _August 29, 2005_
.........................................

This release has support for right-to-left text formatting in markup
commands (sponsored by Aaron Mehl). In addition, it fixes a great
number of bugs, among others, support for writing MIDI files.  (*note
Changes::, *note Old downloads::)

Article in `De Standaard' - _August 20, 2005_
.............................................

The Belgian newspaper _De Standaard_ investigates what drives Free
Software authors in an article titled _Delen van KENNIS zonder
WINSTBEJAG_ (Non-profit sharing of knowlegde) using LilyPond as an
example.  This marks LilyPond's first appearance in mainstream printed
press.

LilyPond 2.7.7 is out - _August 22, 2005_
.........................................

This release has a rewriting of tie formatting which was sponsored by
Bertalan Fodor, Jay Hamilton, Kieren MacMillan, Steve Doonan, Trevor
Baca, and Vicente Solsona Dell&aacute;. (*note Changes::, *note Old
downloads::)

LilyPond 2.7.6 is out - _August 19, 2005_
.........................................

This release adds support for numbered percent repeats, a feature
sponsored by Yoshinobu Ishizaki. It also has bugfixes for clashes
between slurs and symbols, like fingers dynamic signs. (*note Changes::,
*note Old downloads::)

LilyPond 2.7.5 is out - _August 16, 2005_
.........................................

Lily 2.7.5 has a large number of bugfixes, among others, in slur
formatting, spacing, rest collisions and tuplet bracket formatting.
(*note Changes::, *note Old downloads::)

LilyPond 2.7.4 is out - _August 7, 2005_
........................................

LilyPond 2.7.4 has support for proportional notation, where the space
for a note is proportional to the time it takes. (*note Changes::,
*note Old downloads::)

LilyPond 2.6.3 is out - _August 4, 2005_
........................................

This release fixes a memory corruption bug that was triggered by
\override'ing Beam settings. (*note Old downloads::)

LilyPond 2.6.2 is out - _August 2, 2005_
........................................

This release has a few bugfixes, among them: the autopackage will run
in more platforms, LilyPond will be much quicker for large
lilypond-book documents, and the up and down Fa note heads for shaped
heads have been swapped. (*note Changes::, *note Old downloads::)

LilyPond 2.7.3 is out - _July 25, 2005_
.......................................

LilyPond 2.7.3 has improvements in performance which should result in
faster operations (15 to 20 percent). It also contains the new
"\displayLilyMusic" function.  (*note Changes::, *note Old downloads::)

LilyPond 2.7.2 is out - _July 21, 2005_
.......................................

LilyPond 2.7.2 has support for suggested accidentals for musica ficta
notation, easy entry for lyric melismata and improvements for quicker
entry of scores.  (*note Changes::, *note Old downloads::)

LilyPond 2.6 released - _June 27, 2005_
.......................................

Version 2.6 is the latest stable release of LilyPond.  It now installs
in a snap on Windows, MacOS X, and any version of Linux (x86).  *Get up
and running in minutes!* Pango text formatting lets you print *Unicode
* lyrics in your favorite script and font.  Create *SVG* files, and
edit them in Inkscape.  (Announcement (announce-v2.6.html), *note Old
downloads::, *note Changes::)

LilyPond 2.7.1 is out - _July 20, 2005_
.......................................

LilyPond 2.7.1 has no user-visible changes. However, due to
restructuring "under the hood", this version will be 10 to 20 % faster.
(*note Old downloads::)

LilyPond 2.6.1 is out - _July 11, 2005_
.......................................

This version fixes a few minor bugs found in 2.6.0, and also works on
DOS-based Windows versions.  (*note Changes::, *note Old downloads::)

LilyPond 2.7 is out - _July 9, 2005_
....................................

LilyPond 2.7.0 is out. It has support for paragraph text and pitched
trill notation. (*note Changes::, *note Old downloads::)

2.5.31 released - _June 22, 2005_
.................................

LilyPond 2.5.32 is now available for download (binaries for Fedora +
MacOS only). It has a few very minor bugfixes, and a rewrite of the TTF
embedding code, which should be a lot more robust now.  (*note Old
downloads::)

Traduction du site de LilyPond - _15 juin 2005_
...............................................

L'équipe des traducteurs (about/thanks#website) vous présente le site
de LilyPond en français. Nous travaillons sur la traduction des pages
encore non traduites. Bon surf !

2.5.31 for Windows and MacOS - _June 15, 2005_
..............................................

2.5.31 is now available for both Windows and MacOS X. The Windows
version should now work with embedding TTF fonts, and the MacOS X has
better help functionality.  (*note Old downloads::)

2.5.31 released - _June 15, 2005_
.................................

This release has a few bugfixes. In the MacOS X version, ClickEdit has
been renamed to LilyPond, and you can now upgrade your files and
compile them directly from LilyPond. (*note Old downloads::)

2.5.30 released - _June 10, 2005_
.................................

This is (hopefully) the last Release Candidate before 2.6. Give it a
good shake to find those last bugs! (*note Old downloads::)

2.5.29 released - _June 7, 2005_
................................

In this release the documentation also has pictures. In addition, the
Mac version can also read native mac fonts (.dfonts and fonts in
resource forks). (*note Old downloads::)

2.5.27 released - _May 31, 2005_
................................

It has a big bunch of minor bugfixes.  This is another release
candidate for version 2.6, which should be released within the next 2
weeks. Please send a bug report if you find a critical problem with this
release. (*note Old downloads::)

Windows and MacOS installers available - _May 26, 2005_
.......................................................

There are now a native, standalone installers for Windows and MacOS.
They also support PDF point & click. (*note Old downloads::)

2.5.26 released - _May 26, 2005_
................................

This release has a couple of small bugfixes.

2.5.25 released - _May 20, 2005_
................................

This release has many small bugfixes and updates to the documentation.
(*note Old downloads::)

2.5.24 released - _May 12, 2005_
................................

2.5.24 fixes a bunch of bugs; in particular, chord symbols (such as
slashed o) should now work on all platforms. This release has a new
feature: it is now possible to make staves appear in a different order
from the order that they were defined. (*note Old downloads::)

2.5.23 released - _May 6, 2005_
...............................

This release has a couple of small bugfixes, and a new feature. It is
now possible to start and stop the StaffSymbol, during a piece of
music, by doing \stopStaff \startStaff. This can be used to produce
Ossia staves. (*note Changes::, *note Old downloads::)

2.5.22 released - _May 3, 2005_
...............................

2.5.22 is a bugfix release. The most visible improvement is in the PDF
: this release will produce smaller PDF files, with symbols that look
better on screen.  (*note Old downloads::)

April 25, 2005 - 2.5.21 released!
.................................

2.5.21 has more bugfixes. It also has support for "grid lines", bar
like vertical line, which are aligned with the notes. The auto-beam
engraver was rewritten, so it also works with irregular time signatures
like 5/8.  (*note Changes::, *note Old downloads::)

April 18, 2005
..............

LilyPond 2.5.20 has lots of bugfixes, in particular, MIDI files of
multi-movement pieces don't overwrite each other.  Version 2.5.20 also
supports putting arrows on lines, such as glissandi.  More details are
in the the *note Changes:: file, or go straight to *note Old
downloads::.

April 15, 2005
..............

LilyPond 2.5.19 was released. The command `\epsfile' allows inclusion
of EPS graphics into markup texts and the music function
`\musicDisplay' will display a music expression as indented Scheme
code. Take a look at the *note Changes:: file and *note Old downloads::.

April 6, 2005
.............

2.5.18 is a bugfix release. It has many small cleanups in the web-based
documentation, and many small cleanups all over the place. *note Old
downloads::

March 31, 2005
..............

2.5.17 is out. This release features many small bugfixes. In addition,
it has support for string number notation for guitar. This feature was
sponsored by Gunther Strube. *note Old downloads::

March 20, 2005
..............

LilyPond 2.5.16 is out. This release fixes a few minor but irritating
errors. A Fedora Core 3 binary is also available.  *note Old downloads::

March 14, 2005
..............

LilyPond 2.5.15 is out. This release has clean ups in the SVG output,
and now uses the LilyPond number font for time signatures.  It is now
possible to add text before and after music. This can be used to add
verses after a music. Take a look at the *note Changes:: file and *note
Old downloads::!

March 7, 2005
.............

LilyPond 2.5.14 is out. It is now possible (and in fact, encouraged),
to build LilyPond either without the Kpathsea TeX library or with the
Kpathsea dynamically loaded, but only for the -btex backend.  This
means that packages do not have to depend on TeX anymore. With this,
the Windows download size will go down significantly. Take a look at
the *note Changes:: file and download *note Old downloads::!

March 7, 2005
.............

LilyPond 2.4.5 is out. This release backports the tieWaitForNote
feature and has support for tetex-3.0.  *note Old downloads::

February 28, 2005
.................

LilyPond 2.5.13 is available for Fedora Core 3. You need to install ESP
Ghostscript 8.15rc3
(http://lilypond.org/download/binaries/Fedora-3/ghostscript-8.15rc3-0.i386.rpm).
Unfortunately, this version of Ghostscript lacks the IJS dynamic
library, which means that it will conflict with the gimp-print package.
You may install it with -nodeps. Use at your own risk.

February 28, 2005
.................

LilyPond 2.5.13 is out. This release has Point and click support for
PDF output. You can read more about it here
(http://lilypond.org/doc/v2.5/Documentation/user/out-www/lilypond/Point-and-click.html).
Take a look at the *note Changes:: file and download *note Old
downloads::!

February 26, 2005
.................

The Lilypond Snippet Repository (LSR) (http://lsr.dsi.unimi.it/) is a
searchable database of Lilypond code snippets.  You can add snippets
too, so join the LSR project, and contribute creative ideas for using
Lilypond.

February 21, 2005
.................

LilyPond 2.5.12 is out. The big news is that this release supports
TrueType fonts. This means that it is now possible to use *all* fonts
available via FontConfig. Also, arpeggios may be written out using ties
and individual objects may have colors!  Take a look at the *note
Changes:: file and *note Old downloads::!

February 4, 2005
................

LilyPond 2.5.11 is out.  In this release, foreign character sets are
now supported in lilypond-book too, and it is possible to put system
separators between systems.  *note Old downloads::!

January 31, 2005
................

LilyPond 2.5.10 is out. This release sports as new EPS backend, based
on the PS backend. This backend is used in the new and improved
lilypond-book script.  *note Old downloads::

January 26, 2005
................

LilyPond 2.5.9 is out. This release fixes a couple of annoying bugs in
the direct PS output for piano braces.  *note Old downloads::

January 16, 2005
................

LilyPond 2.5.8 is out.  This release has many internal code cleanups.
In addition, accuracy of error reporting has been improved.  See the
change log
(http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.3065&content-type=text/vnd.viewcvs-markup)
and *note Old downloads::!

January 11, 2005
................

LilyPond 2.5.7 is out. This release has a completely usable Pango
integration for the PS backend. The default font is Century Schoolbook
from the PS font suite.  It also has small updates to the tablature
settings by Erlend Aasland, assorted manual updates by Graham, and an
overhaul of the font code by Werner.  *note Old downloads:: and check
out the changes in the ChangeLog
(http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.3048&content-type=text/vnd.viewcvs-markup).

January 02, 2005
................

LilyPond 2.5.6 was released. This is a "technology preview" release,
which means that it has all kinds of nifty features, but is not
actually usable for producing nicely printed scores. For this reason,
an RPM of this release was not produced. The PS backend is now
completely switched over to Pango/FontConfig: for -f ps, LilyPond only
accepts UTF8 input, all text fonts are loaded through Pango, the TeX
backend now offloads all metric computations to LaTeX, the SVG and
GNOME backends are broken, most probably.  *note Old downloads:: and
check out the changes in the ChangeLog
(http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.3013&content-type=text/vnd.viewcvs-markup).

December 28, 2004
.................

LilyPond 2.5.5 is out. It is the first one to link against FontConfig
and Pango, although it is only available in the "-f ps" output. The
default output format has been changed back TeX while we stabilize the
Pango/FontConfig integration.  *note Old downloads:: and check out the
changes in the ChangeLog
(http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=
1.3000&content-type=text/vnd.viewcvs-markup).

December 20, 2004
.................

LilyPond 2.5.4 is out. This release has some major brainsurgery in the
font handling. As of now, LilyPond loads the music fonts in OpenType
font format using FreeType.  This has made a lot of things simpler,
including font handling for the GNOME backend and SVG backend.  *note
Old downloads:: and check out the changes in the ChangeLog
(http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2974&content-type=text/vnd.viewcvs-markup).

December 3, 2004
................

LilyPond 2.5.3 was released. A new script, `\espressivo' has been
added, for a combination of crescendo and decrescendo on a single note.
In markups, expressions stacked with `\column', `\center-align', etc,
are not grouped with `< ...  >' anymore, but with `{ ... }'. LilyPond
will now avoid line breaks that cause long texts to stick outside of
the page staff. Grace notes following a main note, used to be entered
by letting the grace notes follow a skip in a parallel expression.
*note Old downloads:: and check out the changes in the ChangeLog
(http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2908&content-type=text/vnd.viewcvs-markup).

November 26, 2004
.................

LilyPond 2.5.2 was released. It has several goodies, including
solfa-notation (shaped noteheads), and an easier mechanism for
customizing title, footer and header layout. Don't forget to rebuild
the fonts, as they have been changed to accomodate the solfa-notation.
*note Old downloads:: and check out the changes in the ChangeLog
(http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2898&content-type=text/vnd.viewcvs-markup).

November 20, 2004
.................

LilyPond 2.5.1 is out. This is an experimental release, containing some
proof-of-concept code for our graphical layout editor. You can add and
remove things from the file, and the tweaks will still work, as long as
the tweaked notes remain in the place (ie. start at the same time-wise
and be part of the same context). Further attractions are: the gnome
backend now also draws beams and slurs, updates to the SVG backend,
support for the lmodern font set for TeX, various bugfixes.  *note Old
downloads:: and check out the changes in the ChangeLog
(http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2881&content-type=text/vnd.viewcvs-markup).

November 12, 2004
.................

The LilyPond development is OPEN once again! The first release of the
2.5 series has the following new Features: Positioning of slurs can now
be adjusted manually, Grace notes are correctly quoted and formatted
when using cue notes, Cue notes can now be created with


\cueDuring #VOICE-NAME #DIRECTION { MUSIC }

 Stemlets (short stems over beamed rests) have been added.  In
addition, Jan hacked together some highly experimental code where you
can use the mouse to drag and drop objects in the -f gnome backend.
These tweaks can be saved and are applied to the PS and TeX output as
well.  *note Old downloads:: and check out the changes in the ChangeLog
(http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2837&content-type=text/vnd.viewcvs-markup).

November 11, 2004
.................

LilyPond 2.4.2 is out. This release fixes a number of security problems
with -safe, and adds a lot of polishing fixes.  *note Old downloads::

November 4, 2004
................

LilyPond 2.4.1 is out. This release includes a number of small fixes
that were made to 2.4.0 last week.  *note Old downloads:: and check out
the changes in the ChangeLog
(http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2780.2&content-type=text/vnd.viewcvs-markup).

October 31, 2004
................

LilyPond 2.4.0 was just released! (announce-v2.4.html) This new stable
version has support for page-layout, completely rewritten slur
formatting and many other improvements. Read about them in the *note
Changes:: file.  *note Old downloads::

October 29, 2004
................

LilyPond 2.3.26 is out. This is another 2.4 release candidate. This
release fixes a number of minor bugs, and some problems with the
conversion scripts.  *note Old downloads:: and check out the changes in
the ChangeLog
(http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2773&content-type=text/vnd.viewcvs-markup).

October 29, 2004
................

2.3.25 is the final release candidate for Lilypond 2.4.  Werner has
been overhauling the TeX macros and lilypond-book. In addition, this
release contains an important fix for raggedbottom page-layout.  *note
Old downloads:: and check out the changes in the ChangeLog
(http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2765&content-type=text/vnd.viewcvs-markup).

October 27, 2004
................

LilyPond 2.3.24 is a further polished 2.4 release candidate.  This
release has more improvements by Werner for the TeX backend, and a
bunch of other small fixes.  *note Old downloads:: and check out the
changes in the ChangeLog
(http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2752&content-type=text/vnd.viewcvs-markup).

October 24, 2004
................

LilyPond 2.3.23 has bugfixes in the documentation, lilypond-book and
-preview output. This release can be considered as a release candidate
for LilyPond 2.4.  *note Old downloads:: and check out the changes in
the ChangeLog
(http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2742&content-type=text/vnd.viewcvs-markup).

October 10, 2004
................

LilyPond 2.3.22 fixes a bunch more bugs, to make 2.4 a really stable
release.  In addition, it renames the \paper{} block to \layout{}.  The
\bookpaper{} block is now called \paper{}.  *note Old downloads:: and
check out the changes in the ChangeLog
(http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2709&content-type=text/vnd.viewcvs-markup).

October 09, 2004
................

LilyPond 2.3.21 is out. It is a serious release candidate for the next
stable release LilyPond. This version has a cleanup and some small
formatting improvements of the slur code.  *note Old downloads:: and
check out the changes in the ChangeLog
(http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2692&content-type=text/vnd.viewcvs-markup).

October 02, 2004
................

LilyPond 2.3.20 was released. It fixes the biggest problems with
encoding and the TeX backend. As a result, latin1 characters (like the
german SS) show up correctly in the output once again. Also it has the
usual bugfixes and updates in the documentation.  *note Old downloads::
and check out the changes in the ChangeLog
(http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2674&content-type=text/vnd.viewcvs-markup).

September 29, 2004
..................

The LilyPond development team will be present at the Free Software
Bazaar (http://www.nluug.nl/events/sane2004/bazaar/index.html) of the
NLUUG SANE 2004 conference today.  If you are in the neighborhood, drop
by for live contact with the Team or just a friendly chat. Registration
is not required to attend.

September 26, 2004
..................

LilyPond 2.3.19 is out. It's mainly a bugfix release.  *note Old
downloads:: and check out the changes in the ChangeLog
(http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2652&content-type=text/vnd.viewcvs-markup).

September 20, 2004
..................

LilyPond 2.3.18 was released. It has further improvements in the slur
formatting, and a small syntax change: the mode changing commands
(`\chords', `\lyrics', etc.)  have been renamed to `\chordmode',
`\lyricmode', etc. The command `\chords' is an abbreviation for \new
ChordNames \chordmode ...  `\drums', `\lyrics', `\chords', `\figures'
function similarly.  *note Old downloads:: and check out the changes in
the ChangeLog
(http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2614&content-type=text/vnd.viewcvs-markup).

September 11, 2004
..................

LilyPond 2.3.16 was released. It fixes a couple of annoying bugs, and
has an important addition in the slur-formatter. Slurs that pass note
heads much closer than the average distance get an extra penalty. This
fixes a lot of difficult slurring cases. See input/regression/new-slur
for some examples.  Please consider this release as a 3.0 pre-release
so try to find as many bugs as possible. A report including a small .ly
example can be filed at bug-lilypond@gnu.org In this case, a bug is
defined as something that the current 2.3 does worse than the latest
2.2 release.  We want to be sure that no output will get uglier by
upgrading to 3.0, so that once 3.0 is out, nothing will hold users back
in switching.  *note Old downloads:: and check out the changes in the
ChangeLog
(http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2562&content-type=text/vnd.viewcvs-markup).

September 10, 2004
..................

LilyPond 2.3.15 was released. It fixes for some gaffes with the new
vertical spacing engine, has lots of documentation updates, and has
support for landscape output in the direct postscript output. Also, the
types of events quoted with `\quote' can now be tuned with
`quotedEventTypes'. By default, only notes and rests end up in quotes.
*note Old downloads:: and check out the changes in the ChangeLog
(http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2553&content-type=text/vnd.viewcvs-markup).

September 6, 2004
.................

LilyPond 2.3.14 was released and has exciting features!  LilyPond will
try to keep staves at the same distances across a page, but it will
stretch distances to prevent collisions; key signature cancellations
are now printed before the bar line; different voices that all use
"\quote" can now refer to each other.  *note Old downloads:: and check
out the changes in the ChangeLog
(http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2534&content-type=text/vnd.viewcvs-markup).

August 29, 2004
...............

LilyPond now has a Documentation Editor, Graham Percival. From now on,
he will oversee that useful information flows from the mailiing list
into the manual. Also, if there are unclear sections in the manual, let
him know via one of the mailing lists.  As a start of his career, he
worked to transform the "Templates" section of the website into a
readable and comprehensive chapter of the user manual.  A lot of cheers
for Graham!

August 29, 2004
...............

LilyPond 2.3.13 was released. The new slur code was improved, scripts
can be made to avoid slurs, by setting inside-slur to #f. It is no
longer necessary to instantiate "up" and "down" staves separately when
using \autochange. Jurgen Reuter refreshed the logic around mensural
flags, so they are adjusted for staff lines once again.  *note Old
downloads:: and check out the changes in the ChangeLog
(http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2520&content-type=text/vnd.viewcvs-markup).

August 24, 2004
...............

LilyPond 2.2.6 fixes a few minor issues, among others, the disappearing
metronome mark.  *note Old downloads:: and check out the changes in the
ChangeLog
(http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2000.2.33&content-type=text/vnd.viewcvs-markup).

August 23, 2004
...............

LilyPond 2.3.12 is out. This release has a lot of fixes and a new
feature: there is now support for putting two slurs on chords, both
above and below. This is switched on with the `doubleSlurs' property.
*note Old downloads:: and check out the changes in the ChangeLog
(http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2489&content-type=text/vnd.viewcvs-markup).

August 3, 2004
..............

LilyPond 2.3.11 is out. This release basically is 2.3.10 with a few
annoying bugs fixed.  *note Old downloads:: and check out the changes
in the ChangeLog
(http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2449&content-type=text/vnd.viewcvs-markup).

August 1, 2004
..............

LilyPond 2.3.10 is out. This release has a major clean-up of the
input/test/ directory. Many examples have been moved to the regression
test or manual, and the superfluous or outdated ones have been removed.
The directory has gone from 146 examples to 72 examples. That means
that we're halfway cleaning it out.  Incidentally, the manual has gone
from 200 to 220 pages. New features:
   * Running trills now have their own spanner and event. They are
     started and stopped with \startTrillSpan and \stopTrillSpan

   * There is a new markup command `\postscript' that takes a string
     that is dumped as verbatim PostScript

   *note Old downloads:: and check out the changes in the ChangeLog
(http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2435&content-type=text/vnd.viewcvs-markup).

July 30, 2004
.............

LilyPond 2.3.9 is out.  The important change is that lilypond now
once-again directly runs the binary. The old wrapper script has been
renamed to lilypond-latex.py, and should only be used for legacy
projects. The recommended route is either using lilypond directly (with
\book, you can have multiple movements within one document), or to run
lilypond-book with a LaTeX wrapper file.  This release also fixes a
bunch of small errors.  I now consider LilyPond feature complete for a
3.0 release.  Next on the TODO list is updating the manual, and after
that's done we can release 3.0. The projected date for this to happen
is in about a month.  *note Old downloads:: and check out the changes
in the ChangeLog
(http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2416&content-type=text/vnd.viewcvs-markup).

July 23, 2004
.............

Lilypond 2.3.8 fixes a few minor bugs in the new slur code, and has
rewritten support for ledger lines. Now, in tight situations, ledger
lines will be shortened so they stay separate.  This also required a
cleanup of the Ambitus implementation.  *note Old downloads:: and check
out the changes in the ChangeLog
(http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2395&content-type=text/vnd.viewcvs-markup).

July 19, 2004
.............

LilyPond 2.3.7 was released and has new exciting features!  The slur
formatting has been rewritten. The new slur code works similar to the
Beam formatter: scores are assigned for all esthetic components of a
slur. A large number of combinations for begin and end points is then
tried out.  Slurs will now also take into account collisions with staff
lines, scripts (like staccato and accent) and accidentals. In the
LilyPond emacs mode, the `|' will now display the current beat within
the measure.  *note Old downloads:: and check out the changes in the
ChangeLog
(http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2383&content-type=text/vnd.viewcvs-markup).

July 15, 2004
.............

LilyPond 2.2.5 was released. It has a few bug fixes from 2.3.x.  *note
Old downloads:: and check out the changes in the ChangeLog
(http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2000.2.28&content-type=text/vnd.viewcvs-markup).

July 11, 2004
.............

An introductory article on LilyPond appeared on Linux Journal
(http://www.linuxjournal.com/article.php?sid=7657&mode=thread&order=0).

July 5, 2004
............

LilyPond 2.3.6 was released.  This release has more updates for the
Fret diagram code (thanks, Carl!), fixes a bunch of bugs, including a
serious one that trashed a lot of beam formatting, and was also present
in the 2.2 series.  *note Old downloads:: and check out the changes in
the ChangeLog
(http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2306&content-type=text/vnd.viewcvs-markup).

July 5, 2004
............

LilyPond 2.2.4 was released. It is mainly a bug fix release.  *note Old
downloads:: and check out the changes in the ChangeLog
(http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2000.2.23&content-type=text/vnd.viewcvs-markup).

June 25, 2004
.............

LilyPond 2.3.5 has numerous small bugfixes and cleanups, and features
more work in the experimental GNOME output module. Adventurous hackers
can check the instructions at scm/output-gnome.scm and try to run
buildscripts/guile-gnome.sh to see what the fuss is all about.  Carl
Sorensen also provided us with more patches to the fret-diagram output.
Check out the ChangeLog
(http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2293&content-type=text/vnd.viewcvs-markup)
and *note Old downloads::.

June 20, 2004
.............

LilyPond 2.2.3 has a turkish translation and fixes a few minor bugs
that were reported over the past month. Check out the ChangeLog
(http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2000.2.16&content-type=text/vnd.viewcvs-markup)
for a full description and *note Old downloads::.

June 13, 2004
.............

LilyPond 2.3.4 further improves the output backends. As a result,
manual page-breaks, multiple output formats and putting `\score' into
markups now works.  Check out the ChangeLog
(http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2242&content-type=text/vnd.viewcvs-markup)
and *note Old downloads::.

May 31, 2004
............

LilyPond 2.3.3 has many internal changes relating to the output backend
(PostScript) and page-layout. In addition, it contains a few bugfixes
for recently reported problems.  Check out the ChangeLog
(http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2207&content-type=text/vnd.viewcvs-markup)
and *note Old downloads::.

May 31, 2004
............

LilyPond 2.2.2 is out.  It has a number of small bugfixes, so upgrade
if any of these errors concern you.  Check out the ChangeLog
(http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2000.2.9)
or head straight to the *note Old downloads::.

May 26, 2004
............

LilyPond 2.3.2 is out. This release has a lot of internal changes
relating to page layout, but also sports experimental fret-diagram
code.  Check out the *note Changes:: or head straight to the *note Old
downloads::.

May 9, 2004
...........

LilyPond 2.3.1 is out. This release has many new and cool features.
Check out the *note Changes:: or head straight to the *note Old
downloads::.

May 4, 2004
...........

Help LilyPond get better, and join in on LilyPond development!  This
call for help (devel/participating/call-for-help.html) was posted on
the mailing list a month ago, and we are still looking for a Release
Meister, Code Janitor, Newsletter editor and a Writer for implementation
Documentation. Of course, any other help is also welcome!

May 3, 2004
...........

LilyPond 2.2.1 has been released. It fixes a handful of bugs.  *note
Old downloads::.

April 17, 2004
..............

LilyPond 2.2.0 is now available on Windows, and should find its way to
the Cygwin mirrors soon.

April 12, 2004
..............

LilyPond 2.3.0 is the first release in the 2.3 cycle.  The focus for
2.3 is page layout, so instrumentalists can force parts to have page
breaks at sane turning points.  This release is _experimental_; expect
things to break!  More info in the *note Changes::.  *note Old
downloads::.

April 8, 2004
.............

A French article on the new LilyPond release appeared on linuxfr.org
(http://linuxfr.org/2004/04/08/15968.html).

April 8, 2004
.............

Binaries for LilyPond 2.2.0 are available for MacOS X, Slackware,
Mandrake and Debian Woody.  *note Old downloads::

April 1, 2004
.............

LilyPond 2.2.0 is out!  This new stable version has completely revamped
support for for orchestral score formatting, cue notes, font size
management, lyric formatting, drum notation/playback and document
integration. Read about it in the announcement (announce-v2.2.html) or
skip to the *note Old downloads::.

March 31, 2004
..............

LilyPond 2.1.37 has build fixes for Cygwin and SUSE, bugfixes for
part-combining and chord tremolos and even more documentation polish.
This should be the final release candidate; expect only regression bugs
to be fixed before 2.2.  *note Old downloads::.

March 30, 2004
..............

LilyPond 2.1.36 has many fixes in the user manual.  *note Old
downloads::.

March 28, 2004
..............

LilyPond 2.1..35 fixes a slew of bugs, and has the `raggedlast' option,
which causes paragraph like line breaking for scores. More info in the
*note Changes::.  *note Old downloads::

March 22, 2004
..............

LilyPond 2.1.34 fixes minor bugs, and has more rewriting.  *note Old
downloads::.

March 21, 2004
..............

LilyPond 2.1.33 fixes a serious bug, and a few other irritations.
*note Old downloads::

March 20, 2004
..............

LilyPond 2.1.32 has more rewriting in the user manual. There is also an
experimental implementation of optimal page breaking (Postscript backend
only).  *note Old downloads::.

March 15, 2004
..............

LilyPond 2.1.31 is out.  It has fixes the alignment of bass figures and
spurious dynamic warnings in MIDI. New attractions include rewritten
font-selection routines.  See the *note Changes:: and *note Old
downloads::.

March 14, 2004
..............

The linuxmusician.com interview
(http://linuxmusician.com/index.php?option=articles&task=viewarticle&artid=10)
made the slashdot frontpage!
(http://slashdot.org/article.pl?sid=04/03/13/2054227&mode=thread&tid=141&tid=188).

March 11, 2004
..............

linuxmusician.com (http://linuxmusician.com) is running an interview
(http://linuxmusician.com/index.php?option=articles&task=viewarticle&artid=10)
with Han-Wen Nienhuys and Jan Nieuwenhuizen, the main authors of
LilyPond.

March 11, 2004
..............

LilyPond 2.1.30 has editorial fixes for the manual, and experimental
support for page layout in the PostScript backend.  See the *note
Changes:: and *note Old downloads::.

March 9, 2004
.............

LilyPond 2.1.29 fixes a couple of MIDI bugs, and has experimental
support for producing titles with `markup'.

February 29, 2004
.................

In LilyPond 2.1.28 Scheme property functions may be used argument to
`set!'.  In addition, parts of the manual have been proofread and
corrected in this release.  See the *note Changes:: and *note Old
downloads::.

February 24, 2004
.................

LilyPond 2.1.27 takes into account instrument transpositions when
quoting other voices. This release also fixes a number of lyrics
related bugs. See the *note Changes:: and *note Old downloads::.

February 23, 2004
.................

LilyPond 2.1.26 has a new, experimental feature for quoting other
voices in instrumental parts. This can be used to produce cue notes.
More information in the *note Changes::.  *note Old downloads::

February 18, 2004
.................

LilyPond 2.1.25 fixes many bugs, and changes the conventions for
altering accidental rules.  *note Old downloads::

February 16, 2004
.................

LilyPond 2.1.24 has a big internal rewrite. One of its practical
consequences is that `\with' now also works with `Score' contexts.
Further 2.1.23, which was not announced here, fixes a few bugs caused
by the change of `\property' syntax and has updates in the Program
Reference document.  More information in the *note Changes::.  *note
Old downloads::

February 13, 2004
.................

LilyPond 2.1.22 has a simplification of the `\property' syntax: it is
shorter and more consistent now.  More information in the *note
Changes::.  *note Old downloads::

February 12, 2004
.................

In LilyPond 2.1.21, output tweaks can be done at multiple levels of the
context hierarchy.  In addition, it has a bunch of bugfixes,
improvements in the documentation.  More information in the *note
Changes::.  *note Old downloads::

February 9, 2004
................

LilyPond 2.1.20  has MIDI output for drums.  It also sports a
completely rewritten lilypond-book script, which is cleaner, shorter,
and faster.  It also has a large number of bugfixes.  More information
in the *note Changes::.  *note Old downloads::

February 5, 2004
................

LilyPond 2.1.19 has rewritten support for drum notation. This release
also makes some long-standing cleanups: the removal of `Thread' (all
functionality is now moved into `Voice') and Lyrics (functionality
moved to `LyricsVoice')  context.  More information in the *note
Changes::.  *note Old downloads::

February 4, 2004
................

LilyPond 2.1.18 is out. This release has the new part-combiner
installed by default, and a similar implementation of `autochange'.
More information in the *note Changes::.  *note Old downloads::

February 2, 2004
................

LilyPond 2.1.17 is out. It adds texts (solo, a due) for the part
combiner. It also reinstates the `--safe' option which prevents havoc
by Scheme exploits.  More information in the *note Changes::.

January 28, 2004
................

LilyPond 2.1.16 is out; its main feature is that it fixes the autobeams
gaffe of 2.1.15.  The part-combiner has been tested successfully on
larger pieces. In the near future, expect more part-combining eye-candy.
More information in the *note Changes::.  *note Old downloads::

January 26, 2004
................

LilyPond 2.1.15 further improves the part-combiner, and fixes many
bugs, among others in pedal brackets and finger positioning.  More
information in the *note Changes::. *note Old downloads::

January 21, 2004
................

LilyPond 2.1.14 has the first release of the new part combiner. If you
have scores that use part-combining, please consider giving it a
test-run. In addition many bugs relating to mixed staff sizes have been
fixed.  More information in the *note Changes::. *note Old downloads::

January 20, 2004
................

The lilypond.org domain has been moved to a new server. This will
result in better connectivity and more bandwidth.  Due to security
concerns, the new server  does not offer FTP access, but only HTTP
downloads.

January 20, 2004
................

LilyPond 2.1.13  fixes a small but nasty bug in side-positioning
placement, and some bugs in tuplet, tie and accidental formatting. This
release contains rudimentary work on a new part-combiner.  *note Old
downloads::

January 19, 2004
................

LilyPond 2.1.12 fixes many bugs and improves formatting of ottava
brackets.  More information in the *note Changes::. *note Old
downloads::

January 18, 2004
................

LilyPond 2.1.11 is now also available for Windows!  For downloading, go
here (http://www.inf.bme.hu/~berti/lilypond/).

January 17, 2004
................

In 2.1.11, the mechanism for setting staff size and page is much
simplified. In addition there are improvements in the notehead shape,
and there is balloon help!  More information in the *note Changes::.
*note Old downloads::

January 16, 2004
................

LilyPond 2.1.10 has a load of bugfixes and a shorter syntax for octave
checks. More information in the *note Changes::. *note Old downloads::

January 13, 2004
................

LilyPond 2.1.9 has a new mechanism for adding lyrics to melodies. It is
now possible to have different melismatic variations for each stanza.
More information in the *note Changes::. *note Old downloads::

January 9, 2004
...............

LilyPond 2.1.8 has an important new feature: it is now possible to use
`\property' to tune the appearance of spanning objects like
`StaffSymbol' and `SystemStartBrace'.  In addition, contexts may be
modified with `\remove' and `\consists' for individual music
expressions.  More information in the *note Changes::. *note Old
downloads::

January 7, 2004
...............

An update to the stable branch, version 2.0.2, was released today. It
contains a couple of minor bugfixes.  *note Old downloads::

January 6, 2004
...............

LilyPond 2.1.7 continues to improve the layout of the Schubert test
piece; this release focuses on dot placement and multi measure rests
centering.  More information in the *note Changes:: and download here
(install/#2.1).

January 4, 2004
...............

LilyPond 2.1.6 continues to improve the layout of  lyrics.  More
information in the release notes
(@DOC@v2.1/Documentation/topdocs/out-www/NEWS.html) and download here
(install/#2.1).

January 2, 2004
...............

in LilyPond 2.1.5, the lyric alignment is completely revamped, and now
matches my Edition Peters version of the Schubert song S&auml;ngers
Morgen.  More information in the *note Changes:: and download here
(install/#2.1).

December 30, 2003
.................

LilyPond 2.1.4 is released. Font shapes and linethickness are now truly
different for different staff sizes, thus lending an engraved look to
scores printed in smaller type too. See the *note Changes:: and
download here (install/#2.1).

December 23, 2003
.................

LilyPond 2.1.3 released.  Interpreting and formatting is now done while
parsing the file. This allows for Scheme manipulation of music, and
could be used to implement experimental MusicXML output (volunteers to
implement this are welcome!)  See the *note Changes:: and download here
(install/#2.1).

December 17, 2003
.................

LilyPond 2.1.2 released. This release has a new mechanism for setting
font sizes, which combines different font design sizes and continuous
font scaling. See the *note Changes:: and download here (install/#2.1).

December 16, 2003
.................

LilyPond 2.1.1 released. This release wraps together all the small
fixes made during Han-Wen's absence. See the *note Changes:: and
download here (install/#2.1).

October 11, 2003
................

LilyPond 2.1.0 released. See the *note Changes:: and download here
(install/#2.1).

October 11, 2003
................

LilyPond 2.0.1  binaries for Mandrake 9.1 available from here
(http://rpm.nyvalls.se/sound9.1.html) thanks to Heikki Junes.

October 9, 2003
...............

LilyPond 2.0.1  binaries for Slackware 9 available from here
(install/#2.0), thanks to Ricardo Hoffman.

October 5, 2003
...............

LilyPond 2.0.1 binaries are available for Macos X, many thanks to
Matthias Neeracher.  *note Old downloads::

October 4, 2003
...............

LilyPond 2.0.1 binaries are available for Windows (Cygwin version 1.5).
*note Old downloads::.  Thanks to Bertalan Fodor, our new Cygwin
maintainer!

September 29, 2003
..................

LilyPond 2.0.1 is released. It contains minor bugfixes.  See the *note
Changes:: or download here (install/#2.0) directly.

September 27, 2003
..................

PlanetCCRMA has been updated to include LilyPond 2.0. Go here
(http://www-ccrma.stanford.edu/planetccrma/software/soundapps.html#lilypond)
to download.  Thanks to Fernando Pablo Lopez-Lezcano!

September 24, 2003
..................

LilyPond 2.0.0 is released. The focus of this release is cleanups of
the syntax: entering music is now much easier and more efficient. Read
the announcement here (announce-v2.0.html), or go to the download page
(install/#2.0) directly.

September 24, 2003
..................

LilyPond 1.9.10 is released. This is the final LilyPond 2.0 release
candidate. Check the *note Changes:: and download here (install/).

September 23, 2003
..................

LilyPond 1.9.9 is released. This is the second LilyPond 2.0 prerelease.
Check the *note Changes:: and download here (install/).

September 19, 2003
..................

LilyPond 1.9.8 is released. This is the first LilyPond 2.0 prerelease.
Check the *note Changes:: and download here (install/).

September 17, 2003
..................

LilyPond 1.9.7 is released. LilyPond now has support for quarter tone
accidentals!  *note Old downloads::

September 16, 2003
..................

LilyPond 1.9.6 is released.  It has a lot of minor fixes and updates.
*note Old downloads::

September 10, 2003
..................

LilyPond 1.9.5 is released.  With this release, the 1.9 branch is
feature complete. After some stabilization and documentation work, 2.0
will be available in a few weeks.  *note Old downloads::

September 9, 2003
.................

LilyPond 1.8.2 is released. This release fixes a couple of minor bugs.
*note Old downloads::

September 7, 2003
.................

LilyPond 1.8 binaries are available for Windows (Cygwin version 1.5).
*note Old downloads::

August 31, 2003
...............

LilyPond 1.9.4 is released.  _This is an experimental release_: read the
announcement
(http://mail.gnu.org/archive/html/lilypond-devel/2003-08/msg00133.html)
before trying.

August 31, 2003
...............

LilyPond 1.8 binaries for slackware available. Get them here (install/).

August 31, 2003
...............

LilyPond 1.9.3 is released.  This release supports tagging for music
version control, and has better fingering placement flexibility.  Read
the *note Changes:: and get it here (download#1.9).

August 28, 2003
...............

LilyPond 1.9.2 is released. Read the *note Changes:: and get it here
(download#1.9).

August 26, 2003
...............

LilyPond 1.9.1 is released. Read the *note Changes:: and get it here
(download#1.9).

August 25, 2003
...............

The  LilyPond 1.9 development release is available. Read the *note
Changes:: and get it here (download#1.9).

August 25, 2003
...............

Mandrake 9.1 RPMS available, get them here
(http://rpm.nyvalls.se/sound9.1.html).

August 21, 2003
...............

LilyPond 1.8.1 was released. Get it here (install/), or read the *note
Changes::.

August 18, 2003
...............

PlanetCCRMA (eg. RedHat 8 and 9) has been updated to 1.8.  Download
here.
(http://www-ccrma.stanford.edu/planetccrma/software/soundapps.html#lilypond)

August 7, 2003
..............

LilyPond 1.8 is released.  Read *note Changes:: and get it here
(install/).

August 7, 2003
..............

New website went live!

August 6, 2003
..............

Announced new website.

August 1, 2003
..............

LilyPond 1.7.30 released.

July 30, 2003
.............

Website: present treatise (about/automated-engraving/index.html) about
music engraving, music printing software, and LilyPond's unique
faculties.

July 29, 2003
.............

1.7.29 - release candidate 4 has been released.  Packages for Red Hat,
Debian, Cygwin are available (install/).



Tag Table:
Node: Top469
Node: Introduction1845
Node: Features3501
Node: Examples6835
Node: Freedom9766
Node: Background12919
Node: Productions13555
Node: Testimonials15243
Node: Text input20718
Node: Alternate input23799
Node: Download29407
Node: Unix31572
Node: MacOS X34067
Node: Windows36689
Node: Source38775
Node: Old downloads39466
Node: GPL39745
Node: Manuals77482
Node: Learning79708
Node: Glossary80829
Node: Essay81747
Node: Notation82689
Node: Usage83655
Node: Snippets84506
Node: Web85691
Node: FAQ86433
Node: Changes87628
Node: Extend88367
Node: Internals89090
Node: Translated90480
Node: All90687
Node: FDL92612
Node: Community117965
Node: Contact118816
Node: Tiny examples122125
Node: Bug reports123737
Node: Help us125930
Node: Development129865
Node: Authors133847
Node: Publications141848
Node: Old news145679

End Tag Table


Local Variables:
coding: utf-8
End:
