NAME = documentation
LANGS = $(shell $(PYTHON) $(top-src-dir)/python/langdefs.py)
MANUALS_SUBDIRS = usage automated-engraving contributor essay \
- general learning notation extending
+ web learning notation extending
SUBDIRS = $(MANUALS_SUBDIRS) snippets logo pictures misc po css topdocs \
included $(LANGS)
STEPMAKE_TEMPLATES = documentation texinfo tex omf
MAIN_INFO_DOC = lilypond-notation
INFO_DOCS = lilypond-usage lilypond-changes lilypond-contributor lilypond-internals \
lilypond-essay lilypond-learning lilypond-notation music-glossary \
- lilypond-general lilypond-extending
+ lilypond-web lilypond-extending
ifeq ($(out),www)
INFO_DOCS += lilypond-snippets
endif
### Web site idiosyncrases
-$(outdir)/general/index.html: TEXI2HTML_INIT = $(WEB_TEXI2HTML_INIT)
-$(outdir)/general/index.html: TEXI2HTML_SPLIT = $(WEB_TEXI2HTML_SPLIT)
+$(outdir)/web/index.html: TEXI2HTML_INIT = $(WEB_TEXI2HTML_INIT)
+$(outdir)/web/index.html: TEXI2HTML_SPLIT = $(WEB_TEXI2HTML_SPLIT)
-#$(outdir)/general/index.html:
-# $(TEXI2HTML) $(TEXI2HTML_SPLIT) $(TEXI2HTML_FLAGS) --output $(outdir)/ $(outdir)/general.texi
+#$(outdir)/web/index.html:
+# $(TEXI2HTML) $(TEXI2HTML_SPLIT) $(TEXI2HTML_FLAGS) --output $(outdir)/ $(outdir)/web.texi
###########
### Targets
$(MAKE) -C pictures WWW-1
ln -sf ../pictures/$(outdir) $@
-$(outdir)/general.texi: $(outdir)/examples
+$(outdir)/web.texi: $(outdir)/examples
$(outdir)/examples:
- $(MAKE) -C general/examples
- ln -sf ../general/examples/$(outdir) $@
+ $(MAKE) -C web/examples
+ ln -sf ../web/examples/$(outdir) $@
endif
# Ugh, using '%' twice not possible
test -e po/$(ISOLANG).po || cp po/lilypond-doc.pot po/$(ISOLANG).po
@echo "*** Please add a language definition for $(ISOLANG) in python/langdefs.py ***"
-TRANSLATION_DIRS = general texidocs
+TRANSLATION_DIRS = web texidocs
TRANSLATION_FILES = $(shell git ls-files $(ISOLANG) | grep -v GNUmakefile)
TELY_FILES = $(call src-wildcard,$(ISOLANG)/*.tely)
pdf, and info formats. The sources are
@verbatim
-Documentation/general.texi
-Documentation/general/*.texi
+Documentation/web.texi
+Documentation/web/*.texi
@end verbatim
Unless otherwise specified, follow the instructions and policies
Beachten Sie, dass es eine Reihe an Texteditoren mit besserer
Unterstützung für LilyPond gibt. Mehr dazu im Abschnitt
@rprogram{Unterstützung von Texteditoren}.
-@c FIXME: link to @rgeneral{Alternate input}
+@c FIXME: link to @rweb{Alternate input}
@warning{Das erste Mal, wenn Sie LilyPond benutzen, kann es eine
Minute oder länger dauern, weil das Programm zuerst alle Schriftarten,
@translationof MacOS X
@warning{Diese Anweisungen gehen davon aus, dass Sie den installierten
-LilyPad-Editor benutzen. Wenn Sie eins der Programme benutzen, die in @rgeneral{Alternate input} beschrieben sind, schauen
+LilyPad-Editor benutzen. Wenn Sie eins der Programme benutzen, die in @rweb{Alternate input} beschrieben sind, schauen
Sie bitte in der Dokumentation nach, wenn Sie Probleme damit haben,
eine Datei zu kompilieren.}
@translationof Windows
@warning{Diese Anweisungen gehen davon aus, dass Sie den installierten
-LilyPad-Editor benutzen. Wenn Sie eins der Programme benutzen, die in @rgeneral{Alternate input} beschrieben sind, schauen
+LilyPad-Editor benutzen. Wenn Sie eins der Programme benutzen, die in @rweb{Alternate input} beschrieben sind, schauen
Sie bitte in der Dokumentation nach, wenn Sie Probleme damit haben,
eine Datei zu kompilieren.}
@translationof Command-line
@warning{Diese Anweisungen gehen davon aus, dass Sie den installierten
-LilyPad-Editor benutzen. Wenn Sie eins der Programme benutzen, die in @rgeneral{Alternate input} beschrieben sind, schauen
+LilyPad-Editor benutzen. Wenn Sie eins der Programme benutzen, die in @rweb{Alternate input} beschrieben sind, schauen
Sie bitte in der Dokumentation nach, wenn Sie Probleme damit haben,
eine Datei zu kompilieren.}
@ref{\TEXT\,,\DISPLAY\,changes-big-page,Changes}
@end macro
-@macro rgeneral{TEXT}
+@macro rweb{TEXT}
@vindex \TEXT\
-@ref{\TEXT\,,,general-big-page,General Information}
+@ref{\TEXT\,,,web-big-page,General Information}
@end macro
-@macro rgeneralnamed{TEXT,DISPLAY}
+@macro rwebnamed{TEXT,DISPLAY}
@vindex \TEXT\
-@ref{\TEXT\,,\DISPLAY\,general-big-page,General Information}
+@ref{\TEXT\,,\DISPLAY\,web-big-page,General Information}
@end macro
@macro ressay{TEXT}
@ref{\TEXT\,,\DISPLAY\,lilypond-changes,Changes}
@end macro
-@macro rgeneral{TEXT}
+@macro rweb{TEXT}
@vindex \TEXT\
-@ref{\TEXT\,,,lilypond-general,General Information}
+@ref{\TEXT\,,,lilypond-web,General Information}
@end macro
-@macro rgeneralnamed{TEXT,DISPLAY}
+@macro rwebnamed{TEXT,DISPLAY}
@vindex \TEXT\
-@ref{\TEXT\,,\DISPLAY\,lilypond-general, General Information}
+@ref{\TEXT\,,\DISPLAY\,lilypond-web, General Information}
@end macro
@macro ressay{TEXT}
@ref{\TEXT\,,\DISPLAY\,changes,Changes}
@end macro
-@macro rgeneral{TEXT}
+@macro rweb{TEXT}
@lilyvindex{\TEXT\}
-@ref{\TEXT\,,,general,General Information}
+@ref{\TEXT\,,,web,General Information}
@end macro
-@macro rgeneralnamed{TEXT,DISPLAY}
+@macro rwebnamed{TEXT,DISPLAY}
@lilyvindex{\TEXT\}
-@ref{\TEXT\,,\DISPLAY\,general,General Information}
+@ref{\TEXT\,,\DISPLAY\,web,General Information}
@end macro
@macro ressay{TEXT}
ISOLANG = fr
depth = ../..
-SUBDIRS = general learning notation texidocs usage
+SUBDIRS = web learning notation texidocs usage
STEPMAKE_TEMPLATES = documentation
LOCALSTEPMAKE_TEMPLATES = lilypond ly doc-i18n-root
-EXTRA_DIST_FILES = general.texi
+EXTRA_DIST_FILES = web.texi
include $(depth)/make/stepmake.make
+++ /dev/null
-\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
-@c This file is part of general.texi
-@ignore
- Translation of GIT committish: 1b3da70d81938d19a2b107382bbe25a267cf130b
-
- When revising a translation, copy the HEAD committish of the
- version that you are working on. See TRANSLATION for details.
-@end ignore
-
-
-@setfilename general.info
-@settitle LilyPond -- la notation musicale pour tous
-@documentencoding UTF-8
-@documentlanguage fr
-@set web
-@include macros.itexi
-@afourpaper
-@ifnottex
-@node Top
-@top LilyPond
-
-@translationof Top
-
-@c Translators: Test
-
-@chapheading
-@end ifnottex
-@finalout
-@titlepage
-@title LilyPond
-@subtitle
-@titlefont{New Website}
-@author Équipe de développement de LilyPond
-@quotation
-@end quotation
-@vskip 20pt
-@end titlepage
-@copying
-@quotation
-@end quotation
-@end copying
-@divId{pageHeader}
-@heading LilyPond
-
-... la notation musicale pour tous
-@divEnd
-@c @imageId{cmws,web-clef-g-eight-alpha.png,Catchy Musical Web Snippet}
-@imageId{lilylogo,double-lily-modified3.png,LilyPond logo}
-@c @im ageId{cmws,web-snippet-alpha.png,Catchy Musical Web Snippet}
-@divId{quickSummary}
-@subheading Qu'est-ce que c'est LilyPond?
-TODO FIXME FRENCH
-@divClass{align-right}
-@divEnd
-@divEnd
-@divId{news}
-@include news-front.itexi
-@divClass{float-right}
-@divEnd
-@divEnd
-@divId{latestVersion}
-@subheading Quick links
-@c TODO: javascript to detect OS and suggest download?
-@subsubheading Stable
-@ref{Download, Download 2.12.3}
-@ref{Manuals, Manuals 2.12.3}
-@subsubheading Unstable
-@ref{Development, Download 2.13.2}
-@ref{Development, Manuals 2.13.2}
-@divEnd
-@divClass{hide}
-@menu
-* Introduction::
-* Download::
-* Manuals::
-* Community::
-@end menu
-
-@divEnd
-@contents
-@include general/introduction.itexi
-@include general/download.itexi
-@include general/manuals.itexi
-@include general/community.itexi
-@bye
-
+++ /dev/null
-depth = ../../..
-
-LOCALSTEPMAKE_TEMPLATES = ly
-
-include $(depth)/make/stepmake.make
+++ /dev/null
-\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
-@c This file is part of general.texi
-@ignore
- Translation of GIT committish: 1b3da70d81938d19a2b107382bbe25a267cf130b
-
- When revising a translation, copy the HEAD committish of the
- version that you are working on. See TRANSLATION for details.
-@end ignore
-
-
-@c -*- coding: utf-8; mode: texinfo; -*-
-@node Community
-@unnumbered Community
-
-@untranslated
-
-
-@divClass{column-center-top}
-@subheading Interacting with the community
-@ref{Contact}: get help, discuss, and keep in touch!
-@ref{Tiny examples}: these are @emph{highly} recommended when
-@ref{Bug reports}: something went wrong.
-@divEnd
-@divClass{column-left-bottom}
-@subheading Making LilyPond better
-@ref{Help us}: your assistance is requested.
-@ref{Development}: for contributors and testers.
-@ref{Authors}: the people who made LilyPond what it is today.
-@divEnd
-@divClass{column-right-bottom}
-@subheading Miscellaneous
-@ref{Publications}: what we wrote, and have had written about us.
-@ref{Old news}: an archive.
-@divEnd
-@divClass{hide}
-@menu
-* Contact::
-* Tiny examples::
-* Bug reports::
-* Help us::
-* Development::
-* Authors::
-* Publications::
-* Old news::
-@end menu
-
-@divEnd
-@node Contact
-@unnumberedsec Contact
-
-@untranslated
-
-
-@divClass{column-left-bottom}
-@subheading User Discussions and Help
-@subsubheading User mailist: @code{lilypond-user@@gnu.org}
-@quotation
-@end quotation
-@subsubheading IRC
-@subsubheading Other languages
-@divEnd
-@divClass{column-right-top}
-@subheading Stay Informed
-@subsubheading LilyPond Report
-@subsubheading Releases mailist: @code{info-lilypond@@gnu.org}
-@quotation
-@c don't include gmane posting here. -gp
-@end quotation
-@divEnd
-@divClass{column-right-bottom}
-@subheading Developer Discussion
-@subsubheading Developer mailist: @code{lilypond-devel@@gnu.org}
-@quotation
-@end quotation
-@subsubheading Bug mailist: @code{bug-lilypond@@gnu.org}
-@quotation
-@c don't include gmane posting here. -gp
-@end quotation
-@divEnd
-@node Tiny examples
-@unnumberedsec Tiny examples
-
-@untranslated
-
-
-@divClass{column-center-top}
-@subheading What are @qq{Tiny examples}?
-@divEnd
-@divClass{column-left-bottom}
-@subheading Why create them?
-@divClass{keep-bullets}
-@divEnd
-@divEnd
-@divClass{column-right-bottom}
-@subheading How do I create them?
-@divClass{keep-bullets}
-@divEnd
-@divEnd
-@node Bug reports
-@unnumberedsec Bug reports
-
-@untranslated
-
-
-@divClass{column-center-top}
-@subheading Step 1: Known bugs
-@divEnd
-@divClass{column-left-bottom}
-@subheading Step 2: Creating a bug report
-@divEnd
-@divClass{column-right-bottom}
-@subheading Step 3: Sending a bug report
-@divEnd
-@node Help us
-@unnumberedsec Help us
-
-@untranslated
-
-
-@subheading This document
-@subsubheading High priority / blocks release
-@subsubheading Low priority / may never
-@node Development
-@unnumberedsec Development
-
-@untranslated
-
-
-@divClass{heading-center}
-@heading Development materials for LilyPond 2.13.3
-@ref{Manuals}.}
-@divEnd
-@divClass{column-left-bottom}
-@subheading Download
-@subheading Manuals
-@divEnd
-@divClass{column-right-bottom}
-@subheading Contributors' Guide
-@divEnd
-@node Authors
-@unnumberedsec Authors
-
-@untranslated
-
-
-@node Publications
-@unnumberedsec Publications
-
-@untranslated
-
-
-@divClass{column-center-top}
-@subheading What we wrote
-@divClass{keep-bullets}
-@divEnd
-@divEnd
-@divClass{column-center-bottom}
-@subheading What others wrote
-@divClass{keep-bullets}
-@divEnd
-@divEnd
-@node Old news
-@unnumberedsec Old news
-
-@untranslated
-
-
-@include general/news.itexi
-
-@c -- SKELETON FILE --
+++ /dev/null
-\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: fr -*-
-@c This file is part of general.texi
-@ignore
- Translation of GIT committish: dab17828471057f4e12c0d80777ff9bb4c5b2309
-
- When revising a translation, copy the HEAD committish of the
- version that you are working on. See TRANSLATION for details.
-@end ignore
-
-
-@c -*- coding: utf-8; mode: texinfo; -*-
-@node Download
-@unnumbered Download
-
-@untranslated
-
-
-@divClass{heading-center}
-@heading Downloads for LilyPond 2.12.2
-@divEnd
-@divClass{column-left-top}
-@subheading For users
-@c TODO: duplicate to avoid underlined refs in HTML? icky.
-@ref{Unix, @sourceimage{logo-linux} @sourceimage{logo-freebsd}}
-@ref{Unix, Unix (Linux and FreeBSD)}
-@ref{MacOS X, @sourceimage{logo-macosx}}
-@ref{MacOS X, MacOS X}
-@ref{Windows, @sourceimage{logo-windows}}
-@ref{Windows, Microsoft Windows}
-@divEnd
-@divClass{column-right-top}
-@subheading For developers
-@ref{Source}:
-@ref{Old downloads}:
-@divEnd
-@divClass{column-center-bottom}
-@subheading Software License
-@divEnd
-@divClass{color1}
-@subheading Sponsors
-@sourceimage{VTlogo_ITF} @sourceimage{lao_banner_06_on_white_demo}
-@subheading Legalese
-@divClass{legal}
-@divEnd
-@divEnd
-@divClass{hide}
-@menu
-* Unix::
-* MacOS X::
-* Windows::
-* Source::
-* Old downloads::
-* GPL::
-@end menu
-
-@divEnd
-@node Unix
-@unnumberedsec Unix
-
-@untranslated
-
-
-@divClass{column-center-top}
-@subheading Generic Packages or Distribution-Specific Packages?
-@divEnd
-@divClass{column-left-top}
-@subheading Generic Packages
-@subsubheading Download
-@sourceimage{logo-linux}
-@sourceimage{logo-linux}
-@sourceimage{logo-linux}
-@sourceimage{logo-freebsd}
-@sourceimage{logo-freebsd}
-@subsubheading Install
-@subsubheading Uninstall
-@divEnd
-@divClass{column-right-top}
-@subheading Distribution-specific Packages
-@sourceimage{logo-fedora}
-@sourceimage{logo-ubuntu}
-@sourceimage{logo-slackware}
-@sourceimage{logo-debian}
-@sourceimage{logo-suse}
-@divEnd
-@divClass{column-center-bottom}
-@subheading Legalese
-@divClass{legal}
-@divEnd
-@divEnd
-@node MacOS X
-@unnumberedsec MacOS X
-
-@untranslated
-
-
-@divClass{column-left-top}
-@subheading Packages
-@subsubheading Download
-@sourceimage{logo-macosx}
-@sourceimage{logo-macosx}
-@subsubheading Install
-@subsubheading Uninstall
-@divEnd
-@divClass{column-right-top}
-@subheading Running on the command-line
-@subsubheading Using Python scripts on MacOS 10.3 or 10.4
-@c ommand{convert-ly} and @command{lilypond-book} as follows: if the
-@subsubheading MacOS X on the command line
-@c ommand{abc2ly}, and even @command{lilypond} itself --- are included
-@c ommand{lilypond-book}, @command{convert-ly}, @command{abc2ly}, etc.
-@c ode{bin/convert-ly} (or other program name) in the above file.
-@divEnd
-@divClass{column-center-bottom}
-@subheading Legalese
-@divClass{legal}
-@divEnd
-@divEnd
-@node Windows
-@unnumberedsec Windows
-
-@untranslated
-
-
-@divClass{column-left-top}
-@subheading Packages
-@subsubheading Download
-@sourceimage{logo-windows}
-@subsubheading Install
-@subsubheading Uninstall
-@divEnd
-@divClass{column-right-top}
-@subheading Running on the command-line
-@divEnd
-@divClass{column-center-bottom}
-@subheading Legalese
-@divClass{legal}
-@divEnd
-@divEnd
-@node Source
-@unnumberedsec Source
-
-@untranslated
-
-
-@divClass{column-left-bottom}
-@subheading Source tarball
-@divEnd
-@divClass{column-right-bottom}
-@subheading Compiling instructions
-@divEnd
-@node Old downloads
-@unnumberedsec Old downloads
-
-@untranslated
-
-
-@divClass{column-center-top}
-@subheading All versions
-@divEnd
-@node GPL
-@unnumberedsec GPL
-
-@untranslated
-
-
-@divClass{column-center-top}
-@subheading Software license
-@divEnd
-@divClass{column-center-bottom}
-@subheading GNU General Public License version 2
-@include gpl-2.0.itexi
-@divEnd
-
-@c -- SKELETON FILE --
+++ /dev/null
-\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: fr -*-
-@c This file is part of general.texi
-@ignore
- Translation of GIT committish: dab17828471057f4e12c0d80777ff9bb4c5b2309
-
- When revising a translation, copy the HEAD committish of the
- version that you are working on. See TRANSLATION for details.
-@end ignore
-
-
-@c -*- coding: utf-8; mode: texinfo; -*-
-@node Introduction
-@unnumbered Introduction
-
-@untranslated
-
-
-@divClass{column-center-top}
-@subheading Our Goal
-@imageFloat{flat-design.png,right}
-@divEnd
-@divClass{column-left-top}
-@subheading Why use LilyPond?
-@ref{Features}: What can LilyPond do?
-@ref{Examples}: I want to see some music!
-@ref{Freedom}: LilyPond is Free Software.
-@divEnd
-@divClass{column-right-top}
-@subheading Who uses it?
-@ref{Productions}: Real-life use of LilyPond.
-@ref{Testimonials}: What do people say?
-@divEnd
-@divClass{column-center-bottom}
-@subheading Why not use LilyPond?
-@ref{Text input}: You write music as @emph{text}?!
-@divEnd
-@divClass{hide}
-@menu
-* Features::
-* Examples::
-* Freedom::
-* Productions::
-* Testimonials::
-* Text input::
-@end menu
-
-@divEnd
-@node Features
-@unnumberedsec Features
-
-@untranslated
-
-
-@subheading Why switch to LilyPond?
-@subsubheading Excellent classical engraving
-@imageFloat{flat-design.png,right}
-@subsubheading No fiddling
-@subsubheading Text-based input
-@subsubheading Mix music and text
-@imageFloat{lilypond-book.png,right}
-@subsubheading Free software
-@subsubheading Extensible design
-@subsubheading Excellent support
-@divClass{column-center-bottom}
-@subheading Where now?
-@ref{Text input}.
-@divEnd
-@node Examples
-@unnumberedsec Examples
-
-@untranslated
-
-
-@imageClickable{examples/liszt-wagner-small.png, (click to enlarge), examples/liszt-wagner.png, center}
-@subsubheading Classical Music
-@imageClickable{examples/bach-bwv610-small.png, (click to enlarge), examples/bach-bwv610.png, center}
-@subsubheading Complex Notation
-@imageClickable{examples/granados-small.png, (click to enlarge), examples/granados.png, center}
-@subsubheading Early Music
-@imageClickable{examples/ancient-headword-small.png, (click to enlarge), examples/ancient-headword.png, center}
-@subsubheading Modern Music
-@imageClickable{examples/cary-small.png, (click to enlarge), examples/cary.png, center}
-@subsubheading Efficient, flexible creation of performance materials
-@imageClickable{examples/sesto-small.png, (click to enlarge), examples/sesto.png, center}
-@imageClickable{examples/sesto-1-small.png, (click to enlarge), examples/sesto-1.png, center}
-@imageClickable{examples/sesto-2-small.png, (click to enlarge), examples/sesto-2.png, center}
-@subsubheading Tablature
-@imageClickable{examples/bach-tab-example-small.png, (click to enlarge), examples/bach-tab-example.png, center}
-@subsubheading Schenker Graphs
-@imageClickable{examples/bach-schenker-small.png, (click to enlarge), examples/bach-schenker.png, center}
-@subsubheading Vocal Music
-@imageClickable{examples/aucun-snippet-small.png, (click to enlarge), examples/aucun-snippet.png, center}
-@subsubheading Educational Applications
-@imageClickable{examples/theory-small.png, (click to enlarge), examples/theory.png, center}
-@subsubheading Popular Music
-@imageClickable{examples/chart-small.png, (click to enlarge), examples/chart.png, center}
-@subsubheading Large Projects
-@imageClickable{examples/orchestral-small.png, (click to enlarge), examples/orchestral.png, center}
-@divClass{column-center-bottom}
-@subheading Where now?
-@ref{Freedom}. If you've already decided to try LilyPond, first
-@divEnd
-@node Freedom
-@unnumberedsec Freedom
-
-@untranslated
-
-
-@divClass{column-center-top}
-@subheading Free Software
-@ref{GPL, GNU General Public License} and the @ref{FDL, GNU Free
-@divEnd
-@c @divClass{column-left-top}
-@divClass{color2}
-@divClass{keep-bullets}
-@subheading What are the benefits to users?
-@divEnd
-@divEnd
-@c @divClass{column-right-top}
-@divClass{color3}
-@divClass{keep-bullets}
-@subheading Why do LilyPond developers @qq{give away} their work for free?
-@divEnd
-@divEnd
-@divClass{column-center-bottom}
-@subheading Where now?
-@ref{Productions} and sheet music. If you've already decided to
-@divEnd
-@node Productions
-@unnumberedsec Productions
-
-@untranslated
-
-
-@divClass{column-left-top}
-@subheading Concerts
-@divClass{keep-bullets}
-@divEnd
-@divEnd
-@divClass{column-right-top}
-@subheading Published sheet music
-@divClass{keep-bullets}
-@divEnd
-@divEnd
-@divClass{column-center-bottom}
-@subheading Where now?
-@ref{Text input}.
-@divEnd
-@node Testimonials
-@unnumberedsec Testimonials
-
-@untranslated
-
-
-@divClass{testimonial-item}
-@imageFloat{carter-brey.jpg, right}
-@subsubheading @uref{http://nyphil.org/meet/orchestra/index.cfm?page=profile&personNum=7, Carter Brey}, Principal Cellist, New York Philharmonic
-@divEnd
-@divClass{testimonial-item}
-@imageFloat{orm-finnendahl.jpg, left}
-@subsubheading @uref{http://icem-www.folkwang-hochschule.de/~finnendahl/, Orm Finnendahl}, professor of Composition, Musikhochschule Freiburg
-@divEnd
-@divClass{testimonial-item}
-@imageFloat{darius-blasband.jpg, right}
-@subsubheading Darius Blasband, composer (Brussels, Belgium)
-@divEnd
-@divClass{testimonial-item}
-@subsubheading Kieren MacMillan, composer (Toronto, Canada)
-@divEnd
-@divClass{testimonial-item}
-@subsubheading Chris Cannam, lead programmer of the @uref{http://www.rosegardenmusic.com/, RoseGarden} project.
-@divEnd
-@divClass{testimonial-item}
-@subsubheading Chris Snyder, @uref{http://www.adoromusicpub.com/, Adoro Music Publishing}
-@divEnd
-@divClass{testimonial-item}
-@subsubheading David Bobroff, Bass Trombone, Iceland Symphony Orchestra
-@divEnd
-@divClass{testimonial-item}
-@subsubheading Vaylor Trucks, Electric guitar player (Yes, @uref{http://www.allmanbrothersband.com/modules.php?op=modload&name=userpage&file=content&page_id=12, related to})
-@divEnd
-@divClass{testimonial-item}
-@subsubheading @uref{http://nicolas.sceaux.free.fr/, Nicolas Sceaux}, @uref{http://www.mutopiaproject.org/, Mutopia} contributor
-@divEnd
-@divClass{testimonial-item}
-@subsubheading @uref{http://www.troff.org/whoswho.html#werner, Werner Lemberg}, Conductor at the Theatre in Koblenz, Germany and distinguished GNU Hacker.
-@divEnd
-@divClass{testimonial-item}
-@subsubheading Paul Davis, developer of @uref{http://jackaudio.org/, JACK} and @uref{http://www.ardour.org/, Ardour}.
-@divEnd
-@divClass{column-center-bottom}
-@subheading Where now?
-@divEnd
-@node Text input
-@unnumberedsec Text input
-
-@untranslated
-
-
-@c TRANSLATORS: so far it's mostly from
-@c http://lilypond.org/web/switch/howto
-@subheading @qq{Compiling} Music
-@imageClickable{examples/nereid-shot-small.png, (click to enlarge), examples/nereid-shot.png, right}
-@subsubheading It's as simple as A B C
-@imageFloat{text-input-1-annotate.png,center}
-@imageFloat{text-input-1-output.png,center}
-@imageFloat{text-input-2-annotate.png,center}
-@imageFloat{text-input-2-output.png,center}
-@subsubheading Pop music
-@imageFloat{text-input-pop-annotate.png,center}
-@imageFloat{text-input-pop-output.png,center}
-@subsubheading Orchestral parts
-@imageFloat{text-input-parts-both-annotate.png,center}
-@imageFloat{text-input-parts-single-annotate.png,center}
-@imageFloat{text-input-parts-single-output.png,center}
-@imageFloat{text-input-score-annotate.png,center}
-@imageFloat{text-input-score-output.png,center}
-@subsubheading Beginner Documentation
-@subsubheading Easier editing environments
-@divClass{column-center-bottom}
-@subheading Where now?
-@ref{Freedom} that LilyPond provides, or read about users'
-@ref{Productions} and @ref{Testimonials}.
-@divEnd
-
-@c -- SKELETON FILE --
+++ /dev/null
-\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
-@c This file is part of general.texi
-@ignore
- Translation of GIT committish: 1b3da70d81938d19a2b107382bbe25a267cf130b
-
- When revising a translation, copy the HEAD committish of the
- version that you are working on. See TRANSLATION for details.
-@end ignore
-
-
-@c -*- coding: utf-8; mode: texinfo; -*-
-@node Manuals
-@unnumbered Manuals
-
-@untranslated
-
-
-@divClass{heading-center}
-@heading Documentation for LilyPond 2.12.2
-@divEnd
-@divClass{column-center-top}
-@subheading Introduction
-@divEnd
-@divClass{column-left-top}
-@subheading Regular use
-@divEnd
-@divClass{column-right-top}
-@subheading Infrequent Use
-@divEnd
-@divClass{column-center-bottom}
-@subheading Other material
-@divEnd
-@divClass{hide}
-@menu
-* Learning::
-* Glossary::
-* Essay::
-* Notation::
-* Usage::
-* Snippets::
-* FAQ::
-* Changes::
-* Internals::
-* Translated::
-* Old::
-* FDL::
-@end menu
-
-@divEnd
-@c TRANSLATORS: most of the text in this file came from
-@c LM 1.1 About the documentation (before this section was
-@c removed in July 2009).
-@node Learning
-@unnumberedsec Learning
-
-@untranslated
-
-
-@node Glossary
-@unnumberedsec Glossary
-
-@untranslated
-
-
-@node Essay
-@unnumberedsec Essay
-
-@untranslated
-
-
-@node Notation
-@unnumberedsec Notation
-
-@untranslated
-
-
-@node Usage
-@unnumberedsec Usage
-
-@untranslated
-
-
-@node Snippets
-@unnumberedsec Snippets
-
-@untranslated
-
-
-@node FAQ
-@unnumberedsec FAQ
-
-@untranslated
-
-
-@subheading Where are the graphical canvas, menus, and toolbars?
-@subheading There's a lot of documentation! Do I need to read it?
-@subheading That's still a lot of reading! Is it worth it?
-@subheading Something isn't working! How do I fix it?
-@subheading Why do you change the syntax?
-@node Changes
-@unnumberedsec Changes
-
-@untranslated
-
-
-@node Internals
-@unnumberedsec Internals
-
-@untranslated
-
-
-@node Translated
-@unnumberedsec Translated
-
-@untranslated
-
-
-@node Old
-@unnumberedsec Old
-
-@untranslated
-
-
-@node FDL
-@unnumberedsec FDL
-
-@untranslated
-
-
-@divClass{column-center-top}
-@subheading Documentation license
-@divEnd
-@divClass{column-center-bottom}
-@subheading GNU Free Documentation License 1.1
-@include fdl.itexi
-@divEnd
-
-@c -- SKELETON FILE --
+++ /dev/null
-@c -*- coding: utf-8; mode: texinfo; -*-
-@c This file is part of lilypond-general.texi and community.itexi
-
-@c when you add a new item, consider moving the lowest item(s)
-@c into news-old.itexi.
-
-@newsItem
-@subsubheading New Website! @emph{20 Aug 2009}
-
-As you can see, we have a new website design. Many thanks to
-texi2html and CSS for being so flexible!
-
-(FIXME: change date when this is actually announced on lilypond.org)
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.13.3. @emph{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. For changes and download links, see @ref{Development}.
-@newsEnd
-
-
-
-@newsItem
-@subsubheading Hungarian translation! @emph{22 May 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!
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond Report #15. @emph{18 May 2009}
-
-The @emph{LilyPond Report} is a short, informal opinion column
-about the LilyPond project: its team, its world, its community.
-Read it @uref{http://news.lilynet.net/The-LilyPond-Report-15,
-here}!
-@newsEnd
-
-
+++ /dev/null
-@c -*- coding: utf-8; mode: texinfo; -*-
-
-@ignore
-
-NOTE:
-
- * avoid "HERE" as name for links, use descriptive link names like
- @uref{,Download LilyPond 2.5.16}
-
- * avoid putting links in running text. They make text harder to read.
- Preferably: (@uref{,...}, etc. )
-
- * use a descriptive title in @subsubheading
-
- * writing date in "Month DD, YYYY" format is required for
- generating the RSS feed; in case the message (and thus the date)
- is not in English, you must write a well-formed date in English
- like above in a comment between the closing brace of @emph and the
- following line
- (see "Japanese translation" below for an example).
-
- * Split news items in small chunks. It's OK to have more than 1 item
- on one day.
-
-
-FIXME
-
- * add macro for long Google issues list URL
-@end ignore
-
-@newsItem
-@subsubheading New Website! @emph{20 Aug 2009}
-
-As you can see, we have a new website design. Many thanks to
-texi2html and CSS for being so flexible!
-
-(FIXME: change date when this is actually announced on lilypond.org)
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.13.3. @emph{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. For changes and download links, see @ref{Development}.
-@newsEnd
-
-
-
-@newsItem
-@subsubheading Hungarian translation! @emph{22 May 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!
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond Report #15. @emph{18 May 2009}
-
-The @emph{LilyPond Report} is a short, informal opinion column
-about the LilyPond project: its team, its world, its community.
-Read it @uref{http://news.lilynet.net/The-LilyPond-Report-15,
-here}!
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.13.3. @emph{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.@*
-@ref{Changes},
-@ref{Development}.
-@newsEnd
-
-
-@newsItem
-@subsubheading A LilyPond weboldala magyarul. @emph{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 @code{harmathdenes AT gmail.com} címre!
-<p align="right">Harmath Dénes, a LilyPond honosítási projekt
-vezetője
-@newsEnd
-
-
-@newsItem
-@subsubheading The LilyPond Report #15. @emph{May 18, 2009}
-
-The @emph{LilyPond Report} is a short, informal opinion column about the LilyPond project:
-its team, its world, its community.
-Follow @uref{http://news.lilynet.net/The-LilyPond-Report-15,this link}
-to read the full issue...
-@newsEnd
-
-
-@newsItem
-@subsubheading The LilyPond Report #14. @emph{April 13, 2009}
-
-The @emph{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 @uref{http://news.lilynet.net/The-LilyPond-Report-14,this link} to read the full issue...
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.12.2 and 2.13.0 — @emph{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.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.12.0 @qq{Rune} — @emph{December 27, 2008}
-
-A new stable release of LilyPond is available.
-@*
-@uref{announce-v2.12,Announcement},
-@ref{Changes},
-@ref{Download}.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.65 — Release Candidate. @emph{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.@*
-@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_65&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{Changes},
-@ref{Old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.64. @emph{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.
-@*
-@ref{Changes},
-@ref{Old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.63. @emph{October 29, 2008}
-
-LilyPond 2.11.63 is available. This release has lots of updates to the
-documentation and translations.
-@ref{Old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.62 – Release Candidate. @emph{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 @code{\tempo} command, this release has lot of updates
-to Spanish and German documentation translations, and the
-stylesheet for HTML documentation has been improved.
-@*
-@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_62&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{Old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.61 available. @emph{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.
-@*
-@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_61&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{Changes},
-@ref{Old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.60 available. @emph{September 25, 2008}
-
-LilyPond 2.11.60 has been released. A new style of double repeat
-bar line has been added, and @code{printallheaders} variable in
-score block has been renamed to @code{print-all-headers}.
-@ref{Old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.59 available. @emph{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.
-@ref{Old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.58 available. @emph{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.
-@*
-@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_58&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{Changes},
-@ref{Old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.57 available. @emph{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.
-@*
-@ref{Changes},
-@ref{Old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.56 available. @emph{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 @code{\pointAndClickOn},
-@code{\pointAndClickOff} have also been added.
-@*
-@ref{Changes},
-@ref{Old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.55 available. @emph{August 6, 2008}
-
-LilyPond 2.11.55 is out. This release fixes several bugs, and for octavation brackets
-@code{set-octavation} has been replaced by a more user-friendly command, @code{\ottava}.
-@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_55&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{Old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.54 available. @emph{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 @code{short-indent}
-so that short instrument names are no longer indented in the margin.
-@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_54&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{Old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.53 available. @emph{July 23, 2008}
-
-LilyPond 2.11.53 is out. This release fixes a lot of bugs.
-@*
-@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_53&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{Old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.52 available. @emph{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. @ref{Changes},
-@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_52&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{Old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.51 available. @emph{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 @code{fret-diagram-details} property.
-@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_51&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{Old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.50 available. @emph{July 2, 2008}
-
-Release 2.11.50 adds support for metronome marks with text, and
-backslashed numbers for figured bass, contributed by
-Reinhold Kainhofer.
-@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_50&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{Old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading The LilyPond Report #13. @emph{June 23, 2008}
-
-This short, informal, weekly opinion column is about the LilyPond project: its team, its world, its community.
-Follow @uref{http://valentin.villenave.info/The-LilyPond-Report-13,this link} to read the full issue...
-@newsEnd
-
-
-@newsItem
-@subsubheading The LilyPond Report #12. @emph{June 16, 2008}
-
-This short, informal, weekly opinion column is about the LilyPond project: its team, its world, its community.
-Follow @uref{http://valentin.villenave.info/The-LilyPond-Report-12,this link} to read the full issue...
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.49 released. @emph{June 12, 2008}
-
-LilyPond 2.11.49 is out. It fixes a number of bugs, including bugs in beams formatting.
-@*
-@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_49&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{Old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.48 released. @emph{June 9, 2008}
-
-LilyPond 2.11.48 is out. This release fixes a few bugs, and
-@code{\compressMusic} has been renamed
-to @code{\scaleDurations}.
-@*
-@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_48&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{Old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading The LilyPond Report #11. @emph{June 9, 2008}
-
-This short, informal, weekly opinion column is about the LilyPond project: its team, its world, its community.
-Follow @uref{http://valentin.villenave.info/The-LilyPond-Report-11,this link} to read the full issue...
-@newsEnd
-
-
-@newsItem
-@subsubheading The LilyPond Report #10. @emph{June 2, 2008}
-
-Welcome to this special tenth issue of the @emph{LilyPond Report}, entirely dedicated to Algorithmic Composition systems.@*
-Follow @uref{http://valentin.villenave.info/The-LilyPond-Report-10,this link} to read the full issue...
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.47 released. @emph{May 28, 2008}
-
-LilyPond now allows all text context properties to be markups,
-except in @code{\lyricmode}. This release also fixes
-regression tests maintenance for developers.
-@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_47&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{Old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.46 available. @emph{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.
-@ref{Changes},
-@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_46&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{Old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading RSS feed - @emph{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.
-@uref{http://lilypond.org/web/lilypond-rss-feed.xml,Feed URL}.
-The info mailing list (see @ref{Contact}) is still used to
-announce releases and special events.
-@newsEnd
-
-
-@newsItem
-@subsubheading The LilyPond Report #9. @emph{May 05, 2008}
-
-Welcome to this ninth issue of the @emph{LilyPond Report}!@*
-This short, informal, weekly opinion column is about the LilyPond project: its team, its world, its community.
-Follow @uref{http://valentin.villenave.info/The-LilyPond-Report-9,this link} to read the full issue...
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.45 available. @emph{April 26, 2008}
-
-Release 2.11.45 fixes a couple of bugs in the formatting
-engine. @code{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.
-@ref{Changes},
-@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_45&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{Old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.44 available. @emph{April 14, 2008}
-
-Release 2.11.44 is available. Support for figured bass and chord
-names has been added to the MusicXML
-converter. @uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_44&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{Old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading lilypond.org日本語訳 (lilypond.org Japanese translation). @emph{2008年4月8日 (April 4, 2008)}
-
-Lilypond.orgのいくつかのページの日本語訳が出来ました。
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.43 available. @emph{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. @uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_43&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{Old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.42 available. @emph{March 9, 2008}
-
-Release 2.11.42 is out. It fixes some formatting and spacing
-bugs. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_42&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading Comparison of music engraving with Finale and LilyPond. @emph{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.
-@uref{http://www.musicbyandrew.ca/finale-lilypond-1.html,Read
-the articles}.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.41 available. @emph{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. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_41&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.37 available. @emph{January 3, 2008}
-
-Release 2.11.37 is available. It has a few bugfixes, and
-documentation changes. (@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.36 available. @emph{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. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_36&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes}, @ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.33 and 2.10.33 available. @emph{September 20, 2007}
-
-Release 2.11.33 is now available.
-(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_33&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
-2.10}, @uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_33&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
-2.11}, @ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.32 available. @emph{September 2, 2007}
-
-Release 2.11.32 is now available.
-(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_32&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes}, @ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.31 available. @emph{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.
-(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_31&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes}, @ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.30 available. @emph{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. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_30&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes}, @ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.10.29 and 2.11.29 available. @emph{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.
-(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_29&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
-2.10}, @uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_29&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
-2.11}, @ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.28 for FreeBSD x86_64. @emph{August 10, 2007}
-
-Release 2.11.28 is now available as a binary installer for
-FreeBSD x86_64. Download
-@uref{http://lilypond.org/download/binaries/freebsd-64/lilypond-2.11.28-1.freebsd-64.sh,the installer} and
-do @emph{sh lilypond-2.11.28-1.freebsd-64.sh} in a command window.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.28 available - @emph{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.
-(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_28&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
-2.11}, @ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.26 available - @emph{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!
-(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_26&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
-2.11}, @ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.10.25 and 2.11.25 available - @emph{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!
-(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_25&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
-2.11}, @uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_25&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
-2.10}, @ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.10.23 and 2.11.23 available - @emph{May 1, 2007}
-This has lots of bugfixes. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_23&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
-2.11}, @uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_23&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
-2.10}, @ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading Übersetzung der Dokumentation - @emph{10. April 2007}
-Die Kapitel 1-5 (der Abschnitt für Anfänger) des
-LilyPond-Benutzerhandbuchs
-sind auf deutsch übersetzt — sie sind erhältlich für
-die @ref{Changes}
-online und @ref{Old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.22 available - @emph{April 10, 2007}
-This release has updates of the dot collision code. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_22&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
-}, @ref{Changes}, @ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.21 available - @emph{March 24, 2007}
-This release has some documentation updates.
-(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_21&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
-}, @ref{Changes}, @ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading Traduction de la documentation en français - @emph{25 février 2007}
-Les chapitres 1 à 4 et 6 du manuel de l'utilisateur sont
-désormais traduits, et disponibles en ligne — @uref{@@DOC@@v2.10/Documentation/user/lilypond/index.fr.html,version
-2.10}, @uref{@@DOC@@v2.11/Documentation/user/lilypond/index.fr.html,version
-2.11}. Les traductions sont également incluses dans la @uref{install,documentation téléchargeable}.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.10.20 and 2.11.20 available - @emph{February 25, 2007}
-This release fixes many bugs.
-(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_20&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
-2.11},
-@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_20&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
-2.10}, @ref{Changes}, @ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.10.19 and 2.11.19 available - @emph{February 18, 2007}
-This release fixes many bugs.
-(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_19&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
-2.11},
-@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_19&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
-2.10}, @ref{Changes}, @ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.18 available - @emph{February 12, 2007}
-This release fixes still more bugs, and included
-singing support through festival contributed by Milan Zamazal. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_18&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
-2.11}, @ref{Changes}, @ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.17 available - @emph{February 9, 2007}
-This release fixes still more bugs.
-(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_17&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
-2.11}, @ref{Changes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.10.16 and 2.11.16 available - @emph{February 4, 2007}
-This release fixes many bugs.
-(@uref{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.11},
-@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_16&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
-2.10},
-@ref{Changes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.10.15 and 2.11.15 available - @emph{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. (@uref{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.11},
-@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_15&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
-2.10},
-@ref{Changes}, @ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.10.14 and 2.11.14 available - @emph{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.
-(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_14&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{Changes}, @ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.10.13 and 2.11.13 available - @emph{January 17, 2007}
-This release fixes a few minor but irritating bugs. In addition, the
-2.11 release has updates of the tutorial.
-(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_13&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{Changes}, @ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.12 available - @emph{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.
-(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_12&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{Changes}, @ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.10.12 available - @emph{January 17, 2007}
-This release mirrors 2.11.12. Notably, it has the same memory
-usage improvements. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_12&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{Changes}, @ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.10.11 available - @emph{January 12, 2007}
-This release mostly has the same fixes as 2.11.11. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_11&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{Changes}, @ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.11 available - @emph{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. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_11&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{Changes}, @ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.10 available - @emph{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. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_10&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{Changes}, @ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.10.10 available - @emph{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 (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_10&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{Changes}, @ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.9 and 2.10.9 available - @emph{January 3, 2007}
-This release has a couple of bugfixes, and —in 2.11.9&mdash
-further improvements in the regression test suite (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_9&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{Changes}, @ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.8 and 2.10.8 available - @emph{January 3, 2007}
-New! Improved! With even more bugfixes! (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_8&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{Changes}, @ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading @code{lilypond.org} auf deutsch - @emph{31. Dezember 2006}
-Die LilyPond-Webseiten sind jetzt auch auf deutsch übersetzt!
-@newsEnd
-
-
-@newsItem
-@subsubheading @code{lilypond.org} en español - @emph{December 29, 2006}
-¡Ya está disponible la versión en español del sitio web de LilyPond!
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.7 and 2.10.7 available - @emph{January 1, 2007}
-New! Improved! With even more bugfixes! (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_7&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{Changes}, @ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.6 available - @emph{December 30, 2006}
-This release supports arbitrary fractional alterations, allowing
-music with different microtonal conventions to be typeset.
-(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_6&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{Changes}, @ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.10.6 available - @emph{December 30, 2006}
-New! Improved! With even more bugfixes!
-(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_6&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{Changes}, @ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.5 available - @emph{December 24, 2006}
-These releases complete the translation infrastructure for
-Documentation.
-(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_5&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{Changes}, @ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.10.5 available - @emph{December 24, 2006}
-New! Improved! With even more bugfixes!
-(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_5&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{Changes}, @ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.4 available - @emph{December 21, 2006}
-The vertical spacing improvements that were introduced in 2.11.0 now work
-within a system as well as between systems. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_4&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{Changes}, @ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.3 available - @emph{December 19, 2006}
-This release has @uref{http://lilypond.org/doc/v2.11/compare-v2.10.3/index.html,graphical
-test results} and several website build improvements. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_3&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{Changes}, @ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.10.3 available - @emph{December 19, 2006}
-This release fixes several bugs.
-(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_3&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LinuxPPC binaries available! - @emph{December 19, 2006}
-From now on, our GUB binary builds include support for Linux/PPC. (@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading Traduction du tutoriel en français. @emph{December 13, 2006}
-Fruit du travail d'une équipe de traducteurs, le tutoriel en
-français est maintenant disponible en ligne. @uref{@@DOC@@v2.10/Documentation/user/lilypond/Tutorial.fr.html,Version
-2.10}, @uref{@@DOC@@v2.11/Documentation/user/lilypond/Tutorial.fr.html,Version
-2.11}.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.2 available - @emph{December 12, 2006}
-This release supports glissandi and harmonics in tablature. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_2&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{Changes}, @ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.10.2 available - @emph{December 12, 2006}
-A new stable release of LilyPond is available. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_2&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.1 available - @emph{December 4, 2006}
-This release has improved support for horizontal spacing. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_1&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{Changes}, @ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.10.1 available - @emph{December 3, 2006}
-A new stable release of LilyPond is available. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_1&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.0 available - @emph{November 27, 2006}
-This release has improved support for vertical spacing. (@ref{Changes}, @ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.10.0 available - @emph{November 11, 2006}
-A new stable release of LilyPond is available. (@uref{announce-v2.10.html,Announcement}, @ref{Changes}, @ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading GIT repository online - @emph{November 11, 2006}
-LilyPond development has moved over its source code to @uref{http://git.or.cz,GIT}, the fast version control
-system. Check out our repository at @uref{http://git.sv.gnu.org/gitweb/?p=lilypond.git;a=summary,gnu.org}.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.9.29 available - @emph{November 5, 2006}
-This release has many more bugfixes. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_9_29&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.9.28 available - @emph{November 3, 2006}
-This release has many more bugfixes. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_9_28&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.9.27 available - @emph{October 28, 2006}
-This release has a new @code{FretBoards} context, and some further
-bugfixes. (@ref{Changes}, @uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_9_27&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading Music streams thesis available - @emph{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
-(@ref{Publications}).
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.9.26 available - @emph{October 20, 2006}
-This release has further bugfixes. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_9_26&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.9.25 available - @emph{October 18, 2006}
-This release has more bugfixes; from now on, binaries are also
-available for x86/64. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_9_25&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.9.24 available - @emph{October 15, 2006}
-This release has support for right hand guitar fingerings, and offers
-some bugfixes. (@ref{Changes},
-@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed2924&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.9.23 available - @emph{October 12, 2006}
-This release cuts fragments of EPS directly from your finished score,
-and makes it easier to insert ties into lyrics. (@ref{Changes}, @ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.9.22 available - @emph{October 9, 2006}
-Test this release candidate for LilyPond 2.10! (@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.9.21 available - @emph{October 4, 2006}
-Test this release candidate for LilyPond 2.10! (@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.9.20 available - @emph{October 3, 2006}
-Test this release candidate for LilyPond 2.10! (@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.9.17 available - @emph{September 2, 2006}
-This release fixes many bugs. Among others, MacOS X QuickTime now
-honors tempo changes are in the MIDI output. (@ref{Changes}, @ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.9.16 available - @emph{August 25, 2006}
-In this release, chords may be partially tied and lyric extenders have
-tunable padding. Moreover, many bugs were fixed
-(@ref{Changes}, @ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.9.15 available - @emph{August 20, 2006}
-This releases fixes many bugs in the 2.9.14 release. (@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.8.6 available - @emph{August 8, 2006}
-This release contains a few minor bugfixes; the source tarball is also
-available. (@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.9.14 available - @emph{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. (@ref{Changes}, @ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.9.13 available - @emph{July 23, 2006}
-This release supports doits and falls, and more tuning options for
-grace note spacing and tuplet brackets. (@ref{Changes}, @ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.9.12 available - @emph{July 18, 2006}
-This release supports pdftex for lilypond-book, and uses PdfTeX for
-generating manuals, so page numbers and references are now clickable.
-(@ref{Changes}, @ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.9.11 available - @emph{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. (@ref{Changes}, @ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.9.10 available - @emph{June 15, 2006}
-This releases fixes a couple of bugs in 2.9.9.
-(@ref{Changes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.9.9 available - @emph{June 15, 2006}
-This releases fixes many bugs in 2.9.8 and earlier.
-(@ref{Changes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.9.8 available - @emph{June 6, 2006}
-2.9.8 has support for different spacing sections within a single
-score, and better infrastructure for automated regression testing.
-(@ref{Changes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.8.4 available - @emph{June 4, 2006}
-2.8.4 fixes some minor bugs, and includes a backport of the
-infrastructure for automated regression testing.
-(@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading First test results available - @emph{June 4, 2006}
-After a week of frantic tweaking, the first automated testing results
-are available. You can now see @uref{http://lilypond.org/doc/v2.9/compare-v2.8.4/index.html,in full
-glory} what features are broken in the development release
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.9.7 available - @emph{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
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.9.6 available - @emph{May 24, 2006}
-This
-release has new features in beam formatting: beams may now be put on
-single stems, and obey the @code{beatGrouping} property. MusicXML
-converter. (@ref{Changes}, @ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading New essay pages! - @emph{May 22, 2006}
-The @emph{Automated Engraving} essay has been updated with material
-from the @uref{http://fisl.softwarelivre.org,FISL} talk, with
-pages on @uref{about/automated-engraving/problem-statement,modeling
-notation} and @uref{about/automated-engraving/scoring-esthetics,algorithms for
-esthetics}. Happy reading!
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.9.5 available - @emph{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.
-(@ref{Changes}, @ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.9.4 available - @emph{May 12, 2006}
-This release has support for feathered beaming, and note head styles in
-the markup @code{\note} command. In addition, it has a lot of updates
-of the manual and a clean up of the spring spacer.
-(@ref{Changes}, @ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.8.2 available - @emph{May 12, 2006}
-This release has fixes for minor bugs and compilation issues.
-(@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.9.3 is out! - @emph{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. (@ref{Changes}, @ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading FISL7.0 slides available - @emph{April 22, 2006}
-The slides for Han-Wen's talk at
-@uref{http://fisl.softwarelivre.org,FISL 7} are now online.
-(@ref{Publications})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.8.1 is out! - @emph{April 3, 2006}
-Important bugfixes include CJK font handling and a Darwin/x86 port.
-(@ref{Changes}, @ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.9.1 is out! - @emph{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.
-(@ref{Changes}, @ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond on MacOS X/Intel - @emph{March 31, 2006}
-LilyPond now also runs on Intel based macs, offering a 400%
-speedup over the emulated PowerPC binaries. (@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.8.0 is out! - @emph{March 22, 2006}
-Version 2.8 is here! Read the @uref{announce-v2.8.html,release
-announcement}. (@ref{Changes}, @ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.39 is out - @emph{March 17, 2006}
-This release has even more bug fixes. Please test before 2.8 is
-released. (@ref{Changes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.38 is out - @emph{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.
-(@ref{Changes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.37 is out - @emph{March 4, 2006}
-This release has more bug fixes. Please help us by testing it!
-(@ref{Changes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.36 is out - @emph{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. (@ref{Changes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.35 is out - @emph{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 @strong{very} welcome. By
-definition a bug is release critical if it wasn't present in version
-2.6. (@ref{Changes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.34 is out - @emph{February 16, 2006}
-This release has a bunch of bugfixes, and new features. Newly created
-contexts may also be named with @code{\new Voice =
-"alto"}. Thicknesses of tie and slurs may be tuned separately for
-the endings and the middle
-part. (@ref{Changes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.33 is out - @emph{February 10, 2006}
-Items directly connected with a music input element may be
-parenthesized, for example,
-@verbatim
-{
- c4 -\parenthesize -.
- <d \parenthesize fis a>
-}
-@end verbatim
-
-This feature was sponsored by Ramana Kumar. (@ref{Changes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.32 is out - @emph{February 7, 2006}
-This release contains some syntax changes: words inside the \paper and
-\layout block are henceforth written with dashes, for instance:
-
-@verbatim
-{
- \layout {
- ragged-right = ##t
- }
-}
-@end verbatim
-
-Furthermore, in this release, we have dropped some legacy code from
-our library. Now, lily uses standard C++ strings and the STL
-vector. (@ref{Changes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.31 is out - @emph{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.
-(@ref{Changes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.30 is out - @emph{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. (@ref{Changes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.29 is out - @emph{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). (@ref{Changes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.28 is out - @emph{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. (@ref{Changes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.27, release 4 - @emph{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! (@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.27, release 3 - @emph{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 @strong{FreeBSD} as well! Jump
-to the @ref{Old downloads} get them!
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.27 binaries are out - @emph{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
-@uref{http://lilypond.org/download/binaries/linux-x86/lilypond-2.7.27-1.linux.sh,
-Linux/x86},
-@uref{http://lilypond.org/download/binaries/MacOS/lilypond-2.7.27-2.zip,
-MacOS X} and
-@uref{http://lilypond.org/download/binaries/mingw/lilypond-2.7.27-2.exe,
-Windows}.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.27 is out - @emph{January 7, 2006}
-This release allows you to switch staff lines on and off individually
-(feature sponsored by Andrea
-Valle). (@ref{Changes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading Linux Journal article - @emph{January 2006}
-Linux Journal publishes an article on
-@uref{http://www.linuxjournal.com/article/8364,@emph{Make
-Stunning Schenker Graphs with GNU LilyPond}}. 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.”
-This article is now available @uref{http://www.linuxjournal.com/article/8583,on-line}.
-@newsEnd
-
-
-@newsItem
-@subsubheading New binaries for LilyPond 2.7.26 - @emph{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 @ref{Old downloads}
-page. Let us know how you fare!
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.26 is out - @emph{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!
-(@ref{Changes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.25 is out - @emph{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). (@ref{Changes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.24 is out - @emph{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. (@ref{Changes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.23 is out - @emph{December 19, 2005}
-This release has the following new features:
-@itemize
-@item
-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).
-@item
-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).
-@item
-Generic music functions may now also be used on
-articulations and chord elements (feature sponsored by Sean Reed and
-Bertalan Fodor).
-@item
-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.
-@end itemize
-(@ref{Changes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.22 is out - @emph{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. (@ref{Changes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.21 is out - @emph{December 5, 2005}
-Saint Nicholas brings you ... a @uref{http://www.musicxml.org/,MusicXML} convertor for LilyPond!
-The convertor is basic, but working. Check out the @uref{http://www.lilypond-design.com/sponsor/open-features.html#inputfilter,
-LilyPond Software Design} pages for MusicXML features that can be
-sponsored.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.20 is out - @emph{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). (@ref{Changes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.6.5 is out - @emph{December 1, 2005}
-This release updates the bugreporting address and reorganizes the
-documentation tree. (@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.19 is out - @emph{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. (@ref{Changes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.18 is out - @emph{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. (@ref{Changes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.17 is out - @emph{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. (@ref{Changes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.16 is out - @emph{November 11, 2005}
-This release fixes a large number of bugs. Please upgrade before
-reporting bugs in the 2.7 series. (@ref{Changes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.15 is out - @emph{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. (@ref{Changes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.14 is out - @emph{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.
-@verbatim
-
-\override Beam #'direction = #(lambda (grob)
-(if (> (random 10) 5) UP DOWN))
-
-@end verbatim
-will set a random direction for beams. (@ref{Changes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.13 is out - @emph{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. (@ref{Changes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.6.4 is out - @emph{October 11, 2005}
-This release fixes a few minor problems with the stable
-series. (@ref{Changes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.12 is out - @emph{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). (@ref{Changes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.11 is out - @emph{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. (@ref{Changes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.10 is out - @emph{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. (@ref{Changes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.9 is out - @emph{September 5, 2005}
-This is mainly a bugfix
-release. (@ref{Changes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading Traduction française du site - @emph{September 03, 2005}
-Grâce à @uref{about/thanks#website,l'équipe des traducteurs},
-de nombreuses pages du site sont maintenant disponibles en français,
-notamment l'@uref{about/automated-engraving/index.fr.html,essai sur
-la gravure musicale}.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.8 is out - @emph{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. (@ref{Changes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading Article in `De Standaard' - @emph{August 20, 2005}
-The Belgian newspaper @emph{De Standaard} investigates what drives
-Free Software authors in an article titled @emph{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.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.7 is out - @emph{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á. (@ref{Changes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.6 is out - @emph{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. (@ref{Changes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.5 is out - @emph{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. (@ref{Changes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.4 is out - @emph{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. (@ref{Changes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.6.3 is out - @emph{August 4, 2005}
-This release fixes a memory corruption bug that was triggered by
-\override'ing Beam settings. (@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.6.2 is out - @emph{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. (@ref{Changes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.3 is out - @emph{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.
-(@ref{Changes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.2 is out - @emph{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. (@ref{Changes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.6 released - @emph{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).
-@strong{Get up and running in minutes!} Pango text formatting lets you
-print @strong{Unicode } lyrics in your favorite script and font. Create
-@strong{SVG} files, and edit them in Inkscape.
-(@uref{announce-v2.6.html,Announcement}, @ref{Old downloads}, @ref{Changes})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.1 is out - @emph{July 20, 2005}
-LilyPond 2.7.1 has no user-visible changes. However, due to
-restructuring @qq{under the hood}, this version will be 10 to
-20 % faster. (@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.6.1 is out - @emph{July 11, 2005}
-This version fixes a few minor bugs found in
-2.6.0, and also works on DOS-based Windows versions. (@ref{Changes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7 is out - @emph{July 9, 2005}
-LilyPond 2.7.0 is out. It has support for paragraph text and
-pitched trill notation. (@ref{Changes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading 2.5.31 released - @emph{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.
-(@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading Traduction du site de LilyPond - @emph{15 juin 2005}
-@uref{about/thanks#website,L'équipe des traducteurs} vous présente
-le site de LilyPond en français. Nous travaillons sur la traduction des
-pages encore non traduites. Bon surf !
-@newsEnd
-
-
-@newsItem
-@subsubheading 2.5.31 for Windows and MacOS - @emph{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.
-(@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading 2.5.31 released - @emph{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. (@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading 2.5.30 released - @emph{June 10, 2005}
-This is (hopefully) the last Release Candidate before 2.6. Give it a
-good shake to find those last bugs! (@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading 2.5.29 released - @emph{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). (@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading 2.5.27 released - @emph{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. (@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading Windows and MacOS installers available - @emph{May 26, 2005}
-There are now a native, standalone installers for Windows and
-MacOS. They also support PDF point & click. (@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading 2.5.26 released - @emph{May 26, 2005}
-This release has a couple of small bugfixes.
-@newsEnd
-
-
-@newsItem
-@subsubheading 2.5.25 released - @emph{May 20, 2005}
-This release has many small bugfixes and updates to the
-documentation. (@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading 2.5.24 released - @emph{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. (@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading 2.5.23 released - @emph{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. (@ref{Changes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading 2.5.22 released - @emph{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.
-(@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-(@ref{Changes},
-@ref{Old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading 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 @ref{Changes}
-file, or go straight to @ref{Old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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 @ref{Changes}
-file and @ref{Old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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. @ref{Old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading 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. @ref{Old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{Old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading 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 @ref{Changes}
-file and @ref{Old downloads}!
-@newsEnd
-
-
-@newsItem
-@subsubheading 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 @ref{Changes}
-file and download @ref{Old downloads}!
-@newsEnd
-
-
-@newsItem
-@subsubheading March 7, 2005
-LilyPond 2.4.5 is out. This release backports the tieWaitForNote
-feature and has support for tetex-3.0.
-@ref{Old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading February 28, 2005
-LilyPond 2.5.13 is available for Fedora Core 3. You need to install @uref{http://lilypond.org/download/binaries/Fedora-3/ghostscript-8.15rc3-0.i386.rpm,ESP
-Ghostscript 8.15rc3}. 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.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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 @uref{http://lilypond.org/doc/v2.5/Documentation/user/out-www/lilypond/Point-and-click.html,here}.
-Take a look at the @ref{Changes}
-file and download @ref{Old downloads}!
-@newsEnd
-
-
-@newsItem
-@subsubheading February 26, 2005
-The @uref{http://lsr.dsi.unimi.it/,Lilypond Snippet
-Repository (LSR)} 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.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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 @strong{all}
-fonts available via FontConfig. Also, arpeggios may be written out
-using ties and individual objects may have colors! Take a look at
-the @ref{Changes}
-file and @ref{Old downloads}!
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{Old downloads}!
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{Old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{Old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading 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
-@uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.3065&content-type=text/vnd.viewcvs-markup,
-change log
-} and @ref{Old downloads}!
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{Old downloads}
-and check out the changes in
-the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.3048&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{Old downloads}
-and check out the
-changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.3013&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{Old downloads}
-and check out the changes in
-the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev= 1.3000&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{Old downloads}
-and check out the
-changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2974&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{Old downloads}
-and
-check out the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2908&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{Old downloads}
-and check out the changes in
-the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2898&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{Old downloads}
-and check out the changes in
-the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2881&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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
-@verbatim
-
-\cueDuring #VOICE-NAME #DIRECTION { MUSIC }
-
-@end verbatim
-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.
-@ref{Old downloads}
-and check out
-the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2837&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{Old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{Old downloads}
-and check out the changes in
-the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2780.2&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading October 31, 2004
-LilyPond 2.4.0 was just @uref{announce-v2.4.html,released!}
-This new stable version has support for page-layout,
-completely rewritten slur formatting and many other
-improvements. Read about them in the @ref{Changes}
-file.
-@ref{Old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{Old downloads}
-and check out the changes in
-the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2773&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{Old downloads}
-and check out the changes in
-the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2765&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{Old downloads}
-and check out the changes in
-the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2752&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{Old downloads}
-and check out the changes in
-the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2742&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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@{@}.
-@ref{Old downloads}
-and
-check out the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2709&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{Old downloads}
-and check
-out the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2692&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{Old downloads}
-and check out the changes in
-the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2674&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading September 29, 2004
-The LilyPond development team will be present at the @uref{http://www.nluug.nl/events/sane2004/bazaar/index.html,Free
-Software Bazaar} 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.
-@newsEnd
-
-
-@newsItem
-@subsubheading September 26, 2004
-LilyPond 2.3.19 is out. It's mainly a bugfix release.
-@ref{Old downloads}
-and check out the changes
-in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2652&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{Old downloads}
-and check out the changes in
-the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2614&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{Old downloads}
-and check out the changes in
-the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2562&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{Old downloads}
-and check out the changes in
-the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2553&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{Old downloads}
-and check out
-the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2534&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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!
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{Old downloads}
-and
-check out the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2520&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading August 24, 2004
-LilyPond 2.2.6 fixes a few minor issues, among others, the
-disappearing metronome mark.
-@ref{Old downloads}
-and check out the changes in
-the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2000.2.33&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{Old downloads}
-and check out the changes in
-the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2489&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading August 3, 2004
-LilyPond 2.3.11 is out. This release basically is 2.3.10 with a few
-annoying bugs fixed.
-@ref{Old downloads}
-and check out
-the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2449&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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:
-@itemize
-@item
-Running trills now have their own spanner and event. They are
-started and stopped with \startTrillSpan and \stopTrillSpan
-@item
-There is a new markup command `\postscript' that takes a string
-that is dumped as verbatim PostScript
-@end itemize
-
-@ref{Old downloads}
-and check out
-the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2435&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{Old downloads}
-and check out
-the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2416&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{Old downloads}
-and check out the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2395&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{Old downloads}
-and check out the changes in
-the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2383&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading July 15, 2004
-LilyPond 2.2.5 was released. It has a few bug fixes from
-2.3.x.
-@ref{Old downloads}
-and check
-out the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2000.2.28&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading July 11, 2004
-An introductory article on LilyPond appeared on @uref{http://www.linuxjournal.com/article.php?sid=7657&mode=thread&order=0,Linux
-Journal}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{Old downloads}
-and check out the changes
-in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2306&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading July 5, 2004
-LilyPond 2.2.4 was released. It is mainly a bug fix
-release.
-@ref{Old downloads}
-and
-check out the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2000.2.23&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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 @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2293&content-type=text/vnd.viewcvs-markup,ChangeLog}
-and
-@ref{Old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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 @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2000.2.16&content-type=text/vnd.viewcvs-markup,ChangeLog} for a full description and
-@ref{Old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading June 13, 2004
-LilyPond 2.3.4 further improves the output backends. As a
-result, manual page-breaks, multiple output formats and putting
-@code{\score} into markups now works. Check out the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2242&content-type=text/vnd.viewcvs-markup,ChangeLog}
-and
-@ref{Old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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 @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2207&content-type=text/vnd.viewcvs-markup,ChangeLog}
-and
-@ref{Old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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 @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2000.2.9,ChangeLog}
-or head straight to the
-@ref{Old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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 @ref{Changes} or head straight to the
-@ref{Old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading May 9, 2004
-LilyPond 2.3.1 is out. This release has many new and cool
-features. Check out the @ref{Changes} or head straight to the
-@ref{Old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading May 4, 2004
-Help LilyPond get better, and join in on LilyPond
-development! This
-@uref{devel/participating/call-for-help.html,call for
-help} 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!
-@newsEnd
-
-
-@newsItem
-@subsubheading May 3, 2004
-LilyPond 2.2.1 has been released. It fixes a handful of bugs.
-@ref{Old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading April 17, 2004
-LilyPond 2.2.0 is now available
-on Windows, and should find its way to the Cygwin mirrors
-soon.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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 @emph{experimental}; expect things to break!
-More info in the @ref{Changes}.
-@ref{Old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading April 8, 2004
-A French article on the new LilyPond
-release appeared on @uref{http://linuxfr.org/2004/04/08/15968.html,linuxfr.org}.
-@newsEnd
-
-
-@newsItem
-@subsubheading April 8, 2004
-Binaries for LilyPond 2.2.0 are available for
-MacOS X, Slackware, Mandrake and Debian Woody.
-@ref{Old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading 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 @uref{announce-v2.2.html,announcement} or skip to the
-@ref{Old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{Old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading March 30, 2004
-LilyPond 2.1.36 has many fixes in
-the user manual.
-@ref{Old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading March 28, 2004
-LilyPond 2.1..35 fixes a slew of
-bugs, and has the @code{raggedlast} option, which causes
-paragraph like line breaking for scores. More info in the
-@ref{Changes}.
-@ref{Old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading March 22, 2004
-LilyPond 2.1.34 fixes minor bugs, and has more rewriting.
-@ref{Old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading March 21, 2004
-LilyPond 2.1.33 fixes a serious bug, and a few other
-irritations.
-@ref{Old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading 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).
-@ref{Old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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
-@ref{Changes} and
-@ref{Old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading March 14, 2004
-The
-@uref{http://linuxmusician.com/index.php?option=articles&task=viewarticle&artid=10,linuxmusician.com interview} made the
-@uref{http://slashdot.org/article.pl?sid=04/03/13/2054227&mode=thread&tid=141&tid=188,slashdot
-frontpage!}.
-@newsEnd
-
-
-@newsItem
-@subsubheading March 11, 2004
-@uref{http://linuxmusician.com,linuxmusician.com} is
-running an
-@uref{http://linuxmusician.com/index.php?option=articles&task=viewarticle&artid=10,interview}
-with Han-Wen Nienhuys and Jan Nieuwenhuizen, the main
-authors of LilyPond.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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
-@ref{Changes} and
-@ref{Old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading March 9, 2004
-LilyPond 2.1.29 fixes a couple of MIDI bugs, and has
-experimental support for producing titles with
-@code{markup}.
-@newsEnd
-
-
-@newsItem
-@subsubheading February 29, 2004
-In LilyPond 2.1.28 Scheme property functions may be used
-argument to @code{set!}. In addition, parts of the manual
-have been proofread and corrected in this release. See the
-@ref{Changes} and
-@ref{Old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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
-@ref{Changes} and
-@ref{Old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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
-@ref{Changes}.
-@ref{Old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading February 18, 2004
-LilyPond 2.1.25 fixes many bugs, and changes the conventions
-for altering accidental rules.
-@ref{Old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading February 16, 2004
-LilyPond 2.1.24 has a big
-internal rewrite. One of its practical consequences is that
-@code{\with} now also works with @code{Score}
-contexts. Further 2.1.23, which was not announced here,
-fixes a few bugs caused by the change of @code{\property}
-syntax and has updates in the Program Reference document.
-More information in the
-@ref{Changes}.
-@ref{Old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading February 13, 2004
-LilyPond 2.1.22 has a
-simplification of the @code{\property} syntax: it is
-shorter and more consistent now. More information in the
-@ref{Changes}.
-@ref{Old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading 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
-@ref{Changes}.
-@ref{Old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading 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
-@ref{Changes}.
-@ref{Old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading February 5, 2004
-LilyPond 2.1.19 has rewritten
-support for drum notation. This release also makes some
-long-standing cleanups: the removal of @code{Thread} (all
-functionality is now moved into @code{Voice}) and Lyrics
-(functionality moved to @code{LyricsVoice}) context.
-More information in the
-@ref{Changes}.
-@ref{Old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading February 4, 2004
-LilyPond 2.1.18 is out. This
-release has the new part-combiner installed by default, and a
-similar implementation of @code{autochange}. More information
-in the
-@ref{Changes}.
-@ref{Old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading February 2, 2004
-LilyPond 2.1.17 is out. It adds texts
-(solo, a due) for the part combiner. It also reinstates the
-@code{--safe} option which prevents havoc by Scheme exploits. More
-information in the
-@ref{Changes}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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
-@ref{Changes}.
-@ref{Old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading 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
-@ref{Changes}. @ref{Old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading 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
-@ref{Changes}. @ref{Old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{Old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading January 19, 2004
-LilyPond 2.1.12 fixes many bugs
-and improves formatting of ottava brackets. More information in
-the
-@ref{Changes}. @ref{Old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading January 18, 2004
-LilyPond 2.1.11 is now also
-available for Windows! For downloading, go
-@uref{http://www.inf.bme.hu/~berti/lilypond/,here}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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
-@ref{Changes}. @ref{Old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading January 16, 2004
-LilyPond 2.1.10 has a load of
-bugfixes and a shorter syntax for octave checks. More
-information in the
-@ref{Changes}. @ref{Old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading 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
-@ref{Changes}. @ref{Old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading January 9, 2004
-LilyPond 2.1.8 has an important new
-feature: it is now possible to use @code{\property} to tune
-the appearance of spanning objects like @code{StaffSymbol} and
-@code{SystemStartBrace}. In addition, contexts may be
-modified with @code{\remove} and @code{\consists} for
-individual music expressions.
-More information in the
-@ref{Changes}. @ref{Old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading January 7, 2004
-An update to the stable branch,
-version 2.0.2, was released today. It contains a couple of
-minor bugfixes. @ref{Old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading 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
-@ref{Changes} and download @uref{install/#2.1,here}.
-@newsEnd
-
-
-@newsItem
-@subsubheading January 4, 2004
-LilyPond 2.1.6 continues to
-improve the layout of lyrics. More
-information in the
-@uref{@@DOC@@v2.1/Documentation/topdocs/out-www/NEWS.html,release
-notes} and download @uref{install/#2.1,here}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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ängers Morgen. More
-information in the
-@ref{Changes} and download @uref{install/#2.1,here}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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
-@ref{Changes} and download @uref{install/#2.1,here}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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
-@ref{Changes} and download @uref{install/#2.1,here}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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
-@ref{Changes} and download @uref{install/#2.1,here}.
-@newsEnd
-
-
-@newsItem
-@subsubheading December 16, 2003
-LilyPond 2.1.1 released. This
-release wraps together all the small fixes made during
-Han-Wen's absence. See the
-@ref{Changes} and download @uref{install/#2.1,here}.
-@newsEnd
-
-
-@newsItem
-@subsubheading October 11, 2003
-LilyPond 2.1.0 released. See the
-@ref{Changes} and
-download @uref{install/#2.1,here}.
-@newsEnd
-
-
-@newsItem
-@subsubheading October 11, 2003
-LilyPond 2.0.1 binaries for Mandrake 9.1
-available from
-@uref{http://rpm.nyvalls.se/sound9.1.html,here}
-thanks to Heikki Junes.
-@newsEnd
-
-
-@newsItem
-@subsubheading October 9, 2003
-LilyPond 2.0.1 binaries for Slackware 9
-available from @uref{install/#2.0,here},
-thanks to Ricardo Hoffman.
-@newsEnd
-
-
-@newsItem
-@subsubheading October 5, 2003
-LilyPond 2.0.1 binaries are available for Macos X, many thanks to
-Matthias Neeracher.
-@ref{Old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading October 4, 2003
-LilyPond 2.0.1 binaries are available for Windows (Cygwin
-version 1.5).
-@ref{Old downloads}. Thanks to Bertalan
-Fodor, our new Cygwin maintainer!
-@newsEnd
-
-
-@newsItem
-@subsubheading September 29, 2003
-LilyPond 2.0.1 is released. It
-contains minor bugfixes.
-See the @ref{Changes}
-or download @uref{install/#2.0,here} directly.
-@newsEnd
-
-
-@newsItem
-@subsubheading September 27, 2003
-PlanetCCRMA has been updated to include LilyPond 2.0. Go
-@uref{http://www-ccrma.stanford.edu/planetccrma/software/soundapps.html#lilypond,
-here} to download. Thanks to Fernando Pablo
-Lopez-Lezcano!
-@newsEnd
-
-
-@newsItem
-@subsubheading 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
-@uref{announce-v2.0.html,here}, or go to the
-@uref{install/#2.0,download page} directly.
-@newsEnd
-
-
-@newsItem
-@subsubheading September 24, 2003
-LilyPond 1.9.10 is released. This is
-the final LilyPond 2.0 release candidate. Check
-the @ref{Changes} and
-download @uref{install/,here}.
-@newsEnd
-
-
-@newsItem
-@subsubheading September 23, 2003
-LilyPond 1.9.9 is released. This is
-the second LilyPond 2.0 prerelease. Check
-the @ref{Changes} and
-download @uref{install/,here}.
-@newsEnd
-
-
-@newsItem
-@subsubheading September 19, 2003
-LilyPond 1.9.8 is released. This is
-the first LilyPond 2.0 prerelease. Check
-the @ref{Changes} and
-download @uref{install/,here}.
-@newsEnd
-
-
-@newsItem
-@subsubheading September 17, 2003
-LilyPond 1.9.7 is released. LilyPond
-now has support for quarter tone accidentals!
-@ref{Old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading September 16, 2003
-LilyPond 1.9.6 is released.
-It has a lot of minor fixes and updates.
-@ref{Old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{Old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading September 9, 2003
-LilyPond 1.8.2 is released. This
-release fixes a couple of minor bugs.
-@ref{Old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading September 7, 2003
-LilyPond 1.8 binaries are available
-for Windows (Cygwin version 1.5).
-@ref{Old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading August 31, 2003
-LilyPond 1.9.4 is released.
-@emph{This is an experimental release}: read the
-@uref{http://mail.gnu.org/archive/html/lilypond-devel/2003-08/msg00133.html,announcement}
-before trying.
-@newsEnd
-
-
-@newsItem
-@subsubheading August 31, 2003
-LilyPond 1.8 binaries for slackware
-available. Get them @uref{install/,here}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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
-@ref{Changes} and get it @uref{download#1.9,here}.
-@newsEnd
-
-
-@newsItem
-@subsubheading August 28, 2003
-LilyPond 1.9.2 is released. Read the
-@ref{Changes} and get it
-@uref{download#1.9,here}.
-@newsEnd
-
-
-@newsItem
-@subsubheading August 26, 2003
-LilyPond 1.9.1 is released. Read the
-@ref{Changes} and get it
-@uref{download#1.9,here}.
-@newsEnd
-
-
-@newsItem
-@subsubheading August 25, 2003
-The LilyPond 1.9 development release is available. Read the
-@ref{Changes} and get it
-@uref{download#1.9,here}.
-@newsEnd
-
-
-@newsItem
-@subsubheading August 25, 2003
-Mandrake 9.1 RPMS available, get them
-@uref{http://rpm.nyvalls.se/sound9.1.html,here}.
-@newsEnd
-
-
-@newsItem
-@subsubheading August 21, 2003
-LilyPond 1.8.1 was released. Get it @uref{install/,here}, or
-read the @ref{Changes}.
-@newsEnd
-
-
-@newsItem
-@subsubheading August 18, 2003
-PlanetCCRMA (eg. RedHat 8 and 9)
-has been updated to 1.8.
-Download @uref{http://www-ccrma.stanford.edu/planetccrma/software/soundapps.html#lilypond,here.}
-@newsEnd
-
-
-@newsItem
-@subsubheading August 7, 2003
-LilyPond 1.8 is released. Read
-@ref{Changes} and get it @uref{install/,here}.
-@newsEnd
-
-
-@newsItem
-@subsubheading August 7, 2003
-New website went live!
-@newsEnd
-
-
-@newsItem
-@subsubheading August 6, 2003
-Announced new website.
-@newsEnd
-
-
-@newsItem
-@subsubheading August 1, 2003
-LilyPond 1.7.30 released.
-@newsEnd
-
-
-@newsItem
-@subsubheading July 30, 2003
-Website: present @uref{about/automated-engraving/index.html,treatise}
-about music engraving, music printing software, and LilyPond's
-unique faculties.
-@newsEnd
-
-
-@newsItem
-@subsubheading July 29, 2003
-1.7.29 - release candidate 4 has been released. Packages for
-Red Hat, Debian, Cygwin are @uref{install/,available}.
-@newsEnd
-
--- /dev/null
+\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
+@c This file is part of web.texi
+@ignore
+ Translation of GIT committish: 1b3da70d81938d19a2b107382bbe25a267cf130b
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+
+@setfilename web.info
+@settitle LilyPond -- la notation musicale pour tous
+@documentencoding UTF-8
+@documentlanguage fr
+@set web
+@include macros.itexi
+@afourpaper
+@ifnottex
+@node Top
+@top LilyPond
+
+@translationof Top
+
+@c Translators: Test
+
+@chapheading
+@end ifnottex
+@finalout
+@titlepage
+@title LilyPond
+@subtitle
+@titlefont{New Website}
+@author Équipe de développement de LilyPond
+@quotation
+@end quotation
+@vskip 20pt
+@end titlepage
+@copying
+@quotation
+@end quotation
+@end copying
+@divId{pageHeader}
+@heading LilyPond
+
+... la notation musicale pour tous
+@divEnd
+@c @imageId{cmws,web-clef-g-eight-alpha.png,Catchy Musical Web Snippet}
+@imageId{lilylogo,double-lily-modified3.png,LilyPond logo}
+@c @im ageId{cmws,web-snippet-alpha.png,Catchy Musical Web Snippet}
+@divId{quickSummary}
+@subheading Qu'est-ce que c'est LilyPond?
+TODO FIXME FRENCH
+@divClass{align-right}
+@divEnd
+@divEnd
+@divId{news}
+@include news-front.itexi
+@divClass{float-right}
+@divEnd
+@divEnd
+@divId{latestVersion}
+@subheading Quick links
+@c TODO: javascript to detect OS and suggest download?
+@subsubheading Stable
+@ref{Download, Download 2.12.3}
+@ref{Manuals, Manuals 2.12.3}
+@subsubheading Unstable
+@ref{Development, Download 2.13.2}
+@ref{Development, Manuals 2.13.2}
+@divEnd
+@divClass{hide}
+@menu
+* Introduction::
+* Download::
+* Manuals::
+* Community::
+@end menu
+
+@divEnd
+@contents
+@include web/introduction.itexi
+@include web/download.itexi
+@include web/manuals.itexi
+@include web/community.itexi
+@bye
+
--- /dev/null
+depth = ../../..
+
+LOCALSTEPMAKE_TEMPLATES = ly
+
+include $(depth)/make/stepmake.make
--- /dev/null
+\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
+@c This file is part of web.texi
+@ignore
+ Translation of GIT committish: 1b3da70d81938d19a2b107382bbe25a267cf130b
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+
+@c -*- coding: utf-8; mode: texinfo; -*-
+@node Community
+@unnumbered Community
+
+@untranslated
+
+
+@divClass{column-center-top}
+@subheading Interacting with the community
+@ref{Contact}: get help, discuss, and keep in touch!
+@ref{Tiny examples}: these are @emph{highly} recommended when
+@ref{Bug reports}: something went wrong.
+@divEnd
+@divClass{column-left-bottom}
+@subheading Making LilyPond better
+@ref{Help us}: your assistance is requested.
+@ref{Development}: for contributors and testers.
+@ref{Authors}: the people who made LilyPond what it is today.
+@divEnd
+@divClass{column-right-bottom}
+@subheading Miscellaneous
+@ref{Publications}: what we wrote, and have had written about us.
+@ref{Old news}: an archive.
+@divEnd
+@divClass{hide}
+@menu
+* Contact::
+* Tiny examples::
+* Bug reports::
+* Help us::
+* Development::
+* Authors::
+* Publications::
+* Old news::
+@end menu
+
+@divEnd
+@node Contact
+@unnumberedsec Contact
+
+@untranslated
+
+
+@divClass{column-left-bottom}
+@subheading User Discussions and Help
+@subsubheading User mailist: @code{lilypond-user@@gnu.org}
+@quotation
+@end quotation
+@subsubheading IRC
+@subsubheading Other languages
+@divEnd
+@divClass{column-right-top}
+@subheading Stay Informed
+@subsubheading LilyPond Report
+@subsubheading Releases mailist: @code{info-lilypond@@gnu.org}
+@quotation
+@c don't include gmane posting here. -gp
+@end quotation
+@divEnd
+@divClass{column-right-bottom}
+@subheading Developer Discussion
+@subsubheading Developer mailist: @code{lilypond-devel@@gnu.org}
+@quotation
+@end quotation
+@subsubheading Bug mailist: @code{bug-lilypond@@gnu.org}
+@quotation
+@c don't include gmane posting here. -gp
+@end quotation
+@divEnd
+@node Tiny examples
+@unnumberedsec Tiny examples
+
+@untranslated
+
+
+@divClass{column-center-top}
+@subheading What are @qq{Tiny examples}?
+@divEnd
+@divClass{column-left-bottom}
+@subheading Why create them?
+@divClass{keep-bullets}
+@divEnd
+@divEnd
+@divClass{column-right-bottom}
+@subheading How do I create them?
+@divClass{keep-bullets}
+@divEnd
+@divEnd
+@node Bug reports
+@unnumberedsec Bug reports
+
+@untranslated
+
+
+@divClass{column-center-top}
+@subheading Step 1: Known bugs
+@divEnd
+@divClass{column-left-bottom}
+@subheading Step 2: Creating a bug report
+@divEnd
+@divClass{column-right-bottom}
+@subheading Step 3: Sending a bug report
+@divEnd
+@node Help us
+@unnumberedsec Help us
+
+@untranslated
+
+
+@subheading This document
+@subsubheading High priority / blocks release
+@subsubheading Low priority / may never
+@node Development
+@unnumberedsec Development
+
+@untranslated
+
+
+@divClass{heading-center}
+@heading Development materials for LilyPond 2.13.3
+@ref{Manuals}.}
+@divEnd
+@divClass{column-left-bottom}
+@subheading Download
+@subheading Manuals
+@divEnd
+@divClass{column-right-bottom}
+@subheading Contributors' Guide
+@divEnd
+@node Authors
+@unnumberedsec Authors
+
+@untranslated
+
+
+@node Publications
+@unnumberedsec Publications
+
+@untranslated
+
+
+@divClass{column-center-top}
+@subheading What we wrote
+@divClass{keep-bullets}
+@divEnd
+@divEnd
+@divClass{column-center-bottom}
+@subheading What others wrote
+@divClass{keep-bullets}
+@divEnd
+@divEnd
+@node Old news
+@unnumberedsec Old news
+
+@untranslated
+
+
+@include web/news.itexi
+
+@c -- SKELETON FILE --
--- /dev/null
+\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: fr -*-
+@c This file is part of web.texi
+@ignore
+ Translation of GIT committish: dab17828471057f4e12c0d80777ff9bb4c5b2309
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+
+@c -*- coding: utf-8; mode: texinfo; -*-
+@node Download
+@unnumbered Download
+
+@untranslated
+
+
+@divClass{heading-center}
+@heading Downloads for LilyPond 2.12.2
+@divEnd
+@divClass{column-left-top}
+@subheading For users
+@c TODO: duplicate to avoid underlined refs in HTML? icky.
+@ref{Unix, @sourceimage{logo-linux} @sourceimage{logo-freebsd}}
+@ref{Unix, Unix (Linux and FreeBSD)}
+@ref{MacOS X, @sourceimage{logo-macosx}}
+@ref{MacOS X, MacOS X}
+@ref{Windows, @sourceimage{logo-windows}}
+@ref{Windows, Microsoft Windows}
+@divEnd
+@divClass{column-right-top}
+@subheading For developers
+@ref{Source}:
+@ref{Old downloads}:
+@divEnd
+@divClass{column-center-bottom}
+@subheading Software License
+@divEnd
+@divClass{color1}
+@subheading Sponsors
+@sourceimage{VTlogo_ITF} @sourceimage{lao_banner_06_on_white_demo}
+@subheading Legalese
+@divClass{legal}
+@divEnd
+@divEnd
+@divClass{hide}
+@menu
+* Unix::
+* MacOS X::
+* Windows::
+* Source::
+* Old downloads::
+* GPL::
+@end menu
+
+@divEnd
+@node Unix
+@unnumberedsec Unix
+
+@untranslated
+
+
+@divClass{column-center-top}
+@subheading Generic Packages or Distribution-Specific Packages?
+@divEnd
+@divClass{column-left-top}
+@subheading Generic Packages
+@subsubheading Download
+@sourceimage{logo-linux}
+@sourceimage{logo-linux}
+@sourceimage{logo-linux}
+@sourceimage{logo-freebsd}
+@sourceimage{logo-freebsd}
+@subsubheading Install
+@subsubheading Uninstall
+@divEnd
+@divClass{column-right-top}
+@subheading Distribution-specific Packages
+@sourceimage{logo-fedora}
+@sourceimage{logo-ubuntu}
+@sourceimage{logo-slackware}
+@sourceimage{logo-debian}
+@sourceimage{logo-suse}
+@divEnd
+@divClass{column-center-bottom}
+@subheading Legalese
+@divClass{legal}
+@divEnd
+@divEnd
+@node MacOS X
+@unnumberedsec MacOS X
+
+@untranslated
+
+
+@divClass{column-left-top}
+@subheading Packages
+@subsubheading Download
+@sourceimage{logo-macosx}
+@sourceimage{logo-macosx}
+@subsubheading Install
+@subsubheading Uninstall
+@divEnd
+@divClass{column-right-top}
+@subheading Running on the command-line
+@subsubheading Using Python scripts on MacOS 10.3 or 10.4
+@c ommand{convert-ly} and @command{lilypond-book} as follows: if the
+@subsubheading MacOS X on the command line
+@c ommand{abc2ly}, and even @command{lilypond} itself --- are included
+@c ommand{lilypond-book}, @command{convert-ly}, @command{abc2ly}, etc.
+@c ode{bin/convert-ly} (or other program name) in the above file.
+@divEnd
+@divClass{column-center-bottom}
+@subheading Legalese
+@divClass{legal}
+@divEnd
+@divEnd
+@node Windows
+@unnumberedsec Windows
+
+@untranslated
+
+
+@divClass{column-left-top}
+@subheading Packages
+@subsubheading Download
+@sourceimage{logo-windows}
+@subsubheading Install
+@subsubheading Uninstall
+@divEnd
+@divClass{column-right-top}
+@subheading Running on the command-line
+@divEnd
+@divClass{column-center-bottom}
+@subheading Legalese
+@divClass{legal}
+@divEnd
+@divEnd
+@node Source
+@unnumberedsec Source
+
+@untranslated
+
+
+@divClass{column-left-bottom}
+@subheading Source tarball
+@divEnd
+@divClass{column-right-bottom}
+@subheading Compiling instructions
+@divEnd
+@node Old downloads
+@unnumberedsec Old downloads
+
+@untranslated
+
+
+@divClass{column-center-top}
+@subheading All versions
+@divEnd
+@node GPL
+@unnumberedsec GPL
+
+@untranslated
+
+
+@divClass{column-center-top}
+@subheading Software license
+@divEnd
+@divClass{column-center-bottom}
+@subheading GNU General Public License version 2
+@include gpl-2.0.itexi
+@divEnd
+
+@c -- SKELETON FILE --
--- /dev/null
+\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: fr -*-
+@c This file is part of web.texi
+@ignore
+ Translation of GIT committish: dab17828471057f4e12c0d80777ff9bb4c5b2309
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+
+@c -*- coding: utf-8; mode: texinfo; -*-
+@node Introduction
+@unnumbered Introduction
+
+@untranslated
+
+
+@divClass{column-center-top}
+@subheading Our Goal
+@imageFloat{flat-design.png,right}
+@divEnd
+@divClass{column-left-top}
+@subheading Why use LilyPond?
+@ref{Features}: What can LilyPond do?
+@ref{Examples}: I want to see some music!
+@ref{Freedom}: LilyPond is Free Software.
+@divEnd
+@divClass{column-right-top}
+@subheading Who uses it?
+@ref{Productions}: Real-life use of LilyPond.
+@ref{Testimonials}: What do people say?
+@divEnd
+@divClass{column-center-bottom}
+@subheading Why not use LilyPond?
+@ref{Text input}: You write music as @emph{text}?!
+@divEnd
+@divClass{hide}
+@menu
+* Features::
+* Examples::
+* Freedom::
+* Productions::
+* Testimonials::
+* Text input::
+@end menu
+
+@divEnd
+@node Features
+@unnumberedsec Features
+
+@untranslated
+
+
+@subheading Why switch to LilyPond?
+@subsubheading Excellent classical engraving
+@imageFloat{flat-design.png,right}
+@subsubheading No fiddling
+@subsubheading Text-based input
+@subsubheading Mix music and text
+@imageFloat{lilypond-book.png,right}
+@subsubheading Free software
+@subsubheading Extensible design
+@subsubheading Excellent support
+@divClass{column-center-bottom}
+@subheading Where now?
+@ref{Text input}.
+@divEnd
+@node Examples
+@unnumberedsec Examples
+
+@untranslated
+
+
+@imageClickable{examples/liszt-wagner-small.png, (click to enlarge), examples/liszt-wagner.png, center}
+@subsubheading Classical Music
+@imageClickable{examples/bach-bwv610-small.png, (click to enlarge), examples/bach-bwv610.png, center}
+@subsubheading Complex Notation
+@imageClickable{examples/granados-small.png, (click to enlarge), examples/granados.png, center}
+@subsubheading Early Music
+@imageClickable{examples/ancient-headword-small.png, (click to enlarge), examples/ancient-headword.png, center}
+@subsubheading Modern Music
+@imageClickable{examples/cary-small.png, (click to enlarge), examples/cary.png, center}
+@subsubheading Efficient, flexible creation of performance materials
+@imageClickable{examples/sesto-small.png, (click to enlarge), examples/sesto.png, center}
+@imageClickable{examples/sesto-1-small.png, (click to enlarge), examples/sesto-1.png, center}
+@imageClickable{examples/sesto-2-small.png, (click to enlarge), examples/sesto-2.png, center}
+@subsubheading Tablature
+@imageClickable{examples/bach-tab-example-small.png, (click to enlarge), examples/bach-tab-example.png, center}
+@subsubheading Schenker Graphs
+@imageClickable{examples/bach-schenker-small.png, (click to enlarge), examples/bach-schenker.png, center}
+@subsubheading Vocal Music
+@imageClickable{examples/aucun-snippet-small.png, (click to enlarge), examples/aucun-snippet.png, center}
+@subsubheading Educational Applications
+@imageClickable{examples/theory-small.png, (click to enlarge), examples/theory.png, center}
+@subsubheading Popular Music
+@imageClickable{examples/chart-small.png, (click to enlarge), examples/chart.png, center}
+@subsubheading Large Projects
+@imageClickable{examples/orchestral-small.png, (click to enlarge), examples/orchestral.png, center}
+@divClass{column-center-bottom}
+@subheading Where now?
+@ref{Freedom}. If you've already decided to try LilyPond, first
+@divEnd
+@node Freedom
+@unnumberedsec Freedom
+
+@untranslated
+
+
+@divClass{column-center-top}
+@subheading Free Software
+@ref{GPL, GNU General Public License} and the @ref{FDL, GNU Free
+@divEnd
+@c @divClass{column-left-top}
+@divClass{color2}
+@divClass{keep-bullets}
+@subheading What are the benefits to users?
+@divEnd
+@divEnd
+@c @divClass{column-right-top}
+@divClass{color3}
+@divClass{keep-bullets}
+@subheading Why do LilyPond developers @qq{give away} their work for free?
+@divEnd
+@divEnd
+@divClass{column-center-bottom}
+@subheading Where now?
+@ref{Productions} and sheet music. If you've already decided to
+@divEnd
+@node Productions
+@unnumberedsec Productions
+
+@untranslated
+
+
+@divClass{column-left-top}
+@subheading Concerts
+@divClass{keep-bullets}
+@divEnd
+@divEnd
+@divClass{column-right-top}
+@subheading Published sheet music
+@divClass{keep-bullets}
+@divEnd
+@divEnd
+@divClass{column-center-bottom}
+@subheading Where now?
+@ref{Text input}.
+@divEnd
+@node Testimonials
+@unnumberedsec Testimonials
+
+@untranslated
+
+
+@divClass{testimonial-item}
+@imageFloat{carter-brey.jpg, right}
+@subsubheading @uref{http://nyphil.org/meet/orchestra/index.cfm?page=profile&personNum=7, Carter Brey}, Principal Cellist, New York Philharmonic
+@divEnd
+@divClass{testimonial-item}
+@imageFloat{orm-finnendahl.jpg, left}
+@subsubheading @uref{http://icem-www.folkwang-hochschule.de/~finnendahl/, Orm Finnendahl}, professor of Composition, Musikhochschule Freiburg
+@divEnd
+@divClass{testimonial-item}
+@imageFloat{darius-blasband.jpg, right}
+@subsubheading Darius Blasband, composer (Brussels, Belgium)
+@divEnd
+@divClass{testimonial-item}
+@subsubheading Kieren MacMillan, composer (Toronto, Canada)
+@divEnd
+@divClass{testimonial-item}
+@subsubheading Chris Cannam, lead programmer of the @uref{http://www.rosegardenmusic.com/, RoseGarden} project.
+@divEnd
+@divClass{testimonial-item}
+@subsubheading Chris Snyder, @uref{http://www.adoromusicpub.com/, Adoro Music Publishing}
+@divEnd
+@divClass{testimonial-item}
+@subsubheading David Bobroff, Bass Trombone, Iceland Symphony Orchestra
+@divEnd
+@divClass{testimonial-item}
+@subsubheading Vaylor Trucks, Electric guitar player (Yes, @uref{http://www.allmanbrothersband.com/modules.php?op=modload&name=userpage&file=content&page_id=12, related to})
+@divEnd
+@divClass{testimonial-item}
+@subsubheading @uref{http://nicolas.sceaux.free.fr/, Nicolas Sceaux}, @uref{http://www.mutopiaproject.org/, Mutopia} contributor
+@divEnd
+@divClass{testimonial-item}
+@subsubheading @uref{http://www.troff.org/whoswho.html#werner, Werner Lemberg}, Conductor at the Theatre in Koblenz, Germany and distinguished GNU Hacker.
+@divEnd
+@divClass{testimonial-item}
+@subsubheading Paul Davis, developer of @uref{http://jackaudio.org/, JACK} and @uref{http://www.ardour.org/, Ardour}.
+@divEnd
+@divClass{column-center-bottom}
+@subheading Where now?
+@divEnd
+@node Text input
+@unnumberedsec Text input
+
+@untranslated
+
+
+@c TRANSLATORS: so far it's mostly from
+@c http://lilypond.org/web/switch/howto
+@subheading @qq{Compiling} Music
+@imageClickable{examples/nereid-shot-small.png, (click to enlarge), examples/nereid-shot.png, right}
+@subsubheading It's as simple as A B C
+@imageFloat{text-input-1-annotate.png,center}
+@imageFloat{text-input-1-output.png,center}
+@imageFloat{text-input-2-annotate.png,center}
+@imageFloat{text-input-2-output.png,center}
+@subsubheading Pop music
+@imageFloat{text-input-pop-annotate.png,center}
+@imageFloat{text-input-pop-output.png,center}
+@subsubheading Orchestral parts
+@imageFloat{text-input-parts-both-annotate.png,center}
+@imageFloat{text-input-parts-single-annotate.png,center}
+@imageFloat{text-input-parts-single-output.png,center}
+@imageFloat{text-input-score-annotate.png,center}
+@imageFloat{text-input-score-output.png,center}
+@subsubheading Beginner Documentation
+@subsubheading Easier editing environments
+@divClass{column-center-bottom}
+@subheading Where now?
+@ref{Freedom} that LilyPond provides, or read about users'
+@ref{Productions} and @ref{Testimonials}.
+@divEnd
+
+@c -- SKELETON FILE --
--- /dev/null
+\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
+@c This file is part of web.texi
+@ignore
+ Translation of GIT committish: 1b3da70d81938d19a2b107382bbe25a267cf130b
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+
+@c -*- coding: utf-8; mode: texinfo; -*-
+@node Manuals
+@unnumbered Manuals
+
+@untranslated
+
+
+@divClass{heading-center}
+@heading Documentation for LilyPond 2.12.2
+@divEnd
+@divClass{column-center-top}
+@subheading Introduction
+@divEnd
+@divClass{column-left-top}
+@subheading Regular use
+@divEnd
+@divClass{column-right-top}
+@subheading Infrequent Use
+@divEnd
+@divClass{column-center-bottom}
+@subheading Other material
+@divEnd
+@divClass{hide}
+@menu
+* Learning::
+* Glossary::
+* Essay::
+* Notation::
+* Usage::
+* Snippets::
+* FAQ::
+* Changes::
+* Internals::
+* Translated::
+* Old::
+* FDL::
+@end menu
+
+@divEnd
+@c TRANSLATORS: most of the text in this file came from
+@c LM 1.1 About the documentation (before this section was
+@c removed in July 2009).
+@node Learning
+@unnumberedsec Learning
+
+@untranslated
+
+
+@node Glossary
+@unnumberedsec Glossary
+
+@untranslated
+
+
+@node Essay
+@unnumberedsec Essay
+
+@untranslated
+
+
+@node Notation
+@unnumberedsec Notation
+
+@untranslated
+
+
+@node Usage
+@unnumberedsec Usage
+
+@untranslated
+
+
+@node Snippets
+@unnumberedsec Snippets
+
+@untranslated
+
+
+@node FAQ
+@unnumberedsec FAQ
+
+@untranslated
+
+
+@subheading Where are the graphical canvas, menus, and toolbars?
+@subheading There's a lot of documentation! Do I need to read it?
+@subheading That's still a lot of reading! Is it worth it?
+@subheading Something isn't working! How do I fix it?
+@subheading Why do you change the syntax?
+@node Changes
+@unnumberedsec Changes
+
+@untranslated
+
+
+@node Internals
+@unnumberedsec Internals
+
+@untranslated
+
+
+@node Translated
+@unnumberedsec Translated
+
+@untranslated
+
+
+@node Old
+@unnumberedsec Old
+
+@untranslated
+
+
+@node FDL
+@unnumberedsec FDL
+
+@untranslated
+
+
+@divClass{column-center-top}
+@subheading Documentation license
+@divEnd
+@divClass{column-center-bottom}
+@subheading GNU Free Documentation License 1.1
+@include fdl.itexi
+@divEnd
+
+@c -- SKELETON FILE --
--- /dev/null
+@c -*- coding: utf-8; mode: texinfo; -*-
+@c This file is part of lilypond-web.texi and community.itexi
+
+@c when you add a new item, consider moving the lowest item(s)
+@c into news-old.itexi.
+
+@newsItem
+@subsubheading New Website! @emph{20 Aug 2009}
+
+As you can see, we have a new website design. Many thanks to
+texi2html and CSS for being so flexible!
+
+(FIXME: change date when this is actually announced on lilypond.org)
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.13.3. @emph{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. For changes and download links, see @ref{Development}.
+@newsEnd
+
+
+
+@newsItem
+@subsubheading Hungarian translation! @emph{22 May 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!
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond Report #15. @emph{18 May 2009}
+
+The @emph{LilyPond Report} is a short, informal opinion column
+about the LilyPond project: its team, its world, its community.
+Read it @uref{http://news.lilynet.net/The-LilyPond-Report-15,
+here}!
+@newsEnd
+
+
--- /dev/null
+@c -*- coding: utf-8; mode: texinfo; -*-
+
+@ignore
+
+NOTE:
+
+ * avoid "HERE" as name for links, use descriptive link names like
+ @uref{,Download LilyPond 2.5.16}
+
+ * avoid putting links in running text. They make text harder to read.
+ Preferably: (@uref{,...}, etc. )
+
+ * use a descriptive title in @subsubheading
+
+ * writing date in "Month DD, YYYY" format is required for
+ generating the RSS feed; in case the message (and thus the date)
+ is not in English, you must write a well-formed date in English
+ like above in a comment between the closing brace of @emph and the
+ following line
+ (see "Japanese translation" below for an example).
+
+ * Split news items in small chunks. It's OK to have more than 1 item
+ on one day.
+
+
+FIXME
+
+ * add macro for long Google issues list URL
+@end ignore
+
+@newsItem
+@subsubheading New Website! @emph{20 Aug 2009}
+
+As you can see, we have a new website design. Many thanks to
+texi2html and CSS for being so flexible!
+
+(FIXME: change date when this is actually announced on lilypond.org)
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.13.3. @emph{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. For changes and download links, see @ref{Development}.
+@newsEnd
+
+
+
+@newsItem
+@subsubheading Hungarian translation! @emph{22 May 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!
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond Report #15. @emph{18 May 2009}
+
+The @emph{LilyPond Report} is a short, informal opinion column
+about the LilyPond project: its team, its world, its community.
+Read it @uref{http://news.lilynet.net/The-LilyPond-Report-15,
+here}!
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.13.3. @emph{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.@*
+@ref{Changes},
+@ref{Development}.
+@newsEnd
+
+
+@newsItem
+@subsubheading A LilyPond weboldala magyarul. @emph{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 @code{harmathdenes AT gmail.com} címre!
+<p align="right">Harmath Dénes, a LilyPond honosítási projekt
+vezetője
+@newsEnd
+
+
+@newsItem
+@subsubheading The LilyPond Report #15. @emph{May 18, 2009}
+
+The @emph{LilyPond Report} is a short, informal opinion column about the LilyPond project:
+its team, its world, its community.
+Follow @uref{http://news.lilynet.net/The-LilyPond-Report-15,this link}
+to read the full issue...
+@newsEnd
+
+
+@newsItem
+@subsubheading The LilyPond Report #14. @emph{April 13, 2009}
+
+The @emph{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 @uref{http://news.lilynet.net/The-LilyPond-Report-14,this link} to read the full issue...
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.12.2 and 2.13.0 — @emph{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.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.12.0 @qq{Rune} — @emph{December 27, 2008}
+
+A new stable release of LilyPond is available.
+@*
+@uref{announce-v2.12,Announcement},
+@ref{Changes},
+@ref{Download}.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.65 — Release Candidate. @emph{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.@*
+@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_65&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{Changes},
+@ref{Old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.64. @emph{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.
+@*
+@ref{Changes},
+@ref{Old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.63. @emph{October 29, 2008}
+
+LilyPond 2.11.63 is available. This release has lots of updates to the
+documentation and translations.
+@ref{Old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.62 – Release Candidate. @emph{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 @code{\tempo} command, this release has lot of updates
+to Spanish and German documentation translations, and the
+stylesheet for HTML documentation has been improved.
+@*
+@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_62&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{Old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.61 available. @emph{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.
+@*
+@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_61&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{Changes},
+@ref{Old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.60 available. @emph{September 25, 2008}
+
+LilyPond 2.11.60 has been released. A new style of double repeat
+bar line has been added, and @code{printallheaders} variable in
+score block has been renamed to @code{print-all-headers}.
+@ref{Old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.59 available. @emph{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.
+@ref{Old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.58 available. @emph{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.
+@*
+@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_58&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{Changes},
+@ref{Old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.57 available. @emph{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.
+@*
+@ref{Changes},
+@ref{Old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.56 available. @emph{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 @code{\pointAndClickOn},
+@code{\pointAndClickOff} have also been added.
+@*
+@ref{Changes},
+@ref{Old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.55 available. @emph{August 6, 2008}
+
+LilyPond 2.11.55 is out. This release fixes several bugs, and for octavation brackets
+@code{set-octavation} has been replaced by a more user-friendly command, @code{\ottava}.
+@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_55&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{Old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.54 available. @emph{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 @code{short-indent}
+so that short instrument names are no longer indented in the margin.
+@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_54&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{Old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.53 available. @emph{July 23, 2008}
+
+LilyPond 2.11.53 is out. This release fixes a lot of bugs.
+@*
+@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_53&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{Old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.52 available. @emph{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. @ref{Changes},
+@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_52&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{Old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.51 available. @emph{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 @code{fret-diagram-details} property.
+@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_51&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{Old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.50 available. @emph{July 2, 2008}
+
+Release 2.11.50 adds support for metronome marks with text, and
+backslashed numbers for figured bass, contributed by
+Reinhold Kainhofer.
+@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_50&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{Old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading The LilyPond Report #13. @emph{June 23, 2008}
+
+This short, informal, weekly opinion column is about the LilyPond project: its team, its world, its community.
+Follow @uref{http://valentin.villenave.info/The-LilyPond-Report-13,this link} to read the full issue...
+@newsEnd
+
+
+@newsItem
+@subsubheading The LilyPond Report #12. @emph{June 16, 2008}
+
+This short, informal, weekly opinion column is about the LilyPond project: its team, its world, its community.
+Follow @uref{http://valentin.villenave.info/The-LilyPond-Report-12,this link} to read the full issue...
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.49 released. @emph{June 12, 2008}
+
+LilyPond 2.11.49 is out. It fixes a number of bugs, including bugs in beams formatting.
+@*
+@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_49&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{Old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.48 released. @emph{June 9, 2008}
+
+LilyPond 2.11.48 is out. This release fixes a few bugs, and
+@code{\compressMusic} has been renamed
+to @code{\scaleDurations}.
+@*
+@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_48&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{Old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading The LilyPond Report #11. @emph{June 9, 2008}
+
+This short, informal, weekly opinion column is about the LilyPond project: its team, its world, its community.
+Follow @uref{http://valentin.villenave.info/The-LilyPond-Report-11,this link} to read the full issue...
+@newsEnd
+
+
+@newsItem
+@subsubheading The LilyPond Report #10. @emph{June 2, 2008}
+
+Welcome to this special tenth issue of the @emph{LilyPond Report}, entirely dedicated to Algorithmic Composition systems.@*
+Follow @uref{http://valentin.villenave.info/The-LilyPond-Report-10,this link} to read the full issue...
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.47 released. @emph{May 28, 2008}
+
+LilyPond now allows all text context properties to be markups,
+except in @code{\lyricmode}. This release also fixes
+regression tests maintenance for developers.
+@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_47&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{Old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.46 available. @emph{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.
+@ref{Changes},
+@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_46&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{Old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading RSS feed - @emph{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.
+@uref{http://lilypond.org/web/lilypond-rss-feed.xml,Feed URL}.
+The info mailing list (see @ref{Contact}) is still used to
+announce releases and special events.
+@newsEnd
+
+
+@newsItem
+@subsubheading The LilyPond Report #9. @emph{May 05, 2008}
+
+Welcome to this ninth issue of the @emph{LilyPond Report}!@*
+This short, informal, weekly opinion column is about the LilyPond project: its team, its world, its community.
+Follow @uref{http://valentin.villenave.info/The-LilyPond-Report-9,this link} to read the full issue...
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.45 available. @emph{April 26, 2008}
+
+Release 2.11.45 fixes a couple of bugs in the formatting
+engine. @code{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.
+@ref{Changes},
+@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_45&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{Old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.44 available. @emph{April 14, 2008}
+
+Release 2.11.44 is available. Support for figured bass and chord
+names has been added to the MusicXML
+converter. @uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_44&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{Old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading lilypond.org日本語訳 (lilypond.org Japanese translation). @emph{2008年4月8日 (April 4, 2008)}
+
+Lilypond.orgのいくつかのページの日本語訳が出来ました。
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.43 available. @emph{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. @uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_43&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{Old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.42 available. @emph{March 9, 2008}
+
+Release 2.11.42 is out. It fixes some formatting and spacing
+bugs. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_42&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading Comparison of music engraving with Finale and LilyPond. @emph{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.
+@uref{http://www.musicbyandrew.ca/finale-lilypond-1.html,Read
+the articles}.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.41 available. @emph{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. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_41&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.37 available. @emph{January 3, 2008}
+
+Release 2.11.37 is available. It has a few bugfixes, and
+documentation changes. (@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.36 available. @emph{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. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_36&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes}, @ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.33 and 2.10.33 available. @emph{September 20, 2007}
+
+Release 2.11.33 is now available.
+(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_33&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
+2.10}, @uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_33&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
+2.11}, @ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.32 available. @emph{September 2, 2007}
+
+Release 2.11.32 is now available.
+(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_32&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes}, @ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.31 available. @emph{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.
+(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_31&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes}, @ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.30 available. @emph{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. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_30&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes}, @ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.10.29 and 2.11.29 available. @emph{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.
+(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_29&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
+2.10}, @uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_29&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
+2.11}, @ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.28 for FreeBSD x86_64. @emph{August 10, 2007}
+
+Release 2.11.28 is now available as a binary installer for
+FreeBSD x86_64. Download
+@uref{http://lilypond.org/download/binaries/freebsd-64/lilypond-2.11.28-1.freebsd-64.sh,the installer} and
+do @emph{sh lilypond-2.11.28-1.freebsd-64.sh} in a command window.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.28 available - @emph{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.
+(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_28&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
+2.11}, @ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.26 available - @emph{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!
+(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_26&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
+2.11}, @ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.10.25 and 2.11.25 available - @emph{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!
+(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_25&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
+2.11}, @uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_25&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
+2.10}, @ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.10.23 and 2.11.23 available - @emph{May 1, 2007}
+This has lots of bugfixes. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_23&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
+2.11}, @uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_23&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
+2.10}, @ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading Übersetzung der Dokumentation - @emph{10. April 2007}
+Die Kapitel 1-5 (der Abschnitt für Anfänger) des
+LilyPond-Benutzerhandbuchs
+sind auf deutsch übersetzt — sie sind erhältlich für
+die @ref{Changes}
+online und @ref{Old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.22 available - @emph{April 10, 2007}
+This release has updates of the dot collision code. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_22&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
+}, @ref{Changes}, @ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.21 available - @emph{March 24, 2007}
+This release has some documentation updates.
+(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_21&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
+}, @ref{Changes}, @ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading Traduction de la documentation en français - @emph{25 février 2007}
+Les chapitres 1 à 4 et 6 du manuel de l'utilisateur sont
+désormais traduits, et disponibles en ligne — @uref{@@DOC@@v2.10/Documentation/user/lilypond/index.fr.html,version
+2.10}, @uref{@@DOC@@v2.11/Documentation/user/lilypond/index.fr.html,version
+2.11}. Les traductions sont également incluses dans la @uref{install,documentation téléchargeable}.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.10.20 and 2.11.20 available - @emph{February 25, 2007}
+This release fixes many bugs.
+(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_20&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
+2.11},
+@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_20&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
+2.10}, @ref{Changes}, @ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.10.19 and 2.11.19 available - @emph{February 18, 2007}
+This release fixes many bugs.
+(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_19&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
+2.11},
+@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_19&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
+2.10}, @ref{Changes}, @ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.18 available - @emph{February 12, 2007}
+This release fixes still more bugs, and included
+singing support through festival contributed by Milan Zamazal. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_18&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
+2.11}, @ref{Changes}, @ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.17 available - @emph{February 9, 2007}
+This release fixes still more bugs.
+(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_17&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
+2.11}, @ref{Changes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.10.16 and 2.11.16 available - @emph{February 4, 2007}
+This release fixes many bugs.
+(@uref{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.11},
+@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_16&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
+2.10},
+@ref{Changes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.10.15 and 2.11.15 available - @emph{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. (@uref{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.11},
+@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_15&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
+2.10},
+@ref{Changes}, @ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.10.14 and 2.11.14 available - @emph{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.
+(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_14&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{Changes}, @ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.10.13 and 2.11.13 available - @emph{January 17, 2007}
+This release fixes a few minor but irritating bugs. In addition, the
+2.11 release has updates of the tutorial.
+(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_13&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{Changes}, @ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.12 available - @emph{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.
+(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_12&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{Changes}, @ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.10.12 available - @emph{January 17, 2007}
+This release mirrors 2.11.12. Notably, it has the same memory
+usage improvements. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_12&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{Changes}, @ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.10.11 available - @emph{January 12, 2007}
+This release mostly has the same fixes as 2.11.11. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_11&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{Changes}, @ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.11 available - @emph{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. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_11&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{Changes}, @ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.10 available - @emph{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. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_10&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{Changes}, @ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.10.10 available - @emph{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 (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_10&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{Changes}, @ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.9 and 2.10.9 available - @emph{January 3, 2007}
+This release has a couple of bugfixes, and —in 2.11.9&mdash
+further improvements in the regression test suite (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_9&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{Changes}, @ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.8 and 2.10.8 available - @emph{January 3, 2007}
+New! Improved! With even more bugfixes! (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_8&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{Changes}, @ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading @code{lilypond.org} auf deutsch - @emph{31. Dezember 2006}
+Die LilyPond-Webseiten sind jetzt auch auf deutsch übersetzt!
+@newsEnd
+
+
+@newsItem
+@subsubheading @code{lilypond.org} en español - @emph{December 29, 2006}
+¡Ya está disponible la versión en español del sitio web de LilyPond!
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.7 and 2.10.7 available - @emph{January 1, 2007}
+New! Improved! With even more bugfixes! (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_7&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{Changes}, @ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.6 available - @emph{December 30, 2006}
+This release supports arbitrary fractional alterations, allowing
+music with different microtonal conventions to be typeset.
+(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_6&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{Changes}, @ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.10.6 available - @emph{December 30, 2006}
+New! Improved! With even more bugfixes!
+(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_6&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{Changes}, @ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.5 available - @emph{December 24, 2006}
+These releases complete the translation infrastructure for
+Documentation.
+(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_5&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{Changes}, @ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.10.5 available - @emph{December 24, 2006}
+New! Improved! With even more bugfixes!
+(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_5&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{Changes}, @ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.4 available - @emph{December 21, 2006}
+The vertical spacing improvements that were introduced in 2.11.0 now work
+within a system as well as between systems. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_4&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{Changes}, @ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.3 available - @emph{December 19, 2006}
+This release has @uref{http://lilypond.org/doc/v2.11/compare-v2.10.3/index.html,graphical
+test results} and several website build improvements. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_3&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{Changes}, @ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.10.3 available - @emph{December 19, 2006}
+This release fixes several bugs.
+(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_3&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LinuxPPC binaries available! - @emph{December 19, 2006}
+From now on, our GUB binary builds include support for Linux/PPC. (@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading Traduction du tutoriel en français. @emph{December 13, 2006}
+Fruit du travail d'une équipe de traducteurs, le tutoriel en
+français est maintenant disponible en ligne. @uref{@@DOC@@v2.10/Documentation/user/lilypond/Tutorial.fr.html,Version
+2.10}, @uref{@@DOC@@v2.11/Documentation/user/lilypond/Tutorial.fr.html,Version
+2.11}.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.2 available - @emph{December 12, 2006}
+This release supports glissandi and harmonics in tablature. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_2&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{Changes}, @ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.10.2 available - @emph{December 12, 2006}
+A new stable release of LilyPond is available. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_2&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.1 available - @emph{December 4, 2006}
+This release has improved support for horizontal spacing. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_1&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{Changes}, @ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.10.1 available - @emph{December 3, 2006}
+A new stable release of LilyPond is available. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_1&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.0 available - @emph{November 27, 2006}
+This release has improved support for vertical spacing. (@ref{Changes}, @ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.10.0 available - @emph{November 11, 2006}
+A new stable release of LilyPond is available. (@uref{announce-v2.10.html,Announcement}, @ref{Changes}, @ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading GIT repository online - @emph{November 11, 2006}
+LilyPond development has moved over its source code to @uref{http://git.or.cz,GIT}, the fast version control
+system. Check out our repository at @uref{http://git.sv.gnu.org/gitweb/?p=lilypond.git;a=summary,gnu.org}.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.9.29 available - @emph{November 5, 2006}
+This release has many more bugfixes. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_9_29&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.9.28 available - @emph{November 3, 2006}
+This release has many more bugfixes. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_9_28&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.9.27 available - @emph{October 28, 2006}
+This release has a new @code{FretBoards} context, and some further
+bugfixes. (@ref{Changes}, @uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_9_27&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading Music streams thesis available - @emph{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
+(@ref{Publications}).
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.9.26 available - @emph{October 20, 2006}
+This release has further bugfixes. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_9_26&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.9.25 available - @emph{October 18, 2006}
+This release has more bugfixes; from now on, binaries are also
+available for x86/64. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_9_25&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.9.24 available - @emph{October 15, 2006}
+This release has support for right hand guitar fingerings, and offers
+some bugfixes. (@ref{Changes},
+@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed2924&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.9.23 available - @emph{October 12, 2006}
+This release cuts fragments of EPS directly from your finished score,
+and makes it easier to insert ties into lyrics. (@ref{Changes}, @ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.9.22 available - @emph{October 9, 2006}
+Test this release candidate for LilyPond 2.10! (@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.9.21 available - @emph{October 4, 2006}
+Test this release candidate for LilyPond 2.10! (@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.9.20 available - @emph{October 3, 2006}
+Test this release candidate for LilyPond 2.10! (@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.9.17 available - @emph{September 2, 2006}
+This release fixes many bugs. Among others, MacOS X QuickTime now
+honors tempo changes are in the MIDI output. (@ref{Changes}, @ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.9.16 available - @emph{August 25, 2006}
+In this release, chords may be partially tied and lyric extenders have
+tunable padding. Moreover, many bugs were fixed
+(@ref{Changes}, @ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.9.15 available - @emph{August 20, 2006}
+This releases fixes many bugs in the 2.9.14 release. (@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.8.6 available - @emph{August 8, 2006}
+This release contains a few minor bugfixes; the source tarball is also
+available. (@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.9.14 available - @emph{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. (@ref{Changes}, @ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.9.13 available - @emph{July 23, 2006}
+This release supports doits and falls, and more tuning options for
+grace note spacing and tuplet brackets. (@ref{Changes}, @ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.9.12 available - @emph{July 18, 2006}
+This release supports pdftex for lilypond-book, and uses PdfTeX for
+generating manuals, so page numbers and references are now clickable.
+(@ref{Changes}, @ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.9.11 available - @emph{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. (@ref{Changes}, @ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.9.10 available - @emph{June 15, 2006}
+This releases fixes a couple of bugs in 2.9.9.
+(@ref{Changes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.9.9 available - @emph{June 15, 2006}
+This releases fixes many bugs in 2.9.8 and earlier.
+(@ref{Changes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.9.8 available - @emph{June 6, 2006}
+2.9.8 has support for different spacing sections within a single
+score, and better infrastructure for automated regression testing.
+(@ref{Changes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.8.4 available - @emph{June 4, 2006}
+2.8.4 fixes some minor bugs, and includes a backport of the
+infrastructure for automated regression testing.
+(@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading First test results available - @emph{June 4, 2006}
+After a week of frantic tweaking, the first automated testing results
+are available. You can now see @uref{http://lilypond.org/doc/v2.9/compare-v2.8.4/index.html,in full
+glory} what features are broken in the development release
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.9.7 available - @emph{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
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.9.6 available - @emph{May 24, 2006}
+This
+release has new features in beam formatting: beams may now be put on
+single stems, and obey the @code{beatGrouping} property. MusicXML
+converter. (@ref{Changes}, @ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading New essay pages! - @emph{May 22, 2006}
+The @emph{Automated Engraving} essay has been updated with material
+from the @uref{http://fisl.softwarelivre.org,FISL} talk, with
+pages on @uref{about/automated-engraving/problem-statement,modeling
+notation} and @uref{about/automated-engraving/scoring-esthetics,algorithms for
+esthetics}. Happy reading!
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.9.5 available - @emph{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.
+(@ref{Changes}, @ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.9.4 available - @emph{May 12, 2006}
+This release has support for feathered beaming, and note head styles in
+the markup @code{\note} command. In addition, it has a lot of updates
+of the manual and a clean up of the spring spacer.
+(@ref{Changes}, @ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.8.2 available - @emph{May 12, 2006}
+This release has fixes for minor bugs and compilation issues.
+(@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.9.3 is out! - @emph{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. (@ref{Changes}, @ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading FISL7.0 slides available - @emph{April 22, 2006}
+The slides for Han-Wen's talk at
+@uref{http://fisl.softwarelivre.org,FISL 7} are now online.
+(@ref{Publications})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.8.1 is out! - @emph{April 3, 2006}
+Important bugfixes include CJK font handling and a Darwin/x86 port.
+(@ref{Changes}, @ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.9.1 is out! - @emph{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.
+(@ref{Changes}, @ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond on MacOS X/Intel - @emph{March 31, 2006}
+LilyPond now also runs on Intel based macs, offering a 400%
+speedup over the emulated PowerPC binaries. (@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.8.0 is out! - @emph{March 22, 2006}
+Version 2.8 is here! Read the @uref{announce-v2.8.html,release
+announcement}. (@ref{Changes}, @ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.39 is out - @emph{March 17, 2006}
+This release has even more bug fixes. Please test before 2.8 is
+released. (@ref{Changes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.38 is out - @emph{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.
+(@ref{Changes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.37 is out - @emph{March 4, 2006}
+This release has more bug fixes. Please help us by testing it!
+(@ref{Changes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.36 is out - @emph{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. (@ref{Changes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.35 is out - @emph{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 @strong{very} welcome. By
+definition a bug is release critical if it wasn't present in version
+2.6. (@ref{Changes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.34 is out - @emph{February 16, 2006}
+This release has a bunch of bugfixes, and new features. Newly created
+contexts may also be named with @code{\new Voice =
+"alto"}. Thicknesses of tie and slurs may be tuned separately for
+the endings and the middle
+part. (@ref{Changes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.33 is out - @emph{February 10, 2006}
+Items directly connected with a music input element may be
+parenthesized, for example,
+@verbatim
+{
+ c4 -\parenthesize -.
+ <d \parenthesize fis a>
+}
+@end verbatim
+
+This feature was sponsored by Ramana Kumar. (@ref{Changes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.32 is out - @emph{February 7, 2006}
+This release contains some syntax changes: words inside the \paper and
+\layout block are henceforth written with dashes, for instance:
+
+@verbatim
+{
+ \layout {
+ ragged-right = ##t
+ }
+}
+@end verbatim
+
+Furthermore, in this release, we have dropped some legacy code from
+our library. Now, lily uses standard C++ strings and the STL
+vector. (@ref{Changes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.31 is out - @emph{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.
+(@ref{Changes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.30 is out - @emph{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. (@ref{Changes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.29 is out - @emph{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). (@ref{Changes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.28 is out - @emph{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. (@ref{Changes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.27, release 4 - @emph{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! (@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.27, release 3 - @emph{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 @strong{FreeBSD} as well! Jump
+to the @ref{Old downloads} get them!
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.27 binaries are out - @emph{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
+@uref{http://lilypond.org/download/binaries/linux-x86/lilypond-2.7.27-1.linux.sh,
+Linux/x86},
+@uref{http://lilypond.org/download/binaries/MacOS/lilypond-2.7.27-2.zip,
+MacOS X} and
+@uref{http://lilypond.org/download/binaries/mingw/lilypond-2.7.27-2.exe,
+Windows}.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.27 is out - @emph{January 7, 2006}
+This release allows you to switch staff lines on and off individually
+(feature sponsored by Andrea
+Valle). (@ref{Changes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading Linux Journal article - @emph{January 2006}
+Linux Journal publishes an article on
+@uref{http://www.linuxjournal.com/article/8364,@emph{Make
+Stunning Schenker Graphs with GNU LilyPond}}. 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.”
+This article is now available @uref{http://www.linuxjournal.com/article/8583,on-line}.
+@newsEnd
+
+
+@newsItem
+@subsubheading New binaries for LilyPond 2.7.26 - @emph{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 @ref{Old downloads}
+page. Let us know how you fare!
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.26 is out - @emph{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!
+(@ref{Changes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.25 is out - @emph{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). (@ref{Changes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.24 is out - @emph{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. (@ref{Changes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.23 is out - @emph{December 19, 2005}
+This release has the following new features:
+@itemize
+@item
+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).
+@item
+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).
+@item
+Generic music functions may now also be used on
+articulations and chord elements (feature sponsored by Sean Reed and
+Bertalan Fodor).
+@item
+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.
+@end itemize
+(@ref{Changes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.22 is out - @emph{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. (@ref{Changes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.21 is out - @emph{December 5, 2005}
+Saint Nicholas brings you ... a @uref{http://www.musicxml.org/,MusicXML} convertor for LilyPond!
+The convertor is basic, but working. Check out the @uref{http://www.lilypond-design.com/sponsor/open-features.html#inputfilter,
+LilyPond Software Design} pages for MusicXML features that can be
+sponsored.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.20 is out - @emph{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). (@ref{Changes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.6.5 is out - @emph{December 1, 2005}
+This release updates the bugreporting address and reorganizes the
+documentation tree. (@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.19 is out - @emph{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. (@ref{Changes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.18 is out - @emph{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. (@ref{Changes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.17 is out - @emph{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. (@ref{Changes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.16 is out - @emph{November 11, 2005}
+This release fixes a large number of bugs. Please upgrade before
+reporting bugs in the 2.7 series. (@ref{Changes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.15 is out - @emph{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. (@ref{Changes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.14 is out - @emph{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.
+@verbatim
+
+\override Beam #'direction = #(lambda (grob)
+(if (> (random 10) 5) UP DOWN))
+
+@end verbatim
+will set a random direction for beams. (@ref{Changes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.13 is out - @emph{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. (@ref{Changes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.6.4 is out - @emph{October 11, 2005}
+This release fixes a few minor problems with the stable
+series. (@ref{Changes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.12 is out - @emph{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). (@ref{Changes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.11 is out - @emph{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. (@ref{Changes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.10 is out - @emph{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. (@ref{Changes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.9 is out - @emph{September 5, 2005}
+This is mainly a bugfix
+release. (@ref{Changes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading Traduction française du site - @emph{September 03, 2005}
+Grâce à @uref{about/thanks#website,l'équipe des traducteurs},
+de nombreuses pages du site sont maintenant disponibles en français,
+notamment l'@uref{about/automated-engraving/index.fr.html,essai sur
+la gravure musicale}.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.8 is out - @emph{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. (@ref{Changes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading Article in `De Standaard' - @emph{August 20, 2005}
+The Belgian newspaper @emph{De Standaard} investigates what drives
+Free Software authors in an article titled @emph{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.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.7 is out - @emph{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á. (@ref{Changes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.6 is out - @emph{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. (@ref{Changes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.5 is out - @emph{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. (@ref{Changes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.4 is out - @emph{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. (@ref{Changes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.6.3 is out - @emph{August 4, 2005}
+This release fixes a memory corruption bug that was triggered by
+\override'ing Beam settings. (@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.6.2 is out - @emph{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. (@ref{Changes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.3 is out - @emph{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.
+(@ref{Changes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.2 is out - @emph{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. (@ref{Changes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.6 released - @emph{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).
+@strong{Get up and running in minutes!} Pango text formatting lets you
+print @strong{Unicode } lyrics in your favorite script and font. Create
+@strong{SVG} files, and edit them in Inkscape.
+(@uref{announce-v2.6.html,Announcement}, @ref{Old downloads}, @ref{Changes})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.1 is out - @emph{July 20, 2005}
+LilyPond 2.7.1 has no user-visible changes. However, due to
+restructuring @qq{under the hood}, this version will be 10 to
+20 % faster. (@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.6.1 is out - @emph{July 11, 2005}
+This version fixes a few minor bugs found in
+2.6.0, and also works on DOS-based Windows versions. (@ref{Changes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7 is out - @emph{July 9, 2005}
+LilyPond 2.7.0 is out. It has support for paragraph text and
+pitched trill notation. (@ref{Changes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading 2.5.31 released - @emph{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.
+(@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading Traduction du site de LilyPond - @emph{15 juin 2005}
+@uref{about/thanks#website,L'équipe des traducteurs} vous présente
+le site de LilyPond en français. Nous travaillons sur la traduction des
+pages encore non traduites. Bon surf !
+@newsEnd
+
+
+@newsItem
+@subsubheading 2.5.31 for Windows and MacOS - @emph{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.
+(@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading 2.5.31 released - @emph{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. (@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading 2.5.30 released - @emph{June 10, 2005}
+This is (hopefully) the last Release Candidate before 2.6. Give it a
+good shake to find those last bugs! (@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading 2.5.29 released - @emph{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). (@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading 2.5.27 released - @emph{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. (@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading Windows and MacOS installers available - @emph{May 26, 2005}
+There are now a native, standalone installers for Windows and
+MacOS. They also support PDF point & click. (@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading 2.5.26 released - @emph{May 26, 2005}
+This release has a couple of small bugfixes.
+@newsEnd
+
+
+@newsItem
+@subsubheading 2.5.25 released - @emph{May 20, 2005}
+This release has many small bugfixes and updates to the
+documentation. (@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading 2.5.24 released - @emph{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. (@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading 2.5.23 released - @emph{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. (@ref{Changes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading 2.5.22 released - @emph{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.
+(@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+(@ref{Changes},
+@ref{Old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading 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 @ref{Changes}
+file, or go straight to @ref{Old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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 @ref{Changes}
+file and @ref{Old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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. @ref{Old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading 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. @ref{Old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{Old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading 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 @ref{Changes}
+file and @ref{Old downloads}!
+@newsEnd
+
+
+@newsItem
+@subsubheading 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 @ref{Changes}
+file and download @ref{Old downloads}!
+@newsEnd
+
+
+@newsItem
+@subsubheading March 7, 2005
+LilyPond 2.4.5 is out. This release backports the tieWaitForNote
+feature and has support for tetex-3.0.
+@ref{Old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading February 28, 2005
+LilyPond 2.5.13 is available for Fedora Core 3. You need to install @uref{http://lilypond.org/download/binaries/Fedora-3/ghostscript-8.15rc3-0.i386.rpm,ESP
+Ghostscript 8.15rc3}. 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.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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 @uref{http://lilypond.org/doc/v2.5/Documentation/user/out-www/lilypond/Point-and-click.html,here}.
+Take a look at the @ref{Changes}
+file and download @ref{Old downloads}!
+@newsEnd
+
+
+@newsItem
+@subsubheading February 26, 2005
+The @uref{http://lsr.dsi.unimi.it/,Lilypond Snippet
+Repository (LSR)} 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.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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 @strong{all}
+fonts available via FontConfig. Also, arpeggios may be written out
+using ties and individual objects may have colors! Take a look at
+the @ref{Changes}
+file and @ref{Old downloads}!
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{Old downloads}!
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{Old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{Old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading 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
+@uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.3065&content-type=text/vnd.viewcvs-markup,
+change log
+} and @ref{Old downloads}!
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{Old downloads}
+and check out the changes in
+the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.3048&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{Old downloads}
+and check out the
+changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.3013&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{Old downloads}
+and check out the changes in
+the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev= 1.3000&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{Old downloads}
+and check out the
+changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2974&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{Old downloads}
+and
+check out the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2908&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{Old downloads}
+and check out the changes in
+the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2898&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{Old downloads}
+and check out the changes in
+the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2881&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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
+@verbatim
+
+\cueDuring #VOICE-NAME #DIRECTION { MUSIC }
+
+@end verbatim
+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.
+@ref{Old downloads}
+and check out
+the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2837&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{Old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{Old downloads}
+and check out the changes in
+the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2780.2&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading October 31, 2004
+LilyPond 2.4.0 was just @uref{announce-v2.4.html,released!}
+This new stable version has support for page-layout,
+completely rewritten slur formatting and many other
+improvements. Read about them in the @ref{Changes}
+file.
+@ref{Old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{Old downloads}
+and check out the changes in
+the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2773&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{Old downloads}
+and check out the changes in
+the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2765&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{Old downloads}
+and check out the changes in
+the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2752&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{Old downloads}
+and check out the changes in
+the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2742&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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@{@}.
+@ref{Old downloads}
+and
+check out the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2709&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{Old downloads}
+and check
+out the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2692&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{Old downloads}
+and check out the changes in
+the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2674&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading September 29, 2004
+The LilyPond development team will be present at the @uref{http://www.nluug.nl/events/sane2004/bazaar/index.html,Free
+Software Bazaar} 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.
+@newsEnd
+
+
+@newsItem
+@subsubheading September 26, 2004
+LilyPond 2.3.19 is out. It's mainly a bugfix release.
+@ref{Old downloads}
+and check out the changes
+in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2652&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{Old downloads}
+and check out the changes in
+the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2614&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{Old downloads}
+and check out the changes in
+the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2562&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{Old downloads}
+and check out the changes in
+the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2553&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{Old downloads}
+and check out
+the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2534&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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!
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{Old downloads}
+and
+check out the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2520&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading August 24, 2004
+LilyPond 2.2.6 fixes a few minor issues, among others, the
+disappearing metronome mark.
+@ref{Old downloads}
+and check out the changes in
+the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2000.2.33&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{Old downloads}
+and check out the changes in
+the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2489&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading August 3, 2004
+LilyPond 2.3.11 is out. This release basically is 2.3.10 with a few
+annoying bugs fixed.
+@ref{Old downloads}
+and check out
+the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2449&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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:
+@itemize
+@item
+Running trills now have their own spanner and event. They are
+started and stopped with \startTrillSpan and \stopTrillSpan
+@item
+There is a new markup command `\postscript' that takes a string
+that is dumped as verbatim PostScript
+@end itemize
+
+@ref{Old downloads}
+and check out
+the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2435&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{Old downloads}
+and check out
+the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2416&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{Old downloads}
+and check out the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2395&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{Old downloads}
+and check out the changes in
+the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2383&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading July 15, 2004
+LilyPond 2.2.5 was released. It has a few bug fixes from
+2.3.x.
+@ref{Old downloads}
+and check
+out the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2000.2.28&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading July 11, 2004
+An introductory article on LilyPond appeared on @uref{http://www.linuxjournal.com/article.php?sid=7657&mode=thread&order=0,Linux
+Journal}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{Old downloads}
+and check out the changes
+in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2306&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading July 5, 2004
+LilyPond 2.2.4 was released. It is mainly a bug fix
+release.
+@ref{Old downloads}
+and
+check out the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2000.2.23&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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 @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2293&content-type=text/vnd.viewcvs-markup,ChangeLog}
+and
+@ref{Old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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 @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2000.2.16&content-type=text/vnd.viewcvs-markup,ChangeLog} for a full description and
+@ref{Old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading June 13, 2004
+LilyPond 2.3.4 further improves the output backends. As a
+result, manual page-breaks, multiple output formats and putting
+@code{\score} into markups now works. Check out the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2242&content-type=text/vnd.viewcvs-markup,ChangeLog}
+and
+@ref{Old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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 @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2207&content-type=text/vnd.viewcvs-markup,ChangeLog}
+and
+@ref{Old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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 @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2000.2.9,ChangeLog}
+or head straight to the
+@ref{Old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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 @ref{Changes} or head straight to the
+@ref{Old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading May 9, 2004
+LilyPond 2.3.1 is out. This release has many new and cool
+features. Check out the @ref{Changes} or head straight to the
+@ref{Old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading May 4, 2004
+Help LilyPond get better, and join in on LilyPond
+development! This
+@uref{devel/participating/call-for-help.html,call for
+help} 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!
+@newsEnd
+
+
+@newsItem
+@subsubheading May 3, 2004
+LilyPond 2.2.1 has been released. It fixes a handful of bugs.
+@ref{Old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading April 17, 2004
+LilyPond 2.2.0 is now available
+on Windows, and should find its way to the Cygwin mirrors
+soon.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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 @emph{experimental}; expect things to break!
+More info in the @ref{Changes}.
+@ref{Old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading April 8, 2004
+A French article on the new LilyPond
+release appeared on @uref{http://linuxfr.org/2004/04/08/15968.html,linuxfr.org}.
+@newsEnd
+
+
+@newsItem
+@subsubheading April 8, 2004
+Binaries for LilyPond 2.2.0 are available for
+MacOS X, Slackware, Mandrake and Debian Woody.
+@ref{Old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading 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 @uref{announce-v2.2.html,announcement} or skip to the
+@ref{Old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{Old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading March 30, 2004
+LilyPond 2.1.36 has many fixes in
+the user manual.
+@ref{Old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading March 28, 2004
+LilyPond 2.1..35 fixes a slew of
+bugs, and has the @code{raggedlast} option, which causes
+paragraph like line breaking for scores. More info in the
+@ref{Changes}.
+@ref{Old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading March 22, 2004
+LilyPond 2.1.34 fixes minor bugs, and has more rewriting.
+@ref{Old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading March 21, 2004
+LilyPond 2.1.33 fixes a serious bug, and a few other
+irritations.
+@ref{Old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading 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).
+@ref{Old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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
+@ref{Changes} and
+@ref{Old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading March 14, 2004
+The
+@uref{http://linuxmusician.com/index.php?option=articles&task=viewarticle&artid=10,linuxmusician.com interview} made the
+@uref{http://slashdot.org/article.pl?sid=04/03/13/2054227&mode=thread&tid=141&tid=188,slashdot
+frontpage!}.
+@newsEnd
+
+
+@newsItem
+@subsubheading March 11, 2004
+@uref{http://linuxmusician.com,linuxmusician.com} is
+running an
+@uref{http://linuxmusician.com/index.php?option=articles&task=viewarticle&artid=10,interview}
+with Han-Wen Nienhuys and Jan Nieuwenhuizen, the main
+authors of LilyPond.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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
+@ref{Changes} and
+@ref{Old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading March 9, 2004
+LilyPond 2.1.29 fixes a couple of MIDI bugs, and has
+experimental support for producing titles with
+@code{markup}.
+@newsEnd
+
+
+@newsItem
+@subsubheading February 29, 2004
+In LilyPond 2.1.28 Scheme property functions may be used
+argument to @code{set!}. In addition, parts of the manual
+have been proofread and corrected in this release. See the
+@ref{Changes} and
+@ref{Old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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
+@ref{Changes} and
+@ref{Old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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
+@ref{Changes}.
+@ref{Old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading February 18, 2004
+LilyPond 2.1.25 fixes many bugs, and changes the conventions
+for altering accidental rules.
+@ref{Old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading February 16, 2004
+LilyPond 2.1.24 has a big
+internal rewrite. One of its practical consequences is that
+@code{\with} now also works with @code{Score}
+contexts. Further 2.1.23, which was not announced here,
+fixes a few bugs caused by the change of @code{\property}
+syntax and has updates in the Program Reference document.
+More information in the
+@ref{Changes}.
+@ref{Old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading February 13, 2004
+LilyPond 2.1.22 has a
+simplification of the @code{\property} syntax: it is
+shorter and more consistent now. More information in the
+@ref{Changes}.
+@ref{Old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading 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
+@ref{Changes}.
+@ref{Old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading 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
+@ref{Changes}.
+@ref{Old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading February 5, 2004
+LilyPond 2.1.19 has rewritten
+support for drum notation. This release also makes some
+long-standing cleanups: the removal of @code{Thread} (all
+functionality is now moved into @code{Voice}) and Lyrics
+(functionality moved to @code{LyricsVoice}) context.
+More information in the
+@ref{Changes}.
+@ref{Old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading February 4, 2004
+LilyPond 2.1.18 is out. This
+release has the new part-combiner installed by default, and a
+similar implementation of @code{autochange}. More information
+in the
+@ref{Changes}.
+@ref{Old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading February 2, 2004
+LilyPond 2.1.17 is out. It adds texts
+(solo, a due) for the part combiner. It also reinstates the
+@code{--safe} option which prevents havoc by Scheme exploits. More
+information in the
+@ref{Changes}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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
+@ref{Changes}.
+@ref{Old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading 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
+@ref{Changes}. @ref{Old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading 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
+@ref{Changes}. @ref{Old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{Old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading January 19, 2004
+LilyPond 2.1.12 fixes many bugs
+and improves formatting of ottava brackets. More information in
+the
+@ref{Changes}. @ref{Old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading January 18, 2004
+LilyPond 2.1.11 is now also
+available for Windows! For downloading, go
+@uref{http://www.inf.bme.hu/~berti/lilypond/,here}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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
+@ref{Changes}. @ref{Old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading January 16, 2004
+LilyPond 2.1.10 has a load of
+bugfixes and a shorter syntax for octave checks. More
+information in the
+@ref{Changes}. @ref{Old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading 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
+@ref{Changes}. @ref{Old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading January 9, 2004
+LilyPond 2.1.8 has an important new
+feature: it is now possible to use @code{\property} to tune
+the appearance of spanning objects like @code{StaffSymbol} and
+@code{SystemStartBrace}. In addition, contexts may be
+modified with @code{\remove} and @code{\consists} for
+individual music expressions.
+More information in the
+@ref{Changes}. @ref{Old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading January 7, 2004
+An update to the stable branch,
+version 2.0.2, was released today. It contains a couple of
+minor bugfixes. @ref{Old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading 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
+@ref{Changes} and download @uref{install/#2.1,here}.
+@newsEnd
+
+
+@newsItem
+@subsubheading January 4, 2004
+LilyPond 2.1.6 continues to
+improve the layout of lyrics. More
+information in the
+@uref{@@DOC@@v2.1/Documentation/topdocs/out-www/NEWS.html,release
+notes} and download @uref{install/#2.1,here}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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ängers Morgen. More
+information in the
+@ref{Changes} and download @uref{install/#2.1,here}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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
+@ref{Changes} and download @uref{install/#2.1,here}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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
+@ref{Changes} and download @uref{install/#2.1,here}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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
+@ref{Changes} and download @uref{install/#2.1,here}.
+@newsEnd
+
+
+@newsItem
+@subsubheading December 16, 2003
+LilyPond 2.1.1 released. This
+release wraps together all the small fixes made during
+Han-Wen's absence. See the
+@ref{Changes} and download @uref{install/#2.1,here}.
+@newsEnd
+
+
+@newsItem
+@subsubheading October 11, 2003
+LilyPond 2.1.0 released. See the
+@ref{Changes} and
+download @uref{install/#2.1,here}.
+@newsEnd
+
+
+@newsItem
+@subsubheading October 11, 2003
+LilyPond 2.0.1 binaries for Mandrake 9.1
+available from
+@uref{http://rpm.nyvalls.se/sound9.1.html,here}
+thanks to Heikki Junes.
+@newsEnd
+
+
+@newsItem
+@subsubheading October 9, 2003
+LilyPond 2.0.1 binaries for Slackware 9
+available from @uref{install/#2.0,here},
+thanks to Ricardo Hoffman.
+@newsEnd
+
+
+@newsItem
+@subsubheading October 5, 2003
+LilyPond 2.0.1 binaries are available for Macos X, many thanks to
+Matthias Neeracher.
+@ref{Old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading October 4, 2003
+LilyPond 2.0.1 binaries are available for Windows (Cygwin
+version 1.5).
+@ref{Old downloads}. Thanks to Bertalan
+Fodor, our new Cygwin maintainer!
+@newsEnd
+
+
+@newsItem
+@subsubheading September 29, 2003
+LilyPond 2.0.1 is released. It
+contains minor bugfixes.
+See the @ref{Changes}
+or download @uref{install/#2.0,here} directly.
+@newsEnd
+
+
+@newsItem
+@subsubheading September 27, 2003
+PlanetCCRMA has been updated to include LilyPond 2.0. Go
+@uref{http://www-ccrma.stanford.edu/planetccrma/software/soundapps.html#lilypond,
+here} to download. Thanks to Fernando Pablo
+Lopez-Lezcano!
+@newsEnd
+
+
+@newsItem
+@subsubheading 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
+@uref{announce-v2.0.html,here}, or go to the
+@uref{install/#2.0,download page} directly.
+@newsEnd
+
+
+@newsItem
+@subsubheading September 24, 2003
+LilyPond 1.9.10 is released. This is
+the final LilyPond 2.0 release candidate. Check
+the @ref{Changes} and
+download @uref{install/,here}.
+@newsEnd
+
+
+@newsItem
+@subsubheading September 23, 2003
+LilyPond 1.9.9 is released. This is
+the second LilyPond 2.0 prerelease. Check
+the @ref{Changes} and
+download @uref{install/,here}.
+@newsEnd
+
+
+@newsItem
+@subsubheading September 19, 2003
+LilyPond 1.9.8 is released. This is
+the first LilyPond 2.0 prerelease. Check
+the @ref{Changes} and
+download @uref{install/,here}.
+@newsEnd
+
+
+@newsItem
+@subsubheading September 17, 2003
+LilyPond 1.9.7 is released. LilyPond
+now has support for quarter tone accidentals!
+@ref{Old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading September 16, 2003
+LilyPond 1.9.6 is released.
+It has a lot of minor fixes and updates.
+@ref{Old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{Old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading September 9, 2003
+LilyPond 1.8.2 is released. This
+release fixes a couple of minor bugs.
+@ref{Old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading September 7, 2003
+LilyPond 1.8 binaries are available
+for Windows (Cygwin version 1.5).
+@ref{Old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading August 31, 2003
+LilyPond 1.9.4 is released.
+@emph{This is an experimental release}: read the
+@uref{http://mail.gnu.org/archive/html/lilypond-devel/2003-08/msg00133.html,announcement}
+before trying.
+@newsEnd
+
+
+@newsItem
+@subsubheading August 31, 2003
+LilyPond 1.8 binaries for slackware
+available. Get them @uref{install/,here}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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
+@ref{Changes} and get it @uref{download#1.9,here}.
+@newsEnd
+
+
+@newsItem
+@subsubheading August 28, 2003
+LilyPond 1.9.2 is released. Read the
+@ref{Changes} and get it
+@uref{download#1.9,here}.
+@newsEnd
+
+
+@newsItem
+@subsubheading August 26, 2003
+LilyPond 1.9.1 is released. Read the
+@ref{Changes} and get it
+@uref{download#1.9,here}.
+@newsEnd
+
+
+@newsItem
+@subsubheading August 25, 2003
+The LilyPond 1.9 development release is available. Read the
+@ref{Changes} and get it
+@uref{download#1.9,here}.
+@newsEnd
+
+
+@newsItem
+@subsubheading August 25, 2003
+Mandrake 9.1 RPMS available, get them
+@uref{http://rpm.nyvalls.se/sound9.1.html,here}.
+@newsEnd
+
+
+@newsItem
+@subsubheading August 21, 2003
+LilyPond 1.8.1 was released. Get it @uref{install/,here}, or
+read the @ref{Changes}.
+@newsEnd
+
+
+@newsItem
+@subsubheading August 18, 2003
+PlanetCCRMA (eg. RedHat 8 and 9)
+has been updated to 1.8.
+Download @uref{http://www-ccrma.stanford.edu/planetccrma/software/soundapps.html#lilypond,here.}
+@newsEnd
+
+
+@newsItem
+@subsubheading August 7, 2003
+LilyPond 1.8 is released. Read
+@ref{Changes} and get it @uref{install/,here}.
+@newsEnd
+
+
+@newsItem
+@subsubheading August 7, 2003
+New website went live!
+@newsEnd
+
+
+@newsItem
+@subsubheading August 6, 2003
+Announced new website.
+@newsEnd
+
+
+@newsItem
+@subsubheading August 1, 2003
+LilyPond 1.7.30 released.
+@newsEnd
+
+
+@newsItem
+@subsubheading July 30, 2003
+Website: present @uref{about/automated-engraving/index.html,treatise}
+about music engraving, music printing software, and LilyPond's
+unique faculties.
+@newsEnd
+
+
+@newsItem
+@subsubheading July 29, 2003
+1.7.29 - release candidate 4 has been released. Packages for
+Red Hat, Debian, Cygwin are @uref{install/,available}.
+@newsEnd
+
+++ /dev/null
-\input texinfo @c -*- coding: utf-8; mode: texinfo; -*-
-@ignore
- Translation of GIT committish: FILL-IN-HEAD-COMMITTISH
-
- When revising a translation, copy the HEAD committish of the
- version that you are working on. See TRANSLATION for details.
-@end ignore
-
-@setfilename general.info
-@settitle LilyPond -- Music notation for everyone
-@documentencoding UTF-8
-@documentlanguage en
-@afourpaper
-
-@set FDL
-@set web
-@include macros.itexi
-
-@afourpaper
-
-@c don't remove this comment.
-@ignore
-@omfcreator Graham Percival and Patrick McCarty
-@omfdescription General info about the LilyPond music engraving system
-@omftype program usage
-@omfcategory Applications|Publishing
-@omflanguage English
-@end ignore
-
-
-@copying
-Copyright @copyright{} 2009 by the authors.
-
-@quotation
-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''.
-@end quotation
-@end copying
-
-
-@c TITLE PAGE
-@ifnottex
-@node Top
-@top LilyPond... music notation for everyone
-@end ifnottex
-
-
-@c hack for texi2html, bleh -gp
-@ifnothtml
-
-@finalout
-
-@titlepage
-@title LilyPond
-@subtitle The music typesetter
-@titlefont{General Information}
-@author The LilyPond development team
-
-@vskip 0pt plus 1filll
-@c @vskip 20pt
-
-@insertcopying{}
-
-For LilyPond version @version{}
-@end titlepage
-@end ifnothtml
-@c end hack for texi2html
-
-
-@c ************************ WEBSITE START ***************
-
-
-@divId{pageHeader}
-@heading LilyPond
-
-... music notation for everyone
-@divEnd
-
-@c @imageId{cmws,web-clef-g-eight-alpha.png,Catchy Musical Web Snippet}
-@imageId{lilylogo,double-lily-modified3,png,LilyPond logo}
-@c @im ageId{cmws,web-snippet-alpha.png,Catchy Musical Web Snippet}
-
-@divId{quickSummary}
-@subheading 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.
-
-@divClass{align-right}
-Read more in our @ref{introduction}!
-
-@divEnd
-@divEnd
-
-@divClass{separator}
-@divEnd
-
-
-@divId{news}
-
-@c TODO: generate this automatically, including RSS feed.
-@include general/news-front.itexi
-
-@divClass{float-right}
-(@ref{old news})
-@divEnd
-
-@divEnd
-
-
-@divId{latestVersion}
-@subheading Quick links
-
-@c TODO: javascript to detect OS and suggest download?
-
-@subsubheading Stable
-
-@ref{download, Download @versionStable}
-
-@ref{manuals, Manuals @versionStable}
-
-@subsubheading Unstable
-
-@ref{development, Download @versionDevel}
-
-@ref{development, Manuals @versionDevel}
-
-@divEnd
-
-
-@ifnottex
-
-@divClass{hide}
-@menu
-* introduction:: Start here to creating sheet music.
-* download:: Get LilyPond.
-* manuals:: Read The Fine Manuals (RTFM).
-* community:: Contact other users.
-@end menu
-@divEnd
-
-@end ifnottex
-
-@contents
-
-
-@include general/introduction.itexi
-@include general/download.itexi
-@include general/manuals.itexi
-@include general/community.itexi
-
-@bye
+++ /dev/null
-depth = ../..
-LOCALSTEPMAKE_TEMPLATES = ly
-SUBDIRS = examples
-include $(depth)/make/stepmake.make
+++ /dev/null
-@c -*- coding: utf-8; mode: texinfo; -*-
-@c This file is part of community.itexi and ../topdocs/AUTHORS.itexi
-
-@ignore
-
- This file lists authors of LilyPond, and what they wrote. Each
- list is sorted alphabetically by surname. This file lists people
- that have contributed more than a few hours of work.
-
- Developers are people who are (or have been) listed under the
- "Development Team" in the THANKS, and can choose their own
- titles. Contributors are everybody else, and simply list their
- contributions.
-
- Anybody who has finished doing a "main devel team" task should
- list it under developersPrevious, even if they're still doing
- other "main devel team" stuff. See "Graham Percival" for an
- example.
-
- Contributors are split into:
- ...Core (programming)
- ...Font (duh)
- ...Doc (documentation and examples)
- ...Support (building, distributions, editors,
- lilypond-book, LSR, but *not* answering emails)
- ...Translations (duh)
- We might add a "general" or "other" if there's something else.
-
-
-@end ignore
-
-@macro developersCurrent
-
-@itemize
-
-@item Mats Bengtsson:
-Support guru.
-
-@item Han-Wen Nienhuys:
-Main author.
-
-@item Jan Nieuwenhuizen:
-Main author.
-
-@item @uref{http://percival-music.ca, Graham Percival}:
-Project Manager.
-
-@end itemize
-@end macro
-
-
-
-@macro developersPrevious
-
-@itemize
-@item Pedro Kroeger:
-Build meister
-
-@item @uref{http://percival-music.ca, Graham Percival}:
-Documentation editor, Bug meister, Grand Documentation Project
-leader.
-
-@item Erik Sandberg:
-Bug meister
-
-@end itemize
-@end macro
-
-
-
-@macro contributorsCore
-
-@itemize
-@item Erlend Aasland:
-Color support, tablature improvements, trivial @code{\\mark} stuff,
-al-niente hairpins.
-
-@end itemize
-@end macro
-
-
-
-@macro contributorsFont
-
-@itemize
-@item @uref{http://www.juergen-reuter.de, Jürgen Reuter}:
-Ancient notation font Exact Type1 font outlines for feta,
-feta-alphabet.
-
-@end itemize
-@end macro
-
-
-
-@macro contributorsDoc
-
-@itemize
-@item @uref{http://www.s3.kth.se/~mabe/, Mats Bengtsson}:
-Example files, documentation
-
-
-@end itemize
-@end macro
-
-
-
-@macro contributorsSupport
-
-@itemize
-@item Anthony Fok:
-Debian package: @file{debian/*}.
-
-@end itemize
-@end macro
-
-
-
-@macro contributorsTranslations
-
-@itemize
-@item Bjoern Jacke:
-German glossary translations.
-
-
-@end itemize
-@end macro
-
-
-
-
-@ignore
- OLD MATERIAL
-
-Core code:
-
-@itemize @bullet
-@item @email{erlenda@@gmail.com,Erlend Aasland}
- Color support, tablature improvements, trivial \mark stuff,
-al-niente hairpins.
-
-@item @email{benkop@@freestart.hu,Pal Benko},
- Ancient notation.
-@item @email{jch@@pps.jussieu.fr, Juliusz Chroboczek},
- Type42 code.
-@item @email{david.feuer@@gmail.com, David Feuer},
- PS output code refactoring.
-@item @email{bernard@@fong-hurley.org.uk, Bernard Hurley},
- X11 color.
-@item @email{chris@@fluffhouse.org.uk, Chris Jackson},
- Piano pedals, directed arpeggios.
-@item @email{heikki.junes@@hut.fi, Heikki Junes},
- Fine tuning for quarter tones in midi output.
-@item @email{reinhold@@kainhofer.com, Reinhold Kainhofer},
- @uref{http://reinhold.kainhofer.com},
- Musicxml2ly development, various features and fixes.
-@item @email{m.krause@@tu-harburg.de, Michael Krause},
- Breathing signs.
-@item @email{jiba@@tuxfamily.org, Jean-Baptiste Lamy},
- Tablature support.
-@item @email{wl@@gnu.org, Werner Lemberg},
- @TeX{} glue code.
-@item @email{joeneeman@@gmail.com, Joe Neeman},
- Constrained line breaking.
-@item @email{hanwen@@xs4all.nl, Han-Wen Nienhuys},
- @uref{http://www.xs4all.nl/~hanwen/},
- Main author.
-
-@item @email{janneke@@gnu.org, Jan Nieuwenhuizen},
- @uref{http://www.xs4all.nl/~jantien/},
- Main author.
-@item @email{reuter_j@@web.de, Jürgen Reuter},
- @uref{http://www.juergen-reuter.de},
- Ancient notation support (mensural notation,
- Gregorian chant notation), ambitus, clusters.
-@item @email{nicolas.sceaux@@free.fr, Nicolas Sceaux},
- Scheme macros, \markup syntax.
-@item @email{c_sorensen@@byu.edu, Carl Sorensen},
- Fret diagrams.
-@item @email{, Rune Zedeler},
- Auto-accidental code, zigzag glissandi, rest bugfixes, minimum
- fret, @code{subdivideBeams}.
-@end itemize
-
-Font
-
-@itemize @bullet
-
-@item @email{reuter_j@@web.de, Jürgen Reuter},
- @uref{http://www.juergen-reuter.de},
- Ancient notation font
- Exact Type1 font outlines for feta, feta-alphabet.
-@item @email{chris@@fluffhouse.org.uk, Chris Jackson},
- Arpeggio arrow
-@item @email{, Rune Zedeler},
- 16th and shorter rests,
-@item @email{hanwen@@xs4all.nl, Han-Wen Nienhuys},
- @uref{http://www.xs4all.nl/~hanwen/},
- Main author.
-@item @email{janneke@@gnu.org, Jan Nieuwenhuizen},
- @uref{http://www.xs4all.nl/~jantien/},
- Main author.
-@item @email{tca@@gnu.org, Tom Cato Amundsen},
- Accordion symbols.
-@item @email{arno@@arnowaschk.de, Arno Waschk},
- "espressivo" mark.
-@end itemize
-
-
-Documentation and examples
-
-@itemize
-@item @email{mats.bengtsson@@s3.kth.se, Mats Bengtsson},
- @uref{http://www.s3.kth.se/~mabe/},
- Example files, documentation
-@item @email{heikki.junes@@hut.fi, Heikki Junes},
- Cleanups in docs and example files.
-@item @email{john.mandereau@@free.fr, John Mandereau},
- Internationalization.
-@item @email{scancm@@biobase.dk, Christian Mondrup},
- Glossary.
-@item @email{hanwen@@xs4all.nl, Han-Wen Nienhuys},
- @uref{http://www.xs4all.nl/~hanwen/},
- Main author.
-@item @email{janneke@@gnu.org, Jan Nieuwenhuizen},
- @uref{http://www.xs4all.nl/~jantien/},
- Main author.
-@item @email{gpermus@@gmail.com, Graham Percival},
- @uref{http://percival-music.ca},
- Documentation Editor.
-@item @email{pinard@@iro.umontreal.ca, François Pinard},
- @uref{http://www.iro.umontreal.ca/~pinard/},
- Parts of Documentation/user/glossary*, started
- internationalization stuff.
-@item @email{, Rune Zedeler},
- Schumann example.
-@end itemize
-
-Support (distributions, editor support, lilypond-book)
-
-@itemize
-@item @email{foka@@debian.org, Anthony Fok},
- Debian package: debian/*.
-@item @email{chris@@fluffhouse.org.uk, Chris Jackson},
- Emacs mode indentation.
-@item @email{heikki.junes@@hut.fi, Heikki Junes},
- Major Emacs- and Vim-mode updates.
-@item @email{svoboda@@cmu.edu, David Svoboda},
- what-beat emacs module.
-@end itemize
-
-
-Translations
-
-@itemize
-@item @email{bjoern.jacke@@gmx.de, Bjoern Jacke},
- German glossary translations.
-@item @email{nj104@@cus.cam.ac.uk, Neil Jerram},
- Glossary translations.
-@item @email{heikki.junes@@hut.fi, Heikki Junes},
- Finnish translations.
-@item @email{tdm@@dds.nl, Tineke de Munnik},
- Dutch website translation.
-@item @email{august@@infran.ru, August S. Sigov},
- Russian translation.
-@item @email{, David González},
- Spanish glossary translations.
-@item @email{ngclaude@@123mail.org, Nicolas Grandclaude},
- French documentation translation.
-@item @email{lolyfan@@wanadoo.fr, Jean-Charles Malahieude},
- French translation of messages, website and documentation.
-@item @email{john.mandereau@@free.fr, John Mandereau},
- French translation of messages, website and documentation
-@item @email{gauvainpocentek@@yahoo.fr, Gauvain Pocentek},
- French website translation.
-@item @email{ludovicsardain@@gmail.com, Ludovic Sardain},
- French documentation translation.
-@end itemize
-
-@end ignore
-
+++ /dev/null
-@c -*- coding: utf-8; mode: texinfo; -*-
-@ignore
- Translation of GIT committish: FILL-IN-HEAD-COMMITTISH
-
- When revising a translation, copy the HEAD committish of the
- version that you are working on. See TRANSLATION for details.
-@end ignore
-
-@include general/basic-authors.itexi
-
-@node community
-@unnumbered Community
-
-
-@divClass{column-center-top}
-@subheading Interacting with the community
-
-@itemize
-
-@item
-@ref{contact}: get help, discuss, and keep in touch!
-
-@item
-@ref{tiny examples}: these are @emph{highly} recommended when
-discussing LilyPond.
-
-@item
-@ref{bug reports}: something went wrong.
-
-@end itemize
-@divEnd
-
-@divClass{column-left-bottom}
-@subheading Making LilyPond better
-
-@itemize
-
-@item
-@ref{help us}: your assistance is requested.
-
-@item
-@ref{development}: for contributors and testers.
-
-@item
-@ref{authors}: the people who made LilyPond what it is today.
-
-@end itemize
-@divEnd
-
-@divClass{column-right-bottom}
-@subheading Miscellaneous
-
-@itemize
-
-@item
-@ref{publications}: what we wrote, and have had written about us.
-
-@item
-@ref{old news}: an archive.
-
-@end itemize
-@divEnd
-
-
-@divClass{hide}
-@menu
-* contact::
-* tiny examples::
-* bug reports::
-* help us::
-* development::
-* authors::
-* publications::
-* old news::
-@end menu
-@divEnd
-
-
-@node contact
-@unnumberedsec Contact
-
-
-@divClass{column-left-bottom}
-@subheading User Discussions and Help
-
-@subsubheading User mailing list: @code{lilypond-user@@gnu.org}
-
-This mailing list is the main place for users to discuss and help
-each other.
-
-@quotation
-@uref{http://mail.gnu.org/mailman/listinfo/lilypond-user,
-lilypond-user subscribe and info}
-
-@uref{http://mail.gnu.org/archive/html/lilypond-user/,
-user archive1}
-@uref{http://www.mail-archive.com/lilypond-user@@gnu.org/,
-archive2}
-@uref{http://dir.gmane.org/gmane.comp.gnu.lilypond.general,
-archive3}
-
-@uref{http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.general,
-send to lilypond-user with gmane}
-@end quotation
-
-@warning{When asking questions, please use @ref{tiny examples}!}
-
-
-@subsubheading IRC
-
-Some level of support is provided on our IRC channel,
-
-@example
-@uref{irc://irc.freenode.net/lilypond, #lilypond@@irc.freenode.net}
-@end example
-
-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.
-
-@html
-<form action="http://webchat.freenode.net"
- method="get"
- name="f_lily_irc"
- <label>irc name:
- <input name="nick" type="text" size="15" value="">
- </label>
- <input name="channels" type="hidden" value="lilypond">
- <input type="submit" value="Join #lilypond IRC Chat">
-</form>
-
-<script language="JavaScript" type="text/javascript">
- var username = "web";
- var lang = window.navigator.userLanguage ? window.navigator.userLanguage
- : window.navigator.language;
- username += '-' + lang.substr(0, 2);
- username += '-' + navigator.appName.substr(0, 2);
- username += navigator.appCodeName.replace (" ", "").substr(0, 2);
- username += navigator.platform.replace (" ", "").replace("nux", "").replace("n32", "");
- document.forms["f_lily_irc"].nick.value = username;
-</script>
-@end html
-
-@subsubheading Other languages
-
-@quotation
-@uref{http://es.groups.yahoo.com/group/lilypond-es,
-Spanish yahoo group}
-
-@uref{http://www.lilypondforum.de/,
-German forum}
-
-@uref{http://groups.google.com/group/lilypond-brasil,
-Portugese group}
-
-@uref{http://lists.gnu.org/mailman/listinfo/lilypond-user-fr,
-French mailing list}
-
-@uref{http://www.lilypondforum.nl/,
-Dutch forum}
-@end quotation
-
-@divEnd
-
-
-@divClass{column-right-top}
-@subheading Stay Informed
-
-@subsubheading LilyPond Report
-
-The easiest way to keep touch is by reading our community
-newsletter, the @uref{http://news.lilynet.net/, LilyPond Report}.
-
-@subsubheading Releases mailing list: @code{info-lilypond@@gnu.org}
-
-This mailing list is a low-volume, read-only list which receives
-notifications of new releases.
-
-@quotation
-@uref{http://lists.gnu.org/mailman/listinfo/info-lilypond,
-info-lilypond subscribe and info}
-
-@uref{http://mail.gnu.org/archive/html/info-lilypond/,
-info archive1}
-@uref{http://www.mail-archive.com/info-lilypond@@gnu.org/,
-archive2}
-@uref{http://dir.gmane.org/gmane.comp.gnu.lilypond.announce,
-archive3}
-
-@c don't include gmane posting here. -gp
-@end quotation
-
-
-@divEnd
-
-
-@divClass{column-right-bottom}
-@subheading Developer Discussion
-
-@subsubheading Developer mailing list: @code{lilypond-devel@@gnu.org}
-
-Most developer discussion takes place on this list. Patches
-should be sent here.
-
-@quotation
-@uref{http://mail.gnu.org/mailman/listinfo/lilypond-devel,
-lilypond-devel subscribe and info}
-
-@uref{http://mail.gnu.org/archive/html/lilypond-devel/,
-devel archive1}
-@uref{http://www.mail-archive.com/lilypond-devel@@gnu.org/,
-archive2}
-@uref{http://dir.gmane.org/gmane.comp.gnu.lilypond.devel,
-archive3}
-
-@uref{http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.devel,
-send to lilypond-devel with gmane}
-@end quotation
-
-
-@subsubheading Bug mailing list: @code{bug-lilypond@@gnu.org}
-
-Bug-specific discussion takes place here.
-
-@quotation
-@uref{http://mail.gnu.org/mailman/listinfo/bug-lilypond,
-bug-lilypond subscribe and info}
-
-@uref{http://mail.gnu.org/archive/html/bug-lilypond/,
-bug archive1}
-@uref{http://www.mail-archive.com/bug-lilypond@@gnu.org/,
-archive2}
-@uref{http://dir.gmane.org/gmane.comp.gnu.lilypond.bugs,
-archive3}
-
-@c don't include gmane posting here. -gp
-@end quotation
-
-@warning{Before sending a message to the bug list, please read our
-guidelines for @ref{bug reports}.}
-
-@divEnd
-
-
-
-@node tiny examples
-@unnumberedsec Tiny examples
-
-@divClass{column-center-top}
-@subheading What are @qq{Tiny examples}?
-
-A tiny example is an example from which nothing can be removed.
-@divEnd
-
-@divClass{column-left-bottom}
-@subheading Why create them?
-
-@divClass{keep-bullets}
-@itemize
-
-@item
-The simpler the example is, the quicker potential helpers can
-understand it and help you.
-
-@item
-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.
-
-@item
-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
-@qq{bug} in a tiny example, then the problem was probably an
-insufficient understanding of LilyPond, not an actual bug!
-
-@end itemize
-@divEnd
-
-@divEnd
-
-
-@divClass{column-right-bottom}
-@subheading How do I create them?
-
-@divClass{keep-bullets}
-@itemize
-
-@item
-Include the \version number.
-
-@item
-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.
-
-@item
-When trying to create an example, try commenting out @w{(@code{%}
-or @code{%@{ @dots{} %@}})} sections of your file. If you can
-comment something while still demonstrating the main idea, then
-remove the commented-material!
-
-@item
-Avoid using complicated notes, keys, or time signatures, unless
-the bug is about the behavior of those items.
-
-@item
-Do not use @code{\override} or @code{\set} commands unless the bug
-is about those particular commands.
-
-@end itemize
-@divEnd
-
-@divEnd
-
-
-
-
-@node bug reports
-@unnumberedsec Bug reports
-
-@divClass{column-center-top}
-@subheading 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,
-
-@example
-@uref{http://code.google.com/p/lilypond/issues/list}
-@end example
-
-@warning{Please @strong{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.}
-
-@divEnd
-
-
-@divClass{column-left-bottom}
-@subheading Step 2: Creating a bug report
-
-If you have discovered a bug which is not listed, please help us
-by creating a bug report.
-
-@warning{We only accept bug reports in the form of
-@ref{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:
-
-@example
-%% 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
-@}
-@end example
-
-@divEnd
-
-@divClass{column-right-bottom}
-@subheading 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 @qq{no top-posting} check on the
-bug list, which is often incorrectly triggered by lilypond files.
-To avoid this, please add
-
-@example
-> I'm not top posting.
-@end example
-
-@noindent
-(you must include the @code{>} ) to the top of your bug report.
-
-@uref{http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.bugs,
-Post with the gmane lilypond.bugs interface}, or send an email to
-@uref{mailto:bug-lilypond@@gnu.prg, bug-lilypond@@gnu.org}.
-
-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.
-@divEnd
-
-
-@node help us
-@unnumberedsec Help us
-
-TODO: talk about the Frogs, document suggestions, encourage getting
-involved, etc. Maybe mention GLISS and GOP, if those are happening
-in the near future.
-
-frog mailist: @uref{http://frogs.lily.net}
-
-
-@node development
-@unnumberedsec Development
-
-
-@divClass{heading-center}
-@heading Development materials for LilyPond @versionDevel{}
-
-@warning{These are @emph{unstable development} versions. If you
-have the slightest doubt about how to use or install LilyPond, we
-urge you to use the stable @ref{download}, and read the stable
-@ref{manuals}.}
-
-@divEnd
-
-@divClass{column-center-top}
-@subheading Release numbers
-
-There are two sets of releases for LilyPond: stable releases, and
-unstable development releases. Stable versions have an
-even-numbered @q{minor} version number (e.g., 2.8, 2.10, 2.12).
-Development versions have an odd-numbered @q{minor} version number
-(e.g., 2.7, 2.9, 2.11).
-
-@divEnd
-
-
-@divClass{column-left-bottom}
-@subheading Download
-
-Instructions for git and compiling are in the Contributor's Guide.
-
-@quotation
-@uref{http://git.sv.gnu.org/gitweb/?p=lilypond.git, lilypond git repository}
-@end quotation
-
-Documentation writers and testers will generally want to download
-the latest binary:
-
-@quotation
-
-@downloadDevelLinuxNormal
-
-@downloadDevelLinuxBig
-
-@downloadDevelLinuxPPC
-
-@downloadDevelFreeBSDNormal
-
-@downloadDevelFreeBSDBig
-
-@downloadDevelDarwinNormal
-
-@downloadDevelDarwinPPC
-
-@downloadDevelWindows
-
-@downloadDevelSource
-
-@end quotation
-
-
-@subheading Manuals
-
-@help {these need the automatic symlinks or something. Maybe even
-a hard-coded url to lilypond.org/docs/2.13 or something??}
-
-Learning:
-@uref{lm-html, html}
-@uref{lm-big-html, big html}
-@uref{lm-pdf, pdf}
-
-Glossary:
-@uref{mg-html, html}
-@uref{mg-big-html, big html}
-@uref{mg-pdf, pdf}
-
-Essay:
-@uref{essay-html, html}
-@uref{essay-big-html, big html}
-@uref{essay-pdf, pdf}
-
-Notation:
-@uref{notation-html, html}
-@uref{notation-big-html, big html}
-@uref{notation-pdf, pdf}
-
-Usage:
-@uref{usage-html, html}
-@uref{usage-big-html, big html}
-@uref{usage-pdf, pdf}
-
-Snippets:
-@uref{snippets-html, html}
-@uref{snippets-big-html, big html}
-@uref{snippets-pdf, pdf}
-
-Changes:
-@uref{changes-html, html}
-@uref{changes-big-html, big html}
-@uref{changes-pdf, pdf}
-
-Internals:
-@uref{internals-html, html}
-@uref{internals-big-html, big html}
-@uref{internals-pdf, pdf}
-
-@divEnd
-
-
-@divClass{column-right-top}
-@subheading Contributors' Guide
-
-LilyPond development is a fairly complicated matter. LilyPond is
-a large, (mostly) stable project. At any point in time, we have
-between 5 and 25 active contributors. In order to help new
-contributors, and to keep the whole system (mostly) stable, we
-have written a manual for contributors.
-
-@divClass{keep-bullets}
-@itemize
-
-@item @uref{../contributor/index.html, Contributor's guide (split HTML)}:
-the manual is split between many HTML pages.
-@emph{(small download for each page)}
-
-@item @uref{../contributor-big-page.html, Contributor's guide (big HTML)}:
-read this manual as one huge HTML page.
-@emph{(large single download, around 10? Mb)}
-
-@item @uref{../contributor.pdf, contributor.pdf}:
-download as a PDF file.
-@emph{(large single download, 2.8 Mb)}
-
-@c @item @uref{TODO, contributor.info}:
-@c GNU info format for documentation. TODO, link broken.
-
-@end itemize
-@divEnd
-@divEnd
-
-@divClass{column-right-bottom}
-@subheading Regression tests
-
-@divClass{keep-bullets}
-@itemize
-
-@item @uref{../../input/regression/collated-files.html, Regression tests}:
-This releases' tests. (also in
-@uref{../input/regression/collated-files.pdf, pdf})
-
-@item @uref{../../input/regression/musicxml/collated-files.html,
-MusicXML Regression tests}:
-This releases' MusicXML tests. (also in
-@uref{../input/regression/musicxml/collated-files.pdf, pdf})
-
-@item @uref{http://lilypond.org/test, Archive of regression tests}:
-Comparisons beteween versions.
-
-@end itemize
-@divEnd
-@divEnd
-
-@node authors
-@unnumberedsec Authors
-
-@help{Under construction; this is not an accurate list!}
-
-combo of:
-
-http://lilypond.org/web/about/thanks
-
-Documentation/topdocs/AUTHORS.texi
-
-and maybe:
-http://lilypond.org/web/switch/
-
-
-@divClass{column-left-top}
-@subheading Current Development Team
-
-@divClass{keep-bullets}
-@developersCurrent
-@divEnd
-@divEnd
-
-@divClass{column-right-top}
-@subheading Previous Development Team Positions
-
-@divClass{keep-bullets}
-@developersPrevious
-@divEnd
-@divEnd
-
-
-@divClass{column-center-bottom}
-@subheading Programming contributors
-
-@divClass{keep-bullets}
-@contributorsCore
-
-@subheading Font contributors
-
-@contributorsFont
-
-@subheading Documentation contributors
-
-@contributorsDoc
-
-@subheading Support contributors
-
-@contributorsSupport
-
-@subheading Translation contributors
-
-@contributorsTranslations
-
-@divEnd
-@divEnd
-
-
-
-@node publications
-@unnumberedsec Publications
-
-@divClass{column-center-top}
-@subheading What we wrote
-
-@divClass{keep-bullets}
-@itemize
-
-@item
-Han-Wen Nienhuys, @emph{LilyPond, Automated music formatting and
-the Art of Shipping}. Forum Internacional Software Livre 2006
-(FISL7.0) (@uref{http://lilypond.org/web/images/FISL7-slides.pdf,
-PDF 1095k})
-
-@item
-Erik Sandberg, @emph{Separating input language and formatter in
-GNU Lilypond}. Master's Thesis, Uppsala University, Department of
-Information Technology March 2006.
-(@uref{http://lilypond.org/web/images/thesis-erik-sandberg.pdf,
-PDF 750k})
-
-@item
-Han-Wen Nienhuys and Jan Nieuwenhuizen, @emph{LilyPond, a system
-for automated music engraving}. Proceedings of the XIV Colloquium
-on Musical Informatics (XIV CIM 2003), Firenze, Italy, May 2003.
-(@uref{ http://lilypond.org/web/images/xivcim.pdf, PDF 95k})
-
-@end itemize
-
-@divEnd
-@divEnd
-
-
-@divClass{column-center-bottom}
-
-@subheading What others wrote
-
-@divClass{keep-bullets}
-@itemize
-
-@item
-September 2009
-
-The German LinuxUser magazine wrote an
-@uref{http://www.linux-community.de/Internal/Artikel/Print-Artikel/LinuxUser/2009/10/Digitaler-Notenschluessel,
-article about lilypond}.
-
-
-@item
-February 2008
-
-In @uref{http://www.musicbyandrew.ca/finale-lilypond-1.html,
-articles on his personal site}, 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.
-
-@item
-December 2005
-
-Linux journal cover Linux Journal publishes an article titled
-@uref{http://www.linuxjournal.com/article/8364, Make Stunning
-Schenker Graphs with GNU LilyPond}. 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.”
-
-@item
-August 20, 2005
-
-The Belgian newspaper De Standaard investigates what drives Free
-Software authors in an article titled
-@uref{http://www.standaard.be/Artikel/Detail.aspx?artikelId=G42H5GD6,
-Delen van KENNIS zonder WINSTBEJAG} (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.
-
-@item
-June 2005
-
-A French article on the LilyPond 2.6 release appeared on
-@uref{http://linuxfr.org/2005/06/27/19210.html, linuxfr.org}.
-
-@item
-October 2004
-
-The editors of Computer!Totaal, a Dutch computer magazine,
-@uref{http://lilypond.org/web/images/computer-totaal.jpeg,
-describe LilyPond} in the October 2004 issue as: @qq{Wonderful
-free (open source) software [..] The sheet music produced by
-LilyPond is exceptionally pretty [..] a very powerful system that
-can do almost anything.}
-
-@item
-July, August 2004
-
-Dave Phillips wrote an introductory article for Linux Journal At
-the sounding edge: LilyPond, parts
-@uref{http://www.linuxjournal.com/article/7657, one} and
-@uref{http://www.linuxjournal.com/article/7719, two}.
-
-@item
-March 2004
-
-Chris Cannam interviewed Han-Wen Nienhuys and Jan Nieuwenhuizen on
-linuxmusician.com (site now defunct). This interview was also
-reviewed in a
-@uref{http://slashdot.org/article.pl?sid=04/03/13/2054227&tid=,
-slashdot story}.
-
-@item
-February 2004
-
-Jazz singer Gail Selkirk writes about
-@uref{http://www.songbirdofswing.com/editorial_page/lilypond/,
-Diving into LilyPond}. @qq{... you can make lead sheets or full
-orchestral parts, and the results can be stunning.}
-@uref{http://www.computermusic.co.uk/, Computer Music Special},
-issue CMS06.
-
-@end itemize
-
-@divEnd
-@divEnd
-
-
-@node old news
-@unnumberedsec Old news
-
-@include general/news.itexi
+++ /dev/null
-@c -*- coding: utf-8; mode: texinfo; -*-
-@ignore
- Translation of GIT committish: FILL-IN-HEAD-COMMITTISH
-
- When revising a translation, copy the HEAD committish of the
- version that you are working on. See TRANSLATION for details.
-@end ignore
-
-@node download
-@unnumbered Download
-
-@divClass{heading-center}
-@heading Downloads for LilyPond @versionStable
-
-@divEnd
-
-@warning{LilyPond is a @strong{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 @ref{text input}.}
-
-@divClass{column-left-top}
-@subheading For users
-
-@itemize
-
-@item
-@c TODO: duplicate to avoid underlined refs in HTML? icky.
-@ref{UNIX, @sourceimage{logo-linux,,,}
-@sourceimage{logo-freebsd,,,}}
-@ref{UNIX, Unix (Linux and FreeBSD)}
-
-@item
-@ref{MacOS X, @sourceimage{logo-macosx,,,}}
-@ref{MacOS X, MacOS X}
-
-@item
-@ref{Windows, @sourceimage{logo-windows,,,}}
-@ref{Windows, Microsoft Windows}
-
-@end itemize
-
-@divEnd
-
-@divClass{column-right-top}
-@subheading For developers
-
-@itemize
-
-@item
-@ref{source}:
-for packagers
-
-@item
-@ref{old downloads}:
-old versions
-
-@item @ref{development}:
-latest unstable version
-
-@end itemize
-@divEnd
-
-
-@divClass{column-center-bottom}
-
-@subheading Software License
-
-LilyPond is published under the
-@ref{GPL, GNU General Public License}.
-@divEnd
-
-
-@divClass{color1}
-
-@subheading Sponsors
-
-Many thanks to @uref{http://www.vt.edu/, Virgina Tech} and
-@uref{http://www.linuxaudio.org/, linuxaudio.org} for sponsoring
-our bandwidth.
-
-@sourceimage{VTlogo_ITF,,,}
-@sourceimage{lao_banner_06_on_white_demo,,,}
-
-@subheading Legalese
-
-@divClass{legal}
-All logos and product images are copyright and trademark
-acknowledged.
-
-@logoLegalLinux
-
-@logoLegalFreeBSD
-
-@logoLegalMacOSX
-
-@logoLegalWindows
-
-@divEnd
-@divEnd
-
-
-@divClass{hide}
-@menu
-* UNIX::
-* MacOS X::
-* Windows::
-* source::
-* old downloads::
-* GPL::
-@end menu
-@divEnd
-
-
-@node UNIX
-@unnumberedsec UNIX
-
-@divClass{column-center-top}
-@subheading 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.
-
-@divEnd
-
-
-@divClass{column-left-top}
-@subheading Generic Packages
-
-@subsubheading Download
-
-@itemize
-
-@item
-@sourceimage{logo-linux,,,}
-@downloadStableLinuxNormal
-(if in doubt, use this)
-
-@item
-@sourceimage{logo-linux,,,}
-@downloadStableLinuxBig
-
-@item
-@sourceimage{logo-linux,,,}
-@downloadStableLinuxPPC
-
-@item
-@sourceimage{logo-freebsd,,,}
-@downloadStableFreeBSDNormal
-
-@item
-@sourceimage{logo-freebsd,,,}
-@downloadStableFreeBSDBig
-
-@end itemize
-
-
-@subsubheading Install
-
-In the shell, type:
-
-@example
-cd PATH-TO-DOWNLOAD-DIRECTORY
-sh lilypond-@versionStable{}-OS-TYPE.sh
-@end example
-
-@subsubheading Uninstall
-
-In the shell, type:
-
-@example
-uninstall-lilypond
-@end example
-
-@divEnd
-
-
-@divClass{column-right-top}
-@subheading Distribution-specific Packages
-
-Please use your distribution's package manager to install or
-upgrade to these versions.
-
-@itemize
-
-@item
-@sourceimage{logo-fedora,,,}
-@uref{https://admin.fedoraproject.org/pkgdb/packages/name/lilypond,
-Fedora: LilyPond 2.12.0}
-
-@item
-@sourceimage{logo-ubuntu,,,}
-@uref{https://launchpad.net/ubuntu/+source/lilypond,
-Ubuntu: LilyPond 2.12.1}
-
-@item
-@sourceimage{logo-slackware,,,}
-@uref{http://www.johannes-schoepfer.de/lilypond/,
-Slackware: LilyPond 2.12.1}
-
-@item
-@sourceimage{logo-debian,,,}
-@uref{http://packages.debian.org/search?keywords=lilypond,
-Debian: LilyPond 2.10.33}
-
-@item
-@sourceimage{logo-suse,,,}
-@uref{http://opensuse.org/?fixme=urg-no-lilypond-package-page,
-openSUSE: LilyPond 2.10.33}
-
-@end itemize
-
-@divEnd
-
-
-@divClass{column-center-bottom}
-@subheading Legalese
-
-@divClass{legal}
-All logos and product images are copyright and trademark
-acknowledged.
-
-@logoLegalLinux
-
-@logoLegalFreeBSD
-
-@divEnd
-@divEnd
-
-
-@node MacOS X
-@unnumberedsec MacOS X
-
-@divClass{column-left-top}
-@subheading Packages
-
-@subsubheading Download
-
-@itemize
-
-@item
-@sourceimage{logo-macosx,,,}
-@downloadStableDarwinNormal
-For Intel chips (if in doubt, use this).
-
-@item
-@sourceimage{logo-macosx,,,}
-@downloadStableDarwinPPC
-For G3 and G4 CPUs (old Apple computers).
-
-@end itemize
-
-@subsubheading Install
-
-Double-click the downloaded file, then drag it to wherever you
-want.
-
-@subsubheading Uninstall
-
-Delete the LilyPond.app folder.
-
-@divEnd
-
-
-@divClass{column-right-top}
-@subheading Running on the command-line
-
-@warning{If you are happy with the GUI, then please ignore these
-instructions.}
-
-@ignore
-FIXME: I had one report that we don't need this stuff; will delete
-after confirmation. -gp
-
-@subsubheading Using Python scripts on MacOS 10.3 or 10.4
-
-LilyPond binaries for MacOS X do not provide Python, but Python 2.4 or
-newer is required by @command{convert-ly}. Therefore, if you use MacOS
-10.3 or 10.4, you must install a newer Python version from
-@uref{http://python.org/download/}, then edit the first line of
-@command{convert-ly} and @command{lilypond-book} as follows: if the
-Python binary you just installed is in your @var{PATH}, the first line
-should be
-
-@example
-#!/usr/bin/env python
-@end example
-
-@noindent
-otherwise it should be
-
-@example
-#!@var{/path/to/newly_installed/python}
-@end example
-@end ignore
-
-@subsubheading MacOS X on the command line
-
-The most convenient way to run lilypond scripts is by setting up
-@qq{helper} scripts of your own.
-
-@enumerate
-
-@item
-Create a directory to store these scripts,
-
-@example
-mkdir -p ~/bin
-cd ~/bin
-@end example
-
-
-@item
-Create a file called @command{lilypond} which contains
-
-@help obvious css issue to be dealt with. :(
-@c we need a small font here to fit. -gp
-@smallexample
-exec @var{DIR}/LilyPond.app/Contents/Resources/bin/lilypond "$@@"
-@end smallexample
-
-@warning{@var{DIR} will generally be @code{/Applications/}}
-
-
-@item
-Create similar files @command{lilypond-book},
-@command{convert-ly}, and any other scripts you wish to use, by
-replacing the @command{bin/lilypond} with @command{bin/convert-ly}
-(or other program name).
-
-
-@item
-Make the file executable,
-
-@example
-chmod u+x lilypond
-@end example
-
-
-@item
-Now, add this directory to your path. Modify (or create) a file
-called @code{.profile} in your home directory such that it
-contains
-
-@example
-export PATH=$PATH:~/bin
-@end example
-
-This file should end with a blank line.
-
-@end enumerate
-
-
-@subsubheading Invoking individual scripts
-
-The scripts --- such as @command{lilypond-book}, @command{convert-ly},
-@command{abc2ly}, and even @command{lilypond} itself --- are included
-inside the @code{.app} file for MacOS@tie{}X.
-
-Scripts can also be run from the command line by invoking them
-directly:
-
-@example
-@var{path/to}/LilyPond.app/Contents/Resources/bin/lilypond
-@end example
-
-The same is true for all other scripts in that directory, such as
-@command{lilypond-book} and @command{convert-ly}.
-
-@divEnd
-
-
-@divClass{column-center-bottom}
-@subheading Legalese
-
-@divClass{legal}
-All logos and product images are copyright and trademark
-acknowledged.
-
-@logoLegalMacOSX
-
-@divEnd
-@divEnd
-
-
-
-@node Windows
-@unnumberedsec Windows
-
-@divClass{column-left-top}
-@subheading Packages
-
-@subsubheading Download
-
-@itemize
-
-@item
-@sourceimage{logo-windows,,,}
-@downloadStableWindows
-For Windows ME, NT, 2000, XP, and Vista.
-
-@end itemize
-
-@subsubheading Install
-
-@enumerate
-
-@item
-Locate the downloaded file and double-click on it to start the
-installer. You will be presented a window titled @qq{Open File -
-Security Warning}, click on Run to continue.
-
-@item
-You will be presented the License Agreement; read this carefully,
-and click on the Next button if you accept it.
-
-@item
-Preferably leave the destination folder to the default, else
-browse to choose a different location, and click on the Next
-button.
-
-@item
-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.
-
-@item
-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.
-
-@item
-Lilypond is now installed.
-
-@end enumerate
-
-@subsubheading Uninstall
-
-There are two uninstallation routes -
-
-@enumerate
-
-@item
-Choose Uninstall from the Lilypond menu from the start menu
-
-@item
-Open your Install/Uninstall Applications on the Control Panel,
-scroll down to Lilypond and click on the Uninstall buttom.
-
-@end enumerate
-
-@divEnd
-
-
-@divClass{column-right-top}
-@subheading Running on the command-line
-
-@warning{If you are happy with the GUI, then please ignore these
-instructions.}
-
-@help{don't know}
-
-@divEnd
-
-
-@divClass{column-center-bottom}
-@subheading Legalese
-
-@divClass{legal}
-All logos and product images are copyright and trademark
-acknowledged.
-
-@logoLegalWindows
-
-@divEnd
-@divEnd
-
-
-
-@node source
-@unnumberedsec Source
-
-@warning{We @strong{do not} recommend that you attempt to build
-LilyPond yourself; almost all user needs are better met with the
-pre-built version.}
-
-@divClass{column-left-bottom}
-@subheading Source tarball
-
-@downloadStableSource{}
-
-For an extensive listing of all versions (old and new), see our
-@uref{http://download.linuxaudio.org/lilypond/binaries/, download
-site}.
-
-@divEnd
-
-@divClass{column-right-bottom}
-@subheading Compiling instructions
-
-Instructions are listed in @rcontrib{Compiling LilyPond}.
-
-@divEnd
-
-
-@node old downloads
-@unnumberedsec Old downloads
-
-@divClass{column-center-top}
-@subheading All versions
-
-For an extensive listing of all versions (old and new), see our
-@uref{http://download.linuxaudio.org/lilypond/binaries/, download
-site}.
-
-@divEnd
-
-
-@node GPL
-@unnumberedsec GPL
-
-@divClass{column-center-top}
-@subheading 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 @ref{freedom}.
-
-@divEnd
-
-@divClass{column-center-bottom}
-@subheading GNU General Public License version 2
-
-@include gpl-2.0.itexi
-
-@divEnd
-
-
-
+++ /dev/null
-depth=../../..
-LOCALSTEPMAKE_TEMPLATES=lilypond ly
-include $(depth)/make/stepmake.make
-
-LILYPOND_PREVIEW = $(LILYPOND_BINARY) -dpreview -dresolution=150
-
-OUT_PNG_FILES = $(LY_FILES:%.ly=$(outdir)/%.png)
-OUT_PNG_PAGES = $(PNG_PAGES:%=$(outdir)/%.png)
-
-OUT_SMALL_PNG_FILES = $(OUT_PNG_FILES:%.png=%-small.png)
-
-ifeq ($(out),www)
-all: $(OUT_PNG_FILES) $(OUT_SMALL_PNG_FILES)
-endif
-
-$(outdir)/%.png: %.ly
- $(LILYPOND_PREVIEW) -o $(outdir) $<
- mv $(outdir)/$*.preview.png $@
-
-$(outdir)/%-small.png: $(outdir)/%.png
- pngtopnm $< | pnmscale -w=600 | pnmtopng > $@
-
+++ /dev/null
-\version "2.12.0"
-\include "example-header.ily"
-
-#(set-global-staff-size 15)
-
-\include "gregorian.ly"
-
-\score {
- <<
- \new VaticanaVoice = "cantus" {
- \clef "vaticana-do3"
- % Verse 1 — Salve, Regína
- a\melisma \[ a \flexa g \pes a\melismaEnd \] d
- \divisioMinima
- \[ a\melisma \flexa g\melismaEnd \]
- \[ f\melisma \flexa e f \pes g \flexa f\melismaEnd \]
- \[ e\melisma \flexa d\melismaEnd \]
- \divisioMaior
- c d \[d\melisma \flexa c\melismaEnd \] d
- \[ e\melisma \pes f\melismaEnd\] g
- \[d\melisma \pes e \flexa c\melismaEnd \] d
- \finalis
- % Verse 2 — Vita, dulcédo
- % a\melisma \[ a \flexa g \pes a\melismaEnd \] d
- % \divisioMinima
- % \[ a\melisma \flexa g\melismaEnd \]
- % \[ f\melisma \flexa e f \pes g \flexa f\melismaEnd \]
- % \[ e\melisma \flexa d\melismaEnd \]
- % \divisioMaior
- % c d \[e\melisma \pes f\melismaEnd \] g
- % \[d\melisma \pes e \flexa c\melismaEnd \] d
- % \finalis
- % Verse 3 — Ad te clamámus
- \[ d\melisma \pes f\melismaEnd\] a g
- \[ g\melisma \flexa f \pes a\melismaEnd\] e
- \divisioMaior
- g f \[ e\melisma \flexa d \pes g\melismaEnd \]
- \divisioMinima
- c d \[ e\melisma \flexa d \pes g\melismaEnd \]
- \[ f\melisma \flexa e\melismaEnd \] d
- \finalis
- % Verse 4 — Ad te suspirámus
- \[ d\melisma \pes f\melismaEnd \] a c' g
- \[ g\melisma \flexa f \pes g\melismaEnd \] a
- \divisioMaior
- d \[ f\melisma \pes \deminutum g\melismaEnd \] g d
- \[ \virga f\melisma \inclinatum e \inclinatum d\melismaEnd \]
- c \divisioMaior
- d \[ d\melisma \flexa c \pes f\melismaEnd \]
- \[ g\melisma \pes a\melismaEnd \]
- g \[ f\melisma \flexa e\melismaEnd \] g
- \[ f\melisma \flexa \deminutum e\melismaEnd \]
- \[ d\melisma \flexa c \pes d\melismaEnd \]
- \finalis
- % Verse 5 — Eia ergo, Advocáta nostra
- f\melisma \[ f \pes g\melismaEnd \] f
- \[ g\melisma \pes \deminutum a\melismaEnd \] a
- \divisioMinima
- c' g \[ \virga a\melisma \inclinatum g \inclinatum f\melismaEnd \] d g a
- \divisioMaior
- d' d' \[ c'\melisma \flexa b c' \pes d'\melismaEnd \] a
- \divisioMinima
- d' c' a \[ g\melisma \flexa f \pes a\melismaEnd \] g
- \[ d\melisma \pes e\melismaEnd \] f
- \[ \virga e\melisma \inclinatum d \inclinatum c\melismaEnd \]
- \divisioMaior
- \[ c\melisma \pes d\melismaEnd \]
- f \[ g\melisma \flexa \deminutum f\melismaEnd \]
- \[ d\melisma \flexa c \pes d\melismaEnd \] d
- \finalis
- % Verse 6 — Et Jesum
- d a, \[ c\melisma \pes d\melismaEnd \]
- \divisioMinima
- d \[ d\melisma \pes e\melismaEnd \] \[ e\melisma \flexa d d\melismaEnd \]
- c g f \[ e\melisma \flexa \deminutum d\melismaEnd \] g
- \[ f\melisma \flexa e\melismaEnd \]
- \[ d\melisma \flexa c \pes d\melismaEnd \]
- \[ d\melisma \pes a \] \virga bes\melismaEnd a
- \divisioMinima
- \[ \virga a\melisma \inclinatum g \inclinatum f\melismaEnd \] g d f
- \[ f\melisma \flexa e\melismaEnd \] \[ d\melisma \flexa c\melismaEnd \]
- \divisioMinima
- \[ e\melisma \pes f \flexa e\melismaEnd \] d d
- \finalis
- % Verse 7 ad finem — O clemens: O pia: O dulcis Virgo María
- a\melisma \[a \flexa g a \quilisma b \pes c'\melismaEnd \]
- \[ \virga b\melisma \inclinatum a \inclinatum g\melismaEnd \] a
- \finalis
- \[ g\melisma \pes a \quilisma b \pes c' \] \[ c' \flexa b\melismaEnd \]
- \[ a\melisma \flexa g\melismaEnd \] \[ g\melisma \pes a\melismaEnd \]
- \finalis
- \[ a\melisma \flexa d \virga f \inclinatum e \inclinatum d \inclinatum c d \]
- \divisioMinima
- \[ d \pes e f \pes g\melismaEnd \]
- \[ g\melisma \flexa \deminutum f\melismaEnd \]
- \[ g\melisma \pes a\melismaEnd \]
- d c d \[ d\melisma \pes g \flexa f f\melismaEnd \]
- \[ e\melisma \flexa d\melismaEnd \]
- \finalis
- }
- \new Lyrics \lyricsto "cantus" {
- Sal- ve, Re- gí- na, ma- ter mi- se- ri- cór- di- ae:
- % Vi- ta, dul- cé- do, et spes no- stra, sal- ve.
- Ad te cla- má- mus, éx- su- les, fi- li- i He- vae.
- Ad te su- spi- rá- mus, ge- mén- tes et flen- tes in hac la- cri- má- rum
- val- le.
- E- ia er- go, Ad- vo- cá- ta no- stra, il- los tu- os mi- se- ri- cór- des
- ó- cu- los ad nos con- vér- te.
- Et Je- sum, be- ne- díc- tum fruc- tum ven- tris tu- i, no- bis post hoc
- ex- sí- li- um os- tén- de.
- O cle- mens:
- O pi- a:
- O dul- cis Vir- go Ma- rí- a.
- }
- >>
-}
-
-\layout {
- \context {
- \Staff
- \consists Custos_engraver
- }
-}
-
+++ /dev/null
-\version "2.12.0"
-\include "example-header.ily"
-
-\paper {
-% line-width=158\mm % produces 624 pixels
- line-width = 143\mm % reserve 15mm for incipit
-}
-
-% Aucun ont trouvé, from Montpellier Codex
-%
-% Put brackets in where the original has ligatures, using
-% "Analysis Brackets," and adjust the "bracket-flare" property
-% to make the ends vertical instead of slanted.
-
-#(set-global-staff-size 15)
-
-%%%%%%%%%%% INCIPIT DEFS %%%%%%%%%%
-
-incipitGlobal = {
- \override NoteHead #'style = #'mensural
- \override Accidental #'style = #'mensural
- \override KeySignature #'style = #'mensural
- \override Rest #'style = #'mensural
-% \override Staff.TimeSignature #'style = #'mensural
- \cadenzaOn
- \override Score.Clef #'extra-offset = #'(-0.0 . 0.5)
- \override Score.Clef #'font-size = #3
- \clef "vaticana-do1"
-}
-
-incipitTriplum = \markup{
- \score{
- {
- \set Staff.instrumentName="Triplum "
- \incipitGlobal
- s1.
- }
- \layout {
- %indent = 1\cm
- \context {\Voice
- \remove Ligature_bracket_engraver
- \consists Mensural_ligature_engraver
- }
- \context {\Staff
- \remove "Time_signature_engraver"
- }
- line-width=5\mm
- }
- }
-}
-
-incipitMotetus = \markup{
- \score{
- {
- \set Staff.instrumentName="Motetus"
- \incipitGlobal
- s1.
- }
- \layout {
- % indent = 1\cm
- \context {\Voice
- \remove Ligature_bracket_engraver
- \consists Mensural_ligature_engraver
- }
- \context {\Staff
- \remove "Time_signature_engraver"
- }
- line-width=5\mm
- }
- }
-}
-
-incipitTenor = \markup{
- \score{
- {
- \set Staff.instrumentName = "Tenor "
- \incipitGlobal
- s1.*2
- }
- \layout {
- %indent = 1\cm
- \context {\Voice
- \remove Ligature_bracket_engraver
- \consists Mensural_ligature_engraver
- }
- \context {\Staff
- \remove "Time_signature_engraver"
- }
- line-width=5\mm
-}
-}
-}
-
-incipitBassus = \markup{
- \score{ {
- \set Staff.instrumentName = "Bassus "
- \override NoteHead #'style = #'neomensural
- \override Accidental #'style = #'neomensural
- \override Rest #'style = #'neomensural
- \override Staff.TimeSignature #'style = #'neomensural
- \cadenzaOn
- \clef "petrucci-f3"
- \key f \major
- \time 3/2
- \relative c' {
- s1. % R1.*2
- }
- }
- \layout {
- \context { \Voice
- \remove Ligature_bracket_engraver
- \consists Mensural_ligature_engraver
- }
- line-width=5\mm
- }
- }
-}
-
-%%%%%%%%%%% END INCIPIT DEFS %%%%%%%%%%%
-
-#(ly:set-option 'point-and-click #f)
-
-global = {
- \override Staff.TimeSignature #'stencil = #(lambda (grob)
- (bracketify-stencil (ly:time-signature::print grob) Y 0.1 0.2 0.1))
- \time 3/4
- \override Staff.BarLine #'transparent = ##t
- \override HorizontalBracket #'direction = #UP
- \override HorizontalBracket #'bracket-flare = #'(0 . 0)
-}
-
-%%%%%%%%% MACRO FOR MAKING SLASHES THROUGH STEMS %%%%%%%%%%
-MakeSlash = #(define-music-function (parser location angle len-left len-right
-thick y-factor offset)
- (number? number? number? number? number?
-pair?)
-#{
-\once \override Voice.Stem #'text = \markup {
- \postscript #(let ((x-off (car $offset))
- (y-off (cdr $offset)))
- (string-append
- (ly:number->string (car $offset)) " " (ly:number->string (cdr $offset)) "
-translate "
- (ly:number->string $angle) " rotate "
- (ly:number->string (- x-off)) " "
- (ly:number->string (- y-off)) " translate 0 setlinewidth "
- (ly:number->string (- x-off $len-left)) " " (ly:number->string (+ y-off
-$thick)) " moveto "
- (ly:number->string (- x-off $len-left)) " " (ly:number->string y-off)
- " " (ly:number->string $thick) "
-90 270 arc "
- (ly:number->string (+ x-off $len-right)) " " (ly:number->string y-off)
- " " (ly:number->string $thick) "
-270 90 arc "
- " gsave fill grestore stroke")) }
-
-\once \override Voice.Stem #'stencil = #(lambda (grob)
- (let* ((sten1 (ly:stem::print grob))
- (sten2 (ly:text-interface::print grob))
- (extent1 (ly:stencil-extent sten1 Y))
- (extent2 (ly:stencil-extent sten2 Y)))
- (ly:stencil-add
- sten1
- (ly:stencil-translate sten2
- (cons 0 (+ (* $y-factor (cdr extent1))
- (* (- 1 $y-factor) (car extent1))))))))
-#})
-
-
-slash = { \MakeSlash #20 #1.0 #1.1 #0.05 #0.75 #'(0 . -.5) }
-
-%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-
-triplumWords = \lyricmode {
- Au -- cun ont trou -- ve chant par u -- sa -- ge,
- mes a moi en doune o -- choi -- son __
- a -- mours, qui res -- bou -- dist mon cou -- ra -- ge
- si que m'ès -- tuet fai -- re _ chan -- _ _ çon
-}
-
-triplumNotes = \relative c' {
- \clef "treble_8"
- %\set Staff.midiInstrument = "flute"
-% \global
- \override StemTremolo #'beam-thickness = #.125
- \override StemTremolo #'slope = #1.0
- f8 f4 e8 d c f f f | % 1
- % the \scaleDurations command below makes 5 notes last the
- % duration of a dotted quarter
- e8 c4 \scaleDurations #'(3 . 2) { \times 4/5{e16[ d e d e]} } e8 f4 | % 2
- g2. ~ g4. | % 3
- f8 d4 f4. \scaleDurations #'(3 . 2) { \times 4/6{ g16[ f e f e f]}} % 4
- g8 g4 g4. e4. | % 5
- fis8 d4 e8\startGroup g4\stopGroup f8[ e d] | % 6
- c2. r4. | % 7
-}
-
-motetusWords = \lyricmode {
- lonc tans _ _ me fiu -- te -- nu de chan -- _ _ ter __
- mes or ai _ _
-}
-
-motetusNotes = \relative c' {
- \clef "treble_8"
- c2. c8\startGroup b8 \slash c\stopGroup | % 1
- a2. c4. | d2. e4. | % 2-3
- f2. f8 e d | % 4
- c2. ~ c4. | r2. r4. | % 5-6
- g'4. g g8 f e | % 7
-}
-
-
-tenorNotes = \relative c {
- \clef "treble_8"
- f2. | a2. | g2. | r2. | % 1-4
- c2. | b2. | c2. | % 5-7
-}
-
-\score {
- \new StaffGroup <<
- \new Staff = "triplum" <<
- %\set Staff.instrumentName = "Triplum"
- \set Staff.instrumentName = \incipitTriplum
- \set Staff.shortInstrumentName = "Tr."
- \set Staff.timeSignatureFraction = #'(9 . 8)
- \scaleDurations #'(2 . 3)
- \context Voice = "triplum" { \global \triplumNotes }
-% \scaleDurations #'(2 . 3)
-% \context Voice = "slashes" { \triplumSkips }
- \new Lyrics { \lyricsto "triplum" { \triplumWords }}
- >>
- \new Staff = "motetus" <<
- %\set Staff.instrumentName = "Motetus"
- \set Staff.instrumentName = \incipitMotetus
- \set Staff.shortInstrumentName = "M."
- \set Staff.timeSignatureFraction = #'(9 . 8)
- \scaleDurations #'(2 . 3)
- \context Voice = "motetus" { \global \motetusNotes }
- \new Lyrics { \lyricsto "motetus" { \motetusWords }}
- >>
- \new Staff = "tenor" {
- %\set Staff.instrumentName = "Tenor"
- \set Staff.instrumentName = \incipitTenor
- \set Staff.shortInstrumentName = "T."
- \global \tenorNotes
- }
- >>
- %\midi {}
- \layout {
- %\context {
- % \Staff \consists "Horizontal_bracket_engraver"
- %}
- \context {
- \Voice \consists "Horizontal_bracket_engraver"
- }
- }
-}
+++ /dev/null
-\version "2.12.0"
-%\include "example-header.ily"
-
-
-\header {
- mutopiatitle = "Jesu, meine Freude"
- mutopiacomposer = "BachJS"
- poet = "BWV 610"
- %mutopiaopus = "BWV 610"
- mutopiainstrument = "Organ"
- date = ""
- source = "Bach-Album, Ernst H. Wolfram (editor), 6787, C. F. Peters, Leipzig"
- style = "Baroque"
- copyright = "Public Domain"
- maintainer = "Urs Metzger"
- maintainerEmail = "urs@ursmetzger.de"
- lastupdated = "2006/Mar/15"
-
- title = "Jesu, meine Freude"
- composer = "Johann Sebastian Bach"
- %opus="BWV 610"
-
- footer = "Mutopia-2006/03/27-706"
- tagline = \markup { \override #'(box-padding . 1.0) \override #'(baseline-skip . 2.7) \box \center-column { \small \line { Sheet music from \with-url #"http://www.MutopiaProject.org" \line { \teeny www. \hspace #-1.0 MutopiaProject \hspace #-1.0 \teeny .org \hspace #0.5 } • \hspace #0.5 \italic Free to download, with the \italic freedom to distribute, modify and perform. } \line { \small \line { Typeset using \with-url #"http://www.LilyPond.org" \line { \teeny www. \hspace #-1.0 LilyPond \hspace #-1.0 \teeny .org } by \maintainer \hspace #-1.0 . \hspace #0.5 Reference: \footer } } \line { \teeny \line { This sheet music has been placed in the public domain by the typesetter, for details see: \hspace #-0.5 \with-url #"http://creativecommons.org/licenses/publicdomain" http://creativecommons.org/licenses/publicdomain } } } }
-
-}
-
-\include "deutsch.ly"
-
-global = {
- \key c \minor
- \time 4/4
- #(set-accidental-style 'default)
-}
-
-halsup = {
- \stemUp
- \tieUp
-}
-
-halsdown = {
- \stemDown
- \tieDown
-}
-
-staffup = {
- \change Staff = "right" \halsdown
-}
-
-staffdown = {
- \change Staff = "left" \halsup
-}
-
-sopran = {
- \new Voice \relative g' {
- \global
- \halsup
- \repeat volta 2 {
- g4^\markup { \hspace #-4 \large "Largo" } g f es
- d2 c\fermata
- g'4 g a h
- c2 h\fermata
- %% Takt 5 ==============================================
- c8. d16 es4 d4. d8
- c1\fermata
- }
- g4 g as g
- f4. f8 es2\fermata
- g4 g a h
- %% Takt 10 =============================================
- c4 b! a2
- g1\fermata
- g4 g f es
- d2 c2\fermata \bar "|."
- }
-}
-
-alt = {
- \new Voice \relative es' {
- \global
- \halsdown
- \repeat volta 2 {
- es16 d es8~ es16 f es d c8 d~ d c
- c8 c4 h8 c8. \staffdown g16 \staffup c h c d
- es16 d es8~ es16 f es d c8 d16 es f as g f~
- f16 e f8~ f16 g f es d es d8~ d16 es f d
- %% Takt 5 ==============================================
- g8 f es16 g as es f es f d g as g f
- e8 f16 g as g as e f g f8~ f16 f es d
- }
- es16 d es8~ es16 f es des c8 \staffdown b~ b16 b c g
- as16 g as f b c b as g f g8~ g16 b \staffup c d
- es16 d es8~ es16 f es d c8 d16 es f as g f
- %% Takt 10 =============================================
- es16 d es8 d g~g g4 fis8
- g16 d es c \staffdown d h c a h a h c d h g h
- c16 h c \staffup d es d es8~ es d4 c8~
- c16 h c8~ c h c16 \staffdown g as8 g4\fermata
- }
-}
-
-tenor = {
- \new Voice \relative c' {
- \global
- \repeat volta 2 {
- c16 h c8~ c16 h c g a8 g~ g16 g as es
- f16 es f d g as g f es d \tieDown es8~ es16 \tieNeutral f es d
- c16 h c g' c h c c, f8. g16 as!4~
- as16 g as b c h c8 d8. c16 h c d h
- %% Takt 5 ==============================================
- es16 d es d~ d8 c~c c4 h8
- c4~ c8. b16 as b as8 g16 as g f
- }
- \halsdown es16 f g as b des c b as g f8~ f es
- es8 es4 d8 es8. b16 es d es f
- es16 f g8 c16 d c b a g f8~ f4
- %% Takt 10 =============================================
- g16 fis g a b a b g c b c a d es d c
- h8 c16 a h g a fis g8 d16 es f es f8~
- f16 d es h c h c8 r16 f g d es g as fis
- g16 d f! es f as g f e8. f16~ f d e8\fermata
- }
-}
-
-right = {
- \clef treble
- <<
- \alt
- \sopran
- >>
-}
-
-left = {
- \clef bass
- <<
- \tenor
- >>
-}
-
-pedal = {
- \global
- \clef "bass"
- \relative c {
- \repeat volta 2 {
- r8 c16 d es d es8~ es16 a, h g c h c8
- r16 g as f g f g8 c,2
- r8 c'16 d es d es8~ es16 c f es d c d8
- c8 f16 g as g as8~ as16 d, fis d g fis g8
- %% Takt 5 ==============================================
- r8 a16 h c h c8
- r16 g as f g f g8
- r16 g as e f e f8 r16 e f h, c h c8
- }
- r8 es16 f g f g8~ g16 c, d! b es d es8
- r16 b c as b as b8 es,2
- r8 c'16 d es d es8~ es16 c f es d c d8
- %% Takt 10 =============================================
- c8 es16 f! g fis g8 r16 d es c d c d8
- g,1
- c4 c,8 c'16 b! a8 h c16 h c8
- r16 g as fis g fis g8 c,2_\fermata
- }
-}
-
-\score {
- \new PianoStaff
- { \set PianoStaff.instrumentName = \markup { \large \center-column {
- "a" "" "2 Clav." "" "e" "" "Pedale." } \hspace #0.5 }
- <<
- \context Staff = right
- {
- \context Voice = right \right
- }
- \context Staff = left {
- \context Voice = left \left
- }
- \context Staff = pedal {
- \context Voice = pedal \pedal
- }
- >>
- }
- \layout{}
-}
+++ /dev/null
-% -*-coding: utf-8 -*-
-
-\header{
- composer = "J.S. Bach"
- title = "Wenn wir in höchsten Nöten sein"
- subtitle = "Analysis from Gene Biringer's Schenker Text, Ex. 5-27"
-% "BWV641"
- enteredby = "Kris Shaffer"
-}
-
-%%
-%% See http://www.shaffermusic.com/doc/schenker/index.html for more information
-%%
-
-I = \once \override NoteColumn #'ignore-collision = ##t
-
-\version "2.12.0"
-
-staffPiano = \new PianoStaff {
- \set Score.timing = ##f
- \set PianoStaff.followVoice = ##t
-
- <<
- \new Staff = "RH" { % Right hand
- \clef treble
- \key g \major
- \relative c'' {
- \override Staff.NoteCollision
- #'merge-differently-headed = ##t
- <<
- {
- \override Beam #'positions = #'(8 . 8)
- \override NoteHead #'transparent = ##t
- \override NoteHead #'duration-log = #1
- s1 b8[^\markup {
- \override #'(baseline-skip . 0.5)
- \column { \small {^ 3} }
- }
- s4. s1 a8^\markup {
- \override #'(baseline-skip . 0.5)
- \column { \small {^ 2} }
- }
- s4. s2 g8]^\markup {
- \override #'(baseline-skip . 0.5)
- \column { \small {^ 1} }
- }
- s4.
- \revert Beam #'positions
- \revert NoteHead #'transparent
- \revert NoteHead #'duration-log
- }
- \\
- {
- \override Stem #'transparent = ##t
- s1
- \once \override Slur #'height-limit = #6
- \once \override Slur #'extra-offset = #'(1.25 . 0)
- \slurDashed
- \I b2_( s2
- \once \override NoteHead #'transparent = ##t
- b4) s
- \once \override Slur #'height-limit = #3.25
- \once \override Slur #'extra-offset = #'(.75 . 0)
- a2_( s4
- \once \override NoteHead #'transparent = ##t
- a)
- g2
- \revert Stem #'transparent
- }
- \\
- \override Staff.NoteCollision
- #'merge-differently-headed = ##t
- {
- \override Beam #'positions = #'(4 . -3.25)
- \stemUp
- g8[ s s4 s2
- \stemDown
- \once \override NoteHead #'transparent = ##t
- \I b8] s8
- \override Beam #'positions = #'(3 . -2.25)
- \stemUp
- a8[ s s4
- \stemDown
- c8] s s2 s s
- }
- \\
- {
- \override Stem #'transparent = ##t
- \override Stem #'length = #0
- g4_\( fis^(_\markup { \tiny N } g)\)
- a^(^\markup { \tiny P } b2)
- b4^(^\markup { \tiny P }
- \stemUp
- \revert Stem #'transparent
- \override Stem #'length = #10
- c8)^( s
- \override Stem #'length = #14
- b4) s s
- \override Stem #'length = #0
- \override Stem #'transparent = ##t
- \once \override Slur #'extra-offset = #'(0 . 0.35)
- c4^\( b_(_\markup { \tiny P } a)\) s2
- \revert Stem #'length
- }
- \\
- {
- \override Stem #'transparent = ##t
- \override NoteHead #'transparent = ##t
- \override Stem #'length = #0
- s1 s4 e4 s
- \change Staff = "LH"
- fis,4 s2
- \revert Stem #'transparent
- \revert NoteHead #'transparent
- \revert Stem #'length
- }
- \\
- {
- \override Stem #'transparent = ##t
- \override NoteHead #'transparent = ##t
- \override Stem #'length = #0
- s1 s s2
- fis'4 s
- \change Staff = "LH"
- g,4 s s2
- \revert Stem #'transparent
- \revert NoteHead #'transparent
- \revert Stem #'length
- }
- >>
- \bar "|."
- }
- }
-
- \new Staff = "LH" { % Left hand
- \clef bass
- \key g \major
- \relative c' {
- \override Staff.NoteCollision
- #'merge-differently-headed = ##t
- <<
- {
- \override Beam #'positions = #'(-8 . -8)
- \override NoteHead #'transparent = ##t
- \stemDown
- \I g8[_\markup { \bold I } s4. s1 s s2
- \I d8_\markup { \bold V } s4.
- \I g,8]_\markup { \bold I } s4.
- \revert Beam #'positions
- \revert NoteHead #'transparent
- }
- \\
- {
- \override Stem #'transparent = ##t
- \stemDown
- \override TextScript #'extra-offset = #'(-11.75 . -12.25)
- \I g'2 s1 s s2 \I d2 g,2
- \revert Stem #'transparent
- }
- \\
- {
- \override Stem #'transparent = ##t
- \once \override NoteHead #'transparent = ##t
- \override Stem #'length = #0
- g'4
- \once \override TextScript #'padding = #0.25
- a4_(^\markup { \tiny P } b)
- fis4^(^\markup { \tiny P } e)
- \once \override NoteHead #'transparent = ##t
- \once \override Slur #'height-limit = #1.5
- c4^(
- d)^\markup { \tiny N }
- \once \override NoteHead #'transparent = ##t
- \once \override Slur #'extra-offset = #'(0 . 0.5)
- \I fis,4_(
- \revert Stem #'transparent
- \override Stem #'length = #10
- \stemDown
- g4) s
- \once \override Slur #'extra-offset = #'(0 . 0.25)
- \I c8_( s
- \override Stem #'transparent = ##t
- \revert Stem #'length
- a4)
- \once \override NoteHead #'transparent = ##t
- \I d4^( d,4) s2
- }
- \\
- {
- \override Stem #'transparent = ##t
- \override NoteHead #'transparent = ##t
- \I g'4^( s b) s2
- \revert Stem #'transparent
- \revert NoteHead #'transparent
- \override Beam #'positions = #'(-4 . 1)
- \stemDown
- c,8[ s s4
- \stemUp
- fis,8] s
- \override Beam #'positions = #'(1 . -4)
- g8[ s
- \stemDown
- b8] s
- \revert Beam #'positions
- \override Stem #'transparent = ##t
- \override NoteHead #'transparent = ##t
- c4^( s d4) s s2
- }
- \\
- {
- \override Stem #'transparent = ##t
- \override NoteHead #'transparent = ##t
- \override Stem #'length = #0
- \stemDown
- \once \override Slur #'height-limit = #3
- \once \override Slur #'extra-offset = #'(0 . 0.25)
- \I g4_( s2. e4) s2. s2 s1 s2
- \revert Stem #'transparent
- \revert NoteHead #'transparent
- }
- \\
- {
- \override Stem #'transparent = ##t
- \override NoteHead #'transparent = ##t
- \slurDashed
- \once \override Slur #'height-limit = #6.0
- \once \override Slur #'extra-offset = #'(0.5 . -0.25)
- \override Stem #'length = #0
- g4_( s2. s1 g,4) s s1 s2
- \revert Stem #'transparent
- \revert NoteHead #'transparent
- }
- >>
- \bar "|."
- }
- }
- >>
-}
-
-
-\score {
- <<
- \staffPiano
- >>
-
-% \midi {
-% }
-
- \layout {
- indent = 0.0
- ragged-right = ##f
- \context { \Staff \remove "Time_signature_engraver" }
- }
-}
-
-
-\paper {
-}
+++ /dev/null
-
-\version "2.12.0"
-
-\layout {
- indent = #0
- ragged-right = ##t
- \context {
- \Score
-
- proportionalNotationDuration = #(ly:make-moment 1 64)
- \override Beam #'breakable = ##t
- autoBeaming = ##f
- tupletFullLength = ##t
- \override BarNumber #'transparent = ##t
- \override BarLine #'transparent = ##t
- \override SpanBar #'transparent = ##t
- \override Beam #'break-overshoot = #'(-0.5 . 1.0)
- \override TextScript #'staff-padding = #6
- \override Glissando #'thickness = #3
- \override SpacingSpanner #'strict-grace-spacing = ##t
- \override TupletBracket #'bracket-visibility = ##t
- \override NoteColumn #'ignore-collision = ##t
- }
-}
-
-\paper {
- oddHeaderMarkup = \markup \fill-line { " " }
- evenHeaderMarkup = \markup \fill-line { " " }
- oddFooterMarkup = \markup {
- \fill-line {
- \bold \fontsize #3 \on-the-fly #print-page-number-check-first \fromproperty #'page:page-number-string } }
- evenFooterMarkup = \markup {
- \fill-line {
- \bold \fontsize #3 \on-the-fly #print-page-number-check-first \fromproperty #'page:page-number-string } }
- printfirst-page-number = ##t
- print-page-number = ##t
- ragged-last-bottom = ##t
-}
-
-#(set-global-staff-size 14)
-
-
-%% definitions.
-
-
-ppX = #(make-dynamic-script (markup #:combine #:transparent #:dynamic "f" #:line(#:hspace 0 #:dynamic "pp" #:hspace 0)))
-pX = #(make-dynamic-script (markup #:combine #:transparent #:dynamic "f" #:line(#:hspace 0 #:dynamic "p" #:hspace 0)))
-mpX = #(make-dynamic-script (markup #:combine #:transparent #:dynamic "f" #:line(#:hspace 0 #:dynamic "mp" #:hspace 0)))
-fX = #(make-dynamic-script (markup #:combine #:transparent #:dynamic "f" #:line(#:hspace 0 #:dynamic "f" #:hspace 0)))
-ffX = #(make-dynamic-script (markup #:combine #:transparent #:dynamic "f" #:line(#:hspace 0 #:dynamic "ff" #:hspace 0)))
-sfp = #(make-dynamic-script "sfp")
-sfpp = #(make-dynamic-script "sfpp")
-sffp = #(make-dynamic-script "sffp")
-sffpp = #(make-dynamic-script "sffpp")
-
-beam = #(define-music-function (parser location left right) (number? number?)
- (cond ((and (= left 0) (> right 0))
- #{
- \set stemRightBeamCount = #$right
- #})
-
- ((and (> left 0) (= right 0))
- #{
- \set stemLeftBeamCount = #$left
- #})
-
- (else
- #{
- \set stemLeftBeamCount = #$left
- \set stemRightBeamCount = #$right
- #})
- )
-)
-
-fraction = #(define-music-function (parser location music) (ly:music?)
- #{ \tweak #'text #tuplet-number::calc-fraction-text $music #})
-
-triangle = #(define-music-function (parser location music) (ly:music?)
- #{ \once \set shapeNoteStyles = #'#(do do do do do do do) $music #})
-
-semicircle = #(define-music-function (parser location music) (ly:music?)
- #{ \once \set shapeNoteStyles = #'#(re re re re re re re) $music #})
-
-blackdiamond = #(define-music-function (parser location music) (ly:music?)
- #{ \once \set shapeNoteStyles = #'#(mi mi mi mi mi mi mi) $music #})
-
-tiltedtriangle = #(define-music-function (parser location music) (ly:music?)
- #{ \once \set shapeNoteStyles = #'#(fa fa fa fa fa fa fa) $music #})
-
-square = #(define-music-function (parser location music) (ly:music?)
- #{ \once \set shapeNoteStyles = #'#(la la la la la la la) $music #})
-
-wedge = #(define-music-function (parser location music) (ly:music?)
- #{ \once \set shapeNoteStyles = #'#(ti ti ti ti ti ti ti) $music #})
-
-harmonic = #(define-music-function (parser location music) (ly:music?)
- #{ \once \set shapeNoteStyles = #'#(harmonic harmonic harmonic harmonic harmonic harmonic harmonic) $music #})
-
-cross = #(define-music-function (parser location music) (ly:music?)
- #{ \once \set shapeNoteStyles = #'#(cross cross cross cross cross cross cross) $music #})
-
-white = #(define-music-function (parser location music) (ly:music?)
- #{ \once \override NoteHead #'duration-log = #1 $music #})
-
+++ /dev/null
-\version "2.12.0"
-% the example header file caused the head to be chopped off
-%\include "example-header.ily"
-
-
-\header {
- dedication = "Carin Levine"
- instrument = "bass flute"
- title = "ČÁRY"
- year = "2004--2006"
-
- subtitle = \markup { \italic Sorcery (extract) }
- % Measures 6 - 10;
-
- composer = "Trevor Bača"
- copyright = "Copyright 2006 Trevor Bača, licensed under the FDL 1.1 or higher"
-
-}
-
-% Verbatim from composer's score.
-%
-% Upper staff gives fingerings;
-% Lower staff gives special types of breath.
-%
-% Copyright 2006 Trevor Baca, but this exerpt is licensed under
-% the FDL 1.1 or higher.
-
-\include "english.ly"
-\include "cary-layout.ily"
-
-\new Score <<
-
- \new StaffGroup <<
-
- \new Staff \with {
- \override Stem #'direction = #down
- \override Beam #'positions = #'(-7 . -7)
- \override TupletBracket #'direction = #down
- \override TupletBracket #'staff-padding = #5
- \override TupletBracket #'padding = #2.25
- \override VerticalAxisGroup #'minimum-Y-extent = #'(10 . 10)
- } <<
-
- \new Voice {
-
- \override Score.MetronomeMark #'extra-offset = #'(0 . 6)
- \override Score.MetronomeMark #'font-size = #3
- \tempo 8=42
- \time 5/16 s4 ~ s16 \noBreak % measure 6
- \time 4/8 s2 \noBreak % measure 7
- \time 4/8 s2 \noBreak % measure 8
-
- }
-
- \new Voice \with {
- \remove Forbid_line_break_engraver
- } {
-
- % measure 6
- \fraction \times 5/3 {
- \times 4/5 {
- a'64 [ % 36
- cs''64 % 37
- f''64 % 38
- cs''64 % 39
- ef'''64 ] % 40
- }
- \times 4/5 {
- g''64 [ % 41
- c''64 % 42
- e''64 % 43
- g''64 % 44
- ef'''64 ] % 45
- }
- bf''16 % 46
- }
-
- % measure 7
- r8 % 47
- \times 4/5 {
- d''32 [ % 48
- af''32 % 49
- e'32 % 50
- b'32 % 51
- b'32 ] % 52
- }
- ef'''4 % 53
-
- % measure 8
- b''8 [ % 54
- g''8 ] % 55
- d''4 % 56
-
- }
- >>
-
- \new Staff \with {
- \override Clef #'transparent = ##t
- \override StaffSymbol #'line-positions = #'(-4 -2 2 4)
- \override Stem #'direction = #down
- \override TupletBracket #'staff-padding = #5
- \override TupletBracket #'padding = #2.25
- \override VerticalAxisGroup #'minimum-Y-extent = #'(10 . 10)
- } <<
-
- \new Voice \with {
- \remove Forbid_line_break_engraver
- \override Stem #'direction = #up
- \override Stem #'stroke-style = #"grace"
- \override Stem #'font-size = #-3
- \override Rest #'transparent = ##t
- \override NoteHead #'no-ledgers = ##t
- \override Dots #'transparent = ##t
- \override TupletBracket #'transparent = ##t
- \override TupletNumber #'transparent = ##t
- } {
-
- % measure 6
- \fraction \times 5/3 {
- \square f''16 * 1/8 % 40
- \square f''16 * 1/8 % 41
- \square f''16 * 1/8 % 42
- \square f''16 * 1/8 % 43
- \square f''16 * 1/8 % 44
- \square f''16 * 1/8 % 45
- \square f''16 * 1/8 % 46
- \square f''16 * 1/8 % 47
- \times 2/3 {
- \square f''16 % 48
- \square f''16 * 1/2 % 49
- }
- \times 2/3 {
- \square f''16 * 1/4 % 50
- \square f''16 * 1/4 % 51
- \square f''16 * 1/4 % 52
- \square f''16 * 1/4 % 53
- \square f''16 * 1/4 % 54
- \square f''16 * 1/4 % 55
- }
- }
-
- % measure 7
- s8 % 56
- \square g''16 * 2/1 % 57
- \square g''16 % 58
- \square g''16 % 59
- \times 8/9 {
- s16 % 60
- f''16 * 1/4 % 61
- f''16 * 1/4 % 62
- f''16 * 1/4 % 63
- f''16 * 1/4 % 64
- f''16 * 1/4 % 65
- }
-
- % measure 8
- \times 4/5 {
- \times 4/7 {
- s4 % 66
- \triangle a''16 % 67
- \triangle a''16 % 68
- \triangle a''16 % 69
- }
- s8 % 70
- \triangle a''16 * 1/2 % 71
- \triangle a''16 * 1/2 % 72
- \triangle a''16 * 1/2 % 73
- \triangle a''16 * 1/2 % 74
- \triangle a''16 * 1/2 % 75
- \triangle g''16 * 1/2 % 76
- \triangle g''16 * 1/2 % 77
- \triangle g''16 * 1/2 % 78
- }
-
- }
-
- \new Voice \with {
- \remove Forbid_line_break_engraver
- \override Stem #'transparent = ##t
- \override Rest #'transparent = ##t
- \override Rest #'staff-position = #-0.5
- \override Dots #'transparent = ##t
- \override Beam #'transparent = ##t
- \override TupletBracket #'transparent = ##t
- \override TupletNumber #'transparent = ##t
- } {
-
- % measure 6
- \fraction \times 5/3 {
- \blackdiamond f'128 [ % 40
- \blackdiamond f'128 % 41
- \blackdiamond f'128 % 42
- \blackdiamond f'128 % 43
- \blackdiamond f'128 % 44
- \blackdiamond f'128 % 45
- \blackdiamond f'128 % 46
- \blackdiamond f'128 ] % 47
- \times 2/3 {
- \blackdiamond f'16 % 48
- \blackdiamond f'32 % 49
- }
- \times 2/3 {
- \blackdiamond f'64 % 50
- \blackdiamond f'64 % 51
- \blackdiamond f'64 % 52
- \blackdiamond f'64 % 53
- \blackdiamond f'64 % 54
- \blackdiamond f'64 % 55
- }
- }
-
- % measure 7
- s8 % 56
- \harmonic a'8 \glissando % 57
- \harmonic a'16 \glissando % 58
- \blackdiamond a'16 % 59
- \times 8/9 {
- s16 % 60
- \harmonic g'64 \glissando % 61
- \harmonic g'64 \glissando % 62
- \harmonic g'64 \glissando % 63
- \harmonic g'64 \glissando % 64
- \blackdiamond g'64 % 65
- }
-
- % measure 8
- \times 4/5 {
- \times 4/7 {
- s4 % 66
- \blackdiamond f'16 % 67
- \blackdiamond f'16 % 68
- \blackdiamond f'16 % 69
- }
- s8 % 70
- \blackdiamond f'32 % 71
- \blackdiamond f'32 % 72
- \blackdiamond f'32 % 73
- \blackdiamond f'32 % 74
- \blackdiamond f'32 % 75
- \harmonic e'32 \glissando % 76
- \harmonic e'32 \glissando % 77
- \blackdiamond e'32 % 78
- }
-
- }
-
- \new Voice \with {
- \remove Forbid_line_break_engraver
- \override Stem #'direction = #down
- \override Stem #'font-size = #-3
- \override Stem #'stroke-style = #"grace"
- \override Rest #'transparent = ##t
- \override NoteHead #'no-ledgers = ##t
- \override Dots #'transparent = ##t
- \override TupletBracket #'transparent = ##t
- \override TupletNumber #'transparent = ##t
- } {
-
- % measure 6
- \fraction \times 5/3 {
- s128 % 40
- s128 % 41
- s128 % 42
- s128 % 43
- s128 % 44
- s128 % 45
- s128 % 46
- s128 % 47
- \times 2/3 {
- \semicircle a16 % 48
- \semicircle a16 * 1/2 % 49
- }
- \times 2/3 {
- \semicircle a16 * 1/4 % 50
- \semicircle a16 * 1/4 % 51
- \semicircle a16 * 1/4 % 52
- \semicircle a16 * 1/4 % 53
- \semicircle a16 * 1/4 % 54
- \semicircle a16 * 1/4 % 55
- }
- }
-
- % measure 7
- s8 % 56
- s8 % 57
- s16 % 58
- \triangle a16 % 59
- \times 8/9 {
- s16 % 60
- s64 % 61
- s64 % 62
- s64 % 63
- s64 % 64
- \triangle a16 * 1/4 % 65
- }
-
- % measure 8
- \times 4/5 {
- \times 4/7 {
- s4 % 66
- \semicircle a16 % 67
- \semicircle a16 % 68
- \semicircle a16 % 69
- }
- s8 % 70
- \semicircle a16 * 1/2 % 71
- \semicircle a16 * 1/2 % 72
- \semicircle a16 * 1/2 % 73
- \semicircle a16 * 1/2 % 74
- \semicircle a16 * 1/2 % 75
- s32 % 76
- s32 % 77
- \semicircle a16 * 1/2 % 78
- }
-
- }
-
- \new Voice \with {
- \remove Forbid_line_break_engraver
- \override Stem #'direction = #down
- \override NoteHead #'transparent = ##t
- \override NoteHead #'no-ledgers = ##t
- \override Rest #'staff-position = #-18
- \override Stem #'length = #10
- \override Beam #'positions = #'(-13 . -13)
- \override DynamicLineSpanner #'staff-padding = #18
- \override TextSpanner #'(bound-details left text) = #(markup (#:italic "covered"))
- \override TextSpanner #'dash-period = #1
- \override TextSpanner #'dash-fraction = #0.2
- \override TextSpanner #'(bound-details left padding) = #0.5
- \override TextSpanner #'(bound-details right padding) = #0.5
- \override TextSpanner #'staff-padding = #4
- } {
-
- % measure 6
- \fraction \times 5/3 {
- \beam #0 #5 g,128 \sffp \< [ % 40
- \beam #5 #5 g,128 % 41
- \beam #5 #5 g,128 % 42
- \beam #5 #5 g,128 % 43
- \beam #5 #5 g,128 % 44
- \beam #5 #5 g,128 % 45
- \beam #5 #5 g,128 % 46
- \beam #5 #1 g,128 % 47
- \times 2/3 {
- \beam #1 #2 g,16 % 48
- \beam #3 #1 g,32 \fX % 49
- }
- \times 2/3 {
- \beam #1 #4 g,64 \sffp \< % 50
- \beam #4 #4 g,64 % 51
- \beam #4 #4 g,64 % 52
- \beam #4 #4 g,64 % 53
- \beam #4 #4 g,64 % 54
- \beam #4 #0 g,64 \fX ] % 55
- }
- }
-
- % measure 7
- r8 % 56
- g,8 \sf \< [ % 57
- g,16 % 58
- \beam #2 #0 g,16 \ffX ] % 59
- \times 8/9 {
- r16 % 60
- \beam #4 #4 g,64 \sfp \< [ % 61
- \beam #4 #4 g,64 % 62
- \beam #4 #4 g,64 % 63
- \beam #4 #4 g,64 % 64
- \beam #4 #0 g,64 \fX ] % 65
- }
-
- % measure 8
- \times 4/5 {
- \times 4/7 {
- r4 % 66
- \beam #2 #2 g,16 \fX [ % 67
- \beam #2 #2 g,16 \f % 68
- \beam #2 #0 g,16 \fX ] % 69
- }
- r8 % 70
- \beam #3 #3 g,32 \fX [ % 71
- \beam #3 #3 g,32 \fX % 72
- \beam #3 #3 g,32 \fX % 73
- \beam #3 #3 g,32 \fX % 74
- \beam #3 #3 g,32 \fX % 75
- \beam #3 #3 g,32 \sf \< % 76
- \beam #3 #3 g,32 % 77
- \beam #3 #0 g,32 \ffX ] % 78
- }
-
- }
- >>
- >>
->>
+++ /dev/null
-\version "2.12.0"
-\include "example-header.ily"
-
-\include "predefined-guitar-fretboards.ly"
-
-#(set-global-staff-size 17)
-
-global = {
- \time 4/4
- \key g \major
- \partial 4
- \numericTimeSignature
-}
-
-melody = \relative c' {
- \global
- d4
- g4 b8( a) g4 fis
- e e e e
- a c8( b) a4 g
- fis a d
-}
-
-harmonies = \chordmode {
- \global
- s4 g1 | c | a:m | d % 1-3
-}
-
-text = \lyricmode {
- My eyes are dim, I can -- not see,
- I have not brought my specs with me!
-}
-
-\score {
- <<
- \new ChordNames { \harmonies }
- \new FretBoards { \harmonies }
- \new Staff {
- \context Voice = "vocal" { \melody }
- }
- \new Lyrics \lyricsto "vocal" \text
- >>
-}
-
+++ /dev/null
-\version "2.11.33"
-\paper{
- indent=0\mm
- ragged-last=##f
- ragged-right=##f
- line-width=158\mm % produces 624 pixels
- oddFooterMarkup=##f
- oddHeaderMarkup=##f
- bookTitleMarkup = ##f
- scoreTitleMarkup = ##f
-}
-
-\layout {
- \context { \Score
- \override PaperColumn #'keep-inside-line = ##t
- \override NonMusicalPaperColumn #'keep-inside-line = ##t
- }
-}
-
-
+++ /dev/null
-\version "2.12.0"
-\include "example-header.ily"
-
-%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-% This is a brief passage from Enrique Granados %
-% Goyescas, "Coloquio en la Reja." %
-%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-#(set-global-staff-size 17)
-
-\paper {
- ragged-right = ##f
- #(set-paper-size "letter" 'landscape)
- system-count = 1
-}
-
-
-csh = \change Staff = "high"
-csm = \change Staff = "middle"
-csl = \change Staff = "low"
-
-crmolto = \markup { \italic \large "cresc. molto" }
-appassmolto = \markup { \italic \large "appassionato molto" }
-
-#(ly:set-option 'point-and-click #f)
-
-global = {
- \time 3/4
- \set fontSize = #1
- \override Beam #'thickness = #0.5
- \override NoteColumn #'ignore-collision = ##t
-}
-
-upperVoiceOne = \relative c'' {
- \voiceOne
- \override TupletBracket #'transparent = ##t
- <aes f'>8\([ \times 4/5{g'32( aes g f g]) }
- <es aes>8[ \times 4/5{<d bes'>32( c' bes aes bes]) }
- <es, aes es'>8 <d fis b d>\) | % end m. 1
- %--------------------------------------------------%
- <c g' c>4\( \voiceTwo <bes es bes'\arpeggio>\)
- \slurUp <aes aes'>16( <bes bes'> <g g'>8) % end m. 2
- %--------------------------------------------------%
- \noBreak
- \voiceOne
- <f aes d f>8\([ \times 4/5{<g g'>32( aes' g f g]) }
- \set subdivideBeams = ##t
- \set beatLength = #(ly:make-moment 1 8)
- <aes, aes'>16 <c f> \times 4/5{ bes'32( c bes aes bes]) }
- \set subdivideBeams = ##f
- \ottava #1 <es es'>16 <f f'> <d d'> \appoggiatura f8 <es es'>16\)
-}
-
-upperVoiceTwo = \relative c'' {
- \voiceTwo
- s8 c8\< <bes, f'>[ <bes aes'> c' <bes, d fis>\!]
- s32 s32_\appassmolto s8. \voiceOne r8 <bes'' es bes'>-> s4
- \override Stem #'cross-staff = ##t
- \override Stem #'length = #28
- \override Stem #'flag-style = #'no-flag
- s8 \voiceTwo g,8 aes4 s4
-}
-
-middleVoiceOne = \relative c' {
- \override Stem #'cross-staff = ##t
- \override Stem #'length = #32
- \override Stem #'flag-style = #'no-flag
- d!8\noBeam s8 s8 s8_\crmolto s4 % 1
- s4 <g bes\arpeggio>8[ <es' g>] \voiceOne e,8( dis16 e) | % 2
- \revert Stem #'length
- \revert Stem #'cross-staff
- \showStaffSwitch
- \csh \stemUp f4 s2
- %s2. % beginning m. 3
-}
-
-middleVoiceTwo = \relative c' {
- s2. | % 1
- \override Stem #'cross-staff = ##t
- \override Stem #'length = #24
- \override Stem #'flag-style = #'no-flag
- s2 \voiceTwo e!4 | % 2
- s4 \voiceTwo <bes c es f>8 <f' aes es'>16 d' <bes, f' aes c>8 <bes' fis'> | % 3
-}
-
-lowerVoiceOne = \relative c, {
- \override Staff.NoteCollision #'merge-differently-headed = ##t
- \override Staff.NoteCollision #'merge-differently-dotted = ##t
- bes8 \csm \stemDown <bes'' c es>8 s2
- \csl \stemUp
- \set subdivideBeams = ##t
- \set beatLength = #(ly:make-moment 1 16)
- s8 \hideNotes \slurUp \stemDown
- es,,64( bes'' s64 \unHideNotes \stemUp g64[ bes c d c]) s2
- \set subdivideBeams = ##f
- bes,,8 \csm \stemDown <bes'' c es>8 s2
-}
-
-lowerVoiceTwo = \relative c, {
- \voiceTwo
- bes2.
- \csh
- \once \override Beam #'damping = #+inf.0
- <bes'' es g>8 \csl \slurUp
- %\once\override Slur #'extra-offset = #'(0 . 4)
- es,,64 bes' es g s32.
- c64
- s4 <bes des>
- bes,,2.
-}
-
-
-\score {
- \new PianoStaff <<
- \set PianoStaff.connectArpeggios = ##t
-% \override PianoStaff.Arpeggio #'stencil = #ly:arpeggio::brew-chord-bracket
- \new Staff = "high" <<
- \global
- \context Voice = "upperVoiceOne" { \upperVoiceOne }
- \context Voice = "upperVoiceTwo" { \upperVoiceTwo }
- >>
- \new Staff = "middle" <<
- \global
- \context Voice = "middleVoiceOne" { \middleVoiceOne }
- \context Voice = "middleVoiceTwo" { \middleVoiceTwo }
- >>
- \new Staff = "low" <<
- \clef bass
- \global
- \context Voice = "lowerVoiceOne" { \lowerVoiceOne }
- \context Voice = "lowerVoiceTwo" { \lowerVoiceTwo }
- >>
- >>
- \layout {
- \context {
- \Score
- \override TimeSignature #'stencil = ##f
- \remove "Bar_number_engraver"
- }
- }
- %{\midi {
- \context {
- \Score
- tempoWholesPerMinute = #(ly:make-moment 120 4)
- }
- }%}
-}
+++ /dev/null
-\version "2.13.4"
-
-\header {
- tagline = ##f
- title = "Violent Dance For Orchestra"
- composer = "Hu Haipeng"
-% arranger = "July 5, 2009"
-
-% poet = " I'm writing this piece because I'm terribly frustrated, facing a task which will seriously stain my aesthetics and conviction to the true art. It consists of all kinds of devils, dancing and whirling violently, turning the world into an abyss of darkness. Although the main melodies are derived from folk music, these are only a beautiful skin, and the essence of this piece is violent and evil, full of my 10 years' pain and rage. It's a large volcano of my long repressed heart!"
-}
-
-\paper{
- line-width = 158\mm
-}
-
-%% markups
-#(define-markup-list-command (paragraph layout props args) (markup-list?)
- (let ((indent (chain-assoc-get 'par-indent props 2)))
- (interpret-markup-list layout props
- (make-justified-lines-markup-list (cons (make-hspace-markup indent)
- args)))))
-
-#(define-markup-command (vspace layout props amount) (number?)
- "This produces a invisible object taking vertical space."
- (let ((amount (* amount 3.0)))
- (if (> amount 0)
- (ly:make-stencil "" (cons -1 1) (cons 0 amount))
- (ly:make-stencil "" (cons -1 1) (cons amount amount)))))
-
-%% text defs
-presto = \markup { \bold \italic "Presto" }
-div = \markup { \bold "Div." }
-nondiv = \markup { \bold "Non div." }
-unis = \markup { \bold "Unis." }
-piz = \markup { \bold "Pizz." }
-arc = \markup { \bold "Arco" }
-pizz = \set Staff.midiInstrument = "pizzicato strings"
-arco = \set Staff.midiInstrument = "string ensemble 1"
-pont = \markup { \bold \italic "Sul ponticello" }
-naturale = \markup { \bold \italic "Naturale" }
-moltocr = {
- \set crescendoText = \markup { \italic "Molto cresc." }
- \set crescendoSpanner = #'text
- \override DynamicTextSpanner #'style = #'dotted-line
-}
-offCr = {
- \unset crescendoText
- \unset crescendoSpanner
- \revert DynamicTextSpanner #'style
-}
-
-%% Layout to produce piano dynamics context
-\layout {
- \context {
- \type "Engraver_group"
- \name Dynamics
- \alias Voice
- \consists "Output_property_engraver"
- \consists "Skip_event_swallow_translator"
- \consists "Axis_group_engraver"
- \consists "Piano_pedal_engraver"
- pedalSustainStrings = #'("Ped." "*Ped." "*")
- pedalUnaCordaStrings = #'("una corda" "" "tre corde")
- \consists "Script_engraver"
- \consists "New_dynamic_engraver"
- \consists "Dynamic_align_engraver"
- \consists "Text_engraver"
- \consists "Text_spanner_engraver"
- \override VerticalAxisGroup #'minimum-Y-extent = #'(-1 . 1)
- \override DynamicLineSpanner #'Y-offset = #0
- \override TextScript #'font-size = #2
- \override TextSpanner #'bound-details #'left #'stencil-align-dir-y = #CENTER
- \override TextScript #'font-shape = #'italic
- \override TextSpanner #'breakable = ##t
- \override DynamicLineSpanner #'breakable = ##t
- \override DynamicTextSpanner #'breakable = ##t
- }
- \context {
- \PianoStaff
- \accepts "Dynamics"
- }
- \context {
- \Voice
- \override Glissando #'breakable = ##t
- \override TextSpanner #'breakable = ##t
- \override DynamicLineSpanner #'breakable = ##t
- \override DynamicTextSpanner #'breakable = ##t
- \override TrillSpanner #'breakable = ##t
- }
-}
-
-%% layout to create orchestra staff group
-%% with non-spanned barlines between two instrument groups
-\layout {
- \context {
- \StaffGroup
- \name Orchestra
- \remove "Span_bar_engraver"
- }
- \context {
- \Score
- \accepts Orchestra
- }
-}
-
-%% Layout to produce SquareStaff context
-%% to group similar instruments in a staff group with thin square bracket
-\layout {
- \context {
- \StaffGroup
- \name SquareStaff
- systemStartDelimiter = #'SystemStartSquare
- }
- \context {
- \Orchestra
- \accepts SquareStaff
- }
- \context {
- \StaffGroup
- \accepts SquareStaff
- }
-}
-
-%% Layout to produce MarkLine context
-%% to place rehearsal marks and texts above full score
-\layout {
- \context {
- \type "Engraver_group"
- \name "MarkLine"
- \consists "Output_property_engraver"
- \consists "Axis_group_engraver"
- \consists "Mark_engraver"
- \consists "Metronome_mark_engraver"
- \consists "Script_engraver"
- \consists "Text_engraver"
- \consists "Text_spanner_engraver"
- \consists "Font_size_engraver"
- \override VerticalAxisGroup #'minimum-Y-extent = #'(-2 . 2 )
- \override TextSpanner #'breakable = ##t
- }
- \context {
- \Score
- \accepts "MarkLine"
- }
- \context {
- \Orchestra
- \accepts "MarkLine"
- }
- \context {
- \StaffGroup
- \accepts "MarkLine"
- }
-}
-
-%% layout to produce a smaller markline
-%% put before 1st violin part
-\layout {
- \context {
- \MarkLine
- \name "SmallMarkLine"
- \override MetronomeMark #'outside-staff-priority = #800
- \override RehearsalMark #'outside-staff-priority = #1200
- }
- \context {
- \Score
- \accepts SmallMarkLine
- }
- \context {
- \Orchestra
- \accepts SmallMarkLine
- }
- \context {
- \StaffGroup
- \accepts SmallMarkLine
- }
-}
-
-modern =
-#`(Staff ,(make-accidental-rule 'same-octave 0)
- ,(make-accidental-rule 'any-octave 0)
- ,(make-accidental-rule 'same-octave 1))
-
-\layout {
- \context {
- \Score
- autoAccidentals = #modern
- autoCautionaries = #modern
- }
-}
-
- marks = \relative c' {
- \set markFormatter = #format-mark-box-numbers
- \tempo \presto 4.=112
-\set Score.currentBarNumber = #11
- s2.*4 |
- s1*9/8 |
- }
-
- piccolo = \relative c'''' {
- \clef treble \key ees \minor \time 6/8
- \transposition c''
- R2.
- ges,16(\mf\< ees c ees ges bes) c( bes ges bes c ees) |
- ges8-.->\!\ff \offCr r r r4 r8 | R2. |
- \time 9/8
- R1*9/8 |
- }
-
- flutes = \relative c'''' {
- \clef treble \key ees \minor \time 6/8
- R2.
- <ges, c,>16(\mf\< <ees bes> <c ges> <ees bes> <ges c,> <bes ees,>) <c ges>( <bes ees,> <ges c,> <bes ees,> <c ges> <ees bes>) |
- <ges c,>8-.->\!\ff \offCr r r r4 r8 | R2. |
- \time 9/8
- R1*9/8 |
- }
-
- oboes = \relative c''' {
- \clef treble \key ees \minor \time 6/8
- R2. |
- <ges, c,>4(\mf\< <bes ees,>8 <c ges>4 <ees bes>8) |
- <ges c,>-.->\!\ff \offCr r r r4 r8 | R2. |
- \time 9/8
- R1*9/8 |
- }
-
- clarinets = \relative c' {
- \clef treble \key f \minor \time 6/8
- \transposition bes
- <aes' d,>4(\p\< <c f,>8) <d aes>4( <f c>8) |
- <aes d,>4( <c f,>8) <d aes>4( <f c>8) |
- <aes d,>-.->\!\ff \offCr r r r4 r8 | R2. |
- \time 9/8
- R1*9/8 |
- }
-
- bassoons = \relative c, {
- \clef bass \key ees \minor \time 6/8
- <ees bes'>4.\pp\< c'^"a2" |
- bes8-. bes-. bes-. ges-. ges-. ges-. |
- ees-.->\!\ff \offCr <ees bes'>4\pp ~ <ees bes'>4. ~ | <ees bes'>2. |
- \time 9/8
- ges4\p^"I" aes8 aes ees ges ges4 aes16( ges) |
- }
-
- hornI = \relative c'' {
- \clef treble \key bes \minor \time 6/8
- \transposition f
- r4 r8 <f bes,>4.\p\< ~ |
- <f bes,>8-. <f bes,>-. <f bes,>-. <f bes,>-. <f bes,>-. <f bes,>-. |
- <f bes,>-.->\!\ff \offCr r r r4 r8 | R2. |
- \time 9/8
- r4 r8 <b, g>2.\pp |
- }
-
- hornII = \relative c'' {
- \clef treble \key bes \minor \time 6/8
- \transposition f
- \moltocr <des g,>2.\pp\< ~ |
- <des g,>8-. <f bes,>-. <f bes,>-. <f bes,>-. <f bes,>-. <f bes,>-. |
- <f bes,>-.->\!\ff \offCr r r r4 r8 | R2. |
- \time 9/8
- <f, des>2.\pp <f des>4. ~ |
- }
-
- trumpetI = \relative c''' {
- \clef treble \key f \minor \time 6/8
- \transposition bes
-R2. |
- r4 r8 <aes f>-.\f\< <aes f>-. <aes f>-. |
- <c aes>-.->\!\ff r r r4 r8 | R2. |
- \time 9/8
- R1*9/8 |
- }
-
- trumpetII = \relative c'' {
- \clef treble \key f \minor \time 6/8
- \transposition bes
-R2. |
- r8 d-.\mf\< d-. d-. d-. d-. |
- d-.->\!\ff \offCr r r r4 r8 | R2. |
- \time 9/8
- R1*9/8 |
- }
-
- trombones = \relative c' {
- \clef tenor \key ees \minor \time 6/8
- r4 r8 <ges c>4.\mp\< ~ |
- <ges c>8-. <ges c>-. <ges c>-. <ges c>-. <ges c>-. <ges c>-. |
- <ges c>-.->\!\ff \offCr r r r4 r8 | R2. |
- \time 9/8
- R1*9/8 |
- }
-
- tuba = \relative c,, {
- \clef bass \key ees \minor \time 6/8
- <ees' ees'>4.(\pp\< <c c'> |
- <bes bes'>8-.) <bes bes'>-. <bes bes'>-. <ges ges'>-. <ges ges'>-. <ges ges'>-. |
- <ees ees'>-.->\!\ff \offCr r r r4 r8 | R2. |
- \time 9/8
- R1*9/8 |
- }
-
- timpani = \relative c {
- \clef bass \key ees \minor \time 6/8
- ees8\< ees ees ees ees ees |
- bes bes bes bes bes bes |
- ees,->\!\f \offCr ees'\pp ees ees ees ees |
- ees ees ees ees ees ees |
- \time 9/8
- ees r r r4 r8 r4 r8 |
- }
-
- trian = \relative c' {
- \clef percussion \time 6/8
- R2.*4 |
- \time 9/8
- R1*9/8 |
- }
-
- cym = \relative c' {
- \clef percussion \time 6/8
- R2.*4 |
- \time 9/8
- R1*9/8 |
- }
-
- tamt = \relative c' {
- \clef percussion \time 6/8
-R2. |
- r4 r8 r c4\mf\<^"*" ~ |
- c8\!\ff r r r4 r8 | R2. |
- \time 9/8
- R1*9/8 |
- }
-
- tamb = \relative c' {
- \clef percussion \time 6/8
- R2.*4 |
- \time 9/8
- R1*9/8 |
- }
-
- snare = \relative c' {
- \clef percussion \time 6/8
- R2.*4 |
- \time 9/8
- c8\pp c c c c c c c c |
- }
-
- bsdrum = \relative c' {
- \clef percussion \time 6/8
- c2.:32\pp\< ~ | c: ~ |
- c8\!\ff \offCr r r r4 r8 | R2. |
- \time 9/8
- c2.:32\pp ~ c4.: |
- }
-
- harprh = \relative c'' {
- \clef treble \key ees \minor \time 6/8
- \showStaffSwitch
- R2.*4_\markup { \harp-pedal #"--^|^^^^" } |
- \time 9/8
- R1*9/8 |
- }
-
- harplh = \relative c {
- \clef bass \key ees \minor
- \showStaffSwitch
- R2.*4 |
- R1*9/8 |
- }
-
- dynamics = {
- s2.*4 |
- s1*9/8 |
- }
-
-
- violinI = \relative c'''' {
- \clef treble \key ees \minor \time 6/8
- ges,,16(\pp\< ees c ees ges bes) c( bes ges bes c ees) |
- ges( ees c ees ges bes) c( bes ges bes c ees) |
- ges8-.->\!\ff \offCr r r r4 r8 | R2. |
- \time 9/8
- R1*9/8 |
- }
-
- violinII = \relative c''' {
- \clef treble \key ees \minor \time 6/8
- c,,16(\pp\< bes ges bes c ees) ges( ees c ees ges bes) |
- c( bes ges bes c ees) ges( ees c ees ges bes) |
- c8-.->\!\ff \offCr r r r4 r8 | R2. |
- \time 9/8
- r4 r8 \repeat tremolo 6 { c,,32->\pp^\pont e } r4 r8 |
- }
-
- viola = \relative c {
- \clef alto \key ees \minor \time 6/8
- <ees bes'>8-.\pp\< <ees bes'>-. <ees bes'>-. <ges c>-. <ges c>-. <ges c>-. |
- <bes ees>-. <bes ees>-. <bes ees>-. <c ges'>-. <c ges'>-. <c ges'>-. |
- <ees bes'>-.->\!\ff \offCr r r r4 r8 | R2. |
- \time 9/8
- \repeat tremolo 12 { ges,32->^\pont bes } \repeat tremolo 6 {ges->( bes) } |
- }
-
- cello = \relative c {
- \clef bass \key ees \minor \time 6/8
- <c ges'>8-.\pp\< <c ges'>-. <c ges'>-. <bes ees>-. <bes ees>-. <bes ees>-. |
- <c ges'>-. <c ges'>-. <c ges'>-. <c ges'>-. <c ges'>-. <c ges'>-. |
- <bes ges'>8-.->\!\ff \offCr <c ges'>-.\pp <c ges'>-. <c ges'>-. <c ges'>-. <c ges'>-. |
- <c ges'>-. r r r4 r8 |
- \time 9/8
- \repeat tremolo 12 <c ges'>32(^\pont \repeat tremolo 12 <cis g'> \repeat tremolo 12 <c ges'>) |
- }
-
- contrabass = \relative c {
- \clef bass \key ees \minor \time 6/8
- \transposition c
- <ees bes'>8-.\pp\< ees-. ees-. c-. c-. c-. |
- bes-. bes-. ges-. ges-. ges-. ges-. |
- ees-.->\!\ff \offCr <ees' bes'>-.\pp <ees bes'>-. <ees bes'>-. <ees bes'>-. <ees bes'>-. |
- <ees bes'>-. <ees bes'>-. <ees bes'>-. <ees bes'>-. <ees bes'>-. <ees bes'>-. |
- \time 9/8
- <ees bes'>-. <ees bes'>-. <ees bes'>-. <ees bes'>-. <ees bes'>-. <ees bes'>-. <ees bes'>-. <ees bes'>-. <ees bes'>-. |
- }
-
- #(set-global-staff-size 10)
-
- \score {
- \new Orchestra = "orchestra" <<
- \set Score.skipBars = ##f
- \new MarkLine { \marks }
- \new StaffGroup = "woodwind" <<
- \new SquareStaff = "picc fl" <<
- \new Staff = "piccolo" {
- \set Staff.instrumentName = "Piccolo"
- \set Staff.shortInstrumentName = "Picc."
- \piccolo
- }
- \new Staff = "flutes" {
- \set Staff.instrumentName = "Flutes I & II"
- \set Staff.shortInstrumentName = "Fl."
- \flutes
- }
- >>
- \new Staff = "oboes" {
- \set Staff.instrumentName = "Oboes I & II"
- \set Staff.shortInstrumentName = "Ob."
- \oboes
- }
- \new Staff = "clarinets" {
- \set Staff.instrumentName = \markup {
- \column { \line { "Clarinets I & II" }
- \line { "in B" \smaller \flat } } }
- \set Staff.shortInstrumentName = "Cl."
- \clarinets
- }
- \new Staff = "bassoons" {
- \set Staff.instrumentName = "Bassoons I & II"
- \set Staff.shortInstrumentName = "Bn."
- \bassoons
- }
- >>
- \new StaffGroup = "brass" <<
- \new SquareStaff = "horns" <<
- \new Staff = "hornsI" {
- \set Staff.instrumentName = \markup {
- \column { \line { "Horns I & II" }
- \line { "in F" } } }
- \set Staff.shortInstrumentName = "Hn. I & II"
- \hornI
- }
- \new Staff = "hornsII" {
- \set Staff.instrumentName = \markup {
- \column { \line { "Horns III & IV" }
- \line { "in F" } } }
- \set Staff.shortInstrumentName = "Hn. III & IV"
- \hornII
- }
- >>
- \new SquareStaff = "trumpets" <<
- \new Staff = "trumpetI" {
- \set Staff.instrumentName = \markup {
- \column { \line { "Trumpets I & II" }
- \line { "in B" \smaller \flat } } }
- \set Staff.shortInstrumentName = "Tp. I & II"
- \trumpetI
- }
- \new Staff = "trumpetII" {
- \set Staff.instrumentName = \markup {
- \column { \line { "Trumpet III" }
- \line { "in B" \smaller \flat } } }
- \set Staff.shortInstrumentName = "Tp. III"
- \trumpetII
- }
- >>
- \new SquareStaff = "trombones" <<
- \new Staff = "trombones 1 & 2" {
- \set Staff.instrumentName = "Trombones I & II"
- \set Staff.shortInstrumentName = "Tb. I & II"
- \trombones
- }
- \new Staff = "tuba" {
- \set Staff.instrumentName = "Bass trombone & Tuba"
- \set Staff.shortInstrumentName = "Btb. & Tu."
- \tuba
- }
- >>
- >>
- \new Staff = "timpani" {
- \set Staff.instrumentName = "Timpani in A, D & E"
- \set Staff.shortInstrumentName = "Tim."
- \timpani
- }
- \new GrandStaff = "drums" <<
- \new RhythmicStaff = "triangle" {
- \set RhythmicStaff.instrumentName = "Triangle"
- \set RhythmicStaff.shortInstrumentName = "Tri."
- \trian
- }
- \new RhythmicStaff = "cymbals" {
- \set RhythmicStaff.instrumentName = "Suspended cymbal"
- \set RhythmicStaff.shortInstrumentName = "Susp. cym."
- \cym
- }
- \new RhythmicStaff = "tamtam" {
- \set RhythmicStaff.instrumentName = "Tamtam"
- \set RhythmicStaff.shortInstrumentName = "Tamt."
- \tamt
- }
- \new RhythmicStaff = "tambourine" {
- \set RhythmicStaff.instrumentName = "Tambourine"
- \set RhythmicStaff.shortInstrumentName = "Tamb."
- \tamb
- }
- \new RhythmicStaff = "snare" {
- \set RhythmicStaff.instrumentName = "Snare drum"
- \set RhythmicStaff.shortInstrumentName = "Sn."
- \snare
- }
- \new RhythmicStaff = "bass drum" {
- \set RhythmicStaff.instrumentName = "Bass drum"
- \set RhythmicStaff.shortInstrumentName = "Bd."
- \bsdrum
- }
- >>
- \new PianoStaff = "harp" <<
- \set PianoStaff.instrumentName = "Harp"
- \set PianoStaff.shortInstrumentName = "Hrp."
- \set PianoStaff.connectArpeggios = ##t
- \new Staff = "rh" { \harprh }
- \new Dynamics { \dynamics }
- \new Staff = "lh" { \harplh }
- >>
- \new SmallMarkLine { \marks }
- \new StaffGroup = "strings" <<
- \new SquareStaff = "violins" <<
- \new Staff = "violin I" {
- \set Staff.instrumentName = "Violin I"
- \set Staff.shortInstrumentName = "Vn. I"
- \violinI
- }
- \new Staff = "violin II" {
- \set Staff.instrumentName = "Violin II"
- \set Staff.shortInstrumentName = "Vn. II"
- \violinII
- }
- >>
- \new Staff = "viola" {
- \set Staff.instrumentName = "Viola"
- \set Staff.shortInstrumentName = "Vl."
- \viola
- }
- \new SquareStaff = "Cello and Bass" <<
- \new Staff = "violoncello" {
- \set Staff.instrumentName = "Violoncello"
- \set Staff.shortInstrumentName = "Vc."
- \cello
- }
- \new Staff = "contrabass" {
- \set Staff.instrumentName = "Contrabass"
- \set Staff.shortInstrumentName = "Cb."
- \contrabass
- }
- >>
- >>
- >>
- \layout {
- \context {
- \Score
- \remove "Mark_engraver"
- \remove "Metronome_mark_engraver"
- }
- \context {
- \RemoveEmptyStaffContext
- }
- }
- }
-
+++ /dev/null
-%%% G.F Haendel, Giulio Cesare in Egitto
-%%% Act I, scene IV
-%%% Sesto: Svegliatevi nel core, furie d'un alma offesa (excerpt)
-%%%
-%%% Nicolas Sceaux <nicolas.sceaux@free.fr>
-
-\version "2.12.2"
-\include "sesto.ily"
-
-%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-%%%
-%%% Lead sheet
-%%%
-%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-
-\book {
- \paper {
- #(layout-set-staff-size 14)
- }
- \score {
- \new StaffGroupNoBar <<
- \new StaffGroupNoBracket <<
- \new Staff <<
- \set Staff.instrumentName = "Violino I."
- \global \clef treble \keepWithTag #'violin \violinoI
- >>
- \new Staff <<
- \set Staff.instrumentName = "Violino II."
- \global \clef treble \keepWithTag #'violin \violinoII
- >>
- >>
- \new Staff <<
- \new Voice = "sesto" \with { autoBeaming = ##f } <<
- \set Staff.instrumentName = \markup \smallCaps Sesto.
- \global \clef treble \sesto
- >>
- \lyricsto "sesto" \new Lyrics \sestoLyrics
- >>
- \new Staff <<
- \set Staff.instrumentName = "Bassi."
- \global \clef bass \bassi
- >>
- >>
- \layout {
- indent = 20\mm
- \context {
- \Score
- \name Score
-%% FIXME: vertical engine changed!
-%% \override VerticalAlignment #'max-stretch = #ly:align-interface::calc-max-stretch
- \accepts "StaffGroupNoBar"
- skipBars = ##t
- }
- \context {
- \StaffGroup
- \name StaffGroupNoBar
- \description "Like StaffGroup, but without spanbar"
- \remove "Span_bar_engraver"
- \accepts "StaffGroupNoBracket"
- }
- \context {
- \StaffGroup
- \name StaffGroupNoBracket
- \description "Like StaffGroup, but without brackets"
- \remove "System_start_delimiter_engraver"
- }
- }
-% \midi { }
- }
-}
-
-
+++ /dev/null
-%%% G.F Haendel, Giulio Cesare in Egitto
-%%% Act I, scene IV
-%%% Sesto: Svegliatevi nel core, furie d'un alma offesa (excerpt)
-%%%
-%%% Nicolas Sceaux <nicolas.sceaux@free.fr>
-
-\version "2.12.2"
-\include "sesto.ily"
-
-%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-%%%
-%%% Reduction
-%%%
-%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-
-\book {
- \header { instrument = "Vocal part and keyboard reduction" }
- \paper {
- #(layout-set-staff-size 16)
- }
- \score {
- <<
- \new Staff <<
- \new Voice = "sesto" \with { autoBeaming = ##f } <<
- \set Staff.instrumentName = \markup \smallCaps Sesto.
- \global \clef treble \sesto
- >>
- \lyricsto "sesto" \new Lyrics \sestoLyrics
- >>
- \new PianoStaff <<
- \new Staff <<
- \global \clef treble
- \partcombine \keepWithTag #'reduction \violinoI \keepWithTag #'reduction \violinoII
- >>
- \new Staff <<
- \global \clef bass \bassi
- >>
- >>
- >>
- \layout {
- indent = 20\mm
- \context { \Voice printPartCombineTexts = ##f }
- }
- }
-}
-
+++ /dev/null
-%%% G.F Haendel, Giulio Cesare in Egitto
-%%% Act I, scene IV
-%%% Sesto: Svegliatevi nel core, furie d'un alma offesa (excerpt)
-%%%
-%%% Nicolas Sceaux <nicolas.sceaux@free.fr>
-
-\version "2.12.2"
-\include "sesto.ily"
-
-%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-%%%
-%%% Violino I
-%%%
-%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-
-\book {
- \header { instrument = "Violino I" }
- \paper {
- #(layout-set-staff-size 18)
- }
- \score {
- \new Staff <<
- \global \clef treble \keepWithTag #'violin \violinoI
- >>
- \layout { indent = 5\mm }
- }
-}
+++ /dev/null
-%%% G.F Haendel, Giulio Cesare in Egitto
-%%% Act I, scene IV
-%%% Sesto: Svegliatevi nel core, furie d'un alma offesa (excerpt)
-%%%
-%%% Nicolas Sceaux <nicolas.sceaux@free.fr>
-
-\version "2.12.2"
-\header {
- title = "Giulio Cesare in Egitto"
- subtitle = "Sesto: Svegliatevi nel core, furie d'un alma offesa (excerpt)"
- composer = "G.F Handel"
-}
-
-%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-%%%
-%%% Notes and lyrics
-%%%
-%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-sesto = {
- R1*6 |
- r4 r8 g' c'' ees''16[ d''] c''8 c'' |
- c'' g' ees''4 ~ ees''8 d''16 ees'' f''8 aes' |
- aes' g' r c'' c'' b'16[ c''] d''8 g' |
-
-%{
- %%10
- f'4 r8 d'' ees'' d''16[ c''] b'4 |
- c'' r8 c'' c''8. c'16 c'4 |
- r r8 c'' aes' c''16[ bes'] aes'8 g' |
- f' f' r4 bes'8 bes'16 aes' g'8 f' |
- ees' ees' r ees'' ees'' d''16[ ees''] f''8 bes' |
- %%15
- aes'4. bes'8 g' ees'' f'4 |
- ees' r8 ees'' ees''8. ees'16 ees'4 |
- r r8 c'' c''8. c'16 c'4 |
- r r8 c'' c'' d''16[ ees''] f''8 ees'' |
- d'' bes' r4 bes'8 c''16 d'' ees''8 d'' |
- %%20
- c'' c'' r c'' f' f''16[ ees''] d''8 c'' |
- b'16[ a'] g'8 r4 ees''8 ees''16 d'' c''8 bes' |
- aes' g' r g' aes' f' d'' b' |
- f''2 ~ f''8 d'' b' g' |
- ees'4 r8 d'' ees'' d''16[ c''] b'4 |
- %%25
- c'' r8 g' c'' g' ees' g' |
- c'4 r8 g' aes' f' d'' b' |
- f''2 ~ f''8 d'' b' g' |
- ees'4 r8 g'' ees'' d''16[ c''] b'4 |
- c''2 r |
- %%30
- R1*5 |
-%}
-}
-
-sestoLyrics = \lyricmode {
- Sve -- glia -- te -- vi nel co -- re,
- fu -- rie "d'un" al -- "ma of" -- fe -- sa,
-%{
- a far "d'un" tra -- di -- tor a -- spra ven -- det -- ta!
- sve -- glia -- te -- vi,
- sve -- glia te -- vi nel co -- re,
- fu -- rie d'un al -- "ma of" -- fe -- sa,
- a far "d'un" tra -- di -- tor as -- pra ven -- det -- ta,
- sve -- glia -- te -- vi,
- sve -- glia -- te -- vi,
- sve -- glia -- te -- vi nel co -- re,
- fu -- rie d'un al -- "ma of" -- fe -- sa,
- sve -- glia -- te -- vi nel co -- re,
- fu -- rie d'un al -- "ma of" -- fe -- sa,
- a far d'un tra -- di -- tor, __
- d'un tra -- di -- tor as -- spra ven -- det -- ta,
- a far d'un tra -- di -- tor,
- a far d'un tra -- di -- tor, __
- d'un tra -- di -- tor as -- pra ven -- det -- ta!
-%}
-}
-
-violinoI = {
- r4 r8 g' c'' ees''16 d'' c''8 c'' |
- c'' c' ees''4 ~ ees''8 d''16 ees'' f''8 aes' |
- aes' g' r c'' c''8.^\trill b'32 c'' d''8 g' |
- f'4. d''8 ees'' d''16 c'' b'4 |
- %%5
- c''16 g'' f'' g'' ees'' g'' f'' g'' ees'' g'' f'' g'' ees'' g'' f'' g'' |
- c'' g'' f'' g'' ees'' g'' f'' g'' aes''8 g''16 f'' f''4^\trill |
- ees'' r8 g'_\p c'' ees''16 d'' c''8 c'' |
- c'' g' ees''4 ~ ees''8 d''16 ees'' f''8 aes' |
- aes' g' r c'' c'' b'16 c'' d''8 g' |
-%{
- %%10
- f'4 r8 d'' ees'' d''16 c'' b'4 |
- c''16 g'' f'' g'' ees'' g'' f'' g'' ees'' g'' f'' g'' ees'' g'' f'' g'' |
- ees'' g'' f'' g'' ees'' g'' f'' g'' aes''8 aes' r4 |
- d''16 f'' ees'' f'' d'' f'' ees'' f'' g''8 g' r4 |
- ees'16 g' f' g' ees'8 ees'' ees'' d''16 ees'' f''8 bes' |
- %%15
- aes'4. bes'8 g' ees'' d''4 |
- ees''16 bes'' aes'' bes'' g'' bes'' aes'' bes'' g'' bes'' aes'' bes'' g'' bes'' aes'' bes'' |
- g'' g'' f'' g'' ees'' g'' f'' g'' ees'' g'' f'' g'' ees'' g'' f'' g'' |
- ees'' g'' f'' g'' ees'' g'' f'' g'' aes'' c'' c'' bes' aes' c'' bes' c'' |
- d'' f'' ees'' f'' d'' f'' ees'' f'' g'' bes' bes' aes' g' bes' aes' bes' |
- %%20
- c'' ees'' ees'' f'' g'' ees'' f'' g'' aes'' f'' g'' ees'' f'' d'' ees'' c'' |
- \tag #'violin { g'' g' g'' g'' } \tag #'reduction { g'' d'' g'' g'' } g'' b' g'' g'' g'' f'' ees'' d'' c''8 bes' |
- aes' g' r g' aes' f' d'' b' |
- f''2 ~ f''8 d'' b' g' |
- ees'16 c' g' ees' c'' g' g'' d'' g'4 r |
- %%25
- c'''16 ees''' d''' ees''' c''' ees''' d''' ees''' g'' c''' b'' c''' g'' c''' b'' c''' |
- ees'' g'' f'' g'' ees'' g'' f'' g'' \tag #'violin { aes'8 f' } \tag #'reduction { c''8 aes' } d'' b' |
- f''2 ~ f''8 d'' b' g' |
- ees'4^\fermata r r2 |
- r4 r8 c'_\f c'' ees''16 d'' c''8 c'' |
- %%30
- c'' c' ees''4 ~ ees''8 d''16 ees'' f''8 aes' |
- aes' g' r g' aes' f' d'' b' |
- f''2 ~ f''8 d'' b' g' |
- c''16 g'' f'' g'' ees'' g'' f'' g'' c'' g'' f'' g'' ees'' g'' f'' g'' |
- b'8 c''16 d'' ees''8 d'' c''4^\fermata r
-%}
-}
-
-violinoII = {
- r4 r8 g' c'' ees''16 d'' c''8 c'' |
- c'' c' ees''4 ~ ees''8 d''16 ees'' f''8 aes' |
- aes' g' r c'' c''8.^\trill b'32 c'' d''8 g' |
- f'4. d''8 ees'' d''16 c'' b'4 |
- %%5
- c''16 ees'' d'' ees'' c'' ees'' d'' ees'' c'' ees'' d'' ees'' c'' ees'' d'' ees'' |
- c'' ees'' d'' ees'' c'' ees'' d'' ees'' d''8[ ees''] ees'' d'' |
- ees''4 r8 g' c'' ees''16 d'' c''8 c'' |
- c'' g' ees''4 ~ ees''8 d''16 ees'' f''8 aes' |
- aes' g' r c'' c'' b'16 c'' d''8 g' |
-%{
- %%10
- f'4 r8 d'' ees'' d''16 c'' b'4 |
- c''16 ees'' d'' ees'' c'' ees'' d'' ees'' c'' ees'' d'' ees'' c'' ees'' d'' ees'' |
- c'' ees'' d'' ees'' c'' ees'' d'' ees'' f''8 f' r4 |
- bes'16 d'' c'' d'' bes' d'' c'' d'' ees''8 ees' r4 |
- c'16 ees' d' ees' c'8 ees'' ees'' d''16 ees'' f''8 bes' |
- %%15
- aes'4. bes'8 g' ees'' d''4 |
- ees''16 g'' f'' g'' ees'' g'' f'' g'' ees'' g'' f'' g'' ees'' g'' f'' g'' |
- ees'' ees'' d'' ees'' c'' ees'' d'' ees'' c'' ees'' d'' ees'' c'' ees'' d'' ees'' |
- c'' ees'' d'' ees'' c'' ees'' d'' ees'' f'' aes' aes' g' f' aes' g' aes' |
- bes' d'' c'' d'' bes' d'' c'' d'' ees'' g' g' f' ees' g' f' g' |
- %%20
- aes' c'' c'' d'' ees'' c'' d'' ees'' f'' d'' ees'' c'' d'' b' c'' a' |
- \tag #'violin { b' d' d' b' } \tag #'reduction { b' g' d'' b' } b' g' b' d'' g'' f'' ees'' d'' c''8 bes' |
- d' ees' r g' aes' f' d'' b' |
- f''2 ~ f''8 d'' b' g' |
- ees'16 c' g' ees' c'' g' g'' d'' g'4 r |
- %%25
- ees''16 g'' f'' g'' ees'' g'' f'' g'' ees'' ees'' d'' ees'' c'' ees'' d'' ees'' |
- g' ees'' d'' ees'' c'' ees'' d'' ees'' \tag #'violin { c''8 aes' } \tag #'reduction { aes'8 f' } f' d' |
- f''2 ~ f''8 d'' b' g' |
- ees'4^\fermata r r2 |
- r4 r8 c' c'' ees''16 d'' c''8 c'' |
- %%30
- c'' c' ees''4 ~ ees''8 d''16 ees'' f''8 aes' |
- aes' g' r g' aes' f' d'' b' |
- f''2 ~ f''8 d'' b' g' |
- c''16 ees'' d'' ees'' c'' ees'' d'' ees'' c'' ees'' d'' ees'' c'' ees'' d'' ees'' |
- d'8 ees'16 f' g'8 b' c''4^\fermata r
-%}
-}
-
-bassi = {
- c4 r8 g c' ees'16 d' c'8 c' |
- c' c r g aes f bes bes, |
- ees ees, r c ees c g ees |
- aes f d' b c' f g g, |
- %%5
- c4 r c'8 c bes bes, |
- aes aes, g g, f ees bes bes, |
- ees4 r r r8 c_\p |
- c' ees'16 d' c'8 bes aes f bes bes, |
- ees ees, r c ees c g ees |
-%{
- %%10
- aes f d' b c' f g g, |
- c4 r r r8 c' |
- c'8. c16 c4 r8 f d ees |
- bes bes, r bes g aes bes g |
- c' c c' bes16 aes g8 ees bes g |
- %%15
- c' c d bes, ees g bes bes, |
- ees4 r r r8 ees' |
- ees'8. ees16 ees4 r r8 c' |
- c'8. c16 c8 c' aes f r f |
- bes bes, bes, bes g ees r ees |
- %%20
- aes aes, g g, f f, r f |
- g g, r4 c'8 g aes g |
- f ees r4 r r8 g, |
- aes, f, d b, aes f d' b |
- c'4 r8 b c' f g g, |
- %%25
- c' g c g, c,4 r |
- c'8 g c c' f4 r8 g, |
- aes, f, d b, aes f d' b |
- c'4 r8 b c' f g g, |
- c4 r8 c_\f c' ees'16 d' c'8 c' |
- %%30
- c' c r g aes f bes bes, |
- ees g ees c f,4 r8 g, |
- aes, f, d b, aes f d' b |
- c' c bes bes, aes aes, g g, |
- f c g g, c4^\fermata r
-%}
-}
-
-global = {
- \key c \minor
- \set Score . tempoWholesPerMinute = #(ly:make-moment (/ 80 4) 1 0 1)
- \time 4/4
-%s1*34 \bar "|."
-}
-
+++ /dev/null
-\version "2.13.6"
-
-#(set-global-staff-size 22.45)
-
-#(define (glissando::calc-extra-dy grob)
- (let* ((original (ly:grob-original grob))
- (left-bound (ly:spanner-bound original LEFT))
- (right-bound (ly:spanner-bound original RIGHT))
- (left-pitch (ly:event-property (event-cause left-bound) 'pitch))
- (right-pitch (ly:event-property (event-cause right-bound) 'pitch)))
-
- (if (and (= (ly:pitch-octave left-pitch) (ly:pitch-octave right-pitch))
- (= (ly:pitch-notename left-pitch) (ly:pitch-notename right-pitch)))
- (- (ly:pitch-alteration right-pitch) (ly:pitch-alteration left-pitch))
- 0 )))
-
-%% Hide fret number: useful to draw slide into/from a casual point of
-%% the fretboard.
-hideFretNumber = { \once \override TabNoteHead #'transparent = ##t
- \once \override NoteHead #'transparent = ##t
- \once \override Stem #'transparent = ##t
- \once \override NoteHead #'no-ledgers = ##t
-}
-
-\paper {
- indent= #0
- line-width= #180
-}
-
-upper= \relative c' {
- \time 4/4
- \key e \major
- \set Staff.midiInstrument = #"acoustic guitar (steel)"
- \set fingeringOrientations = #'(left)
-
- %\override Staff.Glissando #'extra-offset = #' (0.0 . 1.0)
- \partial 4. \acciaccatura c16 \glissando cis8 e4
- < cis-1 g'-3 >2 s8 \grace a16 ( \glissando <b-2>8\3 ) <d-1> ( b ) |
- <e-3>\2 ( <d-1> b ) \grace <ais-2>16 ( \glissando a8 g ) s4. |
- s4. < d'\3 g\2 >8 < gis,\4 d'\3 fis\2 >2\arpeggio ~ |
-
- < gis\4 d'\3 fis\2 >2 < b'\2\harmonic e\harmonic >2\fermata |
-
-}
-
-lower= \relative c {
- \set fingeringOrientations = #'(left)
-
- \partial 4. s4. |
- s4 e,4 s2 |
- s2 s8 <e'-3>4. ~ |
- e4 \hideFretNumber \grace { b8 \glissando s4 } <e-2>4\5 e,2 ~ |
-
- e2 < e'\6\harmonic > |
-}
-
-\score {
- \new StaffGroup <<
- \new Staff = "guitar" <<
- \context Voice = "upper guitar" { \clef "G_8" \voiceOne
- \override Glissando #'gap = #0.5
- \override Glissando #'extra-offset = #'(-0.5 . 0)
- \override Glissando #'springs-and-rods = #ly:spanner::set-spacing-rods
- \override Glissando #'minimum-length = #4
- \override Glissando #'extra-dy = #glissando::calc-extra-dy
- \upper }
- \context Voice = "lower guitar" { \clef "G_8" \voiceTwo
- \override Glissando #'bound-details #'right #'padding = #1
- \override Glissando #'bound-details #'left #'padding = #0.2
- \lower }
- >>
- \new TabStaff = "tab" <<
- \context TabVoice = "upper tab" { \clef "moderntab" \voiceOne \upper }
- \context TabVoice = "lower tab" { \clef "moderntab" \voiceTwo \lower }
- >>
- >>
-
- \midi {
- \context {
- \Score tempoWholesPerMinute = #(ly:make-moment 120 4)
- }
- }
-
- \layout {
- \context {
- \Staff
- \override StringNumber #'transparent = ##t
- }
-
- \context {
- \TabStaff
- \revert Arpeggio #'stencil
- }
- }
-}
\ No newline at end of file
+++ /dev/null
-\version "2.12.0"
-\include "example-header.ily"
-
-#(ly:set-option 'point-and-click #f)
-
-global = {
- \time 4/4
- \numericTimeSignature
- \key c \major
- #(set-global-staff-size 24)
-}
-
-cf = \relative c {
- \clef bass
- \global
- c4 c' b a |
- g a f d |
- e f g g, |
- c1
-}
-
-upper = \relative c'' {
- \global
- r4 s4 s2 |
- s1*2 |
- s2 s4 s
- \bar "||"
-}
-
-bassFigures = \figuremode {
- s1*2 | s4 <6> <6 4> <7> | s1
-}
-
-\markup { "Exercise 3: Write 8th notes against the given bass line." }
-
-\score {
- \new PianoStaff <<
- \new Staff {
- \context Voice = "added voice" \with {
- \consists "Balloon_engraver"
- }
- \upper
- }
-
- \new Staff = lower {
- <<
-% \context Voice = "cantus firmus" \with {
-% \consists "Balloon_engraver"
-% }
- \context Staff = lower \cf
- \new FiguredBass \bassFigures
- >>
- }
- >>
- \layout {}
- %{\midi {
- \context {
- \Score
- tempoWholesPerMinute = #(ly:make-moment 120 4)
- }
- }%}
-}
-
+++ /dev/null
-@c -*- coding: utf-8; mode: texinfo; -*-
-@ignore
- Translation of GIT committish: FILL-IN-HEAD-COMMITTISH
-
- When revising a translation, copy the HEAD committish of the
- version that you are working on. See TRANSLATION for details.
-@end ignore
-
-@node introduction
-@unnumbered Introduction
-
-@divClass{column-center-top}
-@subheading Our Goal
-
-@imageFloat{flat-design,png,right}
-
-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!
-@divEnd
-
-@divClass{column-left-top}
-@subheading Why use LilyPond?
-
-@itemize
-
-@item
-@ref{features}: What can LilyPond do?
-
-@item
-@ref{examples}: I want to see some music!
-
-@item
-@ref{freedom}: LilyPond is Free Software.
-
-@item
-@ref{background}: Our computational aesthetics.
-
-@end itemize
-@divEnd
-
-@divClass{column-right-top}
-@subheading Who uses it?
-
-@itemize
-
-@item
-@ref{productions}: Real-life use of LilyPond.
-
-@item
-@ref{testimonials}: What do people say?
-
-@end itemize
-@divEnd
-
-@divClass{column-center-bottom}
-@subheading Why not use LilyPond?
-
-@itemize
-
-@item
-@ref{text input}: You write music as @emph{text}?!
-
-@item
-@ref{alternate input}: Other ways of working with LilyPond.
-
-@end itemize
-@divEnd
-
-
-@divClass{hide}
-@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.
-@end menu
-@divEnd
-
-
-
-@node features
-@unnumberedsec Features
-
-@help{hoping to delegate this. Desired: an enthusiastic
-attempt to sway people towards trying lilypond. The warnings
-about writing music as text come in Crash Course, not here.}
-
-Maybe draw inspiration from
-@uref{http://lilypond.org/web/about/features} and
-@uref{http://lilypond.org/web/switch/tour} and
-@uref{http://lilypond.org/web/switch/advantages}
-
-
-
-@subheading Why switch to LilyPond?
-
-
-@subsubheading Excellent classical engraving
-
-@imageFloat{flat-design,png,right}
-
-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 @ref{essay}.
-
-
-@subsubheading 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!
-
-
-@subsubheading 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.
-
-
-@subsubheading 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.
-
-
-@subsubheading Mix music and text
-
-@imageFloat{lilypond-book,png,right}
-
-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.
-
-
-
-@subsubheading 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 @qq{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.
-
-
-@subsubheading 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.
-
-
-@subsubheading 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.
-
-
-
-@divClass{column-center-bottom}
-@subheading Where now?
-
-Still not convinced? Look at some neat @ref{examples}. If you've
-already decided to try LilyPond, first read about our
-@ref{text input}.
-@divEnd
-
-
-
-@node examples
-@unnumberedsec Examples
-
-Lilypond is a powerful and flexible tool for engraving tasks of
-all kinds. Please browse our gallery of examples and be inspired!
-
-@ignore
-Here is a passage from Franz Liszt's solo piano transcription
-of the Overture to Wagner's @emph{Tannhäuser}. The spacing
-in this example was all performed by Lilypond's formatting
-algorithms, without tweaks of any kind. It
-handles cross-staff beaming gracefully and puts the system brace
-perfectly around all three staves.
-
-@exampleImage{liszt-wagner}
-@end ignore
-
-@newsItem
-@subsubheading Classical Music
-
-This organ work by J.S. Bach is a fairly typical engraving project
-in Lilypond.
-
-@exampleImage{bach-bwv610}
-@newsEnd
-
-@newsItem
-@subsubheading Complex Notation
-
-This example from @emph{Goyescas} by Enrique Granados shows some
-of the more advanced features of typesetting, including kneed
-beams, cross-staff stems, and voice-follow lines.
-
-@exampleImage{granados}
-@newsEnd
-
-@newsItem
-@subsubheading Early Music
-
-Lilypond also supports various types of ancient notation, such
-as this passage of Gregorian chant.
-
-@exampleImage{ancient-headword}
-@newsEnd
-
-@newsItem
-@subsubheading Modern Music
-
-Contemporary composers find Lilypond well-suited to displaying
-unusual notation. Here is an excerpt from Trevor Baca's
-@emph{Cáry}, for unaccompanied bass flute.
-
-@exampleImage{cary}
-@newsEnd
-
-
-@newsItem
-@subsubheading Efficient, flexible creation of performance materials
-
-Various performance materials can be created from the same source
-code. This is an excerpt of @uref{http://nicolas.sceaux.free.fr/,
-Nicolas Sceaux's} engraving of Handel's @emph{Giulio Cesare}, in
-full score, piano-vocal reduction, and a violin part.
-
-@exampleImage{sesto-full}
-
-@exampleImage{sesto-piano}
-
-@exampleImage{sesto-violin}
-
-@newsEnd
-
-@newsItem
-@subsubheading 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.
-
-@exampleImage{tab-example}
-@newsEnd
-
-@newsItem
-@subsubheading Schenker Graphs
-
-Standard output can be modified heavily. Here someone has created
-an impressive Schenkerian analysis.
-
-@exampleImage{bach-schenker}
-@newsEnd
-
-@newsItem
-@subsubheading 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.
-
-@exampleImage{aucun-snippet}
-@newsEnd
-
-@newsItem
-@subsubheading Educational Applications
-
-Lilypond is perfectly suited for educational purposes as well.
-Here is an example of a simple counterpoint exercise.
-
-@exampleImage{theory}
-@newsEnd
-
-@newsItem
-@subsubheading 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.
-
-@exampleImage{chart}
-@newsEnd
-
-@newsItem
-@subsubheading 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.
-
-@exampleImage{orchestra}
-@newsEnd
-
-
-@divClass{column-center-bottom}
-@subheading Where now?
-
-Still not convinced? LilyPond is Free software, granting you
-@ref{freedom}. If you've already decided to try LilyPond, first
-read about our @ref{text input}.
-@divEnd
-
-
-@node freedom
-@unnumberedsec Freedom
-
-@divClass{column-center-top}
-@subheading Free Software
-
-@uref{http://www.gnu.org/, GNU} LilyPond is written and maintained
-by a community of enthusiasts. It is published under the
-@ref{GPL, GNU General Public License} and the @ref{FDL, GNU Free
-Documentation License}, giving everybody the freedom to fix,
-modify, and extend the program. Creating beautiful music should
-not require hundreds of dollars of software!
-@divEnd
-
-
-@c @divClass{column-left-top}
-@divClass{color2}
-@divClass{keep-bullets}
-@subheading What are the benefits to users?
-
-@itemize
-
-@item
-No cost: download and try it out! What do you have to lose?
-
-@item
-Sharing: if you like the program, give a copy to your friends,
-teachers, students, and colleagues!
-
-@item
-Source available: if you are curious about how LilyPond creates
-some notation, you can see exactly how it is done.
-
-@item
-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.
-
-@item
-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.
-
-
-@end itemize
-
-@divEnd
-@divEnd
-
-
-@c @divClass{column-right-top}
-@divClass{color3}
-@divClass{keep-bullets}
-@subheading Why do LilyPond developers @qq{give away} their work for free?
-
-Most of us view LilyPond development as a hobby or volunteer work.
-So this question is really asking @qq{why do people volunteer}?
-
-@itemize
-
-@item
-Fun: working towards a goal can be enjoyable, especially when you
-work as a team!
-
-@item
-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.
-
-@item
-@qq{Gift culture}: the Free Software (or @qq{Open Source})
-movement has created many great software projects, such as
-@uref{http://kernel.org/, GNU/Linux},
-@uref{http://www.getfirefox.com/, Mozilla Firefox}, and
-@uref{http://www.wesnoth.org/, Battle for Wesnoth}. Having
-benefitted from these projects, some developers want to @qq{give
-back} to the community.
-
-@item
-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.
-
-
-@end itemize
-
-@divEnd
-@divEnd
-
-
-@divClass{column-center-bottom}
-@subheading Where now?
-
-Still not convinced? Read our extensive essay about our engraving
-philosophy in @ref{background}. If you've already decided to try
-LilyPond, first read about our @ref{text input}.
-@divEnd
-
-
-@node background
-@unnumberedsec Background
-
-@divClass{column-center-top}
-@subheading 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 @ref{essay}.
-@divEnd
-
-@divClass{column-center-bottom}
-@subheading Where now?
-
-Still not convinced? Read about some of our users'
-@ref{productions} and sheet music. If you've already decided to
-try LilyPond, first read about our @ref{text input}.
-@divEnd
-
-
-@node productions
-@unnumberedsec Productions
-
-@divClass{column-left-top}
-@subheading Concerts
-
-Lilypond engravings have been used for performances around the world.
-Some highlights:
-
-@divClass{keep-bullets}
-@itemize
-
-@item
-@emph{Affaire Étrangère}, an opera by Valentin Villenave, with
-libretto by Lewis Trondheim, premiered February 1, 2009, by
-@uref{http://www.orchestre-montpellier.com/, L'Opéra Montpellier}.
-
-@item
-@uref{http://www.mercurybaroque.org/02/02109.aspx, Mercury Baroque}'s
-performance of Lully's @emph{Armide}, May 15-16, 2009, in Houston,
-Texas (engraving by @uref{http://nicolas.sceaux.free.fr/,
-Nicolas Sceaux}).
-
-@item
-Instrumental excerpts from Rameau's @emph{Hippolyte et Aricie} at
-St. James's Church in Manhattan, May 8, 2009, by Frederick Renz
-and his ensemble @uref{http://www.earlymusicny.org/, Early Music
-New York} (engraving by Nicolas Sceaux).
-
-@end itemize
-@divEnd
-
-@divEnd
-
-
-@divClass{column-right-top}
-@subheading Published sheet music
-
-@divClass{keep-bullets}
-@itemize
-
-@item
-@uref{http://www.mutopiaproject.org/index.html, Mutopia Project},
-over 1500 pieces of classical sheet music for free download, and
-the main showcase of LilyPond scores.
-
-@item
-@uref{http://www.adoromusicpub.com/, Adoro Music Publishing},
-high-quality scores of sacred music, available for immediate
-download or in traditional paper format.
-
-@item
-@uref{http://theshadylanepublishing.com/, The Shady Lane
-Publishing},
-a @qq{micro musical publishing house} whose goal is to promote a
-new form of musical economy closer to the musicians and music
-lovers.
-
-@end itemize
-
-@divEnd
-
-@divEnd
-
-
-@divClass{column-center-bottom}
-@subheading Where now?
-
-Still not convinced? Read some of our users' @ref{testimonials}.
-If you've already decided to try LilyPond, first read about our
-@ref{text input}.
-@divEnd
-
-
-@node testimonials
-@unnumberedsec Testimonials
-
-@divClass{testimonial-item}
-@imageFloat{carter-brey,jpg, right}
-@subsubheading @uref{http://nyphil.org/meet/orchestra/index.cfm?page=profile&personNum=7, Carter Brey}, Principal Cellist, New York Philharmonic
-
-@qq{... 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!}
-@divEnd
-
-
-@divClass{testimonial-item}
-@imageFloat{orm-finnendahl,jpg, left}
-@subsubheading @uref{http://icem-www.folkwang-hochschule.de/~finnendahl/, Orm Finnendahl}, professor of Composition, Musikhochschule Freiburg
-
-@qq{Although I don't know [LilyPond] very well yet, I'm
-@strong{*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!} @divEnd
-
-
-@divClass{testimonial-item}
-@imageFloat{darius-blasband,jpg, right}
-@subsubheading Darius Blasband, composer (Brussels, Belgium)
-
-@qq{[..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.}
-
-@divEnd
-
-
-@divClass{testimonial-item}
-@subsubheading Kieren MacMillan, composer (Toronto, Canada)
-
-@qq{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 @q{professional} publications I've compared
-it to (q.v., just about any Warner Bros. score, and even many of
-the most recent by @q{the old houses}). [..]}
-
-@qq{Beat that, Finale/Sibelius/Igor/whatever!!!}
-@divEnd
-
-
-@divClass{testimonial-item}
-@subsubheading Chris Cannam, lead programmer of the @uref{http://www.rosegardenmusic.com/, RoseGarden} project.
-
-@qq{Lilypond is obviously the zillion-ton gorilla [of great music
-typesetting].}
-@divEnd
-
-
-@divClass{testimonial-item}
-@subsubheading Chris Snyder, @uref{http://www.adoromusicpub.com/, Adoro Music Publishing}
-
-@qq{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.}
-
-@qq{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.}
-@divEnd
-
-
-@divClass{testimonial-item}
-@subsubheading David Bobroff, Bass Trombone, Iceland Symphony Orchestra
-
-@qq{I think Lilypond is great [..] The more I learn about LilyPond
-the more I like it!}
-@divEnd
-
-
-@divClass{testimonial-item}
-@subsubheading Vaylor Trucks, Electric guitar player (Yes, @uref{http://www.allmanbrothersband.com/modules.php?op=modload&name=userpage&file=content&page_id=12, related to})
-
-@qq{I am super impressed with LilyPond [..]}
-
-@qq{THIS IS THE BEST PROGRAM EVER!!!}
-
-@qq{Thank you all SO MUCH for your hard work and dedication!}
-@divEnd
-
-
-@divClass{testimonial-item}
-@subsubheading @uref{http://nicolas.sceaux.free.fr/, Nicolas Sceaux}, @uref{http://www.mutopiaproject.org/, Mutopia} contributor
-
-@qq{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.}
-@divEnd
-
-
-@divClass{testimonial-item}
-@subsubheading @uref{http://www.troff.org/whoswho.html#werner, Werner Lemberg}, Conductor at the Theatre in Koblenz, Germany and distinguished GNU Hacker.
-
-@qq{Anyway, LilyPond does an amazingly good job!}
-@divEnd
-
-
-@divClass{testimonial-item}
-@subsubheading Paul Davis, developer of @uref{http://jackaudio.org/, JACK} and @uref{http://www.ardour.org/, Ardour}.
-
-@qq{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.}
-@divEnd
-
-
-@divClass{column-center-bottom}
-@subheading Where now?
-
-Read about our @ref{text input}.
-@divEnd
-
-
-
-@node text input
-@unnumberedsec Text input
-
-@c TRANSLATORS: so far it's mostly from
-@c http://lilypond.org/web/switch/howto
-
-@subheading @qq{Compiling} Music
-
-@imageClickable{nereid-shot-small,png, (click to enlarge), nereid-shot,png, right}
-
-LilyPond is a @emph{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 @qq{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!
-
-@warning{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.}
-
-
-@subsubheading It's as simple as A B C
-
-Notes are encoded with letters and numbers. Special commands are
-entered with backslashes.
-
-@imageFloat{text-input-1-annotate,png,center}
-@imageFloat{text-input-1-output,png,center}
-
-Alterations are made with different names: add @code{-is} for
-sharp, and @code{-es} for flat (these are Dutch note names, other
-languages are available). LilyPond figures out where to put
-accidentals.
-
-@imageFloat{text-input-2-annotate,png,center}
-@imageFloat{text-input-2-output,png,center}
-
-
-@subsubheading Pop music
-
-Put chords and lyrics together to get a lead sheet:
-
-@imageFloat{text-input-pop-annotate,png,center}
-@imageFloat{text-input-pop-output,png,center}
-
-
-
-@subsubheading 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:
-
-@imageFloat{text-input-parts-both-annotate,png,center}
-
-
-This variable is then used in a single part (here transposed, with
-condensed multi rests):
-
-@imageFloat{text-input-parts-single-annotate,png,center}
-@imageFloat{text-input-parts-single-output,png,center}
-
-
-The same variable is used in the full score (here in concert
-pitch):
-
-@imageFloat{text-input-score-annotate,png,center}
-@imageFloat{text-input-score-output,png,center}
-
-
-@subsubheading 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 @ref{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.
-
-@help{any suggestions for a picture here?}
-
-
-@subsubheading 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 @ref{alternate input}.
-
-
-@divClass{column-center-bottom}
-@subheading Where now?
-
-You are now ready to @ref{download, Download LilyPond}. Still not
-convinced? Read about easier editing environments in
-@ref{alternate input}.
-
-@divEnd
-
-
-@node alternate input
-@unnumberedsec Alternate input
-
-@divClass{column-center-top}
-@subheading Graphical environment: Denemo
-
-@imageClickable{screenshot-denemo-small,png,
- (click to enlarge),screenshot-denemo,png,right}
-
-@sourceimage{logo-linux,,,}
-@sourceimage{logo-windows,,,}
-
-@uref{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.
-
-@ignore
-Import: LilyPond, MIDI
-
-Export: Lilypond, MIDI, ABC, CSound Score File, PDF
-@end ignore
-
-@divEnd
-
-@divClass{column-center-top}
-@subheading Mixed environment: LilyPondTool
-
-@imageClickable{lilypondtool-2.12-screenshot-400wide,png,
- (click to enlarge),lilypondtool-2.12-screenshot,png,right}
-
-@sourceimage{logo-linux,,,}
-@sourceimage{logo-freebsd,,,}
-@sourceimage{logo-macosx,,,}
-@sourceimage{logo-windows,,,}
-
-@uref{http://lilypondtool@/.organum@/.hu}
-
-Created as a plugin for the
-@uref{http://@/www@/.jedit@/.org@/,jEdit} 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.
-
-@divEnd
-
-@divClass{column-center-top}
-@subheading Text environment: Emacs and Vim
-
-@sourceimage{logo-linux,,,}
-@sourceimage{logo-freebsd,,,}
-@sourceimage{logo-macosx,,,}
-@sourceimage{logo-windows,,,}
-
-@uref{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 @q{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
-@command{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.
-
-@divEnd
-
-@divClass{column-center-top}
-@subheading Other
-
-@help insert text and a graphic(s)
-
-@subsubheading Mixed environment: Frescobaldi
-
-@imageClickable{frescobaldi-lilypond-editor-small,png,
- (click to enlarge),frescobaldi-lilypond-editor,png,right}
-
-@sourceimage{logo-linux,,,}
-@sourceimage{logo-freebsd,,,}
-
-@uref{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.
-
-
-@subsubheading Text environment: TexShop
-
-@sourceimage{logo-macosx,,,}
-
-@uref{http://@/www@/.uoregon@/.edu/~koch/texshop}
-
-The
-@uref{http://@/www@/.uoregon@/.edu/~koch/texshop/index@/.html,TexShop}
-editor for MacOS@tie{}X can be extended to run LilyPond,
-@command{lilypond-book} and @command{convert-ly} from within the editor,
-using the extensions available at
-@uref{http://@/www@/.dimi@/.uniud@/.it/vitacolo/freesoftware@/.html#desktoppub}.
-
-
-@ignore
-TODO: ask somebody to sponsor/check these. -gp
-
-@subsubheading TextMate
-
-@sourceimage{logo-macosx,,,}
-
-There is a LilyPond bundle for TextMate. It may be installed by
-running:
-
-@example
-mkdir -p /Library/Application\ Support/TextMate/Bundles
-cd /Library/Application\ Support/TextMate/Bundles
-svn co http://macromates.com/svn/Bundles/trunk/Bundles/Lilypond.tmbundle/
-@end example
-@end ignore
-
-@subsubheading Mixed environment: LilyKDE
-
-@sourceimage{logo-linux,,,}
-@sourceimage{logo-freebsd,,,}
-
-@uref{http://lilykde.googlecode.com/}
-
-@uref{http://lilykde.googlecode.com/,LilyKDE} is a plugin for
-KDE's text editor @uref{http://kate-editor.org/,Kate}. It has a
-powerful Score Wizard to quickly setup a LilyPond document and an
-embedded PDF viewer.
-
-LilyKDE can use @uref{http://www.volny.cz/smilauer/rumor/,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.
-
-
-@help clean up this list, check links, etc.
-
-Other programs can export LilyPond code:
-
-@itemize
-@item
-@uref{http://www@/.volny@/.cz/smilauer/rumor/rumor@/.html,Rumor}, a realtime
-monophonic MIDI to LilyPond converter.
-@item
-@uref{http://nicolas@/.sceaux@/.free@/.fr/lilypond/lyqi@/.html,lyqi}, an
-Emacs major mode.
-@item
-@uref{http://@/www@/.nongnu@/.org/@/xml2ly/,xml2ly}, which imports
-@uref{http://@/www@/.musicxml@/.com/xml@/.html,MusicXML}
-@item
-@uref{http://@/noteedit@/.berlios@/.de,NoteEdit}
-which imports @uref{http://@/www@/.musicxml@/.com/xml@/.html,MusicXML}
-@item
-@uref{http://@/www@/.rosegardenmusic@/.com,Rosegarden},
-which imports MIDI
-@item
-@uref{http://@/common-lisp@/.net/project/fomus/,FOMUS},
-a LISP library to generate music notation
-@item
-@uref{http://vsr.informatik.tu-chemnitz.de/staff/jan/nted/nted.xhtml},
-has experimental export for LilyPond.
-@item
-@uref{http://www.tuxguitar.com.ar/}, can export to LilyPond.
-@item
-@uref{http://musescore.org} can also export to LilyPond.
-@end itemize
-@divEnd
-
-
-@divClass{column-center-bottom}
-@subheading Where now?
-
-You are now ready to @ref{download, Download LilyPond}.
-
-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 @ref{features}, @ref{examples}, or the
-@ref{freedom} that LilyPond provides, or read about users'
-@ref{productions} and @ref{testimonials}. In addition, our
-approach to the computational aesthetics of classical engraving is
-explained in our @ref{background}.
-
-
-@subheading Legalese
-
-@divClass{legal}
-All logos and product images are copyright and trademark
-acknowledged.
-
-@logoLegalLinux
-
-@logoLegalFreeBSD
-
-@logoLegalMacOSX
-
-@logoLegalWindows
-
-@divEnd
-
-@divEnd
-
-
-
-
+++ /dev/null
-@c -*- coding: utf-8; mode: texinfo; -*-
-@ignore
- Translation of GIT committish: FILL-IN-HEAD-COMMITTISH
-
- When revising a translation, copy the HEAD committish of the
- version that you are working on. See TRANSLATION for details.
-@end ignore
-
-@node manuals
-@unnumbered Manuals
-
-@divClass{heading-center}
-@heading Documentation for LilyPond @version
-
-@divEnd
-
-@c TODO: do we want these links to be in larger text / bold ? CSS.
-
-@c if you change this page, also change All.
-@divClass{column-center-top}
-@subheading Introduction
-
-@itemize
-
-@item @ref{text input}:
-LilyPond is a @strong{text-based} music engraver. If you are not
-familiar with this concept, please read this now!
-
-@item @ref{learning}:
-a @qq{must-read} gentle introduction to LilyPond.
-
-@item @ref{glossary}:
-@emph{(optional reading)}
-explains musical terms and gives translations for users unfamiliar
-with English musical terms.
-
-@item @ref{essay}:
-@emph{(optional reading)}
-background information about the engraving process and the
-aesthetics of 19th century music engraving.
-
-
-@end itemize
-
-@divEnd
-
-@divClass{column-left-top}
-@subheading Regular use
-
-@itemize
-
-@item @ref{notation}:
-the main portion of the documentation; provides detailed
-information about creating notation.
-
-@item @ref{usage}:
-discusses the actual programs and operating system-specific
-issues.
-
-@item @ref{snippets}:
-short tricks, tips, and examples.
-
-@end itemize
-
-@divEnd
-
-
-@divClass{column-right-top}
-@subheading Infrequent Use
-
-@itemize
-
-@item @ref{FAQ}:
-links to the answers of Frequently Asked Questions.
-
-@item @ref{changes}:
-updates since the last major version.
-
-@item @ref{extend}:
-programming fancy tweaks in LilyPond.
-
-@item @ref{internals}:
-information about LilyPond's internal structures, which is
-required for constructing tweaks.
-
-@end itemize
-
-@divEnd
-
-
-@divClass{column-center-bottom}
-@subheading Other material
-
-@itemize
-
-@item @ref{translated}:
-translation status for non-English readers.
-
-@item @ref{all}:
-quick links, downloadable manuals, and old manuals.
-
-@item @ref{development}:
-manuals for the unstable version.
-
-@item @ref{FDL}:
-these manuals are published under the GNU Free Documentation
-License.
-
-@end itemize
-
-@divEnd
-
-
-@divClass{hide}
-@menu
-* learning:: Learning.
-* glossary:: Glossary.
-* essay:: Essay.
-* notation:: Reference.
-* usage:: Usage.
-* snippets:: Snippets.
-* FAQ:: FAQ.
-* changes:: NEWS.
-* extend:: Programming.
-* internals:: Internals.
-* translated:: Translation.
-* all:: All manuals.
-* FDL:: Licence.
-@end menu
-
-@divEnd
-
-
-@c TRANSLATORS: most of the text in this file came from
-@c LM 1.1 About the documentation (before this section was
-@c removed in July 2009).
-
-@node learning
-@unnumberedsec Learning
-
-@divClass{column-left-top}
-@subheading 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 @strong{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.
-@divEnd
-
-@divClass{column-right-bottom}
-@subheading Read it
-
-@itemize
-
-@item @rlearningnamed{Top,Learning}:
-read this manual in the same format as this one.
-
-@end itemize
-
-@subheading All formats
-
-@divClass{keep-bullets}
-@itemize
-
-@item @uref{../learning/index.html, Learning (split HTML)}:
-the manual is split between many HTML pages.
-@emph{(small download for each page)}
-
-@item @uref{../learning-big-page.html, Learning (big HTML)}:
-read this manual as one huge HTML page.
-@emph{(large single download, around 10? Mb)}
-
-@item @uref{../learning.pdf, learning.pdf}:
-download as a PDF file.
-@emph{(large single download, 2.8 Mb)}
-
-@c TODO: should make links to info?
-@c @item @uref{../TODO, learning.info}:
-@c GNU info format for documentation. link broken.
-
-@end itemize
-@divEnd
-@divEnd
-
-
-@node glossary
-@unnumberedsec Glossary
-
-@divClass{column-left-top}
-@subheading 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.
-
-@divEnd
-
-@divClass{column-right-bottom}
-@subheading Read it
-
-@itemize
-
-@item @rglosnamed{Top,Music glossary}:
-read this manual in the same format as this one.
-
-@end itemize
-
-@subheading All formats
-
-@divClass{keep-bullets}
-@itemize
-
-@item @uref{../music-glossary/index.html, Glossary (split HTML)}:
-the manual is split between many HTML pages.
-@emph{(small download for each page)}
-
-@item @uref{../music-glossary-big-page.html, Glossay (big HTML)}:
-read this manual as one huge HTML page.
-@emph{(large single download, around 10? Mb)}
-
-@item @uref{../music-glossary.pdf, glossary.pdf}:
-download as a PDF file.
-@emph{(large single download, 2.8 Mb)}
-
-@c @item @uref{../TODO, glossary.info}:
-@c GNU info format for documentation. TODO, link broken.
-
-@end itemize
-@divEnd
-@divEnd
-
-
-@node essay
-@unnumberedsec Essay
-
-@divClass{column-left-top}
-@subheading 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.
-
-@warning{The detailed typographical examples are easier to analyze
-in the PDF version due to its higher resolution.}
-
-@divEnd
-
-@divClass{column-right-bottom}
-@subheading Read it
-
-@itemize
-
-@item @ressaynamed{Top,Essay}:
-read this manual in the same format as this one.
-
-@end itemize
-
-@subheading All formats
-
-@divClass{keep-bullets}
-@itemize
-
-@item @uref{../essay/index.html, Essay (split HTML)}:
-the manual is split between many HTML pages.
-@emph{(small download for each page)}
-
-@item @uref{../essay-big-page.html, Essay (big HTML)}:
-read this manual as one huge HTML page.
-@emph{(large single download, around ?? Mb)}
-
-@item @uref{../essay.pdf, essay.pdf}:
-download as a PDF file.
-@emph{(large single download, ?? Mb)}
-
-@c @item @uref{../TODO, essay.info}:
-@c GNU info format for documentation. TODO, link broken.
-
-@end itemize
-@divEnd
-@divEnd
-
-
-@node notation
-@unnumberedsec Notation
-
-@divClass{column-left-top}
-@subheading Notation reference
-
-This book explains all the LilyPond commands which produce
-notation.
-
-@warning{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.}
-
-@divEnd
-
-@divClass{column-right-bottom}
-@subheading Read it
-
-@itemize
-
-@item @rusernamed{Top,Notation}:
-read this manual in the same format as this one.
-
-@end itemize
-
-@subheading All formats
-
-@divClass{keep-bullets}
-@itemize
-
-@item @uref{../notation/index.html, Notation (split HTML)}:
-the manual is split between many HTML pages.
-@emph{(small download for each page)}
-
-@item @uref{../notation-big-page.html, Notation (big HTML)}:
-read this manual as one huge HTML page.
-@emph{(large single download, around 10? Mb)}
-
-@item @uref{../notation.pdf, notation.pdf}:
-download as a PDF file.
-@emph{(large single download, 2.8 Mb)}
-
-@c @item @uref{../TODO, notation.info}:
-@c GNU info format for documentation. TODO, link broken.
-
-@end itemize
-@divEnd
-@divEnd
-
-
-@node usage
-@unnumberedsec Usage
-
-@divClass{column-left-top}
-@subheading Usage manual
-
-This book explains how to execute the programs, how to integrate
-LilyPond notation with other programs, and suggests @qq{best
-practices} for efficient use. It is recommended reading before
-attempting any large projects.
-@divEnd
-
-@divClass{column-right-bottom}
-@subheading Read it
-
-@itemize
-
-@item @rprogramnamed{Top,Usage}:
-read this manual in the same format as this one.
-
-@end itemize
-
-@subheading All formats
-
-@divClass{keep-bullets}
-@itemize
-
-@item @uref{../usage/index.html, Usage (split HTML)}:
-the manual is split between many HTML pages.
-@emph{(small download for each page)}
-
-@item @uref{../usage-big-page.html, Usage (big HTML)}:
-read this manual as one huge HTML page.
-@emph{(large single download, around 10? Mb)}
-
-@item @uref{../usage.pdf, usage.pdf}:
-download as a PDF file.
-@emph{(large single download, 2.8 Mb)}
-
-@c @item @uref{../TODO, lilypond-usage.info}:
-@c GNU info format for documentation. TODO, link broken.
-
-@end itemize
-@divEnd
-@divEnd
-
-
-@node snippets
-@unnumberedsec Snippets
-
-@divClass{column-left-top}
-@subheading Snippets
-
-This shows a selected set of LilyPond snippets from the
-@uref{http://lsr@/.dsi@/.unimi@/.it,LilyPond Snippet Repository}
-(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 @file{input/new/} in the LilyPond
-source tree.
-
-The list of snippets for each subsection of the Notation are also
-linked from the @strong{See also} portion.
-@divEnd
-
-@divClass{column-right-bottom}
-@subheading Read it
-
-@itemize
-
-@item @rlsrnamed{Top,Snippets}:
-read this manual in the same format as this one.
-
-@end itemize
-
-@subheading All formats
-
-@divClass{keep-bullets}
-@itemize
-
-@item @uref{../snippets/index.html, Snippets (split HTML)}:
-the manual is split between many HTML pages.
-@emph{(small download for each page)}
-
-@item @uref{../snippets-big-page.html, Snippets (big HTML)}:
-read this manual as one huge HTML page.
-@emph{(large single download, around 10? Mb)}
-
-@item @uref{../snippets.pdf, snippets.pdf}:
-download as a PDF file.
-@emph{(large single download, 2.8 Mb)}
-
-@c @item @uref{../TODO, snippets.info}:
-@c GNU info format for documentation. TODO, link broken.
-
-@end itemize
-@divEnd
-@divEnd
-
-
-@node FAQ
-@unnumberedsec FAQ
-
-@divClass{column-center-top}
-@subheading Introductory questions
-
-@subsubheading Where are the graphical canvas, menus, and toolbars?
-
-LilyPond requires you to write music as text. Please read about
-our @ref{text input}.
-
-
-@subsubheading There's a lot of documentation! Do I need to read it?
-
-You need to read the @ref{learning, Learning manual}. As for the
-rest of documentation, you only need to read the sections which
-discuss the notation that you wish to create.
-
-
-@subsubheading 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 @ref{introduction}.
-
-@divEnd
-
-@divClass{column-center-bottom}
-@subheading Usage questions
-
-@subsubheading Something isn't working! How do I fix it?
-
-This is explained in @rprogram{Troubleshooting}.
-
-
-@subsubheading Why do you change the syntax?
-
-This is explained in @rprogram{Why does the syntax change?}.
-
-@divEnd
-
-
-@node changes
-@unnumberedsec Changes
-
-@divClass{column-left-top}
-@subheading Changes
-
-This is a summary of important changes and new features in
-LilyPond since the previous stable version.
-
-@divEnd
-
-@divClass{column-right-bottom}
-@subheading Read it
-
-@itemize
-
-@item @rchangesnamed{Top,Changes}:
-read this manual in the same format as this one.
-
-@end itemize
-
-@subheading All formats
-
-@divClass{keep-bullets}
-@itemize
-
-@item @uref{../changes/index.html, Changes (split HTML)}:
-the manual is split between many HTML pages.
-@emph{(small download for each page)}
-
-@item @uref{../changes-big-page.html, Changes (big HTML)}:
-read this manual as one huge HTML page.
-@emph{(large single download, around 10? Mb)}
-
-@item @uref{../changes.pdf, changes.pdf}:
-download as a PDF file.
-@emph{(small single download, 0.5 ?? Mb)}
-
-@c @item @uref{../TODO, changes.info}:
-@c GNU info format for documentation. TODO, link broken.
-
-@end itemize
-@divEnd
-@divEnd
-
-
-@node extend
-@unnumberedsec Extend
-
-@divClass{column-left-top}
-@subheading Extend LilyPond
-
-This manual explains how to write extensions to LilyPond.
-
-@divEnd
-
-@divClass{column-right-bottom}
-@subheading Read it
-
-@itemize
-
-@item @rextendnamed{Top,Extend}:
-read this manual in the same format as this one.
-
-@end itemize
-
-@subheading All formats
-
-@divClass{keep-bullets}
-@itemize
-
-@item @uref{../extending/index.html, Extend (split HTML)}:
-the manual is split between many HTML pages.
-@emph{(small download for each page)}
-
-@item @uref{../extending-big-page.html, Extend (big HTML)}:
-read this manual as one huge HTML page.
-@emph{(large single download, around 10? Mb)}
-
-@item @uref{../extending.pdf, extending.pdf}:
-download as a PDF file.
-@emph{(large single download, 2.8 Mb)}
-
-@c @item @uref{../TODO, extending.info}:
-@c GNU info format for documentation. TODO, link broken.
-
-@end itemize
-@divEnd
-@divEnd
-
-
-@node internals
-@unnumberedsec Internals
-
-@divClass{column-left-top}
-@subheading 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 @b{See also} subsection, which refers to the
-generated documentation. In the HTML document, these subsections
-have clickable links.
-
-@divEnd
-
-@divClass{column-right-bottom}
-@subheading Read it
-
-@itemize
-
-@item @rinternalsnamed{Top,Internals}:
-read this manual in the same format as this one.
-
-@end itemize
-
-@subheading All formats
-
-@divClass{keep-bullets}
-@itemize
-
-@item @uref{../internals/index.html, Internals (split HTML)}:
-the manual is split between many HTML pages.
-@emph{(small download for each page)}
-
-@item @uref{../internals-big-page.html, Internals (big HTML)}:
-read this manual as one huge HTML page.
-@emph{(large single download, around 10? Mb)}
-
-@item @uref{../internals.pdf, internals.pdf}:
-download as a PDF file.
-@emph{(large single download, 2.8 Mb)}
-
-@c @item @uref{../TODO, internals.info}:
-@c GNU info format for documentation. TODO, link broken.
-
-@end itemize
-@divEnd
-@divEnd
-
-
-
-@node translated
-@unnumberedsec Translated
-
-@divClass{column-center-bottom}
-@subheading Translation status
-
-TODO: clean up / prettify
-
-@uref{../translations.html}.
-
-@divEnd
-
-
-@node all
-@unnumberedsec All
-
-@divClass{heading-center}
-@heading Documentation quick links
-
-Links to other formats of these manuals can be found in
-@ref{manuals}.
-
-@divEnd
-
-@c this should match the (main) manual page.
-@divClass{column-center-top}
-@subheading Introduction
-
-@itemize
-
-@item @rlearningnamed{Top,Learning}:
-a @qq{must-read} gentle introduction to LilyPond.
-
-@item @rglosnamed{Top,Glossary}:
-@emph{(optional reading)}
-explains musical terms and gives translations for users unfamiliar
-with English musical terms.
-
-@item @ressaynamed{Top,Essay}:
-@emph{(optional reading)}
-background information about the engraving process and the
-aesthetics of 19th century music engraving.
-
-@end itemize
-
-@divEnd
-
-@divClass{column-left-top}
-@subheading Regular use
-
-@itemize
-
-@item @rusernamed{Top,Notation}:
-the main portion of the documentation; provides detailed
-information about creating notation.
-
-@item @rprogramnamed{Top,Usage}:
-discusses the actual programs and operation system-specific
-issues.
-
-@item @rlsrnamed{Top,Snippets}:
-short tricks, tips, and examples.
-
-@end itemize
-
-@divEnd
-
-
-@divClass{column-right-top}
-@subheading Infrequent Use
-
-@itemize
-
-@item @ref{FAQ}:
-links to answers of Frequently Asked Questions.
-
-@item @rchangesnamed{Top,Changes}:
-updates since the last major version.
-
-@item @rextendnamed{Top,Extend}:
-programming fancy tweaks in LilyPond.
-
-@item @rinternalsnamed{Top,Internals}:
-information about LilyPond's internal structures, which is
-required for constructing tweaks.
-
-@end itemize
-
-@divEnd
-
-
-@divClass{column-center-bottom}
-@subheading Downloadable versions
-
-@help{compare tarball vs. zip size, ask about windows users
-dealing with tarballs (both gz and bz2), etc.}
-
-@help{on second thought, wait until the new doc build. write an
-apology here for no tarballs}
-
-@divClass{keep-bullets}
-@itemize
-
-@item html-split zip
-
-@item html-big zip
-
-@item pdf zip
-
-@item info zip maybe?!?!
-
-@end itemize
-
-@divEnd
-
-@subheading Previous stable versions
-
-@divClass{keep-bullets}
-@itemize
-
-@item @uref{http://lilypond.org/doc/v2.12/Documentation/,
-LilyPond 2.12 Documentation}
-
-@item @uref{http://lilypond.org/doc/v2.10/Documentation/,
-LilyPond 2.10 Documentation}
-
-@item @uref{http://lilypond.org/doc/v2.8/Documentation/,
-LilyPond 2.8 Documentation}
-
-@help anybody want to write this stuff?
-
-@end itemize
-
-@divEnd
-@divEnd
-
-
-@node FDL
-@unnumberedsec FDL
-
-@divClass{column-center-top}
-@subheading 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 @ref{freedom}.
-
-@divEnd
-
-@divClass{column-center-bottom}
-@subheading GNU Free Documentation License 1.1
-
-@include fdl.itexi
-
-@divEnd
-
-
+++ /dev/null
-@c -*- coding: utf-8; mode: texinfo; -*-
-@c This file is part of lilypond-general.texi and community.itexi
-
-@c when you add a new item, consider moving the lowest item(s)
-@c into news-old.itexi.
-
-@newsItem
-@subsubheading New Website! @emph{October 3, 2009}
-
-As you can see, we have a new website design. Many thanks to
-texi2html and CSS for being so flexible!
-
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond Report #16. @emph{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 @uref{http://news.lilynet.net/The-LilyPond-Report-16, issue 16}
-now!
-
-@newsEnd
-
-
+++ /dev/null
-@c -*- coding: utf-8; mode: texinfo; -*-
-
-@ignore
-
-(I'd rather have the below in the CG. -gp)
-NOTE:
-
- * avoid "HERE" as name for links, use descriptive link names like
- @uref{,Download LilyPond 2.5.16}
-
- * avoid putting links in running text. They make text harder to read.
- Preferably: (@uref{,...}, etc. )
-
- * use a descriptive title in @subsubheading
-
- * writing date in "Month DD, YYYY" format is required for
- generating the RSS feed; in case the message (and thus the date)
- is not in English, you must write a well-formed date in English
- like above in a comment between the closing brace of @emph and the
- following line
- (see "Japanese translation" below for an example).
-
- * Split news items in small chunks. It's OK to have more than 1 item
- on one day.
-
-
-TODO
-
- * add macro for long Google issues list URL
-@end ignore
-
-
-@newsItem
-@subsubheading New Website! @emph{October 3, 2009}
-
-As you can see, we have a new website design. Many thanks to
-texi2html and CSS for being so flexible!
-
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond Report #16. @emph{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 @uref{http://news.lilynet.net/The-LilyPond-Report-16, issue 16}
-now!
-
-@newsEnd
-
-
-
-@newsItem
-@subsubheading Hungarian translation! @emph{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!
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond Report #15. @emph{May 18, 2009}
-
-The @emph{LilyPond Report} is a short, informal opinion column
-about the LilyPond project: its team, its world, its community.
-Read it @uref{http://news.lilynet.net/The-LilyPond-Report-15,
-here}!
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.13.3. @emph{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.@*
-@ref{changes},
-@ref{development}.
-@newsEnd
-
-
-@newsItem
-@subsubheading A LilyPond weboldala magyarul. @emph{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 @code{harmathdenes AT gmail.com} címre!
-<p align="right">Harmath Dénes, a LilyPond honosítási projekt
-vezetője
-@newsEnd
-
-
-@newsItem
-@subsubheading The LilyPond Report #15. @emph{May 18, 2009}
-
-The @emph{LilyPond Report} is a short, informal opinion column about the LilyPond project:
-its team, its world, its community.
-Follow @uref{http://news.lilynet.net/The-LilyPond-Report-15,this link}
-to read the full issue...
-@newsEnd
-
-
-@newsItem
-@subsubheading The LilyPond Report #14. @emph{April 13, 2009}
-
-The @emph{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 @uref{http://news.lilynet.net/The-LilyPond-Report-14,this link} to read the full issue...
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.12.2 and 2.13.0 — @emph{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.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.12.0 @qq{Rune} — @emph{December 27, 2008}
-
-A new stable release of LilyPond is available.
-@*
-@uref{announce-v2.12,Announcement},
-@ref{changes},
-@ref{download}.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.65 — Release Candidate. @emph{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.@*
-@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_65&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{changes},
-@ref{old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.64. @emph{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.
-@*
-@ref{changes},
-@ref{old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.63. @emph{October 29, 2008}
-
-LilyPond 2.11.63 is available. This release has lots of updates to the
-documentation and translations.
-@ref{old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.62 – Release Candidate. @emph{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 @code{\tempo} command, this release has lot of updates
-to Spanish and German documentation translations, and the
-stylesheet for HTML documentation has been improved.
-@*
-@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_62&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.61 available. @emph{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.
-@*
-@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_61&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{changes},
-@ref{old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.60 available. @emph{September 25, 2008}
-
-LilyPond 2.11.60 has been released. A new style of double repeat
-bar line has been added, and @code{printallheaders} variable in
-score block has been renamed to @code{print-all-headers}.
-@ref{old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.59 available. @emph{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.
-@ref{old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.58 available. @emph{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.
-@*
-@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_58&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{changes},
-@ref{old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.57 available. @emph{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.
-@*
-@ref{changes},
-@ref{old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.56 available. @emph{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 @code{\pointAndClickOn},
-@code{\pointAndClickOff} have also been added.
-@*
-@ref{changes},
-@ref{old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.55 available. @emph{August 6, 2008}
-
-LilyPond 2.11.55 is out. This release fixes several bugs, and for octavation brackets
-@code{set-octavation} has been replaced by a more user-friendly command, @code{\ottava}.
-@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_55&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.54 available. @emph{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 @code{short-indent}
-so that short instrument names are no longer indented in the margin.
-@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_54&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.53 available. @emph{July 23, 2008}
-
-LilyPond 2.11.53 is out. This release fixes a lot of bugs.
-@*
-@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_53&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.52 available. @emph{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. @ref{changes},
-@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_52&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.51 available. @emph{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 @code{fret-diagram-details} property.
-@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_51&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.50 available. @emph{July 2, 2008}
-
-Release 2.11.50 adds support for metronome marks with text, and
-backslashed numbers for figured bass, contributed by
-Reinhold Kainhofer.
-@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_50&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading The LilyPond Report #13. @emph{June 23, 2008}
-
-This short, informal, weekly opinion column is about the LilyPond project: its team, its world, its community.
-Follow @uref{http://valentin.villenave.info/The-LilyPond-Report-13,this link} to read the full issue...
-@newsEnd
-
-
-@newsItem
-@subsubheading The LilyPond Report #12. @emph{June 16, 2008}
-
-This short, informal, weekly opinion column is about the LilyPond project: its team, its world, its community.
-Follow @uref{http://valentin.villenave.info/The-LilyPond-Report-12,this link} to read the full issue...
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.49 released. @emph{June 12, 2008}
-
-LilyPond 2.11.49 is out. It fixes a number of bugs, including bugs in beams formatting.
-@*
-@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_49&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.48 released. @emph{June 9, 2008}
-
-LilyPond 2.11.48 is out. This release fixes a few bugs, and
-@code{\compressMusic} has been renamed
-to @code{\scaleDurations}.
-@*
-@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_48&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading The LilyPond Report #11. @emph{June 9, 2008}
-
-This short, informal, weekly opinion column is about the LilyPond project: its team, its world, its community.
-Follow @uref{http://valentin.villenave.info/The-LilyPond-Report-11,this link} to read the full issue...
-@newsEnd
-
-
-@newsItem
-@subsubheading The LilyPond Report #10. @emph{June 2, 2008}
-
-Welcome to this special tenth issue of the @emph{LilyPond Report}, entirely dedicated to Algorithmic Composition systems.@*
-Follow @uref{http://valentin.villenave.info/The-LilyPond-Report-10,this link} to read the full issue...
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.47 released. @emph{May 28, 2008}
-
-LilyPond now allows all text context properties to be markups,
-except in @code{\lyricmode}. This release also fixes
-regression tests maintenance for developers.
-@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_47&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.46 available. @emph{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.
-@ref{changes},
-@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_46&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading RSS feed - @emph{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.
-@uref{http://lilypond.org/web/lilypond-rss-feed.xml,Feed URL}.
-The info mailing list (see @ref{contact}) is still used to
-announce releases and special events.
-@newsEnd
-
-
-@newsItem
-@subsubheading The LilyPond Report #9. @emph{May 05, 2008}
-
-Welcome to this ninth issue of the @emph{LilyPond Report}!@*
-This short, informal, weekly opinion column is about the LilyPond project: its team, its world, its community.
-Follow @uref{http://valentin.villenave.info/The-LilyPond-Report-9,this link} to read the full issue...
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.45 available. @emph{April 26, 2008}
-
-Release 2.11.45 fixes a couple of bugs in the formatting
-engine. @code{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.
-@ref{changes},
-@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_45&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.44 available. @emph{April 14, 2008}
-
-Release 2.11.44 is available. Support for figured bass and chord
-names has been added to the MusicXML
-converter. @uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_44&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading lilypond.org日本語訳 (lilypond.org Japanese translation). @emph{2008年4月8日 (April 4, 2008)}
-
-Lilypond.orgのいくつかのページの日本語訳が出来ました。
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.43 available. @emph{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. @uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_43&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.42 available. @emph{March 9, 2008}
-
-Release 2.11.42 is out. It fixes some formatting and spacing
-bugs. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_42&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading Comparison of music engraving with Finale and LilyPond. @emph{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.
-@uref{http://www.musicbyandrew.ca/finale-lilypond-1.html,Read
-the articles}.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.41 available. @emph{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. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_41&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.37 available. @emph{January 3, 2008}
-
-Release 2.11.37 is available. It has a few bugfixes, and
-documentation changes. (@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.36 available. @emph{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. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_36&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes}, @ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.33 and 2.10.33 available. @emph{September 20, 2007}
-
-Release 2.11.33 is now available.
-(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_33&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
-2.10}, @uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_33&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
-2.11}, @ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.32 available. @emph{September 2, 2007}
-
-Release 2.11.32 is now available.
-(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_32&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes}, @ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.31 available. @emph{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.
-(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_31&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes}, @ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.30 available. @emph{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. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_30&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes}, @ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.10.29 and 2.11.29 available. @emph{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.
-(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_29&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
-2.10}, @uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_29&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
-2.11}, @ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.28 for FreeBSD x86_64. @emph{August 10, 2007}
-
-Release 2.11.28 is now available as a binary installer for
-FreeBSD x86_64. Download
-@uref{http://lilypond.org/download/binaries/freebsd-64/lilypond-2.11.28-1.freebsd-64.sh,the installer} and
-do @emph{sh lilypond-2.11.28-1.freebsd-64.sh} in a command window.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.28 available - @emph{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.
-(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_28&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
-2.11}, @ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.26 available - @emph{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!
-(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_26&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
-2.11}, @ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.10.25 and 2.11.25 available - @emph{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!
-(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_25&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
-2.11}, @uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_25&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
-2.10}, @ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.10.23 and 2.11.23 available - @emph{May 1, 2007}
-This has lots of bugfixes. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_23&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
-2.11}, @uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_23&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
-2.10}, @ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading Übersetzung der Dokumentation - @emph{10. April 2007}
-Die Kapitel 1-5 (der Abschnitt für Anfänger) des
-LilyPond-Benutzerhandbuchs
-sind auf deutsch übersetzt — sie sind erhältlich für
-die @ref{changes}
-online und @ref{old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.22 available - @emph{April 10, 2007}
-This release has updates of the dot collision code. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_22&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
-}, @ref{changes}, @ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.21 available - @emph{March 24, 2007}
-This release has some documentation updates.
-(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_21&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
-}, @ref{changes}, @ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading Traduction de la documentation en français - @emph{25 février 2007}
-Les chapitres 1 à 4 et 6 du manuel de l'utilisateur sont
-désormais traduits, et disponibles en ligne — @uref{@@DOC@@v2.10/Documentation/user/lilypond/index.fr.html,version
-2.10}, @uref{@@DOC@@v2.11/Documentation/user/lilypond/index.fr.html,version
-2.11}. Les traductions sont également incluses dans la @uref{install,documentation téléchargeable}.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.10.20 and 2.11.20 available - @emph{February 25, 2007}
-This release fixes many bugs.
-(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_20&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
-2.11},
-@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_20&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
-2.10}, @ref{changes}, @ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.10.19 and 2.11.19 available - @emph{February 18, 2007}
-This release fixes many bugs.
-(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_19&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
-2.11},
-@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_19&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
-2.10}, @ref{changes}, @ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.18 available - @emph{February 12, 2007}
-This release fixes still more bugs, and included
-singing support through festival contributed by Milan Zamazal. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_18&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
-2.11}, @ref{changes}, @ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.17 available - @emph{February 9, 2007}
-This release fixes still more bugs.
-(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_17&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
-2.11}, @ref{changes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.10.16 and 2.11.16 available - @emph{February 4, 2007}
-This release fixes many bugs.
-(@uref{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.11},
-@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_16&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
-2.10},
-@ref{changes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.10.15 and 2.11.15 available - @emph{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. (@uref{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.11},
-@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_15&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
-2.10},
-@ref{changes}, @ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.10.14 and 2.11.14 available - @emph{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.
-(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_14&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{changes}, @ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.10.13 and 2.11.13 available - @emph{January 17, 2007}
-This release fixes a few minor but irritating bugs. In addition, the
-2.11 release has updates of the tutorial.
-(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_13&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{changes}, @ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.12 available - @emph{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.
-(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_12&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{changes}, @ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.10.12 available - @emph{January 17, 2007}
-This release mirrors 2.11.12. Notably, it has the same memory
-usage improvements. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_12&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{changes}, @ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.10.11 available - @emph{January 12, 2007}
-This release mostly has the same fixes as 2.11.11. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_11&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{changes}, @ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.11 available - @emph{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. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_11&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{changes}, @ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.10 available - @emph{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. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_10&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{changes}, @ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.10.10 available - @emph{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 (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_10&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{changes}, @ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.9 and 2.10.9 available - @emph{January 3, 2007}
-This release has a couple of bugfixes, and —in 2.11.9&mdash
-further improvements in the regression test suite (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_9&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{changes}, @ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.8 and 2.10.8 available - @emph{January 3, 2007}
-New! Improved! With even more bugfixes! (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_8&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{changes}, @ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading @code{lilypond.org} auf deutsch - @emph{31. Dezember 2006}
-Die LilyPond-Webseiten sind jetzt auch auf deutsch übersetzt!
-@newsEnd
-
-
-@newsItem
-@subsubheading @code{lilypond.org} en español - @emph{December 29, 2006}
-¡Ya está disponible la versión en español del sitio web de LilyPond!
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.7 and 2.10.7 available - @emph{January 1, 2007}
-New! Improved! With even more bugfixes! (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_7&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{changes}, @ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.6 available - @emph{December 30, 2006}
-This release supports arbitrary fractional alterations, allowing
-music with different microtonal conventions to be typeset.
-(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_6&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{changes}, @ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.10.6 available - @emph{December 30, 2006}
-New! Improved! With even more bugfixes!
-(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_6&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{changes}, @ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.5 available - @emph{December 24, 2006}
-These releases complete the translation infrastructure for
-Documentation.
-(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_5&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{changes}, @ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.10.5 available - @emph{December 24, 2006}
-New! Improved! With even more bugfixes!
-(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_5&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{changes}, @ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.4 available - @emph{December 21, 2006}
-The vertical spacing improvements that were introduced in 2.11.0 now work
-within a system as well as between systems. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_4&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{changes}, @ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.3 available - @emph{December 19, 2006}
-This release has @uref{http://lilypond.org/doc/v2.11/compare-v2.10.3/index.html,graphical
-test results} and several website build improvements. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_3&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{changes}, @ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.10.3 available - @emph{December 19, 2006}
-This release fixes several bugs.
-(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_3&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LinuxPPC binaries available! - @emph{December 19, 2006}
-From now on, our GUB binary builds include support for Linux/PPC. (@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading Traduction du tutoriel en français. @emph{December 13, 2006}
-Fruit du travail d'une équipe de traducteurs, le tutoriel en
-français est maintenant disponible en ligne. @uref{@@DOC@@v2.10/Documentation/user/lilypond/Tutorial.fr.html,Version
-2.10}, @uref{@@DOC@@v2.11/Documentation/user/lilypond/Tutorial.fr.html,Version
-2.11}.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.2 available - @emph{December 12, 2006}
-This release supports glissandi and harmonics in tablature. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_2&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{changes}, @ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.10.2 available - @emph{December 12, 2006}
-A new stable release of LilyPond is available. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_2&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.1 available - @emph{December 4, 2006}
-This release has improved support for horizontal spacing. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_1&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{changes}, @ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.10.1 available - @emph{December 3, 2006}
-A new stable release of LilyPond is available. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_1&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.11.0 available - @emph{November 27, 2006}
-This release has improved support for vertical spacing. (@ref{changes}, @ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.10.0 available - @emph{November 11, 2006}
-A new stable release of LilyPond is available. (@uref{announce-v2.10.html,Announcement}, @ref{changes}, @ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading GIT repository online - @emph{November 11, 2006}
-LilyPond development has moved over its source code to @uref{http://git.or.cz,GIT}, the fast version control
-system. Check out our repository at @uref{http://git.sv.gnu.org/gitweb/?p=lilypond.git;a=summary,gnu.org}.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.9.29 available - @emph{November 5, 2006}
-This release has many more bugfixes. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_9_29&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.9.28 available - @emph{November 3, 2006}
-This release has many more bugfixes. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_9_28&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.9.27 available - @emph{October 28, 2006}
-This release has a new @code{FretBoards} context, and some further
-bugfixes. (@ref{changes}, @uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_9_27&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading Music streams thesis available - @emph{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
-(@ref{publications}).
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.9.26 available - @emph{October 20, 2006}
-This release has further bugfixes. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_9_26&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.9.25 available - @emph{October 18, 2006}
-This release has more bugfixes; from now on, binaries are also
-available for x86/64. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_9_25&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.9.24 available - @emph{October 15, 2006}
-This release has support for right hand guitar fingerings, and offers
-some bugfixes. (@ref{changes},
-@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed2924&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.9.23 available - @emph{October 12, 2006}
-This release cuts fragments of EPS directly from your finished score,
-and makes it easier to insert ties into lyrics. (@ref{changes}, @ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.9.22 available - @emph{October 9, 2006}
-Test this release candidate for LilyPond 2.10! (@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.9.21 available - @emph{October 4, 2006}
-Test this release candidate for LilyPond 2.10! (@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.9.20 available - @emph{October 3, 2006}
-Test this release candidate for LilyPond 2.10! (@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.9.17 available - @emph{September 2, 2006}
-This release fixes many bugs. Among others, MacOS X QuickTime now
-honors tempo changes are in the MIDI output. (@ref{changes}, @ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.9.16 available - @emph{August 25, 2006}
-In this release, chords may be partially tied and lyric extenders have
-tunable padding. Moreover, many bugs were fixed
-(@ref{changes}, @ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.9.15 available - @emph{August 20, 2006}
-This releases fixes many bugs in the 2.9.14 release. (@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.8.6 available - @emph{August 8, 2006}
-This release contains a few minor bugfixes; the source tarball is also
-available. (@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.9.14 available - @emph{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. (@ref{changes}, @ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.9.13 available - @emph{July 23, 2006}
-This release supports doits and falls, and more tuning options for
-grace note spacing and tuplet brackets. (@ref{changes}, @ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.9.12 available - @emph{July 18, 2006}
-This release supports pdftex for lilypond-book, and uses PdfTeX for
-generating manuals, so page numbers and references are now clickable.
-(@ref{changes}, @ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.9.11 available - @emph{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. (@ref{changes}, @ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.9.10 available - @emph{June 15, 2006}
-This releases fixes a couple of bugs in 2.9.9.
-(@ref{changes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.9.9 available - @emph{June 15, 2006}
-This releases fixes many bugs in 2.9.8 and earlier.
-(@ref{changes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.9.8 available - @emph{June 6, 2006}
-2.9.8 has support for different spacing sections within a single
-score, and better infrastructure for automated regression testing.
-(@ref{changes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.8.4 available - @emph{June 4, 2006}
-2.8.4 fixes some minor bugs, and includes a backport of the
-infrastructure for automated regression testing.
-(@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading First test results available - @emph{June 4, 2006}
-After a week of frantic tweaking, the first automated testing results
-are available. You can now see @uref{http://lilypond.org/doc/v2.9/compare-v2.8.4/index.html,in full
-glory} what features are broken in the development release
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.9.7 available - @emph{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
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.9.6 available - @emph{May 24, 2006}
-This
-release has new features in beam formatting: beams may now be put on
-single stems, and obey the @code{beatGrouping} property. MusicXML
-converter. (@ref{changes}, @ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading New essay pages! - @emph{May 22, 2006}
-The @emph{Automated Engraving} essay has been updated with material
-from the @uref{http://fisl.softwarelivre.org,FISL} talk, with
-pages on @uref{about/automated-engraving/problem-statement,modeling
-notation} and @uref{about/automated-engraving/scoring-esthetics,algorithms for
-esthetics}. Happy reading!
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.9.5 available - @emph{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.
-(@ref{changes}, @ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.9.4 available - @emph{May 12, 2006}
-This release has support for feathered beaming, and note head styles in
-the markup @code{\note} command. In addition, it has a lot of updates
-of the manual and a clean up of the spring spacer.
-(@ref{changes}, @ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.8.2 available - @emph{May 12, 2006}
-This release has fixes for minor bugs and compilation issues.
-(@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.9.3 is out! - @emph{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. (@ref{changes}, @ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading FISL7.0 slides available - @emph{April 22, 2006}
-The slides for Han-Wen's talk at
-@uref{http://fisl.softwarelivre.org,FISL 7} are now online.
-(@ref{publications})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.8.1 is out! - @emph{April 3, 2006}
-Important bugfixes include CJK font handling and a Darwin/x86 port.
-(@ref{changes}, @ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.9.1 is out! - @emph{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.
-(@ref{changes}, @ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond on MacOS X/Intel - @emph{March 31, 2006}
-LilyPond now also runs on Intel based macs, offering a 400%
-speedup over the emulated PowerPC binaries. (@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.8.0 is out! - @emph{March 22, 2006}
-Version 2.8 is here! Read the @uref{announce-v2.8.html,release
-announcement}. (@ref{changes}, @ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.39 is out - @emph{March 17, 2006}
-This release has even more bug fixes. Please test before 2.8 is
-released. (@ref{changes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.38 is out - @emph{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.
-(@ref{changes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.37 is out - @emph{March 4, 2006}
-This release has more bug fixes. Please help us by testing it!
-(@ref{changes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.36 is out - @emph{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. (@ref{changes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.35 is out - @emph{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 @strong{very} welcome. By
-definition a bug is release critical if it wasn't present in version
-2.6. (@ref{changes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.34 is out - @emph{February 16, 2006}
-This release has a bunch of bugfixes, and new features. Newly created
-contexts may also be named with @code{\new Voice =
-"alto"}. Thicknesses of tie and slurs may be tuned separately for
-the endings and the middle
-part. (@ref{changes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.33 is out - @emph{February 10, 2006}
-Items directly connected with a music input element may be
-parenthesized, for example,
-@verbatim
-{
- c4 -\parenthesize -.
- <d \parenthesize fis a>
-}
-@end verbatim
-
-This feature was sponsored by Ramana Kumar. (@ref{changes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.32 is out - @emph{February 7, 2006}
-This release contains some syntax changes: words inside the \paper and
-\layout block are henceforth written with dashes, for instance:
-
-@verbatim
-{
- \layout {
- ragged-right = ##t
- }
-}
-@end verbatim
-
-Furthermore, in this release, we have dropped some legacy code from
-our library. Now, lily uses standard C++ strings and the STL
-vector. (@ref{changes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.31 is out - @emph{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.
-(@ref{changes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.30 is out - @emph{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. (@ref{changes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.29 is out - @emph{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). (@ref{changes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.28 is out - @emph{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. (@ref{changes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.27, release 4 - @emph{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! (@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.27, release 3 - @emph{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 @strong{FreeBSD} as well! Jump
-to the @ref{old downloads} get them!
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.27 binaries are out - @emph{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
-@uref{http://lilypond.org/download/binaries/linux-x86/lilypond-2.7.27-1.linux.sh,
-Linux/x86},
-@uref{http://lilypond.org/download/binaries/MacOS/lilypond-2.7.27-2.zip,
-MacOS X} and
-@uref{http://lilypond.org/download/binaries/mingw/lilypond-2.7.27-2.exe,
-Windows}.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.27 is out - @emph{January 7, 2006}
-This release allows you to switch staff lines on and off individually
-(feature sponsored by Andrea
-Valle). (@ref{changes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading Linux Journal article - @emph{January 2006}
-Linux Journal publishes an article on
-@uref{http://www.linuxjournal.com/article/8364,@emph{Make
-Stunning Schenker Graphs with GNU LilyPond}}. 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.”
-This article is now available @uref{http://www.linuxjournal.com/article/8583,on-line}.
-@newsEnd
-
-
-@newsItem
-@subsubheading New binaries for LilyPond 2.7.26 - @emph{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 @ref{old downloads}
-page. Let us know how you fare!
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.26 is out - @emph{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!
-(@ref{changes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.25 is out - @emph{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). (@ref{changes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.24 is out - @emph{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. (@ref{changes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.23 is out - @emph{December 19, 2005}
-This release has the following new features:
-@itemize
-@item
-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).
-@item
-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).
-@item
-Generic music functions may now also be used on
-articulations and chord elements (feature sponsored by Sean Reed and
-Bertalan Fodor).
-@item
-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.
-@end itemize
-(@ref{changes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.22 is out - @emph{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. (@ref{changes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.21 is out - @emph{December 5, 2005}
-Saint Nicholas brings you ... a @uref{http://www.musicxml.org/,MusicXML} convertor for LilyPond!
-The convertor is basic, but working. Check out the @uref{http://www.lilypond-design.com/sponsor/open-features.html#inputfilter,
-LilyPond Software Design} pages for MusicXML features that can be
-sponsored.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.20 is out - @emph{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). (@ref{changes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.6.5 is out - @emph{December 1, 2005}
-This release updates the bugreporting address and reorganizes the
-documentation tree. (@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.19 is out - @emph{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. (@ref{changes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.18 is out - @emph{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. (@ref{changes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.17 is out - @emph{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. (@ref{changes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.16 is out - @emph{November 11, 2005}
-This release fixes a large number of bugs. Please upgrade before
-reporting bugs in the 2.7 series. (@ref{changes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.15 is out - @emph{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. (@ref{changes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.14 is out - @emph{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.
-@verbatim
-
-\override Beam #'direction = #(lambda (grob)
-(if (> (random 10) 5) UP DOWN))
-
-@end verbatim
-will set a random direction for beams. (@ref{changes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.13 is out - @emph{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. (@ref{changes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.6.4 is out - @emph{October 11, 2005}
-This release fixes a few minor problems with the stable
-series. (@ref{changes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.12 is out - @emph{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). (@ref{changes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.11 is out - @emph{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. (@ref{changes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.10 is out - @emph{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. (@ref{changes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.9 is out - @emph{September 5, 2005}
-This is mainly a bugfix
-release. (@ref{changes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading Traduction française du site - @emph{September 03, 2005}
-Grâce à @uref{about/thanks#website,l'équipe des traducteurs},
-de nombreuses pages du site sont maintenant disponibles en français,
-notamment l'@uref{about/automated-engraving/index.fr.html,essai sur
-la gravure musicale}.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.8 is out - @emph{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. (@ref{changes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading Article in `De Standaard' - @emph{August 20, 2005}
-The Belgian newspaper @emph{De Standaard} investigates what drives
-Free Software authors in an article titled @emph{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.
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.7 is out - @emph{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á. (@ref{changes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.6 is out - @emph{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. (@ref{changes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.5 is out - @emph{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. (@ref{changes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.4 is out - @emph{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. (@ref{changes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.6.3 is out - @emph{August 4, 2005}
-This release fixes a memory corruption bug that was triggered by
-\override'ing Beam settings. (@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.6.2 is out - @emph{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. (@ref{changes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.3 is out - @emph{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.
-(@ref{changes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.2 is out - @emph{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. (@ref{changes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.6 released - @emph{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).
-@strong{Get up and running in minutes!} Pango text formatting lets you
-print @strong{Unicode } lyrics in your favorite script and font. Create
-@strong{SVG} files, and edit them in Inkscape.
-(@uref{announce-v2.6.html,Announcement}, @ref{old downloads}, @ref{changes})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7.1 is out - @emph{July 20, 2005}
-LilyPond 2.7.1 has no user-visible changes. However, due to
-restructuring @qq{under the hood}, this version will be 10 to
-20 % faster. (@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.6.1 is out - @emph{July 11, 2005}
-This version fixes a few minor bugs found in
-2.6.0, and also works on DOS-based Windows versions. (@ref{changes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.7 is out - @emph{July 9, 2005}
-LilyPond 2.7.0 is out. It has support for paragraph text and
-pitched trill notation. (@ref{changes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading 2.5.31 released - @emph{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.
-(@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading Traduction du site de LilyPond - @emph{15 juin 2005}
-@uref{about/thanks#website,L'équipe des traducteurs} vous présente
-le site de LilyPond en français. Nous travaillons sur la traduction des
-pages encore non traduites. Bon surf !
-@newsEnd
-
-
-@newsItem
-@subsubheading 2.5.31 for Windows and MacOS - @emph{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.
-(@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading 2.5.31 released - @emph{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. (@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading 2.5.30 released - @emph{June 10, 2005}
-This is (hopefully) the last Release Candidate before 2.6. Give it a
-good shake to find those last bugs! (@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading 2.5.29 released - @emph{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). (@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading 2.5.27 released - @emph{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. (@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading Windows and MacOS installers available - @emph{May 26, 2005}
-There are now a native, standalone installers for Windows and
-MacOS. They also support PDF point & click. (@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading 2.5.26 released - @emph{May 26, 2005}
-This release has a couple of small bugfixes.
-@newsEnd
-
-
-@newsItem
-@subsubheading 2.5.25 released - @emph{May 20, 2005}
-This release has many small bugfixes and updates to the
-documentation. (@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading 2.5.24 released - @emph{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. (@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading 2.5.23 released - @emph{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. (@ref{changes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading 2.5.22 released - @emph{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.
-(@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-(@ref{changes},
-@ref{old downloads})
-@newsEnd
-
-
-@newsItem
-@subsubheading 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 @ref{changes}
-file, or go straight to @ref{old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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 @ref{changes}
-file and @ref{old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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. @ref{old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading 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. @ref{old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading 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 @ref{changes}
-file and @ref{old downloads}!
-@newsEnd
-
-
-@newsItem
-@subsubheading 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 @ref{changes}
-file and download @ref{old downloads}!
-@newsEnd
-
-
-@newsItem
-@subsubheading March 7, 2005
-LilyPond 2.4.5 is out. This release backports the tieWaitForNote
-feature and has support for tetex-3.0.
-@ref{old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading February 28, 2005
-LilyPond 2.5.13 is available for Fedora Core 3. You need to install @uref{http://lilypond.org/download/binaries/Fedora-3/ghostscript-8.15rc3-0.i386.rpm,ESP
-Ghostscript 8.15rc3}. 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.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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 @uref{http://lilypond.org/doc/v2.5/Documentation/user/out-www/lilypond/Point-and-click.html,here}.
-Take a look at the @ref{changes}
-file and download @ref{old downloads}!
-@newsEnd
-
-
-@newsItem
-@subsubheading February 26, 2005
-The @uref{http://lsr.dsi.unimi.it/,Lilypond Snippet
-Repository (LSR)} 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.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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 @strong{all}
-fonts available via FontConfig. Also, arpeggios may be written out
-using ties and individual objects may have colors! Take a look at
-the @ref{changes}
-file and @ref{old downloads}!
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{old downloads}!
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading 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
-@uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.3065&content-type=text/vnd.viewcvs-markup,
-change log
-} and @ref{old downloads}!
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{old downloads}
-and check out the changes in
-the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.3048&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{old downloads}
-and check out the
-changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.3013&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{old downloads}
-and check out the changes in
-the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev= 1.3000&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{old downloads}
-and check out the
-changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2974&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{old downloads}
-and
-check out the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2908&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{old downloads}
-and check out the changes in
-the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2898&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{old downloads}
-and check out the changes in
-the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2881&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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
-@verbatim
-
-\cueDuring #VOICE-NAME #DIRECTION { MUSIC }
-
-@end verbatim
-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.
-@ref{old downloads}
-and check out
-the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2837&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{old downloads}
-and check out the changes in
-the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2780.2&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading October 31, 2004
-LilyPond 2.4.0 was just @uref{announce-v2.4.html,released!}
-This new stable version has support for page-layout,
-completely rewritten slur formatting and many other
-improvements. Read about them in the @ref{changes}
-file.
-@ref{old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{old downloads}
-and check out the changes in
-the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2773&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{old downloads}
-and check out the changes in
-the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2765&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{old downloads}
-and check out the changes in
-the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2752&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{old downloads}
-and check out the changes in
-the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2742&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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@{@}.
-@ref{old downloads}
-and
-check out the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2709&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{old downloads}
-and check
-out the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2692&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{old downloads}
-and check out the changes in
-the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2674&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading September 29, 2004
-The LilyPond development team will be present at the @uref{http://www.nluug.nl/events/sane2004/bazaar/index.html,Free
-Software Bazaar} 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.
-@newsEnd
-
-
-@newsItem
-@subsubheading September 26, 2004
-LilyPond 2.3.19 is out. It's mainly a bugfix release.
-@ref{old downloads}
-and check out the changes
-in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2652&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{old downloads}
-and check out the changes in
-the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2614&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{old downloads}
-and check out the changes in
-the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2562&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{old downloads}
-and check out the changes in
-the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2553&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{old downloads}
-and check out
-the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2534&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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!
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{old downloads}
-and
-check out the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2520&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading August 24, 2004
-LilyPond 2.2.6 fixes a few minor issues, among others, the
-disappearing metronome mark.
-@ref{old downloads}
-and check out the changes in
-the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2000.2.33&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{old downloads}
-and check out the changes in
-the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2489&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading August 3, 2004
-LilyPond 2.3.11 is out. This release basically is 2.3.10 with a few
-annoying bugs fixed.
-@ref{old downloads}
-and check out
-the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2449&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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:
-@itemize
-@item
-Running trills now have their own spanner and event. They are
-started and stopped with \startTrillSpan and \stopTrillSpan
-@item
-There is a new markup command `\postscript' that takes a string
-that is dumped as verbatim PostScript
-@end itemize
-
-@ref{old downloads}
-and check out
-the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2435&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{old downloads}
-and check out
-the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2416&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{old downloads}
-and check out the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2395&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{old downloads}
-and check out the changes in
-the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2383&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading July 15, 2004
-LilyPond 2.2.5 was released. It has a few bug fixes from
-2.3.x.
-@ref{old downloads}
-and check
-out the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2000.2.28&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading July 11, 2004
-An introductory article on LilyPond appeared on @uref{http://www.linuxjournal.com/article.php?sid=7657&mode=thread&order=0,Linux
-Journal}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{old downloads}
-and check out the changes
-in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2306&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading July 5, 2004
-LilyPond 2.2.4 was released. It is mainly a bug fix
-release.
-@ref{old downloads}
-and
-check out the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2000.2.23&content-type=text/vnd.viewcvs-markup,ChangeLog}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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 @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2293&content-type=text/vnd.viewcvs-markup,ChangeLog}
-and
-@ref{old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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 @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2000.2.16&content-type=text/vnd.viewcvs-markup,ChangeLog} for a full description and
-@ref{old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading June 13, 2004
-LilyPond 2.3.4 further improves the output backends. As a
-result, manual page-breaks, multiple output formats and putting
-@code{\score} into markups now works. Check out the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2242&content-type=text/vnd.viewcvs-markup,ChangeLog}
-and
-@ref{old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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 @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2207&content-type=text/vnd.viewcvs-markup,ChangeLog}
-and
-@ref{old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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 @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2000.2.9,ChangeLog}
-or head straight to the
-@ref{old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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 @ref{changes} or head straight to the
-@ref{old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading May 9, 2004
-LilyPond 2.3.1 is out. This release has many new and cool
-features. Check out the @ref{changes} or head straight to the
-@ref{old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading May 4, 2004
-Help LilyPond get better, and join in on LilyPond
-development! This
-@uref{devel/participating/call-for-help.html,call for
-help} 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!
-@newsEnd
-
-
-@newsItem
-@subsubheading May 3, 2004
-LilyPond 2.2.1 has been released. It fixes a handful of bugs.
-@ref{old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading April 17, 2004
-LilyPond 2.2.0 is now available
-on Windows, and should find its way to the Cygwin mirrors
-soon.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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 @emph{experimental}; expect things to break!
-More info in the @ref{changes}.
-@ref{old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading April 8, 2004
-A French article on the new LilyPond
-release appeared on @uref{http://linuxfr.org/2004/04/08/15968.html,linuxfr.org}.
-@newsEnd
-
-
-@newsItem
-@subsubheading April 8, 2004
-Binaries for LilyPond 2.2.0 are available for
-MacOS X, Slackware, Mandrake and Debian Woody.
-@ref{old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading 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 @uref{announce-v2.2.html,announcement} or skip to the
-@ref{old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading March 30, 2004
-LilyPond 2.1.36 has many fixes in
-the user manual.
-@ref{old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading March 28, 2004
-LilyPond 2.1..35 fixes a slew of
-bugs, and has the @code{raggedlast} option, which causes
-paragraph like line breaking for scores. More info in the
-@ref{changes}.
-@ref{old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading March 22, 2004
-LilyPond 2.1.34 fixes minor bugs, and has more rewriting.
-@ref{old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading March 21, 2004
-LilyPond 2.1.33 fixes a serious bug, and a few other
-irritations.
-@ref{old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading 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).
-@ref{old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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
-@ref{changes} and
-@ref{old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading March 14, 2004
-The
-@uref{http://linuxmusician.com/index.php?option=articles&task=viewarticle&artid=10,linuxmusician.com interview} made the
-@uref{http://slashdot.org/article.pl?sid=04/03/13/2054227&mode=thread&tid=141&tid=188,slashdot
-frontpage!}.
-@newsEnd
-
-
-@newsItem
-@subsubheading March 11, 2004
-@uref{http://linuxmusician.com,linuxmusician.com} is
-running an
-@uref{http://linuxmusician.com/index.php?option=articles&task=viewarticle&artid=10,interview}
-with Han-Wen Nienhuys and Jan Nieuwenhuizen, the main
-authors of LilyPond.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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
-@ref{changes} and
-@ref{old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading March 9, 2004
-LilyPond 2.1.29 fixes a couple of MIDI bugs, and has
-experimental support for producing titles with
-@code{markup}.
-@newsEnd
-
-
-@newsItem
-@subsubheading February 29, 2004
-In LilyPond 2.1.28 Scheme property functions may be used
-argument to @code{set!}. In addition, parts of the manual
-have been proofread and corrected in this release. See the
-@ref{changes} and
-@ref{old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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
-@ref{changes} and
-@ref{old downloads}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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
-@ref{changes}.
-@ref{old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading February 18, 2004
-LilyPond 2.1.25 fixes many bugs, and changes the conventions
-for altering accidental rules.
-@ref{old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading February 16, 2004
-LilyPond 2.1.24 has a big
-internal rewrite. One of its practical consequences is that
-@code{\with} now also works with @code{Score}
-contexts. Further 2.1.23, which was not announced here,
-fixes a few bugs caused by the change of @code{\property}
-syntax and has updates in the Program Reference document.
-More information in the
-@ref{changes}.
-@ref{old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading February 13, 2004
-LilyPond 2.1.22 has a
-simplification of the @code{\property} syntax: it is
-shorter and more consistent now. More information in the
-@ref{changes}.
-@ref{old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading 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
-@ref{changes}.
-@ref{old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading 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
-@ref{changes}.
-@ref{old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading February 5, 2004
-LilyPond 2.1.19 has rewritten
-support for drum notation. This release also makes some
-long-standing cleanups: the removal of @code{Thread} (all
-functionality is now moved into @code{Voice}) and Lyrics
-(functionality moved to @code{LyricsVoice}) context.
-More information in the
-@ref{changes}.
-@ref{old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading February 4, 2004
-LilyPond 2.1.18 is out. This
-release has the new part-combiner installed by default, and a
-similar implementation of @code{autochange}. More information
-in the
-@ref{changes}.
-@ref{old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading February 2, 2004
-LilyPond 2.1.17 is out. It adds texts
-(solo, a due) for the part combiner. It also reinstates the
-@code{--safe} option which prevents havoc by Scheme exploits. More
-information in the
-@ref{changes}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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
-@ref{changes}.
-@ref{old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading 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
-@ref{changes}. @ref{old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading 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
-@ref{changes}. @ref{old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading January 19, 2004
-LilyPond 2.1.12 fixes many bugs
-and improves formatting of ottava brackets. More information in
-the
-@ref{changes}. @ref{old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading January 18, 2004
-LilyPond 2.1.11 is now also
-available for Windows! For downloading, go
-@uref{http://www.inf.bme.hu/~berti/lilypond/,here}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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
-@ref{changes}. @ref{old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading January 16, 2004
-LilyPond 2.1.10 has a load of
-bugfixes and a shorter syntax for octave checks. More
-information in the
-@ref{changes}. @ref{old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading 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
-@ref{changes}. @ref{old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading January 9, 2004
-LilyPond 2.1.8 has an important new
-feature: it is now possible to use @code{\property} to tune
-the appearance of spanning objects like @code{StaffSymbol} and
-@code{SystemStartBrace}. In addition, contexts may be
-modified with @code{\remove} and @code{\consists} for
-individual music expressions.
-More information in the
-@ref{changes}. @ref{old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading January 7, 2004
-An update to the stable branch,
-version 2.0.2, was released today. It contains a couple of
-minor bugfixes. @ref{old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading 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
-@ref{changes} and download @uref{install/#2.1,here}.
-@newsEnd
-
-
-@newsItem
-@subsubheading January 4, 2004
-LilyPond 2.1.6 continues to
-improve the layout of lyrics. More
-information in the
-@uref{@@DOC@@v2.1/Documentation/topdocs/out-www/NEWS.html,release
-notes} and download @uref{install/#2.1,here}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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ängers Morgen. More
-information in the
-@ref{changes} and download @uref{install/#2.1,here}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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
-@ref{changes} and download @uref{install/#2.1,here}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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
-@ref{changes} and download @uref{install/#2.1,here}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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
-@ref{changes} and download @uref{install/#2.1,here}.
-@newsEnd
-
-
-@newsItem
-@subsubheading December 16, 2003
-LilyPond 2.1.1 released. This
-release wraps together all the small fixes made during
-Han-Wen's absence. See the
-@ref{changes} and download @uref{install/#2.1,here}.
-@newsEnd
-
-
-@newsItem
-@subsubheading October 11, 2003
-LilyPond 2.1.0 released. See the
-@ref{changes} and
-download @uref{install/#2.1,here}.
-@newsEnd
-
-
-@newsItem
-@subsubheading October 11, 2003
-LilyPond 2.0.1 binaries for Mandrake 9.1
-available from
-@uref{http://rpm.nyvalls.se/sound9.1.html,here}
-thanks to Heikki Junes.
-@newsEnd
-
-
-@newsItem
-@subsubheading October 9, 2003
-LilyPond 2.0.1 binaries for Slackware 9
-available from @uref{install/#2.0,here},
-thanks to Ricardo Hoffman.
-@newsEnd
-
-
-@newsItem
-@subsubheading October 5, 2003
-LilyPond 2.0.1 binaries are available for Macos X, many thanks to
-Matthias Neeracher.
-@ref{old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading October 4, 2003
-LilyPond 2.0.1 binaries are available for Windows (Cygwin
-version 1.5).
-@ref{old downloads}. Thanks to Bertalan
-Fodor, our new Cygwin maintainer!
-@newsEnd
-
-
-@newsItem
-@subsubheading September 29, 2003
-LilyPond 2.0.1 is released. It
-contains minor bugfixes.
-See the @ref{changes}
-or download @uref{install/#2.0,here} directly.
-@newsEnd
-
-
-@newsItem
-@subsubheading September 27, 2003
-PlanetCCRMA has been updated to include LilyPond 2.0. Go
-@uref{http://www-ccrma.stanford.edu/planetccrma/software/soundapps.html#lilypond,
-here} to download. Thanks to Fernando Pablo
-Lopez-Lezcano!
-@newsEnd
-
-
-@newsItem
-@subsubheading 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
-@uref{announce-v2.0.html,here}, or go to the
-@uref{install/#2.0,download page} directly.
-@newsEnd
-
-
-@newsItem
-@subsubheading September 24, 2003
-LilyPond 1.9.10 is released. This is
-the final LilyPond 2.0 release candidate. Check
-the @ref{changes} and
-download @uref{install/,here}.
-@newsEnd
-
-
-@newsItem
-@subsubheading September 23, 2003
-LilyPond 1.9.9 is released. This is
-the second LilyPond 2.0 prerelease. Check
-the @ref{changes} and
-download @uref{install/,here}.
-@newsEnd
-
-
-@newsItem
-@subsubheading September 19, 2003
-LilyPond 1.9.8 is released. This is
-the first LilyPond 2.0 prerelease. Check
-the @ref{changes} and
-download @uref{install/,here}.
-@newsEnd
-
-
-@newsItem
-@subsubheading September 17, 2003
-LilyPond 1.9.7 is released. LilyPond
-now has support for quarter tone accidentals!
-@ref{old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading September 16, 2003
-LilyPond 1.9.6 is released.
-It has a lot of minor fixes and updates.
-@ref{old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading 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.
-@ref{old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading September 9, 2003
-LilyPond 1.8.2 is released. This
-release fixes a couple of minor bugs.
-@ref{old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading September 7, 2003
-LilyPond 1.8 binaries are available
-for Windows (Cygwin version 1.5).
-@ref{old downloads}
-@newsEnd
-
-
-@newsItem
-@subsubheading August 31, 2003
-LilyPond 1.9.4 is released.
-@emph{This is an experimental release}: read the
-@uref{http://mail.gnu.org/archive/html/lilypond-devel/2003-08/msg00133.html,announcement}
-before trying.
-@newsEnd
-
-
-@newsItem
-@subsubheading August 31, 2003
-LilyPond 1.8 binaries for slackware
-available. Get them @uref{install/,here}.
-@newsEnd
-
-
-@newsItem
-@subsubheading 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
-@ref{changes} and get it @uref{download#1.9,here}.
-@newsEnd
-
-
-@newsItem
-@subsubheading August 28, 2003
-LilyPond 1.9.2 is released. Read the
-@ref{changes} and get it
-@uref{download#1.9,here}.
-@newsEnd
-
-
-@newsItem
-@subsubheading August 26, 2003
-LilyPond 1.9.1 is released. Read the
-@ref{changes} and get it
-@uref{download#1.9,here}.
-@newsEnd
-
-
-@newsItem
-@subsubheading August 25, 2003
-The LilyPond 1.9 development release is available. Read the
-@ref{changes} and get it
-@uref{download#1.9,here}.
-@newsEnd
-
-
-@newsItem
-@subsubheading August 25, 2003
-Mandrake 9.1 RPMS available, get them
-@uref{http://rpm.nyvalls.se/sound9.1.html,here}.
-@newsEnd
-
-
-@newsItem
-@subsubheading August 21, 2003
-LilyPond 1.8.1 was released. Get it @uref{install/,here}, or
-read the @ref{changes}.
-@newsEnd
-
-
-@newsItem
-@subsubheading August 18, 2003
-PlanetCCRMA (eg. RedHat 8 and 9)
-has been updated to 1.8.
-Download @uref{http://www-ccrma.stanford.edu/planetccrma/software/soundapps.html#lilypond,here.}
-@newsEnd
-
-
-@newsItem
-@subsubheading August 7, 2003
-LilyPond 1.8 is released. Read
-@ref{changes} and get it @uref{install/,here}.
-@newsEnd
-
-
-@newsItem
-@subsubheading August 7, 2003
-New website went live!
-@newsEnd
-
-
-@newsItem
-@subsubheading August 6, 2003
-Announced new website.
-@newsEnd
-
-
-@newsItem
-@subsubheading August 1, 2003
-LilyPond 1.7.30 released.
-@newsEnd
-
-
-@newsItem
-@subsubheading July 30, 2003
-Website: present @uref{about/automated-engraving/index.html,treatise}
-about music engraving, music printing software, and LilyPond's
-unique faculties.
-@newsEnd
-
-
-@newsItem
-@subsubheading July 29, 2003
-1.7.29 - release candidate 4 has been released. Packages for
-Red Hat, Debian, Cygwin are @uref{install/,available}.
-@newsEnd
-
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<!-- header_tag -->
-<META HTTP-EQUIV="refresh" content="0;URL=general/index.html">
+<META HTTP-EQUIV="refresh" content="0;URL=web/index.html">
<html><body>
Redirecting to the documentation index...
</body></html>
There are several other text editors available with better support
for LilyPond. For more information, see
-@rgeneral{Alternate input}.
+@rweb{Alternate input}.
@warning{The first time you ever run LilyPond, it may take a
minute or two because all of the system fonts have to be analyzed
@warning{These instructions assume that you are using the built-in
LilyPad editor. If you are using any of the programs described in
-@rgeneral{Alternate input}, please consult the documentation for
+@rweb{Alternate input}, please consult the documentation for
those programs if you have any problems compiling a file.}
@warning{These instructions assume that you are using the built-in
LilyPad editor. If you are using any of the programs described in
-@rgeneral{Alternate input}, please consult the documentation for
+@rweb{Alternate input}, please consult the documentation for
those programs if you have any problems compiling a file.}
On Windows, if you double-click in the LilyPond icon on the
@warning{These instructions assume that you are using commond unix
command-line programs. If you are using any of the programs
-described in @rgeneral{Alternate input}, please consult the
+described in @rweb{Alternate input}, please consult the
documentation for those programs if you have any problems
compiling a file.}
}
my $reldir = "";
$reldir = "../" if ($Texi2HTML::Config::SPLIT eq 'section');
- my $uplink = $reldir."general/manuals.${lang}html";
+ my $uplink = $reldir."web/manuals.${lang}html";
print $fh "<p class=\"toc_uplink\"><a href=\"$uplink\"
title=\"Documentation Index\"><< " .
@cartouche
For more information about how this manual fits with the other
documentation, or to read this manual in other formats, see
-@rgeneral{manuals}.
+@rweb{manuals}.
If you are missing any manuals, the complete documentation can be
found at @w{@uref{http://@/www@/.lilypond@/.org/}}.
@c Definitions for references:
@c
-@c @rgeneral
+@c @rweb
@c @ressay
@c @rglos
@c @rinternals
@ref{\TEXT\,,\DISPLAY\,contributor-big-page,Contributor's Guide}
@end macro
-@macro rgeneral{TEXT}
+@macro rweb{TEXT}
@vindex \TEXT\
-@ref{\TEXT\,,,general-big-page,General Information}
+@ref{\TEXT\,,,web-big-page,General Information}
@end macro
-@macro rgeneralnamed{TEXT,DISPLAY}
+@macro rwebnamed{TEXT,DISPLAY}
@vindex \TEXT\
-@ref{\TEXT\,,\DISPLAY\,general-big-page,General Information}
+@ref{\TEXT\,,\DISPLAY\,web-big-page,General Information}
@end macro
@macro ressay{TEXT}
@ref{\TEXT\,,\DISPLAY\,contributor,Contributor's Guide}
@end macro
-@macro rgeneral{TEXT}
+@macro rweb{TEXT}
@vindex \TEXT\
-@ref{\TEXT\,,,general,General Information}
+@ref{\TEXT\,,,web,General Information}
@end macro
-@macro rgeneralnamed{TEXT,DISPLAY}
+@macro rwebnamed{TEXT,DISPLAY}
@vindex \TEXT\
-@ref{\TEXT\,,\DISPLAY\,general,General Information}
+@ref{\TEXT\,,\DISPLAY\,web,General Information}
@end macro
@macro ressay{TEXT}
@ref{\TEXT\,,\DISPLAY\,lilypond-contributor,Contributor's Guide}
@end macro
-@macro rgeneral{TEXT}
+@macro rweb{TEXT}
@vindex \TEXT\
-@ref{\TEXT\,,,lilypond-general,General Information}
+@ref{\TEXT\,,,lilypond-web,General Information}
@end macro
-@macro rgeneralnamed{TEXT,DISPLAY}
+@macro rwebnamed{TEXT,DISPLAY}
@vindex \TEXT\
-@ref{\TEXT\,,\DISPLAY\,lilypond-general, General Information}
+@ref{\TEXT\,,\DISPLAY\,lilypond-web, General Information}
@end macro
@macro ressay{TEXT}
@ref{\TEXT\,,\DISPLAY\,contributor,Contributor's Guide}
@end macro
-@macro rgeneral{TEXT}
+@macro rweb{TEXT}
@lilyvindex{\TEXT\}
-@ref{\TEXT\,,,general,General Information}
+@ref{\TEXT\,,,web,General Information}
@end macro
-@macro rgeneralnamed{TEXT,DISPLAY}
+@macro rwebnamed{TEXT,DISPLAY}
@lilyvindex{\TEXT\}
-@ref{\TEXT\,,\DISPLAY\,general,General Information}
+@ref{\TEXT\,,\DISPLAY\,web,General Information}
@end macro
@macro ressay{TEXT}
This is the Music Glossary (MG) for LilyPond version @version{}.
For more information about how this fits with the other
-documentation, see @rgeneral{Manuals}.
+documentation, see @rweb{Manuals}.
@c arrowref
@macro aref{word}
ISOLANG = nl
depth = ../..
-SUBDIRS = general learning notation texidocs usage
+SUBDIRS = web learning notation texidocs usage
STEPMAKE_TEMPLATES = documentation
LOCALSTEPMAKE_TEMPLATES = lilypond ly doc-i18n-root
NO_PDF_FILES = 1
-EXTRA_DIST_FILES = general.texi
+EXTRA_DIST_FILES = web.texi
include $(depth)/make/stepmake.make
+++ /dev/null
-\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
-@c This file is part of general.texi
-@ignore
- Translation of GIT committish: 1b3da70d81938d19a2b107382bbe25a267cf130b
-
- When revising a translation, copy the HEAD committish of the
- version that you are working on. See TRANSLATION for details.
-@end ignore
-
-
-@setfilename general.info
-@settitle LilyPond -- Muzieknotatie voor iedereen
-@documentencoding UTF-8
-@documentlanguage nl
-@set web
-@include macros.itexi
-@afourpaper
-@ifnottex
-@node Top
-@top
-@translationof Top
-
-
-@chapheading
-@end ifnottex
-@finalout
-@titlepage
-@title LilyPond
-@subtitle
-@titlefont{New Website}
-@author Het LilyPond ontwikkelteam
-@quotation
-@end quotation
-@vskip 20pt
-@end titlepage
-@copying
-@quotation
-@end quotation
-@end copying
-@divId{pageHeader}
-@heading LilyPond
-
-... muzieknotatie voor iedereen
-@divEnd
-@c @imageId{cmws,web-clef-g-eight-alpha.png,Catchy Musical Web Snippet}
-@imageId{lilylogo,double-lily-modified3.png,LilyPond logo}
-@c @im ageId{cmws,web-snippet-alpha.png,Catchy Musical Web Snippet}
-@divId{quickSummary}
-@subheading Wat is LilyPond?
-
-LilyPond is een Open Source muziek-graveer programma, gewijd aan
-het produceren van de hoogst mogelijke kwaliteit bladmuziek.
-
-Wij brengen de esthetiek van traditioneel gegraveerde muziek naar
-computer afdrukken.
-
-LilyPond is Vrije Software, is gratis en is onderdeel van het
-@uref{http://@/www@/.gnu@/.org/, GNU} project.
-
-@divClass{align-right}
-Lees de @ref{Inleiding}!
-
-@c For this to work, essay needs to be split like we are
-@c --split=node --node-files
-@c Dat en meer in ons @ressaynamed{Engraving, essay}.
-@c Possibly, node Top always works?
-@c Dat en meer in ons @ressaynamed{Top, essay}.
-Dat en meer in ons @ref{automated-engraving,,Essay,essay,Essay}.
-
-@divEnd
-@divEnd
-@divId{news}
-@include news-front.itexi
-@divClass{float-right}
-@divEnd
-@divEnd
-@divId{latestVersion}
-@subheading Quick links
-@c TODO: javascript to detect OS and suggest download?
-@subsubheading Stable
-@ref{Download, Download 2.12.3}
-@ref{Handleiding, Handleiding 2.12.3}
-@subsubheading Unstable
-@ref{Development, Download 2.13.2}
-@ref{Handleiding, Handleiding 2.13.2}
-@divEnd
-@divClass{hide}
-@menu
-* inleiding::
-* download::
-* handleiding::
-* community::
-@end menu
-
-@divEnd
-@contents
-@include general/introduction.itexi
-@include general/download.itexi
-@include general/manuals.itexi
-@include general/community.itexi
-@bye
-
+++ /dev/null
-depth = ../../..
-
-LOCALSTEPMAKE_TEMPLATES = ly
-
-include $(depth)/make/stepmake.make
+++ /dev/null
-@c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
-@c This file is part of general.texi
-@ignore
- Translation of GIT committish: 1b3da70d81938d19a2b107382bbe25a267cf130b
-
- When revising a translation, copy the HEAD committish of the
- version that you are working on. See TRANSLATION for details.
-@end ignore
-
-
-@c -*- coding: utf-8; mode: texinfo; -*-
-@node community
-@unnumbered Community
-
-@untranslated
-
-
-@divClass{column-center-top}
-@subheading Interacting with the community
-@ref{Contact}: get help, discuss, and keep in touch!
-@ref{Tiny examples}: these are @emph{highly} recommended when
-@ref{Bug reports}: something went wrong.
-@divEnd
-@divClass{column-left-bottom}
-@subheading Making LilyPond better
-@ref{Help us}: your assistance is requested.
-@ref{Development}: for contributors and testers.
-@ref{Authors}: the people who made LilyPond what it is today.
-@divEnd
-@divClass{column-right-bottom}
-@subheading Miscellaneous
-@ref{Publications}: what we wrote, and have had written about us.
-@ref{Old news}: an archive.
-@divEnd
-@divClass{hide}
-@menu
-* contact::
-* tiny examples::
-* bug reports::
-* help us::
-* development::
-* authors::
-* publications::
-* old news::
-@end menu
-
-@divEnd
-@node contact
-@unnumberedsec Contact
-
-@untranslated
-
-
-@divClass{column-left-bottom}
-@subheading User Discussions and Help
-@subsubheading User mailist: @code{lilypond-user@@gnu.org}
-@quotation
-@end quotation
-@subsubheading IRC
-@subsubheading Other languages
-@divEnd
-@divClass{column-right-top}
-@subheading Stay Informed
-@subsubheading LilyPond Report
-@subsubheading Releases mailist: @code{info-lilypond@@gnu.org}
-@quotation
-@c don't include gmane posting here. -gp
-@end quotation
-@divEnd
-@divClass{column-right-bottom}
-@subheading Developer Discussion
-@subsubheading Developer mailist: @code{lilypond-devel@@gnu.org}
-@quotation
-@end quotation
-@subsubheading Bug mailist: @code{bug-lilypond@@gnu.org}
-@quotation
-@c don't include gmane posting here. -gp
-@end quotation
-@divEnd
-@node tiny examples
-@unnumberedsec Tiny examples
-
-@untranslated
-
-
-@divClass{column-center-top}
-@subheading What are @qq{Tiny examples}?
-@divEnd
-@divClass{column-left-bottom}
-@subheading Why create them?
-@divClass{keep-bullets}
-@divEnd
-@divEnd
-@divClass{column-right-bottom}
-@subheading How do I create them?
-@divClass{keep-bullets}
-@divEnd
-@divEnd
-@node bug reports
-@unnumberedsec Bug reports
-
-@untranslated
-
-
-@divClass{column-center-top}
-@subheading Step 1: Known bugs
-@divEnd
-@divClass{column-left-bottom}
-@subheading Step 2: Creating a bug report
-@divEnd
-@divClass{column-right-bottom}
-@subheading Step 3: Sending a bug report
-@divEnd
-@node help us
-@unnumberedsec Help us
-
-@untranslated
-
-
-@subheading This document
-@subsubheading High priority / blocks release
-@subsubheading Low priority / may never
-@node development
-@unnumberedsec Development
-
-@untranslated
-
-
-@divClass{heading-center}
-@heading Development materials for LilyPond 2.13.3
-@ref{Handleiding}.}
-@divEnd
-@divClass{column-left-bottom}
-@subheading Download
-@subheading Manuals
-@divEnd
-@divClass{column-right-bottom}
-@subheading Contributors' Guide
-@divEnd
-@node authors
-@unnumberedsec Authors
-
-@untranslated
-
-
-@node publications
-@unnumberedsec Publications
-
-@untranslated
-
-
-@divClass{column-center-top}
-@subheading What we wrote
-@divClass{keep-bullets}
-@divEnd
-@divEnd
-@divClass{column-center-bottom}
-@subheading What others wrote
-@divClass{keep-bullets}
-@divEnd
-@divEnd
-@node old news
-@unnumberedsec Old news
-
-@untranslated
-
-
-@include general/news.itexi
-
-@c -- SKELETON FILE --
+++ /dev/null
-\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
-@c This file is part of general.texi
-@ignore
- Translation of GIT committish: dab17828471057f4e12c0d80777ff9bb4c5b2309
-
- When revising a translation, copy the HEAD committish of the
- version that you are working on. See TRANSLATION for details.
-@end ignore
-
-
-@c -*- coding: utf-8; mode: texinfo; -*-
-@node download
-@unnumbered Download
-
-@untranslated
-
-
-@divClass{heading-center}
-@heading Downloads for LilyPond 2.12.2
-@divEnd
-@divClass{column-left-top}
-@subheading For users
-@c TODO: duplicate to avoid underlined refs in HTML? icky.
-@ref{Unix, @sourceimage{logo-linux} @sourceimage{logo-freebsd}}
-@ref{Unix, Unix (Linux and FreeBSD)}
-@ref{MacOS X, @sourceimage{logo-macosx}}
-@ref{MacOS X, MacOS X}
-@ref{Windows, @sourceimage{logo-windows}}
-@ref{Windows, Microsoft Windows}
-@divEnd
-@divClass{column-right-top}
-@subheading For developers
-@ref{Source}:
-@ref{Old downloads}:
-@divEnd
-@divClass{column-center-bottom}
-@subheading Software License
-@divEnd
-@divClass{color1}
-@subheading Sponsors
-@sourceimage{VTlogo_ITF} @sourceimage{lao_banner_06_on_white_demo}
-@subheading Legalese
-@divClass{legal}
-@divEnd
-@divEnd
-@divClass{hide}
-@menu
-* UNIX::
-* MacOS X::
-* Windows::
-* source::
-* old downloads::
-* GPL::
-@end menu
-
-@divEnd
-@node UNIX
-@unnumberedsec UNIX
-
-@untranslated
-
-
-@divClass{column-center-top}
-@subheading Generic Packages or Distribution-Specific Packages?
-@divEnd
-@divClass{column-left-top}
-@subheading Generic Packages
-@subsubheading Download
-@sourceimage{logo-linux}
-@sourceimage{logo-linux}
-@sourceimage{logo-linux}
-@sourceimage{logo-freebsd}
-@sourceimage{logo-freebsd}
-@subsubheading Install
-@subsubheading Uninstall
-@divEnd
-@divClass{column-right-top}
-@subheading Distribution-specific Packages
-@sourceimage{logo-fedora}
-@sourceimage{logo-ubuntu}
-@sourceimage{logo-slackware}
-@sourceimage{logo-debian}
-@sourceimage{logo-suse}
-@divEnd
-@divClass{column-center-bottom}
-@subheading Legalese
-@divClass{legal}
-@divEnd
-@divEnd
-@node MacOS X
-@unnumberedsec MacOS X
-
-@untranslated
-
-
-@divClass{column-left-top}
-@subheading Packages
-@subsubheading Download
-@sourceimage{logo-macosx}
-@sourceimage{logo-macosx}
-@subsubheading Install
-@subsubheading Uninstall
-@divEnd
-@divClass{column-right-top}
-@subheading Running on the command-line
-@subsubheading Using Python scripts on MacOS 10.3 or 10.4
-@c ommand{convert-ly} and @command{lilypond-book} as follows: if the
-@subsubheading MacOS X on the command line
-@c ommand{abc2ly}, and even @command{lilypond} itself --- are included
-@c ommand{lilypond-book}, @command{convert-ly}, @command{abc2ly}, etc.
-@c ode{bin/convert-ly} (or other program name) in the above file.
-@divEnd
-@divClass{column-center-bottom}
-@subheading Legalese
-@divClass{legal}
-@divEnd
-@divEnd
-@node Windows
-@unnumberedsec Windows
-
-@untranslated
-
-
-@divClass{column-left-top}
-@subheading Packages
-@subsubheading Download
-@sourceimage{logo-windows}
-@subsubheading Install
-@subsubheading Uninstall
-@divEnd
-@divClass{column-right-top}
-@subheading Running on the command-line
-@divEnd
-@divClass{column-center-bottom}
-@subheading Legalese
-@divClass{legal}
-@divEnd
-@divEnd
-@node source
-@unnumberedsec Source
-
-@untranslated
-
-
-@divClass{column-left-bottom}
-@subheading Source tarball
-@divEnd
-@divClass{column-right-bottom}
-@subheading Compiling instructions
-@divEnd
-@node old downloads
-@unnumberedsec Old downloads
-
-@untranslated
-
-
-@divClass{column-center-top}
-@subheading All versions
-@divEnd
-@node GPL
-@unnumberedsec GPL
-
-@untranslated
-
-
-@divClass{column-center-top}
-@subheading Software license
-@divEnd
-@divClass{column-center-bottom}
-@subheading GNU General Public License version 2
-@include gpl-2.0.itexi
-@divEnd
-
-@c -- SKELETON FILE --
+++ /dev/null
-\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
-@c This file is part of general.texi
-@ignore
- Translation of GIT committish: dab17828471057f4e12c0d80777ff9bb4c5b2309
-
- When revising a translation, copy the HEAD committish of the
- version that you are working on. See TRANSLATION for details.
-@end ignore
-
-@node inleiding
-@unnumbered Inleiding
-@translationof introduction
-
-@divClass{column-center-top}
-@subheading Ons Doel
-@imageFloat{flat-design.png,right}
-
-De inspiratie voor LilyPond ontstond toen twee bevriende muzikanten
-ontevreden werden met het saaie en inspiratieloze uiterlijk van
-computerafdrukken. Elke muzikant leest liever mooie muziek, dus
-zouden wij als programmeurs dat afdrukprobleem niet kunnen oplossen?
-
-Dat is nu precies wat LilyPond doet: het drukt muziek volgens de
-beste tradities van klassieke muziekgravure, zonder gedoe. Verspil
-geen tijd met het bijstellen van spatiëring, het verplaatsen van
-tekens, of met het vormgeven van legatoboogjes. Imponeer vrienden
-en collega's met haarscherpe bladmuziek!
-@divEnd
-
-@divClass{column-left-top}
-@subheading Why use LilyPond?
-@ref{Features}: What can LilyPond do?
-@ref{Examples}: I want to see some music!
-@ref{Freedom}: LilyPond is Free Software.
-@divEnd
-@divClass{column-right-top}
-@subheading Who uses it?
-@ref{Productions}: Real-life use of LilyPond.
-@ref{Testimonials}: What do people say?
-@divEnd
-@divClass{column-center-bottom}
-@subheading Why not use LilyPond?
-@ref{Text input}: You write music as @emph{text}?!
-@divEnd
-@divClass{hide}
-@menu
-* features::
-* examples::
-* freedom::
-* productions::
-* testimonials::
-* text input::
-@end menu
-
-@divEnd
-@node features
-@unnumberedsec features
-
-@untranslated
-
-
-@subheading Why switch to LilyPond?
-@subsubheading Excellent classical engraving
-@imageFloat{flat-design.png,right}
-@subsubheading No fiddling
-@subsubheading Text-based input
-@subsubheading Mix music and text
-@imageFloat{lilypond-book.png,right}
-@subsubheading Free software
-@subsubheading Extensible design
-@subsubheading Excellent support
-@divClass{column-center-bottom}
-@subheading Where now?
-@ref{Text input}.
-@divEnd
-@node examples
-@unnumberedsec Examples
-
-@untranslated
-
-
-@imageClickable{examples/liszt-wagner-small.png, (click to enlarge), examples/liszt-wagner.png, center}
-@subsubheading Classical Music
-@imageClickable{examples/bach-bwv610-small.png, (click to enlarge), examples/bach-bwv610.png, center}
-@subsubheading Complex Notation
-@imageClickable{examples/granados-small.png, (click to enlarge), examples/granados.png, center}
-@subsubheading Early Music
-@imageClickable{examples/ancient-headword-small.png, (click to enlarge), examples/ancient-headword.png, center}
-@subsubheading Modern Music
-@imageClickable{examples/cary-small.png, (click to enlarge), examples/cary.png, center}
-@subsubheading Efficient, flexible creation of performance materials
-@imageClickable{examples/sesto-small.png, (click to enlarge), examples/sesto.png, center}
-@imageClickable{examples/sesto-1-small.png, (click to enlarge), examples/sesto-1.png, center}
-@imageClickable{examples/sesto-2-small.png, (click to enlarge), examples/sesto-2.png, center}
-@subsubheading Tablature
-@imageClickable{examples/bach-tab-example-small.png, (click to enlarge), examples/bach-tab-example.png, center}
-@subsubheading Schenker Graphs
-@imageClickable{examples/bach-schenker-small.png, (click to enlarge), examples/bach-schenker.png, center}
-@subsubheading Vocal Music
-@imageClickable{examples/aucun-snippet-small.png, (click to enlarge), examples/aucun-snippet.png, center}
-@subsubheading Educational Applications
-@imageClickable{examples/theory-small.png, (click to enlarge), examples/theory.png, center}
-@subsubheading Popular Music
-@imageClickable{examples/chart-small.png, (click to enlarge), examples/chart.png, center}
-@subsubheading Large Projects
-@imageClickable{examples/orchestral-small.png, (click to enlarge), examples/orchestral.png, center}
-@divClass{column-center-bottom}
-@subheading Where now?
-@ref{Freedom}. If you've already decided to try LilyPond, first
-@divEnd
-@node freedom
-@unnumberedsec Freedom
-
-@untranslated
-
-
-@divClass{column-center-top}
-@subheading Free Software
-@ref{GPL, GNU General Public License} and the @ref{FDL, GNU Free
-@divEnd
-@c @divClass{column-left-top}
-@divClass{color2}
-@divClass{keep-bullets}
-@subheading What are the benefits to users?
-@divEnd
-@divEnd
-@c @divClass{column-right-top}
-@divClass{color3}
-@divClass{keep-bullets}
-@subheading Why do LilyPond developers @qq{give away} their work for free?
-@divEnd
-@divEnd
-@divClass{column-center-bottom}
-@subheading Where now?
-@ref{Productions} and sheet music. If you've already decided to
-@divEnd
-@node productions
-@unnumberedsec Productions
-
-@untranslated
-
-
-@divClass{column-left-top}
-@subheading Concerts
-@divClass{keep-bullets}
-@divEnd
-@divEnd
-@divClass{column-right-top}
-@subheading Published sheet music
-@divClass{keep-bullets}
-@divEnd
-@divEnd
-@divClass{column-center-bottom}
-@subheading Where now?
-@ref{Text input}.
-@divEnd
-@node testimonials
-@unnumberedsec Testimonials
-
-@untranslated
-
-
-@divClass{testimonial-item}
-@imageFloat{carter-brey.jpg, right}
-@subsubheading @uref{http://nyphil.org/meet/orchestra/index.cfm?page=profile&personNum=7, Carter Brey}, Principal Cellist, New York Philharmonic
-@divEnd
-@divClass{testimonial-item}
-@imageFloat{orm-finnendahl.jpg, left}
-@subsubheading @uref{http://icem-www.folkwang-hochschule.de/~finnendahl/, Orm Finnendahl}, professor of Composition, Musikhochschule Freiburg
-@divEnd
-@divClass{testimonial-item}
-@imageFloat{darius-blasband.jpg, right}
-@subsubheading Darius Blasband, composer (Brussels, Belgium)
-@divEnd
-@divClass{testimonial-item}
-@subsubheading Kieren MacMillan, composer (Toronto, Canada)
-@divEnd
-@divClass{testimonial-item}
-@subsubheading Chris Cannam, lead programmer of the @uref{http://www.rosegardenmusic.com/, RoseGarden} project.
-@divEnd
-@divClass{testimonial-item}
-@subsubheading Chris Snyder, @uref{http://www.adoromusicpub.com/, Adoro Music Publishing}
-@divEnd
-@divClass{testimonial-item}
-@subsubheading David Bobroff, Bass Trombone, Iceland Symphony Orchestra
-@divEnd
-@divClass{testimonial-item}
-@subsubheading Vaylor Trucks, Electric guitar player (Yes, @uref{http://www.allmanbrothersband.com/modules.php?op=modload&name=userpage&file=content&page_id=12, related to})
-@divEnd
-@divClass{testimonial-item}
-@subsubheading @uref{http://nicolas.sceaux.free.fr/, Nicolas Sceaux}, @uref{http://www.mutopiaproject.org/, Mutopia} contributor
-@divEnd
-@divClass{testimonial-item}
-@subsubheading @uref{http://www.troff.org/whoswho.html#werner, Werner Lemberg}, Conductor at the Theatre in Koblenz, Germany and distinguished GNU Hacker.
-@divEnd
-@divClass{testimonial-item}
-@subsubheading Paul Davis, developer of @uref{http://jackaudio.org/, JACK} and @uref{http://www.ardour.org/, Ardour}.
-@divEnd
-@divClass{column-center-bottom}
-@subheading Where now?
-@divEnd
-@node text input
-@unnumberedsec Text input
-
-@untranslated
-
-
-@c TRANSLATORS: so far it's mostly from
-@c http://lilypond.org/web/switch/howto
-@subheading @qq{Compiling} Music
-@imageClickable{examples/nereid-shot-small.png, (click to enlarge), examples/nereid-shot.png, right}
-@subsubheading It's as simple as A B C
-@imageFloat{text-input-1-annotate.png,center}
-@imageFloat{text-input-1-output.png,center}
-@imageFloat{text-input-2-annotate.png,center}
-@imageFloat{text-input-2-output.png,center}
-@subsubheading Pop music
-@imageFloat{text-input-pop-annotate.png,center}
-@imageFloat{text-input-pop-output.png,center}
-@subsubheading Orchestral parts
-@imageFloat{text-input-parts-both-annotate.png,center}
-@imageFloat{text-input-parts-single-annotate.png,center}
-@imageFloat{text-input-parts-single-output.png,center}
-@imageFloat{text-input-score-annotate.png,center}
-@imageFloat{text-input-score-output.png,center}
-@subsubheading Beginner Documentation
-@subsubheading Easier editing environments
-@divClass{column-center-bottom}
-@subheading Where now?
-@ref{Freedom} that LilyPond provides, or read about users'
-@ref{Productions} and @ref{Testimonials}.
-@divEnd
+++ /dev/null
-@c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
-@c This file is part of general.texi
-@ignore
- Translation of GIT committish: dab17828471057f4e12c0d80777ff9bb4c5b2309
-
- When revising a translation, copy the HEAD committish of the
- version that you are working on. See TRANSLATION for details.
-@end ignore
-
-@node handleiding
-@unnumbered Handleiding
-@translationof manuals
-
-@divClass{heading-center}
-@heading Documentation for LilyPond 2.12.2
-@divEnd
-@divClass{column-center-top}
-@subheading Introduction
-@divEnd
-@divClass{column-left-top}
-@subheading Regular use
-@divEnd
-@divClass{column-right-top}
-@subheading Infrequent Use
-@divEnd
-@divClass{column-center-bottom}
-@subheading Other material
-@divEnd
-@divClass{hide}
-@menu
-* learning::
-* glossary::
-* essay::
-* notation::
-* usage::
-* snippets::
-* FAQ::
-* changes::
-* internals::
-* translated::
-* old::
-* FDL::
-@end menu
-
-@divEnd
-@c TRANSLATORS: most of the text in this file came from
-@c LM 1.1 About the documentation (before this section was
-@c removed in July 2009).
-@node learning
-@unnumberedsec Learning
-
-@untranslated
-
-
-@node glossary
-@unnumberedsec Glossary
-
-@untranslated
-
-
-@node essay
-@unnumberedsec Essay
-
-@untranslated
-
-
-@node notation
-@unnumberedsec Notation
-
-@untranslated
-
-
-@node usage
-@unnumberedsec Usage
-
-@untranslated
-
-
-@node snippets
-@unnumberedsec Snippets
-
-@untranslated
-
-
-@node FAQ
-@unnumberedsec FAQ
-
-@untranslated
-
-
-@subheading Where are the graphical canvas, menus, and toolbars?
-@subheading There's a lot of documentation! Do I need to read it?
-@subheading That's still a lot of reading! Is it worth it?
-@subheading Something isn't working! How do I fix it?
-@subheading Why do you change the syntax?
-@node changes
-@unnumberedsec Changes
-
-@untranslated
-
-
-@node internals
-@unnumberedsec Internals
-
-@untranslated
-
-
-@node translated
-@unnumberedsec Translated
-
-@untranslated
-
-
-@node old
-@unnumberedsec Old
-
-@untranslated
-
-
-@node FDL
-@unnumberedsec FDL
-
-@untranslated
-
-
-@divClass{column-center-top}
-@subheading Documentation license
-@divEnd
-@divClass{column-center-bottom}
-@subheading GNU Free Documentation License 1.1
-@include fdl.itexi
-@divEnd
-
-@c -- SKELETON FILE --
+++ /dev/null
-@c -*- coding: utf-8; mode: texinfo; -*-
-@c This file is part of lilypond-general.texi and community.itexi
-
-@c when you add a new item, consider moving the lowest item(s)
-@c into news-old.itexi.
-
-@newsItem
-@subsubheading New Website! @emph{20 Aug 2009}
-
-As you can see, we have a new website design. Many thanks to
-texi2html and CSS for being so flexible!
-
-(FIXME: change date when this is actually announced on lilypond.org)
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond 2.13.3. @emph{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. For changes and download links, see @ref{Development}.
-@newsEnd
-
-
-
-@newsItem
-@subsubheading Hungarian translation! @emph{22 May 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!
-@newsEnd
-
-
-@newsItem
-@subsubheading LilyPond Report #15. @emph{18 May 2009}
-
-The @emph{LilyPond Report} is a short, informal opinion column
-about the LilyPond project: its team, its world, its community.
-Read it @uref{http://news.lilynet.net/The-LilyPond-Report-15,
-here}!
-@newsEnd
-
-
--- /dev/null
+\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
+@c This file is part of web.texi
+@ignore
+ Translation of GIT committish: 1b3da70d81938d19a2b107382bbe25a267cf130b
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+
+@setfilename web.info
+@settitle LilyPond -- Muzieknotatie voor iedereen
+@documentencoding UTF-8
+@documentlanguage nl
+@set web
+@include macros.itexi
+@afourpaper
+@ifnottex
+@node Top
+@top
+@translationof Top
+
+
+@chapheading
+@end ifnottex
+@finalout
+@titlepage
+@title LilyPond
+@subtitle
+@titlefont{New Website}
+@author Het LilyPond ontwikkelteam
+@quotation
+@end quotation
+@vskip 20pt
+@end titlepage
+@copying
+@quotation
+@end quotation
+@end copying
+@divId{pageHeader}
+@heading LilyPond
+
+... muzieknotatie voor iedereen
+@divEnd
+@c @imageId{cmws,web-clef-g-eight-alpha.png,Catchy Musical Web Snippet}
+@imageId{lilylogo,double-lily-modified3.png,LilyPond logo}
+@c @im ageId{cmws,web-snippet-alpha.png,Catchy Musical Web Snippet}
+@divId{quickSummary}
+@subheading Wat is LilyPond?
+
+LilyPond is een Open Source muziek-graveer programma, gewijd aan
+het produceren van de hoogst mogelijke kwaliteit bladmuziek.
+
+Wij brengen de esthetiek van traditioneel gegraveerde muziek naar
+computer afdrukken.
+
+LilyPond is Vrije Software, is gratis en is onderdeel van het
+@uref{http://@/www@/.gnu@/.org/, GNU} project.
+
+@divClass{align-right}
+Lees de @ref{Inleiding}!
+
+@c For this to work, essay needs to be split like we are
+@c --split=node --node-files
+@c Dat en meer in ons @ressaynamed{Engraving, essay}.
+@c Possibly, node Top always works?
+@c Dat en meer in ons @ressaynamed{Top, essay}.
+Dat en meer in ons @ref{automated-engraving,,Essay,essay,Essay}.
+
+@divEnd
+@divEnd
+@divId{news}
+@include news-front.itexi
+@divClass{float-right}
+@divEnd
+@divEnd
+@divId{latestVersion}
+@subheading Quick links
+@c TODO: javascript to detect OS and suggest download?
+@subsubheading Stable
+@ref{Download, Download 2.12.3}
+@ref{Handleiding, Handleiding 2.12.3}
+@subsubheading Unstable
+@ref{Development, Download 2.13.2}
+@ref{Handleiding, Handleiding 2.13.2}
+@divEnd
+@divClass{hide}
+@menu
+* inleiding::
+* download::
+* handleiding::
+* community::
+@end menu
+
+@divEnd
+@contents
+@include web/introduction.itexi
+@include web/download.itexi
+@include web/manuals.itexi
+@include web/community.itexi
+@bye
+
--- /dev/null
+depth = ../../..
+
+LOCALSTEPMAKE_TEMPLATES = ly
+
+include $(depth)/make/stepmake.make
--- /dev/null
+@c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
+@c This file is part of web.texi
+@ignore
+ Translation of GIT committish: 1b3da70d81938d19a2b107382bbe25a267cf130b
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+
+@c -*- coding: utf-8; mode: texinfo; -*-
+@node community
+@unnumbered Community
+
+@untranslated
+
+
+@divClass{column-center-top}
+@subheading Interacting with the community
+@ref{Contact}: get help, discuss, and keep in touch!
+@ref{Tiny examples}: these are @emph{highly} recommended when
+@ref{Bug reports}: something went wrong.
+@divEnd
+@divClass{column-left-bottom}
+@subheading Making LilyPond better
+@ref{Help us}: your assistance is requested.
+@ref{Development}: for contributors and testers.
+@ref{Authors}: the people who made LilyPond what it is today.
+@divEnd
+@divClass{column-right-bottom}
+@subheading Miscellaneous
+@ref{Publications}: what we wrote, and have had written about us.
+@ref{Old news}: an archive.
+@divEnd
+@divClass{hide}
+@menu
+* contact::
+* tiny examples::
+* bug reports::
+* help us::
+* development::
+* authors::
+* publications::
+* old news::
+@end menu
+
+@divEnd
+@node contact
+@unnumberedsec Contact
+
+@untranslated
+
+
+@divClass{column-left-bottom}
+@subheading User Discussions and Help
+@subsubheading User mailist: @code{lilypond-user@@gnu.org}
+@quotation
+@end quotation
+@subsubheading IRC
+@subsubheading Other languages
+@divEnd
+@divClass{column-right-top}
+@subheading Stay Informed
+@subsubheading LilyPond Report
+@subsubheading Releases mailist: @code{info-lilypond@@gnu.org}
+@quotation
+@c don't include gmane posting here. -gp
+@end quotation
+@divEnd
+@divClass{column-right-bottom}
+@subheading Developer Discussion
+@subsubheading Developer mailist: @code{lilypond-devel@@gnu.org}
+@quotation
+@end quotation
+@subsubheading Bug mailist: @code{bug-lilypond@@gnu.org}
+@quotation
+@c don't include gmane posting here. -gp
+@end quotation
+@divEnd
+@node tiny examples
+@unnumberedsec Tiny examples
+
+@untranslated
+
+
+@divClass{column-center-top}
+@subheading What are @qq{Tiny examples}?
+@divEnd
+@divClass{column-left-bottom}
+@subheading Why create them?
+@divClass{keep-bullets}
+@divEnd
+@divEnd
+@divClass{column-right-bottom}
+@subheading How do I create them?
+@divClass{keep-bullets}
+@divEnd
+@divEnd
+@node bug reports
+@unnumberedsec Bug reports
+
+@untranslated
+
+
+@divClass{column-center-top}
+@subheading Step 1: Known bugs
+@divEnd
+@divClass{column-left-bottom}
+@subheading Step 2: Creating a bug report
+@divEnd
+@divClass{column-right-bottom}
+@subheading Step 3: Sending a bug report
+@divEnd
+@node help us
+@unnumberedsec Help us
+
+@untranslated
+
+
+@subheading This document
+@subsubheading High priority / blocks release
+@subsubheading Low priority / may never
+@node development
+@unnumberedsec Development
+
+@untranslated
+
+
+@divClass{heading-center}
+@heading Development materials for LilyPond 2.13.3
+@ref{Handleiding}.}
+@divEnd
+@divClass{column-left-bottom}
+@subheading Download
+@subheading Manuals
+@divEnd
+@divClass{column-right-bottom}
+@subheading Contributors' Guide
+@divEnd
+@node authors
+@unnumberedsec Authors
+
+@untranslated
+
+
+@node publications
+@unnumberedsec Publications
+
+@untranslated
+
+
+@divClass{column-center-top}
+@subheading What we wrote
+@divClass{keep-bullets}
+@divEnd
+@divEnd
+@divClass{column-center-bottom}
+@subheading What others wrote
+@divClass{keep-bullets}
+@divEnd
+@divEnd
+@node old news
+@unnumberedsec Old news
+
+@untranslated
+
+
+@include general/news.itexi
+
+@c -- SKELETON FILE --
--- /dev/null
+\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
+@c This file is part of web.texi
+@ignore
+ Translation of GIT committish: dab17828471057f4e12c0d80777ff9bb4c5b2309
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+
+@c -*- coding: utf-8; mode: texinfo; -*-
+@node download
+@unnumbered Download
+
+@untranslated
+
+
+@divClass{heading-center}
+@heading Downloads for LilyPond 2.12.2
+@divEnd
+@divClass{column-left-top}
+@subheading For users
+@c TODO: duplicate to avoid underlined refs in HTML? icky.
+@ref{Unix, @sourceimage{logo-linux} @sourceimage{logo-freebsd}}
+@ref{Unix, Unix (Linux and FreeBSD)}
+@ref{MacOS X, @sourceimage{logo-macosx}}
+@ref{MacOS X, MacOS X}
+@ref{Windows, @sourceimage{logo-windows}}
+@ref{Windows, Microsoft Windows}
+@divEnd
+@divClass{column-right-top}
+@subheading For developers
+@ref{Source}:
+@ref{Old downloads}:
+@divEnd
+@divClass{column-center-bottom}
+@subheading Software License
+@divEnd
+@divClass{color1}
+@subheading Sponsors
+@sourceimage{VTlogo_ITF} @sourceimage{lao_banner_06_on_white_demo}
+@subheading Legalese
+@divClass{legal}
+@divEnd
+@divEnd
+@divClass{hide}
+@menu
+* UNIX::
+* MacOS X::
+* Windows::
+* source::
+* old downloads::
+* GPL::
+@end menu
+
+@divEnd
+@node UNIX
+@unnumberedsec UNIX
+
+@untranslated
+
+
+@divClass{column-center-top}
+@subheading Generic Packages or Distribution-Specific Packages?
+@divEnd
+@divClass{column-left-top}
+@subheading Generic Packages
+@subsubheading Download
+@sourceimage{logo-linux}
+@sourceimage{logo-linux}
+@sourceimage{logo-linux}
+@sourceimage{logo-freebsd}
+@sourceimage{logo-freebsd}
+@subsubheading Install
+@subsubheading Uninstall
+@divEnd
+@divClass{column-right-top}
+@subheading Distribution-specific Packages
+@sourceimage{logo-fedora}
+@sourceimage{logo-ubuntu}
+@sourceimage{logo-slackware}
+@sourceimage{logo-debian}
+@sourceimage{logo-suse}
+@divEnd
+@divClass{column-center-bottom}
+@subheading Legalese
+@divClass{legal}
+@divEnd
+@divEnd
+@node MacOS X
+@unnumberedsec MacOS X
+
+@untranslated
+
+
+@divClass{column-left-top}
+@subheading Packages
+@subsubheading Download
+@sourceimage{logo-macosx}
+@sourceimage{logo-macosx}
+@subsubheading Install
+@subsubheading Uninstall
+@divEnd
+@divClass{column-right-top}
+@subheading Running on the command-line
+@subsubheading Using Python scripts on MacOS 10.3 or 10.4
+@c ommand{convert-ly} and @command{lilypond-book} as follows: if the
+@subsubheading MacOS X on the command line
+@c ommand{abc2ly}, and even @command{lilypond} itself --- are included
+@c ommand{lilypond-book}, @command{convert-ly}, @command{abc2ly}, etc.
+@c ode{bin/convert-ly} (or other program name) in the above file.
+@divEnd
+@divClass{column-center-bottom}
+@subheading Legalese
+@divClass{legal}
+@divEnd
+@divEnd
+@node Windows
+@unnumberedsec Windows
+
+@untranslated
+
+
+@divClass{column-left-top}
+@subheading Packages
+@subsubheading Download
+@sourceimage{logo-windows}
+@subsubheading Install
+@subsubheading Uninstall
+@divEnd
+@divClass{column-right-top}
+@subheading Running on the command-line
+@divEnd
+@divClass{column-center-bottom}
+@subheading Legalese
+@divClass{legal}
+@divEnd
+@divEnd
+@node source
+@unnumberedsec Source
+
+@untranslated
+
+
+@divClass{column-left-bottom}
+@subheading Source tarball
+@divEnd
+@divClass{column-right-bottom}
+@subheading Compiling instructions
+@divEnd
+@node old downloads
+@unnumberedsec Old downloads
+
+@untranslated
+
+
+@divClass{column-center-top}
+@subheading All versions
+@divEnd
+@node GPL
+@unnumberedsec GPL
+
+@untranslated
+
+
+@divClass{column-center-top}
+@subheading Software license
+@divEnd
+@divClass{column-center-bottom}
+@subheading GNU General Public License version 2
+@include gpl-2.0.itexi
+@divEnd
+
+@c -- SKELETON FILE --
--- /dev/null
+\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
+@c This file is part of web.texi
+@ignore
+ Translation of GIT committish: dab17828471057f4e12c0d80777ff9bb4c5b2309
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+@node inleiding
+@unnumbered Inleiding
+@translationof introduction
+
+@divClass{column-center-top}
+@subheading Ons Doel
+@imageFloat{flat-design.png,right}
+
+De inspiratie voor LilyPond ontstond toen twee bevriende muzikanten
+ontevreden werden met het saaie en inspiratieloze uiterlijk van
+computerafdrukken. Elke muzikant leest liever mooie muziek, dus
+zouden wij als programmeurs dat afdrukprobleem niet kunnen oplossen?
+
+Dat is nu precies wat LilyPond doet: het drukt muziek volgens de
+beste tradities van klassieke muziekgravure, zonder gedoe. Verspil
+geen tijd met het bijstellen van spatiëring, het verplaatsen van
+tekens, of met het vormgeven van legatoboogjes. Imponeer vrienden
+en collega's met haarscherpe bladmuziek!
+@divEnd
+
+@divClass{column-left-top}
+@subheading Why use LilyPond?
+@ref{Features}: What can LilyPond do?
+@ref{Examples}: I want to see some music!
+@ref{Freedom}: LilyPond is Free Software.
+@divEnd
+@divClass{column-right-top}
+@subheading Who uses it?
+@ref{Productions}: Real-life use of LilyPond.
+@ref{Testimonials}: What do people say?
+@divEnd
+@divClass{column-center-bottom}
+@subheading Why not use LilyPond?
+@ref{Text input}: You write music as @emph{text}?!
+@divEnd
+@divClass{hide}
+@menu
+* features::
+* examples::
+* freedom::
+* productions::
+* testimonials::
+* text input::
+@end menu
+
+@divEnd
+@node features
+@unnumberedsec features
+
+@untranslated
+
+
+@subheading Why switch to LilyPond?
+@subsubheading Excellent classical engraving
+@imageFloat{flat-design.png,right}
+@subsubheading No fiddling
+@subsubheading Text-based input
+@subsubheading Mix music and text
+@imageFloat{lilypond-book.png,right}
+@subsubheading Free software
+@subsubheading Extensible design
+@subsubheading Excellent support
+@divClass{column-center-bottom}
+@subheading Where now?
+@ref{Text input}.
+@divEnd
+@node examples
+@unnumberedsec Examples
+
+@untranslated
+
+
+@imageClickable{examples/liszt-wagner-small.png, (click to enlarge), examples/liszt-wagner.png, center}
+@subsubheading Classical Music
+@imageClickable{examples/bach-bwv610-small.png, (click to enlarge), examples/bach-bwv610.png, center}
+@subsubheading Complex Notation
+@imageClickable{examples/granados-small.png, (click to enlarge), examples/granados.png, center}
+@subsubheading Early Music
+@imageClickable{examples/ancient-headword-small.png, (click to enlarge), examples/ancient-headword.png, center}
+@subsubheading Modern Music
+@imageClickable{examples/cary-small.png, (click to enlarge), examples/cary.png, center}
+@subsubheading Efficient, flexible creation of performance materials
+@imageClickable{examples/sesto-small.png, (click to enlarge), examples/sesto.png, center}
+@imageClickable{examples/sesto-1-small.png, (click to enlarge), examples/sesto-1.png, center}
+@imageClickable{examples/sesto-2-small.png, (click to enlarge), examples/sesto-2.png, center}
+@subsubheading Tablature
+@imageClickable{examples/bach-tab-example-small.png, (click to enlarge), examples/bach-tab-example.png, center}
+@subsubheading Schenker Graphs
+@imageClickable{examples/bach-schenker-small.png, (click to enlarge), examples/bach-schenker.png, center}
+@subsubheading Vocal Music
+@imageClickable{examples/aucun-snippet-small.png, (click to enlarge), examples/aucun-snippet.png, center}
+@subsubheading Educational Applications
+@imageClickable{examples/theory-small.png, (click to enlarge), examples/theory.png, center}
+@subsubheading Popular Music
+@imageClickable{examples/chart-small.png, (click to enlarge), examples/chart.png, center}
+@subsubheading Large Projects
+@imageClickable{examples/orchestral-small.png, (click to enlarge), examples/orchestral.png, center}
+@divClass{column-center-bottom}
+@subheading Where now?
+@ref{Freedom}. If you've already decided to try LilyPond, first
+@divEnd
+@node freedom
+@unnumberedsec Freedom
+
+@untranslated
+
+
+@divClass{column-center-top}
+@subheading Free Software
+@ref{GPL, GNU General Public License} and the @ref{FDL, GNU Free
+@divEnd
+@c @divClass{column-left-top}
+@divClass{color2}
+@divClass{keep-bullets}
+@subheading What are the benefits to users?
+@divEnd
+@divEnd
+@c @divClass{column-right-top}
+@divClass{color3}
+@divClass{keep-bullets}
+@subheading Why do LilyPond developers @qq{give away} their work for free?
+@divEnd
+@divEnd
+@divClass{column-center-bottom}
+@subheading Where now?
+@ref{Productions} and sheet music. If you've already decided to
+@divEnd
+@node productions
+@unnumberedsec Productions
+
+@untranslated
+
+
+@divClass{column-left-top}
+@subheading Concerts
+@divClass{keep-bullets}
+@divEnd
+@divEnd
+@divClass{column-right-top}
+@subheading Published sheet music
+@divClass{keep-bullets}
+@divEnd
+@divEnd
+@divClass{column-center-bottom}
+@subheading Where now?
+@ref{Text input}.
+@divEnd
+@node testimonials
+@unnumberedsec Testimonials
+
+@untranslated
+
+
+@divClass{testimonial-item}
+@imageFloat{carter-brey.jpg, right}
+@subsubheading @uref{http://nyphil.org/meet/orchestra/index.cfm?page=profile&personNum=7, Carter Brey}, Principal Cellist, New York Philharmonic
+@divEnd
+@divClass{testimonial-item}
+@imageFloat{orm-finnendahl.jpg, left}
+@subsubheading @uref{http://icem-www.folkwang-hochschule.de/~finnendahl/, Orm Finnendahl}, professor of Composition, Musikhochschule Freiburg
+@divEnd
+@divClass{testimonial-item}
+@imageFloat{darius-blasband.jpg, right}
+@subsubheading Darius Blasband, composer (Brussels, Belgium)
+@divEnd
+@divClass{testimonial-item}
+@subsubheading Kieren MacMillan, composer (Toronto, Canada)
+@divEnd
+@divClass{testimonial-item}
+@subsubheading Chris Cannam, lead programmer of the @uref{http://www.rosegardenmusic.com/, RoseGarden} project.
+@divEnd
+@divClass{testimonial-item}
+@subsubheading Chris Snyder, @uref{http://www.adoromusicpub.com/, Adoro Music Publishing}
+@divEnd
+@divClass{testimonial-item}
+@subsubheading David Bobroff, Bass Trombone, Iceland Symphony Orchestra
+@divEnd
+@divClass{testimonial-item}
+@subsubheading Vaylor Trucks, Electric guitar player (Yes, @uref{http://www.allmanbrothersband.com/modules.php?op=modload&name=userpage&file=content&page_id=12, related to})
+@divEnd
+@divClass{testimonial-item}
+@subsubheading @uref{http://nicolas.sceaux.free.fr/, Nicolas Sceaux}, @uref{http://www.mutopiaproject.org/, Mutopia} contributor
+@divEnd
+@divClass{testimonial-item}
+@subsubheading @uref{http://www.troff.org/whoswho.html#werner, Werner Lemberg}, Conductor at the Theatre in Koblenz, Germany and distinguished GNU Hacker.
+@divEnd
+@divClass{testimonial-item}
+@subsubheading Paul Davis, developer of @uref{http://jackaudio.org/, JACK} and @uref{http://www.ardour.org/, Ardour}.
+@divEnd
+@divClass{column-center-bottom}
+@subheading Where now?
+@divEnd
+@node text input
+@unnumberedsec Text input
+
+@untranslated
+
+
+@c TRANSLATORS: so far it's mostly from
+@c http://lilypond.org/web/switch/howto
+@subheading @qq{Compiling} Music
+@imageClickable{examples/nereid-shot-small.png, (click to enlarge), examples/nereid-shot.png, right}
+@subsubheading It's as simple as A B C
+@imageFloat{text-input-1-annotate.png,center}
+@imageFloat{text-input-1-output.png,center}
+@imageFloat{text-input-2-annotate.png,center}
+@imageFloat{text-input-2-output.png,center}
+@subsubheading Pop music
+@imageFloat{text-input-pop-annotate.png,center}
+@imageFloat{text-input-pop-output.png,center}
+@subsubheading Orchestral parts
+@imageFloat{text-input-parts-both-annotate.png,center}
+@imageFloat{text-input-parts-single-annotate.png,center}
+@imageFloat{text-input-parts-single-output.png,center}
+@imageFloat{text-input-score-annotate.png,center}
+@imageFloat{text-input-score-output.png,center}
+@subsubheading Beginner Documentation
+@subsubheading Easier editing environments
+@divClass{column-center-bottom}
+@subheading Where now?
+@ref{Freedom} that LilyPond provides, or read about users'
+@ref{Productions} and @ref{Testimonials}.
+@divEnd
--- /dev/null
+@c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
+@c This file is part of web.texi
+@ignore
+ Translation of GIT committish: dab17828471057f4e12c0d80777ff9bb4c5b2309
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+@node handleiding
+@unnumbered Handleiding
+@translationof manuals
+
+@divClass{heading-center}
+@heading Documentation for LilyPond 2.12.2
+@divEnd
+@divClass{column-center-top}
+@subheading Introduction
+@divEnd
+@divClass{column-left-top}
+@subheading Regular use
+@divEnd
+@divClass{column-right-top}
+@subheading Infrequent Use
+@divEnd
+@divClass{column-center-bottom}
+@subheading Other material
+@divEnd
+@divClass{hide}
+@menu
+* learning::
+* glossary::
+* essay::
+* notation::
+* usage::
+* snippets::
+* FAQ::
+* changes::
+* internals::
+* translated::
+* old::
+* FDL::
+@end menu
+
+@divEnd
+@c TRANSLATORS: most of the text in this file came from
+@c LM 1.1 About the documentation (before this section was
+@c removed in July 2009).
+@node learning
+@unnumberedsec Learning
+
+@untranslated
+
+
+@node glossary
+@unnumberedsec Glossary
+
+@untranslated
+
+
+@node essay
+@unnumberedsec Essay
+
+@untranslated
+
+
+@node notation
+@unnumberedsec Notation
+
+@untranslated
+
+
+@node usage
+@unnumberedsec Usage
+
+@untranslated
+
+
+@node snippets
+@unnumberedsec Snippets
+
+@untranslated
+
+
+@node FAQ
+@unnumberedsec FAQ
+
+@untranslated
+
+
+@subheading Where are the graphical canvas, menus, and toolbars?
+@subheading There's a lot of documentation! Do I need to read it?
+@subheading That's still a lot of reading! Is it worth it?
+@subheading Something isn't working! How do I fix it?
+@subheading Why do you change the syntax?
+@node changes
+@unnumberedsec Changes
+
+@untranslated
+
+
+@node internals
+@unnumberedsec Internals
+
+@untranslated
+
+
+@node translated
+@unnumberedsec Translated
+
+@untranslated
+
+
+@node old
+@unnumberedsec Old
+
+@untranslated
+
+
+@node FDL
+@unnumberedsec FDL
+
+@untranslated
+
+
+@divClass{column-center-top}
+@subheading Documentation license
+@divEnd
+@divClass{column-center-bottom}
+@subheading GNU Free Documentation License 1.1
+@include fdl.itexi
+@divEnd
+
+@c -- SKELETON FILE --
--- /dev/null
+@c -*- coding: utf-8; mode: texinfo; -*-
+@c This file is part of lilypond-web.texi and community.itexi
+
+@c when you add a new item, consider moving the lowest item(s)
+@c into news-old.itexi.
+
+@newsItem
+@subsubheading New Website! @emph{20 Aug 2009}
+
+As you can see, we have a new website design. Many thanks to
+texi2html and CSS for being so flexible!
+
+(FIXME: change date when this is actually announced on lilypond.org)
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.13.3. @emph{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. For changes and download links, see @ref{Development}.
+@newsEnd
+
+
+
+@newsItem
+@subsubheading Hungarian translation! @emph{22 May 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!
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond Report #15. @emph{18 May 2009}
+
+The @emph{LilyPond Report} is a short, informal opinion column
+about the LilyPond project: its team, its world, its community.
+Read it @uref{http://news.lilynet.net/The-LilyPond-Report-15,
+here}!
+@newsEnd
+
+
@ignore
@include macros.itexi
-@include general/basic-authors.itexi
+@include web/basic-authors.itexi
@developersCurrent
run on the command line; see @ref{Command-line usage} for more
information. If you have MacOS 10.3 or 10.4 and you have trouble
running some of these scripts, e.g. @code{convert-ly}, see
-@rgeneral{MacOS X}.
+@rweb{MacOS X}.
@knownissues
LilyPond itself does not come with support for any other formats,
but some external tools can also generate LilyPond files. These
-are listed in @rgeneral{Alternate editors}.
+are listed in @rweb{Alternate editors}.
This is a separate program from @command{lilypond} itself, and is run
on the command line; for more information, see @ref{Command-line
usage}. If you have MacOS 10.3 or 10.4 and you have trouble running
-@code{lilypond-book}, see @rgeneral{MacOS X}.
+@code{lilypond-book}, see @rweb{MacOS X}.
This procedure may be applied to @LaTeX{}, HTML, Texinfo or DocBook
documents.
Windows users might be more familiar with the terms @q{DOS shell} or
@q{command shell}. MacOS@tie{}X users might be more familiar with the terms
@q{terminal} or @q{console}. Some additional setup is required
-for MacOS@tie{}X users; please see @rgeneral{MacOS X}.
+for MacOS@tie{}X users; please see @rweb{MacOS X}.
Describing how to use this part of an operating system is outside the
scope of this manual; please consult other documentation on this topic
Other editors (both text and graphical) support LilyPond, but
their special configuration files are not distributed with
LilyPond. Consult their documentation for more information. Such
-editors are listed in @rgeneral{Alternate editors}.
+editors are listed in @rweb{Alternate editors}.
@code{bass} part until you find the problem line.
Another very useful debugging technique is constructing
-@rgeneral{Tiny examples}.
+@rweb{Tiny examples}.
@node Make and Makefiles
--- /dev/null
+\input texinfo @c -*- coding: utf-8; mode: texinfo; -*-
+@ignore
+ Translation of GIT committish: FILL-IN-HEAD-COMMITTISH
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+@setfilename web.info
+@settitle LilyPond -- Music notation for everyone
+@documentencoding UTF-8
+@documentlanguage en
+@afourpaper
+
+@set FDL
+@set web
+@include macros.itexi
+
+@afourpaper
+
+@c don't remove this comment.
+@ignore
+@omfcreator Graham Percival and Patrick McCarty
+@omfdescription General info about the LilyPond music engraving system
+@omftype program usage
+@omfcategory Applications|Publishing
+@omflanguage English
+@end ignore
+
+
+@copying
+Copyright @copyright{} 2009 by the authors.
+
+@quotation
+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''.
+@end quotation
+@end copying
+
+
+@c TITLE PAGE
+@ifnottex
+@node Top
+@top LilyPond... music notation for everyone
+@end ifnottex
+
+
+@c hack for texi2html, bleh -gp
+@ifnothtml
+
+@finalout
+
+@titlepage
+@title LilyPond
+@subtitle The music typesetter
+@titlefont{General Information}
+@author The LilyPond development team
+
+@vskip 0pt plus 1filll
+@c @vskip 20pt
+
+@insertcopying{}
+
+For LilyPond version @version{}
+@end titlepage
+@end ifnothtml
+@c end hack for texi2html
+
+
+@c ************************ WEBSITE START ***************
+
+
+@divId{pageHeader}
+@heading LilyPond
+
+... music notation for everyone
+@divEnd
+
+@c @imageId{cmws,web-clef-g-eight-alpha.png,Catchy Musical Web Snippet}
+@imageId{lilylogo,double-lily-modified3,png,LilyPond logo}
+@c @im ageId{cmws,web-snippet-alpha.png,Catchy Musical Web Snippet}
+
+@divId{quickSummary}
+@subheading 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.
+
+@divClass{align-right}
+Read more in our @ref{introduction}!
+
+@divEnd
+@divEnd
+
+@divClass{separator}
+@divEnd
+
+
+@divId{news}
+
+@c TODO: generate this automatically, including RSS feed.
+@include web/news-front.itexi
+
+@divClass{float-right}
+(@ref{old news})
+@divEnd
+
+@divEnd
+
+
+@divId{latestVersion}
+@subheading Quick links
+
+@c TODO: javascript to detect OS and suggest download?
+
+@subsubheading Stable
+
+@ref{download, Download @versionStable}
+
+@ref{manuals, Manuals @versionStable}
+
+@subsubheading Unstable
+
+@ref{development, Download @versionDevel}
+
+@ref{development, Manuals @versionDevel}
+
+@divEnd
+
+
+@ifnottex
+
+@divClass{hide}
+@menu
+* introduction:: Start here to creating sheet music.
+* download:: Get LilyPond.
+* manuals:: Read The Fine Manuals (RTFM).
+* community:: Contact other users.
+@end menu
+@divEnd
+
+@end ifnottex
+
+@contents
+
+
+@include web/introduction.itexi
+@include web/download.itexi
+@include web/manuals.itexi
+@include web/community.itexi
+
+@bye
--- /dev/null
+depth = ../..
+LOCALSTEPMAKE_TEMPLATES = ly
+SUBDIRS = examples
+include $(depth)/make/stepmake.make
--- /dev/null
+@c -*- coding: utf-8; mode: texinfo; -*-
+@c This file is part of community.itexi and ../topdocs/AUTHORS.itexi
+
+@ignore
+
+ This file lists authors of LilyPond, and what they wrote. Each
+ list is sorted alphabetically by surname. This file lists people
+ that have contributed more than a few hours of work.
+
+ Developers are people who are (or have been) listed under the
+ "Development Team" in the THANKS, and can choose their own
+ titles. Contributors are everybody else, and simply list their
+ contributions.
+
+ Anybody who has finished doing a "main devel team" task should
+ list it under developersPrevious, even if they're still doing
+ other "main devel team" stuff. See "Graham Percival" for an
+ example.
+
+ Contributors are split into:
+ ...Core (programming)
+ ...Font (duh)
+ ...Doc (documentation and examples)
+ ...Support (building, distributions, editors,
+ lilypond-book, LSR, but *not* answering emails)
+ ...Translations (duh)
+ We might add a "general" or "other" if there's something else.
+
+
+@end ignore
+
+@macro developersCurrent
+
+@itemize
+
+@item Mats Bengtsson:
+Support guru.
+
+@item Han-Wen Nienhuys:
+Main author.
+
+@item Jan Nieuwenhuizen:
+Main author.
+
+@item @uref{http://percival-music.ca, Graham Percival}:
+Project Manager.
+
+@end itemize
+@end macro
+
+
+
+@macro developersPrevious
+
+@itemize
+@item Pedro Kroeger:
+Build meister
+
+@item @uref{http://percival-music.ca, Graham Percival}:
+Documentation editor, Bug meister, Grand Documentation Project
+leader.
+
+@item Erik Sandberg:
+Bug meister
+
+@end itemize
+@end macro
+
+
+
+@macro contributorsCore
+
+@itemize
+@item Erlend Aasland:
+Color support, tablature improvements, trivial @code{\\mark} stuff,
+al-niente hairpins.
+
+@end itemize
+@end macro
+
+
+
+@macro contributorsFont
+
+@itemize
+@item @uref{http://www.juergen-reuter.de, Jürgen Reuter}:
+Ancient notation font Exact Type1 font outlines for feta,
+feta-alphabet.
+
+@end itemize
+@end macro
+
+
+
+@macro contributorsDoc
+
+@itemize
+@item @uref{http://www.s3.kth.se/~mabe/, Mats Bengtsson}:
+Example files, documentation
+
+
+@end itemize
+@end macro
+
+
+
+@macro contributorsSupport
+
+@itemize
+@item Anthony Fok:
+Debian package: @file{debian/*}.
+
+@end itemize
+@end macro
+
+
+
+@macro contributorsTranslations
+
+@itemize
+@item Bjoern Jacke:
+German glossary translations.
+
+
+@end itemize
+@end macro
+
+
+
+
+@ignore
+ OLD MATERIAL
+
+Core code:
+
+@itemize @bullet
+@item @email{erlenda@@gmail.com,Erlend Aasland}
+ Color support, tablature improvements, trivial \mark stuff,
+al-niente hairpins.
+
+@item @email{benkop@@freestart.hu,Pal Benko},
+ Ancient notation.
+@item @email{jch@@pps.jussieu.fr, Juliusz Chroboczek},
+ Type42 code.
+@item @email{david.feuer@@gmail.com, David Feuer},
+ PS output code refactoring.
+@item @email{bernard@@fong-hurley.org.uk, Bernard Hurley},
+ X11 color.
+@item @email{chris@@fluffhouse.org.uk, Chris Jackson},
+ Piano pedals, directed arpeggios.
+@item @email{heikki.junes@@hut.fi, Heikki Junes},
+ Fine tuning for quarter tones in midi output.
+@item @email{reinhold@@kainhofer.com, Reinhold Kainhofer},
+ @uref{http://reinhold.kainhofer.com},
+ Musicxml2ly development, various features and fixes.
+@item @email{m.krause@@tu-harburg.de, Michael Krause},
+ Breathing signs.
+@item @email{jiba@@tuxfamily.org, Jean-Baptiste Lamy},
+ Tablature support.
+@item @email{wl@@gnu.org, Werner Lemberg},
+ @TeX{} glue code.
+@item @email{joeneeman@@gmail.com, Joe Neeman},
+ Constrained line breaking.
+@item @email{hanwen@@xs4all.nl, Han-Wen Nienhuys},
+ @uref{http://www.xs4all.nl/~hanwen/},
+ Main author.
+
+@item @email{janneke@@gnu.org, Jan Nieuwenhuizen},
+ @uref{http://www.xs4all.nl/~jantien/},
+ Main author.
+@item @email{reuter_j@@web.de, Jürgen Reuter},
+ @uref{http://www.juergen-reuter.de},
+ Ancient notation support (mensural notation,
+ Gregorian chant notation), ambitus, clusters.
+@item @email{nicolas.sceaux@@free.fr, Nicolas Sceaux},
+ Scheme macros, \markup syntax.
+@item @email{c_sorensen@@byu.edu, Carl Sorensen},
+ Fret diagrams.
+@item @email{, Rune Zedeler},
+ Auto-accidental code, zigzag glissandi, rest bugfixes, minimum
+ fret, @code{subdivideBeams}.
+@end itemize
+
+Font
+
+@itemize @bullet
+
+@item @email{reuter_j@@web.de, Jürgen Reuter},
+ @uref{http://www.juergen-reuter.de},
+ Ancient notation font
+ Exact Type1 font outlines for feta, feta-alphabet.
+@item @email{chris@@fluffhouse.org.uk, Chris Jackson},
+ Arpeggio arrow
+@item @email{, Rune Zedeler},
+ 16th and shorter rests,
+@item @email{hanwen@@xs4all.nl, Han-Wen Nienhuys},
+ @uref{http://www.xs4all.nl/~hanwen/},
+ Main author.
+@item @email{janneke@@gnu.org, Jan Nieuwenhuizen},
+ @uref{http://www.xs4all.nl/~jantien/},
+ Main author.
+@item @email{tca@@gnu.org, Tom Cato Amundsen},
+ Accordion symbols.
+@item @email{arno@@arnowaschk.de, Arno Waschk},
+ "espressivo" mark.
+@end itemize
+
+
+Documentation and examples
+
+@itemize
+@item @email{mats.bengtsson@@s3.kth.se, Mats Bengtsson},
+ @uref{http://www.s3.kth.se/~mabe/},
+ Example files, documentation
+@item @email{heikki.junes@@hut.fi, Heikki Junes},
+ Cleanups in docs and example files.
+@item @email{john.mandereau@@free.fr, John Mandereau},
+ Internationalization.
+@item @email{scancm@@biobase.dk, Christian Mondrup},
+ Glossary.
+@item @email{hanwen@@xs4all.nl, Han-Wen Nienhuys},
+ @uref{http://www.xs4all.nl/~hanwen/},
+ Main author.
+@item @email{janneke@@gnu.org, Jan Nieuwenhuizen},
+ @uref{http://www.xs4all.nl/~jantien/},
+ Main author.
+@item @email{gpermus@@gmail.com, Graham Percival},
+ @uref{http://percival-music.ca},
+ Documentation Editor.
+@item @email{pinard@@iro.umontreal.ca, François Pinard},
+ @uref{http://www.iro.umontreal.ca/~pinard/},
+ Parts of Documentation/user/glossary*, started
+ internationalization stuff.
+@item @email{, Rune Zedeler},
+ Schumann example.
+@end itemize
+
+Support (distributions, editor support, lilypond-book)
+
+@itemize
+@item @email{foka@@debian.org, Anthony Fok},
+ Debian package: debian/*.
+@item @email{chris@@fluffhouse.org.uk, Chris Jackson},
+ Emacs mode indentation.
+@item @email{heikki.junes@@hut.fi, Heikki Junes},
+ Major Emacs- and Vim-mode updates.
+@item @email{svoboda@@cmu.edu, David Svoboda},
+ what-beat emacs module.
+@end itemize
+
+
+Translations
+
+@itemize
+@item @email{bjoern.jacke@@gmx.de, Bjoern Jacke},
+ German glossary translations.
+@item @email{nj104@@cus.cam.ac.uk, Neil Jerram},
+ Glossary translations.
+@item @email{heikki.junes@@hut.fi, Heikki Junes},
+ Finnish translations.
+@item @email{tdm@@dds.nl, Tineke de Munnik},
+ Dutch website translation.
+@item @email{august@@infran.ru, August S. Sigov},
+ Russian translation.
+@item @email{, David González},
+ Spanish glossary translations.
+@item @email{ngclaude@@123mail.org, Nicolas Grandclaude},
+ French documentation translation.
+@item @email{lolyfan@@wanadoo.fr, Jean-Charles Malahieude},
+ French translation of messages, website and documentation.
+@item @email{john.mandereau@@free.fr, John Mandereau},
+ French translation of messages, website and documentation
+@item @email{gauvainpocentek@@yahoo.fr, Gauvain Pocentek},
+ French website translation.
+@item @email{ludovicsardain@@gmail.com, Ludovic Sardain},
+ French documentation translation.
+@end itemize
+
+@end ignore
+
--- /dev/null
+@c -*- coding: utf-8; mode: texinfo; -*-
+@ignore
+ Translation of GIT committish: FILL-IN-HEAD-COMMITTISH
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+@include web/basic-authors.itexi
+
+@node community
+@unnumbered Community
+
+
+@divClass{column-center-top}
+@subheading Interacting with the community
+
+@itemize
+
+@item
+@ref{contact}: get help, discuss, and keep in touch!
+
+@item
+@ref{tiny examples}: these are @emph{highly} recommended when
+discussing LilyPond.
+
+@item
+@ref{bug reports}: something went wrong.
+
+@end itemize
+@divEnd
+
+@divClass{column-left-bottom}
+@subheading Making LilyPond better
+
+@itemize
+
+@item
+@ref{help us}: your assistance is requested.
+
+@item
+@ref{development}: for contributors and testers.
+
+@item
+@ref{authors}: the people who made LilyPond what it is today.
+
+@end itemize
+@divEnd
+
+@divClass{column-right-bottom}
+@subheading Miscellaneous
+
+@itemize
+
+@item
+@ref{publications}: what we wrote, and have had written about us.
+
+@item
+@ref{old news}: an archive.
+
+@end itemize
+@divEnd
+
+
+@divClass{hide}
+@menu
+* contact::
+* tiny examples::
+* bug reports::
+* help us::
+* development::
+* authors::
+* publications::
+* old news::
+@end menu
+@divEnd
+
+
+@node contact
+@unnumberedsec Contact
+
+
+@divClass{column-left-bottom}
+@subheading User Discussions and Help
+
+@subsubheading User mailing list: @code{lilypond-user@@gnu.org}
+
+This mailing list is the main place for users to discuss and help
+each other.
+
+@quotation
+@uref{http://mail.gnu.org/mailman/listinfo/lilypond-user,
+lilypond-user subscribe and info}
+
+@uref{http://mail.gnu.org/archive/html/lilypond-user/,
+user archive1}
+@uref{http://www.mail-archive.com/lilypond-user@@gnu.org/,
+archive2}
+@uref{http://dir.gmane.org/gmane.comp.gnu.lilypond.general,
+archive3}
+
+@uref{http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.general,
+send to lilypond-user with gmane}
+@end quotation
+
+@warning{When asking questions, please use @ref{tiny examples}!}
+
+
+@subsubheading IRC
+
+Some level of support is provided on our IRC channel,
+
+@example
+@uref{irc://irc.freenode.net/lilypond, #lilypond@@irc.freenode.net}
+@end example
+
+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.
+
+@html
+<form action="http://webchat.freenode.net"
+ method="get"
+ name="f_lily_irc"
+ <label>irc name:
+ <input name="nick" type="text" size="15" value="">
+ </label>
+ <input name="channels" type="hidden" value="lilypond">
+ <input type="submit" value="Join #lilypond IRC Chat">
+</form>
+
+<script language="JavaScript" type="text/javascript">
+ var username = "web";
+ var lang = window.navigator.userLanguage ? window.navigator.userLanguage
+ : window.navigator.language;
+ username += '-' + lang.substr(0, 2);
+ username += '-' + navigator.appName.substr(0, 2);
+ username += navigator.appCodeName.replace (" ", "").substr(0, 2);
+ username += navigator.platform.replace (" ", "").replace("nux", "").replace("n32", "");
+ document.forms["f_lily_irc"].nick.value = username;
+</script>
+@end html
+
+@subsubheading Other languages
+
+@quotation
+@uref{http://es.groups.yahoo.com/group/lilypond-es,
+Spanish yahoo group}
+
+@uref{http://www.lilypondforum.de/,
+German forum}
+
+@uref{http://groups.google.com/group/lilypond-brasil,
+Portugese group}
+
+@uref{http://lists.gnu.org/mailman/listinfo/lilypond-user-fr,
+French mailing list}
+
+@uref{http://www.lilypondforum.nl/,
+Dutch forum}
+@end quotation
+
+@divEnd
+
+
+@divClass{column-right-top}
+@subheading Stay Informed
+
+@subsubheading LilyPond Report
+
+The easiest way to keep touch is by reading our community
+newsletter, the @uref{http://news.lilynet.net/, LilyPond Report}.
+
+@subsubheading Releases mailing list: @code{info-lilypond@@gnu.org}
+
+This mailing list is a low-volume, read-only list which receives
+notifications of new releases.
+
+@quotation
+@uref{http://lists.gnu.org/mailman/listinfo/info-lilypond,
+info-lilypond subscribe and info}
+
+@uref{http://mail.gnu.org/archive/html/info-lilypond/,
+info archive1}
+@uref{http://www.mail-archive.com/info-lilypond@@gnu.org/,
+archive2}
+@uref{http://dir.gmane.org/gmane.comp.gnu.lilypond.announce,
+archive3}
+
+@c don't include gmane posting here. -gp
+@end quotation
+
+
+@divEnd
+
+
+@divClass{column-right-bottom}
+@subheading Developer Discussion
+
+@subsubheading Developer mailing list: @code{lilypond-devel@@gnu.org}
+
+Most developer discussion takes place on this list. Patches
+should be sent here.
+
+@quotation
+@uref{http://mail.gnu.org/mailman/listinfo/lilypond-devel,
+lilypond-devel subscribe and info}
+
+@uref{http://mail.gnu.org/archive/html/lilypond-devel/,
+devel archive1}
+@uref{http://www.mail-archive.com/lilypond-devel@@gnu.org/,
+archive2}
+@uref{http://dir.gmane.org/gmane.comp.gnu.lilypond.devel,
+archive3}
+
+@uref{http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.devel,
+send to lilypond-devel with gmane}
+@end quotation
+
+
+@subsubheading Bug mailing list: @code{bug-lilypond@@gnu.org}
+
+Bug-specific discussion takes place here.
+
+@quotation
+@uref{http://mail.gnu.org/mailman/listinfo/bug-lilypond,
+bug-lilypond subscribe and info}
+
+@uref{http://mail.gnu.org/archive/html/bug-lilypond/,
+bug archive1}
+@uref{http://www.mail-archive.com/bug-lilypond@@gnu.org/,
+archive2}
+@uref{http://dir.gmane.org/gmane.comp.gnu.lilypond.bugs,
+archive3}
+
+@c don't include gmane posting here. -gp
+@end quotation
+
+@warning{Before sending a message to the bug list, please read our
+guidelines for @ref{bug reports}.}
+
+@divEnd
+
+
+
+@node tiny examples
+@unnumberedsec Tiny examples
+
+@divClass{column-center-top}
+@subheading What are @qq{Tiny examples}?
+
+A tiny example is an example from which nothing can be removed.
+@divEnd
+
+@divClass{column-left-bottom}
+@subheading Why create them?
+
+@divClass{keep-bullets}
+@itemize
+
+@item
+The simpler the example is, the quicker potential helpers can
+understand it and help you.
+
+@item
+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.
+
+@item
+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
+@qq{bug} in a tiny example, then the problem was probably an
+insufficient understanding of LilyPond, not an actual bug!
+
+@end itemize
+@divEnd
+
+@divEnd
+
+
+@divClass{column-right-bottom}
+@subheading How do I create them?
+
+@divClass{keep-bullets}
+@itemize
+
+@item
+Include the \version number.
+
+@item
+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.
+
+@item
+When trying to create an example, try commenting out @w{(@code{%}
+or @code{%@{ @dots{} %@}})} sections of your file. If you can
+comment something while still demonstrating the main idea, then
+remove the commented-material!
+
+@item
+Avoid using complicated notes, keys, or time signatures, unless
+the bug is about the behavior of those items.
+
+@item
+Do not use @code{\override} or @code{\set} commands unless the bug
+is about those particular commands.
+
+@end itemize
+@divEnd
+
+@divEnd
+
+
+
+
+@node bug reports
+@unnumberedsec Bug reports
+
+@divClass{column-center-top}
+@subheading 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,
+
+@example
+@uref{http://code.google.com/p/lilypond/issues/list}
+@end example
+
+@warning{Please @strong{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.}
+
+@divEnd
+
+
+@divClass{column-left-bottom}
+@subheading Step 2: Creating a bug report
+
+If you have discovered a bug which is not listed, please help us
+by creating a bug report.
+
+@warning{We only accept bug reports in the form of
+@ref{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:
+
+@example
+%% 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
+@}
+@end example
+
+@divEnd
+
+@divClass{column-right-bottom}
+@subheading 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 @qq{no top-posting} check on the
+bug list, which is often incorrectly triggered by lilypond files.
+To avoid this, please add
+
+@example
+> I'm not top posting.
+@end example
+
+@noindent
+(you must include the @code{>} ) to the top of your bug report.
+
+@uref{http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.bugs,
+Post with the gmane lilypond.bugs interface}, or send an email to
+@uref{mailto:bug-lilypond@@gnu.prg, bug-lilypond@@gnu.org}.
+
+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.
+@divEnd
+
+
+@node help us
+@unnumberedsec Help us
+
+TODO: talk about the Frogs, document suggestions, encourage getting
+involved, etc. Maybe mention GLISS and GOP, if those are happening
+in the near future.
+
+frog mailist: @uref{http://frogs.lily.net}
+
+
+@node development
+@unnumberedsec Development
+
+
+@divClass{heading-center}
+@heading Development materials for LilyPond @versionDevel{}
+
+@warning{These are @emph{unstable development} versions. If you
+have the slightest doubt about how to use or install LilyPond, we
+urge you to use the stable @ref{download}, and read the stable
+@ref{manuals}.}
+
+@divEnd
+
+@divClass{column-center-top}
+@subheading Release numbers
+
+There are two sets of releases for LilyPond: stable releases, and
+unstable development releases. Stable versions have an
+even-numbered @q{minor} version number (e.g., 2.8, 2.10, 2.12).
+Development versions have an odd-numbered @q{minor} version number
+(e.g., 2.7, 2.9, 2.11).
+
+@divEnd
+
+
+@divClass{column-left-bottom}
+@subheading Download
+
+Instructions for git and compiling are in the Contributor's Guide.
+
+@quotation
+@uref{http://git.sv.gnu.org/gitweb/?p=lilypond.git, lilypond git repository}
+@end quotation
+
+Documentation writers and testers will generally want to download
+the latest binary:
+
+@quotation
+
+@downloadDevelLinuxNormal
+
+@downloadDevelLinuxBig
+
+@downloadDevelLinuxPPC
+
+@downloadDevelFreeBSDNormal
+
+@downloadDevelFreeBSDBig
+
+@downloadDevelDarwinNormal
+
+@downloadDevelDarwinPPC
+
+@downloadDevelWindows
+
+@downloadDevelSource
+
+@end quotation
+
+
+@subheading Manuals
+
+@help {these need the automatic symlinks or something. Maybe even
+a hard-coded url to lilypond.org/docs/2.13 or something??}
+
+Learning:
+@uref{lm-html, html}
+@uref{lm-big-html, big html}
+@uref{lm-pdf, pdf}
+
+Glossary:
+@uref{mg-html, html}
+@uref{mg-big-html, big html}
+@uref{mg-pdf, pdf}
+
+Essay:
+@uref{essay-html, html}
+@uref{essay-big-html, big html}
+@uref{essay-pdf, pdf}
+
+Notation:
+@uref{notation-html, html}
+@uref{notation-big-html, big html}
+@uref{notation-pdf, pdf}
+
+Usage:
+@uref{usage-html, html}
+@uref{usage-big-html, big html}
+@uref{usage-pdf, pdf}
+
+Snippets:
+@uref{snippets-html, html}
+@uref{snippets-big-html, big html}
+@uref{snippets-pdf, pdf}
+
+Changes:
+@uref{changes-html, html}
+@uref{changes-big-html, big html}
+@uref{changes-pdf, pdf}
+
+Internals:
+@uref{internals-html, html}
+@uref{internals-big-html, big html}
+@uref{internals-pdf, pdf}
+
+@divEnd
+
+
+@divClass{column-right-top}
+@subheading Contributors' Guide
+
+LilyPond development is a fairly complicated matter. LilyPond is
+a large, (mostly) stable project. At any point in time, we have
+between 5 and 25 active contributors. In order to help new
+contributors, and to keep the whole system (mostly) stable, we
+have written a manual for contributors.
+
+@divClass{keep-bullets}
+@itemize
+
+@item @uref{../contributor/index.html, Contributor's guide (split HTML)}:
+the manual is split between many HTML pages.
+@emph{(small download for each page)}
+
+@item @uref{../contributor-big-page.html, Contributor's guide (big HTML)}:
+read this manual as one huge HTML page.
+@emph{(large single download, around 10? Mb)}
+
+@item @uref{../contributor.pdf, contributor.pdf}:
+download as a PDF file.
+@emph{(large single download, 2.8 Mb)}
+
+@c @item @uref{TODO, contributor.info}:
+@c GNU info format for documentation. TODO, link broken.
+
+@end itemize
+@divEnd
+@divEnd
+
+@divClass{column-right-bottom}
+@subheading Regression tests
+
+@divClass{keep-bullets}
+@itemize
+
+@item @uref{../../input/regression/collated-files.html, Regression tests}:
+This releases' tests. (also in
+@uref{../input/regression/collated-files.pdf, pdf})
+
+@item @uref{../../input/regression/musicxml/collated-files.html,
+MusicXML Regression tests}:
+This releases' MusicXML tests. (also in
+@uref{../input/regression/musicxml/collated-files.pdf, pdf})
+
+@item @uref{http://lilypond.org/test, Archive of regression tests}:
+Comparisons beteween versions.
+
+@end itemize
+@divEnd
+@divEnd
+
+@node authors
+@unnumberedsec Authors
+
+@help{Under construction; this is not an accurate list!}
+
+combo of:
+
+http://lilypond.org/web/about/thanks
+
+Documentation/topdocs/AUTHORS.texi
+
+and maybe:
+http://lilypond.org/web/switch/
+
+
+@divClass{column-left-top}
+@subheading Current Development Team
+
+@divClass{keep-bullets}
+@developersCurrent
+@divEnd
+@divEnd
+
+@divClass{column-right-top}
+@subheading Previous Development Team Positions
+
+@divClass{keep-bullets}
+@developersPrevious
+@divEnd
+@divEnd
+
+
+@divClass{column-center-bottom}
+@subheading Programming contributors
+
+@divClass{keep-bullets}
+@contributorsCore
+
+@subheading Font contributors
+
+@contributorsFont
+
+@subheading Documentation contributors
+
+@contributorsDoc
+
+@subheading Support contributors
+
+@contributorsSupport
+
+@subheading Translation contributors
+
+@contributorsTranslations
+
+@divEnd
+@divEnd
+
+
+
+@node publications
+@unnumberedsec Publications
+
+@divClass{column-center-top}
+@subheading What we wrote
+
+@divClass{keep-bullets}
+@itemize
+
+@item
+Han-Wen Nienhuys, @emph{LilyPond, Automated music formatting and
+the Art of Shipping}. Forum Internacional Software Livre 2006
+(FISL7.0) (@uref{http://lilypond.org/web/images/FISL7-slides.pdf,
+PDF 1095k})
+
+@item
+Erik Sandberg, @emph{Separating input language and formatter in
+GNU Lilypond}. Master's Thesis, Uppsala University, Department of
+Information Technology March 2006.
+(@uref{http://lilypond.org/web/images/thesis-erik-sandberg.pdf,
+PDF 750k})
+
+@item
+Han-Wen Nienhuys and Jan Nieuwenhuizen, @emph{LilyPond, a system
+for automated music engraving}. Proceedings of the XIV Colloquium
+on Musical Informatics (XIV CIM 2003), Firenze, Italy, May 2003.
+(@uref{ http://lilypond.org/web/images/xivcim.pdf, PDF 95k})
+
+@end itemize
+
+@divEnd
+@divEnd
+
+
+@divClass{column-center-bottom}
+
+@subheading What others wrote
+
+@divClass{keep-bullets}
+@itemize
+
+@item
+September 2009
+
+The German LinuxUser magazine wrote an
+@uref{http://www.linux-community.de/Internal/Artikel/Print-Artikel/LinuxUser/2009/10/Digitaler-Notenschluessel,
+article about lilypond}.
+
+
+@item
+February 2008
+
+In @uref{http://www.musicbyandrew.ca/finale-lilypond-1.html,
+articles on his personal site}, 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.
+
+@item
+December 2005
+
+Linux journal cover Linux Journal publishes an article titled
+@uref{http://www.linuxjournal.com/article/8364, Make Stunning
+Schenker Graphs with GNU LilyPond}. 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.”
+
+@item
+August 20, 2005
+
+The Belgian newspaper De Standaard investigates what drives Free
+Software authors in an article titled
+@uref{http://www.standaard.be/Artikel/Detail.aspx?artikelId=G42H5GD6,
+Delen van KENNIS zonder WINSTBEJAG} (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.
+
+@item
+June 2005
+
+A French article on the LilyPond 2.6 release appeared on
+@uref{http://linuxfr.org/2005/06/27/19210.html, linuxfr.org}.
+
+@item
+October 2004
+
+The editors of Computer!Totaal, a Dutch computer magazine,
+@uref{http://lilypond.org/web/images/computer-totaal.jpeg,
+describe LilyPond} in the October 2004 issue as: @qq{Wonderful
+free (open source) software [..] The sheet music produced by
+LilyPond is exceptionally pretty [..] a very powerful system that
+can do almost anything.}
+
+@item
+July, August 2004
+
+Dave Phillips wrote an introductory article for Linux Journal At
+the sounding edge: LilyPond, parts
+@uref{http://www.linuxjournal.com/article/7657, one} and
+@uref{http://www.linuxjournal.com/article/7719, two}.
+
+@item
+March 2004
+
+Chris Cannam interviewed Han-Wen Nienhuys and Jan Nieuwenhuizen on
+linuxmusician.com (site now defunct). This interview was also
+reviewed in a
+@uref{http://slashdot.org/article.pl?sid=04/03/13/2054227&tid=,
+slashdot story}.
+
+@item
+February 2004
+
+Jazz singer Gail Selkirk writes about
+@uref{http://www.songbirdofswing.com/editorial_page/lilypond/,
+Diving into LilyPond}. @qq{... you can make lead sheets or full
+orchestral parts, and the results can be stunning.}
+@uref{http://www.computermusic.co.uk/, Computer Music Special},
+issue CMS06.
+
+@end itemize
+
+@divEnd
+@divEnd
+
+
+@node old news
+@unnumberedsec Old news
+
+@include web/news.itexi
--- /dev/null
+@c -*- coding: utf-8; mode: texinfo; -*-
+@ignore
+ Translation of GIT committish: FILL-IN-HEAD-COMMITTISH
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+@node download
+@unnumbered Download
+
+@divClass{heading-center}
+@heading Downloads for LilyPond @versionStable
+
+@divEnd
+
+@warning{LilyPond is a @strong{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 @ref{text input}.}
+
+@divClass{column-left-top}
+@subheading For users
+
+@itemize
+
+@item
+@c TODO: duplicate to avoid underlined refs in HTML? icky.
+@ref{UNIX, @sourceimage{logo-linux,,,}
+@sourceimage{logo-freebsd,,,}}
+@ref{UNIX, Unix (Linux and FreeBSD)}
+
+@item
+@ref{MacOS X, @sourceimage{logo-macosx,,,}}
+@ref{MacOS X, MacOS X}
+
+@item
+@ref{Windows, @sourceimage{logo-windows,,,}}
+@ref{Windows, Microsoft Windows}
+
+@end itemize
+
+@divEnd
+
+@divClass{column-right-top}
+@subheading For developers
+
+@itemize
+
+@item
+@ref{source}:
+for packagers
+
+@item
+@ref{old downloads}:
+old versions
+
+@item @ref{development}:
+latest unstable version
+
+@end itemize
+@divEnd
+
+
+@divClass{column-center-bottom}
+
+@subheading Software License
+
+LilyPond is published under the
+@ref{GPL, GNU General Public License}.
+@divEnd
+
+
+@divClass{color1}
+
+@subheading Sponsors
+
+Many thanks to @uref{http://www.vt.edu/, Virgina Tech} and
+@uref{http://www.linuxaudio.org/, linuxaudio.org} for sponsoring
+our bandwidth.
+
+@sourceimage{VTlogo_ITF,,,}
+@sourceimage{lao_banner_06_on_white_demo,,,}
+
+@subheading Legalese
+
+@divClass{legal}
+All logos and product images are copyright and trademark
+acknowledged.
+
+@logoLegalLinux
+
+@logoLegalFreeBSD
+
+@logoLegalMacOSX
+
+@logoLegalWindows
+
+@divEnd
+@divEnd
+
+
+@divClass{hide}
+@menu
+* UNIX::
+* MacOS X::
+* Windows::
+* source::
+* old downloads::
+* GPL::
+@end menu
+@divEnd
+
+
+@node UNIX
+@unnumberedsec UNIX
+
+@divClass{column-center-top}
+@subheading 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.
+
+@divEnd
+
+
+@divClass{column-left-top}
+@subheading Generic Packages
+
+@subsubheading Download
+
+@itemize
+
+@item
+@sourceimage{logo-linux,,,}
+@downloadStableLinuxNormal
+(if in doubt, use this)
+
+@item
+@sourceimage{logo-linux,,,}
+@downloadStableLinuxBig
+
+@item
+@sourceimage{logo-linux,,,}
+@downloadStableLinuxPPC
+
+@item
+@sourceimage{logo-freebsd,,,}
+@downloadStableFreeBSDNormal
+
+@item
+@sourceimage{logo-freebsd,,,}
+@downloadStableFreeBSDBig
+
+@end itemize
+
+
+@subsubheading Install
+
+In the shell, type:
+
+@example
+cd PATH-TO-DOWNLOAD-DIRECTORY
+sh lilypond-@versionStable{}-OS-TYPE.sh
+@end example
+
+@subsubheading Uninstall
+
+In the shell, type:
+
+@example
+uninstall-lilypond
+@end example
+
+@divEnd
+
+
+@divClass{column-right-top}
+@subheading Distribution-specific Packages
+
+Please use your distribution's package manager to install or
+upgrade to these versions.
+
+@itemize
+
+@item
+@sourceimage{logo-fedora,,,}
+@uref{https://admin.fedoraproject.org/pkgdb/packages/name/lilypond,
+Fedora: LilyPond 2.12.0}
+
+@item
+@sourceimage{logo-ubuntu,,,}
+@uref{https://launchpad.net/ubuntu/+source/lilypond,
+Ubuntu: LilyPond 2.12.1}
+
+@item
+@sourceimage{logo-slackware,,,}
+@uref{http://www.johannes-schoepfer.de/lilypond/,
+Slackware: LilyPond 2.12.1}
+
+@item
+@sourceimage{logo-debian,,,}
+@uref{http://packages.debian.org/search?keywords=lilypond,
+Debian: LilyPond 2.10.33}
+
+@item
+@sourceimage{logo-suse,,,}
+@uref{http://opensuse.org/?fixme=urg-no-lilypond-package-page,
+openSUSE: LilyPond 2.10.33}
+
+@end itemize
+
+@divEnd
+
+
+@divClass{column-center-bottom}
+@subheading Legalese
+
+@divClass{legal}
+All logos and product images are copyright and trademark
+acknowledged.
+
+@logoLegalLinux
+
+@logoLegalFreeBSD
+
+@divEnd
+@divEnd
+
+
+@node MacOS X
+@unnumberedsec MacOS X
+
+@divClass{column-left-top}
+@subheading Packages
+
+@subsubheading Download
+
+@itemize
+
+@item
+@sourceimage{logo-macosx,,,}
+@downloadStableDarwinNormal
+For Intel chips (if in doubt, use this).
+
+@item
+@sourceimage{logo-macosx,,,}
+@downloadStableDarwinPPC
+For G3 and G4 CPUs (old Apple computers).
+
+@end itemize
+
+@subsubheading Install
+
+Double-click the downloaded file, then drag it to wherever you
+want.
+
+@subsubheading Uninstall
+
+Delete the LilyPond.app folder.
+
+@divEnd
+
+
+@divClass{column-right-top}
+@subheading Running on the command-line
+
+@warning{If you are happy with the GUI, then please ignore these
+instructions.}
+
+@ignore
+FIXME: I had one report that we don't need this stuff; will delete
+after confirmation. -gp
+
+@subsubheading Using Python scripts on MacOS 10.3 or 10.4
+
+LilyPond binaries for MacOS X do not provide Python, but Python 2.4 or
+newer is required by @command{convert-ly}. Therefore, if you use MacOS
+10.3 or 10.4, you must install a newer Python version from
+@uref{http://python.org/download/}, then edit the first line of
+@command{convert-ly} and @command{lilypond-book} as follows: if the
+Python binary you just installed is in your @var{PATH}, the first line
+should be
+
+@example
+#!/usr/bin/env python
+@end example
+
+@noindent
+otherwise it should be
+
+@example
+#!@var{/path/to/newly_installed/python}
+@end example
+@end ignore
+
+@subsubheading MacOS X on the command line
+
+The most convenient way to run lilypond scripts is by setting up
+@qq{helper} scripts of your own.
+
+@enumerate
+
+@item
+Create a directory to store these scripts,
+
+@example
+mkdir -p ~/bin
+cd ~/bin
+@end example
+
+
+@item
+Create a file called @command{lilypond} which contains
+
+@help obvious css issue to be dealt with. :(
+@c we need a small font here to fit. -gp
+@smallexample
+exec @var{DIR}/LilyPond.app/Contents/Resources/bin/lilypond "$@@"
+@end smallexample
+
+@warning{@var{DIR} will generally be @code{/Applications/}}
+
+
+@item
+Create similar files @command{lilypond-book},
+@command{convert-ly}, and any other scripts you wish to use, by
+replacing the @command{bin/lilypond} with @command{bin/convert-ly}
+(or other program name).
+
+
+@item
+Make the file executable,
+
+@example
+chmod u+x lilypond
+@end example
+
+
+@item
+Now, add this directory to your path. Modify (or create) a file
+called @code{.profile} in your home directory such that it
+contains
+
+@example
+export PATH=$PATH:~/bin
+@end example
+
+This file should end with a blank line.
+
+@end enumerate
+
+
+@subsubheading Invoking individual scripts
+
+The scripts --- such as @command{lilypond-book}, @command{convert-ly},
+@command{abc2ly}, and even @command{lilypond} itself --- are included
+inside the @code{.app} file for MacOS@tie{}X.
+
+Scripts can also be run from the command line by invoking them
+directly:
+
+@example
+@var{path/to}/LilyPond.app/Contents/Resources/bin/lilypond
+@end example
+
+The same is true for all other scripts in that directory, such as
+@command{lilypond-book} and @command{convert-ly}.
+
+@divEnd
+
+
+@divClass{column-center-bottom}
+@subheading Legalese
+
+@divClass{legal}
+All logos and product images are copyright and trademark
+acknowledged.
+
+@logoLegalMacOSX
+
+@divEnd
+@divEnd
+
+
+
+@node Windows
+@unnumberedsec Windows
+
+@divClass{column-left-top}
+@subheading Packages
+
+@subsubheading Download
+
+@itemize
+
+@item
+@sourceimage{logo-windows,,,}
+@downloadStableWindows
+For Windows ME, NT, 2000, XP, and Vista.
+
+@end itemize
+
+@subsubheading Install
+
+@enumerate
+
+@item
+Locate the downloaded file and double-click on it to start the
+installer. You will be presented a window titled @qq{Open File -
+Security Warning}, click on Run to continue.
+
+@item
+You will be presented the License Agreement; read this carefully,
+and click on the Next button if you accept it.
+
+@item
+Preferably leave the destination folder to the default, else
+browse to choose a different location, and click on the Next
+button.
+
+@item
+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.
+
+@item
+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.
+
+@item
+Lilypond is now installed.
+
+@end enumerate
+
+@subsubheading Uninstall
+
+There are two uninstallation routes -
+
+@enumerate
+
+@item
+Choose Uninstall from the Lilypond menu from the start menu
+
+@item
+Open your Install/Uninstall Applications on the Control Panel,
+scroll down to Lilypond and click on the Uninstall buttom.
+
+@end enumerate
+
+@divEnd
+
+
+@divClass{column-right-top}
+@subheading Running on the command-line
+
+@warning{If you are happy with the GUI, then please ignore these
+instructions.}
+
+@help{don't know}
+
+@divEnd
+
+
+@divClass{column-center-bottom}
+@subheading Legalese
+
+@divClass{legal}
+All logos and product images are copyright and trademark
+acknowledged.
+
+@logoLegalWindows
+
+@divEnd
+@divEnd
+
+
+
+@node source
+@unnumberedsec Source
+
+@warning{We @strong{do not} recommend that you attempt to build
+LilyPond yourself; almost all user needs are better met with the
+pre-built version.}
+
+@divClass{column-left-bottom}
+@subheading Source tarball
+
+@downloadStableSource{}
+
+For an extensive listing of all versions (old and new), see our
+@uref{http://download.linuxaudio.org/lilypond/binaries/, download
+site}.
+
+@divEnd
+
+@divClass{column-right-bottom}
+@subheading Compiling instructions
+
+Instructions are listed in @rcontrib{Compiling LilyPond}.
+
+@divEnd
+
+
+@node old downloads
+@unnumberedsec Old downloads
+
+@divClass{column-center-top}
+@subheading All versions
+
+For an extensive listing of all versions (old and new), see our
+@uref{http://download.linuxaudio.org/lilypond/binaries/, download
+site}.
+
+@divEnd
+
+
+@node GPL
+@unnumberedsec GPL
+
+@divClass{column-center-top}
+@subheading 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 @ref{freedom}.
+
+@divEnd
+
+@divClass{column-center-bottom}
+@subheading GNU General Public License version 2
+
+@include gpl-2.0.itexi
+
+@divEnd
+
+
+
--- /dev/null
+depth=../../..
+LOCALSTEPMAKE_TEMPLATES=lilypond ly
+include $(depth)/make/stepmake.make
+
+LILYPOND_PREVIEW = $(LILYPOND_BINARY) -dpreview -dresolution=150
+
+OUT_PNG_FILES = $(LY_FILES:%.ly=$(outdir)/%.png)
+OUT_PNG_PAGES = $(PNG_PAGES:%=$(outdir)/%.png)
+
+OUT_SMALL_PNG_FILES = $(OUT_PNG_FILES:%.png=%-small.png)
+
+ifeq ($(out),www)
+all: $(OUT_PNG_FILES) $(OUT_SMALL_PNG_FILES)
+endif
+
+$(outdir)/%.png: %.ly
+ $(LILYPOND_PREVIEW) -o $(outdir) $<
+ mv $(outdir)/$*.preview.png $@
+
+$(outdir)/%-small.png: $(outdir)/%.png
+ pngtopnm $< | pnmscale -w=600 | pnmtopng > $@
+
--- /dev/null
+\version "2.12.0"
+\include "example-header.ily"
+
+#(set-global-staff-size 15)
+
+\include "gregorian.ly"
+
+\score {
+ <<
+ \new VaticanaVoice = "cantus" {
+ \clef "vaticana-do3"
+ % Verse 1 — Salve, Regína
+ a\melisma \[ a \flexa g \pes a\melismaEnd \] d
+ \divisioMinima
+ \[ a\melisma \flexa g\melismaEnd \]
+ \[ f\melisma \flexa e f \pes g \flexa f\melismaEnd \]
+ \[ e\melisma \flexa d\melismaEnd \]
+ \divisioMaior
+ c d \[d\melisma \flexa c\melismaEnd \] d
+ \[ e\melisma \pes f\melismaEnd\] g
+ \[d\melisma \pes e \flexa c\melismaEnd \] d
+ \finalis
+ % Verse 2 — Vita, dulcédo
+ % a\melisma \[ a \flexa g \pes a\melismaEnd \] d
+ % \divisioMinima
+ % \[ a\melisma \flexa g\melismaEnd \]
+ % \[ f\melisma \flexa e f \pes g \flexa f\melismaEnd \]
+ % \[ e\melisma \flexa d\melismaEnd \]
+ % \divisioMaior
+ % c d \[e\melisma \pes f\melismaEnd \] g
+ % \[d\melisma \pes e \flexa c\melismaEnd \] d
+ % \finalis
+ % Verse 3 — Ad te clamámus
+ \[ d\melisma \pes f\melismaEnd\] a g
+ \[ g\melisma \flexa f \pes a\melismaEnd\] e
+ \divisioMaior
+ g f \[ e\melisma \flexa d \pes g\melismaEnd \]
+ \divisioMinima
+ c d \[ e\melisma \flexa d \pes g\melismaEnd \]
+ \[ f\melisma \flexa e\melismaEnd \] d
+ \finalis
+ % Verse 4 — Ad te suspirámus
+ \[ d\melisma \pes f\melismaEnd \] a c' g
+ \[ g\melisma \flexa f \pes g\melismaEnd \] a
+ \divisioMaior
+ d \[ f\melisma \pes \deminutum g\melismaEnd \] g d
+ \[ \virga f\melisma \inclinatum e \inclinatum d\melismaEnd \]
+ c \divisioMaior
+ d \[ d\melisma \flexa c \pes f\melismaEnd \]
+ \[ g\melisma \pes a\melismaEnd \]
+ g \[ f\melisma \flexa e\melismaEnd \] g
+ \[ f\melisma \flexa \deminutum e\melismaEnd \]
+ \[ d\melisma \flexa c \pes d\melismaEnd \]
+ \finalis
+ % Verse 5 — Eia ergo, Advocáta nostra
+ f\melisma \[ f \pes g\melismaEnd \] f
+ \[ g\melisma \pes \deminutum a\melismaEnd \] a
+ \divisioMinima
+ c' g \[ \virga a\melisma \inclinatum g \inclinatum f\melismaEnd \] d g a
+ \divisioMaior
+ d' d' \[ c'\melisma \flexa b c' \pes d'\melismaEnd \] a
+ \divisioMinima
+ d' c' a \[ g\melisma \flexa f \pes a\melismaEnd \] g
+ \[ d\melisma \pes e\melismaEnd \] f
+ \[ \virga e\melisma \inclinatum d \inclinatum c\melismaEnd \]
+ \divisioMaior
+ \[ c\melisma \pes d\melismaEnd \]
+ f \[ g\melisma \flexa \deminutum f\melismaEnd \]
+ \[ d\melisma \flexa c \pes d\melismaEnd \] d
+ \finalis
+ % Verse 6 — Et Jesum
+ d a, \[ c\melisma \pes d\melismaEnd \]
+ \divisioMinima
+ d \[ d\melisma \pes e\melismaEnd \] \[ e\melisma \flexa d d\melismaEnd \]
+ c g f \[ e\melisma \flexa \deminutum d\melismaEnd \] g
+ \[ f\melisma \flexa e\melismaEnd \]
+ \[ d\melisma \flexa c \pes d\melismaEnd \]
+ \[ d\melisma \pes a \] \virga bes\melismaEnd a
+ \divisioMinima
+ \[ \virga a\melisma \inclinatum g \inclinatum f\melismaEnd \] g d f
+ \[ f\melisma \flexa e\melismaEnd \] \[ d\melisma \flexa c\melismaEnd \]
+ \divisioMinima
+ \[ e\melisma \pes f \flexa e\melismaEnd \] d d
+ \finalis
+ % Verse 7 ad finem — O clemens: O pia: O dulcis Virgo María
+ a\melisma \[a \flexa g a \quilisma b \pes c'\melismaEnd \]
+ \[ \virga b\melisma \inclinatum a \inclinatum g\melismaEnd \] a
+ \finalis
+ \[ g\melisma \pes a \quilisma b \pes c' \] \[ c' \flexa b\melismaEnd \]
+ \[ a\melisma \flexa g\melismaEnd \] \[ g\melisma \pes a\melismaEnd \]
+ \finalis
+ \[ a\melisma \flexa d \virga f \inclinatum e \inclinatum d \inclinatum c d \]
+ \divisioMinima
+ \[ d \pes e f \pes g\melismaEnd \]
+ \[ g\melisma \flexa \deminutum f\melismaEnd \]
+ \[ g\melisma \pes a\melismaEnd \]
+ d c d \[ d\melisma \pes g \flexa f f\melismaEnd \]
+ \[ e\melisma \flexa d\melismaEnd \]
+ \finalis
+ }
+ \new Lyrics \lyricsto "cantus" {
+ Sal- ve, Re- gí- na, ma- ter mi- se- ri- cór- di- ae:
+ % Vi- ta, dul- cé- do, et spes no- stra, sal- ve.
+ Ad te cla- má- mus, éx- su- les, fi- li- i He- vae.
+ Ad te su- spi- rá- mus, ge- mén- tes et flen- tes in hac la- cri- má- rum
+ val- le.
+ E- ia er- go, Ad- vo- cá- ta no- stra, il- los tu- os mi- se- ri- cór- des
+ ó- cu- los ad nos con- vér- te.
+ Et Je- sum, be- ne- díc- tum fruc- tum ven- tris tu- i, no- bis post hoc
+ ex- sí- li- um os- tén- de.
+ O cle- mens:
+ O pi- a:
+ O dul- cis Vir- go Ma- rí- a.
+ }
+ >>
+}
+
+\layout {
+ \context {
+ \Staff
+ \consists Custos_engraver
+ }
+}
+
--- /dev/null
+\version "2.12.0"
+\include "example-header.ily"
+
+\paper {
+% line-width=158\mm % produces 624 pixels
+ line-width = 143\mm % reserve 15mm for incipit
+}
+
+% Aucun ont trouvé, from Montpellier Codex
+%
+% Put brackets in where the original has ligatures, using
+% "Analysis Brackets," and adjust the "bracket-flare" property
+% to make the ends vertical instead of slanted.
+
+#(set-global-staff-size 15)
+
+%%%%%%%%%%% INCIPIT DEFS %%%%%%%%%%
+
+incipitGlobal = {
+ \override NoteHead #'style = #'mensural
+ \override Accidental #'style = #'mensural
+ \override KeySignature #'style = #'mensural
+ \override Rest #'style = #'mensural
+% \override Staff.TimeSignature #'style = #'mensural
+ \cadenzaOn
+ \override Score.Clef #'extra-offset = #'(-0.0 . 0.5)
+ \override Score.Clef #'font-size = #3
+ \clef "vaticana-do1"
+}
+
+incipitTriplum = \markup{
+ \score{
+ {
+ \set Staff.instrumentName="Triplum "
+ \incipitGlobal
+ s1.
+ }
+ \layout {
+ %indent = 1\cm
+ \context {\Voice
+ \remove Ligature_bracket_engraver
+ \consists Mensural_ligature_engraver
+ }
+ \context {\Staff
+ \remove "Time_signature_engraver"
+ }
+ line-width=5\mm
+ }
+ }
+}
+
+incipitMotetus = \markup{
+ \score{
+ {
+ \set Staff.instrumentName="Motetus"
+ \incipitGlobal
+ s1.
+ }
+ \layout {
+ % indent = 1\cm
+ \context {\Voice
+ \remove Ligature_bracket_engraver
+ \consists Mensural_ligature_engraver
+ }
+ \context {\Staff
+ \remove "Time_signature_engraver"
+ }
+ line-width=5\mm
+ }
+ }
+}
+
+incipitTenor = \markup{
+ \score{
+ {
+ \set Staff.instrumentName = "Tenor "
+ \incipitGlobal
+ s1.*2
+ }
+ \layout {
+ %indent = 1\cm
+ \context {\Voice
+ \remove Ligature_bracket_engraver
+ \consists Mensural_ligature_engraver
+ }
+ \context {\Staff
+ \remove "Time_signature_engraver"
+ }
+ line-width=5\mm
+}
+}
+}
+
+incipitBassus = \markup{
+ \score{ {
+ \set Staff.instrumentName = "Bassus "
+ \override NoteHead #'style = #'neomensural
+ \override Accidental #'style = #'neomensural
+ \override Rest #'style = #'neomensural
+ \override Staff.TimeSignature #'style = #'neomensural
+ \cadenzaOn
+ \clef "petrucci-f3"
+ \key f \major
+ \time 3/2
+ \relative c' {
+ s1. % R1.*2
+ }
+ }
+ \layout {
+ \context { \Voice
+ \remove Ligature_bracket_engraver
+ \consists Mensural_ligature_engraver
+ }
+ line-width=5\mm
+ }
+ }
+}
+
+%%%%%%%%%%% END INCIPIT DEFS %%%%%%%%%%%
+
+#(ly:set-option 'point-and-click #f)
+
+global = {
+ \override Staff.TimeSignature #'stencil = #(lambda (grob)
+ (bracketify-stencil (ly:time-signature::print grob) Y 0.1 0.2 0.1))
+ \time 3/4
+ \override Staff.BarLine #'transparent = ##t
+ \override HorizontalBracket #'direction = #UP
+ \override HorizontalBracket #'bracket-flare = #'(0 . 0)
+}
+
+%%%%%%%%% MACRO FOR MAKING SLASHES THROUGH STEMS %%%%%%%%%%
+MakeSlash = #(define-music-function (parser location angle len-left len-right
+thick y-factor offset)
+ (number? number? number? number? number?
+pair?)
+#{
+\once \override Voice.Stem #'text = \markup {
+ \postscript #(let ((x-off (car $offset))
+ (y-off (cdr $offset)))
+ (string-append
+ (ly:number->string (car $offset)) " " (ly:number->string (cdr $offset)) "
+translate "
+ (ly:number->string $angle) " rotate "
+ (ly:number->string (- x-off)) " "
+ (ly:number->string (- y-off)) " translate 0 setlinewidth "
+ (ly:number->string (- x-off $len-left)) " " (ly:number->string (+ y-off
+$thick)) " moveto "
+ (ly:number->string (- x-off $len-left)) " " (ly:number->string y-off)
+ " " (ly:number->string $thick) "
+90 270 arc "
+ (ly:number->string (+ x-off $len-right)) " " (ly:number->string y-off)
+ " " (ly:number->string $thick) "
+270 90 arc "
+ " gsave fill grestore stroke")) }
+
+\once \override Voice.Stem #'stencil = #(lambda (grob)
+ (let* ((sten1 (ly:stem::print grob))
+ (sten2 (ly:text-interface::print grob))
+ (extent1 (ly:stencil-extent sten1 Y))
+ (extent2 (ly:stencil-extent sten2 Y)))
+ (ly:stencil-add
+ sten1
+ (ly:stencil-translate sten2
+ (cons 0 (+ (* $y-factor (cdr extent1))
+ (* (- 1 $y-factor) (car extent1))))))))
+#})
+
+
+slash = { \MakeSlash #20 #1.0 #1.1 #0.05 #0.75 #'(0 . -.5) }
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+triplumWords = \lyricmode {
+ Au -- cun ont trou -- ve chant par u -- sa -- ge,
+ mes a moi en doune o -- choi -- son __
+ a -- mours, qui res -- bou -- dist mon cou -- ra -- ge
+ si que m'ès -- tuet fai -- re _ chan -- _ _ çon
+}
+
+triplumNotes = \relative c' {
+ \clef "treble_8"
+ %\set Staff.midiInstrument = "flute"
+% \global
+ \override StemTremolo #'beam-thickness = #.125
+ \override StemTremolo #'slope = #1.0
+ f8 f4 e8 d c f f f | % 1
+ % the \scaleDurations command below makes 5 notes last the
+ % duration of a dotted quarter
+ e8 c4 \scaleDurations #'(3 . 2) { \times 4/5{e16[ d e d e]} } e8 f4 | % 2
+ g2. ~ g4. | % 3
+ f8 d4 f4. \scaleDurations #'(3 . 2) { \times 4/6{ g16[ f e f e f]}} % 4
+ g8 g4 g4. e4. | % 5
+ fis8 d4 e8\startGroup g4\stopGroup f8[ e d] | % 6
+ c2. r4. | % 7
+}
+
+motetusWords = \lyricmode {
+ lonc tans _ _ me fiu -- te -- nu de chan -- _ _ ter __
+ mes or ai _ _
+}
+
+motetusNotes = \relative c' {
+ \clef "treble_8"
+ c2. c8\startGroup b8 \slash c\stopGroup | % 1
+ a2. c4. | d2. e4. | % 2-3
+ f2. f8 e d | % 4
+ c2. ~ c4. | r2. r4. | % 5-6
+ g'4. g g8 f e | % 7
+}
+
+
+tenorNotes = \relative c {
+ \clef "treble_8"
+ f2. | a2. | g2. | r2. | % 1-4
+ c2. | b2. | c2. | % 5-7
+}
+
+\score {
+ \new StaffGroup <<
+ \new Staff = "triplum" <<
+ %\set Staff.instrumentName = "Triplum"
+ \set Staff.instrumentName = \incipitTriplum
+ \set Staff.shortInstrumentName = "Tr."
+ \set Staff.timeSignatureFraction = #'(9 . 8)
+ \scaleDurations #'(2 . 3)
+ \context Voice = "triplum" { \global \triplumNotes }
+% \scaleDurations #'(2 . 3)
+% \context Voice = "slashes" { \triplumSkips }
+ \new Lyrics { \lyricsto "triplum" { \triplumWords }}
+ >>
+ \new Staff = "motetus" <<
+ %\set Staff.instrumentName = "Motetus"
+ \set Staff.instrumentName = \incipitMotetus
+ \set Staff.shortInstrumentName = "M."
+ \set Staff.timeSignatureFraction = #'(9 . 8)
+ \scaleDurations #'(2 . 3)
+ \context Voice = "motetus" { \global \motetusNotes }
+ \new Lyrics { \lyricsto "motetus" { \motetusWords }}
+ >>
+ \new Staff = "tenor" {
+ %\set Staff.instrumentName = "Tenor"
+ \set Staff.instrumentName = \incipitTenor
+ \set Staff.shortInstrumentName = "T."
+ \global \tenorNotes
+ }
+ >>
+ %\midi {}
+ \layout {
+ %\context {
+ % \Staff \consists "Horizontal_bracket_engraver"
+ %}
+ \context {
+ \Voice \consists "Horizontal_bracket_engraver"
+ }
+ }
+}
--- /dev/null
+\version "2.12.0"
+%\include "example-header.ily"
+
+
+\header {
+ mutopiatitle = "Jesu, meine Freude"
+ mutopiacomposer = "BachJS"
+ poet = "BWV 610"
+ %mutopiaopus = "BWV 610"
+ mutopiainstrument = "Organ"
+ date = ""
+ source = "Bach-Album, Ernst H. Wolfram (editor), 6787, C. F. Peters, Leipzig"
+ style = "Baroque"
+ copyright = "Public Domain"
+ maintainer = "Urs Metzger"
+ maintainerEmail = "urs@ursmetzger.de"
+ lastupdated = "2006/Mar/15"
+
+ title = "Jesu, meine Freude"
+ composer = "Johann Sebastian Bach"
+ %opus="BWV 610"
+
+ footer = "Mutopia-2006/03/27-706"
+ tagline = \markup { \override #'(box-padding . 1.0) \override #'(baseline-skip . 2.7) \box \center-column { \small \line { Sheet music from \with-url #"http://www.MutopiaProject.org" \line { \teeny www. \hspace #-1.0 MutopiaProject \hspace #-1.0 \teeny .org \hspace #0.5 } • \hspace #0.5 \italic Free to download, with the \italic freedom to distribute, modify and perform. } \line { \small \line { Typeset using \with-url #"http://www.LilyPond.org" \line { \teeny www. \hspace #-1.0 LilyPond \hspace #-1.0 \teeny .org } by \maintainer \hspace #-1.0 . \hspace #0.5 Reference: \footer } } \line { \teeny \line { This sheet music has been placed in the public domain by the typesetter, for details see: \hspace #-0.5 \with-url #"http://creativecommons.org/licenses/publicdomain" http://creativecommons.org/licenses/publicdomain } } } }
+
+}
+
+\include "deutsch.ly"
+
+global = {
+ \key c \minor
+ \time 4/4
+ #(set-accidental-style 'default)
+}
+
+halsup = {
+ \stemUp
+ \tieUp
+}
+
+halsdown = {
+ \stemDown
+ \tieDown
+}
+
+staffup = {
+ \change Staff = "right" \halsdown
+}
+
+staffdown = {
+ \change Staff = "left" \halsup
+}
+
+sopran = {
+ \new Voice \relative g' {
+ \global
+ \halsup
+ \repeat volta 2 {
+ g4^\markup { \hspace #-4 \large "Largo" } g f es
+ d2 c\fermata
+ g'4 g a h
+ c2 h\fermata
+ %% Takt 5 ==============================================
+ c8. d16 es4 d4. d8
+ c1\fermata
+ }
+ g4 g as g
+ f4. f8 es2\fermata
+ g4 g a h
+ %% Takt 10 =============================================
+ c4 b! a2
+ g1\fermata
+ g4 g f es
+ d2 c2\fermata \bar "|."
+ }
+}
+
+alt = {
+ \new Voice \relative es' {
+ \global
+ \halsdown
+ \repeat volta 2 {
+ es16 d es8~ es16 f es d c8 d~ d c
+ c8 c4 h8 c8. \staffdown g16 \staffup c h c d
+ es16 d es8~ es16 f es d c8 d16 es f as g f~
+ f16 e f8~ f16 g f es d es d8~ d16 es f d
+ %% Takt 5 ==============================================
+ g8 f es16 g as es f es f d g as g f
+ e8 f16 g as g as e f g f8~ f16 f es d
+ }
+ es16 d es8~ es16 f es des c8 \staffdown b~ b16 b c g
+ as16 g as f b c b as g f g8~ g16 b \staffup c d
+ es16 d es8~ es16 f es d c8 d16 es f as g f
+ %% Takt 10 =============================================
+ es16 d es8 d g~g g4 fis8
+ g16 d es c \staffdown d h c a h a h c d h g h
+ c16 h c \staffup d es d es8~ es d4 c8~
+ c16 h c8~ c h c16 \staffdown g as8 g4\fermata
+ }
+}
+
+tenor = {
+ \new Voice \relative c' {
+ \global
+ \repeat volta 2 {
+ c16 h c8~ c16 h c g a8 g~ g16 g as es
+ f16 es f d g as g f es d \tieDown es8~ es16 \tieNeutral f es d
+ c16 h c g' c h c c, f8. g16 as!4~
+ as16 g as b c h c8 d8. c16 h c d h
+ %% Takt 5 ==============================================
+ es16 d es d~ d8 c~c c4 h8
+ c4~ c8. b16 as b as8 g16 as g f
+ }
+ \halsdown es16 f g as b des c b as g f8~ f es
+ es8 es4 d8 es8. b16 es d es f
+ es16 f g8 c16 d c b a g f8~ f4
+ %% Takt 10 =============================================
+ g16 fis g a b a b g c b c a d es d c
+ h8 c16 a h g a fis g8 d16 es f es f8~
+ f16 d es h c h c8 r16 f g d es g as fis
+ g16 d f! es f as g f e8. f16~ f d e8\fermata
+ }
+}
+
+right = {
+ \clef treble
+ <<
+ \alt
+ \sopran
+ >>
+}
+
+left = {
+ \clef bass
+ <<
+ \tenor
+ >>
+}
+
+pedal = {
+ \global
+ \clef "bass"
+ \relative c {
+ \repeat volta 2 {
+ r8 c16 d es d es8~ es16 a, h g c h c8
+ r16 g as f g f g8 c,2
+ r8 c'16 d es d es8~ es16 c f es d c d8
+ c8 f16 g as g as8~ as16 d, fis d g fis g8
+ %% Takt 5 ==============================================
+ r8 a16 h c h c8
+ r16 g as f g f g8
+ r16 g as e f e f8 r16 e f h, c h c8
+ }
+ r8 es16 f g f g8~ g16 c, d! b es d es8
+ r16 b c as b as b8 es,2
+ r8 c'16 d es d es8~ es16 c f es d c d8
+ %% Takt 10 =============================================
+ c8 es16 f! g fis g8 r16 d es c d c d8
+ g,1
+ c4 c,8 c'16 b! a8 h c16 h c8
+ r16 g as fis g fis g8 c,2_\fermata
+ }
+}
+
+\score {
+ \new PianoStaff
+ { \set PianoStaff.instrumentName = \markup { \large \center-column {
+ "a" "" "2 Clav." "" "e" "" "Pedale." } \hspace #0.5 }
+ <<
+ \context Staff = right
+ {
+ \context Voice = right \right
+ }
+ \context Staff = left {
+ \context Voice = left \left
+ }
+ \context Staff = pedal {
+ \context Voice = pedal \pedal
+ }
+ >>
+ }
+ \layout{}
+}
--- /dev/null
+% -*-coding: utf-8 -*-
+
+\header{
+ composer = "J.S. Bach"
+ title = "Wenn wir in höchsten Nöten sein"
+ subtitle = "Analysis from Gene Biringer's Schenker Text, Ex. 5-27"
+% "BWV641"
+ enteredby = "Kris Shaffer"
+}
+
+%%
+%% See http://www.shaffermusic.com/doc/schenker/index.html for more information
+%%
+
+I = \once \override NoteColumn #'ignore-collision = ##t
+
+\version "2.12.0"
+
+staffPiano = \new PianoStaff {
+ \set Score.timing = ##f
+ \set PianoStaff.followVoice = ##t
+
+ <<
+ \new Staff = "RH" { % Right hand
+ \clef treble
+ \key g \major
+ \relative c'' {
+ \override Staff.NoteCollision
+ #'merge-differently-headed = ##t
+ <<
+ {
+ \override Beam #'positions = #'(8 . 8)
+ \override NoteHead #'transparent = ##t
+ \override NoteHead #'duration-log = #1
+ s1 b8[^\markup {
+ \override #'(baseline-skip . 0.5)
+ \column { \small {^ 3} }
+ }
+ s4. s1 a8^\markup {
+ \override #'(baseline-skip . 0.5)
+ \column { \small {^ 2} }
+ }
+ s4. s2 g8]^\markup {
+ \override #'(baseline-skip . 0.5)
+ \column { \small {^ 1} }
+ }
+ s4.
+ \revert Beam #'positions
+ \revert NoteHead #'transparent
+ \revert NoteHead #'duration-log
+ }
+ \\
+ {
+ \override Stem #'transparent = ##t
+ s1
+ \once \override Slur #'height-limit = #6
+ \once \override Slur #'extra-offset = #'(1.25 . 0)
+ \slurDashed
+ \I b2_( s2
+ \once \override NoteHead #'transparent = ##t
+ b4) s
+ \once \override Slur #'height-limit = #3.25
+ \once \override Slur #'extra-offset = #'(.75 . 0)
+ a2_( s4
+ \once \override NoteHead #'transparent = ##t
+ a)
+ g2
+ \revert Stem #'transparent
+ }
+ \\
+ \override Staff.NoteCollision
+ #'merge-differently-headed = ##t
+ {
+ \override Beam #'positions = #'(4 . -3.25)
+ \stemUp
+ g8[ s s4 s2
+ \stemDown
+ \once \override NoteHead #'transparent = ##t
+ \I b8] s8
+ \override Beam #'positions = #'(3 . -2.25)
+ \stemUp
+ a8[ s s4
+ \stemDown
+ c8] s s2 s s
+ }
+ \\
+ {
+ \override Stem #'transparent = ##t
+ \override Stem #'length = #0
+ g4_\( fis^(_\markup { \tiny N } g)\)
+ a^(^\markup { \tiny P } b2)
+ b4^(^\markup { \tiny P }
+ \stemUp
+ \revert Stem #'transparent
+ \override Stem #'length = #10
+ c8)^( s
+ \override Stem #'length = #14
+ b4) s s
+ \override Stem #'length = #0
+ \override Stem #'transparent = ##t
+ \once \override Slur #'extra-offset = #'(0 . 0.35)
+ c4^\( b_(_\markup { \tiny P } a)\) s2
+ \revert Stem #'length
+ }
+ \\
+ {
+ \override Stem #'transparent = ##t
+ \override NoteHead #'transparent = ##t
+ \override Stem #'length = #0
+ s1 s4 e4 s
+ \change Staff = "LH"
+ fis,4 s2
+ \revert Stem #'transparent
+ \revert NoteHead #'transparent
+ \revert Stem #'length
+ }
+ \\
+ {
+ \override Stem #'transparent = ##t
+ \override NoteHead #'transparent = ##t
+ \override Stem #'length = #0
+ s1 s s2
+ fis'4 s
+ \change Staff = "LH"
+ g,4 s s2
+ \revert Stem #'transparent
+ \revert NoteHead #'transparent
+ \revert Stem #'length
+ }
+ >>
+ \bar "|."
+ }
+ }
+
+ \new Staff = "LH" { % Left hand
+ \clef bass
+ \key g \major
+ \relative c' {
+ \override Staff.NoteCollision
+ #'merge-differently-headed = ##t
+ <<
+ {
+ \override Beam #'positions = #'(-8 . -8)
+ \override NoteHead #'transparent = ##t
+ \stemDown
+ \I g8[_\markup { \bold I } s4. s1 s s2
+ \I d8_\markup { \bold V } s4.
+ \I g,8]_\markup { \bold I } s4.
+ \revert Beam #'positions
+ \revert NoteHead #'transparent
+ }
+ \\
+ {
+ \override Stem #'transparent = ##t
+ \stemDown
+ \override TextScript #'extra-offset = #'(-11.75 . -12.25)
+ \I g'2 s1 s s2 \I d2 g,2
+ \revert Stem #'transparent
+ }
+ \\
+ {
+ \override Stem #'transparent = ##t
+ \once \override NoteHead #'transparent = ##t
+ \override Stem #'length = #0
+ g'4
+ \once \override TextScript #'padding = #0.25
+ a4_(^\markup { \tiny P } b)
+ fis4^(^\markup { \tiny P } e)
+ \once \override NoteHead #'transparent = ##t
+ \once \override Slur #'height-limit = #1.5
+ c4^(
+ d)^\markup { \tiny N }
+ \once \override NoteHead #'transparent = ##t
+ \once \override Slur #'extra-offset = #'(0 . 0.5)
+ \I fis,4_(
+ \revert Stem #'transparent
+ \override Stem #'length = #10
+ \stemDown
+ g4) s
+ \once \override Slur #'extra-offset = #'(0 . 0.25)
+ \I c8_( s
+ \override Stem #'transparent = ##t
+ \revert Stem #'length
+ a4)
+ \once \override NoteHead #'transparent = ##t
+ \I d4^( d,4) s2
+ }
+ \\
+ {
+ \override Stem #'transparent = ##t
+ \override NoteHead #'transparent = ##t
+ \I g'4^( s b) s2
+ \revert Stem #'transparent
+ \revert NoteHead #'transparent
+ \override Beam #'positions = #'(-4 . 1)
+ \stemDown
+ c,8[ s s4
+ \stemUp
+ fis,8] s
+ \override Beam #'positions = #'(1 . -4)
+ g8[ s
+ \stemDown
+ b8] s
+ \revert Beam #'positions
+ \override Stem #'transparent = ##t
+ \override NoteHead #'transparent = ##t
+ c4^( s d4) s s2
+ }
+ \\
+ {
+ \override Stem #'transparent = ##t
+ \override NoteHead #'transparent = ##t
+ \override Stem #'length = #0
+ \stemDown
+ \once \override Slur #'height-limit = #3
+ \once \override Slur #'extra-offset = #'(0 . 0.25)
+ \I g4_( s2. e4) s2. s2 s1 s2
+ \revert Stem #'transparent
+ \revert NoteHead #'transparent
+ }
+ \\
+ {
+ \override Stem #'transparent = ##t
+ \override NoteHead #'transparent = ##t
+ \slurDashed
+ \once \override Slur #'height-limit = #6.0
+ \once \override Slur #'extra-offset = #'(0.5 . -0.25)
+ \override Stem #'length = #0
+ g4_( s2. s1 g,4) s s1 s2
+ \revert Stem #'transparent
+ \revert NoteHead #'transparent
+ }
+ >>
+ \bar "|."
+ }
+ }
+ >>
+}
+
+
+\score {
+ <<
+ \staffPiano
+ >>
+
+% \midi {
+% }
+
+ \layout {
+ indent = 0.0
+ ragged-right = ##f
+ \context { \Staff \remove "Time_signature_engraver" }
+ }
+}
+
+
+\paper {
+}
--- /dev/null
+
+\version "2.12.0"
+
+\layout {
+ indent = #0
+ ragged-right = ##t
+ \context {
+ \Score
+
+ proportionalNotationDuration = #(ly:make-moment 1 64)
+ \override Beam #'breakable = ##t
+ autoBeaming = ##f
+ tupletFullLength = ##t
+ \override BarNumber #'transparent = ##t
+ \override BarLine #'transparent = ##t
+ \override SpanBar #'transparent = ##t
+ \override Beam #'break-overshoot = #'(-0.5 . 1.0)
+ \override TextScript #'staff-padding = #6
+ \override Glissando #'thickness = #3
+ \override SpacingSpanner #'strict-grace-spacing = ##t
+ \override TupletBracket #'bracket-visibility = ##t
+ \override NoteColumn #'ignore-collision = ##t
+ }
+}
+
+\paper {
+ oddHeaderMarkup = \markup \fill-line { " " }
+ evenHeaderMarkup = \markup \fill-line { " " }
+ oddFooterMarkup = \markup {
+ \fill-line {
+ \bold \fontsize #3 \on-the-fly #print-page-number-check-first \fromproperty #'page:page-number-string } }
+ evenFooterMarkup = \markup {
+ \fill-line {
+ \bold \fontsize #3 \on-the-fly #print-page-number-check-first \fromproperty #'page:page-number-string } }
+ printfirst-page-number = ##t
+ print-page-number = ##t
+ ragged-last-bottom = ##t
+}
+
+#(set-global-staff-size 14)
+
+
+%% definitions.
+
+
+ppX = #(make-dynamic-script (markup #:combine #:transparent #:dynamic "f" #:line(#:hspace 0 #:dynamic "pp" #:hspace 0)))
+pX = #(make-dynamic-script (markup #:combine #:transparent #:dynamic "f" #:line(#:hspace 0 #:dynamic "p" #:hspace 0)))
+mpX = #(make-dynamic-script (markup #:combine #:transparent #:dynamic "f" #:line(#:hspace 0 #:dynamic "mp" #:hspace 0)))
+fX = #(make-dynamic-script (markup #:combine #:transparent #:dynamic "f" #:line(#:hspace 0 #:dynamic "f" #:hspace 0)))
+ffX = #(make-dynamic-script (markup #:combine #:transparent #:dynamic "f" #:line(#:hspace 0 #:dynamic "ff" #:hspace 0)))
+sfp = #(make-dynamic-script "sfp")
+sfpp = #(make-dynamic-script "sfpp")
+sffp = #(make-dynamic-script "sffp")
+sffpp = #(make-dynamic-script "sffpp")
+
+beam = #(define-music-function (parser location left right) (number? number?)
+ (cond ((and (= left 0) (> right 0))
+ #{
+ \set stemRightBeamCount = #$right
+ #})
+
+ ((and (> left 0) (= right 0))
+ #{
+ \set stemLeftBeamCount = #$left
+ #})
+
+ (else
+ #{
+ \set stemLeftBeamCount = #$left
+ \set stemRightBeamCount = #$right
+ #})
+ )
+)
+
+fraction = #(define-music-function (parser location music) (ly:music?)
+ #{ \tweak #'text #tuplet-number::calc-fraction-text $music #})
+
+triangle = #(define-music-function (parser location music) (ly:music?)
+ #{ \once \set shapeNoteStyles = #'#(do do do do do do do) $music #})
+
+semicircle = #(define-music-function (parser location music) (ly:music?)
+ #{ \once \set shapeNoteStyles = #'#(re re re re re re re) $music #})
+
+blackdiamond = #(define-music-function (parser location music) (ly:music?)
+ #{ \once \set shapeNoteStyles = #'#(mi mi mi mi mi mi mi) $music #})
+
+tiltedtriangle = #(define-music-function (parser location music) (ly:music?)
+ #{ \once \set shapeNoteStyles = #'#(fa fa fa fa fa fa fa) $music #})
+
+square = #(define-music-function (parser location music) (ly:music?)
+ #{ \once \set shapeNoteStyles = #'#(la la la la la la la) $music #})
+
+wedge = #(define-music-function (parser location music) (ly:music?)
+ #{ \once \set shapeNoteStyles = #'#(ti ti ti ti ti ti ti) $music #})
+
+harmonic = #(define-music-function (parser location music) (ly:music?)
+ #{ \once \set shapeNoteStyles = #'#(harmonic harmonic harmonic harmonic harmonic harmonic harmonic) $music #})
+
+cross = #(define-music-function (parser location music) (ly:music?)
+ #{ \once \set shapeNoteStyles = #'#(cross cross cross cross cross cross cross) $music #})
+
+white = #(define-music-function (parser location music) (ly:music?)
+ #{ \once \override NoteHead #'duration-log = #1 $music #})
+
--- /dev/null
+\version "2.12.0"
+% the example header file caused the head to be chopped off
+%\include "example-header.ily"
+
+
+\header {
+ dedication = "Carin Levine"
+ instrument = "bass flute"
+ title = "ČÁRY"
+ year = "2004--2006"
+
+ subtitle = \markup { \italic Sorcery (extract) }
+ % Measures 6 - 10;
+
+ composer = "Trevor Bača"
+ copyright = "Copyright 2006 Trevor Bača, licensed under the FDL 1.1 or higher"
+
+}
+
+% Verbatim from composer's score.
+%
+% Upper staff gives fingerings;
+% Lower staff gives special types of breath.
+%
+% Copyright 2006 Trevor Baca, but this exerpt is licensed under
+% the FDL 1.1 or higher.
+
+\include "english.ly"
+\include "cary-layout.ily"
+
+\new Score <<
+
+ \new StaffGroup <<
+
+ \new Staff \with {
+ \override Stem #'direction = #down
+ \override Beam #'positions = #'(-7 . -7)
+ \override TupletBracket #'direction = #down
+ \override TupletBracket #'staff-padding = #5
+ \override TupletBracket #'padding = #2.25
+ \override VerticalAxisGroup #'minimum-Y-extent = #'(10 . 10)
+ } <<
+
+ \new Voice {
+
+ \override Score.MetronomeMark #'extra-offset = #'(0 . 6)
+ \override Score.MetronomeMark #'font-size = #3
+ \tempo 8=42
+ \time 5/16 s4 ~ s16 \noBreak % measure 6
+ \time 4/8 s2 \noBreak % measure 7
+ \time 4/8 s2 \noBreak % measure 8
+
+ }
+
+ \new Voice \with {
+ \remove Forbid_line_break_engraver
+ } {
+
+ % measure 6
+ \fraction \times 5/3 {
+ \times 4/5 {
+ a'64 [ % 36
+ cs''64 % 37
+ f''64 % 38
+ cs''64 % 39
+ ef'''64 ] % 40
+ }
+ \times 4/5 {
+ g''64 [ % 41
+ c''64 % 42
+ e''64 % 43
+ g''64 % 44
+ ef'''64 ] % 45
+ }
+ bf''16 % 46
+ }
+
+ % measure 7
+ r8 % 47
+ \times 4/5 {
+ d''32 [ % 48
+ af''32 % 49
+ e'32 % 50
+ b'32 % 51
+ b'32 ] % 52
+ }
+ ef'''4 % 53
+
+ % measure 8
+ b''8 [ % 54
+ g''8 ] % 55
+ d''4 % 56
+
+ }
+ >>
+
+ \new Staff \with {
+ \override Clef #'transparent = ##t
+ \override StaffSymbol #'line-positions = #'(-4 -2 2 4)
+ \override Stem #'direction = #down
+ \override TupletBracket #'staff-padding = #5
+ \override TupletBracket #'padding = #2.25
+ \override VerticalAxisGroup #'minimum-Y-extent = #'(10 . 10)
+ } <<
+
+ \new Voice \with {
+ \remove Forbid_line_break_engraver
+ \override Stem #'direction = #up
+ \override Stem #'stroke-style = #"grace"
+ \override Stem #'font-size = #-3
+ \override Rest #'transparent = ##t
+ \override NoteHead #'no-ledgers = ##t
+ \override Dots #'transparent = ##t
+ \override TupletBracket #'transparent = ##t
+ \override TupletNumber #'transparent = ##t
+ } {
+
+ % measure 6
+ \fraction \times 5/3 {
+ \square f''16 * 1/8 % 40
+ \square f''16 * 1/8 % 41
+ \square f''16 * 1/8 % 42
+ \square f''16 * 1/8 % 43
+ \square f''16 * 1/8 % 44
+ \square f''16 * 1/8 % 45
+ \square f''16 * 1/8 % 46
+ \square f''16 * 1/8 % 47
+ \times 2/3 {
+ \square f''16 % 48
+ \square f''16 * 1/2 % 49
+ }
+ \times 2/3 {
+ \square f''16 * 1/4 % 50
+ \square f''16 * 1/4 % 51
+ \square f''16 * 1/4 % 52
+ \square f''16 * 1/4 % 53
+ \square f''16 * 1/4 % 54
+ \square f''16 * 1/4 % 55
+ }
+ }
+
+ % measure 7
+ s8 % 56
+ \square g''16 * 2/1 % 57
+ \square g''16 % 58
+ \square g''16 % 59
+ \times 8/9 {
+ s16 % 60
+ f''16 * 1/4 % 61
+ f''16 * 1/4 % 62
+ f''16 * 1/4 % 63
+ f''16 * 1/4 % 64
+ f''16 * 1/4 % 65
+ }
+
+ % measure 8
+ \times 4/5 {
+ \times 4/7 {
+ s4 % 66
+ \triangle a''16 % 67
+ \triangle a''16 % 68
+ \triangle a''16 % 69
+ }
+ s8 % 70
+ \triangle a''16 * 1/2 % 71
+ \triangle a''16 * 1/2 % 72
+ \triangle a''16 * 1/2 % 73
+ \triangle a''16 * 1/2 % 74
+ \triangle a''16 * 1/2 % 75
+ \triangle g''16 * 1/2 % 76
+ \triangle g''16 * 1/2 % 77
+ \triangle g''16 * 1/2 % 78
+ }
+
+ }
+
+ \new Voice \with {
+ \remove Forbid_line_break_engraver
+ \override Stem #'transparent = ##t
+ \override Rest #'transparent = ##t
+ \override Rest #'staff-position = #-0.5
+ \override Dots #'transparent = ##t
+ \override Beam #'transparent = ##t
+ \override TupletBracket #'transparent = ##t
+ \override TupletNumber #'transparent = ##t
+ } {
+
+ % measure 6
+ \fraction \times 5/3 {
+ \blackdiamond f'128 [ % 40
+ \blackdiamond f'128 % 41
+ \blackdiamond f'128 % 42
+ \blackdiamond f'128 % 43
+ \blackdiamond f'128 % 44
+ \blackdiamond f'128 % 45
+ \blackdiamond f'128 % 46
+ \blackdiamond f'128 ] % 47
+ \times 2/3 {
+ \blackdiamond f'16 % 48
+ \blackdiamond f'32 % 49
+ }
+ \times 2/3 {
+ \blackdiamond f'64 % 50
+ \blackdiamond f'64 % 51
+ \blackdiamond f'64 % 52
+ \blackdiamond f'64 % 53
+ \blackdiamond f'64 % 54
+ \blackdiamond f'64 % 55
+ }
+ }
+
+ % measure 7
+ s8 % 56
+ \harmonic a'8 \glissando % 57
+ \harmonic a'16 \glissando % 58
+ \blackdiamond a'16 % 59
+ \times 8/9 {
+ s16 % 60
+ \harmonic g'64 \glissando % 61
+ \harmonic g'64 \glissando % 62
+ \harmonic g'64 \glissando % 63
+ \harmonic g'64 \glissando % 64
+ \blackdiamond g'64 % 65
+ }
+
+ % measure 8
+ \times 4/5 {
+ \times 4/7 {
+ s4 % 66
+ \blackdiamond f'16 % 67
+ \blackdiamond f'16 % 68
+ \blackdiamond f'16 % 69
+ }
+ s8 % 70
+ \blackdiamond f'32 % 71
+ \blackdiamond f'32 % 72
+ \blackdiamond f'32 % 73
+ \blackdiamond f'32 % 74
+ \blackdiamond f'32 % 75
+ \harmonic e'32 \glissando % 76
+ \harmonic e'32 \glissando % 77
+ \blackdiamond e'32 % 78
+ }
+
+ }
+
+ \new Voice \with {
+ \remove Forbid_line_break_engraver
+ \override Stem #'direction = #down
+ \override Stem #'font-size = #-3
+ \override Stem #'stroke-style = #"grace"
+ \override Rest #'transparent = ##t
+ \override NoteHead #'no-ledgers = ##t
+ \override Dots #'transparent = ##t
+ \override TupletBracket #'transparent = ##t
+ \override TupletNumber #'transparent = ##t
+ } {
+
+ % measure 6
+ \fraction \times 5/3 {
+ s128 % 40
+ s128 % 41
+ s128 % 42
+ s128 % 43
+ s128 % 44
+ s128 % 45
+ s128 % 46
+ s128 % 47
+ \times 2/3 {
+ \semicircle a16 % 48
+ \semicircle a16 * 1/2 % 49
+ }
+ \times 2/3 {
+ \semicircle a16 * 1/4 % 50
+ \semicircle a16 * 1/4 % 51
+ \semicircle a16 * 1/4 % 52
+ \semicircle a16 * 1/4 % 53
+ \semicircle a16 * 1/4 % 54
+ \semicircle a16 * 1/4 % 55
+ }
+ }
+
+ % measure 7
+ s8 % 56
+ s8 % 57
+ s16 % 58
+ \triangle a16 % 59
+ \times 8/9 {
+ s16 % 60
+ s64 % 61
+ s64 % 62
+ s64 % 63
+ s64 % 64
+ \triangle a16 * 1/4 % 65
+ }
+
+ % measure 8
+ \times 4/5 {
+ \times 4/7 {
+ s4 % 66
+ \semicircle a16 % 67
+ \semicircle a16 % 68
+ \semicircle a16 % 69
+ }
+ s8 % 70
+ \semicircle a16 * 1/2 % 71
+ \semicircle a16 * 1/2 % 72
+ \semicircle a16 * 1/2 % 73
+ \semicircle a16 * 1/2 % 74
+ \semicircle a16 * 1/2 % 75
+ s32 % 76
+ s32 % 77
+ \semicircle a16 * 1/2 % 78
+ }
+
+ }
+
+ \new Voice \with {
+ \remove Forbid_line_break_engraver
+ \override Stem #'direction = #down
+ \override NoteHead #'transparent = ##t
+ \override NoteHead #'no-ledgers = ##t
+ \override Rest #'staff-position = #-18
+ \override Stem #'length = #10
+ \override Beam #'positions = #'(-13 . -13)
+ \override DynamicLineSpanner #'staff-padding = #18
+ \override TextSpanner #'(bound-details left text) = #(markup (#:italic "covered"))
+ \override TextSpanner #'dash-period = #1
+ \override TextSpanner #'dash-fraction = #0.2
+ \override TextSpanner #'(bound-details left padding) = #0.5
+ \override TextSpanner #'(bound-details right padding) = #0.5
+ \override TextSpanner #'staff-padding = #4
+ } {
+
+ % measure 6
+ \fraction \times 5/3 {
+ \beam #0 #5 g,128 \sffp \< [ % 40
+ \beam #5 #5 g,128 % 41
+ \beam #5 #5 g,128 % 42
+ \beam #5 #5 g,128 % 43
+ \beam #5 #5 g,128 % 44
+ \beam #5 #5 g,128 % 45
+ \beam #5 #5 g,128 % 46
+ \beam #5 #1 g,128 % 47
+ \times 2/3 {
+ \beam #1 #2 g,16 % 48
+ \beam #3 #1 g,32 \fX % 49
+ }
+ \times 2/3 {
+ \beam #1 #4 g,64 \sffp \< % 50
+ \beam #4 #4 g,64 % 51
+ \beam #4 #4 g,64 % 52
+ \beam #4 #4 g,64 % 53
+ \beam #4 #4 g,64 % 54
+ \beam #4 #0 g,64 \fX ] % 55
+ }
+ }
+
+ % measure 7
+ r8 % 56
+ g,8 \sf \< [ % 57
+ g,16 % 58
+ \beam #2 #0 g,16 \ffX ] % 59
+ \times 8/9 {
+ r16 % 60
+ \beam #4 #4 g,64 \sfp \< [ % 61
+ \beam #4 #4 g,64 % 62
+ \beam #4 #4 g,64 % 63
+ \beam #4 #4 g,64 % 64
+ \beam #4 #0 g,64 \fX ] % 65
+ }
+
+ % measure 8
+ \times 4/5 {
+ \times 4/7 {
+ r4 % 66
+ \beam #2 #2 g,16 \fX [ % 67
+ \beam #2 #2 g,16 \f % 68
+ \beam #2 #0 g,16 \fX ] % 69
+ }
+ r8 % 70
+ \beam #3 #3 g,32 \fX [ % 71
+ \beam #3 #3 g,32 \fX % 72
+ \beam #3 #3 g,32 \fX % 73
+ \beam #3 #3 g,32 \fX % 74
+ \beam #3 #3 g,32 \fX % 75
+ \beam #3 #3 g,32 \sf \< % 76
+ \beam #3 #3 g,32 % 77
+ \beam #3 #0 g,32 \ffX ] % 78
+ }
+
+ }
+ >>
+ >>
+>>
--- /dev/null
+\version "2.12.0"
+\include "example-header.ily"
+
+\include "predefined-guitar-fretboards.ly"
+
+#(set-global-staff-size 17)
+
+global = {
+ \time 4/4
+ \key g \major
+ \partial 4
+ \numericTimeSignature
+}
+
+melody = \relative c' {
+ \global
+ d4
+ g4 b8( a) g4 fis
+ e e e e
+ a c8( b) a4 g
+ fis a d
+}
+
+harmonies = \chordmode {
+ \global
+ s4 g1 | c | a:m | d % 1-3
+}
+
+text = \lyricmode {
+ My eyes are dim, I can -- not see,
+ I have not brought my specs with me!
+}
+
+\score {
+ <<
+ \new ChordNames { \harmonies }
+ \new FretBoards { \harmonies }
+ \new Staff {
+ \context Voice = "vocal" { \melody }
+ }
+ \new Lyrics \lyricsto "vocal" \text
+ >>
+}
+
--- /dev/null
+\version "2.11.33"
+\paper{
+ indent=0\mm
+ ragged-last=##f
+ ragged-right=##f
+ line-width=158\mm % produces 624 pixels
+ oddFooterMarkup=##f
+ oddHeaderMarkup=##f
+ bookTitleMarkup = ##f
+ scoreTitleMarkup = ##f
+}
+
+\layout {
+ \context { \Score
+ \override PaperColumn #'keep-inside-line = ##t
+ \override NonMusicalPaperColumn #'keep-inside-line = ##t
+ }
+}
+
+
--- /dev/null
+\version "2.12.0"
+\include "example-header.ily"
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+% This is a brief passage from Enrique Granados %
+% Goyescas, "Coloquio en la Reja." %
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+#(set-global-staff-size 17)
+
+\paper {
+ ragged-right = ##f
+ #(set-paper-size "letter" 'landscape)
+ system-count = 1
+}
+
+
+csh = \change Staff = "high"
+csm = \change Staff = "middle"
+csl = \change Staff = "low"
+
+crmolto = \markup { \italic \large "cresc. molto" }
+appassmolto = \markup { \italic \large "appassionato molto" }
+
+#(ly:set-option 'point-and-click #f)
+
+global = {
+ \time 3/4
+ \set fontSize = #1
+ \override Beam #'thickness = #0.5
+ \override NoteColumn #'ignore-collision = ##t
+}
+
+upperVoiceOne = \relative c'' {
+ \voiceOne
+ \override TupletBracket #'transparent = ##t
+ <aes f'>8\([ \times 4/5{g'32( aes g f g]) }
+ <es aes>8[ \times 4/5{<d bes'>32( c' bes aes bes]) }
+ <es, aes es'>8 <d fis b d>\) | % end m. 1
+ %--------------------------------------------------%
+ <c g' c>4\( \voiceTwo <bes es bes'\arpeggio>\)
+ \slurUp <aes aes'>16( <bes bes'> <g g'>8) % end m. 2
+ %--------------------------------------------------%
+ \noBreak
+ \voiceOne
+ <f aes d f>8\([ \times 4/5{<g g'>32( aes' g f g]) }
+ \set subdivideBeams = ##t
+ \set beatLength = #(ly:make-moment 1 8)
+ <aes, aes'>16 <c f> \times 4/5{ bes'32( c bes aes bes]) }
+ \set subdivideBeams = ##f
+ \ottava #1 <es es'>16 <f f'> <d d'> \appoggiatura f8 <es es'>16\)
+}
+
+upperVoiceTwo = \relative c'' {
+ \voiceTwo
+ s8 c8\< <bes, f'>[ <bes aes'> c' <bes, d fis>\!]
+ s32 s32_\appassmolto s8. \voiceOne r8 <bes'' es bes'>-> s4
+ \override Stem #'cross-staff = ##t
+ \override Stem #'length = #28
+ \override Stem #'flag-style = #'no-flag
+ s8 \voiceTwo g,8 aes4 s4
+}
+
+middleVoiceOne = \relative c' {
+ \override Stem #'cross-staff = ##t
+ \override Stem #'length = #32
+ \override Stem #'flag-style = #'no-flag
+ d!8\noBeam s8 s8 s8_\crmolto s4 % 1
+ s4 <g bes\arpeggio>8[ <es' g>] \voiceOne e,8( dis16 e) | % 2
+ \revert Stem #'length
+ \revert Stem #'cross-staff
+ \showStaffSwitch
+ \csh \stemUp f4 s2
+ %s2. % beginning m. 3
+}
+
+middleVoiceTwo = \relative c' {
+ s2. | % 1
+ \override Stem #'cross-staff = ##t
+ \override Stem #'length = #24
+ \override Stem #'flag-style = #'no-flag
+ s2 \voiceTwo e!4 | % 2
+ s4 \voiceTwo <bes c es f>8 <f' aes es'>16 d' <bes, f' aes c>8 <bes' fis'> | % 3
+}
+
+lowerVoiceOne = \relative c, {
+ \override Staff.NoteCollision #'merge-differently-headed = ##t
+ \override Staff.NoteCollision #'merge-differently-dotted = ##t
+ bes8 \csm \stemDown <bes'' c es>8 s2
+ \csl \stemUp
+ \set subdivideBeams = ##t
+ \set beatLength = #(ly:make-moment 1 16)
+ s8 \hideNotes \slurUp \stemDown
+ es,,64( bes'' s64 \unHideNotes \stemUp g64[ bes c d c]) s2
+ \set subdivideBeams = ##f
+ bes,,8 \csm \stemDown <bes'' c es>8 s2
+}
+
+lowerVoiceTwo = \relative c, {
+ \voiceTwo
+ bes2.
+ \csh
+ \once \override Beam #'damping = #+inf.0
+ <bes'' es g>8 \csl \slurUp
+ %\once\override Slur #'extra-offset = #'(0 . 4)
+ es,,64 bes' es g s32.
+ c64
+ s4 <bes des>
+ bes,,2.
+}
+
+
+\score {
+ \new PianoStaff <<
+ \set PianoStaff.connectArpeggios = ##t
+% \override PianoStaff.Arpeggio #'stencil = #ly:arpeggio::brew-chord-bracket
+ \new Staff = "high" <<
+ \global
+ \context Voice = "upperVoiceOne" { \upperVoiceOne }
+ \context Voice = "upperVoiceTwo" { \upperVoiceTwo }
+ >>
+ \new Staff = "middle" <<
+ \global
+ \context Voice = "middleVoiceOne" { \middleVoiceOne }
+ \context Voice = "middleVoiceTwo" { \middleVoiceTwo }
+ >>
+ \new Staff = "low" <<
+ \clef bass
+ \global
+ \context Voice = "lowerVoiceOne" { \lowerVoiceOne }
+ \context Voice = "lowerVoiceTwo" { \lowerVoiceTwo }
+ >>
+ >>
+ \layout {
+ \context {
+ \Score
+ \override TimeSignature #'stencil = ##f
+ \remove "Bar_number_engraver"
+ }
+ }
+ %{\midi {
+ \context {
+ \Score
+ tempoWholesPerMinute = #(ly:make-moment 120 4)
+ }
+ }%}
+}
--- /dev/null
+\version "2.13.4"
+
+\header {
+ tagline = ##f
+ title = "Violent Dance For Orchestra"
+ composer = "Hu Haipeng"
+% arranger = "July 5, 2009"
+
+% poet = " I'm writing this piece because I'm terribly frustrated, facing a task which will seriously stain my aesthetics and conviction to the true art. It consists of all kinds of devils, dancing and whirling violently, turning the world into an abyss of darkness. Although the main melodies are derived from folk music, these are only a beautiful skin, and the essence of this piece is violent and evil, full of my 10 years' pain and rage. It's a large volcano of my long repressed heart!"
+}
+
+\paper{
+ line-width = 158\mm
+}
+
+%% markups
+#(define-markup-list-command (paragraph layout props args) (markup-list?)
+ (let ((indent (chain-assoc-get 'par-indent props 2)))
+ (interpret-markup-list layout props
+ (make-justified-lines-markup-list (cons (make-hspace-markup indent)
+ args)))))
+
+#(define-markup-command (vspace layout props amount) (number?)
+ "This produces a invisible object taking vertical space."
+ (let ((amount (* amount 3.0)))
+ (if (> amount 0)
+ (ly:make-stencil "" (cons -1 1) (cons 0 amount))
+ (ly:make-stencil "" (cons -1 1) (cons amount amount)))))
+
+%% text defs
+presto = \markup { \bold \italic "Presto" }
+div = \markup { \bold "Div." }
+nondiv = \markup { \bold "Non div." }
+unis = \markup { \bold "Unis." }
+piz = \markup { \bold "Pizz." }
+arc = \markup { \bold "Arco" }
+pizz = \set Staff.midiInstrument = "pizzicato strings"
+arco = \set Staff.midiInstrument = "string ensemble 1"
+pont = \markup { \bold \italic "Sul ponticello" }
+naturale = \markup { \bold \italic "Naturale" }
+moltocr = {
+ \set crescendoText = \markup { \italic "Molto cresc." }
+ \set crescendoSpanner = #'text
+ \override DynamicTextSpanner #'style = #'dotted-line
+}
+offCr = {
+ \unset crescendoText
+ \unset crescendoSpanner
+ \revert DynamicTextSpanner #'style
+}
+
+%% Layout to produce piano dynamics context
+\layout {
+ \context {
+ \type "Engraver_group"
+ \name Dynamics
+ \alias Voice
+ \consists "Output_property_engraver"
+ \consists "Skip_event_swallow_translator"
+ \consists "Axis_group_engraver"
+ \consists "Piano_pedal_engraver"
+ pedalSustainStrings = #'("Ped." "*Ped." "*")
+ pedalUnaCordaStrings = #'("una corda" "" "tre corde")
+ \consists "Script_engraver"
+ \consists "New_dynamic_engraver"
+ \consists "Dynamic_align_engraver"
+ \consists "Text_engraver"
+ \consists "Text_spanner_engraver"
+ \override VerticalAxisGroup #'minimum-Y-extent = #'(-1 . 1)
+ \override DynamicLineSpanner #'Y-offset = #0
+ \override TextScript #'font-size = #2
+ \override TextSpanner #'bound-details #'left #'stencil-align-dir-y = #CENTER
+ \override TextScript #'font-shape = #'italic
+ \override TextSpanner #'breakable = ##t
+ \override DynamicLineSpanner #'breakable = ##t
+ \override DynamicTextSpanner #'breakable = ##t
+ }
+ \context {
+ \PianoStaff
+ \accepts "Dynamics"
+ }
+ \context {
+ \Voice
+ \override Glissando #'breakable = ##t
+ \override TextSpanner #'breakable = ##t
+ \override DynamicLineSpanner #'breakable = ##t
+ \override DynamicTextSpanner #'breakable = ##t
+ \override TrillSpanner #'breakable = ##t
+ }
+}
+
+%% layout to create orchestra staff group
+%% with non-spanned barlines between two instrument groups
+\layout {
+ \context {
+ \StaffGroup
+ \name Orchestra
+ \remove "Span_bar_engraver"
+ }
+ \context {
+ \Score
+ \accepts Orchestra
+ }
+}
+
+%% Layout to produce SquareStaff context
+%% to group similar instruments in a staff group with thin square bracket
+\layout {
+ \context {
+ \StaffGroup
+ \name SquareStaff
+ systemStartDelimiter = #'SystemStartSquare
+ }
+ \context {
+ \Orchestra
+ \accepts SquareStaff
+ }
+ \context {
+ \StaffGroup
+ \accepts SquareStaff
+ }
+}
+
+%% Layout to produce MarkLine context
+%% to place rehearsal marks and texts above full score
+\layout {
+ \context {
+ \type "Engraver_group"
+ \name "MarkLine"
+ \consists "Output_property_engraver"
+ \consists "Axis_group_engraver"
+ \consists "Mark_engraver"
+ \consists "Metronome_mark_engraver"
+ \consists "Script_engraver"
+ \consists "Text_engraver"
+ \consists "Text_spanner_engraver"
+ \consists "Font_size_engraver"
+ \override VerticalAxisGroup #'minimum-Y-extent = #'(-2 . 2 )
+ \override TextSpanner #'breakable = ##t
+ }
+ \context {
+ \Score
+ \accepts "MarkLine"
+ }
+ \context {
+ \Orchestra
+ \accepts "MarkLine"
+ }
+ \context {
+ \StaffGroup
+ \accepts "MarkLine"
+ }
+}
+
+%% layout to produce a smaller markline
+%% put before 1st violin part
+\layout {
+ \context {
+ \MarkLine
+ \name "SmallMarkLine"
+ \override MetronomeMark #'outside-staff-priority = #800
+ \override RehearsalMark #'outside-staff-priority = #1200
+ }
+ \context {
+ \Score
+ \accepts SmallMarkLine
+ }
+ \context {
+ \Orchestra
+ \accepts SmallMarkLine
+ }
+ \context {
+ \StaffGroup
+ \accepts SmallMarkLine
+ }
+}
+
+modern =
+#`(Staff ,(make-accidental-rule 'same-octave 0)
+ ,(make-accidental-rule 'any-octave 0)
+ ,(make-accidental-rule 'same-octave 1))
+
+\layout {
+ \context {
+ \Score
+ autoAccidentals = #modern
+ autoCautionaries = #modern
+ }
+}
+
+ marks = \relative c' {
+ \set markFormatter = #format-mark-box-numbers
+ \tempo \presto 4.=112
+\set Score.currentBarNumber = #11
+ s2.*4 |
+ s1*9/8 |
+ }
+
+ piccolo = \relative c'''' {
+ \clef treble \key ees \minor \time 6/8
+ \transposition c''
+ R2.
+ ges,16(\mf\< ees c ees ges bes) c( bes ges bes c ees) |
+ ges8-.->\!\ff \offCr r r r4 r8 | R2. |
+ \time 9/8
+ R1*9/8 |
+ }
+
+ flutes = \relative c'''' {
+ \clef treble \key ees \minor \time 6/8
+ R2.
+ <ges, c,>16(\mf\< <ees bes> <c ges> <ees bes> <ges c,> <bes ees,>) <c ges>( <bes ees,> <ges c,> <bes ees,> <c ges> <ees bes>) |
+ <ges c,>8-.->\!\ff \offCr r r r4 r8 | R2. |
+ \time 9/8
+ R1*9/8 |
+ }
+
+ oboes = \relative c''' {
+ \clef treble \key ees \minor \time 6/8
+ R2. |
+ <ges, c,>4(\mf\< <bes ees,>8 <c ges>4 <ees bes>8) |
+ <ges c,>-.->\!\ff \offCr r r r4 r8 | R2. |
+ \time 9/8
+ R1*9/8 |
+ }
+
+ clarinets = \relative c' {
+ \clef treble \key f \minor \time 6/8
+ \transposition bes
+ <aes' d,>4(\p\< <c f,>8) <d aes>4( <f c>8) |
+ <aes d,>4( <c f,>8) <d aes>4( <f c>8) |
+ <aes d,>-.->\!\ff \offCr r r r4 r8 | R2. |
+ \time 9/8
+ R1*9/8 |
+ }
+
+ bassoons = \relative c, {
+ \clef bass \key ees \minor \time 6/8
+ <ees bes'>4.\pp\< c'^"a2" |
+ bes8-. bes-. bes-. ges-. ges-. ges-. |
+ ees-.->\!\ff \offCr <ees bes'>4\pp ~ <ees bes'>4. ~ | <ees bes'>2. |
+ \time 9/8
+ ges4\p^"I" aes8 aes ees ges ges4 aes16( ges) |
+ }
+
+ hornI = \relative c'' {
+ \clef treble \key bes \minor \time 6/8
+ \transposition f
+ r4 r8 <f bes,>4.\p\< ~ |
+ <f bes,>8-. <f bes,>-. <f bes,>-. <f bes,>-. <f bes,>-. <f bes,>-. |
+ <f bes,>-.->\!\ff \offCr r r r4 r8 | R2. |
+ \time 9/8
+ r4 r8 <b, g>2.\pp |
+ }
+
+ hornII = \relative c'' {
+ \clef treble \key bes \minor \time 6/8
+ \transposition f
+ \moltocr <des g,>2.\pp\< ~ |
+ <des g,>8-. <f bes,>-. <f bes,>-. <f bes,>-. <f bes,>-. <f bes,>-. |
+ <f bes,>-.->\!\ff \offCr r r r4 r8 | R2. |
+ \time 9/8
+ <f, des>2.\pp <f des>4. ~ |
+ }
+
+ trumpetI = \relative c''' {
+ \clef treble \key f \minor \time 6/8
+ \transposition bes
+R2. |
+ r4 r8 <aes f>-.\f\< <aes f>-. <aes f>-. |
+ <c aes>-.->\!\ff r r r4 r8 | R2. |
+ \time 9/8
+ R1*9/8 |
+ }
+
+ trumpetII = \relative c'' {
+ \clef treble \key f \minor \time 6/8
+ \transposition bes
+R2. |
+ r8 d-.\mf\< d-. d-. d-. d-. |
+ d-.->\!\ff \offCr r r r4 r8 | R2. |
+ \time 9/8
+ R1*9/8 |
+ }
+
+ trombones = \relative c' {
+ \clef tenor \key ees \minor \time 6/8
+ r4 r8 <ges c>4.\mp\< ~ |
+ <ges c>8-. <ges c>-. <ges c>-. <ges c>-. <ges c>-. <ges c>-. |
+ <ges c>-.->\!\ff \offCr r r r4 r8 | R2. |
+ \time 9/8
+ R1*9/8 |
+ }
+
+ tuba = \relative c,, {
+ \clef bass \key ees \minor \time 6/8
+ <ees' ees'>4.(\pp\< <c c'> |
+ <bes bes'>8-.) <bes bes'>-. <bes bes'>-. <ges ges'>-. <ges ges'>-. <ges ges'>-. |
+ <ees ees'>-.->\!\ff \offCr r r r4 r8 | R2. |
+ \time 9/8
+ R1*9/8 |
+ }
+
+ timpani = \relative c {
+ \clef bass \key ees \minor \time 6/8
+ ees8\< ees ees ees ees ees |
+ bes bes bes bes bes bes |
+ ees,->\!\f \offCr ees'\pp ees ees ees ees |
+ ees ees ees ees ees ees |
+ \time 9/8
+ ees r r r4 r8 r4 r8 |
+ }
+
+ trian = \relative c' {
+ \clef percussion \time 6/8
+ R2.*4 |
+ \time 9/8
+ R1*9/8 |
+ }
+
+ cym = \relative c' {
+ \clef percussion \time 6/8
+ R2.*4 |
+ \time 9/8
+ R1*9/8 |
+ }
+
+ tamt = \relative c' {
+ \clef percussion \time 6/8
+R2. |
+ r4 r8 r c4\mf\<^"*" ~ |
+ c8\!\ff r r r4 r8 | R2. |
+ \time 9/8
+ R1*9/8 |
+ }
+
+ tamb = \relative c' {
+ \clef percussion \time 6/8
+ R2.*4 |
+ \time 9/8
+ R1*9/8 |
+ }
+
+ snare = \relative c' {
+ \clef percussion \time 6/8
+ R2.*4 |
+ \time 9/8
+ c8\pp c c c c c c c c |
+ }
+
+ bsdrum = \relative c' {
+ \clef percussion \time 6/8
+ c2.:32\pp\< ~ | c: ~ |
+ c8\!\ff \offCr r r r4 r8 | R2. |
+ \time 9/8
+ c2.:32\pp ~ c4.: |
+ }
+
+ harprh = \relative c'' {
+ \clef treble \key ees \minor \time 6/8
+ \showStaffSwitch
+ R2.*4_\markup { \harp-pedal #"--^|^^^^" } |
+ \time 9/8
+ R1*9/8 |
+ }
+
+ harplh = \relative c {
+ \clef bass \key ees \minor
+ \showStaffSwitch
+ R2.*4 |
+ R1*9/8 |
+ }
+
+ dynamics = {
+ s2.*4 |
+ s1*9/8 |
+ }
+
+
+ violinI = \relative c'''' {
+ \clef treble \key ees \minor \time 6/8
+ ges,,16(\pp\< ees c ees ges bes) c( bes ges bes c ees) |
+ ges( ees c ees ges bes) c( bes ges bes c ees) |
+ ges8-.->\!\ff \offCr r r r4 r8 | R2. |
+ \time 9/8
+ R1*9/8 |
+ }
+
+ violinII = \relative c''' {
+ \clef treble \key ees \minor \time 6/8
+ c,,16(\pp\< bes ges bes c ees) ges( ees c ees ges bes) |
+ c( bes ges bes c ees) ges( ees c ees ges bes) |
+ c8-.->\!\ff \offCr r r r4 r8 | R2. |
+ \time 9/8
+ r4 r8 \repeat tremolo 6 { c,,32->\pp^\pont e } r4 r8 |
+ }
+
+ viola = \relative c {
+ \clef alto \key ees \minor \time 6/8
+ <ees bes'>8-.\pp\< <ees bes'>-. <ees bes'>-. <ges c>-. <ges c>-. <ges c>-. |
+ <bes ees>-. <bes ees>-. <bes ees>-. <c ges'>-. <c ges'>-. <c ges'>-. |
+ <ees bes'>-.->\!\ff \offCr r r r4 r8 | R2. |
+ \time 9/8
+ \repeat tremolo 12 { ges,32->^\pont bes } \repeat tremolo 6 {ges->( bes) } |
+ }
+
+ cello = \relative c {
+ \clef bass \key ees \minor \time 6/8
+ <c ges'>8-.\pp\< <c ges'>-. <c ges'>-. <bes ees>-. <bes ees>-. <bes ees>-. |
+ <c ges'>-. <c ges'>-. <c ges'>-. <c ges'>-. <c ges'>-. <c ges'>-. |
+ <bes ges'>8-.->\!\ff \offCr <c ges'>-.\pp <c ges'>-. <c ges'>-. <c ges'>-. <c ges'>-. |
+ <c ges'>-. r r r4 r8 |
+ \time 9/8
+ \repeat tremolo 12 <c ges'>32(^\pont \repeat tremolo 12 <cis g'> \repeat tremolo 12 <c ges'>) |
+ }
+
+ contrabass = \relative c {
+ \clef bass \key ees \minor \time 6/8
+ \transposition c
+ <ees bes'>8-.\pp\< ees-. ees-. c-. c-. c-. |
+ bes-. bes-. ges-. ges-. ges-. ges-. |
+ ees-.->\!\ff \offCr <ees' bes'>-.\pp <ees bes'>-. <ees bes'>-. <ees bes'>-. <ees bes'>-. |
+ <ees bes'>-. <ees bes'>-. <ees bes'>-. <ees bes'>-. <ees bes'>-. <ees bes'>-. |
+ \time 9/8
+ <ees bes'>-. <ees bes'>-. <ees bes'>-. <ees bes'>-. <ees bes'>-. <ees bes'>-. <ees bes'>-. <ees bes'>-. <ees bes'>-. |
+ }
+
+ #(set-global-staff-size 10)
+
+ \score {
+ \new Orchestra = "orchestra" <<
+ \set Score.skipBars = ##f
+ \new MarkLine { \marks }
+ \new StaffGroup = "woodwind" <<
+ \new SquareStaff = "picc fl" <<
+ \new Staff = "piccolo" {
+ \set Staff.instrumentName = "Piccolo"
+ \set Staff.shortInstrumentName = "Picc."
+ \piccolo
+ }
+ \new Staff = "flutes" {
+ \set Staff.instrumentName = "Flutes I & II"
+ \set Staff.shortInstrumentName = "Fl."
+ \flutes
+ }
+ >>
+ \new Staff = "oboes" {
+ \set Staff.instrumentName = "Oboes I & II"
+ \set Staff.shortInstrumentName = "Ob."
+ \oboes
+ }
+ \new Staff = "clarinets" {
+ \set Staff.instrumentName = \markup {
+ \column { \line { "Clarinets I & II" }
+ \line { "in B" \smaller \flat } } }
+ \set Staff.shortInstrumentName = "Cl."
+ \clarinets
+ }
+ \new Staff = "bassoons" {
+ \set Staff.instrumentName = "Bassoons I & II"
+ \set Staff.shortInstrumentName = "Bn."
+ \bassoons
+ }
+ >>
+ \new StaffGroup = "brass" <<
+ \new SquareStaff = "horns" <<
+ \new Staff = "hornsI" {
+ \set Staff.instrumentName = \markup {
+ \column { \line { "Horns I & II" }
+ \line { "in F" } } }
+ \set Staff.shortInstrumentName = "Hn. I & II"
+ \hornI
+ }
+ \new Staff = "hornsII" {
+ \set Staff.instrumentName = \markup {
+ \column { \line { "Horns III & IV" }
+ \line { "in F" } } }
+ \set Staff.shortInstrumentName = "Hn. III & IV"
+ \hornII
+ }
+ >>
+ \new SquareStaff = "trumpets" <<
+ \new Staff = "trumpetI" {
+ \set Staff.instrumentName = \markup {
+ \column { \line { "Trumpets I & II" }
+ \line { "in B" \smaller \flat } } }
+ \set Staff.shortInstrumentName = "Tp. I & II"
+ \trumpetI
+ }
+ \new Staff = "trumpetII" {
+ \set Staff.instrumentName = \markup {
+ \column { \line { "Trumpet III" }
+ \line { "in B" \smaller \flat } } }
+ \set Staff.shortInstrumentName = "Tp. III"
+ \trumpetII
+ }
+ >>
+ \new SquareStaff = "trombones" <<
+ \new Staff = "trombones 1 & 2" {
+ \set Staff.instrumentName = "Trombones I & II"
+ \set Staff.shortInstrumentName = "Tb. I & II"
+ \trombones
+ }
+ \new Staff = "tuba" {
+ \set Staff.instrumentName = "Bass trombone & Tuba"
+ \set Staff.shortInstrumentName = "Btb. & Tu."
+ \tuba
+ }
+ >>
+ >>
+ \new Staff = "timpani" {
+ \set Staff.instrumentName = "Timpani in A, D & E"
+ \set Staff.shortInstrumentName = "Tim."
+ \timpani
+ }
+ \new GrandStaff = "drums" <<
+ \new RhythmicStaff = "triangle" {
+ \set RhythmicStaff.instrumentName = "Triangle"
+ \set RhythmicStaff.shortInstrumentName = "Tri."
+ \trian
+ }
+ \new RhythmicStaff = "cymbals" {
+ \set RhythmicStaff.instrumentName = "Suspended cymbal"
+ \set RhythmicStaff.shortInstrumentName = "Susp. cym."
+ \cym
+ }
+ \new RhythmicStaff = "tamtam" {
+ \set RhythmicStaff.instrumentName = "Tamtam"
+ \set RhythmicStaff.shortInstrumentName = "Tamt."
+ \tamt
+ }
+ \new RhythmicStaff = "tambourine" {
+ \set RhythmicStaff.instrumentName = "Tambourine"
+ \set RhythmicStaff.shortInstrumentName = "Tamb."
+ \tamb
+ }
+ \new RhythmicStaff = "snare" {
+ \set RhythmicStaff.instrumentName = "Snare drum"
+ \set RhythmicStaff.shortInstrumentName = "Sn."
+ \snare
+ }
+ \new RhythmicStaff = "bass drum" {
+ \set RhythmicStaff.instrumentName = "Bass drum"
+ \set RhythmicStaff.shortInstrumentName = "Bd."
+ \bsdrum
+ }
+ >>
+ \new PianoStaff = "harp" <<
+ \set PianoStaff.instrumentName = "Harp"
+ \set PianoStaff.shortInstrumentName = "Hrp."
+ \set PianoStaff.connectArpeggios = ##t
+ \new Staff = "rh" { \harprh }
+ \new Dynamics { \dynamics }
+ \new Staff = "lh" { \harplh }
+ >>
+ \new SmallMarkLine { \marks }
+ \new StaffGroup = "strings" <<
+ \new SquareStaff = "violins" <<
+ \new Staff = "violin I" {
+ \set Staff.instrumentName = "Violin I"
+ \set Staff.shortInstrumentName = "Vn. I"
+ \violinI
+ }
+ \new Staff = "violin II" {
+ \set Staff.instrumentName = "Violin II"
+ \set Staff.shortInstrumentName = "Vn. II"
+ \violinII
+ }
+ >>
+ \new Staff = "viola" {
+ \set Staff.instrumentName = "Viola"
+ \set Staff.shortInstrumentName = "Vl."
+ \viola
+ }
+ \new SquareStaff = "Cello and Bass" <<
+ \new Staff = "violoncello" {
+ \set Staff.instrumentName = "Violoncello"
+ \set Staff.shortInstrumentName = "Vc."
+ \cello
+ }
+ \new Staff = "contrabass" {
+ \set Staff.instrumentName = "Contrabass"
+ \set Staff.shortInstrumentName = "Cb."
+ \contrabass
+ }
+ >>
+ >>
+ >>
+ \layout {
+ \context {
+ \Score
+ \remove "Mark_engraver"
+ \remove "Metronome_mark_engraver"
+ }
+ \context {
+ \RemoveEmptyStaffContext
+ }
+ }
+ }
+
--- /dev/null
+%%% G.F Haendel, Giulio Cesare in Egitto
+%%% Act I, scene IV
+%%% Sesto: Svegliatevi nel core, furie d'un alma offesa (excerpt)
+%%%
+%%% Nicolas Sceaux <nicolas.sceaux@free.fr>
+
+\version "2.12.2"
+\include "sesto.ily"
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%%%
+%%% Lead sheet
+%%%
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+\book {
+ \paper {
+ #(layout-set-staff-size 14)
+ }
+ \score {
+ \new StaffGroupNoBar <<
+ \new StaffGroupNoBracket <<
+ \new Staff <<
+ \set Staff.instrumentName = "Violino I."
+ \global \clef treble \keepWithTag #'violin \violinoI
+ >>
+ \new Staff <<
+ \set Staff.instrumentName = "Violino II."
+ \global \clef treble \keepWithTag #'violin \violinoII
+ >>
+ >>
+ \new Staff <<
+ \new Voice = "sesto" \with { autoBeaming = ##f } <<
+ \set Staff.instrumentName = \markup \smallCaps Sesto.
+ \global \clef treble \sesto
+ >>
+ \lyricsto "sesto" \new Lyrics \sestoLyrics
+ >>
+ \new Staff <<
+ \set Staff.instrumentName = "Bassi."
+ \global \clef bass \bassi
+ >>
+ >>
+ \layout {
+ indent = 20\mm
+ \context {
+ \Score
+ \name Score
+%% FIXME: vertical engine changed!
+%% \override VerticalAlignment #'max-stretch = #ly:align-interface::calc-max-stretch
+ \accepts "StaffGroupNoBar"
+ skipBars = ##t
+ }
+ \context {
+ \StaffGroup
+ \name StaffGroupNoBar
+ \description "Like StaffGroup, but without spanbar"
+ \remove "Span_bar_engraver"
+ \accepts "StaffGroupNoBracket"
+ }
+ \context {
+ \StaffGroup
+ \name StaffGroupNoBracket
+ \description "Like StaffGroup, but without brackets"
+ \remove "System_start_delimiter_engraver"
+ }
+ }
+% \midi { }
+ }
+}
+
+
--- /dev/null
+%%% G.F Haendel, Giulio Cesare in Egitto
+%%% Act I, scene IV
+%%% Sesto: Svegliatevi nel core, furie d'un alma offesa (excerpt)
+%%%
+%%% Nicolas Sceaux <nicolas.sceaux@free.fr>
+
+\version "2.12.2"
+\include "sesto.ily"
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%%%
+%%% Reduction
+%%%
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+\book {
+ \header { instrument = "Vocal part and keyboard reduction" }
+ \paper {
+ #(layout-set-staff-size 16)
+ }
+ \score {
+ <<
+ \new Staff <<
+ \new Voice = "sesto" \with { autoBeaming = ##f } <<
+ \set Staff.instrumentName = \markup \smallCaps Sesto.
+ \global \clef treble \sesto
+ >>
+ \lyricsto "sesto" \new Lyrics \sestoLyrics
+ >>
+ \new PianoStaff <<
+ \new Staff <<
+ \global \clef treble
+ \partcombine \keepWithTag #'reduction \violinoI \keepWithTag #'reduction \violinoII
+ >>
+ \new Staff <<
+ \global \clef bass \bassi
+ >>
+ >>
+ >>
+ \layout {
+ indent = 20\mm
+ \context { \Voice printPartCombineTexts = ##f }
+ }
+ }
+}
+
--- /dev/null
+%%% G.F Haendel, Giulio Cesare in Egitto
+%%% Act I, scene IV
+%%% Sesto: Svegliatevi nel core, furie d'un alma offesa (excerpt)
+%%%
+%%% Nicolas Sceaux <nicolas.sceaux@free.fr>
+
+\version "2.12.2"
+\include "sesto.ily"
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%%%
+%%% Violino I
+%%%
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+\book {
+ \header { instrument = "Violino I" }
+ \paper {
+ #(layout-set-staff-size 18)
+ }
+ \score {
+ \new Staff <<
+ \global \clef treble \keepWithTag #'violin \violinoI
+ >>
+ \layout { indent = 5\mm }
+ }
+}
--- /dev/null
+%%% G.F Haendel, Giulio Cesare in Egitto
+%%% Act I, scene IV
+%%% Sesto: Svegliatevi nel core, furie d'un alma offesa (excerpt)
+%%%
+%%% Nicolas Sceaux <nicolas.sceaux@free.fr>
+
+\version "2.12.2"
+\header {
+ title = "Giulio Cesare in Egitto"
+ subtitle = "Sesto: Svegliatevi nel core, furie d'un alma offesa (excerpt)"
+ composer = "G.F Handel"
+}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%%%
+%%% Notes and lyrics
+%%%
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+sesto = {
+ R1*6 |
+ r4 r8 g' c'' ees''16[ d''] c''8 c'' |
+ c'' g' ees''4 ~ ees''8 d''16 ees'' f''8 aes' |
+ aes' g' r c'' c'' b'16[ c''] d''8 g' |
+
+%{
+ %%10
+ f'4 r8 d'' ees'' d''16[ c''] b'4 |
+ c'' r8 c'' c''8. c'16 c'4 |
+ r r8 c'' aes' c''16[ bes'] aes'8 g' |
+ f' f' r4 bes'8 bes'16 aes' g'8 f' |
+ ees' ees' r ees'' ees'' d''16[ ees''] f''8 bes' |
+ %%15
+ aes'4. bes'8 g' ees'' f'4 |
+ ees' r8 ees'' ees''8. ees'16 ees'4 |
+ r r8 c'' c''8. c'16 c'4 |
+ r r8 c'' c'' d''16[ ees''] f''8 ees'' |
+ d'' bes' r4 bes'8 c''16 d'' ees''8 d'' |
+ %%20
+ c'' c'' r c'' f' f''16[ ees''] d''8 c'' |
+ b'16[ a'] g'8 r4 ees''8 ees''16 d'' c''8 bes' |
+ aes' g' r g' aes' f' d'' b' |
+ f''2 ~ f''8 d'' b' g' |
+ ees'4 r8 d'' ees'' d''16[ c''] b'4 |
+ %%25
+ c'' r8 g' c'' g' ees' g' |
+ c'4 r8 g' aes' f' d'' b' |
+ f''2 ~ f''8 d'' b' g' |
+ ees'4 r8 g'' ees'' d''16[ c''] b'4 |
+ c''2 r |
+ %%30
+ R1*5 |
+%}
+}
+
+sestoLyrics = \lyricmode {
+ Sve -- glia -- te -- vi nel co -- re,
+ fu -- rie "d'un" al -- "ma of" -- fe -- sa,
+%{
+ a far "d'un" tra -- di -- tor a -- spra ven -- det -- ta!
+ sve -- glia -- te -- vi,
+ sve -- glia te -- vi nel co -- re,
+ fu -- rie d'un al -- "ma of" -- fe -- sa,
+ a far "d'un" tra -- di -- tor as -- pra ven -- det -- ta,
+ sve -- glia -- te -- vi,
+ sve -- glia -- te -- vi,
+ sve -- glia -- te -- vi nel co -- re,
+ fu -- rie d'un al -- "ma of" -- fe -- sa,
+ sve -- glia -- te -- vi nel co -- re,
+ fu -- rie d'un al -- "ma of" -- fe -- sa,
+ a far d'un tra -- di -- tor, __
+ d'un tra -- di -- tor as -- spra ven -- det -- ta,
+ a far d'un tra -- di -- tor,
+ a far d'un tra -- di -- tor, __
+ d'un tra -- di -- tor as -- pra ven -- det -- ta!
+%}
+}
+
+violinoI = {
+ r4 r8 g' c'' ees''16 d'' c''8 c'' |
+ c'' c' ees''4 ~ ees''8 d''16 ees'' f''8 aes' |
+ aes' g' r c'' c''8.^\trill b'32 c'' d''8 g' |
+ f'4. d''8 ees'' d''16 c'' b'4 |
+ %%5
+ c''16 g'' f'' g'' ees'' g'' f'' g'' ees'' g'' f'' g'' ees'' g'' f'' g'' |
+ c'' g'' f'' g'' ees'' g'' f'' g'' aes''8 g''16 f'' f''4^\trill |
+ ees'' r8 g'_\p c'' ees''16 d'' c''8 c'' |
+ c'' g' ees''4 ~ ees''8 d''16 ees'' f''8 aes' |
+ aes' g' r c'' c'' b'16 c'' d''8 g' |
+%{
+ %%10
+ f'4 r8 d'' ees'' d''16 c'' b'4 |
+ c''16 g'' f'' g'' ees'' g'' f'' g'' ees'' g'' f'' g'' ees'' g'' f'' g'' |
+ ees'' g'' f'' g'' ees'' g'' f'' g'' aes''8 aes' r4 |
+ d''16 f'' ees'' f'' d'' f'' ees'' f'' g''8 g' r4 |
+ ees'16 g' f' g' ees'8 ees'' ees'' d''16 ees'' f''8 bes' |
+ %%15
+ aes'4. bes'8 g' ees'' d''4 |
+ ees''16 bes'' aes'' bes'' g'' bes'' aes'' bes'' g'' bes'' aes'' bes'' g'' bes'' aes'' bes'' |
+ g'' g'' f'' g'' ees'' g'' f'' g'' ees'' g'' f'' g'' ees'' g'' f'' g'' |
+ ees'' g'' f'' g'' ees'' g'' f'' g'' aes'' c'' c'' bes' aes' c'' bes' c'' |
+ d'' f'' ees'' f'' d'' f'' ees'' f'' g'' bes' bes' aes' g' bes' aes' bes' |
+ %%20
+ c'' ees'' ees'' f'' g'' ees'' f'' g'' aes'' f'' g'' ees'' f'' d'' ees'' c'' |
+ \tag #'violin { g'' g' g'' g'' } \tag #'reduction { g'' d'' g'' g'' } g'' b' g'' g'' g'' f'' ees'' d'' c''8 bes' |
+ aes' g' r g' aes' f' d'' b' |
+ f''2 ~ f''8 d'' b' g' |
+ ees'16 c' g' ees' c'' g' g'' d'' g'4 r |
+ %%25
+ c'''16 ees''' d''' ees''' c''' ees''' d''' ees''' g'' c''' b'' c''' g'' c''' b'' c''' |
+ ees'' g'' f'' g'' ees'' g'' f'' g'' \tag #'violin { aes'8 f' } \tag #'reduction { c''8 aes' } d'' b' |
+ f''2 ~ f''8 d'' b' g' |
+ ees'4^\fermata r r2 |
+ r4 r8 c'_\f c'' ees''16 d'' c''8 c'' |
+ %%30
+ c'' c' ees''4 ~ ees''8 d''16 ees'' f''8 aes' |
+ aes' g' r g' aes' f' d'' b' |
+ f''2 ~ f''8 d'' b' g' |
+ c''16 g'' f'' g'' ees'' g'' f'' g'' c'' g'' f'' g'' ees'' g'' f'' g'' |
+ b'8 c''16 d'' ees''8 d'' c''4^\fermata r
+%}
+}
+
+violinoII = {
+ r4 r8 g' c'' ees''16 d'' c''8 c'' |
+ c'' c' ees''4 ~ ees''8 d''16 ees'' f''8 aes' |
+ aes' g' r c'' c''8.^\trill b'32 c'' d''8 g' |
+ f'4. d''8 ees'' d''16 c'' b'4 |
+ %%5
+ c''16 ees'' d'' ees'' c'' ees'' d'' ees'' c'' ees'' d'' ees'' c'' ees'' d'' ees'' |
+ c'' ees'' d'' ees'' c'' ees'' d'' ees'' d''8[ ees''] ees'' d'' |
+ ees''4 r8 g' c'' ees''16 d'' c''8 c'' |
+ c'' g' ees''4 ~ ees''8 d''16 ees'' f''8 aes' |
+ aes' g' r c'' c'' b'16 c'' d''8 g' |
+%{
+ %%10
+ f'4 r8 d'' ees'' d''16 c'' b'4 |
+ c''16 ees'' d'' ees'' c'' ees'' d'' ees'' c'' ees'' d'' ees'' c'' ees'' d'' ees'' |
+ c'' ees'' d'' ees'' c'' ees'' d'' ees'' f''8 f' r4 |
+ bes'16 d'' c'' d'' bes' d'' c'' d'' ees''8 ees' r4 |
+ c'16 ees' d' ees' c'8 ees'' ees'' d''16 ees'' f''8 bes' |
+ %%15
+ aes'4. bes'8 g' ees'' d''4 |
+ ees''16 g'' f'' g'' ees'' g'' f'' g'' ees'' g'' f'' g'' ees'' g'' f'' g'' |
+ ees'' ees'' d'' ees'' c'' ees'' d'' ees'' c'' ees'' d'' ees'' c'' ees'' d'' ees'' |
+ c'' ees'' d'' ees'' c'' ees'' d'' ees'' f'' aes' aes' g' f' aes' g' aes' |
+ bes' d'' c'' d'' bes' d'' c'' d'' ees'' g' g' f' ees' g' f' g' |
+ %%20
+ aes' c'' c'' d'' ees'' c'' d'' ees'' f'' d'' ees'' c'' d'' b' c'' a' |
+ \tag #'violin { b' d' d' b' } \tag #'reduction { b' g' d'' b' } b' g' b' d'' g'' f'' ees'' d'' c''8 bes' |
+ d' ees' r g' aes' f' d'' b' |
+ f''2 ~ f''8 d'' b' g' |
+ ees'16 c' g' ees' c'' g' g'' d'' g'4 r |
+ %%25
+ ees''16 g'' f'' g'' ees'' g'' f'' g'' ees'' ees'' d'' ees'' c'' ees'' d'' ees'' |
+ g' ees'' d'' ees'' c'' ees'' d'' ees'' \tag #'violin { c''8 aes' } \tag #'reduction { aes'8 f' } f' d' |
+ f''2 ~ f''8 d'' b' g' |
+ ees'4^\fermata r r2 |
+ r4 r8 c' c'' ees''16 d'' c''8 c'' |
+ %%30
+ c'' c' ees''4 ~ ees''8 d''16 ees'' f''8 aes' |
+ aes' g' r g' aes' f' d'' b' |
+ f''2 ~ f''8 d'' b' g' |
+ c''16 ees'' d'' ees'' c'' ees'' d'' ees'' c'' ees'' d'' ees'' c'' ees'' d'' ees'' |
+ d'8 ees'16 f' g'8 b' c''4^\fermata r
+%}
+}
+
+bassi = {
+ c4 r8 g c' ees'16 d' c'8 c' |
+ c' c r g aes f bes bes, |
+ ees ees, r c ees c g ees |
+ aes f d' b c' f g g, |
+ %%5
+ c4 r c'8 c bes bes, |
+ aes aes, g g, f ees bes bes, |
+ ees4 r r r8 c_\p |
+ c' ees'16 d' c'8 bes aes f bes bes, |
+ ees ees, r c ees c g ees |
+%{
+ %%10
+ aes f d' b c' f g g, |
+ c4 r r r8 c' |
+ c'8. c16 c4 r8 f d ees |
+ bes bes, r bes g aes bes g |
+ c' c c' bes16 aes g8 ees bes g |
+ %%15
+ c' c d bes, ees g bes bes, |
+ ees4 r r r8 ees' |
+ ees'8. ees16 ees4 r r8 c' |
+ c'8. c16 c8 c' aes f r f |
+ bes bes, bes, bes g ees r ees |
+ %%20
+ aes aes, g g, f f, r f |
+ g g, r4 c'8 g aes g |
+ f ees r4 r r8 g, |
+ aes, f, d b, aes f d' b |
+ c'4 r8 b c' f g g, |
+ %%25
+ c' g c g, c,4 r |
+ c'8 g c c' f4 r8 g, |
+ aes, f, d b, aes f d' b |
+ c'4 r8 b c' f g g, |
+ c4 r8 c_\f c' ees'16 d' c'8 c' |
+ %%30
+ c' c r g aes f bes bes, |
+ ees g ees c f,4 r8 g, |
+ aes, f, d b, aes f d' b |
+ c' c bes bes, aes aes, g g, |
+ f c g g, c4^\fermata r
+%}
+}
+
+global = {
+ \key c \minor
+ \set Score . tempoWholesPerMinute = #(ly:make-moment (/ 80 4) 1 0 1)
+ \time 4/4
+%s1*34 \bar "|."
+}
+
--- /dev/null
+\version "2.13.6"
+
+#(set-global-staff-size 22.45)
+
+#(define (glissando::calc-extra-dy grob)
+ (let* ((original (ly:grob-original grob))
+ (left-bound (ly:spanner-bound original LEFT))
+ (right-bound (ly:spanner-bound original RIGHT))
+ (left-pitch (ly:event-property (event-cause left-bound) 'pitch))
+ (right-pitch (ly:event-property (event-cause right-bound) 'pitch)))
+
+ (if (and (= (ly:pitch-octave left-pitch) (ly:pitch-octave right-pitch))
+ (= (ly:pitch-notename left-pitch) (ly:pitch-notename right-pitch)))
+ (- (ly:pitch-alteration right-pitch) (ly:pitch-alteration left-pitch))
+ 0 )))
+
+%% Hide fret number: useful to draw slide into/from a casual point of
+%% the fretboard.
+hideFretNumber = { \once \override TabNoteHead #'transparent = ##t
+ \once \override NoteHead #'transparent = ##t
+ \once \override Stem #'transparent = ##t
+ \once \override NoteHead #'no-ledgers = ##t
+}
+
+\paper {
+ indent= #0
+ line-width= #180
+}
+
+upper= \relative c' {
+ \time 4/4
+ \key e \major
+ \set Staff.midiInstrument = #"acoustic guitar (steel)"
+ \set fingeringOrientations = #'(left)
+
+ %\override Staff.Glissando #'extra-offset = #' (0.0 . 1.0)
+ \partial 4. \acciaccatura c16 \glissando cis8 e4
+ < cis-1 g'-3 >2 s8 \grace a16 ( \glissando <b-2>8\3 ) <d-1> ( b ) |
+ <e-3>\2 ( <d-1> b ) \grace <ais-2>16 ( \glissando a8 g ) s4. |
+ s4. < d'\3 g\2 >8 < gis,\4 d'\3 fis\2 >2\arpeggio ~ |
+
+ < gis\4 d'\3 fis\2 >2 < b'\2\harmonic e\harmonic >2\fermata |
+
+}
+
+lower= \relative c {
+ \set fingeringOrientations = #'(left)
+
+ \partial 4. s4. |
+ s4 e,4 s2 |
+ s2 s8 <e'-3>4. ~ |
+ e4 \hideFretNumber \grace { b8 \glissando s4 } <e-2>4\5 e,2 ~ |
+
+ e2 < e'\6\harmonic > |
+}
+
+\score {
+ \new StaffGroup <<
+ \new Staff = "guitar" <<
+ \context Voice = "upper guitar" { \clef "G_8" \voiceOne
+ \override Glissando #'gap = #0.5
+ \override Glissando #'extra-offset = #'(-0.5 . 0)
+ \override Glissando #'springs-and-rods = #ly:spanner::set-spacing-rods
+ \override Glissando #'minimum-length = #4
+ \override Glissando #'extra-dy = #glissando::calc-extra-dy
+ \upper }
+ \context Voice = "lower guitar" { \clef "G_8" \voiceTwo
+ \override Glissando #'bound-details #'right #'padding = #1
+ \override Glissando #'bound-details #'left #'padding = #0.2
+ \lower }
+ >>
+ \new TabStaff = "tab" <<
+ \context TabVoice = "upper tab" { \clef "moderntab" \voiceOne \upper }
+ \context TabVoice = "lower tab" { \clef "moderntab" \voiceTwo \lower }
+ >>
+ >>
+
+ \midi {
+ \context {
+ \Score tempoWholesPerMinute = #(ly:make-moment 120 4)
+ }
+ }
+
+ \layout {
+ \context {
+ \Staff
+ \override StringNumber #'transparent = ##t
+ }
+
+ \context {
+ \TabStaff
+ \revert Arpeggio #'stencil
+ }
+ }
+}
\ No newline at end of file
--- /dev/null
+\version "2.12.0"
+\include "example-header.ily"
+
+#(ly:set-option 'point-and-click #f)
+
+global = {
+ \time 4/4
+ \numericTimeSignature
+ \key c \major
+ #(set-global-staff-size 24)
+}
+
+cf = \relative c {
+ \clef bass
+ \global
+ c4 c' b a |
+ g a f d |
+ e f g g, |
+ c1
+}
+
+upper = \relative c'' {
+ \global
+ r4 s4 s2 |
+ s1*2 |
+ s2 s4 s
+ \bar "||"
+}
+
+bassFigures = \figuremode {
+ s1*2 | s4 <6> <6 4> <7> | s1
+}
+
+\markup { "Exercise 3: Write 8th notes against the given bass line." }
+
+\score {
+ \new PianoStaff <<
+ \new Staff {
+ \context Voice = "added voice" \with {
+ \consists "Balloon_engraver"
+ }
+ \upper
+ }
+
+ \new Staff = lower {
+ <<
+% \context Voice = "cantus firmus" \with {
+% \consists "Balloon_engraver"
+% }
+ \context Staff = lower \cf
+ \new FiguredBass \bassFigures
+ >>
+ }
+ >>
+ \layout {}
+ %{\midi {
+ \context {
+ \Score
+ tempoWholesPerMinute = #(ly:make-moment 120 4)
+ }
+ }%}
+}
+
--- /dev/null
+@c -*- coding: utf-8; mode: texinfo; -*-
+@ignore
+ Translation of GIT committish: FILL-IN-HEAD-COMMITTISH
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+@node introduction
+@unnumbered Introduction
+
+@divClass{column-center-top}
+@subheading Our Goal
+
+@imageFloat{flat-design,png,right}
+
+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!
+@divEnd
+
+@divClass{column-left-top}
+@subheading Why use LilyPond?
+
+@itemize
+
+@item
+@ref{features}: What can LilyPond do?
+
+@item
+@ref{examples}: I want to see some music!
+
+@item
+@ref{freedom}: LilyPond is Free Software.
+
+@item
+@ref{background}: Our computational aesthetics.
+
+@end itemize
+@divEnd
+
+@divClass{column-right-top}
+@subheading Who uses it?
+
+@itemize
+
+@item
+@ref{productions}: Real-life use of LilyPond.
+
+@item
+@ref{testimonials}: What do people say?
+
+@end itemize
+@divEnd
+
+@divClass{column-center-bottom}
+@subheading Why not use LilyPond?
+
+@itemize
+
+@item
+@ref{text input}: You write music as @emph{text}?!
+
+@item
+@ref{alternate input}: Other ways of working with LilyPond.
+
+@end itemize
+@divEnd
+
+
+@divClass{hide}
+@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.
+@end menu
+@divEnd
+
+
+
+@node features
+@unnumberedsec Features
+
+@help{hoping to delegate this. Desired: an enthusiastic
+attempt to sway people towards trying lilypond. The warnings
+about writing music as text come in Crash Course, not here.}
+
+Maybe draw inspiration from
+@uref{http://lilypond.org/web/about/features} and
+@uref{http://lilypond.org/web/switch/tour} and
+@uref{http://lilypond.org/web/switch/advantages}
+
+
+
+@subheading Why switch to LilyPond?
+
+
+@subsubheading Excellent classical engraving
+
+@imageFloat{flat-design,png,right}
+
+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 @ref{essay}.
+
+
+@subsubheading 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!
+
+
+@subsubheading 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.
+
+
+@subsubheading 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.
+
+
+@subsubheading Mix music and text
+
+@imageFloat{lilypond-book,png,right}
+
+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.
+
+
+
+@subsubheading 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 @qq{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.
+
+
+@subsubheading 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.
+
+
+@subsubheading 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.
+
+
+
+@divClass{column-center-bottom}
+@subheading Where now?
+
+Still not convinced? Look at some neat @ref{examples}. If you've
+already decided to try LilyPond, first read about our
+@ref{text input}.
+@divEnd
+
+
+
+@node examples
+@unnumberedsec Examples
+
+Lilypond is a powerful and flexible tool for engraving tasks of
+all kinds. Please browse our gallery of examples and be inspired!
+
+@ignore
+Here is a passage from Franz Liszt's solo piano transcription
+of the Overture to Wagner's @emph{Tannhäuser}. The spacing
+in this example was all performed by Lilypond's formatting
+algorithms, without tweaks of any kind. It
+handles cross-staff beaming gracefully and puts the system brace
+perfectly around all three staves.
+
+@exampleImage{liszt-wagner}
+@end ignore
+
+@newsItem
+@subsubheading Classical Music
+
+This organ work by J.S. Bach is a fairly typical engraving project
+in Lilypond.
+
+@exampleImage{bach-bwv610}
+@newsEnd
+
+@newsItem
+@subsubheading Complex Notation
+
+This example from @emph{Goyescas} by Enrique Granados shows some
+of the more advanced features of typesetting, including kneed
+beams, cross-staff stems, and voice-follow lines.
+
+@exampleImage{granados}
+@newsEnd
+
+@newsItem
+@subsubheading Early Music
+
+Lilypond also supports various types of ancient notation, such
+as this passage of Gregorian chant.
+
+@exampleImage{ancient-headword}
+@newsEnd
+
+@newsItem
+@subsubheading Modern Music
+
+Contemporary composers find Lilypond well-suited to displaying
+unusual notation. Here is an excerpt from Trevor Baca's
+@emph{Cáry}, for unaccompanied bass flute.
+
+@exampleImage{cary}
+@newsEnd
+
+
+@newsItem
+@subsubheading Efficient, flexible creation of performance materials
+
+Various performance materials can be created from the same source
+code. This is an excerpt of @uref{http://nicolas.sceaux.free.fr/,
+Nicolas Sceaux's} engraving of Handel's @emph{Giulio Cesare}, in
+full score, piano-vocal reduction, and a violin part.
+
+@exampleImage{sesto-full}
+
+@exampleImage{sesto-piano}
+
+@exampleImage{sesto-violin}
+
+@newsEnd
+
+@newsItem
+@subsubheading 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.
+
+@exampleImage{tab-example}
+@newsEnd
+
+@newsItem
+@subsubheading Schenker Graphs
+
+Standard output can be modified heavily. Here someone has created
+an impressive Schenkerian analysis.
+
+@exampleImage{bach-schenker}
+@newsEnd
+
+@newsItem
+@subsubheading 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.
+
+@exampleImage{aucun-snippet}
+@newsEnd
+
+@newsItem
+@subsubheading Educational Applications
+
+Lilypond is perfectly suited for educational purposes as well.
+Here is an example of a simple counterpoint exercise.
+
+@exampleImage{theory}
+@newsEnd
+
+@newsItem
+@subsubheading 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.
+
+@exampleImage{chart}
+@newsEnd
+
+@newsItem
+@subsubheading 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.
+
+@exampleImage{orchestra}
+@newsEnd
+
+
+@divClass{column-center-bottom}
+@subheading Where now?
+
+Still not convinced? LilyPond is Free software, granting you
+@ref{freedom}. If you've already decided to try LilyPond, first
+read about our @ref{text input}.
+@divEnd
+
+
+@node freedom
+@unnumberedsec Freedom
+
+@divClass{column-center-top}
+@subheading Free Software
+
+@uref{http://www.gnu.org/, GNU} LilyPond is written and maintained
+by a community of enthusiasts. It is published under the
+@ref{GPL, GNU General Public License} and the @ref{FDL, GNU Free
+Documentation License}, giving everybody the freedom to fix,
+modify, and extend the program. Creating beautiful music should
+not require hundreds of dollars of software!
+@divEnd
+
+
+@c @divClass{column-left-top}
+@divClass{color2}
+@divClass{keep-bullets}
+@subheading What are the benefits to users?
+
+@itemize
+
+@item
+No cost: download and try it out! What do you have to lose?
+
+@item
+Sharing: if you like the program, give a copy to your friends,
+teachers, students, and colleagues!
+
+@item
+Source available: if you are curious about how LilyPond creates
+some notation, you can see exactly how it is done.
+
+@item
+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.
+
+@item
+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.
+
+
+@end itemize
+
+@divEnd
+@divEnd
+
+
+@c @divClass{column-right-top}
+@divClass{color3}
+@divClass{keep-bullets}
+@subheading Why do LilyPond developers @qq{give away} their work for free?
+
+Most of us view LilyPond development as a hobby or volunteer work.
+So this question is really asking @qq{why do people volunteer}?
+
+@itemize
+
+@item
+Fun: working towards a goal can be enjoyable, especially when you
+work as a team!
+
+@item
+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.
+
+@item
+@qq{Gift culture}: the Free Software (or @qq{Open Source})
+movement has created many great software projects, such as
+@uref{http://kernel.org/, GNU/Linux},
+@uref{http://www.getfirefox.com/, Mozilla Firefox}, and
+@uref{http://www.wesnoth.org/, Battle for Wesnoth}. Having
+benefitted from these projects, some developers want to @qq{give
+back} to the community.
+
+@item
+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.
+
+
+@end itemize
+
+@divEnd
+@divEnd
+
+
+@divClass{column-center-bottom}
+@subheading Where now?
+
+Still not convinced? Read our extensive essay about our engraving
+philosophy in @ref{background}. If you've already decided to try
+LilyPond, first read about our @ref{text input}.
+@divEnd
+
+
+@node background
+@unnumberedsec Background
+
+@divClass{column-center-top}
+@subheading 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 @ref{essay}.
+@divEnd
+
+@divClass{column-center-bottom}
+@subheading Where now?
+
+Still not convinced? Read about some of our users'
+@ref{productions} and sheet music. If you've already decided to
+try LilyPond, first read about our @ref{text input}.
+@divEnd
+
+
+@node productions
+@unnumberedsec Productions
+
+@divClass{column-left-top}
+@subheading Concerts
+
+Lilypond engravings have been used for performances around the world.
+Some highlights:
+
+@divClass{keep-bullets}
+@itemize
+
+@item
+@emph{Affaire Étrangère}, an opera by Valentin Villenave, with
+libretto by Lewis Trondheim, premiered February 1, 2009, by
+@uref{http://www.orchestre-montpellier.com/, L'Opéra Montpellier}.
+
+@item
+@uref{http://www.mercurybaroque.org/02/02109.aspx, Mercury Baroque}'s
+performance of Lully's @emph{Armide}, May 15-16, 2009, in Houston,
+Texas (engraving by @uref{http://nicolas.sceaux.free.fr/,
+Nicolas Sceaux}).
+
+@item
+Instrumental excerpts from Rameau's @emph{Hippolyte et Aricie} at
+St. James's Church in Manhattan, May 8, 2009, by Frederick Renz
+and his ensemble @uref{http://www.earlymusicny.org/, Early Music
+New York} (engraving by Nicolas Sceaux).
+
+@end itemize
+@divEnd
+
+@divEnd
+
+
+@divClass{column-right-top}
+@subheading Published sheet music
+
+@divClass{keep-bullets}
+@itemize
+
+@item
+@uref{http://www.mutopiaproject.org/index.html, Mutopia Project},
+over 1500 pieces of classical sheet music for free download, and
+the main showcase of LilyPond scores.
+
+@item
+@uref{http://www.adoromusicpub.com/, Adoro Music Publishing},
+high-quality scores of sacred music, available for immediate
+download or in traditional paper format.
+
+@item
+@uref{http://theshadylanepublishing.com/, The Shady Lane
+Publishing},
+a @qq{micro musical publishing house} whose goal is to promote a
+new form of musical economy closer to the musicians and music
+lovers.
+
+@end itemize
+
+@divEnd
+
+@divEnd
+
+
+@divClass{column-center-bottom}
+@subheading Where now?
+
+Still not convinced? Read some of our users' @ref{testimonials}.
+If you've already decided to try LilyPond, first read about our
+@ref{text input}.
+@divEnd
+
+
+@node testimonials
+@unnumberedsec Testimonials
+
+@divClass{testimonial-item}
+@imageFloat{carter-brey,jpg, right}
+@subsubheading @uref{http://nyphil.org/meet/orchestra/index.cfm?page=profile&personNum=7, Carter Brey}, Principal Cellist, New York Philharmonic
+
+@qq{... 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!}
+@divEnd
+
+
+@divClass{testimonial-item}
+@imageFloat{orm-finnendahl,jpg, left}
+@subsubheading @uref{http://icem-www.folkwang-hochschule.de/~finnendahl/, Orm Finnendahl}, professor of Composition, Musikhochschule Freiburg
+
+@qq{Although I don't know [LilyPond] very well yet, I'm
+@strong{*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!} @divEnd
+
+
+@divClass{testimonial-item}
+@imageFloat{darius-blasband,jpg, right}
+@subsubheading Darius Blasband, composer (Brussels, Belgium)
+
+@qq{[..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.}
+
+@divEnd
+
+
+@divClass{testimonial-item}
+@subsubheading Kieren MacMillan, composer (Toronto, Canada)
+
+@qq{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 @q{professional} publications I've compared
+it to (q.v., just about any Warner Bros. score, and even many of
+the most recent by @q{the old houses}). [..]}
+
+@qq{Beat that, Finale/Sibelius/Igor/whatever!!!}
+@divEnd
+
+
+@divClass{testimonial-item}
+@subsubheading Chris Cannam, lead programmer of the @uref{http://www.rosegardenmusic.com/, RoseGarden} project.
+
+@qq{Lilypond is obviously the zillion-ton gorilla [of great music
+typesetting].}
+@divEnd
+
+
+@divClass{testimonial-item}
+@subsubheading Chris Snyder, @uref{http://www.adoromusicpub.com/, Adoro Music Publishing}
+
+@qq{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.}
+
+@qq{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.}
+@divEnd
+
+
+@divClass{testimonial-item}
+@subsubheading David Bobroff, Bass Trombone, Iceland Symphony Orchestra
+
+@qq{I think Lilypond is great [..] The more I learn about LilyPond
+the more I like it!}
+@divEnd
+
+
+@divClass{testimonial-item}
+@subsubheading Vaylor Trucks, Electric guitar player (Yes, @uref{http://www.allmanbrothersband.com/modules.php?op=modload&name=userpage&file=content&page_id=12, related to})
+
+@qq{I am super impressed with LilyPond [..]}
+
+@qq{THIS IS THE BEST PROGRAM EVER!!!}
+
+@qq{Thank you all SO MUCH for your hard work and dedication!}
+@divEnd
+
+
+@divClass{testimonial-item}
+@subsubheading @uref{http://nicolas.sceaux.free.fr/, Nicolas Sceaux}, @uref{http://www.mutopiaproject.org/, Mutopia} contributor
+
+@qq{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.}
+@divEnd
+
+
+@divClass{testimonial-item}
+@subsubheading @uref{http://www.troff.org/whoswho.html#werner, Werner Lemberg}, Conductor at the Theatre in Koblenz, Germany and distinguished GNU Hacker.
+
+@qq{Anyway, LilyPond does an amazingly good job!}
+@divEnd
+
+
+@divClass{testimonial-item}
+@subsubheading Paul Davis, developer of @uref{http://jackaudio.org/, JACK} and @uref{http://www.ardour.org/, Ardour}.
+
+@qq{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.}
+@divEnd
+
+
+@divClass{column-center-bottom}
+@subheading Where now?
+
+Read about our @ref{text input}.
+@divEnd
+
+
+
+@node text input
+@unnumberedsec Text input
+
+@c TRANSLATORS: so far it's mostly from
+@c http://lilypond.org/web/switch/howto
+
+@subheading @qq{Compiling} Music
+
+@imageClickable{nereid-shot-small,png, (click to enlarge), nereid-shot,png, right}
+
+LilyPond is a @emph{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 @qq{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!
+
+@warning{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.}
+
+
+@subsubheading It's as simple as A B C
+
+Notes are encoded with letters and numbers. Special commands are
+entered with backslashes.
+
+@imageFloat{text-input-1-annotate,png,center}
+@imageFloat{text-input-1-output,png,center}
+
+Alterations are made with different names: add @code{-is} for
+sharp, and @code{-es} for flat (these are Dutch note names, other
+languages are available). LilyPond figures out where to put
+accidentals.
+
+@imageFloat{text-input-2-annotate,png,center}
+@imageFloat{text-input-2-output,png,center}
+
+
+@subsubheading Pop music
+
+Put chords and lyrics together to get a lead sheet:
+
+@imageFloat{text-input-pop-annotate,png,center}
+@imageFloat{text-input-pop-output,png,center}
+
+
+
+@subsubheading 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:
+
+@imageFloat{text-input-parts-both-annotate,png,center}
+
+
+This variable is then used in a single part (here transposed, with
+condensed multi rests):
+
+@imageFloat{text-input-parts-single-annotate,png,center}
+@imageFloat{text-input-parts-single-output,png,center}
+
+
+The same variable is used in the full score (here in concert
+pitch):
+
+@imageFloat{text-input-score-annotate,png,center}
+@imageFloat{text-input-score-output,png,center}
+
+
+@subsubheading 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 @ref{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.
+
+@help{any suggestions for a picture here?}
+
+
+@subsubheading 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 @ref{alternate input}.
+
+
+@divClass{column-center-bottom}
+@subheading Where now?
+
+You are now ready to @ref{download, Download LilyPond}. Still not
+convinced? Read about easier editing environments in
+@ref{alternate input}.
+
+@divEnd
+
+
+@node alternate input
+@unnumberedsec Alternate input
+
+@divClass{column-center-top}
+@subheading Graphical environment: Denemo
+
+@imageClickable{screenshot-denemo-small,png,
+ (click to enlarge),screenshot-denemo,png,right}
+
+@sourceimage{logo-linux,,,}
+@sourceimage{logo-windows,,,}
+
+@uref{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.
+
+@ignore
+Import: LilyPond, MIDI
+
+Export: Lilypond, MIDI, ABC, CSound Score File, PDF
+@end ignore
+
+@divEnd
+
+@divClass{column-center-top}
+@subheading Mixed environment: LilyPondTool
+
+@imageClickable{lilypondtool-2.12-screenshot-400wide,png,
+ (click to enlarge),lilypondtool-2.12-screenshot,png,right}
+
+@sourceimage{logo-linux,,,}
+@sourceimage{logo-freebsd,,,}
+@sourceimage{logo-macosx,,,}
+@sourceimage{logo-windows,,,}
+
+@uref{http://lilypondtool@/.organum@/.hu}
+
+Created as a plugin for the
+@uref{http://@/www@/.jedit@/.org@/,jEdit} 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.
+
+@divEnd
+
+@divClass{column-center-top}
+@subheading Text environment: Emacs and Vim
+
+@sourceimage{logo-linux,,,}
+@sourceimage{logo-freebsd,,,}
+@sourceimage{logo-macosx,,,}
+@sourceimage{logo-windows,,,}
+
+@uref{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 @q{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
+@command{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.
+
+@divEnd
+
+@divClass{column-center-top}
+@subheading Other
+
+@help insert text and a graphic(s)
+
+@subsubheading Mixed environment: Frescobaldi
+
+@imageClickable{frescobaldi-lilypond-editor-small,png,
+ (click to enlarge),frescobaldi-lilypond-editor,png,right}
+
+@sourceimage{logo-linux,,,}
+@sourceimage{logo-freebsd,,,}
+
+@uref{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.
+
+
+@subsubheading Text environment: TexShop
+
+@sourceimage{logo-macosx,,,}
+
+@uref{http://@/www@/.uoregon@/.edu/~koch/texshop}
+
+The
+@uref{http://@/www@/.uoregon@/.edu/~koch/texshop/index@/.html,TexShop}
+editor for MacOS@tie{}X can be extended to run LilyPond,
+@command{lilypond-book} and @command{convert-ly} from within the editor,
+using the extensions available at
+@uref{http://@/www@/.dimi@/.uniud@/.it/vitacolo/freesoftware@/.html#desktoppub}.
+
+
+@ignore
+TODO: ask somebody to sponsor/check these. -gp
+
+@subsubheading TextMate
+
+@sourceimage{logo-macosx,,,}
+
+There is a LilyPond bundle for TextMate. It may be installed by
+running:
+
+@example
+mkdir -p /Library/Application\ Support/TextMate/Bundles
+cd /Library/Application\ Support/TextMate/Bundles
+svn co http://macromates.com/svn/Bundles/trunk/Bundles/Lilypond.tmbundle/
+@end example
+@end ignore
+
+@subsubheading Mixed environment: LilyKDE
+
+@sourceimage{logo-linux,,,}
+@sourceimage{logo-freebsd,,,}
+
+@uref{http://lilykde.googlecode.com/}
+
+@uref{http://lilykde.googlecode.com/,LilyKDE} is a plugin for
+KDE's text editor @uref{http://kate-editor.org/,Kate}. It has a
+powerful Score Wizard to quickly setup a LilyPond document and an
+embedded PDF viewer.
+
+LilyKDE can use @uref{http://www.volny.cz/smilauer/rumor/,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.
+
+
+@help clean up this list, check links, etc.
+
+Other programs can export LilyPond code:
+
+@itemize
+@item
+@uref{http://www@/.volny@/.cz/smilauer/rumor/rumor@/.html,Rumor}, a realtime
+monophonic MIDI to LilyPond converter.
+@item
+@uref{http://nicolas@/.sceaux@/.free@/.fr/lilypond/lyqi@/.html,lyqi}, an
+Emacs major mode.
+@item
+@uref{http://@/www@/.nongnu@/.org/@/xml2ly/,xml2ly}, which imports
+@uref{http://@/www@/.musicxml@/.com/xml@/.html,MusicXML}
+@item
+@uref{http://@/noteedit@/.berlios@/.de,NoteEdit}
+which imports @uref{http://@/www@/.musicxml@/.com/xml@/.html,MusicXML}
+@item
+@uref{http://@/www@/.rosegardenmusic@/.com,Rosegarden},
+which imports MIDI
+@item
+@uref{http://@/common-lisp@/.net/project/fomus/,FOMUS},
+a LISP library to generate music notation
+@item
+@uref{http://vsr.informatik.tu-chemnitz.de/staff/jan/nted/nted.xhtml},
+has experimental export for LilyPond.
+@item
+@uref{http://www.tuxguitar.com.ar/}, can export to LilyPond.
+@item
+@uref{http://musescore.org} can also export to LilyPond.
+@end itemize
+@divEnd
+
+
+@divClass{column-center-bottom}
+@subheading Where now?
+
+You are now ready to @ref{download, Download LilyPond}.
+
+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 @ref{features}, @ref{examples}, or the
+@ref{freedom} that LilyPond provides, or read about users'
+@ref{productions} and @ref{testimonials}. In addition, our
+approach to the computational aesthetics of classical engraving is
+explained in our @ref{background}.
+
+
+@subheading Legalese
+
+@divClass{legal}
+All logos and product images are copyright and trademark
+acknowledged.
+
+@logoLegalLinux
+
+@logoLegalFreeBSD
+
+@logoLegalMacOSX
+
+@logoLegalWindows
+
+@divEnd
+
+@divEnd
+
+
+
+
--- /dev/null
+@c -*- coding: utf-8; mode: texinfo; -*-
+@ignore
+ Translation of GIT committish: FILL-IN-HEAD-COMMITTISH
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+@node manuals
+@unnumbered Manuals
+
+@divClass{heading-center}
+@heading Documentation for LilyPond @version
+
+@divEnd
+
+@c TODO: do we want these links to be in larger text / bold ? CSS.
+
+@c if you change this page, also change All.
+@divClass{column-center-top}
+@subheading Introduction
+
+@itemize
+
+@item @ref{text input}:
+LilyPond is a @strong{text-based} music engraver. If you are not
+familiar with this concept, please read this now!
+
+@item @ref{learning}:
+a @qq{must-read} gentle introduction to LilyPond.
+
+@item @ref{glossary}:
+@emph{(optional reading)}
+explains musical terms and gives translations for users unfamiliar
+with English musical terms.
+
+@item @ref{essay}:
+@emph{(optional reading)}
+background information about the engraving process and the
+aesthetics of 19th century music engraving.
+
+
+@end itemize
+
+@divEnd
+
+@divClass{column-left-top}
+@subheading Regular use
+
+@itemize
+
+@item @ref{notation}:
+the main portion of the documentation; provides detailed
+information about creating notation.
+
+@item @ref{usage}:
+discusses the actual programs and operating system-specific
+issues.
+
+@item @ref{snippets}:
+short tricks, tips, and examples.
+
+@end itemize
+
+@divEnd
+
+
+@divClass{column-right-top}
+@subheading Infrequent Use
+
+@itemize
+
+@item @ref{FAQ}:
+links to the answers of Frequently Asked Questions.
+
+@item @ref{changes}:
+updates since the last major version.
+
+@item @ref{extend}:
+programming fancy tweaks in LilyPond.
+
+@item @ref{internals}:
+information about LilyPond's internal structures, which is
+required for constructing tweaks.
+
+@end itemize
+
+@divEnd
+
+
+@divClass{column-center-bottom}
+@subheading Other material
+
+@itemize
+
+@item @ref{translated}:
+translation status for non-English readers.
+
+@item @ref{all}:
+quick links, downloadable manuals, and old manuals.
+
+@item @ref{development}:
+manuals for the unstable version.
+
+@item @ref{FDL}:
+these manuals are published under the GNU Free Documentation
+License.
+
+@end itemize
+
+@divEnd
+
+
+@divClass{hide}
+@menu
+* learning:: Learning.
+* glossary:: Glossary.
+* essay:: Essay.
+* notation:: Reference.
+* usage:: Usage.
+* snippets:: Snippets.
+* FAQ:: FAQ.
+* changes:: NEWS.
+* extend:: Programming.
+* internals:: Internals.
+* translated:: Translation.
+* all:: All manuals.
+* FDL:: Licence.
+@end menu
+
+@divEnd
+
+
+@c TRANSLATORS: most of the text in this file came from
+@c LM 1.1 About the documentation (before this section was
+@c removed in July 2009).
+
+@node learning
+@unnumberedsec Learning
+
+@divClass{column-left-top}
+@subheading 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 @strong{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.
+@divEnd
+
+@divClass{column-right-bottom}
+@subheading Read it
+
+@itemize
+
+@item @rlearningnamed{Top,Learning}:
+read this manual in the same format as this one.
+
+@end itemize
+
+@subheading All formats
+
+@divClass{keep-bullets}
+@itemize
+
+@item @uref{../learning/index.html, Learning (split HTML)}:
+the manual is split between many HTML pages.
+@emph{(small download for each page)}
+
+@item @uref{../learning-big-page.html, Learning (big HTML)}:
+read this manual as one huge HTML page.
+@emph{(large single download, around 10? Mb)}
+
+@item @uref{../learning.pdf, learning.pdf}:
+download as a PDF file.
+@emph{(large single download, 2.8 Mb)}
+
+@c TODO: should make links to info?
+@c @item @uref{../TODO, learning.info}:
+@c GNU info format for documentation. link broken.
+
+@end itemize
+@divEnd
+@divEnd
+
+
+@node glossary
+@unnumberedsec Glossary
+
+@divClass{column-left-top}
+@subheading 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.
+
+@divEnd
+
+@divClass{column-right-bottom}
+@subheading Read it
+
+@itemize
+
+@item @rglosnamed{Top,Music glossary}:
+read this manual in the same format as this one.
+
+@end itemize
+
+@subheading All formats
+
+@divClass{keep-bullets}
+@itemize
+
+@item @uref{../music-glossary/index.html, Glossary (split HTML)}:
+the manual is split between many HTML pages.
+@emph{(small download for each page)}
+
+@item @uref{../music-glossary-big-page.html, Glossay (big HTML)}:
+read this manual as one huge HTML page.
+@emph{(large single download, around 10? Mb)}
+
+@item @uref{../music-glossary.pdf, glossary.pdf}:
+download as a PDF file.
+@emph{(large single download, 2.8 Mb)}
+
+@c @item @uref{../TODO, glossary.info}:
+@c GNU info format for documentation. TODO, link broken.
+
+@end itemize
+@divEnd
+@divEnd
+
+
+@node essay
+@unnumberedsec Essay
+
+@divClass{column-left-top}
+@subheading 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.
+
+@warning{The detailed typographical examples are easier to analyze
+in the PDF version due to its higher resolution.}
+
+@divEnd
+
+@divClass{column-right-bottom}
+@subheading Read it
+
+@itemize
+
+@item @ressaynamed{Top,Essay}:
+read this manual in the same format as this one.
+
+@end itemize
+
+@subheading All formats
+
+@divClass{keep-bullets}
+@itemize
+
+@item @uref{../essay/index.html, Essay (split HTML)}:
+the manual is split between many HTML pages.
+@emph{(small download for each page)}
+
+@item @uref{../essay-big-page.html, Essay (big HTML)}:
+read this manual as one huge HTML page.
+@emph{(large single download, around ?? Mb)}
+
+@item @uref{../essay.pdf, essay.pdf}:
+download as a PDF file.
+@emph{(large single download, ?? Mb)}
+
+@c @item @uref{../TODO, essay.info}:
+@c GNU info format for documentation. TODO, link broken.
+
+@end itemize
+@divEnd
+@divEnd
+
+
+@node notation
+@unnumberedsec Notation
+
+@divClass{column-left-top}
+@subheading Notation reference
+
+This book explains all the LilyPond commands which produce
+notation.
+
+@warning{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.}
+
+@divEnd
+
+@divClass{column-right-bottom}
+@subheading Read it
+
+@itemize
+
+@item @rusernamed{Top,Notation}:
+read this manual in the same format as this one.
+
+@end itemize
+
+@subheading All formats
+
+@divClass{keep-bullets}
+@itemize
+
+@item @uref{../notation/index.html, Notation (split HTML)}:
+the manual is split between many HTML pages.
+@emph{(small download for each page)}
+
+@item @uref{../notation-big-page.html, Notation (big HTML)}:
+read this manual as one huge HTML page.
+@emph{(large single download, around 10? Mb)}
+
+@item @uref{../notation.pdf, notation.pdf}:
+download as a PDF file.
+@emph{(large single download, 2.8 Mb)}
+
+@c @item @uref{../TODO, notation.info}:
+@c GNU info format for documentation. TODO, link broken.
+
+@end itemize
+@divEnd
+@divEnd
+
+
+@node usage
+@unnumberedsec Usage
+
+@divClass{column-left-top}
+@subheading Usage manual
+
+This book explains how to execute the programs, how to integrate
+LilyPond notation with other programs, and suggests @qq{best
+practices} for efficient use. It is recommended reading before
+attempting any large projects.
+@divEnd
+
+@divClass{column-right-bottom}
+@subheading Read it
+
+@itemize
+
+@item @rprogramnamed{Top,Usage}:
+read this manual in the same format as this one.
+
+@end itemize
+
+@subheading All formats
+
+@divClass{keep-bullets}
+@itemize
+
+@item @uref{../usage/index.html, Usage (split HTML)}:
+the manual is split between many HTML pages.
+@emph{(small download for each page)}
+
+@item @uref{../usage-big-page.html, Usage (big HTML)}:
+read this manual as one huge HTML page.
+@emph{(large single download, around 10? Mb)}
+
+@item @uref{../usage.pdf, usage.pdf}:
+download as a PDF file.
+@emph{(large single download, 2.8 Mb)}
+
+@c @item @uref{../TODO, lilypond-usage.info}:
+@c GNU info format for documentation. TODO, link broken.
+
+@end itemize
+@divEnd
+@divEnd
+
+
+@node snippets
+@unnumberedsec Snippets
+
+@divClass{column-left-top}
+@subheading Snippets
+
+This shows a selected set of LilyPond snippets from the
+@uref{http://lsr@/.dsi@/.unimi@/.it,LilyPond Snippet Repository}
+(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 @file{input/new/} in the LilyPond
+source tree.
+
+The list of snippets for each subsection of the Notation are also
+linked from the @strong{See also} portion.
+@divEnd
+
+@divClass{column-right-bottom}
+@subheading Read it
+
+@itemize
+
+@item @rlsrnamed{Top,Snippets}:
+read this manual in the same format as this one.
+
+@end itemize
+
+@subheading All formats
+
+@divClass{keep-bullets}
+@itemize
+
+@item @uref{../snippets/index.html, Snippets (split HTML)}:
+the manual is split between many HTML pages.
+@emph{(small download for each page)}
+
+@item @uref{../snippets-big-page.html, Snippets (big HTML)}:
+read this manual as one huge HTML page.
+@emph{(large single download, around 10? Mb)}
+
+@item @uref{../snippets.pdf, snippets.pdf}:
+download as a PDF file.
+@emph{(large single download, 2.8 Mb)}
+
+@c @item @uref{../TODO, snippets.info}:
+@c GNU info format for documentation. TODO, link broken.
+
+@end itemize
+@divEnd
+@divEnd
+
+
+@node FAQ
+@unnumberedsec FAQ
+
+@divClass{column-center-top}
+@subheading Introductory questions
+
+@subsubheading Where are the graphical canvas, menus, and toolbars?
+
+LilyPond requires you to write music as text. Please read about
+our @ref{text input}.
+
+
+@subsubheading There's a lot of documentation! Do I need to read it?
+
+You need to read the @ref{learning, Learning manual}. As for the
+rest of documentation, you only need to read the sections which
+discuss the notation that you wish to create.
+
+
+@subsubheading 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 @ref{introduction}.
+
+@divEnd
+
+@divClass{column-center-bottom}
+@subheading Usage questions
+
+@subsubheading Something isn't working! How do I fix it?
+
+This is explained in @rprogram{Troubleshooting}.
+
+
+@subsubheading Why do you change the syntax?
+
+This is explained in @rprogram{Why does the syntax change?}.
+
+@divEnd
+
+
+@node changes
+@unnumberedsec Changes
+
+@divClass{column-left-top}
+@subheading Changes
+
+This is a summary of important changes and new features in
+LilyPond since the previous stable version.
+
+@divEnd
+
+@divClass{column-right-bottom}
+@subheading Read it
+
+@itemize
+
+@item @rchangesnamed{Top,Changes}:
+read this manual in the same format as this one.
+
+@end itemize
+
+@subheading All formats
+
+@divClass{keep-bullets}
+@itemize
+
+@item @uref{../changes/index.html, Changes (split HTML)}:
+the manual is split between many HTML pages.
+@emph{(small download for each page)}
+
+@item @uref{../changes-big-page.html, Changes (big HTML)}:
+read this manual as one huge HTML page.
+@emph{(large single download, around 10? Mb)}
+
+@item @uref{../changes.pdf, changes.pdf}:
+download as a PDF file.
+@emph{(small single download, 0.5 ?? Mb)}
+
+@c @item @uref{../TODO, changes.info}:
+@c GNU info format for documentation. TODO, link broken.
+
+@end itemize
+@divEnd
+@divEnd
+
+
+@node extend
+@unnumberedsec Extend
+
+@divClass{column-left-top}
+@subheading Extend LilyPond
+
+This manual explains how to write extensions to LilyPond.
+
+@divEnd
+
+@divClass{column-right-bottom}
+@subheading Read it
+
+@itemize
+
+@item @rextendnamed{Top,Extend}:
+read this manual in the same format as this one.
+
+@end itemize
+
+@subheading All formats
+
+@divClass{keep-bullets}
+@itemize
+
+@item @uref{../extending/index.html, Extend (split HTML)}:
+the manual is split between many HTML pages.
+@emph{(small download for each page)}
+
+@item @uref{../extending-big-page.html, Extend (big HTML)}:
+read this manual as one huge HTML page.
+@emph{(large single download, around 10? Mb)}
+
+@item @uref{../extending.pdf, extending.pdf}:
+download as a PDF file.
+@emph{(large single download, 2.8 Mb)}
+
+@c @item @uref{../TODO, extending.info}:
+@c GNU info format for documentation. TODO, link broken.
+
+@end itemize
+@divEnd
+@divEnd
+
+
+@node internals
+@unnumberedsec Internals
+
+@divClass{column-left-top}
+@subheading 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 @b{See also} subsection, which refers to the
+generated documentation. In the HTML document, these subsections
+have clickable links.
+
+@divEnd
+
+@divClass{column-right-bottom}
+@subheading Read it
+
+@itemize
+
+@item @rinternalsnamed{Top,Internals}:
+read this manual in the same format as this one.
+
+@end itemize
+
+@subheading All formats
+
+@divClass{keep-bullets}
+@itemize
+
+@item @uref{../internals/index.html, Internals (split HTML)}:
+the manual is split between many HTML pages.
+@emph{(small download for each page)}
+
+@item @uref{../internals-big-page.html, Internals (big HTML)}:
+read this manual as one huge HTML page.
+@emph{(large single download, around 10? Mb)}
+
+@item @uref{../internals.pdf, internals.pdf}:
+download as a PDF file.
+@emph{(large single download, 2.8 Mb)}
+
+@c @item @uref{../TODO, internals.info}:
+@c GNU info format for documentation. TODO, link broken.
+
+@end itemize
+@divEnd
+@divEnd
+
+
+
+@node translated
+@unnumberedsec Translated
+
+@divClass{column-center-bottom}
+@subheading Translation status
+
+TODO: clean up / prettify
+
+@uref{../translations.html}.
+
+@divEnd
+
+
+@node all
+@unnumberedsec All
+
+@divClass{heading-center}
+@heading Documentation quick links
+
+Links to other formats of these manuals can be found in
+@ref{manuals}.
+
+@divEnd
+
+@c this should match the (main) manual page.
+@divClass{column-center-top}
+@subheading Introduction
+
+@itemize
+
+@item @rlearningnamed{Top,Learning}:
+a @qq{must-read} gentle introduction to LilyPond.
+
+@item @rglosnamed{Top,Glossary}:
+@emph{(optional reading)}
+explains musical terms and gives translations for users unfamiliar
+with English musical terms.
+
+@item @ressaynamed{Top,Essay}:
+@emph{(optional reading)}
+background information about the engraving process and the
+aesthetics of 19th century music engraving.
+
+@end itemize
+
+@divEnd
+
+@divClass{column-left-top}
+@subheading Regular use
+
+@itemize
+
+@item @rusernamed{Top,Notation}:
+the main portion of the documentation; provides detailed
+information about creating notation.
+
+@item @rprogramnamed{Top,Usage}:
+discusses the actual programs and operation system-specific
+issues.
+
+@item @rlsrnamed{Top,Snippets}:
+short tricks, tips, and examples.
+
+@end itemize
+
+@divEnd
+
+
+@divClass{column-right-top}
+@subheading Infrequent Use
+
+@itemize
+
+@item @ref{FAQ}:
+links to answers of Frequently Asked Questions.
+
+@item @rchangesnamed{Top,Changes}:
+updates since the last major version.
+
+@item @rextendnamed{Top,Extend}:
+programming fancy tweaks in LilyPond.
+
+@item @rinternalsnamed{Top,Internals}:
+information about LilyPond's internal structures, which is
+required for constructing tweaks.
+
+@end itemize
+
+@divEnd
+
+
+@divClass{column-center-bottom}
+@subheading Downloadable versions
+
+@help{compare tarball vs. zip size, ask about windows users
+dealing with tarballs (both gz and bz2), etc.}
+
+@help{on second thought, wait until the new doc build. write an
+apology here for no tarballs}
+
+@divClass{keep-bullets}
+@itemize
+
+@item html-split zip
+
+@item html-big zip
+
+@item pdf zip
+
+@item info zip maybe?!?!
+
+@end itemize
+
+@divEnd
+
+@subheading Previous stable versions
+
+@divClass{keep-bullets}
+@itemize
+
+@item @uref{http://lilypond.org/doc/v2.12/Documentation/,
+LilyPond 2.12 Documentation}
+
+@item @uref{http://lilypond.org/doc/v2.10/Documentation/,
+LilyPond 2.10 Documentation}
+
+@item @uref{http://lilypond.org/doc/v2.8/Documentation/,
+LilyPond 2.8 Documentation}
+
+@help anybody want to write this stuff?
+
+@end itemize
+
+@divEnd
+@divEnd
+
+
+@node FDL
+@unnumberedsec FDL
+
+@divClass{column-center-top}
+@subheading 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 @ref{freedom}.
+
+@divEnd
+
+@divClass{column-center-bottom}
+@subheading GNU Free Documentation License 1.1
+
+@include fdl.itexi
+
+@divEnd
+
+
--- /dev/null
+@c -*- coding: utf-8; mode: texinfo; -*-
+@c This file is part of lilypond-web.texi and community.itexi
+
+@c when you add a new item, consider moving the lowest item(s)
+@c into news-old.itexi.
+
+@newsItem
+@subsubheading New Website! @emph{October 3, 2009}
+
+As you can see, we have a new website design. Many thanks to
+texi2html and CSS for being so flexible!
+
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond Report #16. @emph{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 @uref{http://news.lilynet.net/The-LilyPond-Report-16, issue 16}
+now!
+
+@newsEnd
+
+
--- /dev/null
+@c -*- coding: utf-8; mode: texinfo; -*-
+
+@ignore
+
+(I'd rather have the below in the CG. -gp)
+NOTE:
+
+ * avoid "HERE" as name for links, use descriptive link names like
+ @uref{,Download LilyPond 2.5.16}
+
+ * avoid putting links in running text. They make text harder to read.
+ Preferably: (@uref{,...}, etc. )
+
+ * use a descriptive title in @subsubheading
+
+ * writing date in "Month DD, YYYY" format is required for
+ generating the RSS feed; in case the message (and thus the date)
+ is not in English, you must write a well-formed date in English
+ like above in a comment between the closing brace of @emph and the
+ following line
+ (see "Japanese translation" below for an example).
+
+ * Split news items in small chunks. It's OK to have more than 1 item
+ on one day.
+
+
+TODO
+
+ * add macro for long Google issues list URL
+@end ignore
+
+
+@newsItem
+@subsubheading New Website! @emph{October 3, 2009}
+
+As you can see, we have a new website design. Many thanks to
+texi2html and CSS for being so flexible!
+
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond Report #16. @emph{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 @uref{http://news.lilynet.net/The-LilyPond-Report-16, issue 16}
+now!
+
+@newsEnd
+
+
+
+@newsItem
+@subsubheading Hungarian translation! @emph{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!
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond Report #15. @emph{May 18, 2009}
+
+The @emph{LilyPond Report} is a short, informal opinion column
+about the LilyPond project: its team, its world, its community.
+Read it @uref{http://news.lilynet.net/The-LilyPond-Report-15,
+here}!
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.13.3. @emph{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.@*
+@ref{changes},
+@ref{development}.
+@newsEnd
+
+
+@newsItem
+@subsubheading A LilyPond weboldala magyarul. @emph{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 @code{harmathdenes AT gmail.com} címre!
+<p align="right">Harmath Dénes, a LilyPond honosítási projekt
+vezetője
+@newsEnd
+
+
+@newsItem
+@subsubheading The LilyPond Report #15. @emph{May 18, 2009}
+
+The @emph{LilyPond Report} is a short, informal opinion column about the LilyPond project:
+its team, its world, its community.
+Follow @uref{http://news.lilynet.net/The-LilyPond-Report-15,this link}
+to read the full issue...
+@newsEnd
+
+
+@newsItem
+@subsubheading The LilyPond Report #14. @emph{April 13, 2009}
+
+The @emph{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 @uref{http://news.lilynet.net/The-LilyPond-Report-14,this link} to read the full issue...
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.12.2 and 2.13.0 — @emph{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.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.12.0 @qq{Rune} — @emph{December 27, 2008}
+
+A new stable release of LilyPond is available.
+@*
+@uref{announce-v2.12,Announcement},
+@ref{changes},
+@ref{download}.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.65 — Release Candidate. @emph{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.@*
+@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_65&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{changes},
+@ref{old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.64. @emph{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.
+@*
+@ref{changes},
+@ref{old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.63. @emph{October 29, 2008}
+
+LilyPond 2.11.63 is available. This release has lots of updates to the
+documentation and translations.
+@ref{old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.62 – Release Candidate. @emph{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 @code{\tempo} command, this release has lot of updates
+to Spanish and German documentation translations, and the
+stylesheet for HTML documentation has been improved.
+@*
+@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_62&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.61 available. @emph{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.
+@*
+@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_61&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{changes},
+@ref{old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.60 available. @emph{September 25, 2008}
+
+LilyPond 2.11.60 has been released. A new style of double repeat
+bar line has been added, and @code{printallheaders} variable in
+score block has been renamed to @code{print-all-headers}.
+@ref{old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.59 available. @emph{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.
+@ref{old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.58 available. @emph{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.
+@*
+@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_58&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{changes},
+@ref{old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.57 available. @emph{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.
+@*
+@ref{changes},
+@ref{old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.56 available. @emph{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 @code{\pointAndClickOn},
+@code{\pointAndClickOff} have also been added.
+@*
+@ref{changes},
+@ref{old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.55 available. @emph{August 6, 2008}
+
+LilyPond 2.11.55 is out. This release fixes several bugs, and for octavation brackets
+@code{set-octavation} has been replaced by a more user-friendly command, @code{\ottava}.
+@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_55&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.54 available. @emph{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 @code{short-indent}
+so that short instrument names are no longer indented in the margin.
+@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_54&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.53 available. @emph{July 23, 2008}
+
+LilyPond 2.11.53 is out. This release fixes a lot of bugs.
+@*
+@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_53&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.52 available. @emph{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. @ref{changes},
+@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_52&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.51 available. @emph{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 @code{fret-diagram-details} property.
+@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_51&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.50 available. @emph{July 2, 2008}
+
+Release 2.11.50 adds support for metronome marks with text, and
+backslashed numbers for figured bass, contributed by
+Reinhold Kainhofer.
+@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_50&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading The LilyPond Report #13. @emph{June 23, 2008}
+
+This short, informal, weekly opinion column is about the LilyPond project: its team, its world, its community.
+Follow @uref{http://valentin.villenave.info/The-LilyPond-Report-13,this link} to read the full issue...
+@newsEnd
+
+
+@newsItem
+@subsubheading The LilyPond Report #12. @emph{June 16, 2008}
+
+This short, informal, weekly opinion column is about the LilyPond project: its team, its world, its community.
+Follow @uref{http://valentin.villenave.info/The-LilyPond-Report-12,this link} to read the full issue...
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.49 released. @emph{June 12, 2008}
+
+LilyPond 2.11.49 is out. It fixes a number of bugs, including bugs in beams formatting.
+@*
+@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_49&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.48 released. @emph{June 9, 2008}
+
+LilyPond 2.11.48 is out. This release fixes a few bugs, and
+@code{\compressMusic} has been renamed
+to @code{\scaleDurations}.
+@*
+@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_48&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading The LilyPond Report #11. @emph{June 9, 2008}
+
+This short, informal, weekly opinion column is about the LilyPond project: its team, its world, its community.
+Follow @uref{http://valentin.villenave.info/The-LilyPond-Report-11,this link} to read the full issue...
+@newsEnd
+
+
+@newsItem
+@subsubheading The LilyPond Report #10. @emph{June 2, 2008}
+
+Welcome to this special tenth issue of the @emph{LilyPond Report}, entirely dedicated to Algorithmic Composition systems.@*
+Follow @uref{http://valentin.villenave.info/The-LilyPond-Report-10,this link} to read the full issue...
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.47 released. @emph{May 28, 2008}
+
+LilyPond now allows all text context properties to be markups,
+except in @code{\lyricmode}. This release also fixes
+regression tests maintenance for developers.
+@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_47&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.46 available. @emph{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.
+@ref{changes},
+@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_46&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading RSS feed - @emph{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.
+@uref{http://lilypond.org/web/lilypond-rss-feed.xml,Feed URL}.
+The info mailing list (see @ref{contact}) is still used to
+announce releases and special events.
+@newsEnd
+
+
+@newsItem
+@subsubheading The LilyPond Report #9. @emph{May 05, 2008}
+
+Welcome to this ninth issue of the @emph{LilyPond Report}!@*
+This short, informal, weekly opinion column is about the LilyPond project: its team, its world, its community.
+Follow @uref{http://valentin.villenave.info/The-LilyPond-Report-9,this link} to read the full issue...
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.45 available. @emph{April 26, 2008}
+
+Release 2.11.45 fixes a couple of bugs in the formatting
+engine. @code{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.
+@ref{changes},
+@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_45&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.44 available. @emph{April 14, 2008}
+
+Release 2.11.44 is available. Support for figured bass and chord
+names has been added to the MusicXML
+converter. @uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_44&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading lilypond.org日本語訳 (lilypond.org Japanese translation). @emph{2008年4月8日 (April 4, 2008)}
+
+Lilypond.orgのいくつかのページの日本語訳が出来ました。
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.43 available. @emph{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. @uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_43&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.42 available. @emph{March 9, 2008}
+
+Release 2.11.42 is out. It fixes some formatting and spacing
+bugs. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_42&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading Comparison of music engraving with Finale and LilyPond. @emph{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.
+@uref{http://www.musicbyandrew.ca/finale-lilypond-1.html,Read
+the articles}.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.41 available. @emph{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. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_41&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.37 available. @emph{January 3, 2008}
+
+Release 2.11.37 is available. It has a few bugfixes, and
+documentation changes. (@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.36 available. @emph{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. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_36&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes}, @ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.33 and 2.10.33 available. @emph{September 20, 2007}
+
+Release 2.11.33 is now available.
+(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_33&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
+2.10}, @uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_33&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
+2.11}, @ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.32 available. @emph{September 2, 2007}
+
+Release 2.11.32 is now available.
+(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_32&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes}, @ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.31 available. @emph{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.
+(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_31&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes}, @ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.30 available. @emph{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. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_30&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes}, @ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.10.29 and 2.11.29 available. @emph{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.
+(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_29&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
+2.10}, @uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_29&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
+2.11}, @ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.28 for FreeBSD x86_64. @emph{August 10, 2007}
+
+Release 2.11.28 is now available as a binary installer for
+FreeBSD x86_64. Download
+@uref{http://lilypond.org/download/binaries/freebsd-64/lilypond-2.11.28-1.freebsd-64.sh,the installer} and
+do @emph{sh lilypond-2.11.28-1.freebsd-64.sh} in a command window.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.28 available - @emph{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.
+(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_28&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
+2.11}, @ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.26 available - @emph{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!
+(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_26&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
+2.11}, @ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.10.25 and 2.11.25 available - @emph{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!
+(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_25&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
+2.11}, @uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_25&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
+2.10}, @ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.10.23 and 2.11.23 available - @emph{May 1, 2007}
+This has lots of bugfixes. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_23&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
+2.11}, @uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_23&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
+2.10}, @ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading Übersetzung der Dokumentation - @emph{10. April 2007}
+Die Kapitel 1-5 (der Abschnitt für Anfänger) des
+LilyPond-Benutzerhandbuchs
+sind auf deutsch übersetzt — sie sind erhältlich für
+die @ref{changes}
+online und @ref{old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.22 available - @emph{April 10, 2007}
+This release has updates of the dot collision code. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_22&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
+}, @ref{changes}, @ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.21 available - @emph{March 24, 2007}
+This release has some documentation updates.
+(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_21&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
+}, @ref{changes}, @ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading Traduction de la documentation en français - @emph{25 février 2007}
+Les chapitres 1 à 4 et 6 du manuel de l'utilisateur sont
+désormais traduits, et disponibles en ligne — @uref{@@DOC@@v2.10/Documentation/user/lilypond/index.fr.html,version
+2.10}, @uref{@@DOC@@v2.11/Documentation/user/lilypond/index.fr.html,version
+2.11}. Les traductions sont également incluses dans la @uref{install,documentation téléchargeable}.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.10.20 and 2.11.20 available - @emph{February 25, 2007}
+This release fixes many bugs.
+(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_20&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
+2.11},
+@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_20&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
+2.10}, @ref{changes}, @ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.10.19 and 2.11.19 available - @emph{February 18, 2007}
+This release fixes many bugs.
+(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_19&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
+2.11},
+@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_19&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
+2.10}, @ref{changes}, @ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.18 available - @emph{February 12, 2007}
+This release fixes still more bugs, and included
+singing support through festival contributed by Milan Zamazal. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_18&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
+2.11}, @ref{changes}, @ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.17 available - @emph{February 9, 2007}
+This release fixes still more bugs.
+(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_17&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
+2.11}, @ref{changes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.10.16 and 2.11.16 available - @emph{February 4, 2007}
+This release fixes many bugs.
+(@uref{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.11},
+@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_16&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
+2.10},
+@ref{changes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.10.15 and 2.11.15 available - @emph{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. (@uref{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.11},
+@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_15&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes
+2.10},
+@ref{changes}, @ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.10.14 and 2.11.14 available - @emph{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.
+(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_14&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{changes}, @ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.10.13 and 2.11.13 available - @emph{January 17, 2007}
+This release fixes a few minor but irritating bugs. In addition, the
+2.11 release has updates of the tutorial.
+(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_13&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{changes}, @ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.12 available - @emph{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.
+(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_12&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{changes}, @ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.10.12 available - @emph{January 17, 2007}
+This release mirrors 2.11.12. Notably, it has the same memory
+usage improvements. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_12&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{changes}, @ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.10.11 available - @emph{January 12, 2007}
+This release mostly has the same fixes as 2.11.11. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_11&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{changes}, @ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.11 available - @emph{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. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_11&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{changes}, @ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.10 available - @emph{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. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_10&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{changes}, @ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.10.10 available - @emph{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 (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_10&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{changes}, @ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.9 and 2.10.9 available - @emph{January 3, 2007}
+This release has a couple of bugfixes, and —in 2.11.9&mdash
+further improvements in the regression test suite (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_9&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{changes}, @ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.8 and 2.10.8 available - @emph{January 3, 2007}
+New! Improved! With even more bugfixes! (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_8&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{changes}, @ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading @code{lilypond.org} auf deutsch - @emph{31. Dezember 2006}
+Die LilyPond-Webseiten sind jetzt auch auf deutsch übersetzt!
+@newsEnd
+
+
+@newsItem
+@subsubheading @code{lilypond.org} en español - @emph{December 29, 2006}
+¡Ya está disponible la versión en español del sitio web de LilyPond!
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.7 and 2.10.7 available - @emph{January 1, 2007}
+New! Improved! With even more bugfixes! (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_7&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{changes}, @ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.6 available - @emph{December 30, 2006}
+This release supports arbitrary fractional alterations, allowing
+music with different microtonal conventions to be typeset.
+(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_6&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{changes}, @ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.10.6 available - @emph{December 30, 2006}
+New! Improved! With even more bugfixes!
+(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_6&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{changes}, @ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.5 available - @emph{December 24, 2006}
+These releases complete the translation infrastructure for
+Documentation.
+(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_5&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{changes}, @ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.10.5 available - @emph{December 24, 2006}
+New! Improved! With even more bugfixes!
+(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_5&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{changes}, @ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.4 available - @emph{December 21, 2006}
+The vertical spacing improvements that were introduced in 2.11.0 now work
+within a system as well as between systems. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_4&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{changes}, @ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.3 available - @emph{December 19, 2006}
+This release has @uref{http://lilypond.org/doc/v2.11/compare-v2.10.3/index.html,graphical
+test results} and several website build improvements. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_3&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{changes}, @ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.10.3 available - @emph{December 19, 2006}
+This release fixes several bugs.
+(@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_3&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LinuxPPC binaries available! - @emph{December 19, 2006}
+From now on, our GUB binary builds include support for Linux/PPC. (@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading Traduction du tutoriel en français. @emph{December 13, 2006}
+Fruit du travail d'une équipe de traducteurs, le tutoriel en
+français est maintenant disponible en ligne. @uref{@@DOC@@v2.10/Documentation/user/lilypond/Tutorial.fr.html,Version
+2.10}, @uref{@@DOC@@v2.11/Documentation/user/lilypond/Tutorial.fr.html,Version
+2.11}.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.2 available - @emph{December 12, 2006}
+This release supports glissandi and harmonics in tablature. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_2&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{changes}, @ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.10.2 available - @emph{December 12, 2006}
+A new stable release of LilyPond is available. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_2&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.1 available - @emph{December 4, 2006}
+This release has improved support for horizontal spacing. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_11_1&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{changes}, @ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.10.1 available - @emph{December 3, 2006}
+A new stable release of LilyPond is available. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_10_1&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.11.0 available - @emph{November 27, 2006}
+This release has improved support for vertical spacing. (@ref{changes}, @ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.10.0 available - @emph{November 11, 2006}
+A new stable release of LilyPond is available. (@uref{announce-v2.10.html,Announcement}, @ref{changes}, @ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading GIT repository online - @emph{November 11, 2006}
+LilyPond development has moved over its source code to @uref{http://git.or.cz,GIT}, the fast version control
+system. Check out our repository at @uref{http://git.sv.gnu.org/gitweb/?p=lilypond.git;a=summary,gnu.org}.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.9.29 available - @emph{November 5, 2006}
+This release has many more bugfixes. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_9_29&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.9.28 available - @emph{November 3, 2006}
+This release has many more bugfixes. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_9_28&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.9.27 available - @emph{October 28, 2006}
+This release has a new @code{FretBoards} context, and some further
+bugfixes. (@ref{changes}, @uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_9_27&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading Music streams thesis available - @emph{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
+(@ref{publications}).
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.9.26 available - @emph{October 20, 2006}
+This release has further bugfixes. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_9_26&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.9.25 available - @emph{October 18, 2006}
+This release has more bugfixes; from now on, binaries are also
+available for x86/64. (@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed_2_9_25&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.9.24 available - @emph{October 15, 2006}
+This release has support for right hand guitar fingerings, and offers
+some bugfixes. (@ref{changes},
+@uref{http://code.google.com/p/lilypond/issues/list?can=1&q=fixed2924&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary,Bugfixes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.9.23 available - @emph{October 12, 2006}
+This release cuts fragments of EPS directly from your finished score,
+and makes it easier to insert ties into lyrics. (@ref{changes}, @ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.9.22 available - @emph{October 9, 2006}
+Test this release candidate for LilyPond 2.10! (@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.9.21 available - @emph{October 4, 2006}
+Test this release candidate for LilyPond 2.10! (@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.9.20 available - @emph{October 3, 2006}
+Test this release candidate for LilyPond 2.10! (@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.9.17 available - @emph{September 2, 2006}
+This release fixes many bugs. Among others, MacOS X QuickTime now
+honors tempo changes are in the MIDI output. (@ref{changes}, @ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.9.16 available - @emph{August 25, 2006}
+In this release, chords may be partially tied and lyric extenders have
+tunable padding. Moreover, many bugs were fixed
+(@ref{changes}, @ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.9.15 available - @emph{August 20, 2006}
+This releases fixes many bugs in the 2.9.14 release. (@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.8.6 available - @emph{August 8, 2006}
+This release contains a few minor bugfixes; the source tarball is also
+available. (@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.9.14 available - @emph{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. (@ref{changes}, @ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.9.13 available - @emph{July 23, 2006}
+This release supports doits and falls, and more tuning options for
+grace note spacing and tuplet brackets. (@ref{changes}, @ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.9.12 available - @emph{July 18, 2006}
+This release supports pdftex for lilypond-book, and uses PdfTeX for
+generating manuals, so page numbers and references are now clickable.
+(@ref{changes}, @ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.9.11 available - @emph{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. (@ref{changes}, @ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.9.10 available - @emph{June 15, 2006}
+This releases fixes a couple of bugs in 2.9.9.
+(@ref{changes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.9.9 available - @emph{June 15, 2006}
+This releases fixes many bugs in 2.9.8 and earlier.
+(@ref{changes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.9.8 available - @emph{June 6, 2006}
+2.9.8 has support for different spacing sections within a single
+score, and better infrastructure for automated regression testing.
+(@ref{changes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.8.4 available - @emph{June 4, 2006}
+2.8.4 fixes some minor bugs, and includes a backport of the
+infrastructure for automated regression testing.
+(@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading First test results available - @emph{June 4, 2006}
+After a week of frantic tweaking, the first automated testing results
+are available. You can now see @uref{http://lilypond.org/doc/v2.9/compare-v2.8.4/index.html,in full
+glory} what features are broken in the development release
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.9.7 available - @emph{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
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.9.6 available - @emph{May 24, 2006}
+This
+release has new features in beam formatting: beams may now be put on
+single stems, and obey the @code{beatGrouping} property. MusicXML
+converter. (@ref{changes}, @ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading New essay pages! - @emph{May 22, 2006}
+The @emph{Automated Engraving} essay has been updated with material
+from the @uref{http://fisl.softwarelivre.org,FISL} talk, with
+pages on @uref{about/automated-engraving/problem-statement,modeling
+notation} and @uref{about/automated-engraving/scoring-esthetics,algorithms for
+esthetics}. Happy reading!
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.9.5 available - @emph{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.
+(@ref{changes}, @ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.9.4 available - @emph{May 12, 2006}
+This release has support for feathered beaming, and note head styles in
+the markup @code{\note} command. In addition, it has a lot of updates
+of the manual and a clean up of the spring spacer.
+(@ref{changes}, @ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.8.2 available - @emph{May 12, 2006}
+This release has fixes for minor bugs and compilation issues.
+(@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.9.3 is out! - @emph{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. (@ref{changes}, @ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading FISL7.0 slides available - @emph{April 22, 2006}
+The slides for Han-Wen's talk at
+@uref{http://fisl.softwarelivre.org,FISL 7} are now online.
+(@ref{publications})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.8.1 is out! - @emph{April 3, 2006}
+Important bugfixes include CJK font handling and a Darwin/x86 port.
+(@ref{changes}, @ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.9.1 is out! - @emph{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.
+(@ref{changes}, @ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond on MacOS X/Intel - @emph{March 31, 2006}
+LilyPond now also runs on Intel based macs, offering a 400%
+speedup over the emulated PowerPC binaries. (@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.8.0 is out! - @emph{March 22, 2006}
+Version 2.8 is here! Read the @uref{announce-v2.8.html,release
+announcement}. (@ref{changes}, @ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.39 is out - @emph{March 17, 2006}
+This release has even more bug fixes. Please test before 2.8 is
+released. (@ref{changes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.38 is out - @emph{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.
+(@ref{changes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.37 is out - @emph{March 4, 2006}
+This release has more bug fixes. Please help us by testing it!
+(@ref{changes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.36 is out - @emph{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. (@ref{changes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.35 is out - @emph{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 @strong{very} welcome. By
+definition a bug is release critical if it wasn't present in version
+2.6. (@ref{changes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.34 is out - @emph{February 16, 2006}
+This release has a bunch of bugfixes, and new features. Newly created
+contexts may also be named with @code{\new Voice =
+"alto"}. Thicknesses of tie and slurs may be tuned separately for
+the endings and the middle
+part. (@ref{changes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.33 is out - @emph{February 10, 2006}
+Items directly connected with a music input element may be
+parenthesized, for example,
+@verbatim
+{
+ c4 -\parenthesize -.
+ <d \parenthesize fis a>
+}
+@end verbatim
+
+This feature was sponsored by Ramana Kumar. (@ref{changes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.32 is out - @emph{February 7, 2006}
+This release contains some syntax changes: words inside the \paper and
+\layout block are henceforth written with dashes, for instance:
+
+@verbatim
+{
+ \layout {
+ ragged-right = ##t
+ }
+}
+@end verbatim
+
+Furthermore, in this release, we have dropped some legacy code from
+our library. Now, lily uses standard C++ strings and the STL
+vector. (@ref{changes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.31 is out - @emph{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.
+(@ref{changes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.30 is out - @emph{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. (@ref{changes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.29 is out - @emph{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). (@ref{changes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.28 is out - @emph{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. (@ref{changes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.27, release 4 - @emph{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! (@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.27, release 3 - @emph{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 @strong{FreeBSD} as well! Jump
+to the @ref{old downloads} get them!
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.27 binaries are out - @emph{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
+@uref{http://lilypond.org/download/binaries/linux-x86/lilypond-2.7.27-1.linux.sh,
+Linux/x86},
+@uref{http://lilypond.org/download/binaries/MacOS/lilypond-2.7.27-2.zip,
+MacOS X} and
+@uref{http://lilypond.org/download/binaries/mingw/lilypond-2.7.27-2.exe,
+Windows}.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.27 is out - @emph{January 7, 2006}
+This release allows you to switch staff lines on and off individually
+(feature sponsored by Andrea
+Valle). (@ref{changes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading Linux Journal article - @emph{January 2006}
+Linux Journal publishes an article on
+@uref{http://www.linuxjournal.com/article/8364,@emph{Make
+Stunning Schenker Graphs with GNU LilyPond}}. 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.”
+This article is now available @uref{http://www.linuxjournal.com/article/8583,on-line}.
+@newsEnd
+
+
+@newsItem
+@subsubheading New binaries for LilyPond 2.7.26 - @emph{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 @ref{old downloads}
+page. Let us know how you fare!
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.26 is out - @emph{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!
+(@ref{changes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.25 is out - @emph{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). (@ref{changes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.24 is out - @emph{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. (@ref{changes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.23 is out - @emph{December 19, 2005}
+This release has the following new features:
+@itemize
+@item
+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).
+@item
+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).
+@item
+Generic music functions may now also be used on
+articulations and chord elements (feature sponsored by Sean Reed and
+Bertalan Fodor).
+@item
+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.
+@end itemize
+(@ref{changes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.22 is out - @emph{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. (@ref{changes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.21 is out - @emph{December 5, 2005}
+Saint Nicholas brings you ... a @uref{http://www.musicxml.org/,MusicXML} convertor for LilyPond!
+The convertor is basic, but working. Check out the @uref{http://www.lilypond-design.com/sponsor/open-features.html#inputfilter,
+LilyPond Software Design} pages for MusicXML features that can be
+sponsored.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.20 is out - @emph{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). (@ref{changes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.6.5 is out - @emph{December 1, 2005}
+This release updates the bugreporting address and reorganizes the
+documentation tree. (@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.19 is out - @emph{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. (@ref{changes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.18 is out - @emph{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. (@ref{changes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.17 is out - @emph{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. (@ref{changes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.16 is out - @emph{November 11, 2005}
+This release fixes a large number of bugs. Please upgrade before
+reporting bugs in the 2.7 series. (@ref{changes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.15 is out - @emph{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. (@ref{changes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.14 is out - @emph{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.
+@verbatim
+
+\override Beam #'direction = #(lambda (grob)
+(if (> (random 10) 5) UP DOWN))
+
+@end verbatim
+will set a random direction for beams. (@ref{changes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.13 is out - @emph{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. (@ref{changes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.6.4 is out - @emph{October 11, 2005}
+This release fixes a few minor problems with the stable
+series. (@ref{changes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.12 is out - @emph{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). (@ref{changes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.11 is out - @emph{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. (@ref{changes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.10 is out - @emph{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. (@ref{changes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.9 is out - @emph{September 5, 2005}
+This is mainly a bugfix
+release. (@ref{changes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading Traduction française du site - @emph{September 03, 2005}
+Grâce à @uref{about/thanks#website,l'équipe des traducteurs},
+de nombreuses pages du site sont maintenant disponibles en français,
+notamment l'@uref{about/automated-engraving/index.fr.html,essai sur
+la gravure musicale}.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.8 is out - @emph{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. (@ref{changes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading Article in `De Standaard' - @emph{August 20, 2005}
+The Belgian newspaper @emph{De Standaard} investigates what drives
+Free Software authors in an article titled @emph{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.
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.7 is out - @emph{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á. (@ref{changes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.6 is out - @emph{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. (@ref{changes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.5 is out - @emph{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. (@ref{changes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.4 is out - @emph{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. (@ref{changes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.6.3 is out - @emph{August 4, 2005}
+This release fixes a memory corruption bug that was triggered by
+\override'ing Beam settings. (@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.6.2 is out - @emph{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. (@ref{changes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.3 is out - @emph{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.
+(@ref{changes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.2 is out - @emph{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. (@ref{changes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.6 released - @emph{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).
+@strong{Get up and running in minutes!} Pango text formatting lets you
+print @strong{Unicode } lyrics in your favorite script and font. Create
+@strong{SVG} files, and edit them in Inkscape.
+(@uref{announce-v2.6.html,Announcement}, @ref{old downloads}, @ref{changes})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7.1 is out - @emph{July 20, 2005}
+LilyPond 2.7.1 has no user-visible changes. However, due to
+restructuring @qq{under the hood}, this version will be 10 to
+20 % faster. (@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.6.1 is out - @emph{July 11, 2005}
+This version fixes a few minor bugs found in
+2.6.0, and also works on DOS-based Windows versions. (@ref{changes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.7 is out - @emph{July 9, 2005}
+LilyPond 2.7.0 is out. It has support for paragraph text and
+pitched trill notation. (@ref{changes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading 2.5.31 released - @emph{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.
+(@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading Traduction du site de LilyPond - @emph{15 juin 2005}
+@uref{about/thanks#website,L'équipe des traducteurs} vous présente
+le site de LilyPond en français. Nous travaillons sur la traduction des
+pages encore non traduites. Bon surf !
+@newsEnd
+
+
+@newsItem
+@subsubheading 2.5.31 for Windows and MacOS - @emph{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.
+(@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading 2.5.31 released - @emph{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. (@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading 2.5.30 released - @emph{June 10, 2005}
+This is (hopefully) the last Release Candidate before 2.6. Give it a
+good shake to find those last bugs! (@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading 2.5.29 released - @emph{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). (@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading 2.5.27 released - @emph{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. (@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading Windows and MacOS installers available - @emph{May 26, 2005}
+There are now a native, standalone installers for Windows and
+MacOS. They also support PDF point & click. (@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading 2.5.26 released - @emph{May 26, 2005}
+This release has a couple of small bugfixes.
+@newsEnd
+
+
+@newsItem
+@subsubheading 2.5.25 released - @emph{May 20, 2005}
+This release has many small bugfixes and updates to the
+documentation. (@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading 2.5.24 released - @emph{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. (@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading 2.5.23 released - @emph{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. (@ref{changes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading 2.5.22 released - @emph{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.
+(@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+(@ref{changes},
+@ref{old downloads})
+@newsEnd
+
+
+@newsItem
+@subsubheading 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 @ref{changes}
+file, or go straight to @ref{old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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 @ref{changes}
+file and @ref{old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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. @ref{old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading 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. @ref{old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading 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 @ref{changes}
+file and @ref{old downloads}!
+@newsEnd
+
+
+@newsItem
+@subsubheading 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 @ref{changes}
+file and download @ref{old downloads}!
+@newsEnd
+
+
+@newsItem
+@subsubheading March 7, 2005
+LilyPond 2.4.5 is out. This release backports the tieWaitForNote
+feature and has support for tetex-3.0.
+@ref{old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading February 28, 2005
+LilyPond 2.5.13 is available for Fedora Core 3. You need to install @uref{http://lilypond.org/download/binaries/Fedora-3/ghostscript-8.15rc3-0.i386.rpm,ESP
+Ghostscript 8.15rc3}. 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.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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 @uref{http://lilypond.org/doc/v2.5/Documentation/user/out-www/lilypond/Point-and-click.html,here}.
+Take a look at the @ref{changes}
+file and download @ref{old downloads}!
+@newsEnd
+
+
+@newsItem
+@subsubheading February 26, 2005
+The @uref{http://lsr.dsi.unimi.it/,Lilypond Snippet
+Repository (LSR)} 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.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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 @strong{all}
+fonts available via FontConfig. Also, arpeggios may be written out
+using ties and individual objects may have colors! Take a look at
+the @ref{changes}
+file and @ref{old downloads}!
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{old downloads}!
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading 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
+@uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.3065&content-type=text/vnd.viewcvs-markup,
+change log
+} and @ref{old downloads}!
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{old downloads}
+and check out the changes in
+the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.3048&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{old downloads}
+and check out the
+changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.3013&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{old downloads}
+and check out the changes in
+the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev= 1.3000&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{old downloads}
+and check out the
+changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2974&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{old downloads}
+and
+check out the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2908&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{old downloads}
+and check out the changes in
+the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2898&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{old downloads}
+and check out the changes in
+the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2881&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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
+@verbatim
+
+\cueDuring #VOICE-NAME #DIRECTION { MUSIC }
+
+@end verbatim
+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.
+@ref{old downloads}
+and check out
+the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2837&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{old downloads}
+and check out the changes in
+the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2780.2&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading October 31, 2004
+LilyPond 2.4.0 was just @uref{announce-v2.4.html,released!}
+This new stable version has support for page-layout,
+completely rewritten slur formatting and many other
+improvements. Read about them in the @ref{changes}
+file.
+@ref{old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{old downloads}
+and check out the changes in
+the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2773&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{old downloads}
+and check out the changes in
+the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2765&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{old downloads}
+and check out the changes in
+the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2752&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{old downloads}
+and check out the changes in
+the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2742&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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@{@}.
+@ref{old downloads}
+and
+check out the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2709&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{old downloads}
+and check
+out the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2692&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{old downloads}
+and check out the changes in
+the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2674&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading September 29, 2004
+The LilyPond development team will be present at the @uref{http://www.nluug.nl/events/sane2004/bazaar/index.html,Free
+Software Bazaar} 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.
+@newsEnd
+
+
+@newsItem
+@subsubheading September 26, 2004
+LilyPond 2.3.19 is out. It's mainly a bugfix release.
+@ref{old downloads}
+and check out the changes
+in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2652&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{old downloads}
+and check out the changes in
+the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2614&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{old downloads}
+and check out the changes in
+the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2562&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{old downloads}
+and check out the changes in
+the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2553&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{old downloads}
+and check out
+the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2534&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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!
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{old downloads}
+and
+check out the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2520&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading August 24, 2004
+LilyPond 2.2.6 fixes a few minor issues, among others, the
+disappearing metronome mark.
+@ref{old downloads}
+and check out the changes in
+the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2000.2.33&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{old downloads}
+and check out the changes in
+the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2489&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading August 3, 2004
+LilyPond 2.3.11 is out. This release basically is 2.3.10 with a few
+annoying bugs fixed.
+@ref{old downloads}
+and check out
+the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2449&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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:
+@itemize
+@item
+Running trills now have their own spanner and event. They are
+started and stopped with \startTrillSpan and \stopTrillSpan
+@item
+There is a new markup command `\postscript' that takes a string
+that is dumped as verbatim PostScript
+@end itemize
+
+@ref{old downloads}
+and check out
+the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2435&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{old downloads}
+and check out
+the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2416&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{old downloads}
+and check out the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2395&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{old downloads}
+and check out the changes in
+the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2383&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading July 15, 2004
+LilyPond 2.2.5 was released. It has a few bug fixes from
+2.3.x.
+@ref{old downloads}
+and check
+out the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2000.2.28&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading July 11, 2004
+An introductory article on LilyPond appeared on @uref{http://www.linuxjournal.com/article.php?sid=7657&mode=thread&order=0,Linux
+Journal}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{old downloads}
+and check out the changes
+in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2306&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading July 5, 2004
+LilyPond 2.2.4 was released. It is mainly a bug fix
+release.
+@ref{old downloads}
+and
+check out the changes in the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2000.2.23&content-type=text/vnd.viewcvs-markup,ChangeLog}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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 @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2293&content-type=text/vnd.viewcvs-markup,ChangeLog}
+and
+@ref{old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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 @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2000.2.16&content-type=text/vnd.viewcvs-markup,ChangeLog} for a full description and
+@ref{old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading June 13, 2004
+LilyPond 2.3.4 further improves the output backends. As a
+result, manual page-breaks, multiple output formats and putting
+@code{\score} into markups now works. Check out the @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2242&content-type=text/vnd.viewcvs-markup,ChangeLog}
+and
+@ref{old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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 @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2207&content-type=text/vnd.viewcvs-markup,ChangeLog}
+and
+@ref{old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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 @uref{http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lilypond/ChangeLog?rev=1.2000.2.9,ChangeLog}
+or head straight to the
+@ref{old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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 @ref{changes} or head straight to the
+@ref{old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading May 9, 2004
+LilyPond 2.3.1 is out. This release has many new and cool
+features. Check out the @ref{changes} or head straight to the
+@ref{old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading May 4, 2004
+Help LilyPond get better, and join in on LilyPond
+development! This
+@uref{devel/participating/call-for-help.html,call for
+help} 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!
+@newsEnd
+
+
+@newsItem
+@subsubheading May 3, 2004
+LilyPond 2.2.1 has been released. It fixes a handful of bugs.
+@ref{old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading April 17, 2004
+LilyPond 2.2.0 is now available
+on Windows, and should find its way to the Cygwin mirrors
+soon.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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 @emph{experimental}; expect things to break!
+More info in the @ref{changes}.
+@ref{old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading April 8, 2004
+A French article on the new LilyPond
+release appeared on @uref{http://linuxfr.org/2004/04/08/15968.html,linuxfr.org}.
+@newsEnd
+
+
+@newsItem
+@subsubheading April 8, 2004
+Binaries for LilyPond 2.2.0 are available for
+MacOS X, Slackware, Mandrake and Debian Woody.
+@ref{old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading 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 @uref{announce-v2.2.html,announcement} or skip to the
+@ref{old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading March 30, 2004
+LilyPond 2.1.36 has many fixes in
+the user manual.
+@ref{old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading March 28, 2004
+LilyPond 2.1..35 fixes a slew of
+bugs, and has the @code{raggedlast} option, which causes
+paragraph like line breaking for scores. More info in the
+@ref{changes}.
+@ref{old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading March 22, 2004
+LilyPond 2.1.34 fixes minor bugs, and has more rewriting.
+@ref{old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading March 21, 2004
+LilyPond 2.1.33 fixes a serious bug, and a few other
+irritations.
+@ref{old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading 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).
+@ref{old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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
+@ref{changes} and
+@ref{old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading March 14, 2004
+The
+@uref{http://linuxmusician.com/index.php?option=articles&task=viewarticle&artid=10,linuxmusician.com interview} made the
+@uref{http://slashdot.org/article.pl?sid=04/03/13/2054227&mode=thread&tid=141&tid=188,slashdot
+frontpage!}.
+@newsEnd
+
+
+@newsItem
+@subsubheading March 11, 2004
+@uref{http://linuxmusician.com,linuxmusician.com} is
+running an
+@uref{http://linuxmusician.com/index.php?option=articles&task=viewarticle&artid=10,interview}
+with Han-Wen Nienhuys and Jan Nieuwenhuizen, the main
+authors of LilyPond.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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
+@ref{changes} and
+@ref{old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading March 9, 2004
+LilyPond 2.1.29 fixes a couple of MIDI bugs, and has
+experimental support for producing titles with
+@code{markup}.
+@newsEnd
+
+
+@newsItem
+@subsubheading February 29, 2004
+In LilyPond 2.1.28 Scheme property functions may be used
+argument to @code{set!}. In addition, parts of the manual
+have been proofread and corrected in this release. See the
+@ref{changes} and
+@ref{old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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
+@ref{changes} and
+@ref{old downloads}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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
+@ref{changes}.
+@ref{old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading February 18, 2004
+LilyPond 2.1.25 fixes many bugs, and changes the conventions
+for altering accidental rules.
+@ref{old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading February 16, 2004
+LilyPond 2.1.24 has a big
+internal rewrite. One of its practical consequences is that
+@code{\with} now also works with @code{Score}
+contexts. Further 2.1.23, which was not announced here,
+fixes a few bugs caused by the change of @code{\property}
+syntax and has updates in the Program Reference document.
+More information in the
+@ref{changes}.
+@ref{old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading February 13, 2004
+LilyPond 2.1.22 has a
+simplification of the @code{\property} syntax: it is
+shorter and more consistent now. More information in the
+@ref{changes}.
+@ref{old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading 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
+@ref{changes}.
+@ref{old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading 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
+@ref{changes}.
+@ref{old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading February 5, 2004
+LilyPond 2.1.19 has rewritten
+support for drum notation. This release also makes some
+long-standing cleanups: the removal of @code{Thread} (all
+functionality is now moved into @code{Voice}) and Lyrics
+(functionality moved to @code{LyricsVoice}) context.
+More information in the
+@ref{changes}.
+@ref{old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading February 4, 2004
+LilyPond 2.1.18 is out. This
+release has the new part-combiner installed by default, and a
+similar implementation of @code{autochange}. More information
+in the
+@ref{changes}.
+@ref{old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading February 2, 2004
+LilyPond 2.1.17 is out. It adds texts
+(solo, a due) for the part combiner. It also reinstates the
+@code{--safe} option which prevents havoc by Scheme exploits. More
+information in the
+@ref{changes}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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
+@ref{changes}.
+@ref{old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading 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
+@ref{changes}. @ref{old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading 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
+@ref{changes}. @ref{old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading January 19, 2004
+LilyPond 2.1.12 fixes many bugs
+and improves formatting of ottava brackets. More information in
+the
+@ref{changes}. @ref{old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading January 18, 2004
+LilyPond 2.1.11 is now also
+available for Windows! For downloading, go
+@uref{http://www.inf.bme.hu/~berti/lilypond/,here}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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
+@ref{changes}. @ref{old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading January 16, 2004
+LilyPond 2.1.10 has a load of
+bugfixes and a shorter syntax for octave checks. More
+information in the
+@ref{changes}. @ref{old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading 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
+@ref{changes}. @ref{old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading January 9, 2004
+LilyPond 2.1.8 has an important new
+feature: it is now possible to use @code{\property} to tune
+the appearance of spanning objects like @code{StaffSymbol} and
+@code{SystemStartBrace}. In addition, contexts may be
+modified with @code{\remove} and @code{\consists} for
+individual music expressions.
+More information in the
+@ref{changes}. @ref{old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading January 7, 2004
+An update to the stable branch,
+version 2.0.2, was released today. It contains a couple of
+minor bugfixes. @ref{old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading 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
+@ref{changes} and download @uref{install/#2.1,here}.
+@newsEnd
+
+
+@newsItem
+@subsubheading January 4, 2004
+LilyPond 2.1.6 continues to
+improve the layout of lyrics. More
+information in the
+@uref{@@DOC@@v2.1/Documentation/topdocs/out-www/NEWS.html,release
+notes} and download @uref{install/#2.1,here}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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ängers Morgen. More
+information in the
+@ref{changes} and download @uref{install/#2.1,here}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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
+@ref{changes} and download @uref{install/#2.1,here}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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
+@ref{changes} and download @uref{install/#2.1,here}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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
+@ref{changes} and download @uref{install/#2.1,here}.
+@newsEnd
+
+
+@newsItem
+@subsubheading December 16, 2003
+LilyPond 2.1.1 released. This
+release wraps together all the small fixes made during
+Han-Wen's absence. See the
+@ref{changes} and download @uref{install/#2.1,here}.
+@newsEnd
+
+
+@newsItem
+@subsubheading October 11, 2003
+LilyPond 2.1.0 released. See the
+@ref{changes} and
+download @uref{install/#2.1,here}.
+@newsEnd
+
+
+@newsItem
+@subsubheading October 11, 2003
+LilyPond 2.0.1 binaries for Mandrake 9.1
+available from
+@uref{http://rpm.nyvalls.se/sound9.1.html,here}
+thanks to Heikki Junes.
+@newsEnd
+
+
+@newsItem
+@subsubheading October 9, 2003
+LilyPond 2.0.1 binaries for Slackware 9
+available from @uref{install/#2.0,here},
+thanks to Ricardo Hoffman.
+@newsEnd
+
+
+@newsItem
+@subsubheading October 5, 2003
+LilyPond 2.0.1 binaries are available for Macos X, many thanks to
+Matthias Neeracher.
+@ref{old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading October 4, 2003
+LilyPond 2.0.1 binaries are available for Windows (Cygwin
+version 1.5).
+@ref{old downloads}. Thanks to Bertalan
+Fodor, our new Cygwin maintainer!
+@newsEnd
+
+
+@newsItem
+@subsubheading September 29, 2003
+LilyPond 2.0.1 is released. It
+contains minor bugfixes.
+See the @ref{changes}
+or download @uref{install/#2.0,here} directly.
+@newsEnd
+
+
+@newsItem
+@subsubheading September 27, 2003
+PlanetCCRMA has been updated to include LilyPond 2.0. Go
+@uref{http://www-ccrma.stanford.edu/planetccrma/software/soundapps.html#lilypond,
+here} to download. Thanks to Fernando Pablo
+Lopez-Lezcano!
+@newsEnd
+
+
+@newsItem
+@subsubheading 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
+@uref{announce-v2.0.html,here}, or go to the
+@uref{install/#2.0,download page} directly.
+@newsEnd
+
+
+@newsItem
+@subsubheading September 24, 2003
+LilyPond 1.9.10 is released. This is
+the final LilyPond 2.0 release candidate. Check
+the @ref{changes} and
+download @uref{install/,here}.
+@newsEnd
+
+
+@newsItem
+@subsubheading September 23, 2003
+LilyPond 1.9.9 is released. This is
+the second LilyPond 2.0 prerelease. Check
+the @ref{changes} and
+download @uref{install/,here}.
+@newsEnd
+
+
+@newsItem
+@subsubheading September 19, 2003
+LilyPond 1.9.8 is released. This is
+the first LilyPond 2.0 prerelease. Check
+the @ref{changes} and
+download @uref{install/,here}.
+@newsEnd
+
+
+@newsItem
+@subsubheading September 17, 2003
+LilyPond 1.9.7 is released. LilyPond
+now has support for quarter tone accidentals!
+@ref{old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading September 16, 2003
+LilyPond 1.9.6 is released.
+It has a lot of minor fixes and updates.
+@ref{old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading 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.
+@ref{old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading September 9, 2003
+LilyPond 1.8.2 is released. This
+release fixes a couple of minor bugs.
+@ref{old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading September 7, 2003
+LilyPond 1.8 binaries are available
+for Windows (Cygwin version 1.5).
+@ref{old downloads}
+@newsEnd
+
+
+@newsItem
+@subsubheading August 31, 2003
+LilyPond 1.9.4 is released.
+@emph{This is an experimental release}: read the
+@uref{http://mail.gnu.org/archive/html/lilypond-devel/2003-08/msg00133.html,announcement}
+before trying.
+@newsEnd
+
+
+@newsItem
+@subsubheading August 31, 2003
+LilyPond 1.8 binaries for slackware
+available. Get them @uref{install/,here}.
+@newsEnd
+
+
+@newsItem
+@subsubheading 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
+@ref{changes} and get it @uref{download#1.9,here}.
+@newsEnd
+
+
+@newsItem
+@subsubheading August 28, 2003
+LilyPond 1.9.2 is released. Read the
+@ref{changes} and get it
+@uref{download#1.9,here}.
+@newsEnd
+
+
+@newsItem
+@subsubheading August 26, 2003
+LilyPond 1.9.1 is released. Read the
+@ref{changes} and get it
+@uref{download#1.9,here}.
+@newsEnd
+
+
+@newsItem
+@subsubheading August 25, 2003
+The LilyPond 1.9 development release is available. Read the
+@ref{changes} and get it
+@uref{download#1.9,here}.
+@newsEnd
+
+
+@newsItem
+@subsubheading August 25, 2003
+Mandrake 9.1 RPMS available, get them
+@uref{http://rpm.nyvalls.se/sound9.1.html,here}.
+@newsEnd
+
+
+@newsItem
+@subsubheading August 21, 2003
+LilyPond 1.8.1 was released. Get it @uref{install/,here}, or
+read the @ref{changes}.
+@newsEnd
+
+
+@newsItem
+@subsubheading August 18, 2003
+PlanetCCRMA (eg. RedHat 8 and 9)
+has been updated to 1.8.
+Download @uref{http://www-ccrma.stanford.edu/planetccrma/software/soundapps.html#lilypond,here.}
+@newsEnd
+
+
+@newsItem
+@subsubheading August 7, 2003
+LilyPond 1.8 is released. Read
+@ref{changes} and get it @uref{install/,here}.
+@newsEnd
+
+
+@newsItem
+@subsubheading August 7, 2003
+New website went live!
+@newsEnd
+
+
+@newsItem
+@subsubheading August 6, 2003
+Announced new website.
+@newsEnd
+
+
+@newsItem
+@subsubheading August 1, 2003
+LilyPond 1.7.30 released.
+@newsEnd
+
+
+@newsItem
+@subsubheading July 30, 2003
+Website: present @uref{about/automated-engraving/index.html,treatise}
+about music engraving, music printing software, and LilyPond's
+unique faculties.
+@newsEnd
+
+
+@newsItem
+@subsubheading July 29, 2003
+1.7.29 - release candidate 4 has been released. Packages for
+Red Hat, Debian, Cygwin are @uref{install/,available}.
+@newsEnd
+
################################################################
# website (without the rest of the docs)
web-gop:
- touch Documentation/general.texi
- cd Documentation && make out=www out-www/general/index.html
+ touch Documentation/web.texi
+ cd Documentation && make out=www out-www/web/index.html
################################################################
$(outdir)/index.$(ISOLANG).html: TEXI2HTML_SPLIT = $(WEB_TEXI2HTML_SPLIT)
$(outdir)/index.$(ISOLANG).html:
- $(TEXI2HTML) $(TEXI2HTML_FLAGS) $(TEXI2HTML_SPLIT) --output=$(outdir)/ general.texi
+ $(TEXI2HTML) $(TEXI2HTML_FLAGS) $(TEXI2HTML_SPLIT) --output=$(outdir)/ web.texi
find $(outdir)/ -name '*.html' | xargs grep -L --label="" 'UNTRANSLATED NODE: IGNORE ME' | sed 's!$(outdir)/!!g' | xargs $(buildscript-dir)/mass-link --prepend-suffix .$(ISOLANG) hard $(outdir) $(top-build-dir)/Documentation/$(outdir)
.SECONDARY:
XREF_MAPS_FILES=$(TEXINFO_MANUALS:%=$(XREF_MAPS_DIR)/%.$(ISOLANG).xref-map)
XREF_MAP_FLAGS += -I $(outdir)
-WEB_MANUALS=general
+WEB_MANUALS=web
###########
ifneq ($(ISOLANG),)
WEB_TEXI2HTML_SPLIT = --prefix=index --split=node --node-files
TEXI2HTML_SPLIT = $(DOC_TEXI2HTML_SPLIT)
-$(top-build-dir)/Documentation/$(outdir)/general/index.$(ISOLANG).html:\
+$(top-build-dir)/Documentation/$(outdir)/web/index.$(ISOLANG).html:\
TEXI2HTML_INIT = $(WEB_TEXI2HTML_INIT)
-$(top-build-dir)/Documentation/$(outdir)/general/index.$(ISOLANG).html:\
+$(top-build-dir)/Documentation/$(outdir)/web/index.$(ISOLANG).html:\
TEXI2HTML_SPLIT := $(WEB_TEXI2HTML_SPLIT)
TEXI2HTML_INCLUDES += --I=. --I=$(src-dir) --I=$(outdir) $(DOCUMENTATION_INCLUDES) --I=$(XREF_MAPS_DIR)
# FIXME: Hardcoded file names!?
manuals_subdirectories_re = \
- re.compile ('(usage|automated-engraving|changes|essay|extending|general|learning|notation)/')
+ re.compile ('(usage|automated-engraving|changes|essay|extending|web|learning|notation)/')
def add_old_name (file_path):
for new_path in renames_map:
return 'href="' + os.path.join (source_val, m.group (1)) + '"'
# More hardcoding, yay!
-splitted_docs_re = re.compile('(Documentation/out-www/(automated-engraving|essay|notation|changes|music-glossary|usage|general|learning|snippets))/')
+splitted_docs_re = re.compile('(Documentation/out-www/(automated-engraving|essay|notation|changes|music-glossary|usage|web|learning|snippets))/')
lily_snippets_re = re.compile ('(href|src)="([0-9a-f]{2}/lily-.*?)"')
pictures_re = re.compile ('src="(pictures/.*?)"')
### add footer
if footer_tag_re.search (s) == None:
- if 'general' in file_name:
+ if 'web' in file_name:
s = add_footer (s, footer_tag + web_footer)
else:
s = add_footer (s, footer_tag + footer)
projects / lilypond.git / commitdiff