From 29d3c505fa15eaab6f1c39b518e794c1b68aa707 Mon Sep 17 00:00:00 2001 From: Francisco Vila Date: Mon, 21 Dec 2009 11:07:09 +0100 Subject: [PATCH] web-es: a first set of translations committishes not there yet and a few other details left --- Documentation/es/web.texi | 159 + Documentation/es/web/GNUmakefile | 5 + Documentation/es/web/basic-authors.itexi | 596 ++++ Documentation/es/web/community.itexi | 938 ++++++ Documentation/es/web/download.itexi | 549 ++++ Documentation/es/web/introduction.itexi | 1073 +++++++ Documentation/es/web/manuals.itexi | 839 ++++++ Documentation/es/web/news-front.itexi | 20 + Documentation/es/web/news.itexi | 3351 ++++++++++++++++++++++ 9 files changed, 7530 insertions(+) create mode 100644 Documentation/es/web.texi create mode 100644 Documentation/es/web/GNUmakefile create mode 100644 Documentation/es/web/basic-authors.itexi create mode 100644 Documentation/es/web/community.itexi create mode 100644 Documentation/es/web/download.itexi create mode 100644 Documentation/es/web/introduction.itexi create mode 100644 Documentation/es/web/manuals.itexi create mode 100644 Documentation/es/web/news-front.itexi create mode 100644 Documentation/es/web/news.itexi diff --git a/Documentation/es/web.texi b/Documentation/es/web.texi new file mode 100644 index 0000000000..94cdaa7a1c --- /dev/null +++ b/Documentation/es/web.texi @@ -0,0 +1,159 @@ +\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: notación musical para todos +@documentencoding UTF-8 +@documentlanguage es +@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 por los autores. + +@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... notación musical para todos +@end ifnottex + + +@c hack for texi2html, bleh -gp +@ifnothtml + +@finalout + +@titlepage +@title LilyPond +@subtitle El tipografiador de música +@titlefont{Información general} +@author El equipo de desarrollo de LilyPond + +@vskip 0pt plus 1filll +@c @vskip 20pt + +@insertcopying{} + +Para LilyPond versión @version{} +@end titlepage +@end ifnothtml +@c end hack for texi2html + + +@c ************************ WEBSITE START *************** + + +@divId{pageHeader} +@heading LilyPond + +... notación musical para todos +@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é es LilyPond? + +LilyPond es un programa de grabado musical de código abierto, +consagrado a la producción de partituras de la calidad más alta +posible. Este programa de software libre lleva la estética de la +música grabada de la forma tradicional a las partituras impresas +mediante ordenador. + +@divClass{align-right} +¡Puede leer más en nuestra @ref{Introducción}! + +@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 Enlaces rápidos + +@c TODO: javascript to detect OS and suggest download? + +@subsubheading Estable + +@ref{Download, Descarga de @versionStable} + +@ref{Manuals, Manuales de @versionStable} + +@subsubheading Desarrollo + +@ref{Development, Descarga de @versionDevel} + +@ref{Development, Manuales de @versionDevel} + +@divEnd + + +@ifnottex + +@divClass{hide} +@menu +* Introducción:: Empiece aquí a crear partituras musicales. +* Descarga:: Obtener LilyPond. +* Manuales:: Léase los dichosos manuales (RTFM). +* Comunidad:: Póngase en contacto con otros usuarios. +@end menu +@divEnd + +@end ifnottex + +@contents + + +@include web/introduction.itexi +@include web/download.itexi +@include web/manuals.itexi +@include web/community.itexi + +@bye diff --git a/Documentation/es/web/GNUmakefile b/Documentation/es/web/GNUmakefile new file mode 100644 index 0000000000..425cc1d8e2 --- /dev/null +++ b/Documentation/es/web/GNUmakefile @@ -0,0 +1,5 @@ +depth = ../../.. + +LOCALSTEPMAKE_TEMPLATES = ly + +include $(depth)/make/stepmake.make diff --git a/Documentation/es/web/basic-authors.itexi b/Documentation/es/web/basic-authors.itexi new file mode 100644 index 0000000000..a5986b4791 --- /dev/null +++ b/Documentation/es/web/basic-authors.itexi @@ -0,0 +1,596 @@ +@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. All lists are sorted alphabetically. + + 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 also split between Current and Previous, and + each category contains: + 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: +@email{mats.bengtsson@@ee.kth.se}, +@uref{http://www.s3.kth.se/~mabe/}, +Support guru + +@item Trevor Daniels: +Assistant documentation editor + +@item John Mandereau: +@email{john.mandereau@@free.fr}, +Translation meister + +@item Patrick McCarty: +Core developer + +@item Joe Neeman: +Core developer + +@item Han-Wen Nienhuys: +@email{hanwen@@xs4all.nl}, +@uref{http://www.xs4all.nl/~hanwen/}, +Main author + +@item Jan Nieuwenhuizen: +@email{janneke@@gnu.org}, +@uref{http://www.xs4all.nl/~jantien/}, +Main author + +@item Graham Percival: +@uref{http://percival-music.ca}, +Project manager, Documentation Editor + +@item Nicolas Sceaux: +Core developer + +@item Carl Sorensen: +@email{c_sorensen@@byu.edu}, +Core developer, Frog meister + +@item Valentin Villenave: +LSR editor and Bug meister + +@end itemize +@end macro + + + +@macro developersPrevious + +@itemize +@item Pedro Kroeger: +Build meister + +@item Graham Percival: +@uref{http://percival-music.ca}, +Bug meister, Grand Documentation Project leader + +@item Erik Sandberg: +Bug meister + +@end itemize +@end macro + + +@c ***************** current contributors + +@macro coreCurrent + +@itemize +@item Frédéric Bron: Frog + +@item Hajo Dezelski: Frog + +@item Andrew Hawryluk: Frog + +@item Ian Hulin: Frog + +@item Marek Klein: Frog + +@item Kieren MacMillan: Frog + +@item Andrew Wilson: Frog + +@end itemize +@end macro + + + +@macro fontCurrent + +@c nobody listed yet +@c @itemize +@c @item + +@c @end itemize +@end macro + + + +@macro docCurrent + +@itemize +@item Jonathan Kulp: +Clean-ups in documentation + +@item James Lowe: +Minor editing + +@item Ralph Palmer: +Documentation indexing + +@item Patrick Schmidt: +CSS improvements + +@end itemize +@end macro + + +@macro supportCurrent + +@itemize +@item James E. Bailey: +Bug meister + +@item Christian Hitz: +update gui for OSX 10.5. + +@end itemize +@end macro + + + +@macro translationsCurrent + +@itemize +@item Jean-Charles Malahieude: +@email{lolyfan@@wanadoo.fr}, +French translation of messages, website and documentation + +@item Till Rettig: +German translation + +@item Yoshiki Sawada: +Japanese translation + +@item Francisco Vila: +Spanish translation + +@end itemize +@end macro + + +@c ***************** previous contributors + +@macro corePrevious + +@itemize + +@item Erlend Aasland: +Color support, tablature improvements, trivial @code{\\mark} +stuff, al-niente hairpins + +@item Maximilian Albert: + +@item Guido Amoruso: + +@item Kristof Bastiaensen: + +@item Pal Benko: +@email{benkop@@freestart.hu}, +Ancient notation + +@item Juliusz Chroboczek: +@email{jch@@pps.jussieu.fr}, +Type42 code + +@item Angelo Contardi: + +@item David Feuer: +@email{david.feuer@@gmail.com}, +PS output code refactoring + +@item Bertalan Fodor: + +@item Mathieu Giraud: + +@item Yuval Harel: + +@item Bernard Hurley: +@email{bernard@@fong-hurley.org.uk}, +X11 color + +@item Yoshinobu Ishizaki: + +@item Chris Jackson: +@email{chris@@fluffhouse.org.uk}, +Piano pedals, directed arpeggios + +@item David Jedlinsky: + +@item Heikki Junes: +@email{heikki.junes@@hut.fi}, +Fine tuning for quarter tones in midi output + +@item Reinhold Kainhofer: +@email{reinhold@@kainhofer.com}, +@uref{http://reinhold.kainhofer.com}, +Musicxml2ly development, various features and fixes + +@item Michael Krause: +@email{m.krause@@tu-harburg.de}, +Breathing signs + +@item Jean-Baptiste Lamy: +@email{jiba@@tuxfamily.org}, +Tablature support + +@item Werner Lemberg: +@email{wl@@gnu.org}, +@TeX{} glue code + +@item Jonatan Liljedahl: + +@item Peter Lutek: + +@item Hendrik Maryns: + +@item Joe Neeman: +@email{joeneeman@@gmail.com}, +Constrained line breaking + +@item Matthias Neeracher: + +@item Han-Wen Nienhuys: +@email{hanwen@@xs4all.nl}, +@uref{http://www.xs4all.nl/~hanwen/}, +Main author + +@item Jan Nieuwenhuizen: +@email{janneke@@gnu.org}, +@uref{http://www.xs4all.nl/~jantien/}, +Main author + +@item Tatsuya Ono: + +@item Lisa Opus Goldstein: + +@item Guy Gascoigne-Piggford: + +@item Niel Puttock: + +@item Jürgen Reuter: +@email{reuter_j@@web.de}, +@uref{http://www.juergen-reuter.de}, +Ancient notation support (Mensural and Gregorian chant) +ambitus, clusters + +@item Stan Sanderson: +Regression Checker + +@item Erik Sandberg: + +@item Edward Sanford Sutton: + +@item Nicolas Sceaux: +@email{nicolas.sceaux@@free.fr}, +Scheme macros, @code{\\markup} syntax + +@item Andreas Scherer: + +@item Johannes Schindelin: + +@item Kim Shrier: + +@item Vicente Solsona Della: + +@item David Svoboda: + +@item Sebastiano Vigna: + +@item Arno Waschk: + +@item Michael Welsh Duggan: + +@item John Williams: + +@item Milan Zamazal: + +@item Carl Sorensen: +@email{c_sorensen@@byu.edu}, +Fret diagrams + +@item Rune Zedeler: +Auto-accidental code, zigzag glissandi, rest bugfixes, +minimum fret, @code{subdivideBeams}. + +@end itemize +@end macro + + + +@macro fontPrevious + + +@itemize + +@item Tom Cato Amundsen: +@email{tca@@gnu.org}, +Accordion symbols + +@item Chris Jackson: +@email{chris@@fluffhouse.org.uk}, +Arpeggio arrow + +@item Han-Wen Nienhuys: +@email{hanwen@@xs4all.nl}, +@uref{http://www.xs4all.nl/~hanwen/}, +Main author + +@item Jan Nieuwenhuizen: +@email{janneke@@gnu.org}, +@uref{http://www.xs4all.nl/~jantien/}, +Main author + +@item Jürgen Reuter: +@email{reuter_j@@web.de}, +@uref{http://www.juergen-reuter.de}, +Ancient notation font Exact Type1 font outlines for feta, +feta-alphabet + +@item Arno Waschk: +@email{arno@@arnowaschk.de}, +"Espressivo" mark + +@item Rune Zedeler: +16th and shorter rests + +@end itemize +@end macro + + + +@macro docPrevious + + +@itemize + +@item Erlend Aasland: + +@item Trevor Bača: +Inspirational headwords + +@item Alard de Boer: +Formatting + +@item Mats Bengtsson: +@email{mats.bengtsson@@ee.kth.se}, +@uref{http://www.s3.kth.se/~mabe/}, +Example files, documentation + +@item Jay Hamilton: +NR work + +@item Andrew Hawryluk: +NR work + +@item Joseph Harfouch: +NR work + +@item Cameron Horsburgh: +Formatting and editing + +@item Geoff Horton: +Formatting and editing + +@item Heikki Junes: +@email{heikki.junes@@hut.fi}, +Clean-ups in documentation and example files + +@item Reinhold Kainhofer: +Technical aid + +@item Kurt Kroon: +Glossary, updates and NR work + +@item Jonathan Kulp: +Clean-ups in documentation + +@item Dave Luttinen: +Formatting and editing + +@item Patrick McCarty: +NR work + +@item John Mandereau: +@email{john.mandereau@@free.fr}, +Internationalization + +@item Christian Mondrup: +@email{scancm@@biobase.dk}, +Glossary + +@item Han-Wen Nienhuys: +@email{hanwen@@xs4all.nl}, +@uref{http://www.xs4all.nl/~hanwen/}, +Main author + +@item Jan Nieuwenhuizen: +@email{janneke@@gnu.org}, +@uref{http://www.xs4all.nl/~jantien/}, +Main author + +@item Eyolf Østrem: +NR work + +@item Ralph Palmer: +Documentation indexing + +@item François Pinard: +@email{pinard@@iro.umontreal.ca}, +@uref{http://pinard.progiciels-bpi.ca/}, +Parts of Documentation/user/glossary*, +started internationalization stuff + +@item Niel Puttock: +Snippet editor and technical aid + +@item Eduardo Vieira: +NR work + +@item Francisco Vila: +NR work + +@item Michael Rasmussen: +Formatting + +@item Till Rettig: +NR work + +@item Carl Sorensen: +NR work + +@item Rune Zedeler: +Schumann example + +@end itemize +@end macro + + + +@macro supportPrevious + + +@itemize + +@item Anthony Fok: +@email{foka@@debian.org}, +Debian package: @file{debian/*} + +@item Chris Jackson: +@email{chris@@fluffhouse.org.uk}, +Emacs mode indentation + +@item Heikki Junes: +@email{heikki.junes@@hut.fi}, +Major emacs and vim-mode updates + +@item David Svoboda: +@email{svoboda@@cmu.edu}, +What-beat emacs module + +@end itemize +@end macro + + + +@macro translationsPrevious + + +@itemize + +@item Frédéric Chiasson: +French documentation translation + +@item Abel Cheung: + +@item David González: +Spanish glossary translation + +@item Nicolas Grandclaude: +@email{ngclaude@@123mail.org}, +French documentation translation + +@item Damien Heurtebise: + +@item Matthieu Jacquot: + +@item Bjoern Jacke: +@email{bjoern.jacke@@gmx.de}, +German glossary translation + +@item Neil Jerram: +@email{nj104@@cus.cam.ac.uk}, +Glossary translation + +@item Heikki Junes: +@email{heikki.junes@@hut.fi}, +Finnish translation + +@item Nicolas Klutchnikoff: + +@item Tineke de Munnik: +@email{tdm@@dds.nl}, +Dutch website translation + +@item Jean-Charles Malahieude: +@email{lolyfan@@wanadoo.fr}, +French translation of messages, website and documentation + +@item John Mandereau: +@email{john.mandereau@@free.fr}, +French translation of messages, website and documentation + +@item Tineke de Munnik: +@email{tdm@@dds.nl}, +Dutch website translation + +@item Steven Michael Murphy: + +@item Gauvain Pocentek: +@email{gauvainpocentek@@yahoo.fr}, +French website translation + +@item Till Rettig: +German translation + +@item Ludovic Sardain: +@email{ludovicsardain@@gmail.com}, +French documentation translation + +@item Yoshiki Sawada: +Japanese translation + +@item Clytie Siddall: + +@item August S. Sigov: +@email{august@@infran.ru}, +Russian translation + +@item Roland Stigge: + +@item Francisco Vila: +Spanish translation + +@item Olcay Yıldırım: + +@end itemize +@end macro + + diff --git a/Documentation/es/web/community.itexi b/Documentation/es/web/community.itexi new file mode 100644 index 0000000000..b193e58b65 --- /dev/null +++ b/Documentation/es/web/community.itexi @@ -0,0 +1,938 @@ +@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 Comunidad +@unnumbered Comunidad + + +@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 +
irc name: + + + + +
+ + +@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 + +@divClass{column-center-top} +@subheading We need you! + +The LilyPond development team is quite small; we really want to +get more people involved. Please consider helping your fellow +LilyPond users by contributing to development! + +Even working on small tasks can have a big impact: taking care +of them let experienced developers work on advanced tasks, instead +of spending time on those simple tasks. + +@divEnd + + +@divClass{column-left-top} +@subheading Simple tasks + +@divClass{keep-bullets} + +@itemize +@item +Mailing list support: answer questions from fellow users. + +@item +Bug reporting: help users create proper @ref{Bug reports}, and aid +the Bug Team in handling @rcontrib{Issues}. + +@item +Documentation: small changes can be proposed by following the +guidelines for @rcontrib{Documentation suggestions}. + +@item +LilyPond Snippet Repository (LSR): create and fix snippets. See +@rcontrib{Adding and editing snippets}. + +@item +Discussions, reviews, and testing: the developers often ask for +feedback about new documentation, potential syntax changes, and +testing new features. Please contribute to these discussions! + +@end itemize + +@subheading Moderate tasks + +@warning{These jobs generally require that you have the program +and documentation source files, but do not require a full +development environment. See @rcontrib{Starting with git}.} + +@itemize +@item +Documentation: see +@rcontrib{Documentation work}, and +@rcontrib{Building documentation without compiling LilyPond}. + +@item +Website: the website is built from the normal documentation +source. See the info about documentation, and also +@rcontrib{Website work}. + +@item +Translations: see @rcontrib{Translating the documentation}, and +@rcontrib{Translating the website}. + +@end itemize + + +@subheading Complex tasks + +@warning{These jobs generally require that you have the source +code and can compile LilyPond. See @rcontrib{Starting with git}, +and @rcontrib{Compiling LilyPond}.} + +We suggest that new contributors using Windows use a virtual +machine to run @emph{lilybuntu}. See +@rcontrib{Using a Virtual Machine to Compile LilyPond}. + +@itemize +@item +Bugfixes, new features: the best way to begin is to join the +Frogs, and read @rcontrib{Programming work}. + +@end itemize + +@divEnd +@divEnd + + +@divClass{column-right-top} +@subheading Projects + +@subsubheading Frogs + +Website and mailist: @uref{http://frogs.lilynet.net} + +The Frogs are ordinary LilyPond users who have chosen to get +involved in their favorite software's development. Fixing bugs, +implementing new features, documenting the source code: there's a +lot to be done, but most importantly: this is a chance for +everyone to learn more about LilyPond, about Free Software, about +programming... and to have fun. If you're curious about any of +it, then the word is: @emph{Join the Frogs!} + + + +@help{not active yet; either comment out or begin these projects +before 2.14} + +@subsubheading Grand LilyPond Input Syntax Standardization + +Website and mailist: TODO + +GLISS will stabilize the (non-tweak) input syntax for the upcoming +LilyPond 3.0. After updating to 3.0, the input syntax for +untweaked music will remain stable for the foreseeable future. + +We will have an extensive discussion period to determine the final +input specification. + +@subsubheading Grand Organizing Project + +Website and mailist: TODO + +GOP is our big recruiting drive for new contributors. + +@divEnd + + +@ignore +@divClass{column-center-bottom} +@subheading Interested? + +@divEnd +@end ignore + + +@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??} + +Commented out pending a real fix +@ignore + +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} + +@end ignore + +@divEnd + + +@divClass{column-right-top} +@subheading Contributor's Guide + +LilyPond development is a fairly complicated matter. LilyPond is +a large, (mostly) stable project. In order to help new +contributors, and to keep the whole system (mostly) stable, we +have written a manual for contributors. + +@warning{This manual is not intended to be read sequentially; new +contributors should only read the sections which are relevant to +them. For more information about different jobs, see +@ref{Help us}.} + +@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, 500 kb)} + +@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-top} +@subheading Frogs: new contributors + +The Frogs are a collection of new contributors being mentored in +how to @qq{eat} (fix) bugs and add new features to LilyPond. +Programmers unfamiliar with LilyPond are encouraged to send +patches to the Frogs first for initial discussion and +encouragement. + +Website and mailist: @uref{http://frogs.lilynet.net} + +@divEnd + +@divClass{column-right-bottom} +@subheading Regression tests + +@divClass{keep-bullets} +@itemize + +@item @uref{../../input/regression/collated-files.html, Regression tests}: +This release's tests. (also in +@uref{../input/regression/collated-files.pdf, pdf}) + +@item @uref{../../input/regression/musicxml/collated-files.html, +MusicXML Regression tests}: +This release's MusicXML tests. (also in +@uref{../input/regression/musicxml/collated-files.pdf, pdf}) + +@item @uref{http://lilypond.org/test, Archive of regression tests}: +Comparisons between versions. + +@end itemize +@divEnd +@divEnd + +@node Authors +@unnumberedsec Authors + +@help{Under construction; this is not an accurate list!} + + +@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-top} +@subheading Current Contributors + +@divClass{keep-bullets} +@subsubheading Programming + +@coreCurrent + +@subsubheading Font + +@fontCurrent + +@subsubheading Documentation + +@docCurrent + +@subsubheading Support + +@supportCurrent + +@subsubheading Translation + +@translationsCurrent + +@divEnd +@divEnd + + +@divClass{column-center-bottom} +@subheading Previous Contributors + +@divClass{keep-bullets} +@subsubheading Programming + +@corePrevious + +@subsubheading Font + +@fontPrevious + +@subsubheading Documentation + +@docPrevious + +@subsubheading Support + +@supportPrevious + +@subsubheading Translation + +@translationsPrevious + +@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-front.itexi + +@include web/news.itexi + + diff --git a/Documentation/es/web/download.itexi b/Documentation/es/web/download.itexi new file mode 100644 index 0000000000..2a1f62ec84 --- /dev/null +++ b/Documentation/es/web/download.itexi @@ -0,0 +1,549 @@ +@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 Descarga +@unnumbered Descarga + +@divClass{heading-center} +@heading Descargas para LilyPond @versionStable + +@divEnd + +@warning{LilyPond es un sistema de grabado musical @strong{basado en +texto}; es más parecido a un lenguaje de programación que a un +programa gráfico de edición de partituras. Antes de descargar +LilyPond le rogamos que lea lo que tenemos que decirle acerca de +nuestra @ref{Entrada de texto}.} + +@divClass{column-left-top} +@subheading Para usuarios + +@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 Para desarrolladores + +@itemize + +@item +@ref{Código fuente}: +para mantenedores de paquetes + +@item +@ref{Descargas antiguas}: +versiones anteriores + +@item @ref{Desarrollo}: +última versión de desarrollo + +@end itemize +@divEnd + + +@divClass{column-center-bottom} + +@subheading Licencia del Software + +LilyPond está publicado bajo la +@ref{GPL, Licencia General Pública de GNU}. +@divEnd + + +@divClass{color1} + +@subheading Patrocinadores + +Nuestro agradecimiento a @uref{http://www.vt.edu/, Virgina Tech} y a +@uref{http://www.linuxaudio.org/, linuxaudio.org} por patrocinar +nuestro ancho de banda. + +@sourceimage{VTlogo_ITF,,,} +@sourceimage{lao_banner_06_on_white_demo,,,} + +@subheading Legalismos + +@divClass{legal} +Se reconoce el copyright y la marca registrada de todos los logotipos +e imágenes de productos. + +@logoLegalLinux + +@logoLegalFreeBSD + +@logoLegalMacOSX + +@logoLegalWindows + +@divEnd +@divEnd + + +@divClass{hide} +@menu +* Unix:: +* MacOS X:: +* Windows:: +* Código fuente:: +* Descargas antiguas:: +* GPL:: +@end menu +@divEnd + + +@node Unix +@unnumberedsec Unix + +@divClass{column-center-top} +@subheading ¿Paquetes genéricos, o paquetes específicos de la distribución? + +Muchas distribuciones incluyen a LilyPond dentro de su sistema normal +de paquetes. Estas versiones son más fáciles de instalar y +desinstalar que los paquetes genéricos, pero pueden ser más antiguas. +Si quiere utilizar nuestros paquetes genéricos, desinstale la versión +oficial de su sistema utilizando el gestor normal de paquetes para su +distribución. Consulte la documentación de su distribución sobre cómo +usar su gestor de paquetes. + +@divEnd + + +@divClass{column-left-top} +@subheading Paquetes genéricos + +@subsubheading Descarga + +@itemize + +@item +@sourceimage{logo-linux,,,} +@downloadStableLinuxNormal +(si no está seguro, utilice éste) + +@item +@sourceimage{logo-linux,,,} +@downloadStableLinuxBig + +@item +@sourceimage{logo-linux,,,} +@downloadStableLinuxPPC + +@item +@sourceimage{logo-freebsd,,,} +@downloadStableFreeBSDNormal + +@item +@sourceimage{logo-freebsd,,,} +@downloadStableFreeBSDBig + +@end itemize + + +@subsubheading Instalación + +En la línea de órdenes, escriba: + +@example +cd RUTA-DEL-DIRECTORIO-DE-DESCARGA +sh lilypond-@versionStable{}-SISTEMA-OPERATIVO.sh +@end example + +@subsubheading Desinstalación + +En la línea de órdenes, escriba: + +@example +uninstall-lilypond +@end example + +@divEnd + + +@divClass{column-right-top} +@subheading Paquetes específicos de la distribución + +Utilice el gestor de paquetes de su distribción para instalar o +actualizar a estas versiones. + +@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 Legalismos + +@divClass{legal} Se reconoce el copyright y las marcas registradas de +todos los logotipos e imágenes de producto. + +@logoLegalLinux + +@logoLegalFreeBSD + +@divEnd +@divEnd + + +@node MacOS X +@unnumberedsec MacOS X + +@divClass{column-left-top} +@subheading Paquetes + +@subsubheading Descarga + +@itemize + +@item +@sourceimage{logo-macosx,,,} +@downloadStableDarwinNormal +Para procesadores Intel (si no está seguro, utilice éste). + +@item +@sourceimage{logo-macosx,,,} +@downloadStableDarwinPPC +Para CPUs G3 y G4 (ordenadores Apple antiguos). + +@end itemize + +@subsubheading Instalación + +Haga dobe click sobre el archivo descargado. Después, arrástrelo a +donde quiera. + +@subsubheading Desinstalación + +Borre la carpeta LilyPond.app. + +@divEnd + + +@divClass{column-right-top} +@subheading Ejecución desde la línea de órdenes + +@warning{Si está satisfecho con el GUI, ignore estas instrucciones.} + +@ignore +FIXME: I had one report that we don't need this stuff; will delete +after confirmation. -gp + +@subsubheading Uso de guiones Python sobre 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 sobre la línea de órdenes + +La forma más práctica de procesar proyectos de lilypond es mediante la +preparación de guiones @qq{de apoyo} hechos por usted mismo. + +@enumerate + +@item +Cree un directorio apra guardar estos guiones, + +@example +mkdir -p ~/bin +cd ~/bin +@end example + + +@item +Cree un archivo llamado @command{lilypond} que contenga + +@c @hel p 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{en general, @var{DIR} será @code{/Applications/}} + + +@item +Cree archivos similares @command{lilypond-book}, @command{convert-ly}, +y cualesquiera otros que vara a utilizar, sustituyendo la parte +@command{bin/lilypond} con @command{bin/convert-ly} (u otro nombre de +programa). + + +@item +Haga el archivo ejecutable, + +@example +chmod u+x lilypond +@end example + + +@item +Ahora, añada este directorio a su ruta de ejecución. Modifique (o +cree) un archivo llamado @code{.profile} en su directorio principal de +forma que contenga + +@example +export PATH=$PATH:~/bin +@end example + +Este archivo debe terminar en una línea vacía. + +@end enumerate + + +@subsubheading Invocar los guiones individuales + +Los guiones (como @command{lilypond-book}, @command{convert-ly}, +@command{abc2ly} e incluso el propio @command{lilypond}) están +incluidos dentro del archivo @code{.app} para MacOS@tie{}X. + +Los guiones también se pueden lanzar desde la línea de órdenes +mediante su invocación directa: + +@example +@var{path/to}/LilyPond.app/Contents/Resources/bin/lilypond +@end example + +Lo mismo vale para el resto de los guiones de ese directorio, como +@command{lilypond-book} y @command{convert-ly}. + +@divEnd + + +@divClass{column-center-bottom} +@subheading Legalismos + +@divClass{legal} +Se reconoce el copyright y la marca registrada de todos los logotipos +e imágenes de productos. + +@logoLegalMacOSX + +@divEnd +@divEnd + + + +@node Windows +@unnumberedsec Windows + +@divClass{column-left-top} +@subheading Paquetes + +@subsubheading Descarga + +@itemize + +@item +@sourceimage{logo-windows,,,} +@downloadStableWindows +Para Windows ME, NT, 2000, XP, Vista y Windows 7. + +@end itemize + +@subsubheading Instalación + +@enumerate + +@item +Localice el archivo descargado y haga doble click sobre él para +arrancar el instalador. Apareceá una ventana con el título @qq{Abrir +programa: advertencia de seguridad}, pulse sobre Ejecutar para +continuar. + +@item +Aparecerá el Acuerdo de Licencia; léalo detenidamente y pulse sobre el +botón Siguiente si lo acepta. + +@item +Es preferible que deje la carpeta de destino a su ajuste +predeterminado; en caso contrario, elija una carpeta distinta y pulse +sobre el botón Siguiente. + +@item +A continuación está la ventana de Opciones de Instalación, deje las +tres opciones marcadas, porque necesitará tenerlas todas +instaladas. Pulse sobre el botón Siguiente. + +@item +A continuación comienza la instalación; espere un minuto o menos a que +se complete la instalación. Hay un botón de Mostrar Detalles que si +se pulsa mostrará todos los archivos que se instala y dónde lo hacen, +nada que le deba interesar necesariamente. Pulse sobre el botón +Finalizar. + +@item +Lilypond está instalado. + +@end enumerate + +@subsubheading Desinstalación + +Hay dos rutas a la desinstalación: + +@enumerate + +@item +Seleccione Uninstall del menú Lilypond del botón Inicio + +@item +Abra Instalar o Desinstalar Programas del panel de control, localice a +Lilypond y pulse sobre el botón Desinstalar. + +@end enumerate + +@divEnd + + +@divClass{column-right-top} +@subheading Ejecución desde la línea de órdenes + +@warning{Si le satisface el interfaz gráfico, ignore estas +instrucciones.} + +@c @hel p{don't know} + +@divEnd + + +@divClass{column-center-bottom} +@subheading Legalismmos + +@divClass{legal} +Se reconoce el copyright y la marca registrada de todos los logotipos +e imágenes de productos. + +@logoLegalWindows + +@divEnd +@divEnd + + + +@node Código fuente +@unnumberedsec Código fuente + +@warning{@strong{No} recomendamos que intente compilar LilyPond por sí +mismo; casi todas las necesidades del usuario se satisfacen mejor con +la versión precompilada.} + +@divClass{column-left-bottom} +@subheading Tarball del código fuente + +@downloadStableSource{} + +Para ver un amplio listado de todas las versiones (antiguas y +modernas), consulte nuestra +@uref{http://download.linuxaudio.org/lilypond/binaries/, página de +descarga}. + +@divEnd + +@divClass{column-right-bottom} +@subheading Instrucciones de compilación + +Las instrucciones se encuentran desarrolladas dentro de +@rcontrib{Compiling LilyPond}. + +@divEnd + + +@node Descargas antiguas +@unnumberedsec Descargas antiguas + +@divClass{column-center-top} +@subheading Todas las versiones + +Para ver un amplio listado con todas las versiones (antiguas y +modernas), consulte nuestra +@uref{http://download.linuxaudio.org/lilypond/binaries/, página de +descarga}. + +@divEnd + + +@node GPL +@unnumberedsec GPL + +@divClass{column-center-top} +@subheading Licencia del Software + +GNU LilyPond está publicado bajo la Licencia General Pública de GNU. +Se ofrece una introducción a esta licencia y a nuestros motivos para +haberla elegido, en @ref{Freedom}. + +@divEnd + +@divClass{column-center-bottom} +@subheading Licencia General Pública de GNU + +@include gpl.itexi + +@divEnd + + + diff --git a/Documentation/es/web/introduction.itexi b/Documentation/es/web/introduction.itexi new file mode 100644 index 0000000000..2b929a5e54 --- /dev/null +++ b/Documentation/es/web/introduction.itexi @@ -0,0 +1,1073 @@ +@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 Introducción +@unnumbered Introducción + +@divClass{column-center-top} +@subheading Nuestras metas + +@imageFloat{flat-design,png,right} + +El origen de la inspiración para LilyPond está en dos músicos que se +encontraban molestos con el insípido y aburrido aspecto de la música +impresa mediante ordenador. Todo músico prefiere leer música impresa +de manera hermosa, así que ¿por qué no iban a poder los programadores +escribir software para producir partituras mejor impresas? + +Este programa hace simplemente eso: imprime música dentro de las +mejores tradiciones del grabado clásico con un mínimo de +complicaciones. No pierda tiempo en hacer ajustes finos del +espaciado, cambiar símbolos de sitio, o dando forma a las ligaduras. +¡Impresione a sus amigos y colegas con partituras espectaculares! +@divEnd + +@divClass{column-left-top} +@subheading ¿Por qué utilizar LilyPond? + +@itemize + +@item +@ref{Posibilidades}: ¿Qué puede hacer LilyPond? + +@item +@ref{Ejemplos}: ¡Quiero ver música! + +@item +@ref{Libertad}: LilyPond es Software Libre. + +@item +@ref{Trasfondo}: Nociones de nuestra estética computacional. + +@end itemize +@divEnd + +@divClass{column-right-top} +@subheading ¿Quién lo usa? + +@itemize + +@item +@ref{Producciones}: Usos de LilyPond en el mundo real. + +@item +@ref{Testimonios}: ¿Qué dice la gente? + +@end itemize +@divEnd + +@divClass{column-center-bottom} +@subheading ¿Por qué no utilizar LilyPond? + +@itemize + +@item +@ref{Entrada de texto}: ¡¿Escriben música como @emph{texto}?! + +@item +@ref{Entornos mejorados}: Otras formas de trabajar con LilyPond. + +@end itemize +@divEnd + + +@divClass{hide} +@menu +* Posibilidades:: ¿Qué puede hacer LilyPond? +* Ejemplos:: ¡Quiero ver música! +* Libertad:: La libertad y la GPL. +* Trasfondo:: Estética computacional. +* Producciones:: Uso de LilyPond en el mundo real. +* Testimonios:: ¿Qué dice la gente de él? +* Entrada de texto:: ¡¿Escriben música como texto?! +* Entornos mejorados:: Otras formas de trabajar con LilyPond. +@end menu +@divEnd + + + +@node Posibilidades +@unnumberedsec Posibilidades + +(En construcción) + +@subheading ¿Por qué cambiarse a LilyPond? + + +@subsubheading Excelencia en grabado clásico + +@imageFloat{flat-design,png,right} + +El propósito de LilyPond es que lo usemos para producir partituras +elegantes que sean fáciles de leer. La comunidad de desarrolladores +de LilyPond ha empleado miles de horas en desarrollar un programa de +grabado musical que produce como resultado música impresa de forma +hermosa. Todos los ajustes de estilo de LilyPond, el diseño de las +fuentes y los algoritmos se han inspirado en la mejor música grabada a +mano. La salida de LilyPond tiene el mismo aspecto robusto, +equilibrado y elegante que las partituras clásicas mejor grabadas. +Todo esto se explica con detalle en nuestro @ref{Ensayo}. + + +@subsubheading Menos complicaciones + +Pierda menos tiempo en los ajustes de la salida; LilyPond consigue el +formateado más correcto desde el principio. Determina el espaciado +por sí solo y parte las líneas y las páginas de forma que ofrece una +disposición compacta y uniforme. Los choques entre la letra de las +canciones, las notas y los acordes se resuelven, y las ligaduras y las +barras se inclinan ¡automáticamente! + + +@subsubheading Entrada basada en texto + +LilyPond toma una entrada en texto normal, que podemos elaborar en +nuestro editor de texto de preferencia, de forma rápida y cómoda. Se +acabaron los enredos con el ratón. La entrada de texto contiene toda +la información, de manera que no hay necesidad de recordar complejas +secuencias de instrucciones. Tan sólo grabe un código de entrada para +que sirva como referencia futura. + + +@subsubheading Accesibilidad + +La entrada basada en texto también hace posible la escritura de +partituras para usuarios con deficiencias físicas. Los usuarios con +alguna dificultad manual que no pueden teclear o manejar un ratón de +ordenador pueden usar software de reconocimiento de voz para editar +los archivos de LilyPond. Incluso las personas totalmente ciegas +pueden usar lectores de pantalla para escribir los archivos de +LilyPond (una tarea imposible en los programas de edición de +partituras basados en gráficos). + + +@subsubheading Combinar música y texto + +@imageFloat{lilypond-book,png,right} + +Inserte fragmentos de música dentro de textos sin cortar y pegar +imágenes. Integre música dentro de LaTeX o HTML de manera fácil, o +añada música a los documentos de OpenOffice.org con ooolilypond. + + + +@subsubheading Software libre + +¡LilyPond se puede descargar sin coste! Sí: es gratis. Obténgalo de +la página de descarga. + +También es software libre, como la libertad de expresión. Se ofrece +con el código fuente con el permiso para modificarlo y copiarlo. Así +pues, ¿está cansado de algún fallo o suplica una determinada +funcionalidad? tan sólo añádala por sí mismo, o pague a alguien para +que lo haga. + + +@subsubheading Diseño ampliable + +Todos los ajustes se pueden modificar para que se combinen con su +gusto tipográfico personal. Si eso no es suficiente, siempre nos +queda el lenguaje de guiones incorporado, un dialecto del potente +lenguaje LISP. Todos los ajustes, variables y funciones están +documentados en el completo manual de referencia del programa. + + +@subsubheading Soporte excelente + +LilyPond funciona en todas las plataformas populares: Linux, MacOS X y +Windows. LilyPond viene con una completa documentación y cientos de +archivos de ejemplo. Existe una activa comunidad de usuarios +dispuesta a responder dudas y cuestiones en la lista de distribución +de correo de usuarios de Lilypond, mientras que el equipo de +desarrollo se asegura de que los problemas se resuelven con prontitud. + + +@divClass{column-center-bottom} +@subheading ¿Ahora qué? + +¿Aún no está convencido? Eche un vistazo a algunos @ref{Ejemplos} +interesantes. Si ya está decidido a probar LilyPond, en primer lugar +infórmese de nuestra @ref{Entrada de texto}. +@divEnd + + + +@node Ejemplos +@unnumberedsec Ejemplos + +LilyPond es una herramienta potente y flexible para tareas de grabado +musical de todo tipo. Explore libremente nuestra galería de ejemplos +e ¡inspírese! + +@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 Música Clásica + +Esta pieza de órgano de J.S. Bach es un proyecto bastante típico de +grabado con LilyPond. + +@exampleImage{bach-bwv610} +@newsEnd + +@newsItem +@subsubheading Notación compleja + +Este ejemplo procedente de las @emph{Goyescas} de Enrique Granados +muestra algunas de las posiblidades más avanzadas de la composición +tipográfica, como las barras en ángulo, plicas de pentagrama cruzado y +líneas de seguimiento de voces. + +@exampleImage{granados} +@newsEnd + +@newsItem +@subsubheading Música antigua + +Lilypond también contempla distintos tipos de notación antigua, como +este pasaje de canto gregoriano. + +@exampleImage{ancient-headword} +@newsEnd + +@newsItem +@subsubheading Música moderna + +Los compositores contemporáneos encuentran que Lilypond es adecuado +para la impresión de notación inusual. He aquí un extracto de la obra +@emph{Cáry}, de Trevor Bača, para flauta baja sola. + +@exampleImage{cary} +@newsEnd + + +@newsItem +@subsubheading Creación flexible y eficiente de material de interpretación + +Se pueden crear distintos materiales de lectura a partir del mismo +código fuente. He aquí un extracto de la realización de +@uref{http://nicolas.sceaux.free.fr/, Nicolas Sceaux} de @emph{Giulio +Cesare} de Haendel, en partitura completa, reducción para piano y voz, +y una particella de violín. + +@exampleImage{sesto-full} + +@exampleImage{sesto-piano} + +@exampleImage{sesto-violin} + +@newsEnd + +@newsItem +@subsubheading Tablatura + +Lilypond contempla la notación de cifra para guitarra, que se puede +personalizar para adaptarla a cualquier instrumento que lea de +tablatura. La pauta de tablatura se genera automáticamente a partir +de las notas que se escriben para el pentagrama normal. + +@exampleImage{tab-example} +@newsEnd + +@newsItem +@subsubheading Gráficos de Schenker + +La salida estándar se puede modificar de forma muy profunda. Aquí, +alguien ha creado un impresionante análisis schenkeriano. + +@exampleImage{bach-schenker} +@newsEnd + +@newsItem +@subsubheading Música vocal + +Lilypond es excelente para todo tipo de música vocal, desde himnos de +música sacra hasta óperas. Presentamos a continuación un motete +medieval con unos requisitos ligeramente inusuales. La voz de tenor +está escrita en un compás distinto a las otras pero debe alinearse +como si estuviera en el mismo compás. Lilypond trata esta situación +con suma elegancia. Observe también los incipit con las claves en el +estilo de la edición Vaticana, las plicas barradas que indican notas +repetidas, y los corchetes de ligadura por encima de ciertos grupos de +notas. + +@exampleImage{aucun-snippet} +@newsEnd + +@newsItem +@subsubheading Aplicaciones para la educación + +Lilypond está muy indicado también para aplicaciones educativas. He +aquí un ejemplo de un sencillo ejercicio de contrapunto. + +@exampleImage{theory} +@newsEnd + +@newsItem +@subsubheading Música pop + +Es sencillo crear hojas guía de acordes en cifrado americano para +música pop con melodía, letra, nombres de acordes y diagramas de +posiciones de acorde. En este ejemplo vemos algunos de los diagramas +de posiciones predefinidas, pero se pueden personalizar profundamente +para cumplir con casi cualquier situación. + +@exampleImage{chart} +@newsEnd + +@newsItem +@subsubheading Proyectos grandes + +Lilypond es excelente para proyectos grandes como óperas u obras para +orquesta sinfónica, también. Además, la entrada basada en texto +proporciona una mayor accesibilidad (este ejemplo ha sido aportado por +Hu Haipeng, un compositor ciego). + +@exampleImage{orchestra} +@newsEnd + + +@divClass{column-center-bottom} +@subheading ¿Ahora qué? + +¿Aún no está convencido? LilyPond es software libre, le concede a +usted, el usuario, la @ref{Libertad}. Si ya está decidido a probar +LilyPond, lea en primer lugar lo que tenemos que decirle sobre la +@ref{Entrada de texto}. +@divEnd + + +@node Libertad +@unnumberedsec Libertad + +@divClass{column-center-top} +@subheading Software libre + +@uref{http://www.gnu.org/, GNU} LilyPond está escrito y mantenido por +una comunidad de entusiastas. Está publicado bajo la @ref{GPL, +Licencia General Pública de GNU} y la @ref{FDL, Licencia de +Documentación Libre de GNU}, danto a todos la libertad de arreglar, +modificar y ampliar el programa. ¡Crear música hermosa no debería +requerir cientos de euros en software! +@divEnd + + +@c @divClass{column-left-top} +@divClass{color2} +@divClass{keep-bullets} +@subheading ¿Cuáles son los beneficios para los usuarios? + +@itemize + +@item +Sin coste: ¡descárguelo y pruébelo! ¿Qué puede perder? + +@item +Compartir: si le gusta el programa ¡pase una copia a sus amigos, +profesores, alumnos y colegas! + +@item +Disponibilidad de la fuente: si tiene curiosidad acerca de cómo +LilyPond crea algún tipo de notación musical, puede ver exactamente +cómo está hecha. + +@item +Ampliable: usted puede añadir posibilidades, corregir errores y +cambiar el funcionamiento. Si no es un programador, puede contratar a +alguien para que haga estas tareas. + +Esto puede parecer poco atractivo para músicos ocasionales, pero la +capacidad de expandir el software puede ser muy valiosa para los +compositores serios, empresas y académicos. + +@item +Seguridad para el futuro: si una empresa comercial va a la quiebra, +¿qué le ocurre a cualquier música electrónica que dependa de sus +productos? Esto no es un problema con LilyPond; incluso si todo el +equipo de desarrollo lo abandonara (algo extremadamente improbable), +el programa aún seguiría estando disponible de forma legal para su +copia, modificaciones y distribución. + + +@end itemize + +@divEnd +@divEnd + + +@c @divClass{column-right-top} +@divClass{color3} +@divClass{keep-bullets} +@subheading ¿Por qué los desarrolladores de LilyPond @qq{regalan} su trabajo sin pedir nada a cambio? + +Casi todos nosotros vemos el desarrollo de LilyPond como un hobby o un +trabajo voluntario. Así pues, la pregunta es realmente @qq{¿por qué +las personas se prestan voluntarias?} + +@itemize + +@item +Por diversión: el trabajo en busca de una meta puede ser divertido, +¡en especial cuando trabajas en equipo! + +@item +Metas comunes: todos nosotros queremos partituras con buen aspecto, +pero son pocos los que tienen la experiencia (y ninguno tiene tiempo) +para crear un programa que pueda manejar todas las situaciones. +Trabajando en equipos (una persona mejora el código que traza las +barras de corchea, otra mejora la forma de las ligaduras y un terecero +escribe documentación explicando cómo utilizar estas posibilidades) +podemos alcanzar nuestra meta con tan sólo una fracción del esfuerzo +individual. + +@item +La @qq{cultura del regalo}: el movimiento del Software Libre (o de +@qq{fuente abierta}) ha creado muchos proyectos geniales de sofware, +como @uref{http://kernel.org/, GNU/Linux}, +@uref{http://www.getfirefox.com/, Mozilla Firefox} y el juego +@uref{http://www.wesnoth.org/, Battle for Wesnoth}. Después de +haberse visto beneficiados por estos proyectos, algunos +desarrolladores desean @qq{devolver} algo a la comunidad. + +@item +Experiencia laboral: las contribuciones a proyectos de código abierto +son una magnífica forma de practicar la programación, la escritura de +documentación o el diseño. Esta experiencia ha ayudado a muchos +programadores a encontrar trabajo en empresas o en universidades. + + +@end itemize + +@divEnd +@divEnd + + +@divClass{column-center-bottom} +@subheading Y ahora ¿qué? + +¿Aún no está convencido? Lea nuestro extenso ensayo sobre nuestra +filosofía del grabado en @ref{Trasfondo}. Si ya está decidido a +probar LilyPond, en primer lugar lea lo que hemos escrito sobre la +@ref{Entrada de texto}. +@divEnd + + +@node Trasfondo +@unnumberedsec Trasfondo + +@divClass{column-center-top} +@subheading Ensayo sobre el trasfondo + +Tenemos un amplio ensayo que describe la estética computacional: el +arte de crear belleza con un ordenador. + +Si tan sólo quiere una introducción rápida a LilyPond, leer todo el +material que constituye el ensayo podría ser demasiado. Si quiere +leerlo ahora, continúe hacia @ref{Essay}. +@divEnd + +@divClass{column-center-bottom} +@subheading Y ahora ¿qué? + +¿Aún no está convencido? Lea algo acerca de las @ref{Producciones} y +partituras de algunos de nuestros usuarios. Si ya se ha decidido a +probar LilyPond, en primer lugar lea algo sobre nuestra @ref{Entrada +de texto}. +@divEnd + + +@node Producciones +@unnumberedsec Producciones + +@divClass{column-left-top} +@subheading Conciertos + +La música grabada con Lilypond se ha utilizado en interpretaciones y +actuaciones por todo el mundo. Algunos titulares: + +@divClass{keep-bullets} +@itemize + +@item +@emph{Affaire Étrangère}, ópera de Valentin Villenave, con libreto de +Lewis Trondheim, estrenada el 1 de febrero de 2009 en +@uref{http://www.opera-montpellier.com/, L'Opéra Montpellier}. + +@item +La interpretación de +@uref{http://www.mercurybaroque.org/02/02109.aspx, Mercury Baroque} de +@emph{Armide} de Lully, 15 y 16 de mayo de 2009, en Houston, Texas +(tipografía de @uref{http://nicolas.sceaux.free.fr/, Nicolas Sceaux}). + +@item +Extractos instrumentales de @emph{Hippolyte et Aricie} de Rameau en la +iglesia de St. James en Manhattan, el 8 de mayo de 2009, por Frederick +Renz y su conjunto @uref{http://www.earlymusicny.org/, Early Music New +York} (realización tipográfica de Nicolas Sceaux). + +@end itemize +@divEnd + +@divEnd + + +@divClass{column-right-top} +@subheading Partituras publicadas + +@divClass{keep-bullets} +@itemize + +@item +El @uref{http://www.mutopiaproject.org/index.html, Proyecto Mutopia} +incluye más de 1500 partituras de música clásica para su libre +descarga, y es el principal escaparate de partituras de LilyPond. + +@item +@uref{http://www.adoromusicpub.com/, Adoro Music Publishing}, +partituras de música sacra de alta calidad, disponibles para su +descarga inmediata o en el formato tradicional de papel. + +@item +@uref{http://theshadylanepublishing.com/, The Shady Lane Publishing}, +una @qq{micro editorial musical} cuya meta es promover una nueva forma +de economía más cercana a los músicos y amantes de la música. + +@end itemize + +@divEnd + +@divEnd + + +@divClass{column-center-bottom} +@subheading Y ahora ¿qué? + +¿Aún no está convencido? Lea algunos de los @ref{Testimonios} de +nuestros usuarios. Si ya tiene decidido probar LilyPond, en primer +lugar infórmese sobre nuestra @ref{Entrada de texto}. +@divEnd + + +@node Testimonios +@unnumberedsec Testimonios + +@divClass{testimonial-item} +@imageFloat{carter-brey,jpg, right} +@subsubheading @uref{http://nyphil.org/meet/orchestra/index.cfm?page=profile&personNum=7, Carter Brey}, primer cello de la Filarmónica de Nueva York + +@qq{... He escrito un par de piezas para violoncello solista que he +impreso con LilyPond y que voy a enviar a Schirmer para su +publicación. ¡Puedo apostar a que su grabado no será ni la mitad de +bueno que el mío!} +@divEnd + + +@divClass{testimonial-item} +@imageFloat{orm-finnendahl,jpg, left} +@subsubheading @uref{http://icem-www.folkwang-hochschule.de/~finnendahl/, Orm Finnendahl}, profesor de composición, Conservatorio Superior de Friburgo + +@qq{Aún cuando no domino [LilyPond] todavía, estoy @strong{muy} +impresionado. Usé el programa para digitalizar un motete de Josquin +Desprez en notación mensural y no cabe duda de que lilypond ¡se lleva +por delante a otros programas de notación en cuanto a velocidad, +facilidad de uso y apariencia de los resultados!} +@divEnd + + +@divClass{testimonial-item} +@imageFloat{darius-blasband,jpg, right} +@subsubheading Darius Blasband, compositor (Bruselas, Bélgica) + +@qq{[...después del primer ensayo orquestal] obtuve numerosos +cumplidos sobre la calidad de las partituras. Lo que es incluso más +importante: mientras que LilyPond proporciona numerosas formas de +mejorar la apariencia de las partituras, lo que entregué a la orquesta +es básicamente la impresión en bruto, sin retocar.} +@divEnd + + +@divClass{testimonial-item} +@subsubheading Kieren MacMillan, compositor (Toronto, Canadá) + +@qq{Gracias y felicitaciones al equipo de desarrollo por su increíble +trabajo. Nunca he visto nada que se acerque al resultado que obtengo +con LilyPond; confío plenamente en que mis necesidades de publicación +musical serán satisfechas más allá de toda expectativa usando esta +genial aplicación. (...) básicamente, la impresión de LilyPond sin +retocar (...) se ve mejor que la mayoría de las publicaciones +"profesionales" más recientes con que las he comparado (p.ej., +prácticamente cualquier partitura de Warner Bros, e incluso muchas de +las más recientes de @q{las editoras antiguas}). (...)} + +@qq{¡¡¡Toma eso, Finale/Sibelius/Igor/lo que sea!!!} +@divEnd + + +@divClass{testimonial-item} +@subsubheading Chris Cannam, programador principal del proyecto @uref{http://www.rosegardenmusic.com/, RoseGarden}. + +@qq{Lilypond es, obviamente, King Kong [de la tipografía musical a lo +grande].} +@divEnd + + +@divClass{testimonial-item} +@subsubheading Chris Snyder, @uref{http://www.adoromusicpub.com/, Adoro Music Publishing} + +@qq{La forma en que se introduce la música para LilyPond me hace +pensar de una manera más musical -- ha habido veces en que me he +bloqueado sobre cómo decirle a Lily que imprima algo, sólo para darme +cuenta de que incluso si hiciera exactamente lo que el compositor +quería, la música sería confusa de leer. LilyPond me lo pone mucho +más fácil al trabajar en mi doble papel de editor y copista.} + +@qq{Llevo ustilizando exclusivamente LilyPond para mi negocio de +publicación recién inaugurado. Prácticamente sin excepción, todos los +compositores se han quedado boquiabiertos con la calidad del grabado +cuando se lo presentaba con las pruebas de su música previa a la +publicaicón. Me reservo parte del mérito de esto (empleo mucho tiempo +en trucar los resultados, especialmente las ligaduras, sobre todo en +los acordes), pero LilyPond me da unexcelente punto de partida, un +interfaz muy intuitivo, y la capacidad de modificar absolutamente +cualquier cosa si le quiero dedicar el tiempo necesario. Estoy +convencido de que ningún producto comercial se le acerca ni de lejos.} +@divEnd + + +@divClass{testimonial-item} +@subsubheading David Bobroff, trombón bajo, Orquesta Sinfónca de Islandia + +@qq{Creo que Lilypond es genial (...) cuanto más aprendo de LilyPond, +¡más me gusta!} +@divEnd + + +@divClass{testimonial-item} +@subsubheading Vaylor Trucks, intérprete de guitarra eléctrica (sí, @uref{http://www.allmanbrothersband.com/modules.php?op=modload&name=userpage&file=content&page_id=12, pariente de...}) + +@qq{Estoy súper-impresionado con LilyPond (...)} + +@qq{¡¡¡EL MEJOR PROGRAMA DE LA HISTORIA!!!} + +@qq{¡Muchísimas gracias a todos por vuestro duro trabajo y +dedicación!} +@divEnd + + +@divClass{testimonial-item} +@subsubheading @uref{http://nicolas.sceaux.free.fr/, Nicolas Sceaux}, colaborador de @uref{http://www.mutopiaproject.org/, Mutopia} + +@qq{Tenía una especie de relación pasión-odio con LilyPond. Pasión +porque la primera partitura que vi ¡era tan increíble! La descripción +de Lilypond se fundamenta en la belleza ¡esto es demasiada modestia! +(...) conforme LilyPond mejora continuamente y observo cómo se hacen +las cosas con Scheme, tengo cada vez menos frustraciones. De +cualquier forma, lo que quiero decir es: gracias por darnos LilyPond, +es realmente bueno.} +@divEnd + + +@divClass{testimonial-item} +@subsubheading @uref{http://www.troff.org/whoswho.html#werner, Werner Lemberg}, director de orquesta en el Teatro de Koblenz, Alemania, y destacado hacker de GNU. + +@qq{¡De cualquier manera, LilyPond hace un trabajo sensacional!} +@divEnd + + +@divClass{testimonial-item} +@subsubheading Paul Davis, desarrollador de @uref{http://jackaudio.org/, JACK} y @uref{http://www.ardour.org/, Ardour}. + +@qq{Creo que [LilyPond] es un programa increíble, y produce un +resultado realmente maravilloso. Después de haber leído una reseña +sobre él el año pasado, estuve dando la paliza a varios amigos míos +hablándoles de su potencial.} +@divEnd + + +@divClass{column-center-bottom} +@subheading Y ahora ¿qué? + +Lea lo que tenemos que decirle sobre nuestra @ref{Entrada de texto}. +@divEnd + + + +@node Entrada de texto +@unnumberedsec Entrada de texto + +@c TRANSLATORS: so far it's mostly from +@c http://lilypond.org/web/switch/howto + +@subheading @qq{Compilar} la música + +@imageClickable{nereid-shot-small,png, (pulse para ver una imagen más grande), +nereid-shot,png, right} + +LilyPond es un sistema @emph{compilado}: se ejecuta sobre un archivo +de texto que contiene las notas. El resultado se puede ver en la +pantalla o imprimirse. En cierto modo, LilyPond se parece más a un +lenguaje de programación que a los programas de edición gráfica de +partituras. + +No escribimos la música por el procedimiento de coger las notas de una +barra de herramientas gráfica y arrastrarlas a una partitura que se +refresca de forma dinámica; escribimos la música tecleando un texto. +Este texto es interpretado (o @qq{compilado}) por parte de LilyPond, +que a su vez produce una hermosa música impresa. + +Es posible que las personas acostumbradas a interfaces gráficos de +usuario tengan que aprender una forma de trabajo nueva, pero ¡los +resultados, sin duda alguna, merecen la pena! + +@warning{Presentamos aquí una panorámica de nuestro paradigma de +entrada de texto: ¡no es tan complicado como suena! No se preocupe +ahora por comprender todos y cada uno de los detalles de estos +ejemplos; nuestra documentación para principiantes se ocupa de todo +ello a un ritmo mucho más progresivo.} + + +@subsubheading La ele con la a, "La" + +Las notas se codifican mediante letras y números. Las instrucciones +especiales se introducen mediante barras invertidas. + +@imageFloat{text-input-1-annotate,png,center} +@imageFloat{text-input-1-output,png,center} + +Las alteraciones se hacen con nombres distintos: añada @code{-is} para +obtener un sostenido, y @code{-es} para un bemol (son los nombres de +las notas en holandés, pero están disponibles otros idiomas). +LilyPond averigua dónde hay que imprimir las alteraciones. + +@imageFloat{text-input-2-annotate,png,center} +@imageFloat{text-input-2-output,png,center} + + +@subsubheading Música pop + +Junte acordes y letra para obtener una hoja guía de acordes: + +@imageFloat{text-input-pop-annotate,png,center} +@imageFloat{text-input-pop-output,png,center} + + + +@subsubheading Particellas de orquesta + +El archivo de entrada contiene las notas de la pieza. La partitura y +las particellas se pueden hacer a partir de un solo archivo de +entrada. Así, un cambio en una nota siempre afecta tanto a las +particellas como a la partitura general. Para poder compartir las +notas, asignamos la música a una variable: + +@imageFloat{text-input-parts-both-annotate,png,center} + + +Esta variable se usa entonces en una sola parte instrumental (aquí +transportada, con los silencios agrupados): + +@imageFloat{text-input-parts-single-annotate,png,center} +@imageFloat{text-input-parts-single-output,png,center} + + +La misma variable se utiliza en la partitura general (aquí en tono de +concierto): + +@imageFloat{text-input-score-annotate,png,center} +@imageFloat{text-input-score-output,png,center} + + +@subsubheading Documentación para el principiante + +Nos damos cuenta de que muchos usuarios ven un poco extraña esta forma +de introducir la música. Por este motivo, hemos escrito una amplia +documentación de ayuda a los nuevos usuarios, comenzando con +@ref{Learning}. + +¡Le rogamos que lea el Manual de Aprendizaje antes de protestar por +posibles fallos en el programa! Con frecuencia, los usuarios noveles +creen que LilyPond no funciona, cuando de hecho está funcionando +exactamente tay y como está diseñado para hacerlo. + +@c @hel p{any suggestions for a picture here?} + + +@subsubheading Entornos de edición facilitados + +La preocupación de LilyPond está en primer lugar en la producción de +música tipografiada con la máxima calidad; la creación de una interfaz +gráfica de usuario (un GUI) nos habría distraído de esta meta. Sin +embargo, existen otros proyectos cuyo propósito es hacer más fácil la +creación de archivos de entrada de LilyPond. + +Ciertos entornos de edición incluyen el coloreado sintáctico, +compleción automática de instrucciones y plantillas preelaboradas. +Otros programas ofrecen realmente un GUI que permite la manipulación +directa de una partitura gráfica. Para ver más información, lea +nuestra documentación sobre @ref{Entornos mejorados}. + + +@divClass{column-center-bottom} +@subheading Y ahora ¿qué? + +Ya está preparado para @ref{Descarga, Descargar LilyPond}. ¿Aún no +está convencido? Lea lo que tenemos que decirle acerca de los +entornos de edición en @ref{Entornos mejorados}. + +@divEnd + + +@node Entornos mejorados +@unnumberedsec Entornos mejorados + +@divClass{column-center-top} +@subheading Entorno gráfico: Denemo + +@imageClickable{screenshot-denemo-small,png, + (pulse para ver una imagen más grande),screenshot-denemo,png,right} + +@sourceimage{logo-linux,,,} +@sourceimage{logo-windows,,,} + +@uref{http://denemo.org} + +Denemo es un editor gráfico que genera código fuente de LilyPond y +también permite la reproducción sonora de la música. Está en +desarrollo actualmente y genera código para versiones antiguas de +LilyPond (V2.8.7). Permite a los usuarios ver el código de entrada de +LilyPond en paralelo con la visualización gráfica. + +@ignore +Import: LilyPond, MIDI + +Export: Lilypond, MIDI, ABC, CSound Score File, PDF +@end ignore + +@divEnd + +@divClass{column-center-top} +@subheading Entorno mixto: LilyPondTool + +@imageClickable{lilypondtool-2.12-screenshot-400wide,png, (pulse para +ver una imagen más grande),lilypondtool-2.12-screenshot,png,right} + +@sourceimage{logo-linux,,,} +@sourceimage{logo-freebsd,,,} +@sourceimage{logo-macosx,,,} +@sourceimage{logo-windows,,,} + +@uref{http://lilypondtool@/.organum@/.hu} + +Creado como un @q{plugin} o complemento para el editor de texto +@uref{http://@/www@/.jedit@/.org@/,jEdit}, LilyPondTool es una de las +herramientas basadas en texto más ricas en funcionalidades para la +edición de partituras de LilyPond. Entre sus posibilidades se +encuentran: un asistente de documentos que contempla la posibilidad de +introducir letras de canciones para la preparación fácil de +documentos, y un visor de PDF integrado que contempla la posibilidad +de apuntar y pulsar con reflejo en el código. + +@divEnd + +@divClass{column-center-top} +@subheading Entorno mixto: Frescobaldi + +@imageClickable{frescobaldi-lilypond-editor-small,png, (pulse para ver +una imagen más grande),frescobaldi-lilypond-editor,png,right} + +@sourceimage{logo-linux,,,} +@sourceimage{logo-freebsd,,,} + +@uref{http://www.frescobaldi.org} + +Frescobaldi es un editor dedicado de texto y música para LilyPond con +un visor de PDF incorporado, un potente asistente de partituras y +muchas funcionalidades de edición. Está construido alrededor de las +bibliotecas de KDE4 y se ejecuta actualmente en todos los sabores de +Linux y otros sistemas operativos del tipo UNIX. + +@divEnd + +@divClass{column-center-top} +@subheading Entornos de edición de texto: Emacs y Vim + +@sourceimage{logo-linux,,,} +@sourceimage{logo-freebsd,,,} +@sourceimage{logo-macosx,,,} +@sourceimage{logo-windows,,,} + +@c @ure f{http://FIXME} + +Emacs es un editor de texto con funcionalidades avanzadas para muchos +lenuajes de programación. Emacs es un editor ampliamente expandible y +se puede usar como un entorno integrado de desarrollo. Existe un +@q{modo de lilypond} que ofrece las definiciones del lenguaje para +trabajar sobre archivos fuente de Lilypond. + +Vim es un editor de texto minimalista que es una extensión del antiguo +editor @command{vi} de Unix. También es expandible y configurable. + +Por regla general, si no está familiarizado previamente con emacs o +con vim, probablemente prefiera utilizar un editor distinto para +escribir archivos de entrada de LilyPond. + +@divEnd + +@divClass{column-center-top} +@subheading Otros + +@c @hel p insert text and a graphic(s) + +@subsubheading Entorno mixto: LilyKDE + +@imageClickable{lilykde-screenshot-small,png, + (pulse para ver una imagen más grande),lilykde-screenshot,png,right} + +@sourceimage{logo-linux,,,} +@sourceimage{logo-freebsd,,,} + +@uref{http://lilykde.googlecode.com/} + +LilyKDE es un complemento para el editor de texto de KDE +@uref{http://kate-editor.org/,Kate}. Tiene un potente asistente de +partitura para preparar rápidamente un documento de LilyPond, y un +visor de PDF integrado. + +LilyKDE es capaz de utilizar +@uref{http://www.volny.cz/smilauer/rumor/,Rumor}, de manera que se +puede introducir la música tocándola sobre un teclado MIDI. + +Otras posibilidades son el enguionado de la letra de las canciones y +la ejecución de LilyPond sobre varios archivos de una sola vez desde +dentro del gestor de archivos de KDE. + +@subsubheading Entorno de edición de texto: TexShop + +@sourceimage{logo-macosx,,,} + +@uref{http://@/www@/.uoregon@/.edu/~koch/texshop} + +El editor TexShop para MacOS@tie{}X se puede extender para que ejecute +LilyPond, @command{lilypond-book} y @command{convert-ly} desde dentro +del editor, utilizando las extensiones que están disponibles en +@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://svn.textmate.org/trunk/Bundles/LilyPond.tmbundle/ +@end example +@end ignore + +@divEnd + +@divClass{column-center-top} +@subheading Other programs can export LilyPond code + +@ignore +TODO: change url back to full adress, to make it readable in printouts -ch +@end ignore + +@c @hel p clean up this list, check links, etc. + +@subsubheading Entornos gráficos: + +@itemize +@item +@uref{http://@/noteedit@/.berlios@/.de,NoteEdit}, que importa archivos +@uref{http://@/www@/.musicxml@/.com/xml@/.html,MusicXML} +@item +@uref{http://@/www@/.rosegardenmusic@/.com,Rosegarden}, +que importa archivos MIDI +@item +@uref{http://vsr.informatik.tu-chemnitz.de/staff/jan/nted/nted.xhtml,NtEd}, +que exporta archivos de LilyPond de forma experimental. +@item +@uref{http://www.tuxguitar.com.ar/,TuxGuitar} es capaz de exportar +hacia LilyPond. +@item +@uref{http://musescore.org,MuseScore} también exporta hacia LilyPond. +@item +@uref{http://canorus.org,Canorus} puede exportar también a LilyPond, +pero aún es un programa en fase beta, se agradecen las pruebas por +parte de los usuarios. +@end itemize + +@subsubheading Herramientas de línea de comandos: + +@itemize +@item +@uref{http://www@/.volny@/.cz/smilauer/rumor/rumor@/.html,Rumor}, un +convertidor monofónico de MIDI a LilyPond en tiempo real. +@item +@uref{http://nicolas@/.sceaux@/.free@/.fr/lilypond/lyqi@/.html,lyqi}, +un modo principal de Emacs. +@item +@uref{http://@/www@/.nongnu@/.org/@/xml2ly/,xml2ly}, que importa +@uref{http://@/www@/.musicxml@/.com/xml@/.html,MusicXML} +@item +@uref{http://@/common-lisp@/.net/project/fomus/,FOMUS}, +una biblioteca de LISP para generar notación musical +@end itemize +@divEnd + + +@divClass{column-center-bottom} +@subheading Y ahora ¿qué? + +Ya está preparado para @ref{Download, Descargar LilyPond}. + +¿Aún no está convencido? Muchos compositores, músicos y directores de +orquesta han aprendido a escribir música en nuestro formato de +entrada. Los usuarios con experiencia incluso informan de que pueden +introducir una partitura completa en LilyPond ¡más rápido que con un +teclado de piano o con el ratón y un GUI! Posiblemente le apetezca +echar un vistazo a las @ref{Posibilidades}, @ref{Ejemplos} o a la +@ref{Libertad} que LilyPond ofrece, o leer algo sobre las +@ref{Producciones} y @ref{Testimonios} de nuestros usuarios. Además, +nuestro enfoque de la estética computacional del grabado musical +clásico viene explicado en nuestro tratado sobre el @ref{Trasfondo}. + + +@subheading Formalidades legales + +@divClass{legal} + +Se reconoce el copyright de todos los logotipos e imágenes de marca de +productos. + +@logoLegalLinux + +@logoLegalFreeBSD + +@logoLegalMacOSX + +@logoLegalWindows + +@divEnd + +@divEnd diff --git a/Documentation/es/web/manuals.itexi b/Documentation/es/web/manuals.itexi new file mode 100644 index 0000000000..e248604b51 --- /dev/null +++ b/Documentation/es/web/manuals.itexi @@ -0,0 +1,839 @@ +@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 Manuales +@unnumbered Manuales + +@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{Web}: +this document. + +@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. +* Web:: Web. +* 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, 1.5 Mb)} + +@item @uref{../learning.pdf, learning.pdf}: +download as a PDF file. +@*@ @ @emph{(large single download, 3 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, 1 mb)} + +@item @uref{../music-glossary.pdf, glossary.pdf}: +download as a PDF file. +@*@ @ @emph{(large single download, 1.5 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, 2 Mb)} + +@item @uref{../essay.pdf, essay.pdf}: +download as a PDF file. +@*@ @ @emph{(large single download, 2.5 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, 7 Mb)} + +@item @uref{../notation.pdf, notation.pdf}: +download as a PDF file. +@*@ @ @emph{(large single download, 18 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, 300 kb)} + +@item @uref{../usage.pdf, usage.pdf}: +download as a PDF file. +@*@ @ @emph{(large single download, 400 kb)} + +@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, 2.5 Mb)} + +@item @uref{../snippets.pdf, snippets.pdf}: +download as a PDF file. +@*@ @ @emph{(large single download, 8 Mb)} + +@c @item @uref{../TODO, snippets.info}: +@c GNU info format for documentation. TODO, link broken. + +@end itemize +@divEnd +@divEnd + + +@node Web +@unnumberedsec Web + +@divClass{column-left-top} +@subheading Web + +This manual supplies general information about LilyPond. It also +contains information about various community forums, bug +reporting, and development. + +@divEnd + +@divClass{column-right-bottom} +@subheading Read it + +@itemize + +@item @rweb{Top,Web}: +read this manual in the same format as this one. + +@end itemize + +@subheading All formats + +@divClass{keep-bullets} +@itemize + +@item @uref{../web/index.html, Web (split HTML)}: +the manual is split between many HTML pages. +@*@ @ @emph{(small download for each page)} + +@item @uref{../web-big-page.html, Web (big HTML)}: +read this manual as one huge HTML page. +@*@ @ @emph{(large single download, 1 Mb)} + +@item @uref{../web.pdf, web.pdf}: +download as a PDF file. +@*@ @ @emph{(large single download, 2 Mb)} + +@c @item @uref{../TODO, web.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, 6 kb)} + +@item @uref{../changes.pdf, changes.pdf}: +download as a PDF file. +@*@ @ @emph{(small single download, 200 kb)} + +@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, 200 kb)} + +@item @uref{../extending.pdf, extending.pdf}: +download as a PDF file. +@*@ @ @emph{(large single download, 400 kb)} + +@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 + + @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, 2.5 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{Manuales}. + +@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 + + diff --git a/Documentation/es/web/news-front.itexi b/Documentation/es/web/news-front.itexi new file mode 100644 index 0000000000..a7f643096d --- /dev/null +++ b/Documentation/es/web/news-front.itexi @@ -0,0 +1,20 @@ +@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 LilyPond 2.13.9 released! @emph{Decembrer 12, 2009} + +LilyPond 2.13.9 is now out. From 2.13.9 onwards, LilyPond is +licensed under the GNU GPL v3+ for code, and the GNU FDL 1.3+ for +documentation. In addition to the usual round of bugfixes, this +release adds a shortcut for repeated chords. + +Please note that 2.13 is an @strong{unstable development} branch; +normal users should continue to use 2.12. + +@newsEnd + + diff --git a/Documentation/es/web/news.itexi b/Documentation/es/web/news.itexi new file mode 100644 index 0000000000..6ff9a9da54 --- /dev/null +++ b/Documentation/es/web/news.itexi @@ -0,0 +1,3351 @@ +@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. + + * don't duplicate entries from news-front.itexi + +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 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! +

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 -. + +} +@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 + -- 2.39.2