Copied from the branch origin/archive/web into Documentation/misc.
--- /dev/null
+<!--
+ Translation of GIT committish: <FILL-IN-HEAD-COMMITTISH>
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. Refer to `UPDATE A TRANSLATION'
+ in README for details.
+!-->
+
+
+<pre>
+Subject: LilyPond 2.0 - make beautiful music prints
+
+
+Dear music enthousiasts,
+
+
+LilyPond version 2.0 was released today. LilyPond is an automated
+music notation system: it is used to make gorgeous sheet music. It is
+libre software ("open source"), and available for most Unix flavors,
+including Linux and MacOS X, and MS Windows.
+
+Use it for your music too!
+
+For this version, we have dramatically simplified many parts of the
+syntax, making it easier to use than ever before. Other improvements
+include quarter-tone accidentals, and conditional inclusion of music
+fragments. With version 2.0, we have a solid platform for working on
+notation and typography features for coming versions.
+
+Downloads, examples and documentation are available from the website,
+
+ http://lilypond.org
+
+A big thank-you goes out to our hackers and bughunters: Mats
+Bengtsson, Heikki Junes, Juergen Reuter, Antonio Palama, Benjamin
+Milde, Daniel Berjon Diez, David Bobroff, David Rayleigh Arnold, Erik
+Ronstroem, Fabio dos Santos, Fodor Bertalan, Frederic Bron, Graham
+Percival, Ian Bailey-Mortimer, John Williams, Josza Marton, Marco
+Caliari, Matthieu Amiguet, Michael Welsh Duggan, Patrick Atamaniuk,
+Paul Scott, Pedro Kroeger, Peter Lutek, Richard Schoeller, Thorkil
+Wolvendans, and Werner Trobin
+
+
+Happy music printing,
+
+
+
+Han-Wen Nienhuys & Jan Nieuwenhuizen
+(core development team)
+</pre>
+
+
+<h2>New features in 2.0 since 1.8</h2>
+
+ <ul>
+
+ <li>Crescendos can now be drawn dotted or dashed.
+
+ <li>Quarter tones are now supported. They are entered by suffixing
+<code>ih</code> for a half-sharp and <code>eh</code> for a half-flat. Hence, the
+following is an ascending list of pitches:
+
+ <pre class="example"> ceses ceseh ces ceh c cih cis cisih cisis
+ </pre>
+
+ <li>The following constructs have been removed from the syntax:
+
+ <pre class="example"> \duration #SCHEME-DURATION
+ \pitch #SCHEME-PITCH
+ \outputproperty <var>func</var> <var>symbol</var> = <var>value</var>
+ </pre>
+
+ <p>For <code>\outputproperty</code>, the following may be substituted:
+
+ <pre class="example"> \applyoutput #(outputproperty-compatibility <var>func</var>
+ <var>symbol</var> <var>value</var>)
+ </pre>
+
+ </p><li>Clefs may now be transposed arbitrarily, for example
+
+ <pre class="example"> \clef "G_8"
+ \clef "G_15"
+ \clef "G_9"
+ </pre>
+
+ <li>The syntax for chords and simultaneous music have changed.
+Chords are entered as
+
+ <pre class="example"> <<var>pitches</var>>
+ </pre>
+
+ <p>while simultaneous music is entered as
+
+ <pre class="example"> <<<var>..music list..</var>>>
+ </pre>
+
+ <p>In effect, the meanings of both have been swapped relative to their 1.8
+definition. The syntax for lists in <code>\markup</code> has changed
+alongside, but figured bass mode was not changed, i.e.:
+
+ <pre class="example"> \markup { \center <<var>..list of markups..</var>> }
+ \figure { <<var>figures</var>> }
+ </pre>
+
+ <p>As chords the more often used than simultaneous music, this change will
+save keystrokes.
+
+ </p><li>Each music expression can now be tagged, to make different printed
+versions from the same music expression. In the following example,
+we see two versions of a piece of music, one for the full score, and
+one with cue notes for the instrumental part:
+
+ <pre class="example"> << \tag #'part <<
+ { c4 f2 g4 } % in the part, we have cue-notes
+ \\ R1 >>
+ \tag #'score R1 % in the score: only a rest
+ >>
+ </pre>
+
+ <p>The same can be applied to articulations, texts, etc.: they are
+made by prepending
+
+ <pre class="example"> -\tag #<var>your-tags</var>
+ </pre>
+
+ <p>to an articulation, for example,
+
+ <pre class="example"> c4-\tag #'with-fingerings -4 -\tag #'with-strings \6
+ </pre>
+
+ <p>This defines a note, which has a conditional fingering and a
+string-number indication.
+
+ </p><li>The settings for chord-fingering are more flexible. You can specify a
+list where fingerings may be placed, eg.
+
+ <pre class="example"> \property Voice.fingeringOrientations = #'(left down)
+ </pre>
+
+ <p>This will put the fingering for the lowest note below the chord, and the
+rest to the left.
+
+ </p><li>The script previously known as <code>ly2dvi</code> has been renamed to
+<code>lilypond</code>. The binary itself is now installed as
+<code>lilypond-bin</code>.
+
+ <li>Markup text (ie. general text formatting) may now be used for lyrics too.
+
+ <li>Two new commands for grace notes have been added, <code>\acciaccatura</code>
+and <code>\appoggiatura</code>,
+
+ <pre class="example"> \appoggiatura f8 e4
+ \acciaccatura g8 f4
+ </pre>
+
+ <p>Both reflect the traditional meanings of acciaccatura and appogiatura,
+and both insert insert a slur from the first grace note to the main
+note.
+
+ </p><li>Layout options for grace notes are now stored in a context property,
+and may now be set separately from musical content.
+
+ <li>The <code>\new</code> command will create a context with a unique
+name automatically. Hence, for multi-staff scores, it is no longer
+necessary to invent arbitrary context names. For example, a two-staff
+score may be created by
+
+ <pre class="example"> \simultaneous {
+ \new Staff { <var>notes for 1st staff</var> }
+ \new Staff { <var>notes for 2nd staff</var> }
+ }
+ </pre>
+
+ <li>Octave checks make octave errors easier to correct.
+The syntax is
+
+ <pre class="example"> \octave <var>pitch</var>
+ </pre>
+
+ <p>This checks that <var>pitch</var> (without octave) yields <var>pitch</var> (with
+octave) in \relative mode. If not, a warning is printed, and the
+octave is corrected.
+
+ </p><li>All articulations must now be entered postfix. For example,
+
+ <pre class="example"> c8[( d8])
+ </pre>
+
+ <p>is a pair of beamed slurred eighth notes.
+
+ </p><li>The definition of <code>\relative</code> has been simplified. Octaves are
+now always propagated in the order that music is entered. In the
+following example,
+
+ <pre class="example"> PRE
+ \repeat "unfold" 3 BODY \alternative { ALT1 ALT2 }
+ POST
+ </pre>
+
+ <p>the octave of BODY is based on PRE, the starting octave of ALT1 on
+BODY, the starting octave of ALT2 on ALT1, and the starting octave of
+POST on ALT2.
+
+ <p>The same mechanism is used for all other music expressions, except the
+chord. Backwards compatibility is retained through a special program option,
+which is set through
+
+ <pre class="example"> #(ly:set-option 'old-relative)
+ </pre>
+
+ </p><li>Windows users can double click a <code>.ly</code> file to process and view
+it automagically through the new <code>lily-wins</code> frontend.
+
+</ul>
+
+
--- /dev/null
+<title>LilyPond 2.10 now available</title>
+
+<h1>LilyPond version 2.10 available—10 years anniversary release</h1>
+
+Utrecht the Netherlands—November, 2006.
+<p>
+The initial inspiration for LilyPond came ten years ago when two
+musician friends grew disappointed with the bland and boring look of
+computer formatted scores. Every musician prefers to read beautiful
+music, so couldn't we programmers solve that printing problem?
+<p>
+
+LilyPond just does that: it prints music in the best traditions of
+classical engraving with minimum fuss. Don't waste time on tuning
+spacing, moving around symbols, or shaping slurs. Impress friends and
+colleagues with sharp sheet music!
+<p>
+Check out LilyPond at <a href="http://lilypond.org"><tt>http://lilypond.org</tt></a>
+
+<p>
+We are proud to announce the 10-year anniversary release, LilyPond
+version 2.10.
+
+
+<h2>New stuff</h2>
+
+
+
+<ul>
+<li>Better page turns.
+<p>
+ Horizontal and vertical spacing is tuned simultaneously to put page
+ turns at rests or explicitly marked places.
+<li>Flat music export format.
+<p>
+A much simpler intermediate input/output format has been added. In the
+ long term, this will enable other programs to read LilyPond music.
+<li>
+ Small features and improvements.
+<p>
+ This release adds falls and doits, dashed barlines, al niente
+ hairpins, right hand fingerings for guitar, better formatting of
+ tied chords, automatic beaming and nested tuplets. </ul>
+
+
+A full list of new features is at <tt><a
+ href="http://lilypond.org/doc/v2.10/Documentation/topdocs/NEWS.html">
+ http://lilypond.org/doc/v2.10/Documentation/topdocs/NEWS.html
+ </a>
+</tt>
+
+<p>
+
+
+<p>
+<em>Enjoy!</em>
+<p>
+
+Han-Wen Nienhuys - Core development<br>
+Jan Nieuwenhuizen - Core development<br>
+Graham Percival - Documentation Editor and Bug Meister<br>
+Mats Bengtsson - Support Guru <br>
+
+
+
+<h2>Contributors</h2>
+
+
+Angelo Contardi, David Feuer, Erik Sandberg, Erlend Aasland, Guido
+Amoruso, Heikki Junes, and Joe Neeman.
+
+
+<h2>Sponsors</h2>
+
+
+Andrew Sidwell, Anthony Youngman , Chris Sawer, David Griffel, Jamie
+Bullock, Kieren MacMillan, Michael Meixner , Paul Scott, Rick Hansen,
+Steve Doonan, Trent Johnston, Trevor Bača, Vivian Barty-Taylor and
+William Wilson.
+
+
+<h2>Documentation helpers</h2>
+
+
+
+Cameron Horsburgh, Dave Luttinen, Eduardo Vieira, Erlend Aasland,
+Geoff Horton, and Juergen Reuter.
+
+<h2>Bughunters</h2>
+
+
+Albert Frantz, Arvid Grøtting, Anthony Youngman, Aurèle Duda, Ben
+Hoefer, Bernie Arai, Cameron Horsburgh, Charles Cave, Christian Hitz,
+Christopher Ellis, Claude Routhier, Colin Wilding, Daniel Tonda
+Castillo, David Rogers, Francisco Vila, Harald Wellmann, Henrik Frisk,
+Johannes Schindelin, John Williams, J. Leung, Karim Haddad, Karl
+Hammar, Keith Packard, Kieren MacMillan, Lee T. Wilkirson, Lieke van
+der Meer, Luc Wehli, Manuzhai, Mark Dewey, Marcus Macauley, Markus
+Schneider, Matti Aaltonen, Michael Meixner, Michael Welsh Duggan,
+Milan Zamazal, Orm Finnendahl, Paul Scott, Phillip Kirlin, Quentin
+Spencer, Rainer Typke, Rick Hansen, Rutger Helmers, Ruud van Silfhout,
+Sietse Brouwer, Stephen Carter, Stephen Kress, Thies Albrecht, Toine
+Schreurs, Trent Johnston, Trevor Bača, Trevor Daniels, Vaclav
+Smilauer, Vicente Solsona Dellá, Victor Eijkhout, Villum Sejersen,
+Werner Lemberg, Will Oram, and Zoltan V. Laszlo.
+
--- /dev/null
+<!--
+ Translation of GIT Committish: 91b4009e0ed37deccaec5c45bfdd80ade7d574d6
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. Refer to `UPDATE A TRANSLATION'
+ in README for details.
+
+!-->
+<title>LilyPond 2.12 „Rune“ erhältlich</title>
+
+<h1>LilyPond Version 2.12 erhältlich — Die 12-Jahre-Jubiläumsversion</h1>
+
+Dezember 2008.
+
+<p>Wir sind stolz, das Programm GNU/LilyPond 2.12 „Rune“ präsentieren zu können.
+</p>
+
+<p>Unsere Freude ist jedoch getrübt durch Trauer über den Tod unseres langjähren Mitentwicklers und Freundes Rune Zedeler am 2. Juli 2008.
+</p>
+
+<p>Mit Rune verloren wir einen Programmierer, Musiker und wertvollen Entwickler von LilyPond, der die letzten sechs Jahre enthusiastisch in dem Projekt engagiert war. Wir werden ihn sehr in unserer Gemeinschaft vermissen und möchten diese Version ihm und seinem Gedenken widmen.
+</p>
+
+<h2>Bedeutende Neuerungen</h2>
+
+<ul>
+<li>Die Vermeidung von Zusammenstößen wurde sehr stark verbessert. Objekte außerhalb des Notensystems vermeiden jetzt automatisch Zusammenstöße, sodass weniger Anpassungen nötig sind, um einen schönen Notensatz zu erhalten.</li>
+
+<li>Die Dokumentation wurde im Zuge des mehr als ein Jahr dauernden "Großen Dokumentationsprojekts" fast vollständig neu geschrieben und umorganisiert. Zusätzlich hat die Online-Dokumentation nun ein neues, übersichtlicheres Layout erhalten. Das Programm selbst ist mittlerweile in 15 Sprachen erhältlich und die Dokumentation wurde teilweise auf Deutsch, Französisch und Spanisch übersetzt. Es war noch nie so einfach, die ersten perfekt gesetzten Noten mit LilyPond zu erstellen.</li>
+
+<li>Beinahe 30 neue Eigenschaften wurden dem Programm hinzugefügt, unter Anderem transponierbare Bund-Diagramme, Versetzungszeichen für Mikrotöne sowie eine vielfach verbesserte Importmöglichkeit von MusicXML-Dateien (musicxml2ly), und über 200 Fehler wurden beseitigt. Eine vollständige Liste der Änderungen findet sich unter <tt><a
+ href="http://lilypond.org/doc/v2.12/Documentation/topdocs/NEWS.html">http://lilypond.org/doc/v2.12/Documentation/topdocs/NEWS.html</a></tt>.
+</li>
+</ul>
+<br>
+
+<p>Viel Vergnügen beim Notensatz!</p>
+
+<h2>LilyPond wird Ihnen zur Verfügung gestellt von...</h2>
+
+<h3>Entwicklungsteam</h3>
+
+<p>Han-Wen Nienhuys – Hauptentwicklung<br>
+Jan Nieuwenhuizen – Hauptentwicklung<br>
+Joe Neeman – Hauptentwicklung<br>
+Graham Percival – Dokumentationsredaktion und Verwaltung der Fehlermeldungen<br>
+Valentin Villenave – Redaktion des Schnipseldepots und Verwaltung der Fehlermeldungen<br>
+Mats Bengtsson – Unterstützungsguru<br>
+John Mandereau – Redaktion und Implementierung der Übersetzungen</p>
+
+<h3>Mitwirkende</h3>
+
+<p>Rune Zedeler,
+Maximilian Albert,
+Milan Zamazal,
+Reinhold Kainhofer (<tt>musicxml2ly</tt>-Entwicklung),
+Erlend Aasland,
+Stan Sanderson (Regressionsüberprüfung),
+Neil Puttock.</p>
+
+<h3>Das Große DokumenationsProjekt</h3>
+
+<p>Trevor Daniels – Dokumentationsredation<br>
+Andrew Hawryluk, Carl Sorensen, Eyolf Østrem, Francisco Vila,
+Jay Hamilton, Jonathan Kulp, Joseph Harfouch, Patrick McCarty,
+Ralph Palmer, Till Rettig – Arbeit an der Notationsreferenz<br>
+Kurt Kroon – Aktualisierung des Glossars, Arbeit and der Notationsreferenz<br>
+Alard de Boer – Formatierung<br>
+Michael Rasmussen – Formatierung<br>
+Trevor Bača – Inspirierende Notenbeispiele<br>
+Reinhold Kainhofer – Technische Hilfe<br>
+Neil Puttock – Schnipselredation, technische Hilfe.</p>
+
+<h3>Übersetzung</h3>
+
+<p>Clytie Siddall, Damien Heurtebise, Francisco Vila, Heikki Junes,
+Jean-Charles Malahieude, John Mandereau, Nicolas Klutchnikoff, Till
+Rettig, Valentin Villenave.</p>
+
+<h3>Sponsoren</h3>
+
+<p>Mike Amundsen, Trevor Bača.</p>
+
+<h3>Fehlerjäger und Anregungen</h3>
+
+<p>Adam James Wilson, Alard de Boer, Alex Rolex, Andy Haupt, Arvid
+Grøtting, Bertalan Fodor, Benjamin Drung, Cameron Horsburgh, Carl
+Sorensen, Christian Hitz, Christian Herzberg, David Bobroff, David
+Griffel, Daniel Hulme, Daniel Johnson, Dominic Neumann, Eduardo
+Vieira, Frédéric Chiasson, Georg Dummer, Georg Romstorfer, Gilles
+Thibault, Hernán J. González, Hu Haipeng, Jay Anderson, James
+Kilfinger, Jean-Marie Mouchel, Jean-Yves Baudais, Jesús Guillermo
+Andrade, Jonathan Henkelman, Kazuhiro Suzuki, Kevin Dalley, Laura
+Conrad, Luc Wehli, Maarten Hijzelendoorn, Marc Lanoiselée, Mark
+Polesky, Matthijs Frankeno, Martijn Vromans, Marnen Laibow-Koser,
+Maximilian Albert, Mirosław Doroszewski, Mike Coleman, Neil Puttock,
+Nicolas Mayencourt, Nicolas Sceaux, Orm Finnendahl, Peter Budny,
+Phillip Kirlin, Pierre-Emmanuel Brame, Ralph Palmer, Renaud Flavigny,
+Rick Hansen, Risto Vääräniemi, Robin Bannister, Roland Goretzki, Rune
+Zedeler, Ruud van Silfhout, Sean Reed, Steven Weber, Tomas Sauer,
+Thomas Scharkowski, Trevor Bača, Vivian Barty-Taylor, Werner Lemberg,
+Wilbert Berendsen, William Oram, Yota Moteuchi, Zack Charter, and
+Zoltan Selyem.</p>
--- /dev/null
+<!--
+ Translation of GIT Committish: b368624ce125eb38ac5e635a88c0ccf414a3937f
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. Refer to `UPDATE A TRANSLATION'
+ in README for details.
+!-->
+
+<title>Está disponible LilyPond 2.12 “Rune”</title>
+
+<h1>Ya está disponible LilyPond versión 2.12: la edición del duodécimo aniversario</h1>
+
+Diciembre de 2008.
+
+<p>Nos llena de orgullo anunciar el lanzamiento de GNU/LilyPond 2.12
+“Rune”.
+</p>
+
+<p>Nuestra alegría está teñida de tristeza, pues el que fue durante
+mucho tiempo colaborador del proyecto LilyPond y amigo, Rune Zedeler,
+falleció el pasado 2 de julio de 2008. Esta edición está dedicada a su
+memoria.
+</p>
+
+<p>Rune era programador y músico, e hizo valiosos aportes a
+LilyPond. Había estado implicado en el proyecto durante los últimos
+seis años, y nuestra comunidad le echará de menos con gran añoranza.
+</p>
+
+<h2>Principales novedades</h2>
+
+<ul>
+<li>Se ha mejorado enormemente la detección de colisiones. Los objetos
+fuera del pentagrama ahora se evitan automáticamente, de forma que se
+necesitan muchos menos ajustes manuales para obtener un resultado
+satisfactorio.</li>
+
+<li>La documentación también se ha reescrito casi por completo durante
+ el "Proyecto Magno de Documentación" (GDP) que ha durado un año, y la
+ documentación en línea es ahora mucho más atractiva visualmente y
+ también se navega por ella mucho más fácilmente. El programa está
+ traducido a 6 idiomas, y la documentación completa está disponible
+ en español, y parcialmente en francés y alemán. ¡Nunca ha sido tan
+ fácil empezar con 'Pond!</li>
+
+<li>Se han incorporado casi 30 nuevas funcionalidades, entre ellas los
+ diagramas transportables de posiciones de guitarra, alteraciones
+ microtonales y un conversor <tt>musicxml2ly</tt> muy mejorado, y se han
+ corregido casi 200 bugs. Para ver los detalles de estas nuevas
+ posibilidades, diríjase
+ a <tt><a href="http://lilypond.org/doc/v2.12/Documentation/topdocs/NEWS.html">http://lilypond.org/doc/v2.12/Documentation/topdocs/NEWS.html</a></tt>.
+</li>
+</ul>
+<br>
+
+<p>¡Feliz tipografía musical!</p>
+
+<h2>LilyPond le llega por cortesía de...</h2>
+
+<h3>Equipo de desarrollo</h3>
+
+<p>Han-Wen Nienhuys – Desarrollos esenciales<br>
+Jan Nieuwenhuizen – Desarrollos esenciales<br>
+Joe Neeman – Desarrollos esenciales<br>
+Graham Percival – Editor de la documentación y Maestro desinsectador<br>
+Valentin Villenave – Editor del repositorio LSR y Maestro desinsectador<br>
+Mats Bengtsson – Gurú de apoyo<br>
+John Mandereau – Maestro de la infraestructura de traducción</p>
+
+<h3>Colaboradores</h3>
+
+<p>Rune Zedeler,
+Maximilian Albert,
+Milan Zamazal,
+Reinhold Kainhofer (desarrollo de <tt>musicxml2ly</tt>),
+Erlend Aasland,
+Stan Sanderson (revisor de las regresiones),
+Neil Puttock.</p>
+
+<h3>Proyecto Magno de Documentación</h3>
+
+<p>Trevor Daniels – Editor adjunto de la documentación<br>
+Andrew Hawryluk, Carl Sorensen, Eyolf Østrem, Francisco Vila,
+Jay Hamilton, Jonathan Kulp, Joseph Harfouch, Patrick McCarty,
+Ralph Palmer, Till Rettig – trabajos en la Referencia de la Notación<br>
+Kurt Kroon – Actualizaciones del glosario, trabajos en la Referencia de la Notación<br>
+Alard de Boer – Formato<br>
+Michael Rasmussen – Formato<br>
+Trevor Bača – Encabezamientos evocadores<br>
+Reinhold Kainhofer – Asistencia técnica<br>
+Neil Puttock – Editor de fragmentos de código, asistencia técnica.</p>
+
+<h3>Traductores</h3>
+
+<p>Clytie Siddall, Damien Heurtebise, Francisco Vila, Heikki Junes,
+Jean-Charles Malahieude, John Mandereau, Nicolas Klutchnikoff, Till
+Rettig, Valentin Villenave.</p>
+
+<h3>Patrocinadores</h3>
+
+<p>Mike Amundsen, Trevor Bača.</p>
+
+<h3>Cazadores de fallos; sugerencias</h3>
+
+<p>Adam James Wilson, Alard de Boer, Alex Rolex, Andy Haupt, Arvid
+Grøtting, Bertalan Fodor, Benjamin Drung, Cameron Horsburgh, Carl
+Sorensen, Christian Hitz, Christian Herzberg, David Bobroff, David
+Griffel, Daniel Hulme, Daniel Johnson, Dominic Neumann, Eduardo
+Vieira, Frédéric Chiasson, Georg Dummer, Georg Romstorfer, Gilles
+Thibault, Hernán J. González, Hu Haipeng, Jay Anderson, James
+Kilfinger, Jean-Marie Mouchel, Jean-Yves Baudais, Jesús Guillermo
+Andrade, Jonathan Henkelman, Kazuhiro Suzuki, Kevin Dalley, Laura
+Conrad, Luc Wehli, Maarten Hijzelendoorn, Marc Lanoiselée, Mark
+Polesky, Matthijs Frankeno, Martijn Vromans, Marnen Laibow-Koser,
+Maximilian Albert, Mirosław Doroszewski, Mike Coleman, Neil Puttock,
+Nicolas Mayencourt, Nicolas Sceaux, Orm Finnendahl, Peter Budny,
+Phillip Kirlin, Pierre-Emmanuel Brame, Ralph Palmer, Renaud Flavigny,
+Rick Hansen, Risto Vääräniemi, Robin Bannister, Roland Goretzki, Rune
+Zedeler, Ruud van Silfhout, Sean Reed, Steven Weber, Tomas Sauer,
+Thomas Scharkowski, Trevor Bača, Vivian Barty-Taylor, Werner Lemberg,
+Wilbert Berendsen, William Oram, Yota Moteuchi, Zack Charter, and
+Zoltan Selyem.</p>
--- /dev/null
+<!--
+ Translation of GIT Committish: df1e2ce4169851a9d841e7becf9924c7421a2d83
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. Refer to `UPDATE A TRANSLATION'
+ in README for details.
+
+!-->
+<title>LilyPond 2.12 « Rune »</title>
+
+<h1>LilyPond version 2.12 disponible — 12 ans d'âge</h1>
+
+Décembre 2008.
+
+<p>Nous sommes ravis d'annoncer la sortie de GNU LilyPond 2.12
+« Rune ».</p>
+
+<p>Notre enthousiasme est terni par la tritesse causée par la
+ disparition le 2 juillet 2008 de Rune Zedeler, un ami et un
+ contributeur de longue date de Lilypond. Nous lui dédions cette
+ mouture 2.12.
+</p>
+
+<p>Rune était développeur informatique, musicien et un contributeur
+ précieux pour LilyPond. Il était impliqué avec enthousiasme dans le
+ projet depuis six ans, il sera profondément regretté par toute la
+ communauté.
+</p>
+
+<h2>Nouveautés majeures</h2>
+
+<ul>
+<li>La détection des collisions s'est grandement améliorée : les
+ objets en dehors de la portée n'entrent plus jamais en collision,
+ désormais seules des retouches mineures sont parfois nécessaires
+ pour obtenir une gravure très satisfaisante.</li>
+
+<li>La documentation a été presque entièrement réécrite pendant le
+ Grand Projet de Documentation (Grand Documentation Project), et la
+ documentation en ligne est mieux présentée et plus facile à
+ parcourir. Le programme est disponible en 6 langues, et la
+ documentation est partiellement traduite en français, allemand et
+ espagnol. Débuter n'a jamais été aussi facile !</li>
+
+<li>L'équipe de développement et les contributeurs ont ajouté une
+ trentaine de fonctionnalités, dont des tablatures pour guitare
+ transposables et des altérations microtonales, et ont grandement
+ amélioré <tt>musicxml2ly</tt> ; par ailleurs, plus de 200 bogues ont
+ été corrigés depuis la version 2.10. Pour une liste complète des
+ nouvelles fonctionnalités, consultez <tt><a
+ href="http://lilypond.org/doc/v2.12/Documentation/topdocs/NEWS.html">http://lilypond.org/doc/v2.12/Documentation/topdocs/NEWS.html</a></tt>.
+</li>
+</ul>
+<br>
+
+<p>Bonne gravure musicale !</p>
+
+<h2>LilyPond vous est proposé par...</h2>
+
+<h3>Équipe de développement</h3>
+
+<p>Han-Wen Nienhuys – développeur principal<br>
+Jan Nieuwenhuizen – développeur principal<br>
+Joe Neeman – développeur principal<br>
+Graham Percival – éditeur de la documentation et chef des bogues<br>
+Valentin Villenave – éditeur LSR et chef des bogues<br>
+Mats Bengtsson – gourou du support utilisateur<br>
+John Mandereau – chef des traductions</p>
+
+<h3>Contributeurs</h3>
+
+<p>Rune Zedeler,
+Maximilian Albert,
+Milan Zamazal,
+Reinhold Kainhofer (développement de <tt>musicxml2ly</tt>),
+Erlend Aasland,
+Stan Sanderson (vérification des tests de régression),
+Neil Puttock.</p>
+
+<h3>Grand Projet de Documentation</h3>
+
+<p>Trevor Daniels – assistant éditeur de la documentation<br>
+Andrew Hawryluk, Carl Sorensen, Eyolf Østrem, Francisco Vila,
+Jay Hamilton, Jonathan Kulp, Joseph Harfouch, Patrick McCarty,
+Ralph Palmer, Till Rettig – travail sur le manuel de notation<br>
+Kurt Kroon – mise à jour du glossaire, travail sur le
+ manuel de notation<br>
+Alard de Boer – formatage<br>
+Michael Rasmussen – formatage<br>
+Trevor Bača – en-têtes musicaux<br>
+Reinhold Kainhofer – aide technique<br>
+Neil Puttock – éditeur d'extraits de code, aide technique</p>
+
+<h3>Traducteurs</h3>
+
+<p>Clytie Siddall, Damien Heurtebise, Francisco Vila, Heikki Junes,
+Jean-Charles Malahieude, John Mandereau, Nicolas Klutchnikoff, Till
+Rettig, Valentin Villenave.</p>
+
+<h3>Sponsors</h3>
+
+<p>Mike Amundsen, Trevor Bača.</p>
+
+<h3>Chasseurs de bogues et suggestions</h3>
+
+<p>Adam James Wilson, Alard de Boer, Alex Rolex, Andy Haupt, Arvid
+Grøtting, Bertalan Fodor, Benjamin Drung, Cameron Horsburgh, Carl
+Sorensen, Christian Hitz, Christian Herzberg, David Bobroff, David
+Griffel, Daniel Hulme, Daniel Johnson, Dominic Neumann, Eduardo
+Vieira, Frédéric Chiasson, Georg Dummer, Georg Romstorfer, Gilles
+Thibault, Hernán J. González, Hu Haipeng, Jay Anderson, James
+Kilfinger, Jean-Marie Mouchel, Jean-Yves Baudais, Jesús Guillermo
+Andrade, Jonathan Henkelman, Kazuhiro Suzuki, Kevin Dalley, Laura
+Conrad, Luc Wehli, Maarten Hijzelendoorn, Marc Lanoiselée, Mark
+Polesky, Matthijs Frankeno, Martijn Vromans, Marnen Laibow-Koser,
+Maximilian Albert, Mirosław Doroszewski, Mike Coleman, Neil Puttock,
+Nicolas Mayencourt, Nicolas Sceaux, Orm Finnendahl, Peter Budny,
+Phillip Kirlin, Pierre-Emmanuel Brame, Ralph Palmer, Renaud Flavigny,
+Rick Hansen, Risto Vääräniemi, Robin Bannister, Roland Goretzki, Rune
+Zedeler, Ruud van Silfhout, Sean Reed, Steven Weber, Tomas Sauer,
+Thomas Scharkowski, Trevor Bača, Vivian Barty-Taylor, Werner Lemberg,
+Wilbert Berendsen, William Oram, Yota Moteuchi, Zack Charter, and
+Zoltan Selyem.</p>
--- /dev/null
+<title>LilyPond 2.12 “Rune” available</title>
+
+<h1>LilyPond version 2.12 available — 12 year anniversary
+release</h1>
+
+December, 2008.
+
+<p>We are proud to announce the release of GNU LilyPond 2.12 “Rune”.
+</p>
+
+<p>Our joy is tinged with sadness, as long-time LilyPond contributor
+and friend Rune Zedeler passed away on the 2nd of July, 2008. This
+release is dedicated to him.
+</p>
+
+<p>Rune was a computer programmer, a musician and a valued contributor
+to LilyPond. He had been enthusiastically involved in the project
+for the past six years, and he will be sorely missed in our community.
+</p>
+
+<h2>Major updates</h2>
+
+<ul>
+<li>Collision detection has been vastly improved. Outside-staff objects
+ now avoid each other automatically, so far fewer manual tweaks are
+ required to obtain a pleasing layout.</li>
+
+<li>The documentation has been almost entirely rewritten during the
+ year-long "Grand Documentation Project", and the online documentation
+ is both much better-looking and far easier to browse. The program
+ is now available in 6 languages, and the documentation is partially
+ available in French, Spanish and German. It has never been easier to
+ get started with 'Pond!</li>
+
+<li>Almost 30 new features, among others transposable fret diagrams,
+ microtonal accidentals, and a much improved <tt>musicxml2ly</tt>, have been
+ implemented and nearly 200 bugs have been fixed. For a complete
+ overview surf to <tt><a
+ href="http://lilypond.org/doc/v2.12/Documentation/topdocs/NEWS.html">http://lilypond.org/doc/v2.12/Documentation/topdocs/NEWS.html</a></tt>.
+</li>
+</ul>
+<br>
+
+<p>Happy music typesetting!</p>
+
+<h2>LilyPond was brought to you by...</h2>
+
+<h3>Development team</h3>
+
+<p>Han-Wen Nienhuys – Core development<br>
+Jan Nieuwenhuizen – Core development<br>
+Joe Neeman – Core development<br>
+Graham Percival – Documentation Editor and Bug Meister<br>
+Valentin Villenave – LSR Editor and Bug Meister<br>
+Mats Bengtsson – Support Guru<br>
+John Mandereau – Translation Meister</p>
+
+<h3>Contributors</h3>
+
+<p>Rune Zedeler,
+Maximilian Albert,
+Milan Zamazal,
+Reinhold Kainhofer (<tt>musicxml2ly</tt> development),
+Erlend Aasland,
+Stan Sanderson (Regression Checker),
+Neil Puttock.</p>
+
+<h3>Grand Documentation Project</h3>
+
+<p>Trevor Daniels – Assistant Documentation Editor<br>
+Andrew Hawryluk, Carl Sorensen, Eyolf Østrem, Francisco Vila,
+Jay Hamilton, Jonathan Kulp, Joseph Harfouch, Patrick McCarty,
+Ralph Palmer, Till Rettig – Notation Reference work<br>
+Kurt Kroon – Glossary Updates, Notation Reference work<br>
+Alard de Boer – Formatting<br>
+Michael Rasmussen – Formatting<br>
+Trevor Bača – Inspirational Headwords<br>
+Reinhold Kainhofer – Technical Aid<br>
+Neil Puttock – Snippet Editor, Technical Aid.</p>
+
+<h3>Translators</h3>
+
+<p>Clytie Siddall, Damien Heurtebise, Francisco Vila, Heikki Junes,
+Jean-Charles Malahieude, John Mandereau, Nicolas Klutchnikoff, Till
+Rettig, Valentin Villenave.</p>
+
+<h3>Sponsors</h3>
+
+<p>Mike Amundsen, Trevor Bača.</p>
+
+<h3>Bug hunters and suggestions</h3>
+
+<p>Adam James Wilson, Alard de Boer, Alex Rolex, Andy Haupt, Arvid
+Grøtting, Bertalan Fodor, Benjamin Drung, Cameron Horsburgh, Carl
+Sorensen, Christian Hitz, Christian Herzberg, David Bobroff, David
+Griffel, Daniel Hulme, Daniel Johnson, Dominic Neumann, Eduardo
+Vieira, Frédéric Chiasson, Georg Dummer, Georg Romstorfer, Gilles
+Thibault, Hernán J. González, Hu Haipeng, Jay Anderson, James
+Kilfinger, Jean-Marie Mouchel, Jean-Yves Baudais, Jesús Guillermo
+Andrade, Jonathan Henkelman, Kazuhiro Suzuki, Kevin Dalley, Laura
+Conrad, Luc Wehli, Maarten Hijzelendoorn, Marc Lanoiselée, Mark
+Polesky, Matthijs Frankeno, Martijn Vromans, Marnen Laibow-Koser,
+Maximilian Albert, Mirosław Doroszewski, Mike Coleman, Neil Puttock,
+Nicolas Mayencourt, Nicolas Sceaux, Orm Finnendahl, Peter Budny,
+Phillip Kirlin, Pierre-Emmanuel Brame, Ralph Palmer, Renaud Flavigny,
+Rick Hansen, Risto Vääräniemi, Robin Bannister, Roland Goretzki, Rune
+Zedeler, Ruud van Silfhout, Sean Reed, Steven Weber, Tomas Sauer,
+Thomas Scharkowski, Trevor Bača, Vivian Barty-Taylor, Werner Lemberg,
+Wilbert Berendsen, William Oram, Yota Moteuchi, Zack Charter, and
+Zoltan Selyem.</p>
--- /dev/null
+<!--
+ Translation of GIT committish: <FILL-IN-HEAD-COMMITTISH>
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. Refer to `UPDATE A TRANSLATION'
+ in README for details.
+!-->
+
+<title>LilyPond version 2.2 released</title>
+<pre>
+
+Dear music enthusiasts,
+
+
+LilyPond is a program for making beautiful music notation. It is
+free/open source software, and is available for all popular operating
+systems. It runs on most Unix flavors --including Linux and MacOS X-- and MS
+Windows. Use it for your music too!
+
+
+
+LilyPond version 2.2 was released today!
+
+This release has completely revamped support for for orchestral score
+formatting, cue notes, font size management, lyric formatting, drum
+notation/playback and document integration.
+
+In addition, it has numerous syntax simplifications, proper support
+for 8va brackets, and a completely updated manual.
+
+Go and grab it at
+
+ http://lilypond.org
+
+
+A big thank-you goes out to our contributors:
+
+David Bobroff, Edward Sanford Sutton, Heikki Junes, and Nicolas
+Sceaux.
+
+Also thanks to our bug-hunters:
+
+Alexandre Beneteau, Andrew McNabb, Atte Andre Jensen , Bertalan Fodor,
+Bruce McIntyre, Dave Symonds, David Bobroff, Darius, Delma Avers, Doug
+Linhardt, Eric Wurbel, Erik Sandberg, Ferenc Wagner, Hans Forbrich,
+John Williams, José Luis Cruz, Juergen Reuter, Kieren Richard
+MacMillan, Laurent Martelli, Mats Bengtsson, Matthias Kilian, Nancho
+Alvarez, Nick Busigin, Nicolas Sceaux , Olivier Guery, Patrick
+Atamaniuk, Paul Scott, Pawel D, Pedro Kroger, Ray McKinney, Reuben
+Thomas, Rob V, Stef Epardaud, Thomas Willhalm, Thomas Scharkowski, Tom
+Bäckström, Werner Lemberg, and Will Oram.
+
+
+
+Happy music printing,
+
+
+
+
+Han-Wen Nienhuys & Jan Nieuwenhuizen
+(core development team)
+
+</pre>
+
+
+<h2 class="unnumbered">New features in 2.2</h2>
+
+ <ul>
+<li>Setting <code>raggedlast = ##t</code> in the <code>\paper</code> block
+causes the last line to be set flush-left instead of justified.
+
+ <li>The <code>Timing_engraver</code> now sets the <code>Timing</code> alias on
+its containing context automatically.
+
+ <li>The code for font selection has been rewritten. In addition to
+existing font selection properties, the property <code>font-encoding</code>
+has been added, which makes the switch between normal <code>text</code> and
+other encodings like <code>braces</code>, <code>music</code> and <code>math</code>.
+
+ <li>The pmx2ly script has been removed from the distribution.
+
+ <li>Pedal brackets will now run to the last bar of a piece if they are not
+explicitly ended.
+
+ <li>Context definitions now use the word <code>\context</code> instead of <code>\translator</code>.
+
+ <li>Property functions may be used as an argument to <code>set!</code>,
+for example
+
+ <pre class="example"> (set! (ly:grob-property grob 'beam) ... )
+ </pre>
+
+ <li>In anticipation of Emacs 21.4 or 22.1, the info documentation contains
+images.
+
+ <li>Cue notes can be quoted directly from the parts that
+contain them. This will take into account transposition of source and target
+instrument. For example,
+
+ <pre class="verbatim">
+ \addquote clarinet \notes\relative c' {
+ \transposition bes
+ fis4 fis fis fis
+ }
+
+ \score {
+ \notes \relative c'' {
+ c8 d8 \quote 2 oboe es8 gis
+ }
+ }
+</pre>
+
+ <li>The transposition of an instrument can be specified using the
+<code>\transposition</code> command. An
+E-flat alto saxophone is specified as
+
+ <pre class="example"> \transposition es'
+ </pre>
+
+ <li>The naming of exported Scheme functions now follows Scheme conventions.
+Changes be applied to Scheme files with
+
+ <pre class="example"> convert-ly -e -n --from=2.1.24 --to=2.1.26 *.scm
+ </pre>
+
+ <li>Notes can be excluded from auto-beaming, by marking them with
+<code>\noBeam</code>
+ <pre class="example"> c8 c \noBeam c c
+ </pre>
+
+ <p class="noindent">will print two separate eighth notes, and two beamed notes.
+
+ <li>Translators and contexts have been split. The result of this
+internal cleanup is that <code>Score</code> no longer is the top context;
+<code>Score</code> is contained in the <code>Global</code> context. Consequently,
+it is possible to tweak <code>Score</code> as follows:
+
+ <pre class="example"> \context Score \with {
+ ...
+ }
+ </pre>
+
+ <li>The number of staff lines in Tablature notation is now
+automatically deduced from the <code>stringTunings</code> property.
+
+ <li>The program reference has been cleaned up and revised.
+
+ <li>The syntax for setting properties has been simplified:
+the following table lists the differences:
+
+ <pre class="example"> (old) (new)
+
+ \property A.B = #C \set A.B = #C
+ \property A.B \unset \unset A.B
+ \property A.B \set #C = #D \override A.B #C = #D
+ \property A.B \override #C = #D (removed)
+ \property A.B \revert #C \revert A.B #C
+ </pre>
+
+ <p>Furthermore, if <code>A</code> is left out, the bottommost context is used
+by default. In other words, it is no longer necessary to explicitly
+mention <code>Voice</code>, <code>Lyrics</code> or <code>ChordNames</code>.
+
+ <p>Old:
+
+ <pre class="example"> \property Voice.autoBeaming = ##f
+ \property Staff.TimeSignature \set #'style = #'C
+ </pre>
+
+ <p>New:
+
+ <pre class="example"> \set autoBeaming = ##f
+ \override Staff.TimeSignature #'style = #'C
+ </pre>
+
+ <li>Tweaks made with <code>\override</code> and <code>\revert</code> no longer
+hide tweaks at higher context levels.
+
+ <li>Melismata in lyrics are also properly handled in the MIDI output.
+
+ <li>The lilypond-book script has been rewritten.
+It is shorter, cleaner and faster. The special construct
+<code>mbinclude</code> has been removed, plain <code>@include</code> or
+<code>\input</code> can be used now.
+
+ <p>It now supports running convert-ly on the lilypond snippets,
+ <pre class="example"> lilypond-book --filter='convert-ly --from=2.0.0' my-book.tely
+ </pre>
+
+ <li>The <code>LyricsVoice</code> context has been removed. Lyrics should only
+be constructed in <code>Lyrics</code>.
+
+ <li>The <code>Thread</code> context has been removed. Note heads and rests
+are now constructed at <code>Voice</code> level.
+
+ <li>Harmonic notes can now be entered as
+
+ <pre class="example"> <c' g''\harmonic>
+ </pre>
+
+ <li>Drum notation is now supported as a regular feature:
+percussion may be entered in <code>\drums</code> mode, and printed or
+performed in a <code>DrumStaff</code> context:
+
+ <pre class="example"> \score {
+ \drums \new DrumStaff { hihat4 cowbell8 }
+ }
+ </pre>
+
+ <li>The automatic staff changer was internally rewritten. As a
+result, the syntax has been simplified as well:
+
+ <pre class="example"> \autochange <var>the-music</var>
+ </pre>
+
+ <li>The ergonomic syntax of <code>\markup</code> now has an equivalent in
+Scheme. The <code>markup*</code> macro creates such objects; the following
+two markup commands are equivalent:
+ <pre class="example"> f4^#(markup* #:raise 0.2 #:bold "hi")
+ f4^\markup { \raise #0.2 \bold hi }
+ </pre>
+
+ <li>Voice names, for vocal lines, have been added. They are similar
+to instrument names. They can be set by defining <code>vocalName</code>
+and <code>vocNam</code>.
+
+ <li>Safe mode has been reinstated for lilypond.
+When lilypond is invoked with <code>--safe-mode</code>, TeX and
+PostScript file output is disallowed, and lilypond-bin is invoked with
+<code>--safe-mode</code>, the user's Guile expressions are evaluated in a
+safe environment and file inclusion is not allowed.
+
+ <p>Warning: this does not protect against denial-of-service attacks using
+Guile, TeX or PostScript.
+
+ <p>(This feature is still experimental.)
+
+ <li>There is now a Scheme macro for defining markup
+commands. Special mark-up commands can be defined in user-files too.
+
+ <li>Many fixes for dimension scaling have been made,
+resulting in correct results for scores that mix staves in different
+sizes.
+
+ <li>Improved robustness when layout properties are accidentally removed.
+
+ <li>A more cleanly constructed part combiner has been installed.
+It is more robust and less buggy. The part-combiner can be used with
+ <pre class="example"> \partcombine <var>mus1</var> <var>mus2</var>
+ </pre>
+
+ <p class="noindent">See <span class="file">input/regression/new-part-combine.ly</span> for an example.
+
+ <li>Formatting of rehearsal marks has been improved. The <code>\mark</code>
+command now only does automatic incrementing for marks specified as
+integer. For example, <code>\mark #1</code> will print an A in the default
+style. See <span class="file">input/regression/rehearsal-mark-letter.ly</span>,
+<span class="file">input/regression/rehearsal-mark-number.ly</span>.
+
+ <li>Formatting of ottava brackets has been much improved.
+
+ <li>Objects in the output can now be documented: the following fragment
+ boxes the note head, and adds the text “heads or tails?” three
+spaces below the box.
+
+ <pre class="example"> \context Voice \applyoutput #(add-balloon-text
+ 'NoteHead "heads, or tails?"
+ '(0 . -3))
+
+
+ c8
+ </pre>
+
+ <li>Default staff sizes are now scalable. There are two new mechanisms for
+setting staff sizes. Both are demonstrated in this fragment:
+
+ <pre class="example"> #(set-global-staff-size 15)
+ \paper {
+ #(paper-set-staff-size (* 15 pt))
+ }
+ </pre>
+
+ <p class="noindent">Both have the same effect on the global layout of a piece. Similarly,
+the paper size may be changed as follows
+
+ <pre class="example"> #(set-default-paper-size "a4")
+ \paper {
+ #(set-paper-size "a4")
+ }
+ </pre>
+
+ <li>Warnings for bar check errors are more cleverly printed. This
+makes <code>barCheckSynchronize</code> superfluous, so it is now switched
+off by default.
+
+ <p>Warning: this will cause problems in scores that use bar checks to
+shorten measures.
+
+ <li>The black note head was made a little rounder, which causes a less
+ frantic graphic impression.
+
+ <li>A more concise syntax for checking octaves was introduced. A note may
+be followed by <code>=</code><var>quotes</var> which indicates what its absolute
+octave should be. In the following example,
+
+ <pre class="example"> \relative c'' { c='' b=' d,='' }
+ </pre>
+
+ <p class="noindent">the d will generate a warning, because a d” is
+expected, but a d' is found.
+<!-- @code adds ` ', very confusing. -->
+
+ <li>There is a new mechanism for putting lyrics to melodies.
+With this mechanism, <code>Lyrics</code> lines can be put melodies
+individually, allowing for different melismatic sections in every
+<code>Lyrics</code>. See <span class="file">input/regression/lyric-combine-new.ly</span>.
+
+ <li>Bar lines may now be dotted.
+
+ <li>The documentation now has links to a wiki, where everyone can
+add personal comments to the manual.
+
+ <li>Contexts may now be changed locally for an isolated music
+expression. For example,
+
+ <pre class="example"> \new Voice \with {
+ \consists "Pitch_squash_engraver"
+ } {
+ c'4
+ }
+ </pre>
+
+ <li>The syntax for changing staffs has changed. The keyword
+<code>\change</code> should now be used, e.g.
+
+ <pre class="example"> \change Staff = up
+ </pre>
+
+ <li>Features of spanner contexts, like <code>Staff</code>, can now be changed
+ using <code>\set</code>, eg.
+
+ <pre class="example"> \new Staff {
+ \override Staff.StaffSymbol #'line-count = #4
+ c'4
+ }
+ </pre>
+
+ <p class="noindent">puts a quarter note C on a staff with 4 lines.
+
+ <li>Multi measure rests are now truly centered between the
+clefs/barlines of the staff, their position is independent of symbols
+on the other staffs.
+
+ <li>Collision resolution for dots in chords has been improved greatly.
+
+ <li>Spacing following barlines was improved for widely stretched lines.
+
+ <li>Lyric hyphens and extenders now conform to standard typesetting
+practice.
+
+ <li>Lyrics are now aligned under note heads conforming to engraving
+standards. The responsible code has been rewritten, and is drastically
+simpler from the previous version. To aid this rewrite, the syntactic
+function of the extender line ( __ ) has been changed: it is now
+attached to the lyric syllable.
+
+ <li>When redefining a context, the associated identifier is also
+updated. For example, after reading
+
+ <pre class="example"> \translator {
+ \ScoreContext
+ autoBeaming = ##f
+ }
+ </pre>
+
+ <p class="noindent">the definition of <code>ScoreContext</code> is updated to include the changed
+setting.
+
+ <li>The weight of the stafflines is now heavier at smaller staff sizes.
+The font has been modified to match this look: at smaller sizes, the
+font is heavier and the note heads are more rounded.
+
+ <li>Processing scores is now done while parsing the file. New
+Scheme functions give more flexibility: for example, it is now possible
+interpret a score, collecting synchronized musical events in a list, and
+manipulate that information using inline Scheme. For an example, see
+<span class="file">input/no-notation/recording.ly</span>.
+
+ <li>Font sizes can now truly be scaled continuously: the <code>font-size</code>
+is similar to the old <code>font-relative-size</code>, but may be set to
+fractional values; the closest design size will be scaled to achieve
+the desired size. As a side-effect, there are now no longer
+limitations in using smaller fonts (eg. grace notes) at small staff
+sizes.
+
+ <li>Stem tips are now also engraved with rounded corners.
+
+ <li>The placement of accidentals on chords and ledgered notes is improved.
+
+</ul>
+
--- /dev/null
+<!--
+ Translation of GIT committish: <FILL-IN-HEAD-COMMITTISH>
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. Refer to `UPDATE A TRANSLATION'
+ in README for details.
+!-->
+
+<title>LilyPond version 2.4 released</title>
+<pre>
+
+
+Dear music enthusiasts,
+
+
+LilyPond version 2.4 was released today!
+
+
+LilyPond is a program for making beautiful music notation. It is
+open source/free software, and is available for all popular operating
+systems. It runs on most Unix flavors --including Linux and MacOS X--
+and MS Windows. Use it for your music too!
+
+With this release, LilyPond does not rely anymore on TeX to do titling
+and page layout, but distributes page breaks optimally to produce
+evenly spaced pages, while respecting user specified turning points.
+
+The slur formatting code has been completely rewritten, and now yields
+classical engraving quality results for most cases.
+
+In addition, version 2.4 adds fret diagrams, a safe execution mode for
+webserver use, a further simplified input format, better typography
+for ledger lines, many bugfixes and a fully revised and updated
+manual.
+
+Go and grab it at
+
+ http://lilypond.org
+
+
+
+A big thank-you goes out to our contributors:
+
+Carl Sorensen
+David Svoboda
+Guy Gascoigne-Piggford
+Heikki Junes
+Hendrik Maryns
+Kristof Bastiaensen
+Lisa Opus Goldstein
+Mats Bengtsson
+Michael Welsh Duggan
+Peter Lutek
+Werner Lemberg
+
+
+Also thanks to our bug-hunters:
+
+Antti Kaihola, Bertalan Fodor, Brian Clements, Christian Hitz,
+Christoph Ludwig, Christophe Papazian, Daniel Berjón Díez, Dave
+Phillips, David Bobroff, David Brandon, Doug Asherman, Ed Jackson,
+Heinz Stolba, Jefferson dos Santos Felix, Karl Hammar, Marco Gusy,
+Martin Norbäck, Matthias Neeracher, Maurizio Tomasi, Michael
+Kiermaier, Pascal Legris, Peter Rosenbeck, Russ Ross, Stephen Pollei,
+Thomas Scharlowski, Will Oram, Yuval Harel,
+
+
+Happy music printing,
+
+
+
+The LilyPond development team,
+
+Han-Wen Nienhuys & Jan Nieuwenhuizen
+Core development
+
+Graham Percival
+Documentation Editor
+
+Erik Sandberg
+Bugmeister
+
+Pedro Kroeger
+Build meister
+
+</pre>
--- /dev/null
+<!--
+ Translation of GIT committish: <FILL-IN-HEAD-COMMITTISH>
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. Refer to `UPDATE A TRANSLATION'
+ in README for details.
+!-->
+
+<title>LilyPond version 2.6 now available for download</title>
+<pre>
+LilyPond - Music Notation for Everyone.
+
+
+
+LilyPond is a free/open source package to create beautiful music
+notation. With version 2.6, LilyPond is now truly for everyone.
+
+- For every platform
+
+ LilyPond now installs in a snap on Windows, MacOS X, and any version
+ of Linux. Get up and running in minutes!
+
+- For every language
+
+ Pango text formatting lets you print Unicode lyrics in your favorite
+ script and font.
+
+- For every application
+
+ Create SVG files, and edit them in Inkscape.
+
+
+
+In addition, version 2.6 adds support for
+
+ - staves starting anywhere on the page
+ - solfa notation
+ - arrowed lines
+ - better auto-beaming
+ - circled text
+ - string-number notation
+ - better ledger line formatting
+ - score separators
+ - cleaner syntax for text markup
+ - pagebreaks around titles
+ - stemlets on beams
+ - easier titles customization
+ - direct PostScript or SVG output
+ - (te)TeX no longer necessary
+ - revised manual
+ - website now translated into Dutch and French
+
+Grab it at
+
+ http://lilypond.org
+
+</pre>
--- /dev/null
+<title>LilyPond 2.8 now available</title>
+
+<h1>LilyPond version 2.8 available - prettier music than ever</h1>
+
+Utrecht the Netherlands--March 21, 2006.
+<p>
+After 9 months of backbreaking hacking, the LilyPond Development Team
+is proud to announce LilyPond 2.8.0, software for better looking music
+notation.
+<p>
+
+The inspiration for LilyPond came when two befriended musicians got
+annoyed with the bland and boring look of computer print-out. Every
+musician prefers reading beautiful music, so couldn't we programmers
+solve that printing problem?
+<p>
+
+LilyPond just does that: it prints music in the best traditions of
+classical engraving with minimum fuss. Don't waste time on tuning
+spacing, moving around symbols, or shaping slurs. Impress friends and
+colleagues with sharp sheet music!
+
+
+<h2>New stuff</h2>
+
+Version 2.8 replaces the latest "stable" release 2.6. The newest
+version adds three major typographical improvements
+
+<ul>
+<li>Page Layout Options
+<p>
+
+ Creating good page layout has never been easier: tune vertical
+ spacing per system, set the total number of systems, visualize page
+ parameters.
+
+<li>Exact proportional spacing
+<p>
+
+ Algorithmic notation buffs will love this option, where mixed exotic
+ rhythms and nested tuplets still produce mathematically consistent
+ spacing.
+
+<li>Vastly improved formatting for ties
+<p>
+
+ Get the best tied chord formatting anywhere, and if that doesn't
+ satisfy you, just override each offending tie configuration.
+</ul>
+
+That's not all, check out
+<pre>
+ <a
+ href="http://lilypond.org/doc/v2.8/Documentation/topdocs/NEWS.html">
+ http://lilypond.org/doc/v2.8/Documentation/topdocs/NEWS.html
+ </a>
+</pre>
+for all changes.
+
+
+<h2>Style your own pond</h2>
+
+Most of the new features have been implemented at user's requests. By
+ordering custom code from the designers of LilyPond you too can get
+your favorite gripe fixed. Read the <a
+href="http://lilypond.org/web/sponsor/">sponsorship pages</a> to learn
+more.
+<p>
+Download your ready-to-run binary from
+<pre>
+<a href="http://lilypond.org">lilypond.org</a>
+</pre>
+We have them for MacOS X (ppc), Windows, Linux and FreeBSD.
+<p>
+
+Happy music printing!
+
+<h3>Development team</h3>
+
+
+Han-Wen Nienhuys - Core development<br>
+
+Jan Nieuwenhuizen - Core development<br>
+Erik Sandberg - Bug Meister<br>
+Pedro Kroger - Build Meister<br>
+Graham Percival - Documentation Editor<br>
+Mats Bengtsson - Support Guru<br>
+
+<h3>Contributors</h3>
+
+Erlend Aasland, Heikki Junes, Joe Neeman, Johannes Schindelin, Nicolas
+Sceaux, Werner Lemberg, Yoshinobu Ishizaki.
+
+<h3>Sponsors</h3>
+
+Aaron Mehl, Basil Crow, Bertalan Fodor, Christian Ebert, Henrik Frisk,
+Jay Hamilton, Jamie Bullock, John Mandereau, D. Josiah Boothby, Kieren
+MacMillan, Kris Shaffer, Mark van den Borre, Mike Rolish,
+Muziekacademie Lede, Nancho Alvarez, Nicolas Sceaux, Sean Reed, Steve
+Doonan, Sven Axelsson, Trent Johnston, Trevor Bača, Yoshinobu
+Ishizaki, and Vicente Solsona Dellá.
+
+<h3>Bug hunters and suggestions</h3>
+
+Alan Stern, Andrea Valle, Bertalan Fodor, Bob Broadus, Bruce
+Fairchild, Cameron Horsburgh, Chris Sawer, Christian Ebert, Christian
+Hitz, Darius Blasband, David Bobroff, David Raleigh Arnold, Donald
+Axel, Don Blaheta, Dunstan Vavasour, Edward Neeman, Eduardo Vieira,
+Ernesto Gancedo, François Vion, Frédéric Bron, Geoff Horton, Gianluca
+D., Hans Forbrich, Hoang Nguyen, Joe Neeman, Jordi Nadal, Jukka
+Akkanen, Kieren Richard MacMillan, Lambros Lambrou, Laura Conrad,
+Libero Mureddu, Marcus Macauley, Mark Steinheuser, Matevž Jekovec,
+Michael Kiermaier, Michael Welsh Duggan, Milan Zamazal, Nicolas
+Mayencourt, Orm Finnendahl, Patrick K Welton, Paul Scott, Ralph
+Little, Richard Schoeller, Robert Vlatasy, Roman Kurakin, Russell
+Lang, Scott Russell, Sean Reed, Seng Liang, Steve Doonan, Steven
+Weber, Sven Axelsson, Thomas Scharkowski, Thomas Bushnell BSG, Toine
+Schreurs, Trent Johnston, Trevor Bača, Vicente Solsona Dellá, Vincenzo
+Colonnella, Will Oram, and Wolfgang Hoffmann.
projects / lilypond.git / commitdiff