LilyPond... notazione musicale per tutti
LilyPond è un programma di incisione musicale e il suo scopo è produrre spartiti
musicali della migliore qualità possibile. Introduce nelle stampe prodotte dai
computer l’estetica della musica incisa secondo i metodi tradizionali. LilyPond è
software libero e parte del Progetto GNU.
Musica bella per gli occhi
LilyPond è uno strumento potente e flessibile, adatto a ogni genere di
spartito, per esempio musica classica (come nell’esempio precedente di J.S.
Bach), notazione complessa, musica antica, musica moderna, tablatura,
musica vocale, spartiti semplificati, materiali didattici, grandi
progetti orchestrali, output personalizzato e perfino grafici Schenker.
Guarda la galleria di Esempi e lasciati ispirare!
Introduzione
Il nostro obiettivo
LilyPond è nato dal desiderio di due musicisti di andare oltre
l’aspetto meccanico degli spartiti realizzati col computer. I musicisti
preferiscono leggere musica ben scritta; allora, perché dei programmatori
non potrebbero scrivere un software in grado di produrre partiture eleganti?
Il risultato è un programma che crea delle belle partiture seguendo le
migliori tradizioni della tipografia musicale. Si prende cura in modo
programmatico dei dettagli della formattazione, consentendo a compositori,
trascrittori e editori di prestare attenzione alla musica invece di
cercare di migliorare l’output del proprio software. Gli esecutori
otterranno delle parti che permetteranno loro di concentrarsi sull’
esecuzione della musica invece che sulla sua lettura.
Funzionalità
Eccellente incisione classica
LilyPond offre ai musicisti la possibilità di realizzare spartiti eleganti
e comodi da leggere. La sua comunità di sviluppatori ha dedicato migliaia
di ore a sviluppare un potente software di incisione musicale che produce
spartiti di ottima qualità. Tutte le impostazioni di stile, i font e gli
algoritmi di LilyPond sono ispirati alla migliore musica incisa a mano.
L’output di LilyPond ha lo stesso aspetto netto, equilibrato ed elegante
delle migliori partiture classiche. Questo è stato approfondito nel nostro
Saggio.
Input testuale
Tutto è esplicito
LilyPond elabora input testuale, contenente tutte le informazioni
sul contenuto della partitura e può essere facilmente letto
da un altro essere umano così come da un altro programma. Non ci
sono oscure impostazioni nascoste dietro le voci di un menù né
salvataggi in file binari.
Questo concetto è approfondito in Input testuale.
Le modifiche manuali sono robuste e tracciabili
Se devi cambiare qualcosa relativo all’aspetto, tale modifica
sarà visibile anche nel file di input in una forma comprensibile
per un essere umano. Quindi sei sempre in grado di rivedere
le tracce di ciò che hai fatto. Se tu dovessi per sbaglio
rendere il file non funzionante, puoi facilmente ripristinare
o modificare qualsiasi decisione senza essere costretto a
usare una funzione Annulla.
I file di testo sono a prova di fallimento e di futuro
I file di testo sono molto robusti contro la corruzione di file. Ed
essendo leggibili dall’essere umano sei anche sempre in grado di
interpretarli pur non avendo accesso al programma che li ha creati.
Gestisci le tue partiture col controllo di versione
I file di testo possono essere gestiti con un programma di controllo
di versione. Provalo e sperimenta gli infiniti e diversi meccanismi
per annullare e ripetere le modifiche nonché la possibilità di avere la
storia dell’intero sviluppo delle tue partiture. Il controllo di
versione potrebbe anche aprirti la strada a nuovi metodi di lavoro
(collaborativo).
Usabilità
Scelte di formattazione efficaci
Impieghi minor tempo nel correggere l’output; LilyPond imposta la formattazione
corretta fin dall’inizio. Determina da solo lo spazio, e le interruzioni di
linea e di pagina per fornire un’impaginazione proporzionata e uniforme. Le
collisioni tra testo, note e accordi vengono risolte e le legature di portamento
e le codette sono posizionate automaticamente!
Unisci musica e testo
Inserisci frammenti di musica nel testo senza dover tagliare e incollare
immagini. Integra comodamente la musica in LaTeX o HTML, o aggiungi la
musica in OpenOffice.org e LibreOffice con
OOoLilypond.
Esistono anche dei plugin che permettono di usare l’input di LilyPond in blog e
wiki, rendendo possibile la collaborazione online.
Accessibilità
L’input testuale rende inoltre la scrittura musicale possibile per gli utenti
con serie inabilità fisiche. Gli utenti con problemi di coordinazione che non
sono in grado di usare la tastiera o il mouse possono usare software di
riconoscimento vocale per modificare i file LilyPond. Anche gli utenti
totalmente privi di vista possono usare un software di lettura dello schermo per
scrivere file LilyPond – un’operazione impossibile nei programmi di scrittura
musicale basati su interfaccia grafica. Puoi vedere una partitura spettacolare
in Esempi.
Diversità degli editor
Molti sviluppatori, loro stessi attivi utenti LilyPond, hanno scritto
degli strumenti volti proprio a rendere più veloce e efficace il processo
di modifica dei file LilyPond; non sei quindi legato a una singola interfaccia
utente ma puoi usare strumenti diversi per compiti diversi. Puoi perfino
usare un editor LilyPond ricco di funzionalità a casa e l’app blocco note
del telefonino per modificare i file quando sei in movimento. Alcuni esempi
sono elencati in Editing facilitato.
Progettazione estendibile
Facile gestione dei fogli di stile
Tutte le impostazioni possono essere modificate per soddisfare il tuo
personale gusto tipografico. Puoi facilmente scrivere dei fogli di
stile che cambiano qualsiasi elemento dell’aspetto predefinito delle
partiture create da LilyPond. Dato che anche questi sono scritti come
file di testo e possono essere salvati in file separati, puoi semplicemente
passare da un foglio di stile all’altro per produrre partiture con un
aspetto o una disposizione completamente diversi.
Desideri stampare una partitura su foglio A4 e proiettarla con un
proiettore, un sistema per pagina? Il motore della formattazione di
LilyPond genererà entrambi dallo stesso input.
Aggiungi le tue funzioni
Se questo non è ancora abbastanza, c’è sempre il linguaggio di scripting
Scheme, che può accedere al motore della formattazione di LilyPond allo
stesso di livello cui ci accede LilyPond stesso, rendendolo uno strumento
molto potente. Impostazioni, variabili e funzioni sono tutte
documentate nell’esauriente manuale di riferimento del programma..
Elabora le partiture tramite la programmazione
I file di input di LilyPond possono essere modificati o perfino generati
da programmi e script, per esempio per la composizionoe algoritmica.
Ma si può accedere al contenuto musicale anche per analizzarlo o per
gestire dei frammenti di input in un database. Non ci sono limiti
tranne la tua immaginazione.
Creare nuovi strumenti che usano LilyPond
LilyPond, non essendo un monolitico programma a interfaccia grafica ma
uno strumento a linea di comando, può essere usato anche da altre applicazioni.
È così possibile dare il potere di incisione di LilyPond a certi
programmi come un’applicazione web. Esistono già vari strumenti online
che usano LilyPond.
Ambiente
Ottimo supporto
LilyPond gira su tutte le piattaforme più note: GNU/Linux, MacOS X, e
Windows. LilyPond include un’ampia documentazione e centinaia di file
di esempio. C’è un’attiva comunità di utenti che risponde alle
domande nella mailing list internazionale dedicata agli utenti LilyPond,
offrendo gentilmente il proprio aiuto. I tempi di risposta sono solitamente
molto brevi e spesso vengono suggerite brillanti soluzioni dei problemi
segnalati. Grazie alla stretta interazione col team di sviluppo, tali
soluzioni sono spesso incluse in LilyPond stesso. Maggiori informazioni
in Comunità.
Software libero
LilyPond può essere scaricato gratuitamente! Sì: è gratuito. Scaricalo
dalla pagina di download.
È anche software libero. Viene distribuito col codice sorgente e il
permesso di modificarlo e copiarlo. Sei infastidito da un
malfunzionamento, o desideri una nuova funzionalità? Puoi aggiungerla tu
stesso, o pagare qualcun altro per farlo.
Maggiori informazioni in Libertà.
E ora?
Non sei ancora convinto? Guarda alcuni specifici Esempi. Se hai
già deciso di provare LilyPond, per prima cosa informati sul nostro
Input testuale.
Esempi
Begli esempi
LilyPond è uno strumento potente e flessibile per scrivere ogni tipo
di musica. Dai un’occhiata alla galleria di esempi e lasciati ispirare!
Musica Classica
Questo brano per organo di J.S. Bach rappresenta un tipico esempio di
progetto LilyPond.
(clicca per ingrandire)
Notazione Complessa
Questo esempio tratto dalle Goyescas di Enrique Granados mostra alcune
delle funzionalità tipografiche più avanzate, come la ripartizione di travature
e gambi tra più righi e l’evidenziazione dello svolgimento di una singola voce
mediante tratti spezzati.
(clicca per ingrandire)
Musica Antica
LilyPond supporta anche vari tipi di notazione antica, come
questo passaggio di canto gregoriano.
(clicca per ingrandire)
Musica Moderna
I compositori contemporanei ritengono che LilyPond sia molto adatto a
visualizzare notazioni non convenzionali. Ecco un estratto dal Čáry di
Trevor Bača, per flauto basso non accompagnato.
(clicca per ingrandire)
Creazione efficiente e flessibile di materiali da esecuzione
A partire dallo stesso codice
sorgente possono essere creati diversi materiali d’esecuzione. Questo è
un estratto della partitura di Nicolas Sceaux del Giulio Cesare di Handel, in partitura
completa, riduzione per canto e pianoforte, e parte per violino.
(clicca per ingrandire)
(clicca per ingrandire)
(clicca per ingrandire)
Intavolatura
LilyPond supporta la notazione per intavolatura, che può essere personalizzata
per adattarsi a ogni strumento che ne fa uso. Il rigo
dell’intavolatura viene generato automaticamente dalle note inserite per
il pentagramma.
(clicca per ingrandire)
Musica Vocale
LilyPond è eccellente per la musica vocale di tutti i generi, dagli inni
sacri all’opera. Ecco un mottetto medievale con requisiti leggermente
insoliti. Il tenor è scritto in un metro diverso dagli altri,
ma deve essere allineato come se fosse nello stesso tempo.
LilyPond gestisce questo aspetto in modo molto elegante. Si notino anche gli
incipit con chiave in stile Vaticana, i gambi barrati a indicare note plicate,
e le parentesi quadre sulle sezioni legate.
(clicca per ingrandire)
Spartiti semplificati
È semplice creare spartiti semplificati con melodia, testo,
nomi degli accordi, e tastiere. In questo esempio puoi vedere alcuni
dei diagrammi di tastiera predefiniti, ma questi possono essere ampiamente
personalizzati per adattarsi a quasi ogni situazione.
(clicca per ingrandire)
Materiali didattici
LilyPond è molto indicato anche per creare materiali didattici.
Ecco un esempio di un semplice esercizio di contrappunto.
(clicca per ingrandire)
Grandi Progetti
LilyPond è ottimo anche per progetti ad ampio respiro come opere o lavori per
un’orchestra sinfonica al completo. Inoltre l’input testuale permette
una maggiore accessibilità – questo esempio è stato realizzato
da Hu Haipeng, un compositore cieco.
(clicca per ingrandire)
Output personalizzato
Un breve estratto del Klavierstück II di Stockhausen per dimostrare la
capacità di LilyPond di fornire output personalizzato.
(clicca per ingrandire)
Grafici Schenker
L’output di default può essere ampiamente modificato. Ecco un’analisi
Schenkeriana di grande effetto, creata da Kris Schaffer, per un articolo
su Linux Journal.
I colori sono stati aggiunti per migliorare la visibilità.
(clicca per ingrandire)
E ora?
Non sei ancora convinto? LilyPond è Software Libero, e ti dà
Libertà. Se hai già deciso di provare LilyPond, per prima cosa
informati sul nostro Input testuale.
Libertà
Software Libero
GNU LilyPond è scritto e mantenuto
da una comunità di appassionati. È distribuito secondo la
GNU General Public License e la GNU Free Documentation License, che danno a tutti la libertà di correggere,
modificare, ed estendere il programma. Creare della bella musica non
dovrebbe richiedere centinaia di dollari di software!
Quali sono i vantaggi per gli utenti?
-
Nessuna spesa: scaricalo e provalo! Cosa hai da perdere?
-
Condivisione: se ti piace il programma, dai una copia a amici,
insegnanti, studenti, e colleghi!
-
Codice sorgente disponibile: se sei curioso di sapere come LilyPond crea
la notazione, puoi vedere esattamente come viene fatto.
-
Estendibile: puoi aggiungere funzionalità, correggere i malfunzionamenti, e cambiare
il funzionamento. Se non sei un programmatore, puoi assumere qualcuno
per questi compiti.
Questo potrebbe non sembrare interessante agli occhi dei musicisti non
professionisti, ma l’abilità di estendere il software può avere un grande
valore per i compositori di professione, le aziende e gli studiosi.
-
Sicurezza per il futuro: se un’azienda commerciale fallisce, cosa succede
alla musica in formato elettronico che dipende dai loro prodotti? Questa
preoccupazione non riguarda LilyPond; anche se tutto il team di sviluppo
abbandonasse il progetto (molto improbabile), il programma continuerebbe ad
essere legalmente disponibile per la copia, la modifica e la distribuzione.
Perché gli sviluppatori di LilyPond “regalano” la loro opera?
La maggior parte di noi vede lo sviluppo di LilyPond come un hobby o un
lavoro volontario. Quindi la vera domanda è: “perché si lavora come volontari”?
-
Divertimento: lavorare per raggiungere un obiettivo può essere divertente,
soprattutto quando si lavora in gruppo!
-
Obiettivi condivisi: vogliamo tutti delle belle partiture, ma poche persone
hanno la competenza (e nessuno ha il tempo!), per creare un programma
che può gestire tutte le situazioni. Ma lavorando insieme – una
persona migliora il codice per le travature automatiche, un’altra migliora
la forma delle legature, e una terza persona scrive la documentazione
spiegando come usare queste funzionalità – possiamo raggiungere
il nostro obiettivo usando solo una frazione dello sforzo individuale.
-
“Cultura del dono”: il movimento del Software Libero
ha creato vari grandi progetti software, come
GNU/Linux,
Mozilla Firefox, e
Battle for Wesnoth. Avendo
tratto vantaggio da questi progetti, alcuni sviluppatori vogliono “dare
in cambio” qualcosa alla comunità.
-
Esperienza di lavoro: contribuire a progetti di software libero è un ottimo modo
per esercitarsi nel programmare, scrivere la documentazione, o progettare.
Questa esperienza ha aiutato alcuni sviluppatori ad ottenere offerte di
lavoro o borse di studio.
E ora?
Non sei ancora convinto? Leggi il saggio sulla nostra filosofia
tipografica in Storia. Se hai già deciso di provare
LilyPond, per prima cosa informati sul nostro Input testuale.
Storia
Saggio
Abbiamo un lungo saggio che descrive l’estetica computazionale:
l’arte di creare la bellezza con un computer.
Si tratta di una lettura interessante se ti incuriosisce una discussione
approfondita delle nostre idee principali. A causa del suo volume, il
saggio è presentato come "manunale". Se vuoi leggerlo ora, passa a
Saggio. Tuttavia, se vuoi solo una rapida introduzione a LilyPond,
per ora puoi saltarlo.
E ora?
Non sei ancora convinto? Guarda alcune delle Produzioni e
degli spartiti dei nostri utenti. Se hai già deciso di provare
LilyPond, per prima cosa informati sul nostro Input testuale.
Produzioni
Produzioni che usano LilyPond
Qui puoi informarti sulle persone che usano LilyPond nelle
loro produzioni, sia per le esecuzioni della loro musica
che per le partiture pubblicate.
Concerti
LilyPond è stato usato per esecuzioni in tutto il mondo.
In evidenza:
-
Aurélien Bello ha arrangiato una
versione del Der Rosenkavalier di Richard Strauss
per quattro voci e un’orchestra da camera di tredici musicisti. È stata
commissionata dall’Orchestra Filarmonica di Berlino i cui membri saranno
gli esecutori il
2 e 6 Aprile
al Festspielhaus, Baden-Baden, e poi il
26 Aprile
alla Großer Saal della Philarmonie di Berlino.
Siamo contenti di vedere musicisti di tale reputazione suonare leggendo
partiture prodotte da LilyPond (e, a quanto si dice, sono molto soddisfatti
di queste partiture).
Aurélien ha anche riorchestrato il Der Ring des Nibelungen di Richard Wagner in una
versione ridotta per bambini.
Scritta per un’orchestra sinfonica standard, ma con un cast ridotto di
cantanti, è stata eseguita dalla
Radio-Sinfonieorchester Berlin
nell’Aprile 2014 al teatro Atze Musiktheater di Berlino. Il direttore
era Heiko Matthias Förster.
-
Joe Smeets ha creato una partitura per il libro di bambini Zing Mee
(Sing along) di Annie M.G. pubblicato da
Querido – ISBN 9789045106205;
le partiture delle prove del coro per la traduzione olandese del
Saint Nicolas di Benjamin Britten sono state eseguite dal
Muziektheater Hollands Diep nel 2011;
www.muziektheaterhollandsdiep.nl.
Ha lavorato anche alla partitura e alle parti di un arrangiamento del
Boris Godounov di Moussurgsky per quartetto d’archi, pianoforte e
percussioni, eseguito nel 2014, di nuovo dal Muziektheater Hollands Diep.
-
Un’edizione critica di Enea nel Lazio (1760) di Tommaso
Traetta, opera seria con libretto di Vittorio Amedeo Cigna-Santi, in
quattro parti:
Parte prima
Parte seconda
Parte terza
Parte quarta
Creata da
Luca Rossetto Casel
per la sua tesi di dottorato.
-
Pictures at an exhibition di Mussorgsky, riorchestrata e diretta
da Aurélien Bello con
la Junge Philharmonie Brandenburg
nell’Ottobre 2011 e nell’Aprile 2012.
-
Kieren MacMillan, compositore e
direttore musicale. Le sue opere recenti sono: Go Thy Way,
eseguita da Salt Lake Choral Artists nel Marzo 2012; Just Out of Reach Suite
eseguita dal
Chrysalis Duo ; thrafsmata eseguita nel Luglio 2011 dal
Pittsburgh New Music Ensemble.
-
Anonymous Student Compliment or Complaint, di
Mike Solomon, che ha vinto il
Left Coast Composition Contest del 2011,
a cui hanno partecipato 172 opere provenienti da 22 paesi.
Altre opere comprendono Norman (age 1) per clarinetto solo, eseguita all’Electroacoustic
Music Festival (FEMF) della University of Florida
nell’Ottobre 2010.
-
Edizione moderna della Serenata Erminia di Alessandro Scarlatti,
curata da Thomas Griffin, Musicologo (Roma, Italia). Eseguita il 22
Ottobre 2010 presso la Galleria di Palazzo Zevallos Stigliano, Napoli,
Italia. Alessandro Scarlatti 2010,
per celebrare il 350° compleanno del compositore.
-
Esecuzione dell’ Armide di Lully da parte della
Mercury Baroque,
15-16 Maggio 2009, a Houston, Texas (spartiti realizzati da
Nicolas Sceaux).
-
Brani strumentali dall’ Hippolyte et Aricie di Rameau presso
la St. James’s Church a Manhattan, 8 Maggio 2009, di Frederick Renz
e il suo complesso Early Music New York (spartiti realizzati da
Nicolas Sceaux).
-
Affaire étrangère, un opera di
Valentin Villenave
basata su un libretto francese di
Lewis Trondheim. La prima rappresentazione ha avuto luogo il 1 Febbraio 2009 presso
L’Opéra National di Montpellier, Francia.
Spartiti pubblicati
-
Mutopia Project,
oltre 1500 spartiti di brani di musica classica liberamente scaricabili, e
principale vetrina delle partiture fatte con LilyPond.
-
Adoro Music Publishing,
spartiti di alta qualità di musica sacra, disponibili per il
download immediato o nel tradizionale supporto cartaceo.
-
The Shady Lane Publishing,
una “piccola casa editrice musicale” il cui obiettivo è promuovere una
nuova forma di economia della musica più vicina ai musicisti e agli
amanti della musica.
E ora?
Non sei ancora convinto? Leggi le Recensioni di alcuni nostri utenti.
Se hai già deciso di provare LilyPond, per prima cosa informati sul
nostro Input testuale.
Recensioni
Articoli pubblicati
-
Aprile 2011
Linux Magazine pubblica un
articolo intitolato
Projects on the Move. È un articolo introduttivo a MuseScore,
LilyPond e Chordii. L’autrice Carla Schroder afferma “LilyPond è un
programma a linea di comando, ma non lasciatevi spaventare dalla mancanza
dell’interfaccia grafica; LilyPond è facile da usare e da imparare”, e fornisce
anche un esempio pratico.
-
Maggio 2010
Peter Kirn, sul sito Create Digital Music, pubblica una
recensione di LilyPond. Offre un parere equilibrato sull’utilizzo, elogia l’alta qualità della
notazione in LilyPond e consiglia di provarlo.
-
Settembre 2009
La rivista tedesca LinuxUser ha scritto un
articolo su LilyPond.
-
Agosto 2009
Ann Drinan, sul sito
Polyphonic.org, presenta
i commenti di due bibliotecari di un’orchestra che parlano dell’uso del
software per gestire le loro biblioteche.
-
Giugno 2009
In un articolo
pubblicato nella rivista annuale francese National Conservatory Parent
Association, Valentin Villenave, compositore francese e collaboratore di
LilyPond, spiega come le licenze libere, e in particolare le partiture
realizzate con LilyPond, siano uno strumento per rendere la musica scritta
accessibile a tutti.
-
Febbraio 2008
In alcuni articoli sul suo sito personale, Andrew Hawryluk confronta Finale
e LilyPond in termini generali, e valuta in dettaglio le capacità di
incisione di entrambi i software. Il secondo articolo è un’analisi
istruttiva dei problemi di incisione nel Preludio n. 6 per pianoforte
di Rachmaninoff, e include dei confronti con un’edizione di riferimento
incisa a mano.
-
Giugno 2006
DistroWatch premia LilyPond e
scrive
“Signore e signori, siamo lieti di annunciare che, in base alle
richieste dei lettori, la donazione di Maggio 2006 di DistroWatch
è stata assegnata a LilyPond (€190.00) e Lua (US$250.00).”
-
Dicembre 2005
Linux Journal pubblica un articolo
intitolato Crea dei fantastici grafici Schenker con GNU LilyPond. È un articolo
approfondito e pratico con attraenti grafici di LilyPond. L’autore
Kris Shaffer commenta “GNU LilyPond genera una grafica splendida
che fa sembrare le alternative commerciali di second’ordine.”
-
20 Agosto 2005
La rivista belga De Standaard fa un’indagine sulle motivazioni degli
autori di Software Libero in un articolo intitolato
Delen van KENNIS zonder WINSTBEJAG (Condividere la conoscenza senza
scopo di lucro) nel suo ‘DS2 bijlage’. LilyPond viene citato come esempio
e l’articolo è disseminato di estratti di un’intervista email
con Jan Nieuwenhuizen. Questo articolo segna la prima comparsa di
LilyPond su un periodico tradizionale, su carta stampata.
-
Giugno 2005
Un articolo in francese sul rilascio di LilyPond 2.6 è apparso su
linuxfr.org.
-
Ottobre 2004
Gli editor di Computer!Totaal, una rivista olandese di computer,
nel numero di Ottobre 2004
descrivono LilyPond come: “Meraviglioso software
libero […] Gli spartiti prodotti da
LilyPond sono incredibilmente belli […] un sistema molto potente che
può fare praticamente qualsiasi cosa.”
-
Luglio, Agosto 2004
Dave Phillips ha scritto un articolo introduttivo per
Linux Journal: At
the sounding edge: LilyPond, parte
uno e
due.
-
Marzo 2004
Chris Cannam
ha intervistato
Han-Wen Nienhuys e Jan Nieuwenhuizen su linuxmusician.com
(sito originale defunto). Questa intervista è stata anche recensita in una
storia di slashdot.
-
Febbraio 2004
Il cantante jazz Gail Selkirk scrive su
Tuffarsi in LilyPond. “… puoi scrivere lead sheet o parti per
un’intera orchestra, e i risultati possono essere sorprendenti.”
Computer Music Special,
numero CMS06.
Utenti testimonial
Carter Brey, primo violoncellista, New York Philharmonic
“… Ho composto un paio di bis per violoncello solista
che ho scritto con LilyPond e che sto per consegnare a Schirmer per
la pubblicazione. Scommetto che la loro versione non sarà elegante
nemmeno la metà della mia!”
Orm Finnendahl, professore di Composizione, Musikhochschule Freiburg
“Anche se non conosco [LilyPond] molto bene ancora, sono
molto colpito. Ho usato il programma per scrivere un mottetto di
Josquin Desprez in notazione mensurale e non c’è dubbio che
lilypond batte facilmente tutti gli altri programmi di notazione per
quanto riguarda la velocità, la facilità d’uso e la resa grafica!”
Darius Blasband, compositore (Bruxelles, Belgio)
“[…dopo la prima prova d’orchestra] ho ricevuto molti
complimenti per la qualità degli spartiti. Ancora più
importante: sebbene LilyPond fornisca molti trucchi per migliorare
l’aspetto degli spartiti, quello che l’orchestra ha ricevuto da me è
l’output grezzo e privo di ritocchi.”
Kieren MacMillan, compositore (Toronto, Canada)
“grazie e complimenti al team di sviluppo per il suo incredibile
lavoro. Non ho mai visto niente che possa avvicinarsi all’output di
LilyPond – sono assolutamente sicuro che le mie necessità nel campo
dell’editoria musicale saranno soddisfatte oltre ogni aspettativa usando
questo fantastico programma. […] l’output predefinito di LilyPond […] ha
un aspetto migliore delle recenti pubblicazioni ‘professionali’ con cui
l’ho confrontato (ovvero quasi qualsiasi spartito della Warner Bros, e anche molti
dei più recenti delle ‘vecchie case editrici’). […]”
“Li batte tutti, Finale/Sibelius/Igor/, qualsiasi cosa!!!”
Chris Cannam, principale programmatore di RoseGarden
“LilyPond è ovviamente il super gorilla [della
grande tipografia musicale].”
“Il modo in cui la musica viene inserita in LilyPond mi fa pensare in
modo più musicale – a volte non sapevo come dire a
Lily di incidere qualcosa, per poi capire che anche se
avessi ottenuto ciò che il compositore voleva, la musica sarebbe
stata più difficile da leggere. LilyPond mi rende molto più facile
lavorare nel mio doppio ruolo di editor e incisore.”
“Uso esclusivamente LilyPond per la mia giovane casa editrice
musicale. Praticamente senza eccezione, ogni compositore
è rimasto colpito dalla qualità tipografica quando gli sono state
presentate le bozze della sua musica pronte per la pubblicazione. Il merito
va in parte a me – ho dedicato molto tempo a modificare
l’output, soprattutto le legature di valore (specialmente negli accordi) – ma LilyPond mi
dà un eccellente punto di partenza, un’interfaccia molto intuitiva, e la
possibilità di modificare totalmente qualsiasi cosa, se ho tempo per
farlo. Sono sicuro che nessun prodotto commerciale può avvicinarsi a questo.”
David Bobroff, trombone basso, Iceland Symphony Orchestra
“Credo che LilyPond sia un grande programma […] Più imparo LilyPond
e più mi piace!”
Vaylor Trucks, chitarrista elettrico
(connesso con i Yes)
“Sono impressionato da LilyPond […]”
“QUESTO È IL MIGLIOR PROGRAMMA MAI ESISTITO!!!”
“Mille grazie a tutti per il vostro duro lavoro e la vostra dedizione!”
“Con LilyPond avevo una specie di relazione di amore-odio. Amore
perché il primo spartito che ho visto era così meraviglioso! Il modo in cui
LilyPond viene presentato mente sulla sua bellezza, è troppo modesto! […] Via
via che LilyPond migliora, costantemente, e io vedo come le cose vengono
fatte in Scheme, ho sempre meno frustrazioni. Comunque,
quello che voglio dire è: grazie per metterci a disposizione LilyPond, è davvero
un ottimo programma.”
Werner Lemberg, Direttore d’orchestra presso il Theatre a Koblenz, Germania e brillante hacker GNU
“Comunque, LilyPond fa un lavoro incredibilmente buono!”
Paul Davis, sviluppatore di JACK e Ardour
“Credo che [LilyPond è] un programma incredibile, e produce output
davvero meraviglioso. Quando ho letto un’intervista a suo proposito l’anno
scorso, ne ho parlato entusiasticamente a molti miei amici e ho mostrato
loro le sue potenzialità.”
“Ho il più profondo rispetto verso LilyPond e i suoi creatori
e collaboratori perché so per esperienza personale quanto difficile
possa essere questo tipo di software.”
David Cameron, Musicista, tipografo professionista e utente di lunga data di SCORE
“Il mio sincero ringraziamento per tutti coloro che contribuiscono a questo progetto. Negli
anni ’90 sono stato un esperto utente di SCORE per le grandi case tipografiche,
ma credo che LilyPond mi permetta finalmente di ottenere sulla pagina esattamente
ciò che voglio, specialmente quando non si tratta di una pratica "standard".”
Input testuale
“Compilare” Musica
(clicca per ingrandire)
LilyPond è un sistema compilato: viene eseguito su un file di testo
che descrive la musica. L’output risultante può essere visualizzato sullo
schermo o stampato. In un certo senso, LilyPond è più simile a un linguaggio
di programmazione che a un software grafico per la creazione di spartiti.
Non si scrive la musica trascinando le note da una barra degli strumenti grafica
e mettendole su una partitura che si aggiorna in modo dinamico; si scrive
musica digitando del testo. Questo testo viene interpretato (o “compilato”)
da LilyPond, che produce degli spartiti di elevata qualità.
Chi è abituato alle interfacce grafiche dovrà imparare un nuovo modo di
lavorare, ma ne vale assolutamente la pena se si considerano i risultati!
Nota: Presentiamo una rapida panoramica del nostro input testuale – non è
complicato come sembra! Non c’è bisogno di comprendere ogni dettaglio
di questi esempi; la nostra documentazione per i principianti si occupa
di tutto questo a un ritmo molto più graduale.
È semplice come l’A B C
Le note vengono codificate con lettere e numeri. I comandi speciali sono
inseriti con barre inverse (backslash).
Le alterazioni si ottengono con nomi diversi: si aggiunge -is per
il diesis, e -es per il bemolle (questi sono i nomi delle note in
olandese, ma sono disponibili altre lingue). LilyPond calcola dove mettere
le alterazioni.
Musica Pop
Testo e accordi possono essere combinati per ottenere uno spartito semplificato:
Parti per orchestra
Il file di input contiene le note del brano musicale. La partitura e
le parti possono essere ottenute da un solo file di input, cosicché la
modifica di una nota interesserà sempre la partitura e le parti. Per
poter includere la stessa musica in più punti, occorre assegnare alla
musica una “variabile” (un nome).
Questa variabile viene poi usata in una parte singola (qui trasposta, con
pause abbreviate che si estendono per diverse misure):
La stessa variabile viene utilizzata nella partitura completa (qui in
altezza reale):
Documentazione per il principiante
Comprendiamo il fatto che molti utenti trovino questo modo di scrivere
musica un po’ strano. Per questo motivo, abbiamo scritto un’ampia documentazione
per aiutare i nuovi utenti, a cominciare dal manuale di Apprendimento. Il Manuale
di Apprendimento è il luogo migliore da cui iniziare, perché molte domande trovano
risposta prima ancora di manifestarsi!
Talvolta i nuovi utenti sono confusi, senza motivo, da alcuni aspetti del
comportamento di LilyPond. Leggi la documentazione prima di pensare che
LilyPond non stia funzionando bene.
Informazioni più approfondite sono disponibili nei Manuali.
Ben Lemon, un utente di LilyPond, ha creato una serie di
video tutorial
sul suo blog che sono rivolti ai nuovi utenti.
Editing facilitato
(clicca per ingrandire)
L’obiettivo primario di LilyPond è produrre spartiti di
elevata qualità; creare un interfaccia grafica (GUI)
ci distrarrebbe da questo scopo. Tuttavia esistono altri
progetti che hanno lo scopo di rendere più facile la creazione di file
di input per LilyPond.
Alcuni ambienti di editing includono l’evidenziatura della sintassi, il
completamento automatico dei comandi, e modelli preimpostati. Altri
programmi forniscono una vera e propria interfaccia grafica che consente
la manipolazione diretta di una partitura grafica. Per maggiori informazioni,
si veda Editing facilitato.
Editing facilitato
Denemo
(clicca per ingrandire)
http://denemo.org
Denemo è un editor grafico che genera codice sorgente LilyPond
e permette anche la riproduzione audio. Consente agli utenti di vedere
il codice sorgente LilyPond in parallelo alla visualizzazione grafica. Modifiche
manuali del codice possono essere attaccate a note, accordi etc. e vengono
salvate nel file di Denemo, così che gli utenti possano continuare a
modificare il documento tramite l’interfaccia grafica.
Se si muove il cursore nel codice LilyPond si muove anche il cursore
nella visualizzazione grafica, e qualsiasi errore di sintassi nelle tue modifiche
manuali al codice LilyPond viene evidenziato nella visualizzazione testuale
quando elaborato da lì.
Editor online su browser
LilyBin
http://lilybin.com
Un editor LilyPond che si usa nel browser e permette di scrivere una
partitura direttamente senza dover installare LilyPond, purché si sia
connessi a Internet.
Editor testuali
Emacs
http://www.gnu.org/software/emacs/
Emacs è un editor di testo che ha la capacità di comprendere molti
diversi linguaggi informatici. Emacs è un editor molto estendibile
e può essere usato come ambiente di sviluppo integrato (IDE).
C’è una ‘modalità lilypond’ che fornisce le definizioni del
linguaggio per poter lavorare con i file sorgente di LilyPond.
Uno sviluppatore ha scritto
lyqi, una
modalità primaria di Emacs.
A meno che tu non sia un utente esperto di Emacs, probabilmente
dovresti usare un altro editor per scrivere file di input di
LilyPond.
Maggori informazioni su come impostare Emacs si trovano in
LilyPond e gli editor di testo.
Vim
http://www.vim.org
Vim è un editor di testo minimale che deriva dal vecchio editor Unix
vi. Anch’esso è estendibile e configurabile.
A meno che tu non sia un utente esperto di Vim, probabilmente
dovresti usare un altro editor per scrivere file di input di
LilyPond.
Puoi trovare maggiori informazioni sulla configurazione di Emacs e Vim in
LilyPond e gli editor di testo.
TeXShop
http://pages.uoregon.edu/koch/texshop/
L’editor TeXShop per MacOS X può essere potenziato per eseguire LilyPond,
lilypond-book e convert-ly all’interno dell’editor,
usando le estensioni disponibili presso:
http://users.dimi.uniud.it/~nicola.vitacolonna/home/content/lilypond-scripts
Altri programmi che possono esportare in codice LilyPond
Editor di partiture, intavolature e MIDI:
-
bwwtolily tenta
di convertire un file
.bww o .bmw in formato
LilyPond. Anche se non tutti gli abbellimenti verranno
convertiti correttamente (questo vale soprattutto per i
piobaireachd), il programma li elenca.
-
Canorus, un editor di partiture, può anche
esportare in formato LilyPond, ma è un software ancora in beta. Gli utenti
che vogliono provarlo sono benvenuti.
-
OOoLilypond,
un’estensione di OpenOffice.org che converte i file di LilyPond in immagini
incluse nei documenti di OpenOffice.org. Sebbene non sia più sviluppato,
sembra che funzioni ancora nella versione 4.
-
Enc2ly è un programma GNU/Linux che
converte uno spartito Encore in uno in formato LilyPond.
-
go-enc2ly è uno strumento Go che
converte i file Encore in formato LilyPond. È stato creato grazie al
lavoro di ricerca e di reverse engineering di Felipe Castro, che ha
modificato file .enc esistenti e li ha caricati usando la versione demo 4.55.
-
NtEd,
un editor di partiture basato sulla libreria
Cairo, supporta in via sperimentale
l’esportazione in formato LilyPond.
-
NW2LY è un programma scritto in C# che converte una canzone di NoteWorthy
in formato LilyPond.
-
Ripple è
un programma che aiuta a creare partiture e parti; include un modo per
mischiare insieme opere musicali diverse in una singola partitura o parte.
-
Rosegarden, un sequencer audio
e MIDI, che ha anche un editor per le partiture con un solo rigo.
Generatori di codice algoritmici:
-
Abjad, una API
Python per il Formalized Score
Control progettata per aiutare i compositori a costruire pezzi complessi
di notazione LilyPond in modo iterativo e incrementale.
-
FOMUS, (FOrmat MUSic)
è uno strumento di notazione musicale per compositori di
musica elettronica. È scritto nel linguaggio di programmazione
LISP ed è stato testato su vari interpreti. È disponibile
anche un port in C++.
-
Strasheela, un
ambiente costruito sul
Mozart Programming System.
Altri programmi che non sono più sviluppati attivamente
-
LilyPondTool è stato
creato come plugin dell’editor di testo jEdit.
-
LilyKDE è stato sostituito da
Frescobaldi; esiste soltanto come
LilyKDE3 per KDE 3.5 e lilypond-KDE4 per KDE 4.1.
-
LilyComp è un programma grafico di
inserimento note, che si comporta in modo molto simile a un tastierino numerico
che produce note nella sintassi di LilyPond.
-
MuseScore, un editor di partiture.
L’esportazione in formato LilyPond è stata rimossa nella versione 2.0 ma
sono ancora disponibili e scaricabili le versioni precedenti su
Sourceforge.
-
NoteEdit, che importava
MusicXML, è stato "forkato"
in
NtEd
e Canorus.
-
Rumor, un convertitore
realtime monofonico da MIDI a LilyPond.
-
tunefl
Con tunefl è possibile scrivere le partiture direttamente online,
senza bisogno di installare LilyPond sul proprio computer. Consente di
sperimentare tutte le funzionalità del programma usando una comoda
interfaccia web.
-
TuxGuitar, un editor e riproduttore
multitraccia per tablatura, include un visualizzatore della partitura e può
esportare in formato LilyPond.
E ora?
Sei ora pronto per Scaricare LilyPond.
Non sei ancora convinto? Molti compositori, musicisti e direttori
hanno imparato a scrivere musica nel nostro formato di input. Utenti
esperti raccontano addirittura di poter scrivere una partitura completa
in LilyPond più velocemente che con una tastiera di pianoforte o col mouse in
un programma a interfaccia grafica! Forse vuoi riesaminare
le Funzionalità, gli Esempi, o la
Libertà che LilyPond fornisce, o informarti sulle
Produzioni degli utenti e le Recensioni. Inoltre, il nostro
approccio all’estetica computazionale della tipografia musicale classica
viene spiegato nella nostra Storia.
Download
Download per LilyPond 2.19.65
Nota: I link alla versione stabile di LilyPond si possono trovare su
lilypond.org
Nota: LilyPond è un compositore tipografico musicale basato su testo; è
più simile a un linguaggio di programmazione che a un editor grafico di
spartiti. Prima di scaricare LilyPond, dovresti informarti sul
nostro Input testuale.
Unix
Nota: LilyPond è un compositore tipografico musicale basato su testo; è
più simile a un linguaggio di programmazione che a un editor grafico di
spartiti. Prima di scaricare LilyPond, dovresti informarti sul
nostro Input testuale.
Pacchetti generici o pacchetti specifici di una distribuzione?
Molte distribuzioni includono LilyPond nei loro repository ma i loro
pacchetti sono spesso molto più vecchi della versione
stabile corrente. Anche se questi pacchetti più vecchi sono più facili
da installare, consigliamo caldamente di usare i nostri pacchetti
generici. In questo caso, controlla che il tuo editor LilyPond stia usando
la versione corretta. Vedi Editing facilitato.
Pacchetti generici
Download
Installazione
Digita in un terminale:
cd PERCORSO-ALLA-DIRECTORY-DI-DOWNLOAD
sh lilypond-2.18.2-SISTEMA-OPERATIVO.sh
Disinstallazione
Digita nel terminale:
uninstall-lilypond
Aiuto
Digita nel terminale:
sh lilypond-2.18.2-OS-TYPE.sh --help
Compilare un file
Nota: Queste istruzioni presumono che tu abbia familiarità con i
programmi a linea di comando. Se stai usando uno dei programmi descritti in
Editing facilitato, in caso di problemi nel compilare un file consulta
la documentazione di quei programmi.
Passo 1. Crea il tuo file ‘.ly’
Crea un file di testo chiamato ‘test.ly’ e scrivi:
\version "2.18.2"
{
c' e' g' e'
}
Passo 2. Compila (da linea di comando)
Per elaborare ‘test.ly’, scrivi il seguente comando nel terminale:
lilypond test.ly
Vedrai qualcosa di simile a questo:
GNU LilyPond 2.18.2
Processing `test.ly'
Parsing...
Interpreting music...
Preprocessing graphical objects...
Solving 1 page-breaking chunks...[1: 1 pages]
Drawing systems...
Layout output to `test.ps'...
Converting to `./test.pdf'...
Success: compilation successfully completed
Passo 3. Visualizza l’output
Puoi visualizzare o stampare il file ‘test.pdf’.
MacOS X
Nota: LilyPond è un compositore tipografico musicale basato su testo; è
più simile a un linguaggio di programmazione che a un editor grafico di
spartiti. Prima di scaricare LilyPond, dovresti informarti sul
nostro Input testuale.
Pacchetti
Download
Installazione
Clicca due volte sul file scaricato, poi trascinalo dove preferisci.
Disinstallazione
Elimina la cartella LilyPond.app.
Esecuzione da linea di comando
Nota: Se ti trovi bene con le istruzioni per interfaccia grafica sotto, puoi
ignorare queste istruzioni.
MacOS X su linea di comando
Il modo più comodo di eseguire script lilypond è impostare dei propri
script d’ “aiuto”.
-
Crea una directory dove salvare questi script,
mkdir -p ~/bin
cd ~/bin
-
Crea un file chiamato
lilypond che contiene
Nota: DIR si trova generalmente in /Applications/
-
Crea file simili
lilypond-book,
convert-ly, e un qualsiasi altro script tu voglia usare,
sostituendo bin/lilypond con bin/convert-ly
(o il nome di un altro programma).
-
Rendi eseguibile il file,
chmod u+x lilypond
-
Ora, aggiungi questa directory alla tua variabile path. Modifica (o crea) un file
chiamato
.profile nella tua home in modo che contenga
export PATH=$PATH:~/bin
Questo file deve finire con una linea bianca.
Lanciare i singoli script
Gli script — come lilypond-book, convert-ly,
abc2ly, e anche lilypond stesso — sono inclusi
nel file .app per MacOS X.
Gli script possono essere eseguiti dalla linea di comando anche lanciandoli
direttamente:
Lo stesso vale per tutti gli altri script in quella directory, come
lilypond-book e convert-ly.
Compilare un file
Nota: Queste istruzioni presumono che tu stia usando il programma
LilyPond. Se stai usando uno dei programmi descritti in
Editing facilitato, in caso di problemi consulta la documentazione
di quei programmi.
Passo 1. Crea il tuo file ‘.ly’
Clicca due volte su LilyPond.app, si aprirà un file di esempio.
Dai menu in cima a sinistra dello schermo seleziona
File > Salva.
Scegli un nome per il tuo file, ad esempio ‘test.ly’.
Passo 2. Compila (con LilyPad)
Dagli stessi menu seleziona
Compile > Typeset.
Si aprirà una nuova finestra che mostra i messaggi di log della compilazione
del file che hai appena salvato.
Passo 3. Visualizza l’output
Quando la compilazione è finita, un file PDF con lo stesso nome del file
originale viene creato e automaticamente aperto nel visualizzatore
PDF predefinito, che lo mostrerà sullo schermo.
Altri comandi
Per creare nuovi file per LilyPond, comincia col selezionare
File > New
oppure File > Open per aprire e modificare file esistenti che
hai salvato precedentemente.
Devi salvare qualsiasi nuova modifica fatta al file prima di cliccare
Compile > Typeset e se il file PDF non compare controlla se
ci sono degli errori nella finestra dei messaggi di log.
Se non stai usando il visualizzatore d’anteprima PDF incluso nel sistema
operativo del Mac e un file PDF generato da una compilazione precedente
è aperto, qualsiasi compilazione successiva potrebbe non riuscire a
generare un PDF aggiornato finché non chiudi l’originale.
Legalese
Si riconoscono il copyright e i marchi di tutti i loghi e le immagini dei prodotti.
L’ “immagine X” non è un marchio registrato. È stato creato da
Nihonjoe e
CyberSkull, e
posto sotto la GNU Free Documentation License versione 1.2 o successive.
Abbiamo trovato l’immagine su
questa pagina di Wikimedia Commons.
Windows
Nota: LilyPond è un compositore tipografico musicale basato su testo; è
più simile a un linguaggio di programmazione che a un editor grafico di
spartiti. Prima di scaricare LilyPond, dovresti informarti sul
nostro Input testuale.
Pacchetti
Download
Installazione
-
Trova il file scaricato e clicca due volte su di esso per avviare
il programma di installazione. Segui le istruzioni fornite dal programma.
Ti consigliamo di lasciare tutte le opzioni di installazione attivate e
e di usare il percorso di installazione predefinito. Clicca sul bottone ‘Finito’
quando la procedura di installazione è terminata. LilyPond è ora installato.
Disinstallazione
Per disinstallare LilyPond:
-
Trova la cartella LilyPond dal menu ‘Start’ e clicca sull’icona
‘Disinstalla’. Clicca il bottone ‘Finito’ quando la disinstallazione
è terminata.
-
Oppure dal Pannello di Controllo, trova e seleziona LilyPond e poi
scegli l’opzione per disinstallare/rimuovere il software. Clicca il
bottone ‘Finish’ quando la disinstallazione è terminata.
Esecuzione da linea di comando
Nota: Se ti trovi bene con le istruzioni per interfaccia grafica sotto, puoi
ignorare queste istruzioni.
Windows da linea di comando
Il modo più comodo per eseguire LilyPond è aggiungere la cartella
che contiene i file eseguibili di LilyPond alla variabile d’ambiente
“Path”.
-
Apri il “Sistema” nel Panello di Controllo,
seleziona la linguetta Avanzate e clicca il bottone Variabili d’Ambiente.
-
Seleziona la variabile “Path” dalla lista delle variabili d’ambiente
e clicca il bottone Modifica.
Apparirà una finestra intitolata “Modifica il Sistema delle Variabili”;
attacca al “valore della variabile” il nome della cartella
che contiene i file eseguibili di LilyPond, in questo modo:
[pre-set paths];DIR\LilyPond\usr\bin
Nota: DIR generalmente è C:\Program Files (x86) per i
sistemi a 64 bit e C:\Program Files per quelli a 32 bit.
e clicca il bottone “OK” per chiudere la finestra.
Lanciare singoli file eseguibili
I file eseguibili di LilyPond
– come lilypond, lilypond-book, convert-ly, etc. –
possono essere eseguiti dalla linea di comando lanciandoli:
lilypond test.ly
Compilare un file
Nota: Queste istruzioni presumono che tu stia usando l’editor LilyPad
incluso nel programma. Se stai usando uno dei programmi descritti in
Editing facilitato, in caso di problemi nel compilare un file consulta
la documentazione di quei programmi.
Passo 1. Crea il tuo file ‘.ly’
Clicca due volte sull’icona di LilyPond sulla scrivania e si aprirà
un file di esempio.
Dai menu che appaiono in cima al file di esempio seleziona
File > Salva come. Non usare File > Salva
per il file di esempio perché non funzionerà finché non gli darai
un nome di file valido per LilyPond.
Scegli un nome per il tuo file, ad esempio ‘test.ly’.
Passo 2. Compila
Per trasformare il file LilyPond in una partitura devi compilarlo. Ci sono
vari modi per farlo: il trascina e rilascia (drag and drop), il clic destro,
il doppio clic o la linea di comando (nel riquadro del terminale DOS). Vediamo
intanto i primi tre.
1. Trascinare e rilasciare il file sull’icona LilyPond che si trova nel desktop.
Sembrerà che non stia accadendo niente, ma dopo pochi secondi dovresti
vedere due nuovi file sul desktop: ‘test.log’ e ‘test.pdf’.
2. Cliccare col tasto destro sul file e dal menu contestuale a comparsa scegliere
Generate PDF.
3. O semplicemente cliccare due volte su ‘test.ly’.
Passo 3. Visualizza l’output
‘test.pdf’ contiene il file ‘test.ly’ compilato. Cliccalo due
volte e si dovrebbe aprire in un visualizzatore PDF:
Altri comandi
Per creare un nuovo file, per prima cosa seleziona File > Nuovo se
hai aperto un file creato in precedenza oppure File > Apri
per aprire e modificare i file che hai salvato prima. Puoi modificare
un file anche facendo un clic destro e selezionando Edit Source.
Devi salvare qualsiasi nuova modifica prima di compilare. Se il file
PDF non viene creato o l’output non è quello che ti aspetti, controlla
se ci sono degli errori nel file di log che sarà stato creato durante
il tentativo di compilazione.
Questo file di log viene sovrascritto ogni volta che compili il file LilyPond.
Se visualizzi il file in un lettore PDF, devi chiudere il PDF se desideri
provare una nuova compilazione, perché potrebbe non riuscire a creare il
nuovo file PDF mentre è ancora aperto per la visualizzazione.
Legalese
Si riconoscono il copyright e i marchi di tutti i loghi e le immagini dei prodotti.
L’ “immagine con quattro rettangoli colorati” non è un marchio
registrato. È stato creato da
Rohitbd ed è
posto sotto la GNU Free Documentation License versione 1.2. Abbiamo
trovato l’immagine su
questa pagina di Wikimedia Commons.
Sorgente
Nota: LilyPond è un compositore tipografico musicale basato su testo; è
più simile a un linguaggio di programmazione che a un editor grafico di
spartiti. Prima di scaricare LilyPond, dovresti informarti sul
nostro Input testuale.
Nota: Noi non ti consigliamo di cercare di compilare
LilyPond; le necessità di quasi tutti gli utenti sono meglio soddisfatte
dalla versione precompilata.
Vecchi download
Nota: LilyPond è un compositore tipografico musicale basato su testo; è
più simile a un linguaggio di programmazione che a un editor grafico di
spartiti. Prima di scaricare LilyPond, dovresti informarti sul
nostro Input testuale.
Tutte le versioni
Per un vasto elenco di tutte le versioni (vecchie e nuove), si veda
il nostro sito di download.
GPL
Licenza Software
GNU LilyPond è distribuito secondo la GNU General Public License.
Un’introduzione a questa licenza, e le ragioni per cui l’abbiamo scelta,
si trovano in Libertà.
GNU General Public License
Version 3, 29 June 2007
| | Copyright © 2007 Free Software Foundation, Inc. http://fsf.org/
Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.
|
Preamble
The GNU General Public License is a free, copyleft license for
software and other kinds of works.
The licenses for most software and other practical works are designed
to take away your freedom to share and change the works. By contrast,
the GNU General Public License is intended to guarantee your freedom
to share and change all versions of a program—to make sure it remains
free software for all its users. We, the Free Software Foundation,
use the GNU General Public License for most of our software; it
applies also to any other work released this way by its authors. You
can apply it to your programs, too.
When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
them if you wish), that you receive source code or can get it if you
want it, that you can change the software or use pieces of it in new
free programs, and that you know you can do these things.
To protect your rights, we need to prevent others from denying you
these rights or asking you to surrender the rights. Therefore, you
have certain responsibilities if you distribute copies of the
software, or if you modify it: responsibilities to respect the freedom
of others.
For example, if you distribute copies of such a program, whether
gratis or for a fee, you must pass on to the recipients the same
freedoms that you received. You must make sure that they, too,
receive or can get the source code. And you must show them these
terms so they know their rights.
Developers that use the GNU GPL protect your rights with two steps:
(1) assert copyright on the software, and (2) offer you this License
giving you legal permission to copy, distribute and/or modify it.
For the developers’ and authors’ protection, the GPL clearly explains
that there is no warranty for this free software. For both users’ and
authors’ sake, the GPL requires that modified versions be marked as
changed, so that their problems will not be attributed erroneously to
authors of previous versions.
Some devices are designed to deny users access to install or run
modified versions of the software inside them, although the
manufacturer can do so. This is fundamentally incompatible with the
aim of protecting users’ freedom to change the software. The
systematic pattern of such abuse occurs in the area of products for
individuals to use, which is precisely where it is most unacceptable.
Therefore, we have designed this version of the GPL to prohibit the
practice for those products. If such problems arise substantially in
other domains, we stand ready to extend this provision to those
domains in future versions of the GPL, as needed to protect the
freedom of users.
Finally, every program is threatened constantly by software patents.
States should not allow patents to restrict development and use of
software on general-purpose computers, but in those that do, we wish
to avoid the special danger that patents applied to a free program
could make it effectively proprietary. To prevent this, the GPL
assures that patents cannot be used to render the program non-free.
The precise terms and conditions for copying, distribution and
modification follow.
TERMS AND CONDITIONS
- Definitions.
“This License” refers to version 3 of the GNU General Public License.
“Copyright” also means copyright-like laws that apply to other kinds
of works, such as semiconductor masks.
“The Program” refers to any copyrightable work licensed under this
License. Each licensee is addressed as “you”. “Licensees” and
“recipients” may be individuals or organizations.
To “modify” a work means to copy from or adapt all or part of the work
in a fashion requiring copyright permission, other than the making of
an exact copy. The resulting work is called a “modified version” of
the earlier work or a work “based on” the earlier work.
A “covered work” means either the unmodified Program or a work based
on the Program.
To “propagate” a work means to do anything with it that, without
permission, would make you directly or secondarily liable for
infringement under applicable copyright law, except executing it on a
computer or modifying a private copy. Propagation includes copying,
distribution (with or without modification), making available to the
public, and in some countries other activities as well.
To “convey” a work means any kind of propagation that enables other
parties to make or receive copies. Mere interaction with a user
through a computer network, with no transfer of a copy, is not
conveying.
An interactive user interface displays “Appropriate Legal Notices” to
the extent that it includes a convenient and prominently visible
feature that (1) displays an appropriate copyright notice, and (2)
tells the user that there is no warranty for the work (except to the
extent that warranties are provided), that licensees may convey the
work under this License, and how to view a copy of this License. If
the interface presents a list of user commands or options, such as a
menu, a prominent item in the list meets this criterion.
- Source Code.
The “source code” for a work means the preferred form of the work for
making modifications to it. “Object code” means any non-source form
of a work.
A “Standard Interface” means an interface that either is an official
standard defined by a recognized standards body, or, in the case of
interfaces specified for a particular programming language, one that
is widely used among developers working in that language.
The “System Libraries” of an executable work include anything, other
than the work as a whole, that (a) is included in the normal form of
packaging a Major Component, but which is not part of that Major
Component, and (b) serves only to enable use of the work with that
Major Component, or to implement a Standard Interface for which an
implementation is available to the public in source code form. A
“Major Component”, in this context, means a major essential component
(kernel, window system, and so on) of the specific operating system
(if any) on which the executable work runs, or a compiler used to
produce the work, or an object code interpreter used to run it.
The “Corresponding Source” for a work in object code form means all
the source code needed to generate, install, and (for an executable
work) run the object code and to modify the work, including scripts to
control those activities. However, it does not include the work’s
System Libraries, or general-purpose tools or generally available free
programs which are used unmodified in performing those activities but
which are not part of the work. For example, Corresponding Source
includes interface definition files associated with source files for
the work, and the source code for shared libraries and dynamically
linked subprograms that the work is specifically designed to require,
such as by intimate data communication or control flow between those
subprograms and other parts of the work.
The Corresponding Source need not include anything that users can
regenerate automatically from other parts of the Corresponding Source.
The Corresponding Source for a work in source code form is that same
work.
- Basic Permissions.
All rights granted under this License are granted for the term of
copyright on the Program, and are irrevocable provided the stated
conditions are met. This License explicitly affirms your unlimited
permission to run the unmodified Program. The output from running a
covered work is covered by this License only if the output, given its
content, constitutes a covered work. This License acknowledges your
rights of fair use or other equivalent, as provided by copyright law.
You may make, run and propagate covered works that you do not convey,
without conditions so long as your license otherwise remains in force.
You may convey covered works to others for the sole purpose of having
them make modifications exclusively for you, or provide you with
facilities for running those works, provided that you comply with the
terms of this License in conveying all material for which you do not
control copyright. Those thus making or running the covered works for
you must do so exclusively on your behalf, under your direction and
control, on terms that prohibit them from making any copies of your
copyrighted material outside their relationship with you.
Conveying under any other circumstances is permitted solely under the
conditions stated below. Sublicensing is not allowed; section 10
makes it unnecessary.
- Protecting Users’ Legal Rights From Anti-Circumvention Law.
No covered work shall be deemed part of an effective technological
measure under any applicable law fulfilling obligations under article
11 of the WIPO copyright treaty adopted on 20 December 1996, or
similar laws prohibiting or restricting circumvention of such
measures.
When you convey a covered work, you waive any legal power to forbid
circumvention of technological measures to the extent such
circumvention is effected by exercising rights under this License with
respect to the covered work, and you disclaim any intention to limit
operation or modification of the work as a means of enforcing, against
the work’s users, your or third parties’ legal rights to forbid
circumvention of technological measures.
- Conveying Verbatim Copies.
You may convey verbatim copies of the Program’s source code as you
receive it, in any medium, provided that you conspicuously and
appropriately publish on each copy an appropriate copyright notice;
keep intact all notices stating that this License and any
non-permissive terms added in accord with section 7 apply to the code;
keep intact all notices of the absence of any warranty; and give all
recipients a copy of this License along with the Program.
You may charge any price or no price for each copy that you convey,
and you may offer support or warranty protection for a fee.
- Conveying Modified Source Versions.
You may convey a work based on the Program, or the modifications to
produce it from the Program, in the form of source code under the
terms of section 4, provided that you also meet all of these
conditions:
-
The work must carry prominent notices stating that you modified it,
and giving a relevant date.
-
The work must carry prominent notices stating that it is released
under this License and any conditions added under section 7. This
requirement modifies the requirement in section 4 to “keep intact all
notices”.
-
You must license the entire work, as a whole, under this License to
anyone who comes into possession of a copy. This License will
therefore apply, along with any applicable section 7 additional terms,
to the whole of the work, and all its parts, regardless of how they
are packaged. This License gives no permission to license the work in
any other way, but it does not invalidate such permission if you have
separately received it.
-
If the work has interactive user interfaces, each must display
Appropriate Legal Notices; however, if the Program has interactive
interfaces that do not display Appropriate Legal Notices, your work
need not make them do so.
A compilation of a covered work with other separate and independent
works, which are not by their nature extensions of the covered work,
and which are not combined with it such as to form a larger program,
in or on a volume of a storage or distribution medium, is called an
“aggregate” if the compilation and its resulting copyright are not
used to limit the access or legal rights of the compilation’s users
beyond what the individual works permit. Inclusion of a covered work
in an aggregate does not cause this License to apply to the other
parts of the aggregate.
- Conveying Non-Source Forms.
You may convey a covered work in object code form under the terms of
sections 4 and 5, provided that you also convey the machine-readable
Corresponding Source under the terms of this License, in one of these
ways:
-
Convey the object code in, or embodied in, a physical product
(including a physical distribution medium), accompanied by the
Corresponding Source fixed on a durable physical medium customarily
used for software interchange.
-
Convey the object code in, or embodied in, a physical product
(including a physical distribution medium), accompanied by a written
offer, valid for at least three years and valid for as long as you
offer spare parts or customer support for that product model, to give
anyone who possesses the object code either (1) a copy of the
Corresponding Source for all the software in the product that is
covered by this License, on a durable physical medium customarily used
for software interchange, for a price no more than your reasonable
cost of physically performing this conveying of source, or (2) access
to copy the Corresponding Source from a network server at no charge.
-
Convey individual copies of the object code with a copy of the written
offer to provide the Corresponding Source. This alternative is
allowed only occasionally and noncommercially, and only if you
received the object code with such an offer, in accord with subsection
6b.
-
Convey the object code by offering access from a designated place
(gratis or for a charge), and offer equivalent access to the
Corresponding Source in the same way through the same place at no
further charge. You need not require recipients to copy the
Corresponding Source along with the object code. If the place to copy
the object code is a network server, the Corresponding Source may be
on a different server (operated by you or a third party) that supports
equivalent copying facilities, provided you maintain clear directions
next to the object code saying where to find the Corresponding Source.
Regardless of what server hosts the Corresponding Source, you remain
obligated to ensure that it is available for as long as needed to
satisfy these requirements.
-
Convey the object code using peer-to-peer transmission, provided you
inform other peers where the object code and Corresponding Source of
the work are being offered to the general public at no charge under
subsection 6d.
A separable portion of the object code, whose source code is excluded
from the Corresponding Source as a System Library, need not be
included in conveying the object code work.
A “User Product” is either (1) a “consumer product”, which means any
tangible personal property which is normally used for personal,
family, or household purposes, or (2) anything designed or sold for
incorporation into a dwelling. In determining whether a product is a
consumer product, doubtful cases shall be resolved in favor of
coverage. For a particular product received by a particular user,
“normally used” refers to a typical or common use of that class of
product, regardless of the status of the particular user or of the way
in which the particular user actually uses, or expects or is expected
to use, the product. A product is a consumer product regardless of
whether the product has substantial commercial, industrial or
non-consumer uses, unless such uses represent the only significant
mode of use of the product.
“Installation Information” for a User Product means any methods,
procedures, authorization keys, or other information required to
install and execute modified versions of a covered work in that User
Product from a modified version of its Corresponding Source. The
information must suffice to ensure that the continued functioning of
the modified object code is in no case prevented or interfered with
solely because modification has been made.
If you convey an object code work under this section in, or with, or
specifically for use in, a User Product, and the conveying occurs as
part of a transaction in which the right of possession and use of the
User Product is transferred to the recipient in perpetuity or for a
fixed term (regardless of how the transaction is characterized), the
Corresponding Source conveyed under this section must be accompanied
by the Installation Information. But this requirement does not apply
if neither you nor any third party retains the ability to install
modified object code on the User Product (for example, the work has
been installed in ROM).
The requirement to provide Installation Information does not include a
requirement to continue to provide support service, warranty, or
updates for a work that has been modified or installed by the
recipient, or for the User Product in which it has been modified or
installed. Access to a network may be denied when the modification
itself materially and adversely affects the operation of the network
or violates the rules and protocols for communication across the
network.
Corresponding Source conveyed, and Installation Information provided,
in accord with this section must be in a format that is publicly
documented (and with an implementation available to the public in
source code form), and must require no special password or key for
unpacking, reading or copying.
- Additional Terms.
“Additional permissions” are terms that supplement the terms of this
License by making exceptions from one or more of its conditions.
Additional permissions that are applicable to the entire Program shall
be treated as though they were included in this License, to the extent
that they are valid under applicable law. If additional permissions
apply only to part of the Program, that part may be used separately
under those permissions, but the entire Program remains governed by
this License without regard to the additional permissions.
When you convey a copy of a covered work, you may at your option
remove any additional permissions from that copy, or from any part of
it. (Additional permissions may be written to require their own
removal in certain cases when you modify the work.) You may place
additional permissions on material, added by you to a covered work,
for which you have or can give appropriate copyright permission.
Notwithstanding any other provision of this License, for material you
add to a covered work, you may (if authorized by the copyright holders
of that material) supplement the terms of this License with terms:
-
Disclaiming warranty or limiting liability differently from the terms
of sections 15 and 16 of this License; or
-
Requiring preservation of specified reasonable legal notices or author
attributions in that material or in the Appropriate Legal Notices
displayed by works containing it; or
-
Prohibiting misrepresentation of the origin of that material, or
requiring that modified versions of such material be marked in
reasonable ways as different from the original version; or
-
Limiting the use for publicity purposes of names of licensors or
authors of the material; or
-
Declining to grant rights under trademark law for use of some trade
names, trademarks, or service marks; or
-
Requiring indemnification of licensors and authors of that material by
anyone who conveys the material (or modified versions of it) with
contractual assumptions of liability to the recipient, for any
liability that these contractual assumptions directly impose on those
licensors and authors.
All other non-permissive additional terms are considered “further
restrictions” within the meaning of section 10. If the Program as you
received it, or any part of it, contains a notice stating that it is
governed by this License along with a term that is a further
restriction, you may remove that term. If a license document contains
a further restriction but permits relicensing or conveying under this
License, you may add to a covered work material governed by the terms
of that license document, provided that the further restriction does
not survive such relicensing or conveying.
If you add terms to a covered work in accord with this section, you
must place, in the relevant source files, a statement of the
additional terms that apply to those files, or a notice indicating
where to find the applicable terms.
Additional terms, permissive or non-permissive, may be stated in the
form of a separately written license, or stated as exceptions; the
above requirements apply either way.
- Termination.
You may not propagate or modify a covered work except as expressly
provided under this License. Any attempt otherwise to propagate or
modify it is void, and will automatically terminate your rights under
this License (including any patent licenses granted under the third
paragraph of section 11).
However, if you cease all violation of this License, then your license
from a particular copyright holder is reinstated (a) provisionally,
unless and until the copyright holder explicitly and finally
terminates your license, and (b) permanently, if the copyright holder
fails to notify you of the violation by some reasonable means prior to
60 days after the cessation.
Moreover, your license from a particular copyright holder is
reinstated permanently if the copyright holder notifies you of the
violation by some reasonable means, this is the first time you have
received notice of violation of this License (for any work) from that
copyright holder, and you cure the violation prior to 30 days after
your receipt of the notice.
Termination of your rights under this section does not terminate the
licenses of parties who have received copies or rights from you under
this License. If your rights have been terminated and not permanently
reinstated, you do not qualify to receive new licenses for the same
material under section 10.
- Acceptance Not Required for Having Copies.
You are not required to accept this License in order to receive or run
a copy of the Program. Ancillary propagation of a covered work
occurring solely as a consequence of using peer-to-peer transmission
to receive a copy likewise does not require acceptance. However,
nothing other than this License grants you permission to propagate or
modify any covered work. These actions infringe copyright if you do
not accept this License. Therefore, by modifying or propagating a
covered work, you indicate your acceptance of this License to do so.
- Automatic Licensing of Downstream Recipients.
Each time you convey a covered work, the recipient automatically
receives a license from the original licensors, to run, modify and
propagate that work, subject to this License. You are not responsible
for enforcing compliance by third parties with this License.
An “entity transaction” is a transaction transferring control of an
organization, or substantially all assets of one, or subdividing an
organization, or merging organizations. If propagation of a covered
work results from an entity transaction, each party to that
transaction who receives a copy of the work also receives whatever
licenses to the work the party’s predecessor in interest had or could
give under the previous paragraph, plus a right to possession of the
Corresponding Source of the work from the predecessor in interest, if
the predecessor has it or can get it with reasonable efforts.
You may not impose any further restrictions on the exercise of the
rights granted or affirmed under this License. For example, you may
not impose a license fee, royalty, or other charge for exercise of
rights granted under this License, and you may not initiate litigation
(including a cross-claim or counterclaim in a lawsuit) alleging that
any patent claim is infringed by making, using, selling, offering for
sale, or importing the Program or any portion of it.
- Patents.
A “contributor” is a copyright holder who authorizes use under this
License of the Program or a work on which the Program is based. The
work thus licensed is called the contributor’s “contributor version”.
A contributor’s “essential patent claims” are all patent claims owned
or controlled by the contributor, whether already acquired or
hereafter acquired, that would be infringed by some manner, permitted
by this License, of making, using, or selling its contributor version,
but do not include claims that would be infringed only as a
consequence of further modification of the contributor version. For
purposes of this definition, “control” includes the right to grant
patent sublicenses in a manner consistent with the requirements of
this License.
Each contributor grants you a non-exclusive, worldwide, royalty-free
patent license under the contributor’s essential patent claims, to
make, use, sell, offer for sale, import and otherwise run, modify and
propagate the contents of its contributor version.
In the following three paragraphs, a “patent license” is any express
agreement or commitment, however denominated, not to enforce a patent
(such as an express permission to practice a patent or covenant not to
sue for patent infringement). To “grant” such a patent license to a
party means to make such an agreement or commitment not to enforce a
patent against the party.
If you convey a covered work, knowingly relying on a patent license,
and the Corresponding Source of the work is not available for anyone
to copy, free of charge and under the terms of this License, through a
publicly available network server or other readily accessible means,
then you must either (1) cause the Corresponding Source to be so
available, or (2) arrange to deprive yourself of the benefit of the
patent license for this particular work, or (3) arrange, in a manner
consistent with the requirements of this License, to extend the patent
license to downstream recipients. “Knowingly relying” means you have
actual knowledge that, but for the patent license, your conveying the
covered work in a country, or your recipient’s use of the covered work
in a country, would infringe one or more identifiable patents in that
country that you have reason to believe are valid.
If, pursuant to or in connection with a single transaction or
arrangement, you convey, or propagate by procuring conveyance of, a
covered work, and grant a patent license to some of the parties
receiving the covered work authorizing them to use, propagate, modify
or convey a specific copy of the covered work, then the patent license
you grant is automatically extended to all recipients of the covered
work and works based on it.
A patent license is “discriminatory” if it does not include within the
scope of its coverage, prohibits the exercise of, or is conditioned on
the non-exercise of one or more of the rights that are specifically
granted under this License. You may not convey a covered work if you
are a party to an arrangement with a third party that is in the
business of distributing software, under which you make payment to the
third party based on the extent of your activity of conveying the
work, and under which the third party grants, to any of the parties
who would receive the covered work from you, a discriminatory patent
license (a) in connection with copies of the covered work conveyed by
you (or copies made from those copies), or (b) primarily for and in
connection with specific products or compilations that contain the
covered work, unless you entered into that arrangement, or that patent
license was granted, prior to 28 March 2007.
Nothing in this License shall be construed as excluding or limiting
any implied license or other defenses to infringement that may
otherwise be available to you under applicable patent law.
- No Surrender of Others’ Freedom.
If conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot convey
a covered work so as to satisfy simultaneously your obligations under
this License and any other pertinent obligations, then as a
consequence you may not convey it at all. For example, if you agree
to terms that obligate you to collect a royalty for further conveying
from those to whom you convey the Program, the only way you could
satisfy both those terms and this License would be to refrain entirely
from conveying the Program.
- Use with the GNU Affero General Public License.
Notwithstanding any other provision of this License, you have
permission to link or combine any covered work with a work licensed
under version 3 of the GNU Affero General Public License into a single
combined work, and to convey the resulting work. The terms of this
License will continue to apply to the part which is the covered work,
but the special requirements of the GNU Affero General Public License,
section 13, concerning interaction through a network will apply to the
combination as such.
- Revised Versions of this License.
The Free Software Foundation may publish revised and/or new versions
of the GNU General Public License from time to time. Such new
versions will be similar in spirit to the present version, but may
differ in detail to address new problems or concerns.
Each version is given a distinguishing version number. If the Program
specifies that a certain numbered version of the GNU General Public
License “or any later version” applies to it, you have the option of
following the terms and conditions either of that numbered version or
of any later version published by the Free Software Foundation. If
the Program does not specify a version number of the GNU General
Public License, you may choose any version ever published by the Free
Software Foundation.
If the Program specifies that a proxy can decide which future versions
of the GNU General Public License can be used, that proxy’s public
statement of acceptance of a version permanently authorizes you to
choose that version for the Program.
Later license versions may give you additional or different
permissions. However, no additional obligations are imposed on any
author or copyright holder as a result of your choosing to follow a
later version.
- Disclaimer of Warranty.
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM “AS IS” WITHOUT
WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND
PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE
DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR
CORRECTION.
- Limitation of Liability.
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR
CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES
ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT
NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR
LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM
TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER
PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
- Interpretation of Sections 15 and 16.
If the disclaimer of warranty and limitation of liability provided
above cannot be given local legal effect according to their terms,
reviewing courts shall apply local law that most closely approximates
an absolute waiver of all civil liability in connection with the
Program, unless a warranty or assumption of liability accompanies a
copy of the Program in return for a fee.
END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.
To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
state the exclusion of warranty; and each file should have at least
the “copyright” line and a pointer to where the full notice is found.
| | one line to give the program's name and a brief idea of what it does.
Copyright (C) year name of author
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or (at
your option) any later version.
This program is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see http://www.gnu.org/licenses/.
|
Also add information on how to contact you by electronic and paper mail.
If the program does terminal interaction, make it output a short
notice like this when it starts in an interactive mode:
| | program Copyright (C) year name of author
This program comes with ABSOLUTELY NO WARRANTY; for details type ‘show w’.
This is free software, and you are welcome to redistribute it
under certain conditions; type ‘show c’ for details.
|
The hypothetical commands ‘show w’ and ‘show c’ should show
the appropriate parts of the General Public License. Of course, your
program’s commands might be different; for a GUI interface, you would
use an “about box”.
You should also get your employer (if you work as a programmer) or school,
if any, to sign a “copyright disclaimer” for the program, if necessary.
For more information on this, and how to apply and follow the GNU GPL, see
http://www.gnu.org/licenses/.
The GNU General Public License does not permit incorporating your
program into proprietary programs. If your program is a subroutine
library, you may consider it more useful to permit linking proprietary
applications with the library. If this is what you want to do, use
the GNU Lesser General Public License instead of this License. But
first, please read http://www.gnu.org/philosophy/why-not-lgpl.html.
Manuali
Manuali di LilyPond 2.21.0
Altro materiale
-
Tutti:
versioni stabili precedenti e quella attuale in un archivio compresso.
- Tradotti:
stato delle traduzioni per i lettori di lingua non inglese.
-
LilyPond Snippet Repository:
esempi, consigli e trucchi creati dagli utenti.
-
Video Tutorial:
Ben Lemon, un utente di LilyPond, ha creato una serie di video tutorial sul
suo blog rivolti ai nuovi utenti.
- Sviluppo:
manuali per la versione non stabile.
- FDL:
questi manuali sono pubblicati e distribuiti secondo la GNU Free Documentation
License.
Formati dei manuali
I manuali di LilyPond vengono offerti generalmente in tre
formati: HTML multipagina, HTML grande e PDF. L’HTML multipagina
è ottimale per la lettura online. L’HTML grande (e alcuni di
questi possono essere davvero grandi) contiene l’intero manuale
in una sola pagina. Il PDF può essere scaricato e usato offline.
Per vedere questi tre formati segui i collegamenti
dettagli di e poi il nome del manuale.
Apprendimento
Manuale di apprendimento
Questo libro spiega come iniziare a imparare LilyPond, e illustra
in modo semplice alcuni concetti fondamentali. Dovresti leggere
questi capitoli uno dopo l’altro.
Alla fine di ogni sezione c’è un paragrafo Vedi anche,
che contiene riferimenti incrociati alle altre sezioni: a una prima
lettura non dovresti seguire questi riferimenti. Quando hai letto
tutto il manuale, potresti voler leggere alcune sezioni di nuovo
e seguire questi riferimenti incrociati per maggiori informazioni.
Glossario
Glossario
Questo manuale spiega i termini musicali, tradotti
in varie lingue. Se non hai una buona conoscenza della notazione o
della terminologia musicale (soprattutto se non sei di madrelingua inglese),
si raccomanda vivamente di consultare il glossario.
Saggio
Saggio
Questo libro contiene una breve storia della tipografia musicale, seguita
da un’analisi delle tecniche di incisione di LilyPond. Comprende un
confronto tra LilyPond e altri sistemi di incisione musicale.
Nota: i dettagliati esempi tipografici sono più facili da analizzare
nella versione PDF a causa della sua maggiore risoluzione.
Notazione
Guida alla Notazione
Questo libro spiega tutti i comandi LilyPond che producono la
notazione.
Nota: la Guida alla Notazione dà per scontato che il lettore conosca
il materiale di base esposto nel Manuale di Apprendimento e i termini
musicali inglesi presentati nel Glossario.
Uso
Manuale d’uso
Questo libro spiega come eseguire i programmi, come integrare la
notazione di LilyPond in altri programmi, e suggerisce le “migliori
tecniche” per un uso efficiente. È consigliabile leggerlo prima di
intraprendere un progetto impegnativo.
Leggilo
- Uso (HTML multipagina)
-
il manuale è diviso in tante pagine HTML.
(piccolo download per ogni pagina)
- Uso (HTML pagina unica)
-
leggi questo manuale in un’unica grande pagina HTML.
(un solo grande download, 400 KB)
- usage.pdf
-
scarica come file PDF.
(un solo grande download, 650 KB)
Frammenti
Frammenti
Questo manuale presenta una selezione di frammenti di codice LilyPond tratti dal
LilyPond Snippet Repository
(LSR). Tutti i frammenti di codice sono nel pubblico dominio.
Si prega di notare che questo documento non è un sottoinsieme esatto del LSR. LSR
utilizza una versione stabile di LilyPond, dunque i frammenti che
illustrano le nuove funzionalità di una versione di sviluppo devono essere
aggiunti separatamente. Vengono memorizzati in ‘Documentation/snippets/new/’
nell’albero dei sorgenti di LilyPond.
Ogni sottosezione della Guida alla Notazione, nella parte Vedi anche,
ha un collegamento alla lista dei relativi frammenti di codice.
FAQ
Domande iniziali
Dove sono l’area di lavoro, i menu e la barra degli strumenti?
Per usare LilyPond devi scrivere musica in formato testo. Leggi cosa
è il nostro Input testuale.
C’è un sacco di documentazione! Devo leggerla?
Devi leggere il Manuale di Apprendimento. Per quanto
riguarda il resto della documentazione, puoi leggere solo le sezioni
sul tipo di notazione che vuoi creare.
C’è ancora molto da leggere! Ne vale la pena?
Tocca a te decidere; le ragioni per cui potresti voler usare
LilyPond sono esposte nell’Introduzione.
Web
Web
Questo manuale fornisce informazioni generali su LilyPond. Contiene
anche delle informazioni riguardanti le varie comunità, la segnalazione
di bug e lo sviluppo.
Leggi
Ultimo manuale
Manuale Web in 2.19.65
- Web (HTML multipagina)
-
il manuale è diviso in tante pagine HTML.
(piccolo download per ogni pagina)
- Web (HTML pagina unica)
-
leggi questo manuale in un’unica grande pagina HTML.
(un solo grande download, 2.5 MB)
- web.pdf
-
scarica come file PDF.
(un solo grande download, 3.5 MB)
Cambiamenti
Cambiamenti
Questo è un sommario degli importanti cambiamenti e delle nuove
funzionalità di LilyPond rispetto alla versione stabile precedente.
Estendere
Estendere LilyPond
Questo manuale spiega come scrivere delle estensioni delle
funzionalità di LilyPond.
Funzionamento interno
Guida al Funzionamento interno
Si tratta di un insieme di pagine ricche di collegamenti che documentano
i dettagli essenziali di ogni classe, oggetto e funzione di LilyPond.
È prodotto direttamente dalle definizioni di formattazione
presenti nel codice sorgente.
Quasi tutte le funzionalità di formattazione usate internamente sono
direttamente accessibili per l’utente. Ad esempio, gran parte delle
variabili che controllano i valori dello spessore, le distanze, ecc.,
può essere modificata nei file di input. Esistono moltissime opzioni di
formattazione, e tutte queste sono descritte in questo documento. Ogni
sezione della Guida alla Notazione ha una sottosezione Vedi anche,
che si riferisce alla documentazione generata.
Tradotti
Stato delle traduzioni
Ultimo aggiornamento Sat Jun 24 12:50:41 UTC 2017
| Cambiamenti in LilyPond | Traduttori | Revisori | Tradotto | Aggiornato | Altre informazioni |
|---|
Section titles
2784 | Federico Bruni | | sì | sì | pre-GDP |
LilyPond — \TITLE\
1139 | Federico Bruni | | sì | sì | pre-GDP |
| Saggio sull’incisione musicale automatizzata | Traduttori | Revisori | Tradotto | Aggiornato | Altre informazioni |
|---|
Section titles
92 | Tommaso Gordini | Federico Bruni | sì | sì | pre-GDP |
LilyPond — \TITLE\
1139 | Tommaso Gordini | Federico Bruni | sì | sì | pre-GDP |
1 Incisione musicale
5315 | Tommaso Gordini | Federico Bruni | sì | sì | pre-GDP |
2 Bibliografia
382 | Tommaso Gordini | Federico Bruni | sì | sì | pre-GDP |
| Manuale di apprendimento di LilyPond | Traduttori | Revisori | Tradotto | Aggiornato | Altre informazioni |
|---|
Section titles
124 | Federico Bruni | Luca Rossetto Casel | sì | sì | pre-GDP |
LilyPond — \TITLE\
1139 | Federico Bruni | Luca Rossetto Casel | sì | sì | pre-GDP |
1 Tutorial
2499 | Federico Bruni | Luca Rossetto Casel | sì | sì | pre-GDP |
2 Notazione comunemente utilizzata
4421 | Federico Bruni | Luca Rossetto Casel | sì | sì | pre-GDP |
3 Concetti fondamentali
11240 | Federico Bruni | Luca Rossetto Casel | sì | sì | pre-GDP |
4 Modifica dell’output
16592 | Federico Bruni | Luca Rossetto Casel | sì | sì | pre-GDP |
A Modelli
1236 | Federico Bruni | Luca Rossetto Casel | sì | sì | pre-GDP |
| Guida alla Notazione di LilyPond | Traduttori | Revisori | Tradotto | Aggiornato | Altre informazioni |
|---|
Section titles
326 | Federico Bruni | | sì | sì | pre-GDP |
LilyPond — \TITLE\
1139 | Federico Bruni | | sì | sì | pre-GDP |
1 Notazione musicale
91 | Federico Bruni | | sì | sì | pre-GDP |
1.1 Altezze
5413 | Federico Bruni | Luca Rossetto Casel | sì | sì | pre-GDP |
1.2 Ritmi
6853 | Federico Bruni | Luca Rossetto Casel | sì | sì | pre-GDP |
1.3 Segni di espressione
1819 | Federico Bruni | Luca Rossetto Casel | sì | sì | pre-GDP |
1.4 Ripetizioni
1288 | Federico Bruni | Luca Rossetto Casel | sì | sì | pre-GDP |
1.5 Note simultanee
2979 | Federico Bruni | Luca Rossetto Casel | sì | parzialmente | pre-GDP |
1.6 Notazione del rigo
2554 | Federico Bruni | | sì | sì | pre-GDP |
1.7 Note editoriali
1481 | Federico Bruni | | sì | sì | pre-GDP |
1.8 Testo
2754 | Federico Bruni | | sì | sì | pre-GDP |
2 Notazione specialistica
81 | Federico Bruni | | sì | sì | pre-GDP |
2.1 Musica vocale
4977 | Federico Bruni | | sì | sì | pre-GDP |
2.2 World music
1446 | Federico Bruni | | sì | sì | pre-GDP |
3 Input e output
12853 | Federico Bruni | | sì | sì | pre-GDP |
4 Gestione dello spazio
10982 | Federico Bruni | | sì | sì | pre-GDP |
5 Modifica delle impostazioni predefinite
17050 | Federico Bruni | | sì | sì | pre-GDP |
A Tabelle del manuale della notazione
3079 | Federico Bruni | | sì | sì | pre-GDP |
B Schema riassuntivo
252 | Federico Bruni | | sì | sì | pre-GDP |
| LilyPond: manuale d’uso del programma | Traduttori | Revisori | Tradotto | Aggiornato | Altre informazioni |
|---|
Section titles
135 | Federico Bruni | Luca Rossetto Casel | sì | sì | pre-GDP |
LilyPond — \TITLE\
1139 | Federico Bruni | Luca Rossetto Casel | sì | sì | pre-GDP |
1 Eseguire lilypond
5469 | Federico Bruni | Luca Rossetto Casel | sì | sì | pre-GDP |
2 Aggiornare i file con convert-ly
2097 | Federico Bruni | Luca Rossetto Casel | sì | sì | pre-GDP |
3 Eseguire lilypond-book
4211 | Federico Bruni | Luca Rossetto Casel | sì | sì | pre-GDP |
4 Programmi esterni
2786 | Federico Bruni | Luca Rossetto Casel | sì | sì | pre-GDP |
5 Consigli su come scrivere i file
2793 | Federico Bruni | Luca Rossetto Casel | sì | sì | pre-GDP |
| LilyPond – Notazione musicale per tutti | Traduttori | Revisori | Tradotto | Aggiornato | Altre informazioni |
|---|
Section titles
760 | Federico Bruni | Luca Rossetto Casel | sì | sì | pre-GDP |
LilyPond — \TITLE\
1139 | Federico Bruni | Luca Rossetto Casel | sì | sì | pre-GDP |
Introduzione
5793 | Federico Bruni | Luca Rossetto Casel | sì | sì | pre-GDP |
Download
1158 | Federico Bruni | Luca Rossetto Casel | sì | sì | pre-GDP |
Manuali
1314 | Federico Bruni | Luca Rossetto Casel | sì | sì | pre-GDP |
Comunità
2449 | Federico Bruni | Luca Rossetto Casel | sì | sì | pre-GDP |
Tutti
Versioni stabili precedenti
FDL
Licenza della Documentazione
La documentazione per GNU LilyPond è pubblicata secondo la GNU Free
Documentation License. Un’introduzione a questa licenza, e le ragioni
per cui l’abbiamo scelta, è disponibile in Libertà.
GNU Free Documentation License 1.1
Version 1.3, 3 November 2008
| | Copyright © 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc.
http://fsf.org/
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
|
-
PREAMBLE
The purpose of this License is to make a manual, textbook, or other
functional and useful document free in the sense of freedom: to
assure everyone the effective freedom to copy and redistribute it,
with or without modifying it, either commercially or noncommercially.
Secondarily, this License preserves for the author and publisher a way
to get credit for their work, while not being considered responsible
for modifications made by others.
This License is a kind of “copyleft”, which means that derivative
works of the document must themselves be free in the same sense. It
complements the GNU General Public License, which is a copyleft
license designed for free software.
We have designed this License in order to use it for manuals for free
software, because free software needs free documentation: a free
program should come with manuals providing the same freedoms that the
software does. But this License is not limited to software manuals;
it can be used for any textual work, regardless of subject matter or
whether it is published as a printed book. We recommend this License
principally for works whose purpose is instruction or reference.
-
APPLICABILITY AND DEFINITIONS
This License applies to any manual or other work, in any medium, that
contains a notice placed by the copyright holder saying it can be
distributed under the terms of this License. Such a notice grants a
world-wide, royalty-free license, unlimited in duration, to use that
work under the conditions stated herein. The “Document”, below,
refers to any such manual or work. Any member of the public is a
licensee, and is addressed as “you”. You accept the license if you
copy, modify or distribute the work in a way requiring permission
under copyright law.
A “Modified Version” of the Document means any work containing the
Document or a portion of it, either copied verbatim, or with
modifications and/or translated into another language.
A “Secondary Section” is a named appendix or a front-matter section
of the Document that deals exclusively with the relationship of the
publishers or authors of the Document to the Document’s overall
subject (or to related matters) and contains nothing that could fall
directly within that overall subject. (Thus, if the Document is in
part a textbook of mathematics, a Secondary Section may not explain
any mathematics.) The relationship could be a matter of historical
connection with the subject or with related matters, or of legal,
commercial, philosophical, ethical or political position regarding
them.
The “Invariant Sections” are certain Secondary Sections whose titles
are designated, as being those of Invariant Sections, in the notice
that says that the Document is released under this License. If a
section does not fit the above definition of Secondary then it is not
allowed to be designated as Invariant. The Document may contain zero
Invariant Sections. If the Document does not identify any Invariant
Sections then there are none.
The “Cover Texts” are certain short passages of text that are listed,
as Front-Cover Texts or Back-Cover Texts, in the notice that says that
the Document is released under this License. A Front-Cover Text may
be at most 5 words, and a Back-Cover Text may be at most 25 words.
A “Transparent” copy of the Document means a machine-readable copy,
represented in a format whose specification is available to the
general public, that is suitable for revising the document
straightforwardly with generic text editors or (for images composed of
pixels) generic paint programs or (for drawings) some widely available
drawing editor, and that is suitable for input to text formatters or
for automatic translation to a variety of formats suitable for input
to text formatters. A copy made in an otherwise Transparent file
format whose markup, or absence of markup, has been arranged to thwart
or discourage subsequent modification by readers is not Transparent.
An image format is not Transparent if used for any substantial amount
of text. A copy that is not “Transparent” is called “Opaque”.
Examples of suitable formats for Transparent copies include plain
ASCII without markup, Texinfo input format, LaTeX input
format, SGML or XML using a publicly available
DTD, and standard-conforming simple HTML,
PostScript or PDF designed for human modification. Examples
of transparent image formats include PNG, XCF and
JPG. Opaque formats include proprietary formats that can be
read and edited only by proprietary word processors, SGML or
XML for which the DTD and/or processing tools are
not generally available, and the machine-generated HTML,
PostScript or PDF produced by some word processors for
output purposes only.
The “Title Page” means, for a printed book, the title page itself,
plus such following pages as are needed to hold, legibly, the material
this License requires to appear in the title page. For works in
formats which do not have any title page as such, “Title Page” means
the text near the most prominent appearance of the work’s title,
preceding the beginning of the body of the text.
The “publisher” means any person or entity that distributes copies
of the Document to the public.
A section “Entitled XYZ” means a named subunit of the Document whose
title either is precisely XYZ or contains XYZ in parentheses following
text that translates XYZ in another language. (Here XYZ stands for a
specific section name mentioned below, such as “Acknowledgements”,
“Dedications”, “Endorsements”, or “History”.) To “Preserve the Title”
of such a section when you modify the Document means that it remains a
section “Entitled XYZ” according to this definition.
The Document may include Warranty Disclaimers next to the notice which
states that this License applies to the Document. These Warranty
Disclaimers are considered to be included by reference in this
License, but only as regards disclaiming warranties: any other
implication that these Warranty Disclaimers may have is void and has
no effect on the meaning of this License.
-
VERBATIM COPYING
You may copy and distribute the Document in any medium, either
commercially or noncommercially, provided that this License, the
copyright notices, and the license notice saying this License applies
to the Document are reproduced in all copies, and that you add no other
conditions whatsoever to those of this License. You may not use
technical measures to obstruct or control the reading or further
copying of the copies you make or distribute. However, you may accept
compensation in exchange for copies. If you distribute a large enough
number of copies you must also follow the conditions in section 3.
You may also lend copies, under the same conditions stated above, and
you may publicly display copies.
-
COPYING IN QUANTITY
If you publish printed copies (or copies in media that commonly have
printed covers) of the Document, numbering more than 100, and the
Document’s license notice requires Cover Texts, you must enclose the
copies in covers that carry, clearly and legibly, all these Cover
Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on
the back cover. Both covers must also clearly and legibly identify
you as the publisher of these copies. The front cover must present
the full title with all words of the title equally prominent and
visible. You may add other material on the covers in addition.
Copying with changes limited to the covers, as long as they preserve
the title of the Document and satisfy these conditions, can be treated
as verbatim copying in other respects.
If the required texts for either cover are too voluminous to fit
legibly, you should put the first ones listed (as many as fit
reasonably) on the actual cover, and continue the rest onto adjacent
pages.
If you publish or distribute Opaque copies of the Document numbering
more than 100, you must either include a machine-readable Transparent
copy along with each Opaque copy, or state in or with each Opaque copy
a computer-network location from which the general network-using
public has access to download using public-standard network protocols
a complete Transparent copy of the Document, free of added material.
If you use the latter option, you must take reasonably prudent steps,
when you begin distribution of Opaque copies in quantity, to ensure
that this Transparent copy will remain thus accessible at the stated
location until at least one year after the last time you distribute an
Opaque copy (directly or through your agents or retailers) of that
edition to the public.
It is requested, but not required, that you contact the authors of the
Document well before redistributing any large number of copies, to give
them a chance to provide you with an updated version of the Document.
-
MODIFICATIONS
You may copy and distribute a Modified Version of the Document under
the conditions of sections 2 and 3 above, provided that you release
the Modified Version under precisely this License, with the Modified
Version filling the role of the Document, thus licensing distribution
and modification of the Modified Version to whoever possesses a copy
of it. In addition, you must do these things in the Modified Version:
-
Use in the Title Page (and on the covers, if any) a title distinct
from that of the Document, and from those of previous versions
(which should, if there were any, be listed in the History section
of the Document). You may use the same title as a previous version
if the original publisher of that version gives permission.
-
List on the Title Page, as authors, one or more persons or entities
responsible for authorship of the modifications in the Modified
Version, together with at least five of the principal authors of the
Document (all of its principal authors, if it has fewer than five),
unless they release you from this requirement.
-
State on the Title page the name of the publisher of the
Modified Version, as the publisher.
-
Preserve all the copyright notices of the Document.
-
Add an appropriate copyright notice for your modifications
adjacent to the other copyright notices.
-
Include, immediately after the copyright notices, a license notice
giving the public permission to use the Modified Version under the
terms of this License, in the form shown in the Addendum below.
-
Preserve in that license notice the full lists of Invariant Sections
and required Cover Texts given in the Document’s license notice.
-
Include an unaltered copy of this License.
-
Preserve the section Entitled “History”, Preserve its Title, and add
to it an item stating at least the title, year, new authors, and
publisher of the Modified Version as given on the Title Page. If
there is no section Entitled “History” in the Document, create one
stating the title, year, authors, and publisher of the Document as
given on its Title Page, then add an item describing the Modified
Version as stated in the previous sentence.
-
Preserve the network location, if any, given in the Document for
public access to a Transparent copy of the Document, and likewise
the network locations given in the Document for previous versions
it was based on. These may be placed in the “History” section.
You may omit a network location for a work that was published at
least four years before the Document itself, or if the original
publisher of the version it refers to gives permission.
-
For any section Entitled “Acknowledgements” or “Dedications”, Preserve
the Title of the section, and preserve in the section all the
substance and tone of each of the contributor acknowledgements and/or
dedications given therein.
-
Preserve all the Invariant Sections of the Document,
unaltered in their text and in their titles. Section numbers
or the equivalent are not considered part of the section titles.
-
Delete any section Entitled “Endorsements”. Such a section
may not be included in the Modified Version.
-
Do not retitle any existing section to be Entitled “Endorsements” or
to conflict in title with any Invariant Section.
-
Preserve any Warranty Disclaimers.
If the Modified Version includes new front-matter sections or
appendices that qualify as Secondary Sections and contain no material
copied from the Document, you may at your option designate some or all
of these sections as invariant. To do this, add their titles to the
list of Invariant Sections in the Modified Version’s license notice.
These titles must be distinct from any other section titles.
You may add a section Entitled “Endorsements”, provided it contains
nothing but endorsements of your Modified Version by various
parties—for example, statements of peer review or that the text has
been approved by an organization as the authoritative definition of a
standard.
You may add a passage of up to five words as a Front-Cover Text, and a
passage of up to 25 words as a Back-Cover Text, to the end of the list
of Cover Texts in the Modified Version. Only one passage of
Front-Cover Text and one of Back-Cover Text may be added by (or
through arrangements made by) any one entity. If the Document already
includes a cover text for the same cover, previously added by you or
by arrangement made by the same entity you are acting on behalf of,
you may not add another; but you may replace the old one, on explicit
permission from the previous publisher that added the old one.
The author(s) and publisher(s) of the Document do not by this License
give permission to use their names for publicity for or to assert or
imply endorsement of any Modified Version.
-
COMBINING DOCUMENTS
You may combine the Document with other documents released under this
License, under the terms defined in section 4 above for modified
versions, provided that you include in the combination all of the
Invariant Sections of all of the original documents, unmodified, and
list them all as Invariant Sections of your combined work in its
license notice, and that you preserve all their Warranty Disclaimers.
The combined work need only contain one copy of this License, and
multiple identical Invariant Sections may be replaced with a single
copy. If there are multiple Invariant Sections with the same name but
different contents, make the title of each such section unique by
adding at the end of it, in parentheses, the name of the original
author or publisher of that section if known, or else a unique number.
Make the same adjustment to the section titles in the list of
Invariant Sections in the license notice of the combined work.
In the combination, you must combine any sections Entitled “History”
in the various original documents, forming one section Entitled
“History”; likewise combine any sections Entitled “Acknowledgements”,
and any sections Entitled “Dedications”. You must delete all
sections Entitled “Endorsements.”
-
COLLECTIONS OF DOCUMENTS
You may make a collection consisting of the Document and other documents
released under this License, and replace the individual copies of this
License in the various documents with a single copy that is included in
the collection, provided that you follow the rules of this License for
verbatim copying of each of the documents in all other respects.
You may extract a single document from such a collection, and distribute
it individually under this License, provided you insert a copy of this
License into the extracted document, and follow this License in all
other respects regarding verbatim copying of that document.
-
AGGREGATION WITH INDEPENDENT WORKS
A compilation of the Document or its derivatives with other separate
and independent documents or works, in or on a volume of a storage or
distribution medium, is called an “aggregate” if the copyright
resulting from the compilation is not used to limit the legal rights
of the compilation’s users beyond what the individual works permit.
When the Document is included in an aggregate, this License does not
apply to the other works in the aggregate which are not themselves
derivative works of the Document.
If the Cover Text requirement of section 3 is applicable to these
copies of the Document, then if the Document is less than one half of
the entire aggregate, the Document’s Cover Texts may be placed on
covers that bracket the Document within the aggregate, or the
electronic equivalent of covers if the Document is in electronic form.
Otherwise they must appear on printed covers that bracket the whole
aggregate.
-
TRANSLATION
Translation is considered a kind of modification, so you may
distribute translations of the Document under the terms of section 4.
Replacing Invariant Sections with translations requires special
permission from their copyright holders, but you may include
translations of some or all Invariant Sections in addition to the
original versions of these Invariant Sections. You may include a
translation of this License, and all the license notices in the
Document, and any Warranty Disclaimers, provided that you also include
the original English version of this License and the original versions
of those notices and disclaimers. In case of a disagreement between
the translation and the original version of this License or a notice
or disclaimer, the original version will prevail.
If a section in the Document is Entitled “Acknowledgements”,
“Dedications”, or “History”, the requirement (section 4) to Preserve
its Title (section 1) will typically require changing the actual
title.
-
TERMINATION
You may not copy, modify, sublicense, or distribute the Document
except as expressly provided under this License. Any attempt
otherwise to copy, modify, sublicense, or distribute it is void, and
will automatically terminate your rights under this License.
However, if you cease all violation of this License, then your license
from a particular copyright holder is reinstated (a) provisionally,
unless and until the copyright holder explicitly and finally
terminates your license, and (b) permanently, if the copyright holder
fails to notify you of the violation by some reasonable means prior to
60 days after the cessation.
Moreover, your license from a particular copyright holder is
reinstated permanently if the copyright holder notifies you of the
violation by some reasonable means, this is the first time you have
received notice of violation of this License (for any work) from that
copyright holder, and you cure the violation prior to 30 days after
your receipt of the notice.
Termination of your rights under this section does not terminate the
licenses of parties who have received copies or rights from you under
this License. If your rights have been terminated and not permanently
reinstated, receipt of a copy of some or all of the same material does
not give you any rights to use it.
-
FUTURE REVISIONS OF THIS LICENSE
The Free Software Foundation may publish new, revised versions
of the GNU Free Documentation License from time to time. Such new
versions will be similar in spirit to the present version, but may
differ in detail to address new problems or concerns. See
http://www.gnu.org/copyleft/.
Each version of the License is given a distinguishing version number.
If the Document specifies that a particular numbered version of this
License “or any later version” applies to it, you have the option of
following the terms and conditions either of that specified version or
of any later version that has been published (not as a draft) by the
Free Software Foundation. If the Document does not specify a version
number of this License, you may choose any version ever published (not
as a draft) by the Free Software Foundation. If the Document
specifies that a proxy can decide which future versions of this
License can be used, that proxy’s public statement of acceptance of a
version permanently authorizes you to choose that version for the
Document.
-
RELICENSING
“Massive Multiauthor Collaboration Site” (or “MMC Site”) means any
World Wide Web server that publishes copyrightable works and also
provides prominent facilities for anybody to edit those works. A
public wiki that anybody can edit is an example of such a server. A
“Massive Multiauthor Collaboration” (or “MMC”) contained in the
site means any set of copyrightable works thus published on the MMC
site.
“CC-BY-SA” means the Creative Commons Attribution-Share Alike 3.0
license published by Creative Commons Corporation, a not-for-profit
corporation with a principal place of business in San Francisco,
California, as well as future copyleft versions of that license
published by that same organization.
“Incorporate” means to publish or republish a Document, in whole or
in part, as part of another Document.
An MMC is “eligible for relicensing” if it is licensed under this
License, and if all works that were first published under this License
somewhere other than this MMC, and subsequently incorporated in whole
or in part into the MMC, (1) had no cover texts or invariant sections,
and (2) were thus incorporated prior to November 1, 2008.
The operator of an MMC Site may republish an MMC contained in the site
under CC-BY-SA on the same site at any time before August 1, 2009,
provided the MMC is eligible for relicensing.
ADDENDUM: How to use this License for your documents
To use this License in a document you have written, include a copy of
the License in the document and put the following copyright and
license notices just after the title page:
| | Copyright (C) year your name.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.3
or any later version published by the Free Software Foundation;
with no Invariant Sections, no Front-Cover Texts, and no Back-Cover
Texts. A copy of the license is included in the section entitled ``GNU
Free Documentation License''.
|
If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts,
replace the “with…Texts.” line with this:
| | with the Invariant Sections being list their titles, with
the Front-Cover Texts being list, and with the Back-Cover Texts
being list.
|
If you have Invariant Sections without Cover Texts, or some other
combination of the three, merge those two alternatives to suit the
situation.
If your document contains nontrivial examples of program code, we
recommend releasing these examples in parallel under your choice of
free software license, such as the GNU General Public License,
to permit their use in free software.
Comunità
Interagire con la comunità
-
Contatti: chiedi aiuto, discuti e resta in contatto!
-
Esempi minimi: questi esempi sono altamente raccomandati
quando si discute di LilyPond.
-
Segnalazione bug: qualcosa non ha funzionato.
Varie
-
Pubblicazioni: cosa abbiamo scritto, e cosa è stato scritto su di noi.
-
Notizie: notizie sul progetto LilyPond.
-
Soffitta: annunci e changelog delle versioni precedenti.
Contatti
Esempi minimi
Cosa sono gli “Esempi minimi”?
Un esempio minimo è un esempio dal quale niente può essere tolto.
Perché crearli?
-
Più l’esempio è semplice, più rapidamente potenziali solutori
possono comprenderlo e aiutarti.
-
Un esempio minimo dimostra che hai tentato di risolvere il problema
da solo. Quando le persone inviano grandi porzioni di codice, sembra
che non si preoccupino che li possiamo aiutare o no.
-
Creare un esempio minimo ti aiuta a capire cosa sta
succedendo. Molte segnalazioni di un falso problema possono essere
evitate se si prova a creare un esempio minimo; se non riesci a ricreare
un “bug” in un esempio minimo, allora probabilmente il problema è
una conoscenza di LilyPond insufficiente, non un vero bug!
Come crearli?
-
Includi il numero di versione nel comando
\version.
-
Crea un esempio piccolo! Gli esempi che riguardano la spaziatura o la
formattazione di pagina potrebbero richiedere molte battute, ma la maggior
parte dei problemi può essere riprodotta con meno di una battuta.
-
Durante la preparazione di un esempio, cerca di commentare (
%
o %{ … %}) le sezioni del tuo file. Se riesci a
commentare una porzione di codice riuscendo a mantenere chiara l’idea principale,
allora elimina il materiale commentato!
-
Evita di usare note, tonalità o segni di tempo complessi a meno che
il malfunzionamento non riguardi proprio il comportamento di questi elementi.
-
Non usare i comandi
\override o \set, a meno che il malfunzionamento
non riguardi questi comandi in particolare.
-
Eventualmente, allega un’immagine che mostri il risultato grafico desiderato.
Quanto piccoli devono essere?
Il codice seguente è un esempio minimo?
\version "2.14.1"
\include "english.ly"
\score {
\new Staff {
\key d \major
\numericTimeSignature
\time 2/4
<cs' d'' b''>16 <cs' d'' b''>8.
%% Here: the tie on the D's looks funny
%% Too tall? Left-hand endpoint is not aligned with the B tie?
~
<cs' d'' b''>8 [ <b d'' a''> ]
}
}
Non è poi così grande, ma un vero esempio minimo è il seguente:
\version "2.14.1"
{
% middle tie looks funny here:
<c' d'' b''>8. ~ <c' d'' b''>8
}
Sono pochi gli esempi minimi che superano 10 righe di codice -
spesso 4 righe sono sufficienti per illustrare il problema!
Segnalazione bug
Se hai un codice di input che produce un crash o un output sbagliato,
allora si tratta di un bug.
Passo 1: Bug noti
Potremmo già essere a conoscenza di questo bug. Controlla qui:
http://sourceforge.net/p/testlilyissues/issues/
Nota: Per favore NON aggiungere segnalazioni di bug direttamente
nel bug tracker. Una volta che il problema è stato aggiunto al tracker, aggiungi
pure maggiori informazioni nella segnalazione.
Passo 2: Creare una segnalazione bug
Se hai scoperto un bug che non è ancora stato riportato, puoi aiutarci creando
una segnalazione bug.
Nota: Accettiamo segnalazioni bug esclusivamente nella forma di Esempi minimi. Abbiamo risorse molto limitate, quindi qualsiasi esempio non minimo
sarà scartato. Quasi ogni bug può essere dimostrato con quattro note o meno!
Ecco un esempio di una valida segnalazione bug:
% Le alterazioni dovrebbero comparire solo nella
% prima nota di una legatura di valore, ma questa
% versione mostra il bemolle accanto a entrambe le note.
\version "2.10.1"
\relative c'' {
bes1 ~
bes1
}
Passo 3: Inviare una segnalazione bug
Dopo aver verificato che il problema non sia già noto e aver
creato una segnalazione bug, inviacela!
-
Sei iscritto alla mailing list bug-lilypond@gnu.org, puoi inviare una normale email.
-
Se non sei iscritto, puoi comunque inviare una segnalazione bug attraverso
l’interfaccia web lilypond.bugs di gmane.
Purtroppo c’è un severo controllo “contro il top-posting” nell’interfaccia di
gmane, che viene spesso innescato erroneamente dai file lilypond.
Per evitarlo, aggiungi
> I'm not top posting.
(devi includere il > ) in cima alla tua segnalazione bug.
Passo 4: Attendi una risposta
Una volta che la segnalazione bug è stata inviata alla lista, la nostra Squadra
Bug la esaminerà e forse ti chiederà maggiori informazioni. Verrai avvisato
quando la segnalazione viene aggiunta al bug tracker. Una risposta può richiedere
fino a 4 giorni, perché abbiamo un numero limitato di volontari per questo compito.
Una volta che un bug è stato aggiunto al tracker, puoi commentarlo per aggiungere
informazioni a riguardo. Per ricevere automaticamente delle notifiche su
qualsiasi attività relativa al bug, puoi iscriverti cliccando sul simbolo
della busta vicino al titolo del bug. Per commentare e iscriversi occorre un
account sourceforge.
Aiuto facoltativo: mostra il comportamento desiderato
Dopo che il problema è stato aggiunto al tracker, può essere molto
utile poter vedere l’output desiderato. Aggiungi pure del codice di
input e/o delle immagini (se possibile, create con altri strumenti) che
mostrino come dovrebbe apparire secondo te!
Aiutaci
Abbiamo bisogno di te!
Ti ringraziamo per l’interesse nel darci una mano — ci farebbe molto
piacere vederti partecipare! Il tuo contributo aiuterà tanti utenti a
scrivere belle partiture.
Anche lavorare su piccoli compiti può avere un grande impatto: occuparsi di
questi compiti permette agli sviluppatori esperti di lavorare sui compiti
complessi, invece di impiegare il tempo in quelli semplici.
In un progetto complesso come LilyPond, talvolta è difficile sapere da dove
iniziare. Oltre alle possibilità proposte sotto, puoi inviare un
email alla mailing list lilypond-devel@gnu.org, e ti aiuteremo nel tuo percorso iniziale.
Compiti semplici
Non è necessario saper programmare!
-
Supporto nelle mailing list: rispondi alle domande degli utenti.
-
Segnalazione bug: aiuta gli utenti a creare una
Segnalazione bug
corretta e/o entra nel Bug Squad per l’organizzazione dei
Problemi.
-
Documentazione: puoi proporre piccole modifiche seguendo le linee
guida per i
Consigli per la documentazione.
-
LilyPond Snippet Repository (LSR): crea e correggi i frammenti di codice
seguendo le linee guida in
Aggiungere e modificare i frammenti di codice.
-
Discussioni, revisioni e prove: gli sviluppatori chiedono spesso
delle opinioni sulla documentazione, possibili cambiamenti di sintassi
e il test di nuove funzionalità. Contribuisci a queste discussioni!
Compiti avanzati
Questi compiti di solito richiedono il codice sorgente e la capacità di
compilare LilyPond.
Nota: Consigliamo ai collaboratori che usano Windows o MacOS X di
non cercare di configurare il proprio ambiente di sviluppo;
si consiglia invece di usare Lilydev come spiegato in
Avvio rapido.
Anche i collaboratori che usano Linux o FreeBSD possono usare Lilydev, ma se
preferiscono il proprio ambiente di sviluppo, devono leggere
Lavorare col codice sorgente e
Compilare.
Si consiglia di iniziare con la lettura
del
Sommario per programmatori esperti.
Sponsor
Remunerazioni (bounty)
In passato,
- alcuni utenti hanno pagato per avere nuove funzionalità
- alcuni sviluppatori hanno aggiunto nuove funzionalità a pagamento
Il progetto LilyPond non coordina queste iniziative; non appoggiamo
né scoraggiamo tali accordi. Qualsiasi contratto tra individui
privati è affar loro, non nostro.
Linee guida
Gli utenti che desiderano offrire del denaro in cambio di lavoro devono
tenere a mente i seguenti punti:
-
Gli sviluppatori di LilyPond talvolta pubblicizzano i propri servizi sulle
liste email di lilypond.
-
Qualsiasi accordo tra singoli individui deve includere le normali
precauzioni da prendere quando si conduce un affare: chi paga, quanto
paga, con quale metodo di pagamento e in base a quali
condizioni. Suggeriamo di risolvere qualsiasi ambiguità o incertezza
su tali questioni prima che il lavoro inizi.
Sviluppatori interessati
Di seguito riportiamo una lista di persone interessate a lavorare
dietro remunerazione. Si noti che la quantità di lavoro fatto da parte dei
singoli varia nel corso degli anni. Non garantiamo che questa lista
sia aggiornata, né che le persone qui elencate abbiano particolari
abilità. L’unico criterio è "XYZ ha chiesto di essere
inserito in questa pagina".
Un buon modo per sapere quali sono gli sviluppatori più attivi e preparati
è guardare la storia del repository git. Statistiche fino alla versione
2.19.65:
Sviluppatori interessati:
- mailing list degli sviluppatori di LilyPond
In questo momento nessuno programmatore si è proposto per fornire miglioramenti
di LilyPond a pagamento, ma è comunque possibile provare a chiedere nella
mailing list degli sviluppatori.
Sviluppo
Sviluppo di LilyPond 2.21.0
Numeri di versione
LilyPond viene distribuito in due versioni: la versione stabile e quella
di sviluppo o instabile. Le versioni stabili hanno un numero di versione
‘minore’ pari (per esempio 2.8, 2.10, 2.12). Le versioni di sviluppo
hanno un numero di versione ‘minore’ dispari (per esempio 2.7, 2.9, 2.11).
Guida del Collaboratore
Lo sviluppo di LilyPond è piuttosto complesso. Per aiutare i
nuovi collaboratori e mantenere l’intero sistema (tendenzialmente)
stabile, abbiamo scritto un manuale per i compiti di sviluppo.
Manuali
Nota: Questi manuali sono per LilyPond 2.21.0; gli ultimi
manuali sono reperibili su http://lilypond.org
Google Summer of Code
What is Google Summer of Code?
GSoC is a global program
that offers students stipends to write code for free software and open
source projects during the summer. For three months students work to
complete a given task as part of the project’s community and under the
guidance of experienced mentors. The program is an excellent
opportunity for students to gain experience with real-world software
development and make a contribution that benefits everyone. It brings
new contributors to LilyPond and enables students who are already
involved to become more involved. LilyPond participates in GSoC as part
of the GNU project.
We have had GSoC participants in 2012, 2015, 2016 and 2017. This site
will be updated in time before the 2018 season will start.
Project Ideas List
Below is a list of GSoC project ideas (last update: May 2017), but
if you have other ideas for a project you may complete within the three
months of the program you’re welcome to make a suggestion on our
developer mailing list (see Contatti). There are a number of areas
where LilyPond could be improved, and our development team is always
willing to help those who would like to tackle a project similar to
those listed below. As mentor availability varies from project to
project and from year to year it is wise to get in touch with us as
early as possible.
A full list of all the current open issues can be found
here.
Adopt the SMuFL music font encoding standard
For several years now a new standard for music fonts has been around:
SMuFL, which is also discussed as becoming part of
a future W3C standard for music encoding. As a FLOSS tool LilyPond should
adhere to such an open standard instead of using an isolated solution like it
does today. Adopting SMuFL will help integrating LilyPond with the world of
music notation software and eventually give LilyPond users access to a wider
selection of notation fonts.
Making LilyPond compliant to SMuFL includes remapping of the glyphs that are
built from METAFONT sources, adjusting the glyphs’ metrics to SMuFL’s
specifications, and finally updating the way LilyPond looks up and positions the
glyphs. As an optional part of this project LilyPond’s font loading mechanism
could be modified to use notation fonts installed as system fonts instead of
inside the LilyPond installation.
Difficulty: Easy/medium
Requirements: C++ and willingness to get familiar with LilyPond
internals.
Recommended: Interest and experience in working with font files.
A little bit of METAFONT.
Mentors: Werner Lemberg, Abraham Lee
Adding variants of font glyphs
-
Adding ‘on’ and ‘between’ staff-line variants.
-
Shorter and narrower variants of some glyphs for example, accidentals.
Another, more specific example could be an ancient notation breve
notehead coming in two variants one with a small or big ‘hole’ within
it.
Difficulty: easy
Requirements: MetaFont, C++, good eye for details
Recommended knowledge: basic LilyPond knowledge
Mentor: Werner Lemberg
Contemporary Notation
LilyPond is very good at creating non-standard notation. Having to
code every graphical element instead of simply drawing
it may seem cumbersome but is in fact a strong asset. New notational
functionality can be provided with consistent appearance, automatic
layout and a natural syntactic interface.
Within the openLilyLib
library system the student will create a fundamental infrastructure
and building blocks to make creating contemporary notation easier.
Additionally (at least) one concrete package is developed to
cover specific contemporary notation, such as for example the style
of a given composer, extended playing techniques for a specific
instrument or a certain category of effects.
Difficulty: medium
Requirements: Scheme (interaction with LilyPond internals),
contemporary notation techniques
Recommended: sense of building hierarchical frameworks
Mentors: NN, Urs Liska
Rewrite LibreOffice LilyPond Extension with Python
The OOoLilyPond extension
made it possible to conveniently include LilyPond score snippets in
OpenOffice.org/LibreOffice Writer, Draw and Impress documents while
keeping source and image together. After many years without development
an initial effort has started to make the extension compatible again
with current versions of LibreOffice and LilyPond.
However, as the LibreOffice ecosystem has changed substantially it is
now possible to rewrite the extension with Python and PyQt. This will
not only be more powerful in general but will allow the integration of
functionality from Frescobaldi, such as
for example syntax highlighting, entry helpers, score wizards or musical
transformations.
Difficulty: easy/medium
Requirements: Python, PyQt, LilyPond basics, LibreOffice
extension basics
Recommended knowledge: Familiarity with Frescobaldi code based
or willingness to learn during bonding period
Mentor(s): Joram Berger, Urs Liska, (Thorsten Behrens/LibreOffice)
Automated testing and documentation for openLilyLib
openLilyLib is an extension
framework for LilyPond code providing a “snippets” repository and a
suite of integrated packages such as for example page layout tools or
scholarly annotations. It is very powerful and promising, but to really
get off the ground two features are missing: automated testing and
documentation generation.
Automated testing is necessary to ensure modifications to functionality
don’t break other functions within the library. There is already some
Automated Testing of the “snippets” repository with Github’s Travis
server, but this has to be reconsidered and extended to cover the
standalone packages too.
In order to be usable for a wider range of LilyPond users on a “consumer
level” openLilyLib needs proper documentation. This documentation has
to be generated from the sources, so a system is needed that requires
package authors to document the input files and provide additional usage
examples, from which documentation is generated. Ideally but not
necessarily this is implemented as a Git hook, i.e. automatically upon
each update to the repository. We don’t prescribe the tools and
approaches to be used, but the most widely used language in the LilyPond
domain is Python, so there would be some bias towards that.
Alternatively a Scheme solution could be fine so generating the
documentation would actually be triggered by “compiling” a certain
LilyPond input file. In general it is advisable to make use of proven
concepts and tools from other languages.
The eventual output of the documentation should be a static HTML site
that can be viewed locally and/or uploaded to a website. But it would
be beneficial if the tool would first generate an intermediate
representation (e.g. a JSON file with additional media files) from which
a Single Page Application could retrieve content for display on
openLilyLib’s website. Development of
such a SPA can be part of the GSoC project, but is optional.
Difficulty: medium
Requirements: Python or Scheme, static website generator(s) or
(Node.js based) dynamic web application technology. Continuous
Integration (can be learned during the bonding period)
Mentors: Urs Liska, Matteo Ceccarello
MusicXML
Improving MusicXML import and export functions:
File interchange between LilyPond and other applications using MusicXML
is still a difficult matter. To import MusicXML it has to be converted
manually by the musicxml2ly script. Export to MusicXML is
only available as a rudimentary feature inside Frescobaldi. In order to
provide natural interchange between LilyPond and MusicXML based
applications there’s the need of actual import functionality and a
dedicated export backend.
Importing XML shall provide file, line and column to add origin
attributes to generated objects. That way point and click can be
made available in Frescobaldi or other supported IDEs.
Exporting XML shall be realized with an exporter class like the MIDI
export. This may be based on the work already done in
GSoC 2015
by David Garfinkle. It should be checked if it is possible to use
another XML library than the one provided by guile-2 in order to have
this feature available in current LilyPond (which is based on guile-1.8).
Difficulty: medium
Requirements: MusicXML, Python, Scheme, basic LilyPond knowledge
Recommended: Familiarity with other scorewriters (for cross-testing)
Mentor: Jan-Peter Voigt
Information for Applicants/Participants
In order to have a satisfying experience with GSoC applicants are
strongly advised to thoroughly read the following recommendations. Some
of these are relevant for the application process, others for the time
within the project.
-
Read all applicable information on the program’s website, particularly
the
students’ manual. Make sure you fulfil all of Google’s prerequisites
and are willing to join the program as a full-time commitment over the
coding period of three months.
-
Please get in touch with us as soon as possible if you are interested in
applying with a project. Mentor availability may change without notice,
project proposals may need fine-tuning, and many other reasons might
require us to reject or ignore an application that hasn’t been discussed
before.
-
We do not know in advance how many “slots” we will have available for
projects, so please be aware that you may find yourself in competition
with other applicants or not. Interested or even enthusiastic response
from our mentors is no guarantee of eventually being accepted, and
not being accepted does not necessarily indicate a negative
evaluation of your application. If we have to decide between different
applicants there may be various aspects to consider.
-
Integration in the LilyPond community is a fundamental part of GSoC, and
we expect our students to make substantial efforts to become community
members. Within the bonding period we expect you to write a blog
post about your project (either on Scores of Beauty or on any other blog) and to be active on our mailing lists,
introducing yourself but also communicating about unrelated tasks. This
goes beyond the mere setting up of a working environment and
familiarizing yourself with the relevant code, but we think it is
crucial for the GSoC project to be mutually satisfying.
-
If you are accepted to the program you will have one mentor explicitly
assigned to your project. With this mentor you will have to agree upon
a communication strategy, be it emails, chatrooms, issue trackers or
voice/video chats. Regular communication is absolutely crucial for the
success of a GSoC project so you are stricly required to keep talking to
your mentor. But keep in mind that your mentor has explicitly taken
over the responsibility for your project, and while unlike you he isn’t
paid for this activity you are still entitled to get regular attention
from him.
-
In order to get support from your mentor you have to give him a chance
to follow your progress and efforts. Therefore it is important to
regularly commit your changes to the versioning repository you are
working on. Don’t hesitate making unfinished code available because you
are afraid of criticism, and don’t suppress questions because you think
they might be considered stupid. But ideally your code should at any
time be accompanied by compatible testing code. Your mentor may not be
able to properly assess your code by only reading it without the
opportunity to apply it in a real example.
There is a list of inactive projects in the Soffitta. We list
projects there that are still considered valuable but for which there
are currently no mentors available.
Autori
Team di Sviluppo attuale
- Trevor Daniels:
t.daniels@treda.co.uk,
Assistant documentation editor
- Colin Hall:
Bug meister
- Phil Holmes:
mail@philholmes.net
http://www.philholmes.net
Build unentangler, Bug squad member
- David Kastrup:
dak@gnu.org,
hard core developer, user and programming interfaces, bug squashing and
swamp drainage.
- Werner Lemberg,
wl@gnu.org,
Fonts, bug squasher
- Han-Wen Nienhuys:
hanwen@xs4all.nl,
http://www.xs4all.nl/~hanwen/,
Main author
- Jan Nieuwenhuizen:
janneke@gnu.org,
http://JoyofSource.com,
http://AvatarAcademy.nl,
Main author
- Mark Polesky:
Documentation, Code cleanup
- Carl Sorensen:
c_sorensen@byu.edu,
Core developer
- Francisco Vila:
Translation Meister
- Valentin Villenave:
Core developer
- Janek Warchoł:
janek.lilypond@gmail.com,
Core developer
Team di Sviluppo precedente
- Mats Bengtsson:
mats.bengtsson@ee.kth.se,
https://www.kth.se/profile/matben/,
Support guru
- Bertrand Bordage:
bordage.bertrand@gmail.com,
Core developer, font designer
- Ian Hulin:
Core developer
- Reinhold Kainhofer:
reinhold@kainhofer.com,
http://reinhold.kainhofer.com,
Core developer, Music2xml wrangler
- Pedro Kroeger:
Build meister
- Jonathan Kulp:
Assistant documentation editor
- Joe Neeman:
Core developer
- John Mandereau:
john.mandereau@free.fr,
Translation meister
- Patrick McCarty:
SVG guru, bug squad member, bug squasher, text handling
- Graham Percival:
http://percival-music.ca,
Bug meister, Grand Documentation Project leader
- Neil Puttock:
Core developer
- Jürgen Reuter:
reuter_j@web.de,
http://www.juergen-reuter.de,
Ancient notation
- Mike Solomon:
mike@mikesolomon.org,
Core developer, Frog meister
- Erik Sandberg:
Bug meister
- Nicolas Sceaux:
Core developer, Schemer extraordinaire
Collaboratori attuali
Programmazione
Guido Aulisi,
Joe Austin,
Federico Bruni,
Nathan Chou,
Dan Eble,
John Gourlay,
Marc Hohl,
Masamichi Hosoda,
Mark Knoop,
Tobias Kretschmar,
Vincent Le Ligeour,
James Lowe,
Thomas Morley,
Paul Morris,
David Nalesnik,
Keith OHara,
Benkő Pál,
Knut Petersen,
Julien Rioux,
Ben Rudiak-Gould,
Devon Schudy,
Heikki Tauriainen
Font tipografico
Jay Anderson,
Masamichi Hosoda,
Abraham Lee
Documentazione
Simon Albrecht,
Frédéric Bron,
Federico Bruni,
Colin Campbell,
Urs Liska,
James Lowe,
Thomas Morley,
Jean-Charles Malahieude,
Patrick Schmidt,
Pierre Perol-Schneider,
Greg Swinford,
Martin Tarenskeen
Bug squad
Simon Albrecht,
Federico Bruni,
Colin Campbell,
Phil Holmes,
Ralph Palmer
Supporto
Simon Albrecht,
Colin Campbell,
Eluze,
Marc Hohl,
Phil Holmes,
Marek Klein,
Alex Loomis,
Kieren MacMillan,
Thomas Morley,
Tim McNamara,
Paul Morris,
David Nalesnik,
Urs Liska,
Ralph Palmer,
Pierre Perol-Schneider,
Neil Puttock,
Tao
Traduzione
Federico Bruni,
Luca Rossetto Casel,
Felipe Castro,
Pavel Fric,
Walter Garcia-Fontes,
Tommaso Gordini,
Erika Griechisch,
Denes Harmath,
Masamichi Hosoda,
Jean-Charles Malahieude,
Till Paala,
Yoshiki Sawada,
Tomohiro Tatejima,
Paco Tomillo
Collaboratori precedenti
Programmazione
Erlend Aasland,
Maximilian Albert,
Aleksandr Andreev,
Guido Amoruso,
Sven Axelsson,
Kristof Bastiaensen,
Pál Benkő,
Frédéric Bron,
Juliusz Chroboczek,
Peter Chubb,
Angelo Contardi,
Vicente Solsona Della,
Hajo Dezelski,
Michael Welsh Duggan,
David Feuer,
Bertalan Fodor,
Richard Gay,
Mathieu Giraud,
Lisa Opus Goldstein,
Torsten Hämmerle,
Yuval Harel,
Andrew Hawryluk,
Christian Hitz,
Karin Hoethker,
Rutger Hofmann,
Marc Hohl,
Bernard Hurley,
Yoshinobu Ishizaki,
Chris Jackson,
Felix Janda,
David Jedlinsky,
Heikki Junes,
Michael Käppler,
Thomas Klausner,
Marek Klein,
Michael Krause,
Jean-Baptiste Lamy,
Jonatan Liljedahl,
Peter Lutek,
Andrew Main,
Kieren MacMillan,
Hendrik Maryns,
Thomas Morgan,
David Nalesnik,
Matthias Neeracher,
Keith OHara,
Justin Ohmie,
Tatsuya Ono,
Benkő Pál,
Benjamin Peterson,
Guy Gascoigne-Piggford,
Anders Pilegaard,
Henning Hraban Ramm,
Nathan Reed,
Julien Rioux,
Johannes Rohrer,
Stan Sanderson,
Andreas Scherer,
Johannes Schindelin,
Patrick Schmidt,
Boris Shingarov,
Kim Shrier,
Edward Sanford Sutton,
Adam Spiers,
David Svoboda,
Heikki Taurainen,
Piers Titus van der Torren,
Owen Tuz,
Sebastiano Vigna,
Jan-Peter Voigt,
Arno Waschk,
John Williams,
Andrew Wilson,
Milan Zamazal,
Rune Zedeler,
Rodolfo Zitellini
Font tipografico
Tom Cato Amundsen,
Marc Hohl,
Chris Jackson,
Alexander Kobel,
Abraham Lee,
Keith OHara,
Carsten Steger,
Arno Waschk,
Rune Zedeler
Documentazione
Erlend Aasland,
Trevor Bača,
Alard de Boer,
Colin Campbell,
Jay Hamilton,
Joseph Harfouch,
Andrew Hawryluk,
Cameron Horsburgh,
Geoff Horton,
Heikki Junes,
Kurtis Kroon,
James Lowe,
Dave Luttinen,
Kieren MacMillan,
Christian Mondrup,
Mike Moral,
Eyolf Østrem,
Ralph Palmer,
François Pinard,
David Pounder,
Michael Rasmussen,
Till Rettig,
Pavel Roskin,
Patrick Schmidt,
Alberto Simoes,
Guy Stalnaker,
Arnold Theresius,
Anh Hai Trinh,
Eduardo Vieira,
Stefan Weil,
Rune Zedeler,
Rodolfo Zitellini
Supporto
Colin Campbell,
Anthony Fok,
Christian Hitz,
Phil Holmes,
Chris Jackson,
Heikki Junes,
David Svoboda
Traduzione
Alard de Boer,
Federico Bruni,
Abel Cheung,
Frédéric Chiasson,
Simon Dahlbacka,
Orm Finnendahl,
David González,
Nicolas Grandclaude,
Dénes Harmath,
Damien Heurtebise,
Bjoern Jacke,
Matthieu Jacquot,
Neil Jerram,
Heikki Junes,
Nicolas Klutchnikoff,
Jean-Charles Malahieude,
Adrian Mariano,
Christian Mondrup,
Tineke de Munnik,
Steven Michael Murphy,
Till Paala,
François Pinard,
Gauvain Pocentek,
Till Rettig,
Ludovic Sardain,
Yoshiki Sawada,
Thomas Scharkowski,
Clytie Siddall,
August S. Sigov,
Roland Stigge,
Risto Vääräniemi,
Andrea Valle,
Ralf Wildenhues,
Olcay Yıldırım
Riconoscimenti
Pubblicazioni
Cosa abbiamo scritto su LilyPond
-
Server Acim.
GNU/LilyPond (Turkish Language).
2013.
(PDF 2100k).
-
Graham Percival.
Sustainability in F/OSS: developers as a non-renewable resource.
In Rencontres Mondiales du Logiciel Libre 2010 (RMLL2010), 2010.
(PDF 333k).
-
Han Wen Nienhuys and Jan Nieuwenhuizen.
LilyPond, a system for automated music engraving.
In Colloquium on Musical Informatics (XIV CIM 2003), May 2003.
(PDF 95k).
-
Han Wen Nienhuys.
LilyPond, Automated music formatting and the Art of Shipping.
In Forum Internacional Software Livre 2006 (FISL7.0), 2006.
(PDF 1095k).
-
Margarethe Maierhofer Lischka & Florian Hollerweger.
Lilypond: music notation for everyone!.
In Linux Audio Conference 2013 (LAC2013), 2013.
(PDF 890k).
-
Reinhold Kainhofer.
OrchestralLily: A Package for Professional Music Publishing with
LilyPond and LATEX.
In The Linux Audio Conference 2010 (LAC2010), 2010.
(PDF 767k).
-
Erik Sandberg.
Separating input language and formatter in GNU LilyPond.
Master’s thesis, Uppsala University, Department of Information Technology,
March 2006.
(PDF 750k).
-
Francisco Vila.
Tipografía musical para la educación y análisis de la dinámica del
software libre (Spanish language).
PhD thesis, Universidad de Extremadura, 2015.
(PDF 20M).
Cosa altri hanno fatto con LilyPond
-
Kevin C. Baird.
Real-time generation of music notation via audience interaction using
python and GNU LilyPond.
In New Interfaces for Music Expression, May 2005.
-
Alexandre Tachard Passos, Marcos Sampaio, Pedro Kröger, and Givaldo de Cidra.
Functional Harmonic Analysis and Computational Musicology in Rameau.
In Proceedings of the 12th Brazilian Symposium on Computer Music, pages
207–210, 2009.
-
Graham Percival, Tosten Anders, and George Tzanetakis.
Generating Targeted Rhythmic Exercises for Music Students with
Constraint Satisfaction Programming.
In International Computer Music Conference, 2008.
-
Alberto Simões, Anália Lourenço, and José João Almeida. (J. Neves et al.,
editor).
Using Text Mining Techniques for Classical Music Scores Analysis.
In New Trends in Artificial Intelligence, 2007.
Notizie
Nota: Molti dei vecchi annunci e changelog si possono trovare
in Soffitta
Rilasciato LilyPond 2.19.60 8 maggio 2017
Siamo felici di annunciare il rilascio di LilyPond
2.19.60. Questo rilascio comprende vari miglioramenti e contiene anche
funzionalità non ancora complete. Permette di avere accesso alle funzionalità
più recenti, ma è bene tenere presente che alcune potrebbero essere incomplete
e non si possono escludere difetti o crash del programma. A chi necessita di
una versione stabile di LilyPond consigliamo di usare la versione 2.18.
Rilasciato LilyPond 2.18.2! 23 marzo 2014
Siamo orgogliosi di annunciare il rilascio di GNU LilyPond 2.18.2.
LilyPond è un programma di notazione musicale dedicato alla produzione
di spartiti musicali della migliore qualità possibile. Introduce nelle
stampe prodotte dai computer l’estetica della musica incisa secondo i
metodi tradizionali.
Questa versione fornisce vari aggiornamenti alla 2.18.0, tra cui i
manuali aggiornati. Consigliamo tutti gli utenti di aggiornare a
questa versione.
Due progetti LilyPond accettati al Google Summer of Code 2016 23 aprile 2016
Siamo felici di vedere due studenti, Nathan Chou e Jeffery Shivers, al lavoro
su LilyPond in qualità di partecipanti del Google Summer of Code di quest’anno.
Ci auguriamo che possano ottenere grandi risultati e che restino nella comunità
degli sviluppatori anche in seguito.
Nathan affronterà una fastidiosa limitazione, ovvero l’impossibilità degli
estensori di attraversare le voci. Il suo lavoro renderà obsoleto un insieme
di orribili soluzioni temporanee.
Jeffery porterà il pacchetto ScholarLY[1] a un livello qualitativo maturo e
aggiungerà un pacchetto LaTeX, rendendo possibile la creazione di relazioni
critiche a partire dai dati inseriti direttamente nella partitura LilyPond.
[1] https://github.com/openlilylib/scholarly
Rilasciato LilyPond 2.18.0! 29 dicembre 2013
Siamo felici di annunciare il rilascio di GNU LilyPond 2.18.0.
LilyPond è un programma di notazione musicale dedicato alla produzione
di spartiti musicali della migliore qualità possibile. Introduce nelle
stampe prodotte dai computer l’estetica della musica incisa secondo i
metodi tradizionali.
Tra i numerosi miglioramenti e cambiamenti, i seguenti sono i più rilevanti:
-
Molti elementi sono ora posizionati usando il loro reale contorno invece
di un riquadro rettangolare. Ciò riduce enormemente il numero di
grandi e sgradevoli spazi vuoti.
-
Le impostazioni e le sovrascritture possono usare ora la sintassi
\override Voice.TextSpanner.bound-details.left.text = "rit."
invece della precedente
\override Voice.TextSpanner #'(bound-details left text) = "rit."
-
Le terzine aventi la stessa durata per ciascun gruppo si possono scrivere
\tuplet 3/2 4 { c8 c c c c c }
invece di
\times 2/3 { c8 c c } \times 2/3 { c8 c c }
Un elenco completo delle nuove funzionalità degne di nota si trova in:
http://lilypond.org/doc/v2.18/Documentation/changes/index.it.html
Un grande ringraziamento all’ampio gruppo di persone entusiaste di LilyPond
il cui contributo finanziario ha fatto sì che uno degli sviluppatori
principali, David Kastrup, potesse dedicarsi interamente a LilyPond
durante l’intero ciclo di sviluppo.
LilyPond 2.18 è stato realizzato da
- Principali sviluppatori:
Bertrand Bordage, Trevor Daniels, Colin Hall, Phil Holmes, Ian
Hulin, Reinhold Kainhofer, David Kastrup, Jonathan Kulp, Werner
Lemberg, John Mandereau, Patrick McCarty, Joe Neeman, Han-Wen
Nienhuys, Jan Nieuwenhuizen, Graham Percival, Mark Polesky, Neil
Puttock, Mike Solomon, Carl Sorensen, Francisco Vila, Valentin
Villenave, Janek Warchoł
- Principali collaboratori:
Aleksandr Andreev, Frédéric Bron, Torsten Hämmerle, Marc Hohl,
James Lowe, Andrew Main, Thomas Morley, David Nalesnik, Keith
OHara, Benkő Pál, Anders Pilegaard, Julien Rioux, Johannes Rohrer,
Adam Spiers, Heikki Tauriainen
- Autori della documentazione:
Frédéric Bron, Federico Bruni, Colin Campbell, Urs Liska, James
Lowe, Thomas Morley, Jean-Charles Malahieude, Guy Stalnaker,
Martin Tarenskeen, Arnold Theresius, Rodolfo Zitellini
- Bug Squad:
Colin Campbell, Eluze, Marc Hohl, Phil Holmes, Marek Klein, Ralph
Palmer
- Team di supporto:
Colin Campbell, Eluze, Marc Hohl, Marek Klein, Kieren MacMillan,
Urs Liska, Ralph Palmer
- Traduttori:
Federico Bruni, Luca Rossetto Casel, Felipe Castro, Pavel Fric,
Jean-Charles Malahieude, Till Paala, Yoshiki Sawada
e molti altri collaboratori.
Vecchie notizie
Le vecchie notizie si trovano in Soffitta, insieme a vecchi annunci
e registri di modifiche (changelog).
Soffitta
Annunci
Annunci e notizie ordinati per versione:
v2.16,
v2.14,
v2.12,
v2.10,
v2.8,
v2.6,
v2.4,
v2.2,
v2.0,
v1.2,
v1.0,
v0.1
Elenco descrittivo dei cambiamenti per ogni versione:
v2.16,
v2.14,
v2.12,
v2.10,
v2.8,
v2.6,
v2.4,
v2.2,
v2.0,
v1.8,
v1.6,
v1.4,
v1.2
Grazie
Grazie a sviluppatori, collaboratori, cacciatori di bug e a chi ci ha dato
preziosi suggerimenti
v2.16,
v2.14,
v2.12,
v2.10,
v2.8,
v2.6,
v2.4,
v2.2,
v2.0,
v1.8
Lista dei cambiamenti
Lista dei cambiamenti apportati da ciascun sviluppatore in ogni versione:
v2.10,
v2.3,
v2.1,
v1.5 (1),
v1.5 (2),
v1.4,
v1.3,
v1.2,
v1.1,
v1.0,
v0.1,
v0.0
Inactive Google Summer of Code project suggestions
The following list describes GSoC projects that had been proposed
in recent years and which are still considered valuable but for
which we currently don’t have mentors available.
Improve slurs and ties
The engraving quality of slurs and ties is often unsatisfactory. Ties
‘broken’ by clef or staff changes are not handled well. The project
could include collecting and sorting examples of bad output, deciding on
the intended output and writing code to improve them.
Difficulty: hard
Requirements: C++, experience with writing heuristics
Recommended knowledge: LilyPond knowledge, aesthetic sense
Grace notes
Fix problems with synchronization of grace notes. Grace notes can
interfere with LilyPond’s timing and cause odd effects, especially when
multiple staffs are used where some have grace notes and others don’t.
This is one of the longest-standing and one of the more embarrassing
bugs in
LilyPond.
Difficulty: medium
Requirements: C++, MIDI
Recommended: familiarity with LilyPond internals
Improve default beam positioning
For regular, cross-staff, broken and kneed beams. Beaming should depend
on context and neighbor notes (see section 2.2 of
this book). If possible also reduce beaming-computation time.
Difficulty: medium
Requirements: C++, experience with writing heuristics
Recommended knowledge: aesthetic sense
Help improve compilation behavior
Automatic code analysis tools, like valgrind memory leak detection or
callgrind code profilers, provide valuable information about possible
flaws in our C++ code. Cleaning up warnings would allow us to automate
the rejection of any patch which introduced extra warnings.
Difficulty: medium
Requirements: C++
Vecchie notizie
Le vecchie notizie che risalgono fino al luglio 2003. Le notizie più recenti
si trovano alla pagina Notizie.
LilyPond 2.19.64 released July 15, 2017
We are happy to announce the release of LilyPond
2.19.64. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.63 released June 28, 2017
We are happy to announce the release of LilyPond
2.19.63. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.62 released June 10, 2017
We are happy to announce the release of LilyPond
2.19.62. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.61 released May 21, 2017
We are happy to announce the release of LilyPond
2.19.61. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.60 released May 08, 2017
We are happy to announce the release of LilyPond
2.19.60. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.59 released April 09, 2017
We are happy to announce the release of LilyPond
2.19.59. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.58 released March 26, 2017
We are happy to announce the release of LilyPond
2.19.58. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.57 released March 12, 2017
We are happy to announce the release of LilyPond
2.19.57. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.56 released February 26, 2017
We are happy to announce the release of LilyPond
2.19.56. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.55 released February 12, 2017
We are happy to announce the release of LilyPond
2.19.55. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.54 released January 4, 2017
We are happy to announce the release of LilyPond
2.19.54. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.53 released December 17, 2016
We are happy to announce the release of LilyPond
2.19.53. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.52 released December 4, 2016
We are happy to announce the release of LilyPond
2.19.52. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.51 released November 20, 2016
We are happy to announce the release of LilyPond
2.19.51. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.50 released November 6, 2016
We are happy to announce the release of LilyPond
2.19.50. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.49 released October 16, 2016
We are happy to announce the release of LilyPond
2.19.49. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.48 released September 13, 2016
We are happy to announce the release of LilyPond
2.19.48. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.47 released August 31, 2016
We are happy to announce the release of LilyPond
2.19.47. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.46 released July 26, 2016
We are happy to announce the release of LilyPond
2.19.46. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.45 released July 09, 2016
We are happy to announce the release of LilyPond
2.19.45. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.44 released June 21, 2016
We are happy to announce the release of LilyPond
2.19.44. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.43 released June 8, 2016
We are happy to announce the release of LilyPond
2.19.43. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.42 released May 15, 2016
We are happy to announce the release of LilyPond
2.19.42. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.41 released May 1, 2016
We are happy to announce the release of LilyPond
2.19.41. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.40 released April 17, 2016
We are happy to announce the release of LilyPond
2.19.40. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.39 released March 27, 2016
We are happy to announce the release of LilyPond
2.19.39. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.38 released March 13, 2016
We are happy to announce the release of LilyPond
2.19.38. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.37 released February 28, 2016
We are happy to announce the release of LilyPond
2.19.37. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.36 released January 31, 2016
We are happy to announce the release of LilyPond
2.19.36. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.35 released January 02, 2016
We are happy to announce the release of LilyPond
2.19.35. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.34 released December 22, 2015
We are happy to announce the release of LilyPond
2.19.34. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.33 released December 6, 2015
We are happy to announce the release of LilyPond
2.19.33. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.32 released November 22, 2015
We are happy to announce the release of LilyPond
2.19.32. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.31 released November 8, 2015
We are happy to announce the release of LilyPond
2.19.31. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.30 released October 25, 2015
We are happy to announce the release of LilyPond
2.19.30. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.29 released October 18, 2015
We are happy to announce the release of LilyPond
2.19.29. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.28 released September 27, 2015
We are happy to announce the release of LilyPond
2.19.28. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.27 released September 12, 2015
We are happy to announce the release of LilyPond
2.19.27. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.26 released August 27, 2015
We are happy to announce the release of LilyPond
2.19.26. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.25 released August 9, 2015
We are happy to announce the release of LilyPond
2.19.25. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.24 released July 26, 2015
We are happy to announce the release of LilyPond
2.19.24. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.23 released July 12, 2015
We are happy to announce the release of LilyPond
2.19.23. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.22 released June 28, 2015
We are happy to announce the release of LilyPond
2.19.22. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.21 released May 24, 2015
We are happy to announce the release of LilyPond
2.19.21. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.20 released May 10, 2015
We are happy to announce the release of LilyPond
2.19.20. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.19 released April 26, 2015
We are happy to announce the release of LilyPond
2.19.19. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.18 released April 5, 2015
We are happy to announce the release of LilyPond
2.19.18. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.17 released March 15, 2015
We are happy to announce the release of LilyPond
2.19.17. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.16 released February 28, 2015
At long last, we are very happy to announce the release of LilyPond
2.19.16. This release includes a number of enhancements, and contains some
work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
We would like to acknowledge and thank Masamichi Hosoda for making this
release possible with his work on updating GUB, the build tool.
LilyPond 2.19.15 released September 28, 2014
We are happy to announce the release of LilyPond 2.19.15. This
release includes a number of enhancements, and contains some work
in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.14 released September 14, 2014
We are happy to announce the release of LilyPond 2.19.14. This
release includes a number of enhancements, and contains some work
in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.13 released August 31, 2014
We are happy to announce the release of LilyPond 2.19.13. This
release includes a number of enhancements, and contains some work
in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.12 released August 17, 2014
We are happy to announce the release of LilyPond 2.19.12. This
release includes a number of enhancements, and contains some work
in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.11 released August 3, 2014
We are happy to announce the release of LilyPond 2.19.11. This
release includes a number of enhancements, and contains some work
in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.10 released July 13, 2014
We are happy to announce the release of LilyPond 2.19.10. This
release includes a number of enhancements, and contains some work
in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.9 released June 29, 2014
We are happy to announce the release of LilyPond 2.19.9. This
release includes a number of enhancements, and contains some work
in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.8 released June 15, 2014
We are happy to announce the release of LilyPond 2.19.8. This
release includes a number of enhancements, and contains some work
in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.7 released May 25, 2014
We are happy to announce the release of LilyPond 2.19.7. This
release includes a number of enhancements, and contains some work
in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.6 released May 11, 2014
We are happy to announce the release of LilyPond 2.19.6. This
release includes a number of enhancements, and contains some work
in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you
require a stable version of LilyPond, we recommend using the 2.18
version.
LilyPond 2.19.5 released April 20, 2014
We are happy to announce the release of LilyPond 2.19.5. This
release includes a number of enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
a stable version of LilyPond, we recommend using the 2.18 version.
LilyPond 2.19.4 released April 6, 2014
We are happy to announce the release of LilyPond 2.19.4. This
release includes a number of enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
a stable version of LilyPond, we recommend using the 2.18 version.
LilyPond production named BEST EDITION 2014 March 11, 2014
We are thrilled that the edition of the songs of Oskar
Fried (1871-1941), published recently by our fellow contributors Urs Liska
and Janek Warchoł [1], received the "Musikeditionspreis BEST EDITION
2014" of the German Music Publishers’ Association [2]. The ceremony
took place at the Frankfurt Musikmesse.
We congratulate Janek and Urs for gaining such public recognition of
typographical and editorial excellence of their work. We are also delighted
to inform you that they intend to make their work available under a Free
license as soon as the publisher expenses are covered. Please support this
initiative by buying the printed volume through the publisher [3].
[1] http://lilypondblog.org/category/fried-songs
[2] http://www.best-edition.de
[3] http://www.sound-rel.de
LilyPond 2.19.3 released March 2, 2014
We are happy to announce the release of LilyPond 2.19.3. This
release includes a number of enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
a stable version of LilyPond, we recommend using the 2.18 version.
LilyPond 2.18.1 February 16, 2014
We have released updated manuals for LilyPond’s stable version, 2.18.
The manuals are now for 2.18.1 and have a number of updates and improvements
over 2.18.0. There will be a further release of 2.18 in the future (2.18.2),
and this will include the updates to the manuals as well as some minor
enhancements to the LilyPond core functionality.
To summarise the current situation: stable LilyPond application: 2.18.0;
stable LilyPond manuals: 2.18.1; development for both: 2.19.2.
LilyPond 2.19.2 released February 2, 2014
We are happy to announce the release of LilyPond 2.19.2. This
release includes a number of enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
a stable version of LilyPond, we recommend using the 2.18 version.
LilyPond 2.19.1 released January 19, 2014
We are happy to announce the release of LilyPond 2.19.1. This
release includes a number of enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
a stable version of LilyPond, we recommend using the 2.18 version.
LilyPond 2.19.0 released January 5, 2014
We are happy to announce the release of LilyPond 2.19.0. This
release includes a number of enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
a stable version of LilyPond, we recommend using the 2.18 version.
LilyPond 2.17.97 released! December 8, 2013
We are excited to announce the release of LilyPond 2.17.97 as
a potential final beta release for the upcoming stable release 2.18. The
developers believe this to be feature-complete, the
documentation to be accurate, and no important issues to be
overlooked. For upgrading the syntax of your input files to the
latest version, see Updating files with convert-ly.
Please test this release and report back any problems, see
Bug reports.
LilyPond 2.17.96 released! November 24, 2013
We are excited to announce the release of LilyPond 2.17.96 as
a further beta release for the upcoming stable release 2.18. The
developers believe the release to be feature-complete, the
documentation to be accurate, and no important issues to be
overlooked. For upgrading the syntax of your input files to the
latest version, see Updating files with convert-ly.
Please test this release and report back any problems, see
Bug reports.
LilyPond 2.17.95 released! November 3, 2013
We are excited to announce the release of LilyPond 2.17.95 as
beta release for the upcoming stable release 2.18. The
developers are still busy finding solutions for some last-minute
problems, but the release is supposed to be feature-complete, the
documentation to be accurate, and no important issues to be
overlooked. For upgrading the syntax of your input files to the
latest version, see Updating files with convert-ly.
Please test this release and report back any problems, see
Bug reports.
LilyPond 2.17.29 released! October 20, 2013
We are happy to announce the release of LilyPond 2.17.29. This
release contains the usual number of bugfixes and enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
a stable version of LilyPond, we recommend using the 2.16 version.
LilyPond 2.17.28 released! October 6, 2013
We are happy to announce the release of LilyPond 2.17.28. This
release contains the usual number of bugfixes and enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
a stable version of LilyPond, we recommend using the 2.16 version.
LilyPond 2.17.27 released! September 26, 2013
We are happy to announce the release of LilyPond 2.17.27. This
release contains the usual number of bugfixes and enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
a stable version of LilyPond, we recommend using the 2.16 version.
LilyPond 2.17.26 released! September 8, 2013
We are happy to announce the release of LilyPond 2.17.26. This
release contains the usual number of bugfixes and enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
a stable version of LilyPond, we recommend using the 2.16 version.
LilyPond 2.17.25 released! August 25, 2013
We are happy to announce the release of LilyPond 2.17.25. This
release contains the usual number of bugfixes and enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
a stable version of LilyPond, we recommend using the 2.16 version.
LilyPond 2.17.24 released! August 11, 2013
We are happy to announce the release of LilyPond 2.17.24. This
release contains the usual number of bugfixes and enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
a stable version of LilyPond, we recommend using the 2.16 version.
LilyPond 2.17.23 released! July 28, 2013
We are happy to announce the release of LilyPond 2.17.23. This
release contains the usual number of bugfixes and enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
a stable version of LilyPond, we recommend using the 2.16 version.
LilyPond 2.17.22 released! July 14, 2013
We are happy to announce the release of LilyPond 2.17.22. This
release contains the usual number of bugfixes and enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
a stable version of LilyPond, we recommend using the 2.16 version.
This update cures the issue with the Windows version crashing with a problem
with positioning text.
LilyPond 2.17.21 released! June 30, 2013
We are happy to announce the release of LilyPond 2.17.21. This
release contains the usual number of bugfixes and enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
a stable version of LilyPond, we recommend using the 2.16 version.
LilyPond 2.17.20 released! June 9, 2013
We are happy to announce the release of LilyPond 2.17.20. This
release contains the usual number of bugfixes and enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
a stable version of LilyPond, we recommend using the 2.16 version.
LilyPond blog. June 2, 2013
Janek Warchoł has created a LilyPond blog. You can find it at
lilypondblog.org!
LilyPond 2.17.19 released! May 26, 2013
We are happy to announce the release of LilyPond 2.17.19. This
release contains the usual number of bugfixes and enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
a stable version of LilyPond, we recommend using the 2.16 version.
LilyPond 2.17.18 released! May 11, 2013
We are happy to announce the release of LilyPond 2.17.18. This
release contains the usual number of bugfixes and enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
a stable version of LilyPond, we recommend using the 2.16 version.
LilyPond 2.17.17 released! April 27, 2013
We are happy to announce the release of LilyPond 2.17.17. This
release contains the usual number of bugfixes and enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
a stable version of LilyPond, we recommend using the 2.16 version.
LilyPond 2.17.16 released! April 13, 2013
We are happy to announce the release of LilyPond 2.17.16. This
release contains the usual number of bugfixes and enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
a stable version of LilyPond, we recommend using the 2.16 version.
LilyPond 2.17.15 released! March 30, 2013
We are happy to announce the release of LilyPond 2.17.15. This
release contains the usual number of bugfixes and enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
a stable version of LilyPond, we recommend using the 2.16 version.
LilyPond 2.17.14 released! March 10, 2013
We are happy to announce the release of LilyPond 2.17.14. This
release contains the usual number of bugfixes (including putting span bars back
where they should be) and enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
a stable version of LilyPond, we recommend using the 2.16 version.
LilyPond 2.17.13 released! February 23, 2013
We are happy to announce the release of LilyPond 2.17.13. This
release contains the usual number of bugfixes and enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
a stable version of LilyPond, we recommend using the 2.16 version.
LilyPond 2.17.12 released! February 8, 2013
We are happy to announce the release of LilyPond 2.17.12. This
release contains the usual number of bugfixes and enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
a stable version of LilyPond, we recommend using the 2.16 version.
LilyPond 2.17.11 released! January 26, 2013
We are happy to announce the release of LilyPond 2.17.11. This
release contains the usual number of bugfixes and enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
a stable version of LilyPond, we recommend using the 2.16 version.
LilyPond 2.17.10 released! January 12 2013
We are happy to announce the release of LilyPond 2.17.10. This
release contains the usual number of bugfixes and enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
a stable version of LilyPond, we recommend using the 2.16 version.
LilyPond 2.16.2 released! January 4, 2013
We are happy to announce the release of LilyPond 2.16.2. This release is mainly
to correct a problem with lilypond-book running on Windows. We recommend that
only people requiring this functionality upgrade to this version.
LilyPond 2.17.9 released! December 15, 2012
We are happy to announce the release of LilyPond 2.17.9. This
release contains the usual number of bugfixes and enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
a stable version of LilyPond, we recommend using the 2.16 version.
LilyPond 2.17.8 released! December 1, 2012
We are happy to announce the release of LilyPond 2.17.8. This
release contains the usual number of bugfixes and enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
a stable version of LilyPond, we recommend using the 2.16 version.
LilyPond 2.17.7 released! November 17, 2012
We are happy to announce the release of LilyPond 2.17.7. This
release contains the usual number of bugfixes and enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
a stable version of LilyPond, we recommend using the 2.16 version.
LilyPond 2.16.1 released! November 9, 2012
We are happy to announce the release of LilyPond 2.16.1. This has a number of
updates to the previous stable version, and should cause no problems. We
recommend that everybody upgrade to this version.
LilyPond 2.17.6 released! November 3, 2012
We are happy to announce the release of LilyPond 2.17.6. This
release contains the usual number of bugfixes and enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
a stable version of LilyPond, we recommend using the 2.16 version.
LilyPond 2.17.5 released! October 20, 2012
We are happy to announce the release of LilyPond 2.17.5. This
release contains the usual number of bugfixes and enhancements, and contains
some work in progress. You will have access to the very latest features, but
some may be incomplete, and you may encounter bugs and crashes. If you require
a stable version of LilyPond, we recommend using the 2.16 version.
LilyPond 2.17.4 released! October 6, 2012
We are happy to announce the release of LilyPond 2.17.4. This
release contains the usual number of bugfixes. It is strongly
recommended that normal users do not use this release,
and instead use the stable 2.16 version.
LilyPond 2.17.3 released! September 23, 2012
We are happy to announce the release of LilyPond 2.17.3. This
release contains the usual number of bugfixes. It is strongly
recommended that normal users do not use this release,
and instead use the stable 2.16 version.
LilyPond 2.17.2 released! September 10, 2012
We are happy to announce the release of LilyPond 2.17.2. This
release contains the usual number of bugfixes. It is strongly
recommended that normal users do not use this release,
and instead use the stable 2.16 version.
LilyPond 2.17.1 released! August 28, 2012
We are happy to announce the release of LilyPond 2.17.1. This
release contains the usual number of bugfixes. It is strongly
recommended that normal users do not use this release,
and instead use the stable 2.16 version.
LilyPond 2.17.0 released! August 26, 2012
We are happy to announce the release of LilyPond 2.17.0. This
release contains the usual number of bugfixes. It is strongly
recommended that normal users do not use this release,
and instead use the stable 2.16 version.
LilyPond 2.16.0 released! August 24, 2012
We are proud to announce the release of GNU LilyPond 2.16.0.
LilyPond is a music engraving program, devoted to producing the
highest-quality sheet music possible. It brings the aesthetics of
traditionally engraved music to computer printouts.
Many improvements have been made in the past year since the previous
main stable version. A few major improvements are:
-
Support for kievan square notation
-
User and programming interfaces have greatly improved
-
Music functions have become quite more versatile
A full list of new features is given in:
http://lilypond.org/doc/v2.16/Documentation/changes/index.html
Happy music typesetting! LilyPond 2.16 was brought to you by...
Main development team:
Bertrand Bordage, Trevor Daniels, Colin Hall, Phil Holmes, Ian Hulin,
Reinhold Kainhofer, David Kastrup, Jonathan Kulp, Werner Lemberg,
John Mandereau, Patrick McCarty, Joe Neeman, Han-Wen Nienhuys,
Jan Nieuwenhuizen, Graham Percival, Mark Polesky, Neil Puttock,
Mike Solomon, Carl Sorensen, Francisco Vila, Valentin Villenave,
Jan Warchoł
Programming contributors:
Aleksandr Andreev, Sven Axelsson, Peter Chubb, Karin Hoethker,
Marc Hohl, David Nalesnik, Justin Ohmie, Benkő Pál, Julien Rioux, Patrick Schmidt,
Adam Spiers, Heikki Taurainen, Piers Titus van der Torren,
Jan-Peter Voigt, Janek Warchol
Documentation contributors:
James Lowe, Pavel Roskin, Alberto Simoes, Stefan Weil
Bug squad:
Colin Campbell, Eluze, Phil Holmes, Marek Klein, Ralph Palmer,
James Lowe
Support:
Colin Campbell, Christian Hitz, Phil Holmes
Translation contributors:
Jean-Charles Malahieude, Till Paala, Yoshiki Sawada
LilyPond 2.15.95 released! August 11, 2012
We are excited to announce the release of LilyPond 2.15.95.
With this release, development on version 2.15 is frozen for the
upcoming 2.16 stable release and only open to bug fixes.
All users are urged to try this version to ensure the best
quality of the upcoming stable release. If you discover any
problems, please send us Segnalazione bug.
New features since 2.14.2 are listed in the “Changes” manual
on the website section about Sviluppo.
LilyPond 2.15.42 released! August 02, 2012
We are happy to announce the release of LilyPond 2.15.42. This
release contains the usual number of bugfixes.
It is strongly recommended that normal users do not use
this release, and instead use the stable 2.14 version. Please
note that due to a few Critical bugs, this is not the next release
candidate.
The LilyPond Report #27. August 2, 2012
The LilyPond Report is back, with some interesting insights on
new Scheme-related features recently added by our community’s only paid
developer David Kastrup (thanks to your
continuing donations). Also
to be found in this issue are an overview of some lesser-known LilyPond
companion projects, and a handful of more shallow factoids.
Come
read LilyPond Report 27 now; comments and contributions are
warmly encouraged!
Release candidate withdrawn July 11, 2012
We have discovered a regression since 2.14.2, so lilypond 2.15.41
is no longer a candidate for the 2.16.0 release. However, please
continue testing it – we would like to discover (and fix!) any
more regressions as soon as possible. If you discover any
problems, please send us Segnalazione bug.
Release candidate 8 of 2.16 - LilyPond 2.15.41 released! July 4, 2012
LilyPond 2.15.41 is out; this is the eighth release candidate of
the upcoming 2.16 stable release. All users are invited to
experiment with this version. New features since 2.14.2 are
listed in the “Changes” manual on the website section about
Sviluppo.
There are no known Critical issues with this release. If no
Critical bugs are found, then the official 2.16.0 release will be
on 18 July 2012. If you discover any problems, please send us
Segnalazione bug.
LilyPond 2.15.40 released! June 05, 2012
We are happy to announce the release of LilyPond 2.15.40. This
release contains the usual number of bugfixes.
It is strongly recommended that normal users do not use
this release, and instead use the stable 2.14 version. Please
note that due to a few Critical bugs, this is not the next release
candidate.
Release candidate withdrawn June 01, 2012
We have discovered a regression since 2.14.2, so lilypond 2.15.39
is no longer a candidate for the 2.16.0 release. However, please
continue testing it – we would like to discover (and fix!) any
more regressions as soon as possible. If you discover any
problems, please send us Segnalazione bug.
Release candidate 7 of 2.16 - LilyPond 2.15.39 released! May 22, 2012
LilyPond 2.15.39 is out; this is the seventh release candidate of
the upcoming 2.16 stable release. All users are invited to
experiment with this version. New features since 2.14.2 are
listed in the “Changes” manual on the website section about
Sviluppo.
There are no known Critical issues with this release. If no
Critical bugs are found, then the official 2.16.0 release will be
on 05 June 2012. If you discover any problems, please send us
Segnalazione bug.
The LilyPond Report #26. May 22, 2012
The LilyPond Report is back, with a new editor on board -
Pavel Roskin, who tells us about his adventures in strange lands
of compiler bugs! There is also a detailed report about current
development status, and an analysis of example LilyPond output -
see for yourself how close (or how far?) are we from matching
the quality of hand-engraved scores.
Come
read LilyPond Report 26 now; comments and contributions are
warmly encouraged!
Release candidate 6 of 2.16 - LilyPond 2.15.38 released! May 3, 2012
LilyPond 2.15.38 is out; this is the sixth release candidate of
the upcoming 2.16 stable release. All users are invited to
experiment with this version. New features since 2.14.2 are
listed in the “Changes” manual on the website section about
Sviluppo.
Update: Due to a few Critical bugs, another release
candidate will be required.
LilyPond takes part in Google Summer of Code 2012! April 25, 2012
Being a part of GNU project, we are participating in
Google Summer of Code program, which offers students stipends for
working on open source software.
Our contributor Janek Warchoł was accepted for 2012 edition of GSoC.
He will be working on advanced lyrics positioning in LilyPond.
Release candidate 5 of 2.16 - LilyPond 2.15.37 released! April 19, 2012
LilyPond 2.15.37 is out; this is the fifth release candidate of
the upcoming 2.16 stable release. All users are invited to
experiment with this version. New features since 2.14.2 are
listed in the “Changes” manual on the website section about
Sviluppo.
There are no known Critical issues with this release. If no
Critical bugs are found, then the official 2.16.0 release will be
on 03 May 2012. If you discover any problems, please send us
Segnalazione bug.
Release candidate 4 of 2.16 - LilyPond 2.15.36 released! April 6, 2012
LilyPond 2.15.36 is out; this is the fourth release candidate of
the upcoming 2.16 stable release. All users are invited to
experiment with this version. New features since 2.14.2 are
listed in the “Changes” manual on the website section about
Sviluppo.
There are no known Critical issues with this release. If no
Critical bugs are found, then the official 2.16.0 release will be
on 20 April 2012. If you discover any problems, please send us
Segnalazione bug.
The LilyPond Report #25. Apr 1st, 2012
The LilyPond Report is back, with a rather unusual
issue featuring our young Polish contributor Janek Warchoł!
Also included in this issue are quite a few unexpected items,
including (but not limited to)… a cooking recipe!
Come
read LilyPond Report 25 now; comments and contributions are
warmly encouraged!
LilyPond 2.15.35 released! Mar 28, 2012
We are happy to announce the release of LilyPond 2.15.35. This
release contains the usual number of bugfixes.
It is strongly recommended that normal users do not use
this release, and instead use the stable 2.14 version. Please
note that due to a few Critical bugs, this is not the next release
candidate.
LilyPond 2.15.34 released! Mar 19, 2012
We are happy to announce the release of LilyPond 2.15.34. This
release contains the usual number of bugfixes.
It is strongly recommended that normal users do not use
this release, and instead use the stable 2.14 version. Please
note that due to a few Critical bugs, this is not the next release
candidate.
LilyPond 2.15.33 released! Mar 08, 2012
We are happy to announce the release of LilyPond 2.15.33. This
release contains the usual number of bugfixes.
It is strongly recommended that normal users do not use
this release, and instead use the stable 2.14 version. Please
note that due to a few Critical bugs, this is not the next release
candidate.
The LilyPond Report #24. Mar 5, 2012
A new issue of the LilyPond Report is now
available for reading; topics include a request for funding,
an article about exciting new features in LilyPond grammar,
and an overview of LilyPond-based web applications.
Come
read LilyPond Report 24 now; comments and contributions are
warmly encouraged!
LilyPond 2.15.32 released! Mar 03, 2012
We are happy to announce the release of LilyPond 2.15.32. This
release contains the usual number of bugfixes.
It is strongly recommended that normal users do not use
this release, and instead use the stable 2.14 version. Please
note that due to a few Critical bugs, this is not the next release
candidate.
LilyPond 2.15.31 released! Feb 29, 2012
We are happy to announce the release of LilyPond 2.15.31. This
release contains the usual number of bugfixes.
It is strongly recommended that normal users do not use
this release, and instead use the stable 2.14 version. Please
note that due to a few Critical bugs, this is not the next release
candidate.
Release candidate 3 of 2.16 - LilyPond 2.15.30 released! Feb 17, 2012
LilyPond 2.15.30 is out; this is the third release candidate of
the upcoming 2.16 stable release. All users are invited to
experiment with this version. New features since 2.14.2 are
listed in the “Changes” manual on the website section about
Sviluppo.
There are no known Critical issues with this release. If no
Critical bugs are found, then the official 2.16.0 release will be
on 02 March 2012. If you discover any problems, please send us
Segnalazione bug.
LilyPond 2.15.29 released! Feb 9, 2012
We are happy to announce the release of LilyPond 2.15.29. This
release contains the usual number of bugfixes.
It is strongly recommended that normal users do not use
this release, and instead use the stable 2.14 version. Please
note that due to a few Critical bugs, this is not the next release
candidate.
LilyPond 2.15.28 released! Feb 3, 2012
We are happy to announce the release of LilyPond 2.15.28. This
release contains the usual number of bugfixes.
It is strongly recommended that normal users do not use
this release, and instead use the stable 2.14 version. Please
note that due to a few Critical bugs, this is not the next release
candidate.
LilyPond 2.15.27 released! Jan 24, 2012
We are happy to announce the release of LilyPond 2.15.27. This
release contains the usual number of bugfixes.
It is strongly recommended that normal users do not use
this release, and instead use the stable 2.14 version. Please
note that due to a few Critical bugs, this is not the next release
candidate.
The LilyPond Report #23. Jan 20, 2012
The LilyPond Report is back, with developer
David Kastrup as a new editor! This issue features
an exposé on some of the new, handy commands
recently added to LilyPond, as well as an interview
with LilyPond contributor and composer Mike Solomon.
Come
read LilyPond Report 23 now; comments and contributions are
warmly encouraged!
LilyPond 2.15.26 released! Jan 16, 2012
We are happy to announce the release of LilyPond 2.15.26. This
release contains the usual number of bugfixes.
It is strongly recommended that normal users do not use
this release, and instead use the stable 2.14 version. Please
note that due to a few Critical bugs, this is not the next release
candidate.
The 2.15.25 has been skipped due to build problems.
LilyPond 2.15.24 released! Jan 07, 2012
We are happy to announce the release of LilyPond 2.15.24. This
release contains the usual number of bugfixes.
It is strongly recommended that normal users do not use
this release, and instead use the stable 2.14 version. Please
note that due to a few Critical bugs, this is not the next release
candidate.
LilyPond 2.15.23 released! Dec 21, 2011
We are happy to announce the release of LilyPond 2.15.23. This
release contains the usual number of bugfixes.
It is strongly recommended that normal users do not use
this release, and instead use the stable 2.14 version. Please
note that due to a few Critical bugs, this is not the next release
candidate.
LilyPond 2.15.22 released! Dec 15, 2011
We are happy to announce the release of LilyPond 2.15.22. This
release contains the usual number of bugfixes.
It is strongly recommended that normal users do not use
this release, and instead use the stable 2.14 version. Please
note that due to a few Critical bugs, this is not the next release
candidate.
LilyPond 2.15.21 released! Dec 6, 2011
We are happy to announce the release of LilyPond 2.15.21. This
release contains the usual number of bugfixes.
It is strongly recommended that normal users do not use
this release, and instead use the stable 2.14 version. Please
note that due to a few Critical bugs, this is not the next release
candidate.
LilyPond 2.15.20 released! Nov 24, 2011
We are happy to announce the release of LilyPond 2.15.20. This
release contains the usual number of bugfixes.
It is strongly recommended that normal users do not use
this release, and instead use the stable 2.14 version. Please
note that due to a few Critical bugs, this is not the next release
candidate.
LilyPond 2.15.19 released! Nov 18, 2011
We are happy to announce the release of LilyPond 2.15.19. This
release contains the usual number of bugfixes.
It is strongly recommended that normal users do not use
this release, and instead use the stable 2.14 version. Please
note that due to a few Critical bugs, this is not the next release
candidate.
LilyPond 2.15.18 released! Nov 12, 2011
We are happy to announce the release of LilyPond 2.15.18. This
release contains the usual number of bugfixes.
It is strongly recommended that normal users do not use
this release, and instead use the stable 2.14 version. Please
note that due to a few Critical bugs, this is not the next release
candidate.
LilyPond 2.15.17 released! Nov 10, 2011
We are happy to announce the release of LilyPond 2.15.17. This
release contains the usual number of bugfixes.
It is strongly recommended that normal users do not use
this release, and instead use the stable 2.14 version. Please
note that due to a few Critical bugs, this is not the next release
candidate.
LilyPond 2.15.16 released! October 28, 2011
We are happy to announce the release of LilyPond 2.15.16. This
release contains the usual number of bugfixes.
It is strongly recommended that normal users do not use
this release, and instead use the stable 2.14 version. Please
note that due to a few Critical bugs, this is not the next release
candidate.
LilyPond 2.15.15 released! October 24, 2011
We are happy to announce the release of LilyPond 2.15.15. This
release contains the usual number of bugfixes.
It is strongly recommended that normal users do not use
this release, and instead use the stable 2.14 version. Please
note that due to a few Critical bugs, this is not the next release
candidate.
LilyPond 2.15.14 released! October 7, 2011
We are happy to announce the release of LilyPond 2.15.14. This
release contains the usual number of bugfixes.
It is strongly recommended that normal users do not use
this release, and instead use the stable 2.14 version. Please
note that due to a few Critical bugs, this is not the next release
candidate.
LilyPond 2.15.13 released! September 27, 2011
We are happy to announce the release of LilyPond 2.15.13. This
release contains the usual number of bugfixes.
It is strongly recommended that normal users do not use
this release, and instead use the stable 2.14 version. Please
note that due to a few Critical bugs, this is not the next release
candidate.
Release candidate 2 cancelled Sep 23, 2011
The release countdown is cancelled due to the discovery of a
Critical regression.
Release candidate 2 of 2.16 - LilyPond 2.15.12 released! Sep 20, 2011
LilyPond 2.15.12 is out; this is the second release candidate of
the upcoming 2.16 stable release. All users are invited to
experiment with this version. New features since 2.14.2 are
listed in the “Changes” manual on the website section about
Sviluppo.
There are no known Critical issues with this release. If no
Critical bugs are found, then the official 2.16.0 release will be
on 27 Sep 2011. If you discover any problems, please send us
Segnalazione bug.
LilyPond 2.15.11 released! September 11, 2011
We are happy to announce the release of LilyPond 2.15.11. This
release contains the usual number of bugfixes.
It is strongly recommended that normal users do not use
this release, and instead use the stable 2.14 version. Please
note that due to the possibility of a few Critical bugs, this is
not the next release candidate.
LilyPond 2.15.10 released! September 6, 2011
We are happy to announce the release of LilyPond 2.15.10. This
release contains the usual number of bugfixes.
It is strongly recommended that normal users do not use
this release, and instead use the stable 2.14 version. Please
note that due to a few outstanding Critical bugs, this is not the
next release candidate.
LilyPond 2.15.9 released! August 30, 2011
We are happy to announce the release of LilyPond 2.15.9. This
release contains the usual number of bugfixes, and also adds
support for MacOS X 10.7.
It is strongly recommended that normal users do not use
this release, and instead use the stable 2.14 version. Please
note that due to a few outstanding Critical bugs, this is not the
next release candidate.
Release candidate 1 of 2.16 - LilyPond 2.15.8 released! Aug 01, 2011
LilyPond 2.15.8 is out; this is the first release candidate of
the upcoming 2.16 stable release. All users are invited to
experiment with this version. New features since 2.14.2 are
listed in the “Changes” manual on the website section about
Sviluppo.
There are no known Critical issues with this release. If no
Critical bugs are found, then the official 2.16.0 release will be
on 08 Aug 2011. If you discover any problems, please send us
Segnalazione bug.
LilyPond 2.15.7 released! July 29, 2011
We are happy to announce the release of LilyPond 2.15.7. This
release contains the usual number of bugfixes.
It is strongly recommended that normal users do not use
this release, and instead use the stable 2.14 version.
LilyPond 2.15.6 released! July 26, 2011
We are happy to announce the release of LilyPond 2.15.6. This
release contains the usual number of bugfixes.
It is strongly recommended that normal users do not use
this release, and instead use the stable 2.14 version.
LilyPond 2.14.2 released! July 25, 2011
We are happy to announce the release of LilyPond 2.14.2. This
fixes a few minor bugs in the stable version, and should cause no
problems. We recommend that everybody upgrade to this version.
LilyPond 2.15.5 released! July 12, 2011
We are happy to announce the release of LilyPond 2.15.5. This
release contains the usual number of bugfixes.
It is strongly recommended that normal users do not use
this release, and instead use the stable 2.14 version.
LilyPond 2.15.4 released! July 4, 2011
We are happy to announce the release of LilyPond 2.15.4. This
release contains the usual number of bugfixes.
It is strongly recommended that normal users do not use
this release, and instead use the stable 2.14 version.
LilyPond 2.15.3 released! June 27, 2011
We are happy to announce the release of LilyPond 2.15.3. This
release contains the usual number of bugfixes.
It is strongly recommended that normal users do not use
this release, and instead use the stable 2.14 version.
LilyPond 2.15.2 released! June 18, 2011
We are happy to announce the release of LilyPond 2.15.2. This
release contains the usual number of bugfixes.
It is strongly recommended that normal users do not use
this release, and instead use the stable 2.14 version.
LilyPond 2.14.1 released! June 12, 2011
We are happy to announce the release of LilyPond 2.14.1. This
fixes a few minor bugs in the stable version, and should cause no
problems. We recommend that everybody upgrade to this version.
LilyPond 2.15.1 released! June 11, 2011
We are happy to announce the release of LilyPond 2.15.1. This is
the beginning of a new unstable development effort, and adds the
usual number of bugs.
It is strongly recommended that normal users do not use
this release, and instead use the stable 2.14 version.
LilyPond 2.15.0 released! June 7, 2011
We are happy to announce the release of LilyPond 2.15.0. This is
the beginning of a new unstable development effort, and adds the
usual number of bugs.
It is strongly recommended that normal users do not use
this release, and instead use the stable 2.14 version.
LilyPond 2.14.0 released! June 6, 2011
We are proud to announce the release of GNU LilyPond 2.14.
LilyPond is a music engraving program, devoted to producing the
highest-quality sheet music possible. It brings the aesthetics of
traditionally engraved music to computer printouts.
Many improvements have been made in the past two and a half years
since the previous main stable version. A few major improvements
are:
-
LilyPond is now licensed under the GNU GPL v3 or higher.
-
The vertical spacing engine has been drastically changed, making
it much more flexible and easier to control.
-
Automatic beaming is now more flexible, and beam collisions are
avoided.
A full list of new features is given in:
http://lilypond.org/doc/v2.14/Documentation/changes/index.html
Happy music typesetting! LilyPond 2.14 was brought to you by...
Main development team:
Trevor Daniels, Reinhold Kainhofer, David Kastrup, Jonathan Kulp,
Werner Lemberg, John Mandereau, Patrick McCarty, Joe Neeman,
Han-Wen Nienhuys, Jan Nieuwenhuizen, Graham Percival, Mark
Polesky, Neil Puttock, Mike Solomon, Carl Sorensen, Francisco
Vila, Valentin Villenave.
Programming contributors:
Sven Axelsson, Pál Benkő, Bertrand Bordage, Frédéric Bron, Peter Chubb, Hajo Dezelski, Richard
Gay, Keith OHara, Andrew Hawryluk, Christian Hitz, Marc Hohl,
Henning Hraban Ramm, Ian Hulin, Michael Käppler, Marek Klein,
Kieren MacMillan, Thomas Morgan, Benjamin Peterson, Nathan Reed,
Julien Rioux, Boris Shingarov, Patrick Schmidt, Owen Tuz, Jan Warchoł, Andrew
Wilson, Rodolfo Zitellini.
Font contributors:
Keith OHara, Marc Hohl, Alexander Kobel, Carsten Steger.
Documentation contributors:
Colin Campbell, Andrew Hawryluk, James Lowe, Mike Moral, Ralph
Palmer, David Pounder, Patrick Schmidt.
Bug squad:
James E. Bailey, Colin Campbell, Phil Holmes, Urs Liska, Ralph
Palmer, Kieren MacMillan, Dmytro O. Redchuk.
Binaries support contributors:
Christian Hitz.
Translation contributors:
Federico Bruni, Dénes Harmath, Jean-Charles Malahieude, Tineke de
Munnik, Till Paala, Ralf Wildenhues, Yoshiki Sawada.
Release candidate 7 of 2.14 - LilyPond 2.13.63 released! May 30, 2011
LilyPond 2.13.63 is out; this is the seventh release candidate of
the upcoming 2.14 stable release. All users are invited to
experiment with this version. New features since 2.12.3 are
listed in the “Changes” manual on the website section about
Sviluppo.
There are no known Critical issues with this release. If no
Critical bugs are found, then the official 2.14.0 release will be
on June 6, 2011. If you discover any problems, please send us
Segnalazione bug.
LilyPond 2.13.62 released! May 24, 2011
We are happy to announce the release of LilyPond 2.13.62. This
release contains the usual number of bugfixes.
Please note that this is not the next release candidate,
due to a few remaining Critical bugs.
LilyPond 2.13.61 released! May 1, 2011
We are happy to announce the release of LilyPond 2.13.61. This
release contains the usual number of bugfixes.
Please note that this is not the next release candidate,
due to a few remaining Critical bugs.
LilyPond 2.13.60 released! April 16, 2011
We are happy to announce the release of LilyPond 2.13.60. This
release contains the usual number of bugfixes.
Please note that this is not the next release candidate,
due to a few remaining Critical bugs.
Linux Journal Magazine article - April 2011
Linux Magazine publishes an
article in the May 2011 issue titled
Projects on the Move. It is an introduction to MuseScore,
LilyPond and Chordii. Author Carla Schroder states “LilyPond is
driven from the command line, but don’t let the lack of a GUI scare
you away; LilyPond is user-friendly and easy to learn”, and provides
a hands-on example.
LilyPond 2.13.59 released! April 10, 2011
We are happy to announce the release of LilyPond 2.13.59. This
release contains the usual number of bugfixes.
Please note that this is not the next release candidate,
due to a few remaining Critical bugs.
Release candidate 6 of 2.14 - LilyPond 2.13.58 released! April 7, 2011
LilyPond 2.13.58 is out; this is the sixth release candidate of
the upcoming 2.14 stable release. All users are invited to
experiment with this version. New features since 2.12.3 are
listed in the “Changes” manual on the website section about
Sviluppo.
There are no known Critical issues with this release. If no
Critical bugs are found, then the official 2.14.0 release will be
on April 14, 2011. If you discover any problems, please send us
Segnalazione bug.
Release candidate 5 of 2.14 - LilyPond 2.13.57 released! April 3, 2011
LilyPond 2.13.57 is out; this is the fifth release candidate of
the upcoming 2.14 stable release. All users are invited to
experiment with this version. New features since 2.12.3 are
listed in the “Changes” manual on the website section about
Sviluppo.
There are no known Critical issues with this release. If no
Critical bugs are found, then the official 2.14.0 release will be
on April 10, 2011. If you discover any problems, please send us
Segnalazione bug.
Release candidate 4 of 2.14 - LilyPond 2.13.56 released! Mar 29, 2011
LilyPond 2.13.56 is out; this is the fourth release candidate of
the upcoming 2.14 stable release. All users are invited to
experiment with this version. New features since 2.12.3 are
listed in the “Changes” manual on the website section about
Sviluppo.
There are no known Critical issues with this release. If no
Critical bugs are found, then the official 2.14.0 release will be
on April 5, 2011. If you discover any problems, please send us
Segnalazione bug.
LilyPond 2.13.55 released! Mar 22, 2011
We are happy to announce the release of LilyPond 2.13.55. This
release contains the usual number of bugfixes.
Please note that this is not the fourth release candidate,
due to a few remaining Critical bugs.
Release candidate 3 withdrawn Mar 15, 2011
We have discovered a regression since 2.12.3, so lilypond 2.13.54
is no longer a candidate for the 2.14.0 release. However, please
continue testing it – we would like to discover (and fix!) any
more regressions as soon as possible. If you discover any
problems, please send us Segnalazione bug.
Release candidate 3 of 2.14 - LilyPond 2.13.54 released! Mar 13, 2011
LilyPond 2.13.54 is out; this is the third release candidate of
the upcoming 2.14 stable release. All users are invited to
experiment with this version. New features since 2.12.3 are
listed in the “Changes” manual on the website section about
Sviluppo.
There are no known Critical issues with this release. If no
Critical bugs are found, then the official 2.14.0 release will be
on March 27, 2011. If you discover any problems, please send us
Segnalazione bug.
LilyPond 2.13.53 released! Mar 6, 2011
We are happy to announce the release of LilyPond 2.13.53. This
release contains the usual number of bugfixes.
Please note that this is not the third release candidate,
due to a few remaining Critical bugs.
LilyPond 2.13.52 released! Mar 1, 2011
We are happy to announce the release of LilyPond 2.13.52. This
release contains the usual number of bugfixes.
Please note that this is not the third release candidate,
due to a few remaining Critical bugs.
LilyPond 2.13.51 released! Feb 22, 2011
We are happy to announce the release of LilyPond 2.13.51. This
release contains the usual number of bugfixes.
Please note that this is not the third release candidate,
due to a few remaining Critical bugs.
LilyPond 2.13.50 released! Feb 13, 2011
We are happy to announce the release of LilyPond 2.13.50. This
release contains the usual number of bugfixes.
Please note that this is not the third release candidate.
Due to a number of untested changes to our build process, we
cannot be at all confident about the quality of this release.
New Chinese and Czech translations of the web page! Feb 11,2011
Two new languages are added to our web page: Chinese by Ben Luo, and
Czech by Pavel Fric. It is a work in progress but they are fully
functional. That makes ten languages to choose from!
Release candidate 2 of 2.14 - LilyPond 2.13.49 released! Feb 9, 2011
LilyPond 2.13.49 is out; this is the second release candidate of
the upcoming 2.14 stable release. All users are invited to
experiment with this version. New features since 2.12.3 are
listed in the “Changes” manual on the website section about
Sviluppo.
There are no known Critical issues with this release. If no
Critical bugs are found, then the official 2.14.0 release will be
on Feb 23, 2011. If you discover any problems, please send us
Segnalazione bug.
LilyPond 2.13.48 released! Feb 5, 2011
We are happy to announce the release of LilyPond 2.13.48. This
release contains the usual number of bugfixes. However, a number
of critical issues still remain, so this release is intended for
developers only.
LilyPond 2.13.47 released! Jan 28, 2011
We are happy to announce the release of LilyPond 2.13.47. This
release contains the usual number of bugfixes. However, a number
of critical issues still remain, so this release is intended for
developers only.
Release candidate 1 withdrawn Jan 13, 2011
We have discovered a regression since 2.12.3, so lilypond 2.13.46
is no longer a candidate for the 2.14.0 release. However, please
continue testing it – we would like to discover (and fix!) any
more regressions as soon as possible. If you discover any
problems, please send us Segnalazione bug.
Release candidate 1 of 2.14 - LilyPond 2.13.46 released! Jan 12, 2011
LilyPond 2.13.46 is out; this is the first release candidate of
the upcoming 2.14 stable release. All users are invited to
experiment with this version. New features since 2.12.3 are
listed in the “Changes” manual on the website section about
Sviluppo.
There are no known Critical issues with this release. If no
Critical bugs are found, then the official 2.14.0 release will be
on 26 Jan 2011. If you discover any problems, please send us
Segnalazione bug.
LilyPond 2.13.45 released! Jan 3, 2011
We are happy to announce the release of LilyPond 2.13.45. This
release contains the usual number of bugfixes. However, a number
of critical issues still remain, so this release is intended for
developers only.
Beta test three of 2.14 – LilyPond 2.13.44 released! Dec 25, 2010
LilyPond 2.13.44 is out; this is the third beta test of the
upcoming 2.14 stable release. Users are invited to experiment
with this version. New features since 2.12.3 are listed in the
“Changes” manual on the website section about
Sviluppo.
There is still one Critical problem with this release: in one
case, the vertical spacing is much too compressed. If you decide
to test this version, do not be surprised to discover problems;
just send us polite Segnalazione bug.
Beta test two of 2.14 – LilyPond 2.13.43 released! Dec 14, 2010
LilyPond 2.13.43 is out; this is the second beta test of the
upcoming 2.14 stable release. Users are invited to experiment
with this version. New features since 2.12.3 are listed in the
“Changes” manual on the website section about
Sviluppo.
There is still one Critical problem with this release: in one
case, the vertical spacing is much too compressed. If you decide
to test this version, do not be surprised to discover problems;
just send us polite Segnalazione bug.
LilyPond 2.13.42 released! Dec 8, 2010
We are happy to announce the release of LilyPond 2.13.42. This
release contains the usual number of bugfixes. However, a number
of critical issues still remain, so this release is intended for
developers only.
Please note that this is not the second beta test. Due
to a number of untested changes to our build process, we cannot be
at all confident about the quality of this release.
LilyPond 2.13.41 released! Dec 4, 2010
We are happy to announce the release of LilyPond 2.13.41. This
release contains the usual number of bugfixes. However, a number
of critical issues still remain, so this release is intended for
developers only.
Please note that this is not the second beta test. Due
to a number of untested changes to our build process, we cannot be
at all confident about the quality of this release.
LilyPond 2.13.40 released! Nov 21, 2010
We are happy to announce the release of LilyPond 2.13.40. This
release contains the usual number of bugfixes. However, a number
of critical issues still remain, so this release is intended for
developers only.
Please note that this is not the second beta test. Due
to a number of untested changes to our build process, we cannot be
at all confident about the quality of this release.
Beta test one of 2.14 – LilyPond 2.13.39 released! Nov 15, 2010
LilyPond 2.13.39 is out; this is the first beta test of the
upcoming 2.14 stable release. Users are invited to experiment
with this version. New features since 2.12.3 are listed in the
“Changes” manual on the website section about
Sviluppo.
There are still some Critical problems with this release: the
vertical spacing is suspicious in two cases, and lilypond can
crash with some odd input. If you decide to test 2.13.39, do not
be surprised to discover problems; just send us polite
Segnalazione bug.
The LilyPond Report #22. Nov 3, 2010
The LilyPond Report is back, with some surprises and exciting
news for the whole LilyPond community! To be found in this issue is
an up-to-date, complete list of all LilyPond mailing lists and forums
around the world. Also, for the very first time our special guest
today is LilyPond’s co-founder and core developer
Jan Nieuwenhuizen, who has been busy these past months –
read on to find out what for!
Come
read LilyPond Report 22 now; comments and contributions are
warmly encouraged!
Alpha test four of 2.14 – LilyPond 2.13.38 released! Oct 31, 2010
LilyPond 2.13.38 is out; this is the fourth alpha test of the
upcoming 2.14 stable release. Users are invited to experiment
with this version. New features since 2.12.3 are listed in the
“Changes” manual on the website section about
Sviluppo.
There are still some Critical problems with this release: the
vertical spacing is suspicious in two cases, and lilypond can
crash with some odd input. If you decide to test 2.13.38, do not
be surprised to discover problems; just send us polite
Segnalazione bug.
Alpha test three of 2.14 – LilyPond 2.13.37 released! Oct 25, 2010
LilyPond 2.13.37 is out; this is the third alpha test of the
upcoming 2.14 stable release. Users are invited to experiment
with this version. New features since 2.12.3 are listed in the
“Changes” manual on the website section about
Sviluppo.
There are still some Critical problems with this release: the
vertical spacing is suspicious in two cases, and lilypond can
crash with some odd input. If you decide to test 2.13.37, do not
be surprised to discover problems; just send us polite
Segnalazione bug.
LilyPond 2.13.36 released! Oct 19, 2010
We are happy to announce the release of LilyPond 2.13.36. This
release contains the usual number of bugfixes. However, a number
of critical issues still remain, so this release is intended for
developers only.
Please note that this is not the third alpha test. Due
to a number of untested changes to our build process, we cannot be
at all confident about the quality of this release.
The LilyPond Report #21. Oct 3, 2010
The LilyPond Report is back, with its two
“grumpy-and-fluffy” editors! This issue mainly deals with
microtonal notation in LilyPond, but does also include a how-to
about running LilyPond from an USB key, not to forget the regular
release news, the bug report of the Report, and some news from
the frog pond!
Come
read LilyPond Report 21 now; comments and contributions are
warmly encouraged!
LilyPond 2.13.33 released! Sep 10, 2010
We are happy to announce the release of LilyPond 2.13.33. This
release contains the usual number of bugfixes. However, a number
of critical issues still remain, so this release is intended for
developers only.
LilyPond 2.13.32 released! Sep 3, 2010
We are happy to announce the release of LilyPond 2.13.32. This
release contains the usual number of bugfixes. However, a number
of critical issues still remain, so this release is intended for
developers only.
LilyPond Report #20. Sep 2, 2010
The LilyPond Report is back, with its two
“grumpy-and-fluffy” editors! This issue contains a review of an
online notation editor using lilypond, along with the regular
release news, snippet of the report, news from the frog pond, and
the bug report of the report!
Come
read LilyPond Report 20 now; comments and contributions are
warmly encouraged!
LilyPond 2.13.31 released! Aug 24, 2010
We are happy to announce the release of LilyPond 2.13.31. This
release contains the usual number of bugfixes. However, a number
of critical issues still remain, so this release is intended for
developers only.
LilyPond 2.13.30 released! Aug 13, 2010
We are happy to announce the release of LilyPond 2.13.30. This
release contains the usual number of bugfixes. However, a number
of critical issues still remain, so this release is intended for
developers only.
LilyPond Report #19. Aug 9, 2010
The LilyPond Report is back, with its two
“grumpy-and-fluffy” editors! This issue contains some
conference news, along with the regular release news, snippet of
the report, news from the frog pond, and the bug report of the
report!
Come
read LilyPond Report 19 now; comments and contributions are
warmly encouraged!
LilyPond 2.13.29 released! Aug 4, 2010
We are happy to announce the release of LilyPond 2.13.29. This
release contains the usual number of bugfixes. However, a number
of critical issues still remain, so this release is intended for
developers only.
This release radically changes the autobeaming rules, so use extra
caution and expect breakage.
LilyPond 2.13.28 released! July 13, 2010
We are happy to announce the release of LilyPond 2.13.28. This
release contains the usual number of bugfixes. However, a number
of critical issues still remain, so this release is intended for
developers only.
This release includes some major untested changes to the windows
lilypad editor. Windows users should not be using this release
because it is intended for developers only, but you ignore these
warnings and try it anyway, use extra caution.
LilyPond 2.13.27 released! July 5, 2010
We are happy to announce the release of LilyPond 2.13.27. This
release contains the usual number of bugfixes. However, a number
of critical issues still remain, so this release is intended for
developers only.
Testing our new website! June 29, 2010
We’re testing our new website! For the next 24 hours, the new
website will be the default website; after that, we will switch
back to the old website while we examine feedback and make
improvements to the new website.
Please send feedback to lilypond-user; you can find more
information on our page about Contatti.
Nota: There are a few known problems with translations. If you
are a non-English speaker, you may prefer to view the old lilypond
website at:
http://lilypond.org/web/
LilyPond 2.13.26 released! June 26, 2010
We are happy to announce the release of LilyPond 2.13.26. This
release contains the usual number of bugfixes. However, a number
of critical issues still remain, so this release is intended for
developers only.
LilyPond 2.13.25 released! June 20, 2010
We are happy to announce the release of LilyPond 2.13.25. This
release contains the usual number of bugfixes. However, a number
of critical issues still remain, so this release is intended for
developers only.
LilyPond 2.13.24 released! June 14, 2010
We are happy to announce the release of LilyPond 2.13.24. This
release contains the usual number of bugfixes. However, a number
of critical issues still remain, so this release is intended for
developers only.
LilyPond 2.13.23 released! June 3, 2010
We are happy to announce the release of LilyPond 2.13.23. This
release contains the usual number of bugfixes. However, a number
of critical issues still remain, so this release is intended for
developers only.
LilyPond 2.13.22 released! May 27, 2010
We are happy to announce the release of LilyPond 2.13.22. This
release contains the usual number of bugfixes. However, a number
of critical issues still remain, so this release is intended for
developers only.
LilyPond 2.13.21 released! May 12, 2010
We are happy to announce the release of LilyPond 2.13.21. This
release contains the usual number of bugfixes. However, a number
of critical issues still remain, so this release is intended for
developers only.
This release should be of particular interest to package
maintainers: we have made a few changes to the configure script
and the required libraries. Barring any urgent bug reports, this
is the build system and libraries that will be used for the next
stable release.
LilyPond Report #18. May 11, 2010
The LilyPond Report is back, with its two
“grumpy-and-fluffy” editors! This issue will be filled
with emotion and coolness, paper bags and zigzag-ending
staves, plus the usual Frogs and Bugs.
Come
read LilyPond Report 18 now; comments and contributions are
warmly encouraged!
LilyPond 2.13.20 released! May 5, 2010
We are happy to announce the release of LilyPond 2.13.20. This
release contains the usual number of bugfixes. However, a number
of critical issues still remain, so this release is intended for
developers only.
Minor syntax change: the undocumented \cresc and
\decresc have changed. In addition, the [options] for the
LaTeX mode of lilypond-book now comes after the
{lilypond}, following normal LaTeX practice. As always,
see the Changes document for more information.
LilyPond 2.13.19 released! April 24, 2010
We are happy to announce the release of LilyPond 2.13.19. This
release contains the usual number of bugfixes. However, 11
critical issues still remain, so this release is intended for
developers only.
LilyPond 2.13.18 released! April 16, 2010
We are happy to announce the release of LilyPond 2.13.18. This
release contains the usual number of bugfixes, along with improved
website translations. However, 14 critical issues still remain,
so this release is intended for developers only.
LilyPond 2.13.17 released! April 2, 2010
We are happy to announce the release of LilyPond 2.13.17. This
release includes bugfixes for 4 critical issues. However, 15
critical issues still remain, so this release is intended for
developers only.
LilyPond 2.13.16 released! March 15, 2010
We are happy to announce the release of LilyPond 2.13.16. This
release is intended for developers only, and includes the usual
round of bugfixes.
LilyPond 2.13.15 released! March 4, 2010
We are happy to announce the release of LilyPond 2.13.15. This
release is intended for developers only, and includes a few
updates to the binary build process in addition to the usual round
of bugfixes.
LilyPond Report #17. March 1, 2010
Yay, the Report is back, with a new team! It has been said that
two heads are better than one — does it apply to newsletters as
well? Read on and let us know! In this issue we’ll talk about
websites and poetry, frogs and bugs, not to mention an extensive
review of the Frescobaldi editor!
What are you waiting for? Come
read LilyPond Report 17 now!
LilyPond 2.13.14 released! February 27, 2010
We are happy to announce the release of LilyPond 2.13.14. This
release is intended for developers only, and includes a large
translation update in addition to the usual round of bugfixes.
LilyPond 2.13.13 released! February 13, 2010
We are happy to announce the release of LilyPond 2.13.13. This
release is intended for developers only, and fixes various
problems with documentation build system as well as adding an
output-preview-framework for our SVG backend. In addition, the
binaries are now approximately 6 megabytes smaller.
LilyPond 2.13.12 released! February 2, 2010
We are happy to announce the release of LilyPond 2.13.12. This
release is intended for developers only, and brings more stability
and fewer bugs to the build system and Contributor’s Guide.
LilyPond 2.13.11 released! January 16, 2010
We are happy to announce the release of LilyPond 2.13.11. This
release is intended for developers only, and brings a number of
improvements to the build system, Contributor’s Guide, and fixes 4
critical regressions against earlier versions.
LilyPond 2.13.10 released! December 31, 2009
We are happy to announce the release of LilyPond 2.13.10. This
release is intended for developers only, and brings a number of
improvements such as predictable regression test output filenames
and English names for feta filenames.
LilyPond 2.12.3 released! December 20, 2009
We are happy to announce the release of LilyPond 2.12.3. This
version contains the long-awaited fix for our GUI on MacOS X 10.5
and 10.6. In addition to the GUI fixes, this version contains
dozens of bugfixes backported from the unstable development
version.
We recommend that all users upgrade to this version. This is the
last planned release in the 2.12 stable series; development now
shifts towards the upcoming 2.14 series.
LilyPond 2.13.9 released! December 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 unstable development branch;
normal users should continue to use 2.12.
New Website! October 3, 2009
As you can see, we have a new website design. Many thanks to
texi2html and CSS for being so flexible!
LilyPond Report #16. September 6, 2009
The LilyPond Report is back! This short, informal opinion column is
about the LilyPond project: its team, its world, its community.
Read issue 16
now!
LilyPond 2.13.3. July 2, 2009
This unstable release contains working menus in OSX 10.5; many
thanks to Christian Hitz for fixing this long-standing problem!
This release also contains numerous other bugfixes and features
such as ties with variable thickness, partially dashed slurs, and
eyeglasses.
We are planning another 2.12 release in the next week or two,
which will include the menu fixes for OSX 10.5. Normal users may
wish to wait for this release rather than using an unstable
release.
Cambiamenti,
Sviluppo.
A LilyPond weboldala magyarul. May 22, 2009
Elkészült a lilypond.org nagy részének magyar fordítása a LilyPond
honosítási projekt első lépéseként. A projekt célja a LilyPond
szabad kottaszedő szoftver minél széleskörűbben elérhetővé tétele
a magyar felhasználók számára a teljes weboldal és dokumentáció
lefordítása révén. A teljes dokumentáció lefordításához
közreműködőket keresünk. Ha részt vennél a honosításban, küldj egy
e-mailt a harmathdenes AT gmail.com címre!
Harmath Dénes, a LilyPond honosítási projekt
vezetője
The LilyPond Report #15. May 18, 2009
The LilyPond Report is a short, informal opinion column about the LilyPond project:
its team, its world, its community.
Follow this link
to read the full issue...
The LilyPond Report #14. April 13, 2009
The LilyPond Report is back, on a new website!
This short, informal, weekly opinion column is about the LilyPond project: its team, its world, its community.
Follow this link to read the full issue...
LilyPond 2.12.2 and 2.13.0 — March 21, 2009
As a very belated announcement, the stable version of LilyPond is
now 2.12.2, and the next development version has begun with
2.13.0.
LilyPond 2.11.65 — Release Candidate. December 2, 2008
This release has improvements to MusicXML import, contributed by
Reinhold Kainhofer, and adds support for splitting a book in several
book parts, contributed by Nicolas Sceaux.
Nested contexts of the same type are now allowed with any depth, and
overriding nested properties can be done with list syntax, thanks to
Neil Puttock.
This is hopefully the last Release Candidate before stable release 2.12,
so you are welcome to test this release if you can to report new
issues.
Bugfixes,
Cambiamenti,
Vecchi download.
LilyPond 2.11.64. November 18, 2008
LilyPond 2.11.64 is available. MusicXML import has been improved,
including church modes support, and a few bugs in the compilation
and documentation building processes are fixed. The three
documentation manuals are now fully translated in Spanish, thanks
to Francisco Vila. The font cache problem in Windows binaries
which used to cause excessive slowness should be fixed.
Cambiamenti,
Vecchi download.
LilyPond 2.11.63. October 29, 2008
LilyPond 2.11.63 is available. This release has lots of updates to the
documentation and translations.
Vecchi download.
LilyPond 2.11.62 – Release Candidate. October 11, 2008
LilyPond 2.11.62 is available. This is is one of the last releases
before 2.12, so testing it is encouraged. In addition to a bugfix
in \tempo command, this release has lot of updates
to Spanish and German documentation translations, and the
stylesheet for HTML documentation has been improved.
Bugfixes,
Vecchi download.
LilyPond 2.11.61 available. October 1, 2008
LilyPond 2.11.61 has been released. It has updates to
documentation translations, and a new automatic accidentals style
(teaching) has been added.
Bugfixes,
Cambiamenti,
Vecchi download.
LilyPond 2.11.60 available. September 25, 2008
LilyPond 2.11.60 has been released. A new style of double repeat
bar line has been added, and printallheaders variable in
score block has been renamed to print-all-headers.
Vecchi download.
LilyPond 2.11.59 available. September 20, 2008
Release 2.11.59 is out. LilyPond now uses 64 bit integers for
rational numbers, which allows typesetting more complex polymetric
music. This release also has updates to German and Spanish
translations of the documentation.
Vecchi download.
LilyPond 2.11.58 available. September 13, 2008
LilyPond 2.11.58 is a beta release, which means the next stable
release is expected in a few weeks. This release is also special,
as it includes code which supports more flexible automatic
accidentals rules, written several months ago by Rune Zedeler,
deceased since then. All the development team express their
condolences to his family and his friends. Besides this,
automatic beaming has been improved by Carl Sorensen, support
for creating stem flags in a new style has been contributed by
Reinhold Kainhofer, and a few bugs have been fixed.
Bugfixes,
Cambiamenti,
Vecchi download.
LilyPond 2.11.57 available. August 27, 2008
LilyPond 2.11.57 is out. This release adds support for harp pedal
diagrams, contributed by Reinhold Kainhofer, and some changes in
markup command names have been made.
Cambiamenti,
Vecchi download.
LilyPond 2.11.56 available. August 17, 2008
LilyPond 2.11.56 is out. This release features transposable fret
diagrams, contributed by Carl Sorensen. Translations status pages
are now available from the documentation start page. Two
predefined commands \pointAndClickOn,
\pointAndClickOff have also been added.
Cambiamenti,
Vecchi download.
LilyPond 2.11.55 available. August 6, 2008
LilyPond 2.11.55 is out. This release fixes several bugs, and for octavation brackets
set-octavation has been replaced by a more user-friendly command, \ottava.
Bugfixes,
Vecchi download.
LilyPond 2.11.54 available. July 30, 2008
LilyPond 2.11.54 is out. This release fixes a bug in tie formatting
following a line break, and changes the behavior of short-indent
so that short instrument names are no longer indented in the margin.
Bugfixes,
Vecchi download.
LilyPond 2.11.53 available. July 23, 2008
LilyPond 2.11.53 is out. This release fixes a lot of bugs.
Bugfixes,
Vecchi download.
LilyPond 2.11.52 available. July 14, 2008
Release 2.11.52 fixes wrong offset of a bar number when it follows
a breath mark, and syntax changes made in recent development
releases are now fully listed on the News page.
Bugfixes,
Cambiamenti,
Vecchi download.
LilyPond 2.11.51 available. July 8, 2008
Release 2.11.51 has a couple of bugfixes, and a lot of changes in
predefined command names. Fret diagrams formatting has been
improved by Carl Sorensen, it is now controlled
by fret-diagram-details property.
Bugfixes,
Vecchi download.
LilyPond 2.11.50 available. July 2, 2008
Release 2.11.50 adds support for metronome marks with text, and
backslashed numbers for figured bass, contributed by
Reinhold Kainhofer.
Bugfixes,
Vecchi download.
The LilyPond Report #13. June 23, 2008
This short, informal, weekly opinion column is about the LilyPond project: its team, its world, its community.
Follow this link to read the full issue...
The LilyPond Report #12. June 16, 2008
This short, informal, weekly opinion column is about the LilyPond project: its team, its world, its community.
Follow this link to read the full issue...
LilyPond 2.11.49 released. June 12, 2008
LilyPond 2.11.49 is out. It fixes a number of bugs, including bugs in beams formatting.
Bugfixes,
Vecchi download.
LilyPond 2.11.48 released. June 9, 2008
LilyPond 2.11.48 is out. This release fixes a few bugs, and
\compressMusic has been renamed
to \scaleDurations.
Bugfixes,
Vecchi download.
The LilyPond Report #11. June 9, 2008
This short, informal, weekly opinion column is about the LilyPond project: its team, its world, its community.
Follow this link to read the full issue...
The LilyPond Report #10. June 2, 2008
Welcome to this special tenth issue of the LilyPond Report, entirely dedicated to Algorithmic Composition systems.
Follow this link to read the full issue...
LilyPond 2.11.47 released. May 28, 2008
LilyPond now allows all text context properties to be markups,
except in \lyricmode. This release also fixes
regression tests maintenance for developers.
Bugfixes,
Vecchi download.
LilyPond 2.11.46 available. May 22, 2008
Release 2.11.46 fixes a lot of bugs and includes a rewrite of
dynamics engravers. Support for slur-shaped arpeggios has been added.
Bugfixes,
Cambiamenti,
Vecchi download.
RSS feed - May 21, 2008
A RSS feed is now available on lilypond.org. It contains all
news announced on the web site start page: releases, LilyPond
report, new translations of the site and publications.
Feed URL.
The info mailing list (see Contatti) is still used to
announce releases and special events.
The LilyPond Report #9. May 05, 2008
Welcome to this ninth issue of the LilyPond Report!
This short, informal, weekly opinion column is about the LilyPond project: its team, its world, its community.
Follow this link to read the full issue...
LilyPond 2.11.45 available. April 26, 2008
Release 2.11.45 fixes a couple of bugs in the formatting
engine. lilypond-book has been improved, with better
performance, a bugfix about included files, and more flexibility
for preprocessing documents with LaTeX variants. Support for
enclosing text in a rounded box has been contributed by Valentin
Villenave.
Bugfixes,
Cambiamenti,
Vecchi download.
LilyPond 2.11.44 available. April 14, 2008
Release 2.11.44 is available. Support for figured bass and chord
names has been added to the MusicXML
converter.
Bugfixes,
Vecchi download.
lilypond.org日本語訳 (lilypond.org Japanese translation). 2008年4月8日 (April 4, 2008)
lilypond.orgのいくつかのページの日本語訳が出来ました。
LilyPond 2.11.43 available. March 31, 2008
Release 2.11.43 has been available since March 27. It fixes a
couple of formatting bugs, and the font cache problem with
MS-Windows binaries which caused excessive slowness has been
fixed.
Bugfixes,
Vecchi download.
LilyPond 2.11.42 available. March 9, 2008
Release 2.11.42 is out. It fixes some formatting and spacing
bugs.
Bugfixes,
Vecchi download.
Comparison of music engraving with Finale and LilyPond. February 25, 2008
In three articles, Andrew Hawryluk compares Finale and LilyPond in
general terms, and evaluates in detail engraving capabilities of
both pieces of software. The second article is an instructive
analysis of Rachmaninoff’s Piano Prelude 6 engraving, including
comparisons with a reference hand-engraved edition.
Read the articles.
LilyPond 2.11.41 available. February 25, 2008
Release 2.11.41 is available. It has a few bugfixes, updated
program messages in French, German, Spanish and Vietnamese, and
updates to the MusicXML converter.
Bugfixes,
Vecchi download.
LilyPond 2.11.37 available. January 3, 2008
Release 2.11.37 is available. It has a few bugfixes, and
documentation changes. (Vecchi download)
LilyPond 2.11.36 available. December 13, 2007
Release 2.11.36 is now available. It has many bugfixes, updates
for MusicXML import, and it includes major documentation changes from
Grand Documentation Project.
Bugfixes,
Vecchi download.
LilyPond 2.11.31 available. August 31, 2007
Release 2.11.31 is now available. It has more bugfixes, updates
for MusicXML import and lots of updates for the translations.
Bugfixes,
Vecchi download.
LilyPond 2.11.30 available. August 20, 2007
Release 2.11.30 is now available. It has various bugfixes among
others in the new spacing code, MusicXML import and lots of updates
for the translations.
Bugfixes,
Vecchi download.
LilyPond 2.10.29 and 2.11.29 available. August 11, 2007
Release 2.11.29 is now available. 2.10.29 has a few small fixes.
2.11.29 has several bugfixes, among others in the new spacing code,
and lots of updates for the translations.
Bugfixes 2.10,
Bugfixes 2.11,
Vecchi download.
LilyPond 2.11.28 for FreeBSD x86_64. August 10, 2007
Release 2.11.28 is now available as a binary installer for
FreeBSD x86_64. Download
the installer and
do sh lilypond-2.11.28-1.freebsd-64.sh in a command window.
LilyPond 2.11.28 available - July 25, 2007
Release 2.11.28 has several updates to the manual and its
translations, an plethora of bugfixes and a complete cleanup of the
spacing engine code.
Bugfixes,
Vecchi download.
LilyPond 2.11.26 available - June 8, 2007
Release 2.11.26 supports page markers, eg. for use in
tables-of-contents. In addition, it fixes a number of bugs. Enjoy!
Bugfixes,
Vecchi download.
LilyPond 2.10.25 and 2.11.25 available - May 20, 2007
Release 2.11.25 has support for toplevel page breaking commands,
and page breaking as a whole has been sped up significantly. Enjoy!
Bugfixes 2.10,
Bugfixes 2.11,
Vecchi download.
Übersetzung der Dokumentation - 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 Cambiamenti
online und Vecchi download.
Traduction de la documentation en français - 25 février 2007
Les chapitres 1 à 4 et 6 du manuel de l’utilisateur sont désormais traduits, et
disponibles en ligne —
version 2.10,
version 2.11.
Les traductions sont également incluses dans la
documentation téléchargeable.
LilyPond 2.11.18 available - February 12, 2007
This release fixes still more bugs, and included
singing support through festival contributed by Milan Zamazal.
Bugfixes,
Cambiamenti,
Vecchi download.
LilyPond 2.10.15 and 2.11.15 available - February 1, 2007
This release will stretch piano staves on a
system-by-system basis and add a few glyphs: a black harmonic note
head and the slashed mirrored flat.
Bugfixes 2.10,
Bugfixes 2.11,
Cambiamenti,
Vecchi download.
LilyPond 2.10.14 and 2.11.14 available - January 26, 2007
This release has a rewrite of the line-spanner code, responsible for
among other glissandi and text-crescendos, making them more flexible.
Bugfixes,
Cambiamenti,
Vecchi download
LilyPond 2.10.13 and 2.11.13 available - January 17, 2007
This release fixes a few minor but irritating bugs. In addition, the
2.11 release has updates of the tutorial.
Bugfixes,
Cambiamenti,
Vecchi download.
LilyPond 2.11.12 available - January 17, 2007
This release fixes lots of bugs. In particular, the tie formatting has
been further improved, and memory usage has been improved enormously.
Bugfixes,
Cambiamenti,
Vecchi download.
LilyPond 2.11.11 available - January 11, 2007
This release has further fixes for popular bugs. Timing of the MIDI
output won’t get confused by tuplets and grace notes anymore. Some fat
has also been trimmed of the skyline code performance.
Bugfixes,
Cambiamenti,
Vecchi download.
LilyPond 2.11.10 available - January 8, 2007
LilyPond 2.11.10 has further review of the test-suite, performance and
code coverage. This brought to light several problems that were
fixed. Notably, 2.11.10 fixes lots of regressions in optical
correction spacing and MIDI dynamics. Also, this version is 20 to 50
% faster than previous 2.11 releases.
Bugfixes,
Cambiamenti,
Vecchi download.
LilyPond 2.10.10 available - January 8, 2007
This release fixes several popular bugs, among others: MIDI files
that go silent after (de)crescendi, and tuplets problems with quoting
and part-combining.
Bugfixes,
Cambiamenti,
Vecchi download.
LilyPond 2.11.9 and 2.10.9 available - January 3, 2007
This release has a couple of bugfixes, and —in 2.11.9—
further improvements in the regression test suite
Bugfixes,
Cambiamenti,
Vecchi download.
lilypond.org auf deutsch - 31. Dezember 2006
Die LilyPond-Webseiten sind jetzt auch auf deutsch übersetzt!
lilypond.org en español - December 29, 2006
¡Ya está disponible la versión en español del sitio web de LilyPond!
LilyPond 2.11.6 available - December 30, 2006
This release supports arbitrary fractional alterations, allowing
music with different microtonal conventions to be typeset.
Bugfixes,
Cambiamenti,
Vecchi download.
LilyPond 2.11.4 available - December 21, 2006
The vertical spacing improvements that were introduced in 2.11.0 now work
within a system as well as between systems.
Bugfixes,
Cambiamenti,
Vecchi download.
LinuxPPC binaries available! - December 19, 2006
From now on, our GUB binary builds include support for Linux/PPC. (Vecchi download)
Traduction du tutoriel en français. December 13, 2006
Fruit du travail d’une équipe de traducteurs, le tutoriel en français est
maintenant disponible en ligne.
Version 2.10,
Version 2.11.
LilyPond 2.10.2 available - December 12, 2006
A new stable release of LilyPond is available.
Bugfixes,
Vecchi download.
LilyPond 2.10.1 available - December 3, 2006
A new stable release of LilyPond is available.
Bugfixes,
Vecchi download.
LilyPond 2.11.0 available - November 27, 2006
This release has improved support for vertical spacing. (Cambiamenti, Vecchi download)
GIT repository online - November 11, 2006
LilyPond development has moved over its source code to GIT, the fast version control
system. Check out our repository at gnu.org.
Music streams thesis available - October 21, 2006
The last months, Erik Sandberg has been overhauling the internals of
Lily. This change introduces a new intermediate format, Music Streams,
which will make it easier get music data out of LilyPond. A copy of
the thesis is now available from lilypond.org
(Pubblicazioni).
LilyPond 2.9.25 available - October 18, 2006
This release has more bugfixes; from now on, binaries are also
available for x86/64.
Bugfixes,
Vecchi download.
LilyPond 2.9.24 available - October 15, 2006
This release has support for right hand guitar fingerings, and offers
some bugfixes. (Cambiamenti,
Bugfixes,
Vecchi download)
LilyPond 2.9.23 available - October 12, 2006
This release cuts fragments of EPS directly from your finished score,
and makes it easier to insert ties into lyrics. (Cambiamenti, Vecchi download)
LilyPond 2.9.22 available - October 9, 2006
Test this release candidate for LilyPond 2.10! (Vecchi download)
LilyPond 2.9.21 available - October 4, 2006
Test this release candidate for LilyPond 2.10! (Vecchi download)
LilyPond 2.9.20 available - October 3, 2006
Test this release candidate for LilyPond 2.10! (Vecchi download)
LilyPond 2.9.17 available - September 2, 2006
This release fixes many bugs. Among others, MacOS X QuickTime now
honors tempo changes are in the MIDI output. (Cambiamenti, Vecchi download)
LilyPond 2.9.16 available - August 25, 2006
In this release, chords may be partially tied and lyric extenders have
tunable padding. Moreover, many bugs were fixed
(Cambiamenti, Vecchi download)
LilyPond 2.9.15 available - August 20, 2006
This releases fixes many bugs in the 2.9.14 release. (Vecchi download)
LilyPond 2.8.6 available - August 8, 2006
This release contains a few minor bugfixes; the source tarball is also
available. (Vecchi download)
LilyPond 2.9.14 available - August 4, 2006
This release supports instrument name changes, dotted barlines and
better spacing for floating grace notes. In addition, it contains
ongoing work by Erik Sandberg to extend the interpretation phase with
stream support. (Cambiamenti, Vecchi download)
LilyPond 2.9.13 available - July 23, 2006
This release supports doits and falls, and more tuning options for
grace note spacing and tuplet brackets. (Cambiamenti, Vecchi download)
LilyPond 2.9.12 available - July 18, 2006
This release supports pdftex for lilypond-book, and uses PdfTeX for
generating manuals, so page numbers and references are now clickable.
(Cambiamenti, Vecchi download)
LilyPond 2.9.11 available - July 12, 2006
This release wraps improvements of the last two weeks. As a new
feature, it supports tunable tuplet number formatting for nested
tuplets. (Cambiamenti, Vecchi download)
LilyPond 2.9.8 available - June 6, 2006
2.9.8 has support for different spacing sections within a single
score, and better infrastructure for automated regression testing.
(Cambiamenti,
Vecchi download)
LilyPond 2.8.4 available - June 4, 2006
2.8.4 fixes some minor bugs, and includes a backport of the
infrastructure for automated regression testing.
(Vecchi download)
First test results available - June 4, 2006
After a week of frantic tweaking, the first automated testing results
are available. You can now see in full glory what features are broken in the development release
LilyPond 2.9.7 available - May 30, 2006
2.9.7 has improvements in the formatting for figured bass, and
includes a new framework for detecting bugs earlier, which will make
the development releases even better
LilyPond 2.9.6 available - May 24, 2006
This
release has new features in beam formatting: beams may now be put on
single stems, and obey the beatGrouping property. MusicXML
converter. (Cambiamenti, Vecchi download)
LilyPond 2.9.5 available - May 17, 2006
This release supports object rotation, hairpins with circled tips,
hairpins that run to barlines before notes and improvements in the
MusicXML converter.
(Cambiamenti, Vecchi download)
LilyPond 2.9.4 available - May 12, 2006
This release has support for feathered beaming, and note head styles in
the markup \note command. In addition, it has a lot of updates
of the manual and a clean up of the spring spacer.
(Cambiamenti, Vecchi download)
LilyPond 2.8.2 available - May 12, 2006
This release has fixes for minor bugs and compilation issues.
(Vecchi download)
LilyPond 2.9.3 is out! - May 7, 2006
This new release has lots of updates of the manual, courtesy Graham
and the contributors of the mailing. It handles formatting for ties in
arpegiated chords better (feature sponsored by
Steve Doonan), it has al niente hairpins, courtesy of Erlend Aasland,
and some cleanups of the PostScript output, courtesy David Feuer. (Cambiamenti, Vecchi download)
FISL7.0 slides available - April 22, 2006
The slides for Han-Wen’s talk at
FISL 7 are now online.
(Pubblicazioni)
LilyPond 2.8.1 is out! - April 3, 2006
Important bugfixes include CJK font handling and a Darwin/x86 port.
(Cambiamenti, Vecchi download)
LilyPond 2.9.1 is out! - April 3, 2006
It’s mostly a bugfix release, and it’s almoste the same as 2.8.1. This
release mainly fixes problems with CJK font loading.
(Cambiamenti, Vecchi download)
LilyPond on MacOS X/Intel - March 31, 2006
LilyPond now also runs on Intel based macs, offering a 400%
speedup over the emulated PowerPC binaries. (Vecchi download)
LilyPond 2.7.39 is out - March 17, 2006
This release has even more bug fixes. Please test before 2.8 is
released. (Cambiamenti,
Vecchi download)
LilyPond 2.7.38 is out - March 12, 2006
This is likely to be the last release candidate before we release 2.8,
so report any bugs that you might find. New attractions include:
lilypond postscript files now work with GSView, cut & pasting lily
code from PDF files should now work, and spacing fixes for
multi-measure rests.
(Cambiamenti,
Vecchi download)
LilyPond 2.7.37 is out - March 4, 2006
This release has more bug fixes. Please help us by testing it!
(Cambiamenti,
Vecchi download)
LilyPond 2.7.36 is out - February 24, 2006
This is another release candidate for 2.8. It has lots of bug fixes
and polishes to the documentation. It also contains support for
creating ties that are only on their right side connected to note
heads, which is handy for repeats (feature sponsored by Steve Doonan).
The documentation suite can now be downloaded as a separate tarball
from lilypond.org. (Cambiamenti,
Vecchi download)
LilyPond 2.7.35 is out - February 19, 2006
This release has lots of bugs fixes. The plan is to release 2.8 at the
end of this month, so bug reports are very welcome. By
definition a bug is release critical if it wasn’t present in version
2.6. (Cambiamenti,
Vecchi download)
LilyPond 2.7.34 is out - February 16, 2006
This release has a bunch of bugfixes, and new features. Newly created
contexts may also be named with \new Voice =
"alto". Thicknesses of tie and slurs may be tuned separately for
the endings and the middle
part. (Cambiamenti,
Vecchi download)
LilyPond 2.7.33 is out - February 10, 2006
Items directly connected with a music input element may be
parenthesized, for example,
{
c4 -\parenthesize -.
<d \parenthesize fis a>
}
This feature was sponsored by Ramana Kumar. (Cambiamenti,
Vecchi download)
LilyPond 2.7.32 is out - February 7, 2006
This release contains some syntax changes: words inside the \paper and
\layout block are henceforth written with dashes, for instance:
{
\layout {
ragged-right = ##t
}
}
Furthermore, in this release, we have dropped some legacy code from
our library. Now, lily uses standard C++ strings and the STL
vector. (Cambiamenti,
Vecchi download)
LilyPond 2.7.31 is out - February 2, 2006
This release fixes a load of bugs, and has some internal
cleanups. Exported C++ members are now named
ly:class-name::function-name in Scheme instead of
Class_name::function_name. We are now using C++ vectors and strings
instead of our own. The Linux/FreeBSD builds now include wrappers for
Python scripts too, so you can run convert-ly and midi2ly.
(Cambiamenti,
Vecchi download)
LilyPond 2.7.30 is out - January 30, 2006
This release has a few bug fixes, like the solfa note head shape and
collisions, the \epsfile command, and in getting No. ligature in
normal words. (Cambiamenti,
Vecchi download)
LilyPond 2.7.29 is out - January 27, 2006
This release has the following new features. Alignments of staves may
be tuned per system (feature sponsored by Trevor Baca), individual
systems may be positioned manually (feature sponsored by Trevor Baca
and Nicolas Sceaux), a linebreaking configuration can now be saved as
a ‘.ly’ file automatically. This allows vertical alignments to be
stretched to fit pages in a second formatting run (feature sponsored
by Trevor Baca and Nicolas
Sceaux). (Cambiamenti,
Vecchi download)
LilyPond 2.7.28 is out - January 22, 2006
This release contains numerous small fixes that were already in our
GUB binaries. In addition, it has further polish for formatting of
tied chords. Theses improvements were sponsored by Steve
Doonan. (Cambiamenti,
Vecchi download)
LilyPond 2.7.27, release 4 - January 13, 2006
The fourth release of our Grand Unified Binary for 2.7.27 is
available. This release uses Pango 1.11.1, which has support for
ligatures and kerning. Enjoy! (Vecchi download)
LilyPond 2.7.27, release 3 - January 12, 2006
The third release of our Grand Unified Binaries is available. This
release fixes external font-support, the decompression flag for
Linux. Also, we have support for FreeBSD as well! Jump
to the Vecchi download get them!
LilyPond 2.7.27 binaries are out - January 7, 2006
Starting with 2.7.26, the development team has been working on the
installers. We’re proud to announce another version of these: they are
now available for
Linux/x86,
MacOS X and
Windows.
LilyPond 2.7.27 is out - January 7, 2006
This release allows you to switch staff lines on and off individually
(feature sponsored by Andrea
Valle). (Cambiamenti,
Vecchi download)
Linux Journal article - January 2006
Linux Journal publishes an article on
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 on-line.
New binaries for LilyPond 2.7.26 - January 4, 2006
The Development team has been working around the clock to improve
to fix the first wave bugs reported by you. The new results for MacOS
and Windows are up on the Vecchi download
page. Let us know how you fare!
LilyPond 2.7.26 is out - December 31, 2005
This release has an improvement in the MusicXML importer (feature
sponsored by Mark vd Borre’s Music Academy): now, staves and voices
are also setup, so you can readily run LilyPond on the .ly output.
The important occasion for this release is our new build
environment: we have completely revamped it, which means that binaries
for all platforms (including MacOS, Windows, Linux/x86, but probably
FreeBSD too) will be more quickly available for download.
A happy 2006 from the LilyPond Development Team!
(Cambiamenti,
Vecchi download)
LilyPond 2.7.25 is out - December 24, 2005
This release has various bugfixes. Also, stems on the center line now
have their directions interpolated to minimize the number of direction
changes (feature sponsored by Basil Crow and Mike
Rolish). (Cambiamenti,
Vecchi download)
LilyPond 2.7.24 is out - December 20, 2005
This release fixes a couple of bugs, but more importantly, slurs now
avoid TupletNumbers, and tuplet numbers may enter the staff (feature
sponsored by Trent Johnston), tuplet brackets and numbers are
implemented as separate grobs, TupletBracket and TupletNumber (rewrite
sponsored by Trent Johnston), string arguments for music functions may
be specified without # marks. This allows syntactical constructs (like
\clef and \bar) to be expressed in generic music
functions. (Cambiamenti,
Vecchi download)
LilyPond 2.7.23 is out - December 19, 2005
This release has the following new features:
-
Ties in chords are also formatted using score based
formatting. This reduces the number of collisions for ties in chords
(feature sponsored by Steve Doonan).
-
With the \tweak music function, layout objects that are directly
connected to input may be tuned easily (feature sponsored by Sean Reed
and Bertalan Fodor).
-
Generic music functions may now also be used on
articulations and chord elements (feature sponsored by Sean Reed and
Bertalan Fodor).
-
Better support for MusicXML, more options for spacing Lyrics;
it is now possible to separately specify minimum distances for normal
and hyphenated syllables (features sponsored by Mark van den Borre and
Bertalan Fodor.
(Cambiamenti,
Vecchi download)
LilyPond 2.7.22 is out - December 9, 2005
This release has better support for MusicXML: it also supports ties,
beams and editorial accidentals. It also has more options for spacing
Lyrics; it is now possible to separately specify minimum distances for
normal and hyphenated syllables. These features were sponsored by Mark
van den Borre and Bertalan
Fodor. (Cambiamenti,
Vecchi download)
LilyPond 2.7.21 is out - December 5, 2005
Saint Nicholas brings you ... a MusicXML convertor for LilyPond!
The convertor is basic, but working. Check out the LilyPond Software Design pages for MusicXML features that can be
sponsored.
LilyPond 2.7.20 is out - December 2, 2005
This release contains the following improvements: Texts set in a
TrueType font are now kerned. Using the TeX no longer requires linking
or dynamically opening the kpathsea library, making the backend more
easily usable on various systems (feature sponsored by Christian Ebert
of Black Trash
Productions). (Cambiamenti,
Vecchi download)
LilyPond 2.6.5 is out - December 1, 2005
This release updates the bugreporting address and reorganizes the
documentation tree. (Vecchi download)
LilyPond 2.7.19 is out - November 26, 2005
This version contains a few bugfixes, and now allows the type of
brackets in system start bracket hierarchies to be specified. Also,
the horizontal alignment of rehearsal marks may be changed: marks can
be put on key signatures, clefs, time signatures,
etc. (Cambiamenti,
Vecchi download)
LilyPond 2.7.18 is out - November 21, 2005
This version features nestable system start delimiters, like bracket,
brace. It also adds "square" line bracket (feature sponsored by Trevor
Baca). It also has refactored routines for tie formatting. This will
make it easier to get better tie formatting for chords (feature
sponsored by Steve Doonan). It also has a few bug
fixes. (Cambiamenti,
Vecchi download)
LilyPond 2.7.17 is out - November 17, 2005
This version has refactored routines for tie formatting. This will
make it easier to get better tie formatting for chords (feature
sponsored by Steve Doonan). It also has a few bug
fixes. (Cambiamenti,
Vecchi download)
LilyPond 2.7.16 is out - November 11, 2005
This release fixes a large number of bugs. Please upgrade before
reporting bugs in the 2.7 series. (Cambiamenti,
Vecchi download)
LilyPond 2.7.15 is out - November 3, 2005
This release has another massive cleanup of the backend. Each grob
property may also be a "grob closure". This means that it is possible
to combine functions. Calculation of extent and offset of grob is now
controlled via the ‘X-extent’, ‘Y-extent’, ‘X-offset’ and ‘Y-offset’
properties. (Cambiamenti,
Vecchi download)
LilyPond 2.7.14 is out - October 23, 2005
This release has more cleanup in the layout-engine. Now,
properties that have Procedure values are thought to be procedures
that compute said property, i.e.
\override Beam #'direction = #(lambda (grob)
(if (> (random 10) 5) UP DOWN))
will set a random direction for beams. (Cambiamenti,
Vecchi download)
LilyPond 2.7.13 is out - October 18, 2005
This release features slashed numerals, plus signs and interruptible
extender lines for figured bass. Merging of Figured bass lines has
been made switchable with the figuredBassCenterContinuations
property. For each grob, a subproperty in ‘callbacks’ property defines
the procedure which computes it. This is major internal cleanup, which
also provides advanced tweakability for power
users. (Cambiamenti,
Vecchi download)
LilyPond 2.6.4 is out - October 11, 2005
This release fixes a few minor problems with the stable
series. (Cambiamenti,
Vecchi download)
LilyPond 2.7.12 is out - October 07, 2005
It features more annotations for the page layout engine and some more
sponsored features. Beamlets may stick out of the side of beams
(feature sponsored by Trevor Baca); new support for figured bass with
support for continuation lines and tuning of figures, brackets, and
alignments (feature sponsored by Trent Johnston); vertical alignments
of staves can now be tuned easily for individual systems (feature
sponsored by Nicolas
Sceaux). (Cambiamenti,
Vecchi download)
LilyPond 2.7.11 is out - October 02, 2005
Vertical spacing for page layout can now be tuned for each system
individually (feature sponsored by Trevor Baca and Nicolas
Sceaux). The slope of a stem-tremolo may be set manually (feature
sponsored by Sven Axelsson). There are a number of cleanups in the
handling and representation of systems, among other features and bug
fixes. (Cambiamenti,
Vecchi download)
LilyPond 2.7.10 is out - September 13, 2005
This version adds proper support for "laissez vibrer ties", just enter
\laissezVibrer after a chord. This feature was sponsored by Henrik
Frisk. It also has a couple of minor
bugfixes. (Cambiamenti,
Vecchi download)
LilyPond 2.7.8 is out - August 29, 2005
This release has support for right-to-left text formatting in markup
commands (sponsored by Aaron Mehl). In addition, it fixes a great
number of bugs, among others, support for writing MIDI files. (Cambiamenti,
Vecchi download)
Article in ‘De Standaard’ - August 20, 2005
The Belgian newspaper De Standaard investigates what drives
Free Software authors in an article titled Delen van KENNIS
zonder WINSTBEJAG (Non-profit sharing of
knowlegde) using LilyPond as an example. This marks
LilyPond’s first appearance in mainstream printed press.
LilyPond 2.7.7 is out - August 22, 2005
This release has a rewriting of tie formatting which was sponsored by
Bertalan Fodor, Jay Hamilton, Kieren MacMillan, Steve Doonan, Trevor
Baca, and Vicente Solsona Dellá. (Cambiamenti,
Vecchi download)
LilyPond 2.7.6 is out - August 19, 2005
This release adds support for numbered percent repeats, a feature
sponsored by Yoshinobu Ishizaki. It also has bugfixes for clashes
between slurs and symbols, like fingers dynamic
signs. (Cambiamenti,
Vecchi download)
LilyPond 2.7.5 is out - August 16, 2005
Lily 2.7.5 has a large number of bugfixes, among others, in slur
formatting, spacing, rest collisions and tuplet bracket
formatting. (Cambiamenti,
Vecchi download)
LilyPond 2.7.4 is out - August 7, 2005
LilyPond 2.7.4 has support for proportional notation, where the space
for a note is proportional to the time it
takes. (Cambiamenti,
Vecchi download)
LilyPond 2.6.3 is out - August 4, 2005
This release fixes a memory corruption bug that was triggered by
\override’ing Beam settings. (Vecchi download)
LilyPond 2.6.2 is out - August 2, 2005
This release has a few bugfixes, among them: the autopackage will run
in more platforms, LilyPond will be much quicker for large
lilypond-book documents, and the up and down Fa note heads for shaped
heads have been
swapped. (Cambiamenti,
Vecchi download)
LilyPond 2.7.3 is out - July 25, 2005
LilyPond 2.7.3 has improvements in performance which should result in
faster operations (15 to 20 percent). It also contains the new
"\displayLilyMusic" function.
(Cambiamenti,
Vecchi download)
LilyPond 2.7.2 is out - July 21, 2005
LilyPond 2.7.2 has support for suggested accidentals for musica
ficta notation, easy entry for lyric melismata and improvements for
quicker entry of scores. (Cambiamenti,
Vecchi download)
LilyPond 2.6 released - June 27, 2005
Version 2.6 is the latest stable release of LilyPond.
It now
installs in a snap on Windows, MacOS X, and any version of Linux (x86).
Get up and running in minutes! Pango text formatting lets you
print Unicode lyrics in your favorite script and font. Create
SVG files, and edit them in Inkscape.
(Announcement, Vecchi download, Cambiamenti)
LilyPond 2.7.1 is out - July 20, 2005
LilyPond 2.7.1 has no user-visible changes. However, due to
restructuring “under the hood”, this version will be 10 to
20 % faster. (Vecchi download)
LilyPond 2.6.1 is out - July 11, 2005
This version fixes a few minor bugs found in
2.6.0, and also works on DOS-based Windows versions. (Cambiamenti,
Vecchi download)
LilyPond 2.7 is out - July 9, 2005
LilyPond 2.7.0 is out. It has support for paragraph text and
pitched trill notation. (Cambiamenti,
Vecchi download)
2.5.31 released - June 22, 2005
LilyPond 2.5.32 is now available for download (binaries for Fedora +
MacOS only). It has a few very minor bugfixes, and a rewrite of the
TTF embedding code, which should be a lot more robust now.
(Vecchi download)
Traduction du site de LilyPond - 15 juin 2005
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 !
2.5.31 for Windows and MacOS - June 15, 2005
2.5.31 is now available for both Windows and MacOS X. The Windows
version should now work with embedding TTF fonts, and the MacOS X has
better help functionality.
(Vecchi download)
2.5.31 released - June 15, 2005
This release has a few bugfixes. In the MacOS X version, ClickEdit has
been renamed to LilyPond, and you can now upgrade your files and
compile them directly from
LilyPond. (Vecchi download)
2.5.30 released - June 10, 2005
This is (hopefully) the last Release Candidate before 2.6. Give it a
good shake to find those last bugs! (Vecchi download)
2.5.29 released - June 7, 2005
In this release the documentation also has pictures. In addition, the
Mac version can also read native mac fonts (.dfonts and fonts in
resource forks). (Vecchi download)
2.5.27 released - May 31, 2005
It has a big bunch of minor bugfixes. This is another release
candidate for version 2.6, which should be released within the next 2
weeks. Please send a bug report if you find a critical problem with this
release. (Vecchi download)
Windows and MacOS installers available - May 26, 2005
There are now a native, standalone installers for Windows and
MacOS. They also support PDF point & click. (Vecchi download)
2.5.26 released - May 26, 2005
This release has a couple of small bugfixes.
2.5.25 released - May 20, 2005
This release has many small bugfixes and updates to the
documentation. (Vecchi download)
2.5.24 released - May 12, 2005
2.5.24 fixes a bunch of bugs; in particular, chord symbols (such as
slashed o) should now work on all platforms. This release has a new
feature: it is now possible to make staves appear in a different order
from the order that they were defined. (Vecchi download)
2.5.23 released - May 6, 2005
This release has a couple of small bugfixes, and a new feature. It is
now possible to start and stop the StaffSymbol, during a piece of
music, by doing \stopStaff \startStaff. This can be used to
produce Ossia staves. (Cambiamenti,
Vecchi download)
2.5.22 released - May 3, 2005
2.5.22 is a bugfix
release. The most visible improvement is in the PDF : this release
will produce smaller PDF files, with symbols that look better on
screen.
(Vecchi download)
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.
(Cambiamenti,
Vecchi download)
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 Cambiamenti
file, or go straight to Vecchi download.
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 Cambiamenti
file and Vecchi download.
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. Vecchi download
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. Vecchi download
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.
Vecchi download
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 Cambiamenti
file and Vecchi download!
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 Cambiamenti
file and download Vecchi download!
March 7, 2005
LilyPond 2.4.5 is out. This release backports the tieWaitForNote
feature and has support for tetex-3.0.
Vecchi download
February 28, 2005
LilyPond 2.5.13 is available for Fedora Core 3. You need to install
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.
February 28, 2005
LilyPond 2.5.13 is out. This release has Point and click support for
PDF output. You can read more about it here.
Take a look at the Cambiamenti
file and download Vecchi download!
February 26, 2005
The 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.
February 21, 2005
LilyPond 2.5.12 is out. The big news is that this release supports
TrueType fonts. This means that it is now possible to use all
fonts available via FontConfig. Also, arpeggios may be written out
using ties and individual objects may have colors! Take a look at
the Cambiamenti
file and Vecchi download!
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.
Vecchi download!
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.
Vecchi download
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.
Vecchi download
January 16, 2005
LilyPond 2.5.8 is out. This
release has many internal code cleanups. In addition,
accuracy of error reporting has been improved.
See the
change log and Vecchi download!
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.
Vecchi download
and check out the changes in
the ChangeLog.
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.
Vecchi download
and check out the
changes in the ChangeLog.
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.
Vecchi download
and check out the changes in
the ChangeLog.
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.
Vecchi download
and check out the
changes in the ChangeLog.
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.
Vecchi download
and
check out the changes in the ChangeLog.
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.
Vecchi download
and check out the changes in
the ChangeLog.
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.
Vecchi download
and check out the changes in
the ChangeLog.
November 12, 2004
The LilyPond development is OPEN once again! The first
release of the 2.5 series has the following new Features:
Positioning of slurs can now be adjusted manually, Grace
notes are correctly quoted and formatted when using cue
notes, Cue notes can now be created with
\cueDuring #VOICE-NAME #DIRECTION { MUSIC }
Stemlets (short stems over beamed rests) have been added.
In addition, Jan hacked together some highly experimental
code where you can use the mouse to drag and drop objects in
the -f gnome backend. These tweaks can be saved and are
applied to the PS and TeX output as well.
Vecchi download
and check out
the changes in the ChangeLog.
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.
Vecchi download
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.
Vecchi download
and check out the changes in
the ChangeLog.
October 31, 2004
LilyPond 2.4.0 was just released!
This new stable version has support for page-layout,
completely rewritten slur formatting and many other
improvements. Read about them in the Cambiamenti
file.
Vecchi download
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.
Vecchi download
and check out the changes in
the ChangeLog.
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.
Vecchi download
and check out the changes in
the ChangeLog.
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.
Vecchi download
and check out the changes in
the ChangeLog.
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.
Vecchi download
and check out the changes in
the ChangeLog.
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{}.
Vecchi download
and
check out the changes in the ChangeLog.
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.
Vecchi download
and check
out the changes in the ChangeLog.
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.
Vecchi download
and check out the changes in
the ChangeLog.
September 29, 2004
The LilyPond development team will be present at the 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.
September 26, 2004
LilyPond 2.3.19 is out. It’s mainly a bugfix release.
Vecchi download
and check out the changes
in the ChangeLog.
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.
Vecchi download
and check out the changes in
the ChangeLog.
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.
Vecchi download
and check out the changes in
the ChangeLog.
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.
Vecchi download
and check out the changes in
the ChangeLog.
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.
Vecchi download
and check out
the changes in the ChangeLog.
August 29, 2004
LilyPond now has a Documentation
Editor, Graham Percival. From now on, he will oversee that
useful information flows from the mailiing list into the
manual. Also, if there are unclear sections in the manual,
let him know via one of the mailing lists.
As a start of his career, he worked to transform the
"Templates" section of the website into a readable and comprehensive
chapter of the user manual.
A lot of cheers for Graham!
August 29, 2004
LilyPond 2.3.13 was released. The new slur code was
improved, scripts can be made to avoid slurs, by setting
inside-slur to #f. It is no longer necessary to instantiate
"up" and "down" staves separately when using
\autochange. Jurgen Reuter refreshed the logic around
mensural flags, so they are adjusted for staff lines once
again.
Vecchi download
and
check out the changes in the ChangeLog.
August 24, 2004
LilyPond 2.2.6 fixes a few minor issues, among others, the
disappearing metronome mark.
Vecchi download
and check out the changes in
the ChangeLog.
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.
Vecchi download
and check out the changes in
the ChangeLog.
August 3, 2004
LilyPond 2.3.11 is out. This release basically is 2.3.10 with a few
annoying bugs fixed.
Vecchi download
and check out
the changes in the ChangeLog.
August 1, 2004
LilyPond 2.3.10 is out. This release has a major clean-up of the
input/test/ directory. Many examples have been moved to the regression
test or manual, and the superfluous or outdated ones have been
removed. The directory has gone from 146 examples to 72 examples. That
means that we’re halfway cleaning it out. Incidentally, the manual
has gone from 200 to 220 pages. New features:
-
Running trills now have their own spanner and event. They are
started and stopped with \startTrillSpan and \stopTrillSpan
-
There is a new markup command ‘\postscript’ that takes a string
that is dumped as verbatim PostScript
Vecchi download
and check out
the changes in the ChangeLog.
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.
Vecchi download
and check out
the changes in the ChangeLog.
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.
Vecchi download
and check out the changes in the ChangeLog.
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.
Vecchi download
and check out the changes in
the ChangeLog.
July 15, 2004
LilyPond 2.2.5 was released. It has a few bug fixes from
2.3.x.
Vecchi download
and check
out the changes in the ChangeLog.
July 11, 2004
An introductory article on LilyPond appeared on Linux Journal.
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.
Vecchi download
and check out the changes
in the ChangeLog.
July 5, 2004
LilyPond 2.2.4 was released. It is mainly a bug fix
release.
Vecchi download
and
check out the changes in the ChangeLog.
June 25, 2004
LilyPond 2.3.5 has numerous small bugfixes and cleanups, and
features more work in the experimental GNOME output
module. Adventurous hackers can check the instructions at
scm/output-gnome.scm and try to run
buildscripts/guile-gnome.sh to see what the fuss is all about.
Carl Sorensen also provided us with more patches to the
fret-diagram output. Check out the ChangeLog
and
Vecchi download.
June 20, 2004
LilyPond 2.2.3 has a turkish translation and fixes a few minor
bugs that were reported over the past month. Check out the ChangeLog for a full description and
Vecchi download.
June 13, 2004
LilyPond 2.3.4 further improves the output backends. As a
result, manual page-breaks, multiple output formats and putting
\score into markups now works. Check out the ChangeLog
and
Vecchi download.
May 31, 2004
LilyPond 2.3.3 has many internal changes relating to the output
backend (PostScript) and page-layout. In addition, it contains a few
bugfixes for recently reported problems. Check out the ChangeLog
and
Vecchi download.
May 31, 2004
LilyPond 2.2.2 is out. It has a number of small bugfixes, so upgrade
if any of these errors concern you. Check out the ChangeLog
or head straight to the
Vecchi download.
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 Cambiamenti or head straight to the
Vecchi download.
May 9, 2004
LilyPond 2.3.1 is out. This release has many new and cool
features. Check out the Cambiamenti or head straight to the
Vecchi download.
May 4, 2004
Help LilyPond get better, and join in on LilyPond
development! This
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!
May 3, 2004
LilyPond 2.2.1 has been released. It fixes a handful of bugs.
Vecchi download.
April 17, 2004
LilyPond 2.2.0 is now available
on Windows, and should find its way to the Cygwin mirrors
soon.
April 12, 2004
LilyPond 2.3.0 is the first release
in the 2.3 cycle. The focus for 2.3 is page layout, so
instrumentalists can force parts to have page breaks at sane turning
points. This release is experimental; expect things to break!
More info in the Cambiamenti.
Vecchi download.
April 8, 2004
A French article on the new LilyPond
release appeared on linuxfr.org.
April 8, 2004
Binaries for LilyPond 2.2.0 are available for
MacOS X, Slackware, Mandrake and Debian Woody.
Vecchi download
April 1, 2004
LilyPond 2.2.0 is out! This new stable version has
completely revamped support for for orchestral score
formatting, cue notes, font size management, lyric formatting,
drum notation/playback and document integration. Read about it in
the announcement or skip to the
Vecchi download.
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.
Vecchi download.
March 30, 2004
LilyPond 2.1.36 has many fixes in
the user manual.
Vecchi download.
March 28, 2004
LilyPond 2.1..35 fixes a slew of
bugs, and has the raggedlast option, which causes
paragraph like line breaking for scores. More info in the
Cambiamenti.
Vecchi download
March 22, 2004
LilyPond 2.1.34 fixes minor bugs, and has more rewriting.
Vecchi download.
March 21, 2004
LilyPond 2.1.33 fixes a serious bug, and a few other
irritations.
Vecchi download
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).
Vecchi download.
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
Cambiamenti and
Vecchi download.
March 11, 2004
linuxmusician.com is
running an
interview
with Han-Wen Nienhuys and Jan Nieuwenhuizen, the main
authors of LilyPond.
March 11, 2004
LilyPond 2.1.30 has editorial fixes for the manual, and
experimental support for page layout in the PostScript
backend. See the
Cambiamenti and
Vecchi download.
March 9, 2004
LilyPond 2.1.29 fixes a couple of MIDI bugs, and has
experimental support for producing titles with
markup.
February 29, 2004
In LilyPond 2.1.28 Scheme property functions may be used
argument to set!. In addition, parts of the manual
have been proofread and corrected in this release. See the
Cambiamenti and
Vecchi download.
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
Cambiamenti and
Vecchi download.
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
Cambiamenti.
Vecchi download
February 18, 2004
LilyPond 2.1.25 fixes many bugs, and changes the conventions
for altering accidental rules.
Vecchi download
February 16, 2004
LilyPond 2.1.24 has a big
internal rewrite. One of its practical consequences is that
\with now also works with Score
contexts. Further 2.1.23, which was not announced here,
fixes a few bugs caused by the change of \property
syntax and has updates in the Program Reference document.
More information in the
Cambiamenti.
Vecchi download
February 13, 2004
LilyPond 2.1.22 has a
simplification of the \property syntax: it is
shorter and more consistent now. More information in the
Cambiamenti.
Vecchi download
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
Cambiamenti.
Vecchi download
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
Cambiamenti.
Vecchi download
February 5, 2004
LilyPond 2.1.19 has rewritten
support for drum notation. This release also makes some
long-standing cleanups: the removal of Thread (all
functionality is now moved into Voice) and Lyrics
(functionality moved to LyricsVoice) context.
More information in the
Cambiamenti.
Vecchi download
February 4, 2004
LilyPond 2.1.18 is out. This
release has the new part-combiner installed by default, and a
similar implementation of autochange. More information
in the
Cambiamenti.
Vecchi download
February 2, 2004
LilyPond 2.1.17 is out. It adds texts
(solo, a due) for the part combiner. It also reinstates the
‘--safe’ option which prevents havoc by Scheme exploits. More
information in the
Cambiamenti.
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
Cambiamenti.
Vecchi download
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
Cambiamenti. Vecchi download
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
Cambiamenti. Vecchi download
January 20, 2004
The lilypond.org domain has been moved to a new server. This
will result in better connectivity and more bandwidth. Due
to security concerns, the new server does not offer FTP
access, but only HTTP downloads.
January 20, 2004
LilyPond 2.1.13 fixes a small but
nasty bug in side-positioning placement, and some bugs in
tuplet, tie and accidental formatting. This release contains
rudimentary work on a new part-combiner.
Vecchi download
January 19, 2004
LilyPond 2.1.12 fixes many bugs
and improves formatting of ottava brackets. More information in
the
Cambiamenti. Vecchi download
January 18, 2004
LilyPond 2.1.11 is now also
available for Windows! For downloading, go
here.
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
Cambiamenti. Vecchi download
January 16, 2004
LilyPond 2.1.10 has a load of
bugfixes and a shorter syntax for octave checks. More
information in the
Cambiamenti. Vecchi download
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
Cambiamenti. Vecchi download
January 9, 2004
LilyPond 2.1.8 has an important new
feature: it is now possible to use \property to tune
the appearance of spanning objects like StaffSymbol and
SystemStartBrace. In addition, contexts may be
modified with \remove and \consists for
individual music expressions.
More information in the
Cambiamenti. Vecchi download
January 7, 2004
An update to the stable branch,
version 2.0.2, was released today. It contains a couple of
minor bugfixes. Vecchi download
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
Cambiamenti and download here.
January 4, 2004
LilyPond 2.1.6 continues to improve the layout of lyrics. More
information in the
release notes and download here.
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 Cambiamenti and
download here.
December 30, 2003
LilyPond 2.1.4 is released. Font shapes and line thickness
are now truly different for different staff sizes, thus lending
an engraved look to scores printed in smaller type too. See the
Cambiamenti and download here.
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
Cambiamenti and download here.
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
Cambiamenti and download here.
December 16, 2003
LilyPond 2.1.1 released. This
release wraps together all the small fixes made during
Han-Wen’s absence. See the
Cambiamenti and download here.
October 11, 2003
LilyPond 2.1.0 released. See the
Cambiamenti and
download here.
October 11, 2003
LilyPond 2.0.1 binaries for Mandrake 9.1
available from
here
thanks to Heikki Junes.
October 9, 2003
LilyPond 2.0.1 binaries for Slackware 9
available from here,
thanks to Ricardo Hoffman.
October 5, 2003
LilyPond 2.0.1 binaries are available for Macos X, many thanks to
Matthias Neeracher.
Vecchi download
October 4, 2003
LilyPond 2.0.1 binaries are available for Windows (Cygwin
version 1.5).
Vecchi download. Thanks to Bertalan
Fodor, our new Cygwin maintainer!
September 29, 2003
LilyPond 2.0.1 is released. It
contains minor bugfixes.
See the Cambiamenti
or download here directly.
September 27, 2003
PlanetCCRMA has been updated to include LilyPond 2.0. Go
here to download. Thanks to Fernando Pablo
Lopez-Lezcano!
September 24, 2003
LilyPond 2.0.0 is released. The
focus of this release is cleanups of the syntax: entering music is
now much easier and more efficient. Read the announcement
here, or go to the
download page directly.
September 24, 2003
LilyPond 1.9.10 is released. This is
the final LilyPond 2.0 release candidate. Check
the Cambiamenti and
download here.
September 23, 2003
LilyPond 1.9.9 is released. This is
the second LilyPond 2.0 prerelease. Check
the Cambiamenti and
download here.
September 19, 2003
LilyPond 1.9.8 is released. This is
the first LilyPond 2.0 prerelease. Check
the Cambiamenti and
download here.
September 17, 2003
LilyPond 1.9.7 is released. LilyPond
now has support for quarter tone accidentals!
Vecchi download
September 16, 2003
LilyPond 1.9.6 is released.
It has a lot of minor fixes and updates.
Vecchi download
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.
Vecchi download
September 9, 2003
LilyPond 1.8.2 is released. This
release fixes a couple of minor bugs.
Vecchi download
September 7, 2003
LilyPond 1.8 binaries are available
for Windows (Cygwin version 1.5).
Vecchi download
August 31, 2003
LilyPond 1.9.4 is released.
This is an experimental release: read the
announcement
before trying.
August 31, 2003
LilyPond 1.8 binaries for slackware
available. Get them here.
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
Cambiamenti and get it here.
August 28, 2003
LilyPond 1.9.2 is released. Read the
Cambiamenti and get it
here.
August 26, 2003
LilyPond 1.9.1 is released. Read the
Cambiamenti and get it
here.
August 25, 2003
The LilyPond 1.9 development release is available. Read the
Cambiamenti and get it
here.
August 25, 2003
Mandrake 9.1 RPMS available, get them
here.
August 21, 2003
LilyPond 1.8.1 was released. Get it here, or
read the Cambiamenti.
August 18, 2003
PlanetCCRMA (eg. RedHat 8 and 9)
has been updated to 1.8.
Download here.
August 7, 2003
New website went live!
August 6, 2003
Announced new website.
August 1, 2003
LilyPond 1.7.30 released.
July 30, 2003
Website: present treatise
about music engraving, music printing software, and LilyPond’s
unique faculties.
July 29, 2003
1.7.29 - release candidate 4 has been released. Packages for
Red Hat, Debian, Cygwin are available.
Indice
Informazioni su questo documento
This document was generated by Karlin High on Ottobre 3, 2017 using texi2html 1.82.
I bottoni nei pannelli di navigazione hanno il seguente significato:
| Bottone |
Nome |
Vai a |
Da 1.2.3 vai a |
| [] |
|
|
|
| [ << ] |
Indietro veloce |
Inizio di questo capitolo o capitolo precedente |
1 |
| [] |
|
|
|
| [Inizio] |
Inizio |
Copertina (inizio) del documento |
|
| [Contenuti] |
Contenuti |
Indice |
|
| [Indice] |
Indice |
Indice |
|
| [ ? ] |
Informazioni |
Informazioni (aiuto) |
|
| [] |
|
|
|
| [ >> ] |
Avanti veloce |
Capitolo successivo |
2 |
| [] |
|
|
|
| [] |
|
|
|
| [ < ] |
Indietro |
Sezione precedente in ordine di lettura |
1.2.2 |
| [] |
|
|
|
| [ Su ] |
Su |
Sezione superiore |
1.2 |
| [] |
|
|
|
| [ > ] |
Avanti |
Sezione successiva in ordine di lettura |
1.2.4 |
dove Esempio assume che l’attuale posizione è alla Sottosottosezione Uno-Due-Tre di un documento che ha la seguente struttura:
- 1. Sezione uno
- 1.1 Sottosezione Uno-Uno
- 1.2 Sottosezione Uno-Due
- 1.2.1 Sottosottosezione Uno-Due-Uno
- 1.2.2 Sottosottosezione Uno-Due-Due
- 1.2.3 Sottosottosezione Uno-Due-Tre
<== Posizione Attuale
- 1.2.4 Sottosottosezione Uno-Due-Quattro
- 1.3 Sottosezione Uno-Tre
- 1.4 Sottosezione Uno-Quattro
Altre lingue: English, català, česky, deutsch, español, français, magyar, 日本語, nederlands, 中文.
About automatic language selection.
Validation
Grazie a
webdev.nl per l'hosting di
lilypond.org.
