LilyPond – kottaszedés mindenkinek

# LilyPond... kottaszedés mindenkinek

## LilyPond

...kottaszedés mindenkinek

### Mi az a LilyPond?

A LilyPond egy nyílt forrású kottaszedő program, mely a lehető legjobb minőségű kotta előállítására képes. Ez a szabad szoftver a hagyományos, kézzel szedett kották szépségét adja vissza.

Ha többet akarsz róla megtudni, olvasd el a Bevezetést!

#### LilyPond 2.14.2 released! July 22, 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.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.13/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.

(Hírarchívum)

# Bevezetés

### Célkitűzés

Az ihlet akkor jött, amikor két zenész barát megelégelte a számítógéppel szedett kották csúnya kinézetét. Minden zenésznek jobb, ha a kotta, amiből játszik, szép; hát akkor mi, programozók, nem tudnánk erre megoldást találni? – gondolták.

A megoldás a LilyPond: az általa szedett kotta a legmagasabb tipográfiai igényeknek felel meg, kézi beavatkozás nélkül. Ne azzal foglalkozz, hogy helyükre igazítsd a kotta elemeit! Ejtsd ámulatba zenész társaidat professzionális kinézetű kottákkal!

### Miért használd a LilyPondot?

- Képességek: Mire képes a LilyPond?
- Példák: Kottákat szeretnék látni!
- Szabadság: A LilyPond szabad szoftver.
- Háttér: Esztétikai elveink.

### Ki használja?

- Felhasználások: A LilyPonddal szedett kották előfordulásai a valós életben.
- Ajánlások: Mit mondanak róla az emberek?

### Miért ne használnád a LilyPondot?

- Szöveges bevitel: A zenét szövegként kell beírni?!
- Könnyebb bevitel: Egyszerűbb szerkesztési módok.

## Képességek

### Miért érdemes a LilyPondra váltani?

#### Kitűnő hagyományos szedés

Minden elem, szimbólum és algoritmus megtervezéséhez a régi, aprólékosan kézzel szedett kottákból merítettünk ihletet. A LilyPond kimenete ugyanolyan jól olvasható, mint bármelyik klasszikus kotta. (Erről az Esszében olvashatsz bővebben.)

#### Nincs szükség finomhangolásra

Ne töltsd azzal az idődet, hogy a kimenetet kézzel tökéletesíted; a LilyPond kezdettől fogva ügyel a tökéletes formázásra. Önmagától meghatározza az optimális elhelyezést, a sor- és oldaltöréseket az egyenletes kottakép érdekében. Nincsenek egymást átfedő elemek, az ívek és gerendák pedig szép arányosak – mindez automatikusan!

#### Szöveges formátum

A LilyPond bemenete egyszerű szöveges fájl, melyet saját kedvenc szövegszerkesztőddel írhatsz, gyorsan és kényelmesen. Nincs több babrálás az egérrel! A bemenet minden információt tartalmaz, így nincs szükség összetett menüstruktúrák megjegyzésére. Ha egy témára később szükséged van, csak elmented, és később hivatkozhatsz rá.

#### Zene és szöveg együtt

Egyszerűen helyezhetsz el kottapéldákat dokumentumaidban; nincs szükség képek konvertálására és beillesztésére. Akár LaTeX, akár HTML, sőt, az ooolilypond révén még OpenOffice.org dokumentumokba is simán integrálható a LilyPond.

#### Szólamkották a lehető legegyszerűbben

A partitúra és a szólamkották egy forrásból származnak, így minden változás automatikusan tükröződik a partitúrában és a szólamanyagokban is. A LilyPond hasonló technikával a belépés előtti segédhangokat is képes beszúrni.

#### Szabad szoftver

A LilyPond ingyenesen letölthető! Bizony, teljesen ingyen. Szerezd be most a letöltések közül!

Ráadásul a LilyPond szabad szoftver. Forráskódja szabadon elérhető, és bárki továbbfejlesztheti. Tehát, ha zavar egy hiba, vagy nagyon vágysz egy megvalósítatlan képességre, te magad jobbá teheted a programot, vagy finanszírozhatod, hogy más tegye meg ezt.

#### Bővíthetőség

Minden beállítás módosítható a saját tipográfiai ízlésed szerint. Ha ez még mindig nem lenne elég, beépített scriptelési lehetőség áll rendelkezésedre Scheme nyelven, amivel szinte mindent megtehetsz. A beállítások, változók és függvények egytől egyig pontosan le vannak dokumentálva a mindenre kiterjedő programreferenciában.

#### Széles körű támogatás

A LilyPond minden népszerű operációs rendszeren fut: Linuxon, Mac OS X-en és Windowson. A LilyPondhoz egy 600 oldalas felhasználói kézikönyv és több, mint 400 példafájl tartozik. Segítőkész felhasználói közösség kész megválaszolni kérdéseidet a LilyPond-felhasználók levelezőlistáján, a fejlesztőcsapat pedig gondoskodik arról, hogy a problémák gyorsan megoldódjanak.

### Hogyan tovább?

Még mindig nem vagy meggyőzve? Nézd meg a gyönyörű példákat! Ha úgy döntöttél, hogy használni szeretnéd a LilyPondot, először olvasd el a tudnivalókat a szöveges bevitelről.

## Példák

A LilyPond egy hatékony és rugalmas eszköz, mely mindenféle kottaszedési feladatra alkalmas. Gyönyörködj az alábbi példákban, és meríts ihletet belőlük!

#### Klasszikus zene

J. S. Bach eme orgonaműve egyszerű szedési feladatot jelent.

(Kattints a képre a nagyításhoz)

#### Komplex lejegyzés

Enrique Granados Goyescas c. művének részlete bemutat pár bonyolultabb kottaelemet, mint például a kottasorok közötti szárak vagy a szólamok más kottasorba ugrását jelző vonalak.

(Kattints a képre a nagyításhoz)

#### Régizene

A LilyPond a menzurális és a kvadrátnotációt is támogatja, amint azt az alábbi gregorián antifóna-részlet is mutatja.

(Kattints a képre a nagyításhoz)

#### Modern zene

A kortárs szerzők szokatlan lejegyzési igényeit a LilyPond teljes mértékben kielégíti. Íme egy részlet Trevor Bača Cáry c. művéből basszusfuvolára.

(Kattints a képre a nagyításhoz)

#### Szólamkották egyszerű és gyors létrehozása

Egyazon forrásból automatikusan különböző célú próbaanyagok hozhatók létre. Händel Giulio Cesare c. operájának partitúráját, zongorakivonatát és hegedűszólamát láthatjuk Nicolas Sceaux szedésében.

(Kattints a képre a nagyításhoz)

(Kattints a képre a nagyításhoz)

(Kattints a képre a nagyításhoz)

#### Tabulatúra

A LilyPond tabulatúra szedésére is képes, és testreszabható bármilyen hangszerre, amely tabulatúrából olvas. A hangok bevitele ugyanúgy történik, mint a rendes ötvanalas vonalrendszerben, a LilyPond automatikusan tabulatúraként jegyzi le őket.

(Kattints a képre a nagyításhoz)

#### Schenker-diagramok

Az alapbeállítású kimenet erőteljesen módosítható. Példánkban egy figyelemreméltó Schenker-féle analízis eredményét láthatjuk.

(Kattints a képre a nagyításhoz)

#### Vokális zene

A LilyPond kiválóan alkalmas mindenféle vokális zene szedésére, az egyházi énekektől az operákig. Itt egy középkori motetta látható némileg szokatlan követelményekkel: a tenor szólam más metrumban van, mint a többi, de lüktetésének alapegysége ugyanakkora. A LilyPond ezt teljesen elegánsan kezeli. Az incipiteket is érdemes megfigyelni a régi stílusú kulcsokkal, a plicát jelző áthúzott szárat, valamint a ligatúrákat.

(Kattints a képre a nagyításhoz)

#### Oktatási anyagok

A LilyPond tökéletesen megfelel oktatási célokra is. Bemutatunk egy egyszerű ellenpont-kidolgozási feladatot.

(Kattints a képre a nagyításhoz)

#### Popszámok

Könnyűzenei számok is egyszerűen lekottázhatóak dallamal, dalszöveggel, akkordnevekkel és -ábrákkal. Az alábbi példa az alapbeállítású akkordábrákat mutatja, de ezek is tetszőlegesen testreszabhatóak.

(Kattints a képre a nagyításhoz)

#### Nagy projektek

A LilyPond kitűnően használható nagy művek, például operák vagy nagyzenekari művek szedésére. Ráadásul a szöveges beviteli mód akadálymentességet biztosít – a következő példa Hu Haipengtől, egy vak zeneszerzőtől származik.

(Kattints a képre a nagyításhoz)

### Hogyan tovább?

Még mindig nem vagy meggyőzve? A LilyPond szabad szoftver, mely szabadságot ad. Ha úgy döntöttél, hogy használni szeretnéd a LilyPondot, először olvasd el a tudnivalókat a szöveges bevitelről.

## Szabadság

### Szabad szoftver

A GNU LilyPondot lelkes, zenét és informatikát kedvelő emberek írták és tartják karban. A program licence a GNU General Public License, a dokumentációé pedig a GNU Free Documentation License, ezáltal mindenki szabadon javíthatja, módosíthatja és bővítheti azt. Nem szabad, hogy több száz dollárba kerülő szoftverre legyen szükség gyönyörű kották írásához!

### Milyen előnyökkel jár ez a felhasználó számára?

- Ingyenesség: csak töltsd le és próbáld ki! Mi vesztenivalód van?
- Megosztás: ha tetszik, nyugodtan adhatsz belőle egy példányt barátaidnak, tanáraidnak, tanítványaidnak és kollégáidnak!
- Elérhető forráskód: ha kíváncsi vagy, hogyan működik a LilyPond, bármikor megvizsgálhatod.
- Bővíthetőség: bármikor megvalósíthatsz új funkcionalitást, kijavíthatsz hibákat, vagy megváltoztathatod a működést. Ha nem tudsz programozni, finanszírozhatod, hogy más tegye meg ezt.

  Ez a lehetőség lehet, hogy a mindennapi zenész számára nem vonzó, de a szoftver bővítésének lehetősége nagyon fontos lehet komoly igényekkel rendelkező zeneszerzők, cégek és akadémiák számára.

- Garancia a jövőre nézve: ha egy kottaszerkesztő szoftvert fejlesztő cég csődbe megy, mi lesz a kottákkal, amiket csak az ő termékük tud megnyitni? Ez a veszély nem áll fenn a LilyPond esetén; még ha az egész fejlesztőcsapat abba is hagyná a fejlesztést (ami persze elég valószínűtlen), a program továbbra is legálisan másolható, terjeszthető és módosítható marad, így bárki folytathatja a fejlesztését és a támogatását.

### Miért ajánlják fel ingyen a fejlesztők a munkájukat?

A legtöbben hobbiból, önkéntes módon fejlesztjük a LilyPondot. Így valójában az a kérdés: miért vállalkozik valaki ilyen önkéntes munkára?

- Élvezet: egy cél eléréséért végzett munka motiváló erővel bír, főleg, ha az ember csapatban dolgozik!
- Közös célok: mindannyian szeretnénk gyönyörű kottából játszani, de kevés embernek van szakértelme (és senkinek sincs ideje!), hogy létrehozzon egy programot, amely minden szituációt kezelni tud. De együttes erővel – egyvalaki az automatikus gerendázást fejleszti, másvalaki az ívek alakját javítja, megint másvalaki dokumentációt ír, hogy elmagyarázza, hogyan kell a funkciókat használni – el tudjuk érni a célunkat az egyébként egyénileg belefektetendő erőfeszítés töredékével.
- „Ajándék-kultúra”: a szabad szoftver- (vagy „nyílt forrás-”) mozgalom már sok nagyszerű szoftver projekttel állt elő, pl. a GNU/Linux, a Mozilla Firefox vagy a Battle for Wesnoth. Ezeket a projekteket használván, bizonyos fejlesztők szeretnének „visszaadni” valamit a közösségnek.
- Szakmai tapasztalat: a nyílt forrású projektekben való közreműködés egy remek módja annak, hogy az ember gyakorolja a programozást, dokumentálást vagy tervezést. Ez a tapasztalat sok fejlesztőt segített már álláshoz vagy ösztöndíjhoz.

### Hogyan tovább?

Még mindig nem vagy meggyőzve? Olvasd el az esszénket a kottaszedési filozófiánk hátteréről. Ha úgy döntöttél, hogy használni szeretnéd a LilyPondot, először olvasd el a tudnivalókat a szöveges bevitelről.

## Háttér

### Esszé

Írtunk egy sok mindenre kiterjedő esszét a számítási esztétikánkról, arról, hogyan kell számítógéppel szépet létrehozni.

Ha csak egy gyors bevezetést szeretnél a LilyPondba, az esszé kicsit terjedelmes lehet, de ha kíváncsi vagy rá, olvasd el nyugodtan.

### Hogyan tovább?

Még mindig nem vagy meggyőzve? Tájékozódj a LilyPonddal szedett kották felhasználásairól! Ha úgy döntöttél, hogy használni szeretnéd a LilyPondot, először olvasd el a tudnivalókat a szöveges bevitelről.

## Felhasználások

### Koncertek

A LilyPonddal szedett kottákat szerte a világon használják előadásokon. Íme néhány ezek közül:

- Affaire Étrangère, Valentin Villenave operája, Lewis Trondheim szövegkönyvére. Bemutatója 2009. február 1-én volt, az Opéra Montpellier-ben.
- Lully Armide c. operája a Mercury Baroque előadásában, 2009. május 15-én és 16-án, a Texas állambeli Houstonban (Nicolas Sceaux szedésével).
- Zenekari tételek Rameau Hippolyte et Aricie c. operájából a manhattani St. James’s Churchben, 2009. május 8-án Frederick Renz és együttese, az Early Music New York előadásában (Nicolas Sceaux szedésével).

### Kiadók

- Mutopia Project: több, mint 1500 klasszikus zenemű szabadon letölthető kottájával a LilyPonddal szedett kották online tárháza.
- Adoro Music Publishing: egyházi zeneművek kiadója, közvetlenül letölthető vagy papíron megrendelhető, rendkívül jó minőségű kottákkal.
- The Shady Lane Publishing: egy kis kottakiadó, melynek célja, hogy a kottakiadás gazdasági rendszerének egy új formáját hozza közelebb a zenészekhez és zenekedvelőkhöz.

### Hogyan tovább?

Még mindig nem vagy meggyőzve? Olvasd el felhasználóink ajánlásait! Ha úgy döntöttél, hogy használni szeretnéd a LilyPondot, először olvasd el a tudnivalókat a szöveges bevitelről.

## Ajánlások

#### Carter Brey, cselló szólamvezető, New York-i Filharmonikusok

„...Írtam pár virtuóz szólócsellóművet. Ezeket kinyomtattam LilyPonddal, és el fogom küldeni őket a Schirmer kiadónak publikálásra. Fogadjunk, hogy az általuk szedett verzió fele olyan szép sem lesz, mint az enyém!”

#### Orm Finnendahl, zeneszerzés professzor, Musikhochschule Freiburg

„Bár még nem ismerem [a LilyPondot] túlságosan, már most nagyon le vagyok nyűgözve. Nemrég Josquin Desprez egy motettáját nyomtattam ki vele menzurális notációban, és kétségem sincs afelől, hogy a LilyPond messze felülmúl minden más kottaszedő programot sebesség, könnyű használat és kinézet terén!”

#### Darius Blasband, zeneszerző (Brüsszel, Belgium)

„[Az első zenekari próba után] számos dícséretet kaptam a kotta minőségével kapcsolatban. Ami a legfontosabb, hogy a LilyPond (bár számos módon hangolhatjuk vele a kotta kinézetét) olyan kottát produkált, amit gyakorlatilag módosítás, kézi szerkesztés nélkül adtam oda a zenekarnak.”

#### Kieren MacMillan, zeneszerző (Toronto, Canada)

„Köszönet és hála a fejlesztőcsapatnak a hihetetlen munkáért. Még nem láttam bármit is, ami akár csak megközelítené a LilyPonddal szedett kotta kinézetét. Bizalommal mondhatom, hogy ez a nagyszerű alkalmazás messze felülmúlja az igényeimet. [...] A LilyPond módosítatlan kimenete [...] már önmagában jobban néz ki, mint az ún. "professzionális" kiadások. [...]”

„Ezt múld felül, Finale/Sibelius/Igor/akármi!!!”

#### Graham Percival, zeneszerző-palánta és csellótanár

„Itt az ideje, hogy a LilyPond a rivaldafényben álljon; már két éve használom az egyetemen a zeneszerzés órákon, így megspórolva többszáz dollárt (vagy mennyibe is kerülnek a Finale vagy Sibelius "olcsó", iskolai verziói). És többen kiáltottak már fel: "Aszta! Hogy vetted rá a Finalét, hogy ilyen gyönyörű kottaképet kapj?"”

#### Chris Cannam, a RoseGarden projekt fő fejlesztője

„A LilyPond egyértelműen nehézsúlyú bajnok [a professzionális kottaszedésben].”

#### David Bobroff, basszusharsona, Izlandi Szimfonikus Zenekar

„Nagyszerűnek tartom a LilyPondot. [...] Minél többet tanulok róla, annál jobban szeretem!”

#### Vaylor Trucks, elektromos gitárművész (igen, ő az)

„Nagy hatást tett rám a LilyPond. [...]”

„EZ A VILÁG LEGJOBB PROGRAMJA!!! ”

„EZER köszönet a beléje fektetett sok kemény munkáért!”

#### Nicolas Sceaux, Mutopia közreműködő

„Ambivalens érzéseim voltak vele szemben. A pozitív érzést az jelentette, amikor megláttam az első vele készült kottát, mert egyszerűen bámulatos volt! A LilyPondot gyönyörűnek mondani enyhe kifejezés! [...] Ahogy a LilyPond egyre jobb lesz, és ahogy én egyre többet tudok meg a Scheme-ről, egyre kevesebb frusztrációt érzek vele kapcsolatban. Mindent egybevetve: köszönöm a LilyPondot, szerintem nagyon jó.”

#### Werner Lemberg, a koblenzi opera karmestere és kiváló GNU coder

„Egyébként a LilyPond kiválóan teszi a dolgát!”

#### Paul Davis, a JACK és az Ardour fejlesztője

„Véleményem szerint [a LilyPond] egy hihetetlen program, a kimenet egyszerűen csodálatos. Amikor tavaly olvastam róla egy interjúban, lelkendezve meséltem a barátaimnak, mikre képes.”

### Hogyan tovább?

Olvasd el a tudnivalókat a szöveges bevitelről.

## Szöveges bevitel

### A LilyPond működése

(Kattints a képre a nagyításhoz)

A LilyPond parancssori program: meg kell adni neki egy szöveges fájlt, ami a zene leírását tartalmazza. Az eredményül kapott kotta képernyőn megtekinthető vagy kinyomtatható.

A kotta beírása nem grafikus felhasználói felületen történik, hanem a zene szöveges formájának begépelésével. Ezt a szöveget aztán „lefordítja” a LilyPond, azaz gyönyörűen szedett kottává alakítja.

A grafikus felületekhez szokott felhasználók részéről ez másfajta gondolkodásmódot igényel, de az eredmény mindenképpen megéri a beléje fektetett munkát!

Figyelem: Itt gyorsan áttekintjük a szöveges bevitel alapjait – ez messze nem olyan bonyolult, mint amilyennek hangzik! Nem baj, ha nem érted az alábbi példák minden egyes részletét; a tankönyv mindent részletesen, fokozatosan haladva elmagyaráz.

#### Egyszerű, mint az ABC

A hangok betűkkel és számokkal írhatók le. A speciális parancsok a \ karakterrel kezdődnek.

Módosított hangokat a hangnevek módosításával lehet elérni: a keresztes hang neve után -is, a bés hang neve után -es írandó. (Más nyelveknek megfelelő jelölések is alkalmazhatóak.) A LilyPond kitalálja, hova rakjon módosítójelet.

#### Popzene

Könnyen írhatsz dalszöveget és akkordokat a dallam mellé:

#### Zenekari művek

A bemeneti fájl a mű összes hangját tartalmazza. A partitúra és a szólamkották egyetlen forrásból származnak. Így a változások mind a partitúrában, mind az egyes szólamokban tükröződnek. A szólamok hangjainak újrafelhasználásához el kell nevezni őket:

Az így létrejött változóra később lehet hivatkozni (akár transzponálva és összevonva a többütemes szüneteket, mint itt):

Ugyanazt a változót használhatjuk a partitúrában (ez alkalommal hangzó magasságban):

#### Tankönyv

Tisztában vagyunk vele, hogy sok felhasználónak szokatlan lehet a szöveges bevitel. Ezért a tankönyvben alapos segítséget nyújtunk az újdonsült felhasználóknak.

A kevésbé tapasztalt felhasználók néha azt hiszik, hogy a LilyPond hibás, miközben valójában tökéletesen működik. Addig ne jelents be hibát, amíg végig nem olvastad a tankönyvet, és meg nem bizonyosodtál arról, hogy valóban hibára bukkantál!

#### Könnyebb szerkesztés

A LilyPond elsődleges profilja a csúcsminőségű kottaszedés. A grafikus felhasználói felület fejlesztése másodlagos, nehogy szem elől tévesszük a fő célt. Mindazonáltal léteznek olyan projektek, amelyek azt a célt szolgálják, hogy a LilyPond forrásfájlok létrehozása és karbantartása egyszerűbb legyen.

Ezekbe az eszközökbe tipikusan szintaxiskiemelés, automatikus parancskiegészítés és sok előre gyártott sablon van beépítve. Más programok valamilyen szinten pótolják a grafikus felhasználói felületet, és lehetővé teszik a kotta vizuális szerkesztését. Ezekről a Könnyebb bevitel c. szakaszban olvashatsz.

### Hogyan tovább?

Most már készen állsz a LilyPond letöltésére.

Még mindig nem vagy meggyőzve? Tudd meg, hogyan lehet egyszerűbben szerkeszteni a LilyPond fájlokat erre specializálódott szerkesztőprogramokkal!

## Könnyebb bevitel

### LilyPondTool

(Kattints a képre a nagyításhoz)

http://lilypondtool.organum.hu

A magyar fejlesztésű LilyPondTool a jEdit szövegszerkesztő bővítménye, és a legtöbbet tudó integrált LilyPond-környezet. Sokrétű funkciói közül megemlítendő a beépített PDF-nézegető, mely támogatja a kottáról forráskódra és visszafelé történő ugrást, ill. a kottaelemek grafikus pozicionálását; az Új kotta varázsló, amely megkönnyíti nagy művek létrehozását; valamint az automatikus elválasztás dalszövegek gyors begépeléséhez.

### Frescobaldi

(Kattints a képre a nagyításhoz)

http://www.frescobaldi.org

A Frescobaldi egy dedikált LilyPond-szerkesztő beépített PDF-előnézettel, jól konfigurálható Új kotta varázslóval és sok szerkesztési funkcióval. A KDE4 könyvtárakat használja, így minden Linuxon és UNIX-szerű operációs rendszeren fut.

### Denemo

(Kattints a képre a nagyításhoz)

http://denemo.org

A Denemo egy grafikus szerkesztő, amely LilyPond forrásfájlokat generál, és le is játssza a beírt kottát. Jelenleg fejlesztés alatt áll, és a LilyPond régebbi verziójának formátumát használja. Szerkesztés közben párhuzomosan mutatja a kottát és a LilyPond forrást.

### Emacs és Vim

http://www.geoffhorton.com/lilymacs.html

Az Emacs egy szövegszerkesztő, mely sok programnyelv-specifikus képességgel bír. Az Emacs rugalmasan bővíthető, és így integrált fejlesztőkörnyezetként is szolgálhat. Létezik hozzá egy ‘lilypond mód’, amely LilyPond forrásfájlok szerkesztését megkönnyítő funkciókat tartalmaz.

A Vim egy minimalista szövegszerkesztő, a régi Unixos `vi` szerkesztő továbbfejlesztett változata. Szintén nagyon jól bővíthető és konfigurálható.

Amennyiben még nem vagy járatos az Emacs vagy a Vim használatában, inkább azt ajánljuk, más programot használj a LilyPond fájlok szerkesztéséhez.

### Egyéb

#### LilyKDE

(Kattints a képre a nagyításhoz)

http://lilykde.googlecode.com/

A LilyKDE a Kate KDE-s szövegszerkesztő egy beépülő modulja.

A Rumort használja, így a kotta bevitele MIDI-billentyűzetről is lehetséges.

Hasznos funkciója többek között, hogy a KDE fájlkezelőjéből több fájlt le lehet fordítani egyszerre a segítségével.

#### TexShop

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

A Mac OS X alá írt TexShop szerkesztő a http://www.dimi.uniud.it/vitacolo/freesoftware.html#desktoppub címen található kiterjesztésekkel képes futtatni a LilyPondot, valamint a `lilypond-book` és a `convert-ly` segédprogramokat.

### A LilyPond formátumába exportáló programok

#### Grafikus kottaszerkesztők:

- NoteEdit
- Rosegarden
- NtEd
- TuxGuitar
- MuseScore
- Canorus

#### Parancssori eszközök:

- Rumor, amely az egyszólamú MIDI bemenetet valós időben LilyPond bemenetté konvertálja
- lyqi, egy Emacs mód
- xml2ly, amely MusicXML-LilyPond konverzióra képes
- FOMUS, egy LISP könyvtár, amellyel kottát lehet generálni

### Hogyan tovább?

Most már készen állsz a LilyPond letöltésére.

Még mindig nem vagy meggyőzve? Számos zeneszerző, előadó és karmester könnyen elsajátította a LilyPond nyelvét. A tapasztalt felhasználók bizonyos esetekben gyorsabban begépelnek LilyPonddal egy kottát, mint MIDI billentyűzettel vagy egy grafikus kottaszerkesztővel! Esetleg nézd meg, mit tud a LilyPond, milyen gyönyörű kottákat szed, milyen szabadságot ad, vagy olvasd el felhasználóink ajánlásait. Ezenkívül a számítógéppel történő kottaszedés esztétikájának hátteréről is olvashatsz.

### Jogi tudnivalók

Minden logó és termékábrázolás szerzői joggal védett.

Tux, a Linux pingvin lewing@isc.tamu.edu műve, és a GNU Image Manipulation Program segítségével készült.

A FreeBSD logó a FreeBSD Alapítvány bejegyzett védjegye.

Az „X-et ábrázoló kép” nem bejegyzett védjegy. Nihonjoe és CyberSkull műve, a GNU Free Documentation License (GNU Szabad Dokumentációs Licenc) 1.2-es verziója vonatkozik rá. A kép forrása ez a Wikipedia Commons oldal.

A „négyszínű ablakot ábrázoló kép” nem bejegyzett védjegy. Rohitbd műve és a GNU Free Documentation License (GNU Szabad Dokumentációs Licenc) 1.2-es verziója vonatkozik rá. A kép forrása ez a Wikipedia Commons oldal.

# Letöltés

## A LilyPond 2.14.1 letöltése

Figyelem: A LilyPond egy szöveges alapú kottaszedő program, nem egy grafikus kottaszerkesztő. Mielőtt letöltenéd a LilyPondot, olvasd el a tudnivalókat a Szöveges bevitelről.

### Felhasználóknak

- Unix (Linux és FreeBSD)
- Mac OS X
- Microsoft Windows

### Fejlesztőknek

- Forrás: csomagkészítőknek
- Régi verziók: az idejétmúlt változatok archívuma
- Fejlesztés: a legfrissebb fejlesztői verzió

### Licenc

A LilyPond licence a GNU General Public License.

### Támogatók

Köszönet a Virgina Tech és a linuxaudio.org részére a sávszélesség költségeinek fedezéséért.

### Jogi tudnivalók

Minden logó és termékábrázolás szerzői joggal védett.

Tux, a Linux pingvin lewing@isc.tamu.edu műve, és a GNU Image Manipulation Program segítségével készült.

A FreeBSD logó a FreeBSD Alapítvány bejegyzett védjegye.

Az „X-et ábrázoló kép” nem bejegyzett védjegy. Nihonjoe és CyberSkull műve, a GNU Free Documentation License (GNU Szabad Dokumentációs Licenc) 1.2-es verziója vonatkozik rá. A kép forrása ez a Wikipedia Commons oldal.

A „négyszínű ablakot ábrázoló kép” nem bejegyzett védjegy. Rohitbd műve és a GNU Free Documentation License (GNU Szabad Dokumentációs Licenc) 1.2-es verziója vonatkozik rá. A kép forrása ez a Wikipedia Commons oldal.

## Unix

### Generikus vagy disztribúció-specifikus csomagokat használjak?

Sok disztribúció csomagkezelőjében megtalálható a LilyPond. Ezeket a verziókat egyszerűbb telepíteni és eltávolítani, mint a generikus csomagokat, de régebbiek lehetnek. Ha egy generikus csomagot akarsz használni, előbb távolítsd el a csomag hivatalos verzióját a csomagkezelővel. Ehhez a disztribúció csomagkezelőjének dokumentációja nyújt segítséget.

### Generikus csomagok

#### Letöltés

- Linux x86: LilyPond 2.14.1-1 (ha bizonytalan vagy afelől, hogy melyiket töltsd le, ezt válaszd)
- Linux 64: LilyPond 2.14.1-1
- Linux PPC: LilyPond 2.14.1-1
- FreeBSD i386: LilyPond 2.14.1-1
- FreeBSD amd64: LilyPond 2.14.1-1

#### Telepítés

Add ki a következő parancsokat:

>     cd PATH-TO-DOWNLOAD-DIRECTORY
>     sh lilypond-2.14.1-OS-TYPE.sh

#### Eltávolítás

Add ki a következő parancsot:

>     uninstall-lilypond

### Disztribúció-specifikus csomagok

Ezeket a csomagokat a disztribúciód csomagkezelőjével tudod telepíteni.

- Fedora: LilyPond 2.12.0
- Ubuntu: LilyPond 2.12.1
- Slackware: LilyPond 2.12.1
- Debian: LilyPond 2.10.33
- openSUSE: LilyPond 2.10.33

### Jogi tudnivalók

Minden logó és termékábrázolás szerzői joggal védett.

Tux, a Linux pingvin lewing@isc.tamu.edu műve, és a GNU Image Manipulation Program segítségével készült.

A FreeBSD logó a FreeBSD Alapítvány bejegyzett védjegye.

## Mac OS X

### Csomagok

#### Letöltés

- MacOS X x86: LilyPond 2.14.1-1 Intel processzorokra (ha bizonytalan vagy afelől, hogy melyiket töltsd le, ezt válaszd)
- MacOS X PPC: LilyPond 2.14.1-1 G3 és G4 processzorokra (régi Apple gépekben találhatóak)

#### Telepítés

Csak kattints duplán a letöltött fájlra a kitömörítéséhez, majd a kicsomagolt LilyPond.app alkalmazást húzd be az Applications könyvtárba.

#### Eltávolítás

Töröld a LilyPond.app alkalmazást.

### Parancssori futtatás

Figyelem: Ha a grafikus felület megfelel, ezeket az utasításokat nyugodtan figyelmen kívül hagyhatod.

Írd be a könyvtáradban található ‘`.profile`’ fájlba a következő sort:

>     export PATH=/Applications/LilyPond.app/Contents/Resources/bin:$PATH

### Jogi tudnivalók

Minden logó és termékábrázolás szerzői joggal védett.

Az „X-et ábrázoló kép” nem bejegyzett védjegy. Nihonjoe és CyberSkull műve, a GNU Free Documentation License (GNU Szabad Dokumentációs Licenc) 1.2-es verziója vonatkozik rá. A kép forrása ez a Wikipedia Commons oldal.

## Windows

### Csomagok

#### Letöltés

- Windows: LilyPond 2.14.1-1 Támogatott verziók: Windows ME, NT, 2000, XP, Vista és Windows 7

#### Telepítés

1. Kattintsd duplán a letöltött fájlra a telepítő elindításához. Amennyiben figyelmeztetést kapsz a fájl futtatásával kapcsolatban, válaszd a futtatást.
2. Ezután olvasd el figyelmesen a licencszerződést, és ha elfogadod, kattints a Tovább gombra.
3. A célkönyvtárat ajánlott az alapértelmezetten hagyni. Amennyiben mégis máshová akarod telepíteni a LilyPondot, válassz egy könyvtárat, és kattints a Tovább gombra.
4. A következő oldalon hagyd mindhárom opciót bekapcsolva, mert mindhárom komponensre szükség lesz. Kattints a Tovább gombra.
5. Megkezdődik a telepítés, amely pár percet igénybe vehet. Ha a Részletek mutatása gombra kattintasz, megláthatod, milyen fájlok és hova kerültek telepítésre, de erre az információra nem lesz szükséged. Miután a telepítés befejeződött, kattints a Befejezés gombra.
6. Sikeresen telepítetted a LilyPondot!

#### Eltávolítás

Az eltávolításnak két módja van:

1. Kattints a Start menü > LilyPond > Eltávolítás parancsikonra.
2. A Vezérlőpult > Alkalmazások telepítése és eltávolítása ablakban jelöld ki a LilyPondot, és kattints az Eltávolítás gombra.

### Jogi tudnivalók

Minden logó és termékábrázolás szerzői joggal védett.

A „négyszínű ablakot ábrázoló kép” nem bejegyzett védjegy. Rohitbd műve és a GNU Free Documentation License (GNU Szabad Dokumentációs Licenc) 1.2-es verziója vonatkozik rá. A kép forrása ez a Wikipedia Commons oldal.

## Forrás

Figyelem: Hacsak nem vagy fejlesztő, a LilyPond fordítása nem ajánlott; szinte minden végfelhasználó számára jobb, ha az előre lefordított futtatható verziót használja.

### Tarball

Forrás: lilypond-2.14.1.tar.gz

A LilyPond összes verziójának forrása ezen az oldalon található.

### Fordítási útmutató

A tudnivalók a Compiling LilyPond c. fejezetben vannak leírva.

## Régi verziók

### A régi verziók archívuma

A LilyPond összes verziója ezen az oldalon található.

## GPL

### Szoftverlicenc

A GNU LilyPond licence a GNU General Public License. A licenc választásának főbb előnyeit a Szabadság c. szakasz ismerteti.

### 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

1. 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.

2. 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.

3. 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.

4. 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.

5. 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.

6. 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:

   1. The work must carry prominent notices stating that you modified it, and giving a relevant date.
   2. 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”.
   3. 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.
   4. 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.

7. 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:

   1. 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.
   2. 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.
   3. 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.
   4. 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.
   5. 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.

8. 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:

   1. Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or
   2. 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
   3. 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
   4. Limiting the use for publicity purposes of names of licensors or authors of the material; or
   5. Declining to grant rights under trademark law for use of some trade names, trademarks, or service marks; or
   6. 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.

9. 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.

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.

11. 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.

12. 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.

13. 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.

14. 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.

15. 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.

16. 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.

17. 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.

18. 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.

# Dokumentáció

## A LilyPond 2.14.2 dokumentációja

### Bevezetés

- Szöveges bevitel: A LilyPond egy szöveges alapú kottaszedő program. Ha nem vagy tisztában ennek a fogalmával, akkor előbb ezt olvasd el!
- Tankönyv: Bevezetés a LilyPond használatába lépésről lépésre. (Tankönyv részletei)
- Fogalomtár: (opcionális) Zenei fogalmak gyűjteménye több nyelven. (Fogalomtár részletei)
- Esszé: (opcionális) Háttérinformáció a kottaszedés folyamatáról és a 19. századi kottaszedés esztétikai elveiről. (Esszé részletei)

### Mindennapi használat

- Kottaírás: A dokumentáció törzsanyaga; részletesen bemutatja a különböző kottaelemek beviteli módját. (Kottaírás részletei)
- Használat: Bemutatja a alkalmazás parancssori használatát, ügyelve a különböző operációs rendszerek közötti különbségekre. (Használat részletei)
- Kódrészletek: Hasznos példák, tippek, trükkök. (Kódrészletek részletei)

### Speciális használat

- GYIK: Gyakran Ismételt Kérdések.
- Web: A weboldal.
- Változások: A legutóbbi verzióváltás óta történt változások. (Változások részletei)
- Bővítés: A LilyPond képességeinek kiterjesztése. (Bővítés részletei)
- Belső működés: A LilyPond belső szerkezetének referenciája. A kimenet finomhangolásához szükséges. (Belső működés részletei)

### Egyéb anyagok

- Honosítás: A honosítás állapota.
- Teljes dokumentáció: Gyorslinkek a dokumentáció különböző részeihez, letölthető változataihoz és régi verzióihoz.
- Fejlesztés: Dokumentáció fejlesztőknek.
- FDL: A dokumentáció licence, a GNU Free Documentation License.

## Tankönyv

A tankönyv fokozatosan bevezet a LilyPond használatába, és közérthetően elmagyarázza az ehhez szükséges alapfogalmakat. Fejezeteit lineárisan, az elejétől a végéig érdemes olvasni.

A tankönyv minden szakaszának végén található egy Lásd még bekezdés is, mely más szakaszokra mutató kereszthivatkozásokat tartalmaz: ezeket első olvasásra nem praktikus követni, csak az egész tankönyv elolvasása után, az összefüggések meglátása végett.

### Olvasd el

- Tankönyv (HTML oldalak) - megtekintés sok HTML oldalra elosztva.
  (oldalanként egy-egy kis letöltés)
- Tankönyv (egy nagy HTML oldal) - megtekintés egy nagy HTML oldalként.
  (egyszeri, nagy letöltés, 1.5 MB)
- learning.pdf - letöltés PDF formátumban.
  (egyszeri, nagy letöltés, 3 MB)

## Fogalomtár

A fogalomtár zenei fogalmak definícióját és honosításait tartalmazza. Ha egy fogalommal nem vagy tisztában, vagy egy kifejezés angol nyelvű megfelelőjére vagy kíváncsi, érdemes megnézni a fogalomtárban.

### Olvasd el

- Fogalomtár (HTML oldalak) - megtekintés sok HTML oldalra elosztva.
  (oldalanként egy-egy kis letöltés)
- Fogalomtár (egy nagy HTML oldal) - megtekintés egy nagy HTML oldalként.
  (egyszeri, nagy letöltés, 1 MB)
- music-glossary.pdf - letöltés PDF formátumban.
  (egyszeri, nagy letöltés, 1.5 MB)

## Esszé

Az esszé rövid áttekintést nyújt a kottaszedés történelméről, majd felületesen bemutatja a LilyPond szedési technikáit, összehasonlítva az eredményt más kottaszedő programok kimenetével.

Figyelem: A kottapéldák nagy felbontásuk miatt a PDF változatban élvezhetőek leginkább.

### Olvasd el

- Esszé (HTML oldalak) - megtekintés sok HTML oldalra elosztva.
  (oldalanként egy-egy kis letöltés)
- Esszé (egy nagy HTML oldal) - megtekintés egy nagy HTML oldalként.
  (egyszeri, nagy letöltés, 2 MB)
- essay.pdf - letöltés PDF formátumban.
  (egyszeri, nagy letöltés, 2.5 MB)

## Kottaírás

### A kottaírás kézikönyve

Ez a kézikönyv minden kottaelemhez tartozó LilyPond parancs megadási módját ismerteti.

Figyelem: A kottaírás kézikönyve feltételezi, hogy az olvasó birtokában van a Tankönyvben leírt alapismereteknek, és ismeri a zenei kifejezések angol megfelelőjét, melyek a Fogalomtárban vannak leírva.

### Olvasd el

- Kottaírás (HTML oldalak) - megtekintés sok HTML oldalra elosztva.
  (oldalanként egy-egy kis letöltés)
- Kottaírás (egy nagy HTML oldal) - megtekintés egy nagy HTML oldalként.
  (egyszeri, nagy letöltés, 7 MB)
- notation.pdf - letöltés PDF formátumban.
  (egyszeri, nagy letöltés, 18 MB)

## Használat

### Az alkalmazás használata

Ez a kézikönyv bemutatja, hogyan kell futtatni a LilyPondot és a hozzá tartozó segédprogramokat, hogyan integrálható a LilyPonddal szedett kotta más dokumentumszedő programokkal készített dokumentumokba, és a gyakorlatban jól bevált módszereket ismertet a hatékony használathoz. Ajánlott elolvasni, mielőtt nagy művek bevitelébe kezd az ember.

### Olvasd el

- Használat (HTML oldalak) - megtekintés sok HTML oldalra elosztva.
  (oldalanként egy-egy kis letöltés)
- Használat (egy nagy HTML oldal) - megtekintés egy nagy HTML oldalként.
  (egyszeri, nagy letöltés, 300 KB)
- usage.pdf - letöltés PDF formátumban.
  (egyszeri, nagy letöltés, 400 KB)

## Kódrészletek

Ez egy válogatás a LilyPond Kódrészletek Tárházából. Minden kódrészlet közkincs.

A kottaírás kézikönyvének megfelelő szakaszaiban is találhatóak ilyenek a Válogatott kódrészletek c. bekezdésekben.

### Olvasd el

- Kódrészletek (HTML oldalak) - megtekintés sok HTML oldalra elosztva.
  (oldalanként egy-egy kis letöltés)
- Kódrészletek (egy nagy HTML oldal) - megtekintés egy nagy HTML oldalként.
  (egyszeri, nagy letöltés, 2.5 MB)
- snippets.pdf - letöltés PDF formátumban.
  (egyszeri, nagy letöltés, 8 MB)

## GYIK

### Általános kérdések

#### Hol a grafikus felület?

A LilyPond számára a zenét egy szöveges fájlban kell leírni, amit feldolgoz. Olvasd el a Szöveges bevitelről szóló szakaszt.

#### Nagyon sok dokumentáció van! Mindet el kell olvasni?

Csak a Tankönyv az, amit teljes egészében ajánlott elolvasni. Később a dokumentációból csak azokat a részeket kell elolvasni, amelyek a begépelni kívánt kottaelemhez szükségesek.

#### Ez még mindig túl sok olvasnivaló! Megéri mindezt megtanulni?

Ezt döntsd el a saját szempontjaid szerint; az előnyök, amik miatt megtérülhet a befektetés, a Bevezetésben vannak leírva.

### Kérdések a használattal kapcsolatban

#### Valami nem működik! Hogyan javítsam ki?

Lásd: Troubleshooting

#### Miért változik a nyelvtan?

Lásd: Miért változik a szintaxis?

## Web

A LilyPond weboldala, mely általános információkat tartalmaz a LilyPondról a felhasználók széles rétege számára, az újdonsült felhasználóktól a fejlesztőkig.

### Olvasd el

#### Legutóbbi verzió

- Web

#### 2.15.1

- Web (HTML oldalak) - megtekintés sok HTML oldalra elosztva.
  (oldalanként egy-egy kis letöltés)
- Web (egy nagy HTML oldal) - megtekintés egy nagy HTML oldalként.
  (egyszeri, nagy letöltés, 1 MB)
- web.pdf - letöltés PDF formátumban.
  (egyszeri, nagy letöltés, 2 MB)

## Változások

Összefoglaló az új funkciókról és a LilyPond nyelvének változásairól az előző stabil verzió óta.

### Olvasd el

- Változások (HTML oldalak) - megtekintés sok HTML oldalra elosztva.
  (oldalanként egy-egy kis letöltés)
- Változások (egy nagy HTML oldal) - megtekintés egy nagy HTML oldalként.
  (egyszeri, nagy letöltés, 6 KB)
- changes.pdf - letöltés PDF formátumban.
  (egyszeri, nagy letöltés, 200 KB)

## Bővítés

### A LilyPond bővítése

Ez a kézikönyv azt írja le, hogyan lehet a LilyPond képességeit kiterjeszteni Scheme nyelven írt bővítményekkel.

### Olvasd el

- Bővítés (HTML oldalak) - megtekintés sok HTML oldalra elosztva.
  (oldalanként egy-egy kis letöltés)
- Bővítés (egy nagy HTML oldal) - megtekintés egy nagy HTML oldalként.
  (egyszeri, nagy letöltés, 200 KB)
- extending.pdf - letöltés PDF formátumban.
  (egyszeri, nagy letöltés, 400 KB)

## Belső működés

### A belső működés referenciája

Ez a referencia a LilyPond által használt osztályok, függvények és tulajdonságok összes adatát tartalmazza. A felhasználó ezek mindegyikét finomhangolhatja. Ha egy kottaelemet az alapbeállítástól eltérően szeretnél formázni, ebben a listában érdemes megkeresni az adott tulajdonság nevét.

### Olvasd el

- Belső működés (HTML oldalak) - megtekintés sok HTML oldalra elosztva.
  (oldalanként egy-egy kis letöltés)
- Belső működés (egy nagy HTML oldal) - megtekintés egy nagy HTML oldalként.
  (egyszeri, nagy letöltés, 2.5 MB)
- internals.pdf - letöltés PDF formátumban.
  (egyszeri, nagy letöltés, 2.8 MB)

## Honosítás

### A honosítások állapota

Last updated Thu Mar 24 14:52:33 UTC 2011

LilyPond Tankönyv | Translators | Translation checkers | Translated | Up to date | Other info
--- | --- | --- | --- | --- | ---
Section titles 124 | Harmath Dénes |  | yes | partially | pre-GDP
LilyPond — \TITLE\ 1139 | Harmath Dénes |  | yes | partially | pre-GDP
1 Első lecke 2535 | Harmath Dénes |  | partially (80 %) | partially | pre-GDP
2 Elemi kottaírás 4184 | Harmath Dénes |  | yes | partially | pre-GDP
3 Alapfogalmak 11139 | Harmath Dénes |  | yes | partially | pre-GDP
4 A kimenet finomhangolása 15408 | Harmath Dénes |  | no | partially | pre-GDP
A Sablonok 225 | Harmath Dénes |  | no | partially | pre-GDP

LilyPond Használati útmutató | Translators | Translation checkers | Translated | Up to date | Other info
--- | --- | --- | --- | --- | ---
Section titles 135 | Team-hu |  | yes | partially | pre-GDP
LilyPond — \TITLE\ 1139 | Team-hu |  | yes | partially | pre-GDP
1 A `lilypond` használata 3622 | Team-hu |  | partially (96 %) | partially | pre-GDP
2 A `convert-ly` használata 1189 | Team-hu |  | yes | partially | pre-GDP

LilyPond – kottaszedés mindenkinek | Translators | Translation checkers | Translated | Up to date | Other info
--- | --- | --- | --- | --- | ---
Section titles 585 | Harmath Dénes |  | yes | yes | pre-GDP
LilyPond — \TITLE\ 1139 | Harmath Dénes |  | yes | partially | pre-GDP
Bevezetés 4506 | Harmath Dénes |  | yes | yes | pre-GDP
Letöltés 1183 | Harmath Dénes |  | yes | yes | pre-GDP
Dokumentáció 1200 | Harmath Dénes |  | yes | yes | pre-GDP
Közösség 1755 | Harmath Dénes |  | yes | yes | pre-GDP

## Teljes dokumentáció

### Letölthető változatok

A csomagok letölthetőek a http://lilypond.org weboldalról.

### Előző stabil verziók

- 2.12
- 2.11
- 2.10
- 2.8
- 2.6
- 2.4
- 2.2
- 2.0
- 1.8
- 1.6

## FDL

### Dokumentációs licenc

A GNU LilyPond dokumentációjának licence a GNU Free Documentation License. A licenc választásának főbb előnyeit a Szabadság c. szakasz ismerteti.

### 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.

1. 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.

2. 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.

3. 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.

4. 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.

5. 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:

   1. 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.
   2. 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.
   3. State on the Title page the name of the publisher of the Modified Version, as the publisher.
   4. Preserve all the copyright notices of the Document.
   5. Add an appropriate copyright notice for your modifications adjacent to the other copyright notices.
   6. 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.
   7. Preserve in that license notice the full lists of Invariant Sections and required Cover Texts given in the Document’s license notice.
   8. Include an unaltered copy of this License.
   9. 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.
   10. 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.
   11. 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.
   12. 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.
   13. Delete any section Entitled “Endorsements”. Such a section may not be included in the Modified Version.
   14. Do not retitle any existing section to be Entitled “Endorsements” or to conflict in title with any Invariant Section.
   15. 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.

6. 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.”

7. 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.

8. 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.

9. 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.

10. 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.

11. 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.

12. 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.

# Közösség

### Kommunikáció a közösséggel

- Kapcsolat: Kérj segítséget, tegyél fel kérdéseket, és segíts másoknak!
- Minimális példák: Amikor egy zenei jelenségről van szó, ha csak lehet, minimális példákat kell bemutatni.
- Hibajelentés: Mi a teendő, ha valami nem működik?

### A LilyPond jobbá tétele

- Közreműködés: A Te segítségedre van szükségünk!
- Fejlesztés: Anyagok fejlesztők és tesztelők számára.
- Készítők: Azoknak az embereknek a listája, akik segítettek abban, hogy a LilyPond mára azzá legyen, ami.

### Egyéb

- Publikációk: Írások, amiket mi írtunk, vagy rólunk írtak.
- Hírarchívum: A régebbi hírek archívuma.

## Kapcsolat

### A felhasználók fórumai

#### Felhasználói levelezőlista: `lilypond-user@gnu.org`

Ezen a levelezőlistán a felhasználók segítséget kérhetnek egymástól és nyújthatnak egymásnak.

> feliratkozás és információ

> 1. archívum 2. archívum 3. archívum

> webes hozzászólás

Figyelem: Amikor kérdéseket teszel föl, Minimális példákat használj!

#### IRC

Bizonyos szintű támogatást nyújtunk az IRC csatornánkon keresztül:

>     #lilypond@irc.freenode.net

Ennek a csatornának nincs publikus archívuma, így ha olyan kérdésed van, amely hasznos lehet mások számára is, inkább a levelezőlistára írd.

IRC név:

#### Más nyelveken

> Magyar LilyPond-felhasználók közössége

> Spanyol LilyPond-felhasználók közössége

> Német LilyPond-felhasználók közössége

> Portugál LilyPond-felhasználók közössége

> Francia LilyPond-felhasználók közössége

> Holland LilyPond-felhasználók közössége

### Kövesd a fejlesztést!

#### LilyPond hírlevél

Közösségi hírlevelünket olvasva nyomon követheted a program fejlődését: LilyPond hírlevél.

#### Értesítés a kiadott verziókról: `info-lilypond@gnu.org`

Ez a levelezőlista egy alacsony forgalmú, csak olvasható lista, melyen értesítünk az új verziókról.

> feliratkozás és információ

> 1. archívum 2. archívum 3. archívum

### A fejlesztők fórumai

#### Fejlesztői levelezőlista: `lilypond-devel@gnu.org`

A fejlesztők itt tárgyalják meg a vitás kérdéseket, és ide kell küldeni a patcheket is.

> feliratkozás és információ

> 1. archívum 2. archívum 3. archívum

> webes hozzászólás

#### Hibabejelentő levelezőlista: `bug-lilypond@gnu.org`

A hibákat ezen a listán kell bejelenteni.

> feliratkozás és információ

> 1. archívum 2. archívum 3. archívum

Figyelem: Mielőtt bejelentenél egy hibát, olvasd el a tudnivalókat a Hibajelentésről.

## Minimális példák

### Mik azok a „minimális példák”?

A minimális példa egy olyan LilyPond példaforrás, amelyből semmit nem lehet elvenni.

### Miért kellenek a minimális példák?

- Minél egyszerűbb a példa, annál gyorsabban tudják mások megérteni és segíteni neked.
- A minimális példán látszik, hogy már te magad is tettel lépéseket a probléma megoldása felé. Ezt látván mások jobban motiváltak, hogy segítsenek.
- Egy minimális példa létrehozása kényszerít arra, hogy megértsd, mi is történik valójában. Számos téves hibajelentés elkerülhető, ha az ember megpróbál létrehozni egy minimális példát; ha egy hibát nem sikerül reprodukálni egy minimális példával, akkor a hiba valószínűleg nem a LilyPond helytelen működéséből, hanem a megértés hiányából fakad.

### Milyen egy jó minimális példa?

- Tartalmazza a verziószámot (\version).
- Rövid. A legtöbb hiba egyetlenegy ütemmel reprodukálható. Az oldalak elrendezésével kapcsolatos hibák esetleg sok ütemet igényelhetnek, de ezek is elérhetőek rövid forráskóddal.
- Ha nem vagy biztos abban, hogy egy rész szükséges-e, kommentezd ki (a `%` vagy `%{ … %}` jelek használatával). Ha a lényeg ezután sem változik, nyugodtan kitörölheted a kikommentezett részt.
- Kerüld a bonyolult konstrukciók (akkordok, előjegyzés, ütemmutató stb.) használatát, hacsaknem ezekben van a hiba.
- Ne használj finomhangolásokat (`\override`, `\set`), hacsaknem ezek a hibásak.

## Hibajelentés

### 1. lépés: Ismert hibák

Ha egy adott bemenetre a LilyPond elszáll, vagy hibás kimenetet ad, akkor hibával állunk szemben. Az ismert hibák listája a következő oldalon található:

>     http://code.google.com/p/lilypond/issues/list

Figyelem: Ide TILOS új hibákat bejelenteni, a hibajelentés a levelezőlistán történik. Miután a hiba bekerült a nyilvántartásba, nyugodtan kiegészítheted a jelentést a szükséges információkkal.

### 2. lépés: Hibajelentés létrehozása

Ha tényleg felfedeztél egy még nem ismert hibát, nagy segítséget jelent, ha bejelented.

Figyelem: Csakis Minimális példákat fogadunk el hibabejelentésnél. Nagyon szűkösek az erőforrásaink, amiket a hibajelentések feldolgozására fordíthatunk, így minden nem minimális példát visszautasítunk. Szinte minden hiba négy vagy kevesebb hanggal bemutatható!

Íme, egy jó példa hibajelentésre:

>     %% a set-octavation parancs
>     %% nincs hatással a kimenetre!

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

### 3. lépés: Hibajelentés elküldése

Miután megbizonyosodtál arról, hogy tényleg egy új hibáról van szó, és megírtad a hibajelentést, küldd el nekünk!

A hibajelentés elejére mindenképpen írd oda:

>     > I'm not top posting.

(a `>` karakter is fontos).

Itt küldheted be webes felületen a hibát, vagy írhatsz e-mailt a bug-lilypond@gnu.org levelezőlistára.

Amikor a jelentés megérkezett a levelezőlistára, a hibafelelős megvizsgálja azt. Esetleg kérhet tőled további információt. Ha elfogadta, nyilvántartásba veszi a hibát, és elküldi a linkjét.

A hibajelentést megjelölheted kedvencként, hogy e-mailben értesülj bármilyen tevékenységről a hibával kapcsolatban. Ehhez csak egy Google fiók szükséges.

## Közreműködés

### Rád van szükségünk!

A LilyPond fejlesztőcsapata igen kicsi, szeretnénk, ha minél több ember segítene. Kérlek, ha tetszik a LilyPond, segíts a többi felhasználónak azzal, hogy közreműködsz a fejlesztésben!

A legkisebb feladat elvégzésének is nagy hatása lehet: lehetővé teszi, hogy a tapasztalt fejlesztők ezek helyett bonyolultabb feladatokon dolgozhassanak.

### Egyszerű feladatok

- Felhasználók támogatása a levelezőlistán: ha valamelyik felhasználónak kérdése van a levelezőlistán, válaszolj neki.
- Hibajelentés: készíts jó Hibajelentéseket, vagy segíts a hibafelelősöknek a hibajelentések kezelésében.
- Dokumentáció: tegyél bármilyen javaslatot a dokumentációval kapcsolatban a Documentation suggestions c. fejezetben leírt módon.
- LilyPond Kódrészletek Tárháza: készíts hasznos kódrészleteket! Ld. a Adding and editing snippets c. fejezetet.
- Visszajelzés: a fejlesztők gyakran kérnek visszajelzést az új dokumentációról, a nyelvtan jövőbeli változásairól, vagy megkérnek, hogy tesztelj új képességeket. Ezekben is segíthetsz.

### Bonyolultabb feladatok

Figyelem: Ezek a feladatokhoz szükséges, hogy meglegyen a program és a dokumentáció forrása, de nem kell hozzájuk teljes fejlesztői környezet. Ld. a Starting with Git c. fejezetet.

- Dokumentáció: ld. Documentation work és Building documentation without compiling c. fejezeteket.
- Weboldal: a weboldal a dokumentáció része, ld. a rá vonatkozó szabályokat, ill. a Website work c. fejezetet.
- Honosítás: ld. Translating the documentation és Translating the website c. fejezeteket.

### Bonyolult feladatok

Figyelem: Ezekhez a feladatokhoz szükséges, hogy meglegyen a forráskód, és le tudd fordítani a LilyPondot. Ld. a Starting with Git és Compiling LilyPond c. fejezeteket.

Windowst használó felhasználóknak javasoljuk a lilydev virtuális gép használatát. Ld. a Lilydev c. fejezetet.

- Hibák kijavítása, új képességek megvalósítása: csatlakozz a Békákhoz, és olvasd el a Programming work c. fejezetet!

### Projektek

#### Békák

Weboldal és levelezőlista: http://frogs.lilynet.net

A Békák mindennapi LilyPond-felhasználók, akik úgy döntöttek, hogy részt vesznek kedvenc programjuk fejlesztésében. Hibajavítás, fejlesztés, a forráskód dokumentációja: nagyon sok a tennivaló, és főleg: itt a nagy lehetőség, hogy több mindent tudj meg a LilyPondról, a szabad szoftverekről, a programozásról... az alkotás öröméért. Ha kedved támadt, ne habozz: csatlakozz a Békákhoz!

## Fejlesztés

## A LilyPond 2.15.1 fejlesztőknek szóló anyagai

Figyelem: Ezek fejlesztői, kísérleti verziók. Ha nem vagy teljesen biztos abban, hogyan kell telepíteni vagy használni a LilyPondot, a stabil verzió letöltését és dokumentációját ajánljuk.

### Verziószámok

A LilyPond fejlesztése két ágon történik: stabil és fejlesztői ágon. A stabil verziók alverziószáma páros (pl. 2.8, 2.10, 2.12), míg a fejlesztői verzióké páratlan (pl. 2.7, 2.9, 2.11).

### Letöltés

A git használatáról és a LilyPond fordításáról a közreműködőknek szóló útmutatóban olvashatsz.

> Git repository

Dokumentációt író és tesztelést végző felhasználók számára a legfrissebb fejlesztői verziót ajánljuk:

> Linux x86: LilyPond 2.15.1-1

> Linux 64: LilyPond 2.15.1-1

> Linux PPC: LilyPond 2.15.1-1

> FreeBSD i386: LilyPond 2.15.1-1

> FreeBSD amd64: LilyPond 2.15.1-1

> MacOS X x86: LilyPond 2.15.1-1

> MacOS X PPC: LilyPond 2.15.1-1

> Windows: LilyPond 2.15.1-1

> Source: lilypond-2.15.1.tar.gz

### Dokumentáció

- Tankönyv:

  Tankönyv (HTML oldalak)
  Tankönyv (egy nagy HTML oldal)
  Tankönyv.pdf

- Fogalomtár:

  Fogalomtár (HTML oldalak)

  Fogalomtár (egy nagy HTML oldal)

  Fogalomtár.pdf

- Esszé:

  Esszé (HTML oldalak)

  Esszé (egy nagy HTML oldal)

  Esszé.pdf

- Kottaírás:

  Kottaírás (HTML oldalak)

  Kottaírás (egy nagy HTML oldal)

  Kottaírás.pdf

- Használat:

  Használat (HTML oldalak)

  Használat (egy nagy HTML oldal)

  Használat.pdf

- Kódrészletek:

  Kódrészletek (HTML oldalak)

  Kódrészletek (egy nagy HTML oldal)

  Kódrészletek.pdf

- Web:

  Web (HTML oldalak)

  Web (egy nagy HTML oldal)

  Web.pdf

- Változások:

  Változások (HTML oldalak)

  Változások (egy nagy HTML oldal)

  Változások.pdf

- Bővítés:

  Bővítés (HTML oldalak)

  Bővítés (egy nagy HTML oldal)

  Bővítés.pdf

- Belső működés:

  Belső működés (HTML oldalak)

  Belső működés (egy nagy HTML oldal)

  Belső működés.pdf

### Útmutató közreműködőknek

A LilyPond fejlesztése igen bonyolult feladat. A LilyPond egy nagy, (javarészt) stabil projekt. Az újdonsült közreműködők számára a rendszer stabilitása érdekében írtunk egy útmutatót.

Figyelem: Ezt a kézikönyvet nem folyamatosan kell olvasni; az új közreműködőknek csak azokat a részeket kell elolvasni, amelyek számukra fontosak. A különböző feladatokról a Közreműködés c. szakaszban olvashatsz.

- Útmutató közreműködőknek (HTML oldalak) - megtekintés sok HTML oldalra elosztva.
  (oldalanként egy-egy kis letöltés)
- Útmutató közreműködőknek (egy nagy HTML oldal) - megtekintés egy nagy HTML oldalként.
  (egyszeri, nagy letöltés, 500 kB)
- contributor.pdf - letöltés PDF formátumban.
  (egyszeri, nagy letöltés, 2.8 MB)

### Regressziós tesztek

- Regressziós tesztek: A kottaszedés tesztjei. (PDF formátumban)
- MusicXML tesztek: A MusicXML konverzió tesztjei. (PDF formátumban)
- abc2ly tesztek: Az abc2ly konverzió tesztjei. (PDF formátumban)
- lilypond-book tesztek: A lilypond-book tesztjei. (PDF formátumban)

#### Minden verzió

- Összehasonlítás
- Archívum

## Készítők

### Jelenlegi fejlesztők

- Trevor Daniels: t.daniels@treda.co.uk, Assistant documentation editor
- Reinhold Kainhofer: reinhold@kainhofer.com, http://reinhold.kainhofer.com, Core developer, Music2xml wrangler
- David Kastrup: dak@gnu.org Code worrier, support fighter, accordionist
- Jonathan Kulp: Assistant documentation editor
- Werner Lemberg, wl@gnu.org, Fonts, bug squasher
- John Mandereau: john.mandereau@free.fr, Translations
- Patrick McCarty: SVG guru, bug squad member, bug squasher, text handling
- Joe Neeman: Core developer
- 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
- Graham Percival: http://percival-music.ca, Project manager, Documentation Editor
- Mark Polesky: Assistant documentation editor, Code cleanup
- Neil Puttock: Core developer
- Mike Solomon: mike@apollinemike.com, Contemporary music attaché
- Carl Sorensen: c_sorensen@byu.edu, Core developer, Frog meister
- Francisco Vila: Translation Meister
- Valentin Villenave: LSR editor and Bug squad member

### Volt fejlesztők

- Mats Bengtsson: mats.bengtsson@ee.kth.se, http://www.s3.kth.se/~mabe/, Support guru
- Pedro Kroeger: Build meister
- John Mandereau: john.mandereau@free.fr, Translation meister
- Graham Percival: http://percival-music.ca, Bug meister, Grand Documentation Project leader
- Jürgen Reuter: reuter_j@web.de, http://www.juergen-reuter.de, Ancient notation
- Erik Sandberg: Bug meister
- Nicolas Sceaux: Core developer, Schemer extraordinaire

### Jelenlegi közreműködők

#### Programozás

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

#### Betűtípus

Keith OHara, Marc Hohl, Alexander Kobel, Carsten Steger

#### Dokumentáció

Colin Campbell, Andrew Hawryluk, James Lowe, Mike Moral, Ralph Palmer, David Pounder, Patrick Schmidt

#### Támogatás

Christian Hitz

#### Honosítás

Federico Bruni, Dénes Harmath, Jean-Charles Malahieude, Tineke de Munnik, Till Paala, Ralf Wildenhues, Yoshiki Sawada

### Volt közreműködők

#### Programozás

Erlend Aasland, Maximilian Albert, Guido Amoruso, Kristof Bastiaensen, Pál Benkő, Juliusz Chroboczek, Angelo Contardi, David Feuer, Bertalan Fodor, Mathieu Giraud, Yuval Harel, Bernard Hurley, Yoshinobu Ishizaki, Chris Jackson, David Jedlinsky, Heikki Junes, Michael Krause, Jean-Baptiste Lamy, Jonatan Liljedahl, Peter Lutek, Hendrik Maryns, Joe Neeman, Matthias Neeracher, Tatsuya Ono, Lisa Opus Goldstein, Guy Gascoigne-Piggford, Stan Sanderson, Edward Sanford Sutton, Andreas Scherer, Johannes Schindelin, Kim Shrier, Vicente Solsona Della, David Svoboda, Sebastiano Vigna, Arno Waschk, Michael Welsh Duggan, John Williams, Milan Zamazal, Rune Zedeler

#### Betűtípus

Tom Cato Amundsen, Chris Jackson, Arno Waschk, Rune Zedeler

#### Dokumentáció

Erlend Aasland, Trevor Bača, Alard de Boer, Jay Hamilton, Andrew Hawryluk, Joseph Harfouch, Cameron Horsburgh, Geoff Horton, Ian Hulin, Heikki Junes, Kurtis Kroon, Dave Luttinen, Kieren MacMillan, Christian Mondrup, Eyolf Østrem, Ralph Palmer, François Pinard, Eduardo Vieira, Michael Rasmussen, Till Rettig, Carl D. Sorensen, Anh Hai Trinh, Rune Zedeler

#### Támogatás

Anthony Fok, Chris Jackson, Heikki Junes, David Svoboda

#### Honosítás

Frédéric Chiasson, Abel Cheung, Alard de Boer, Simon Dahlbacka, Orm Finnendahl, David González, Nicolas Grandclaude, Damien Heurtebise, Matthieu Jacquot, Bjoern Jacke, Neil Jerram, Heikki Junes, Nicolas Klutchnikoff, Jean-Charles Malahieude, Adrian Mariano, Christian Mondrup, Tineke de Munnik, Steven Michael Murphy, 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, Olcay Yıldırım

## Publikációk

### Amit mi írtunk

- Han-Wen Nienhuys: LilyPond, automatikus kottaformázás és a szoftvertermék kiadásának művészete. A szabad szoftver nemzetközi fóruma 2006 (FISL7.0) (PDF 1095k)
- Erik Sandberg: A bemeneti nyelv és a formázó szétválasztása a GNU Lilypondban. Diplomaterv, Uppsalai Egyetem, Információtechnológiai Tanszék, 2006. március (PDF 750k)
- Han-Wen Nienhuys, Jan Nieuwenhuizen: LilyPond, egy automatizált kottaszedő rendszer. Jegyzőkönyv a XIV. zenei informatikai kollokviumról (XIV CIM 2003), Firenze, Olaszország, 2003. május (PDF 95k)

### Amit mások írtak

- 2009. szeptember

  A német LinuxUser magazin írt egy cikket a LilyPondról.

- 2008. február

  Andrew Hawryluk személyes oldalán egy cikksorozatban összehasonlítja általánosságban a Finalét és a LilyPondot, és a két szoftver kottaszedési képességeit értékeli részletesen. A második cikk egy tanulságos elemzés Rachmanyinov 6. prelűdjének kottaképéről, melyben egy kézzel szedett kiadás szolgál összehasonlítási alapul.

- 2005. december

  A Linux Journal közzétesz egy cikket Schenker-diagramok készítése GNU LilyPonddal címen. Ez egy gyakorlatias cikk igen szép LilyPond grafikákkal. A szerző, Kris Shaffer megjegyzi: „A GNU Lilypond gyönyörű kottaképe után a kereskedelmi alternatívák másodosztályúnak tűnnek.” A cikk elérhető online.

- 2005. augusztus 20.

  A belga hírlap, a De Standaard szerkesztői annak járnak utána, mi motiválja a szabad szoftverek fejlesztőit. Erről A tudás nonprofit megosztása című cikkben írnak. A szemléltető példa a LilyPond. A cikkben szerepelnek egy Jan Nieuwenhuizennel e-mailben készített riport részletei is. Ez a LilyPond első megjelenése a nyomtatott szakmai sajtóban.

- 2005. június

  A LilyPond 2.6-os verziójának kiadásáról megjelenik egy francia cikk a linuxfr.org weboldalon.

- 2004. október

  A Computer!Totaal holland informatikai magazin szerkesztői azt írják a LilyPondról a 2004. októberi számban: „A LilyPond egy csodálatos szabad (nyílt forrású) szoftver! [...] A LilyPonddal szedett kotta kivételesen szép. [...] Egy sokrétű rendszerrel állunk szemben, ami szinte mindenre képes!”

- 2004. július-augusztus

  Dave Phillips egy bevezető cikket ír a Linux Journalba Csúcstechnológia a kottaírásban: LilyPond címmel. 1. rész, 2. rész.

- 2004. március

  Chris Cannam riportot készít Han-Wen Nienhuysszal és Jan Nieuwenhuizennel a linuxmusician.com (ma már nem létező) oldalon. A riport megjelenik a slashdot.org-on is.

- 2004. február

  Gail Selkirk jazzénekes ír arról, hogyan Merüljünk bele a LilyPond világába.

  „...Könnyedén lejegyezhetsz akár slágereket, akár nagyzenekari műveket, az eredmény pompás!” (A Computer Music Special CMS06 száma)

## Hírarchívum

#### LilyPond 2.14.2 released! July 22, 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.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.13/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 Fejlesztés.

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 Hibajelentés.

#### 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 Fejlesztés.

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 Hibajelentés.

#### 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 Fejlesztés.

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 Hibajelentés.

#### 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 Fejlesztés.

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 Hibajelentés.

#### 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 Hibajelentés.

#### 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 Fejlesztés.

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 Hibajelentés.

#### 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 Fejlesztés.

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 Hibajelentés.

#### 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 Hibajelentés.

#### 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 Fejlesztés.

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 Hibajelentés.

#### 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 Fejlesztés.

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 Hibajelentés.

#### 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 Fejlesztés.

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 Hibajelentés.

#### 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 Fejlesztés.

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 Hibajelentés.

#### 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 Fejlesztés.

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 Hibajelentés.

#### 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 Fejlesztés.

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 Hibajelentés.

#### 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!

#### Alpha test two of 2.14 – LilyPond 2.13.35 released! Sep 29, 2010

LilyPond 2.13.35 is out; this is the second 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 Fejlesztés.

Three known regressions against 2.12.3 still exist: Issue 1173 MetronomeMarks cannot be aligned on a note if a multi-measure rest exists in another voice, and two spacing bugs: Issue 1240 and Issue 1252. If you decide to test 2.13.35, do not be surprised to discover problems; just send us polite Hibajelentés.

#### Alpha test of 2.14 – LilyPond 2.13.34 released! Sep 21, 2010

LilyPond 2.13.34 is out; this is the first 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 Fejlesztés.

One known regression against 2.12.3 still exist: Issue 1173 MetronomeMarks cannot be aligned on a note if a multi-measure rest exists in another voice, but we expect to find more. If you decide to test 2.13.34, do not be surprised to discover problems; just send us polite Hibajelentés.

#### 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 Kapcsolat.

Figyelem: 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.
Változások, Fejlesztés.

#### 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.12.0 „Rune” — December 27, 2008

A new stable release of LilyPond is available.
Announcement, Változások, Letöltés.

#### 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, Változások, Régi verziók.

#### 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.
Változások, Régi verziók.

#### LilyPond 2.11.63. October 29, 2008

LilyPond 2.11.63 is available. This release has lots of updates to the documentation and translations. Régi verziók.

#### LilyPond 2.11.62 &ndash; Release Candidate. October 11, 2008

LilyPond 2.11.62 is available. This is is one of the last releases before 2.12, so testing it is encouraged. In addition to a bugfix in `\tempo` command, this release has lot of updates to Spanish and German documentation translations, and the stylesheet for HTML documentation has been improved.
Bugfixes, Régi verziók.

#### 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, Változások, Régi verziók.

#### 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`. Régi verziók.

#### 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. Régi verziók.

#### 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, Változások, Régi verziók.

#### 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.
Változások, Régi verziók.

#### 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.
Változások, Régi verziók.

#### 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, Régi verziók.

#### 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, Régi verziók.

#### LilyPond 2.11.53 available. July 23, 2008

LilyPond 2.11.53 is out. This release fixes a lot of bugs.
Bugfixes, Régi verziók.

#### 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, Változások, Régi verziók.

#### 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, Régi verziók.

#### 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, Régi verziók.

#### 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, Régi verziók.

#### 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, Régi verziók.

#### 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, Régi verziók.

#### 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, Változások, Régi verziók.

#### 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 Kapcsolat) 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, Változások, Régi verziók.

#### 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, Régi verziók.

#### 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, Régi verziók.

#### LilyPond 2.11.42 available. March 9, 2008

Release 2.11.42 is out. It fixes some formatting and spacing bugs.
Bugfixes, Régi verziók.

#### 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, Régi verziók.

#### LilyPond 2.11.37 available. January 3, 2008

Release 2.11.37 is available. It has a few bugfixes, and documentation changes. (Régi verziók)

#### 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, Régi verziók.

#### LilyPond 2.10.33 and 2.11.33 available. September 20, 2007

Release 2.11.33 is now available.
Bugfixes 2.10, Bugfixes 2.11, Régi verziók.

#### LilyPond 2.11.32 available. September 2, 2007

Release 2.11.32 is now available.
Bugfixes, Régi verziók.

#### 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, Régi verziók.

#### 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, Régi verziók.

#### 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, Régi verziók.

#### 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, Régi verziók.

#### 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, Régi verziók.

#### 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, Régi verziók.

#### LilyPond 2.10.23 and 2.11.23 available - May 1, 2007

This has lots of bugfixes.
Bugfixes 2.10, Bugfixes 2.11, Régi verziók.

#### &Uuml;bersetzung der Dokumentation - 10. April 2007

Die Kapitel 1-5 (der Abschnitt für Anf&auml;nger) des LilyPond-Benutzerhandbuchs sind auf deutsch &uuml;bersetzt &mdash; sie sind erh&auml;ltlich f&uuml;r die Változások online und Régi verziók.

#### LilyPond 2.11.22 available - April 10, 2007

This release has updates of the dot collision code.
Bugfixes, Változások, Régi verziók.

#### LilyPond 2.11.21 available - March 24, 2007

This release has some documentation updates.
Bugfixes, Változások, Régi verziók.

#### Traduction de la documentation en fran&ccedil;ais - 25 f&eacute;vrier 2007

Les chapitres 1 &agrave; 4 et 6 du manuel de l’utilisateur sont d&eacute;sormais traduits, et disponibles en ligne &mdash; version 2.10, version 2.11. Les traductions sont &eacute;galement incluses dans la documentation t&eacute;l&eacute;chargeable.

#### LilyPond 2.10.20 and 2.11.20 available - February 25, 2007

This release fixes many bugs.
Bugfixes 2.10, Bugfixes 2.11, Változások, Régi verziók.

#### LilyPond 2.10.19 and 2.11.19 available - February 18, 2007

This release fixes many bugs.
Bugfixes 2.10, Bugfixes 2.11, Változások, Régi verziók.

#### 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, Változások, Régi verziók.

#### LilyPond 2.11.17 available - February 9, 2007

This release fixes still more bugs.
Bugfixes, Változások, Régi verziók.

#### LilyPond 2.10.16 and 2.11.16 available - February 4, 2007

This release fixes many bugs. (Bugfixes 2.10, Bugfixes 2.11, Változások, Régi verziók)

#### 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, Változások, Régi verziók.

#### 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, Változások, Régi verziók

#### 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, Változások, Régi verziók.

#### 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, Változások, Régi verziók.

#### LilyPond 2.10.12 available - January 17, 2007

This release mirrors 2.11.12. Notably, it has the same memory usage improvements.
Bugfixes, Változások, Régi verziók.

#### LilyPond 2.10.11 available - January 12, 2007

This release mostly has the same fixes as 2.11.11.
Bugfixes, Változások, Régi verziók.

#### 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, Változások, Régi verziók.

#### 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, Változások, Régi verziók.

#### 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, Változások, Régi verziók.

#### LilyPond 2.11.9 and 2.10.9 available - January 3, 2007

This release has a couple of bugfixes, and &mdash;in 2.11.9&mdash further improvements in the regression test suite
Bugfixes, Változások, Régi verziók.

#### LilyPond 2.11.8 and 2.10.8 available - January 3, 2007

New! Improved! With even more bugfixes!
Bugfixes, Változások, Régi verziók.

#### `lilypond.org` auf deutsch - 31. Dezember 2006

Die LilyPond-Webseiten sind jetzt auch auf deutsch &uuml;bersetzt!

#### `lilypond.org` en español - December 29, 2006

¡Ya está disponible la versión en español del sitio web de LilyPond!

#### LilyPond 2.11.7 and 2.10.7 available - January 1, 2007

New! Improved! With even more bugfixes!
Bugfixes, Változások, Régi verziók.

#### LilyPond 2.11.6 available - December 30, 2006

This release supports arbitrary fractional alterations, allowing music with different microtonal conventions to be typeset.
Bugfixes, Változások, Régi verziók.

#### LilyPond 2.10.6 available - December 30, 2006

New! Improved! With even more bugfixes!
Bugfixes, Változások, Régi verziók.

#### LilyPond 2.11.5 available - December 24, 2006

These releases complete the translation infrastructure for Documentation.
Bugfixes, Változások, Régi verziók.

#### LilyPond 2.10.5 available - December 24, 2006

New! Improved! With even more bugfixes!
Bugfixes, Változások, Régi verziók.

#### 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, Változások, Régi verziók.

#### LilyPond 2.11.3 available - December 19, 2006

This release has graphical test results and several website build improvements.
Bugfixes, Változások, Régi verziók.

#### LilyPond 2.10.3 available - December 19, 2006

This release fixes several bugs.
Bugfixes, Régi verziók.

#### LinuxPPC binaries available! - December 19, 2006

From now on, our GUB binary builds include support for Linux/PPC. (Régi verziók)

#### Traduction du tutoriel en fran&ccedil;ais. December 13, 2006

Fruit du travail d’une &eacute;quipe de traducteurs, le tutoriel en fran&ccedil;ais est maintenant disponible en ligne. Version 2.10, Version 2.11.

#### LilyPond 2.11.2 available - December 12, 2006

This release supports glissandi and harmonics in tablature.
Bugfixes, Változások, Régi verziók.

#### LilyPond 2.10.2 available - December 12, 2006

A new stable release of LilyPond is available.
Bugfixes, Régi verziók.

#### LilyPond 2.11.1 available - December 4, 2006

This release has improved support for horizontal spacing.
Bugfixes, Változások, Régi verziók.

#### LilyPond 2.10.1 available - December 3, 2006

A new stable release of LilyPond is available.
Bugfixes, Régi verziók.

#### LilyPond 2.11.0 available - November 27, 2006

This release has improved support for vertical spacing. (Változások, Régi verziók)

#### LilyPond 2.10.0 available - November 11, 2006

A new stable release of LilyPond is available. (Announcement, Változások, Régi verziók)

#### 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.

#### LilyPond 2.9.29 available - November 5, 2006

This release has many more bugfixes.
Bugfixes, Régi verziók.

#### LilyPond 2.9.28 available - November 3, 2006

This release has many more bugfixes.
Bugfixes, Régi verziók.

#### LilyPond 2.9.27 available - October 28, 2006

This release has a new `FretBoards` context, and some further bugfixes.
Bugfixes, Változások, Régi verziók.

#### 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 (Publikációk).

#### LilyPond 2.9.26 available - October 20, 2006

This release has further bugfixes.
Bugfixes, Régi verziók.

#### LilyPond 2.9.25 available - October 18, 2006

This release has more bugfixes; from now on, binaries are also available for x86/64.
Bugfixes, Régi verziók.

#### LilyPond 2.9.24 available - October 15, 2006

This release has support for right hand guitar fingerings, and offers some bugfixes. (Változások, Bugfixes, Régi verziók)

#### 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. (Változások, Régi verziók)

#### LilyPond 2.9.22 available - October 9, 2006

Test this release candidate for LilyPond 2.10! (Régi verziók)

#### LilyPond 2.9.21 available - October 4, 2006

Test this release candidate for LilyPond 2.10! (Régi verziók)

#### LilyPond 2.9.20 available - October 3, 2006

Test this release candidate for LilyPond 2.10! (Régi verziók)

#### 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. (Változások, Régi verziók)

#### 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 (Változások, Régi verziók)

#### LilyPond 2.9.15 available - August 20, 2006

This releases fixes many bugs in the 2.9.14 release. (Régi verziók)

#### LilyPond 2.8.6 available - August 8, 2006

This release contains a few minor bugfixes; the source tarball is also available. (Régi verziók)

#### 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. (Változások, Régi verziók)

#### 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. (Változások, Régi verziók)

#### 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. (Változások, Régi verziók)

#### 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. (Változások, Régi verziók)

#### LilyPond 2.9.10 available - June 15, 2006

This releases fixes a couple of bugs in 2.9.9. (Változások, Régi verziók)

#### LilyPond 2.9.9 available - June 15, 2006

This releases fixes many bugs in 2.9.8 and earlier. (Változások, Régi verziók)

#### 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. (Változások, Régi verziók)

#### 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. (Régi verziók)

#### 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. (Változások, Régi verziók)

#### New essay pages! - May 22, 2006

The Automated Engraving essay has been updated with material from the FISL talk, with pages on modeling notation and algorithms for esthetics. Happy reading!

#### LilyPond 2.9.5 available - May 17, 2006

This release supports object rotation, hairpins with circled tips, hairpins that run to barlines before notes and improvements in the MusicXML converter. (Változások, Régi verziók)

#### 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. (Változások, Régi verziók)

#### LilyPond 2.8.2 available - May 12, 2006

This release has fixes for minor bugs and compilation issues. (Régi verziók)

#### 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. (Változások, Régi verziók)

#### FISL7.0 slides available - April 22, 2006

The slides for Han-Wen’s talk at FISL 7 are now online. (Publikációk)

#### LilyPond 2.8.1 is out! - April 3, 2006

Important bugfixes include CJK font handling and a Darwin/x86 port. (Változások, Régi verziók)

#### 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. (Változások, Régi verziók)

#### 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. (Régi verziók)

#### LilyPond 2.8.0 is out! - March 22, 2006

Version 2.8 is here! Read the release announcement. (Változások, Régi verziók)

#### LilyPond 2.7.39 is out - March 17, 2006

This release has even more bug fixes. Please test before 2.8 is released. (Változások, Régi verziók)

#### 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. (Változások, Régi verziók)

#### LilyPond 2.7.37 is out - March 4, 2006

This release has more bug fixes. Please help us by testing it! (Változások, Régi verziók)

#### 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. (Változások, Régi verziók)

#### 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. (Változások, Régi verziók)

#### 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. (Változások, Régi verziók)

#### 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. (Változások, Régi verziók)

#### 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. (Változások, Régi verziók)

#### 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. (Változások, Régi verziók)

#### 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. (Változások, Régi verziók)

#### 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). (Változások, Régi verziók)

#### 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. (Változások, Régi verziók)

#### 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! (Régi verziók)

#### 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 Régi verziók 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). (Változások, Régi verziók)

#### 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 &ldquo;GNU LilyPond generates beautiful graphics that make commercial alternatives seem second-rate.&rdquo; 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 Régi verziók 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! (Változások, Régi verziók)

#### 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). (Változások, Régi verziók)

#### 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. (Változások, Régi verziók)

#### 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.

(Változások, Régi verziók)

#### 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. (Változások, Régi verziók)

#### 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). (Változások, Régi verziók)

#### LilyPond 2.6.5 is out - December 1, 2005

This release updates the bugreporting address and reorganizes the documentation tree. (Régi verziók)

#### 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. (Változások, Régi verziók)

#### 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. (Változások, Régi verziók)

#### 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. (Változások, Régi verziók)

#### 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. (Változások, Régi verziók)

#### 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. (Változások, Régi verziók)

#### 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. (Változások, Régi verziók)

#### 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. (Változások, Régi verziók)

#### LilyPond 2.6.4 is out - October 11, 2005

This release fixes a few minor problems with the stable series. (Változások, Régi verziók)

#### 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). (Változások, Régi verziók)

#### 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. (Változások, Régi verziók)

#### 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. (Változások, Régi verziók)

#### LilyPond 2.7.9 is out - September 5, 2005

This is mainly a bugfix release. (Változások, Régi verziók)

#### Traduction fran&ccedil;aise du site - September 03, 2005

Grâce à l’équipe des traducteurs, de nombreuses pages du site sont maintenant disponibles en fran&ccedil;ais, notamment l’essai sur la gravure musicale.

#### 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. (Változások, Régi verziók)

#### Article in ‘De Standaard’ - August 20, 2005

The Belgian newspaper De Standaard investigates what drives Free Software authors in an article titled Delen van KENNIS zonder WINSTBEJAG (Non-profit sharing of knowlegde) using LilyPond as an example. This marks LilyPond’s first appearance in mainstream printed press.

#### LilyPond 2.7.7 is out - August 22, 2005

This release has a rewriting of tie formatting which was sponsored by Bertalan Fodor, Jay Hamilton, Kieren MacMillan, Steve Doonan, Trevor Baca, and Vicente Solsona Dell&aacute;. (Változások, Régi verziók)

#### 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. (Változások, Régi verziók)

#### 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. (Változások, Régi verziók)

#### 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. (Változások, Régi verziók)

#### LilyPond 2.6.3 is out - August 4, 2005

This release fixes a memory corruption bug that was triggered by \override’ing Beam settings. (Régi verziók)

#### 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. (Változások, Régi verziók)

#### 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. (Változások, Régi verziók)

#### 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. (Változások, Régi verziók)

#### 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, Régi verziók, Változások)

#### 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. (Régi verziók)

#### 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. (Változások, Régi verziók)

#### LilyPond 2.7 is out - July 9, 2005

LilyPond 2.7.0 is out. It has support for paragraph text and pitched trill notation. (Változások, Régi verziók)

#### 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. (Régi verziók)

#### 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. (Régi verziók)

#### 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. (Régi verziók)

#### 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! (Régi verziók)

#### 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). (Régi verziók)

#### 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. (Régi verziók)

#### 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. (Régi verziók)

#### 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. (Régi verziók)

#### 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. (Régi verziók)

#### 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. (Változások, Régi verziók)

#### 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. (Régi verziók)

#### 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. (Változások, Régi verziók)

#### 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 Változások file, or go straight to Régi verziók.

#### 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 Változások file and Régi verziók.

#### 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. Régi verziók

#### 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. Régi verziók

#### 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. Régi verziók

#### 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 Változások file and Régi verziók!

#### 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 Változások file and download Régi verziók!

#### March 7, 2005

LilyPond 2.4.5 is out. This release backports the tieWaitForNote feature and has support for tetex-3.0. Régi verziók

#### February 28, 2005

LilyPond 2.5.13 is available for Fedora Core 3. You need to install ESP Ghostscript 8.15rc3. Unfortunately, this version of Ghostscript lacks the IJS dynamic library, which means that it will conflict with the gimp-print package. You may install it with –nodeps. Use at your own risk.

#### 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 Változások file and download Régi verziók!

#### 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 Változások file and Régi verziók!

#### 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. Régi verziók!

#### 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. Régi verziók

#### 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. Régi verziók

#### 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 Régi verziók!

#### 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. Régi verziók 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. Régi verziók 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. Régi verziók 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. Régi verziók 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. Régi verziók 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. Régi verziók 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. Régi verziók 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. Régi verziók 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. Régi verziók

#### 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. Régi verziók 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 Változások file. Régi verziók

#### 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. Régi verziók 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. Régi verziók 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. Régi verziók 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. Régi verziók 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{}. Régi verziók 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. Régi verziók 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. Régi verziók 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. Régi verziók 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. Régi verziók 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. Régi verziók 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. Régi verziók 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. Régi verziók 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. Régi verziók 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. Régi verziók 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. Régi verziók 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. Régi verziók 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

Régi verziók 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. Régi verziók 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. Régi verziók 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. Régi verziók 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. Régi verziók 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. Régi verziók and check out the changes in the ChangeLog.

#### July 5, 2004

LilyPond 2.2.4 was released. It is mainly a bug fix release. Régi verziók 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 Régi verziók.

#### 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 Régi verziók.

#### 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 Régi verziók.

#### 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 Régi verziók.

#### 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 Régi verziók.

#### 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 Változások or head straight to the Régi verziók.

#### May 9, 2004

LilyPond 2.3.1 is out. This release has many new and cool features. Check out the Változások or head straight to the Régi verziók.

#### 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. Régi verziók.

#### 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 Változások. Régi verziók.

#### 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. Régi verziók

#### 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 Régi verziók.

#### 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. Régi verziók.

#### March 30, 2004

LilyPond 2.1.36 has many fixes in the user manual. Régi verziók.

#### 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 Változások. Régi verziók

#### March 22, 2004

LilyPond 2.1.34 fixes minor bugs, and has more rewriting. Régi verziók.

#### March 21, 2004

LilyPond 2.1.33 fixes a serious bug, and a few other irritations. Régi verziók

#### 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). Régi verziók.

#### 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 Változások and Régi verziók.

#### March 14, 2004

The linuxmusician.com interview made the slashdot frontpage!.

#### 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 Változások and Régi verziók.

#### 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 Változások and Régi verziók.

#### 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 Változások and Régi verziók.

#### 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 Változások. Régi verziók

#### February 18, 2004

LilyPond 2.1.25 fixes many bugs, and changes the conventions for altering accidental rules. Régi verziók

#### 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 Változások. Régi verziók

#### 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 Változások. Régi verziók

#### 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 Változások. Régi verziók

#### 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 Változások. Régi verziók

#### 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 Változások. Régi verziók

#### 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 Változások. Régi verziók

#### 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 Változások.

#### 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 Változások. Régi verziók

#### 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 Változások. Régi verziók

#### 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 Változások. Régi verziók

#### 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. Régi verziók

#### January 19, 2004

LilyPond 2.1.12 fixes many bugs and improves formatting of ottava brackets. More information in the Változások. Régi verziók

#### 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 Változások. Régi verziók

#### January 16, 2004

LilyPond 2.1.10 has a load of bugfixes and a shorter syntax for octave checks. More information in the Változások. Régi verziók

#### 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 Változások. Régi verziók

#### 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 Változások. Régi verziók

#### January 7, 2004

An update to the stable branch, version 2.0.2, was released today. It contains a couple of minor bugfixes. Régi verziók

#### 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 Változások 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&auml;ngers Morgen. More information in the Változások and download here.

#### December 30, 2003

LilyPond 2.1.4 is released. Font shapes and linethickness are now truly different for different staff sizes, thus lending an engraved look to scores printed in smaller type too. See the Változások 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 Változások 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 Változások 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 Változások and download here.

#### October 11, 2003

LilyPond 2.1.0 released. See the Változások 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. Régi verziók

#### October 4, 2003

LilyPond 2.0.1 binaries are available for Windows (Cygwin version 1.5). Régi verziók. Thanks to Bertalan Fodor, our new Cygwin maintainer!

#### September 29, 2003

LilyPond 2.0.1 is released. It contains minor bugfixes. See the Változások 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 Változások and download here.

#### September 23, 2003

LilyPond 1.9.9 is released. This is the second LilyPond 2.0 prerelease. Check the Változások and download here.

#### September 19, 2003

LilyPond 1.9.8 is released. This is the first LilyPond 2.0 prerelease. Check the Változások and download here.

#### September 17, 2003

LilyPond 1.9.7 is released. LilyPond now has support for quarter tone accidentals! Régi verziók

#### September 16, 2003

LilyPond 1.9.6 is released. It has a lot of minor fixes and updates. Régi verziók

#### 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. Régi verziók

#### September 9, 2003

LilyPond 1.8.2 is released. This release fixes a couple of minor bugs. Régi verziók

#### September 7, 2003

LilyPond 1.8 binaries are available for Windows (Cygwin version 1.5). Régi verziók

#### 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 Változások and get it here.

#### August 28, 2003

LilyPond 1.9.2 is released. Read the Változások and get it here.

#### August 26, 2003

LilyPond 1.9.1 is released. Read the Változások and get it here.

#### August 25, 2003

The LilyPond 1.9 development release is available. Read the Változások 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 Változások.

#### August 18, 2003

PlanetCCRMA (eg. RedHat 8 and 9) has been updated to 1.8. Download here.

#### August 7, 2003

LilyPond 1.8 is released. Read Változások and get it 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.

# Tartalomjegyzék

# A navigációs panel használata

This document was generated by Graham Percival on július 26, 2011 using texi2html 1.82.

A navigációs panelen levő gombok jelentése a következő:

Gomb | Név | Cél | 1.2.3-ból ide jutunk
--- | --- | --- | ---
[] |  |  |
[ << ] | Visszaugrás | Fejezet eleje vagy előző fejezet | 1
[] |  |  |
[Címoldal] | Címoldal | Dokumentum címoldala |
[Tartalom] | Tartalom | Tartalomjegyzék |
[Tárgymutató] | Tárgymutató | Tárgymutató |
[ ? ] | Súgó | Segítség a navigációhoz |
[] |  |  |
[ >> ] | Előreugrás | Következő fejezet | 2
[] |  |  |
[] |  |  |
[ < ] | Vissza | Előző szakasz az olvasási sorrendben | 1.2.2
[] |  |  |
[Fel] | Fel | Szülő szakasz | 1.2
[] |  |  |
[ > ] | Előre | Következő szakasz az olvasási sorrendben | 1.2.4

Példánkban az aktuális pozíció az 1.2.3 alalszakasz egy olyan dokumentumban, melynek szerkezete a következő:

- 1. szakasz
  - 1.1 alszakasz
    - ...
  - 1.2 alszakasz
    - 1.2.1 alalszakasz
    - 1.2.2 alalszakasz
    - 1.2.3 alalszakasz <== Aktuális pozíció
    - 1.2.4 alalszakasz
  - 1.3 alszakasz
    - ...
  - 1.4 alszakasz

Más nyelvek: English, česky, deutsch, español, français, italiano, 日本語, nederlands, 中文.

### Validation

Köszönet a webdev.nl részére a `lilypond.org` tárhelyért.