@end macro
+@dircategory GNU LilyPond --- the music typesetter
+@direntry
+* LilyPond Changes: (lilypond-changes). Changes to recent versions.
+@end direntry
+
@documentencoding utf-8
@documentlanguage en
@afourpaper
@documentlanguage en
@afourpaper
+@dircategory GNU LilyPond --- the music typesetter
+@direntry
+* LilyPond Contributor Guide: (lilypond-contributor). Technical issues and policies for contributors.
+@end direntry
+
@macro manualIntro
This manual documents contributing to LilyPond version
@version{}. It discusses technical issues and policies that
@settitle Příručka k učení se
@afourpaper
+@dircategory GNU LilyPond --- the music typesetter
+@direntry
+* Příručka LilyPond k učení se: (lilypond-learning). Začátek je zde.
+@end direntry
+
@macro manualIntro
Tento soubor poskytuje úvod pro LilyPond verze
@version{}.
@c expected to be found in lilypond/ subdirectory.
@dircategory GNU LilyPond --- the music typesetter
@direntry
-* Příručka LilyPond k učení se: (lilypond-learning). Začátek je zde.
* Slovníček: (music-glossary). Překlad pojmů z angličtiny do dalších řečí.
* Příručka pro zápis not v LilyPondu: (lilypond-notation). Příručka pro zápis not v LilyPondu.
* Úryvky LilyPondu: (lilypond-snippets). Mnoho triků, rad a příkladů.
@documentlanguage de
@afourpaper
+@dircategory GNU LilyPond --- the music typesetter
+@direntry
+* LilyPond automatischen Musiksatz: (lilypond-essay). Automatischen Musiksatz von LilyPond.
+@end direntry
+
@c Translators: Till Paala
@include macros.itexi
@documentlanguage de
@afourpaper
+@dircategory GNU LilyPond --- the music typesetter
+@direntry
+* LilyPond Erweiterung: (lilypond-extending). Wie man die Funktionalität von LilyPond erweitern kann.
+@end direntry
+
@c Translators: Till Paala
@macro manualIntro
@settitle LilyPond Handbuch zum Lernen
@afourpaper
+@dircategory GNU LilyPond --- the music typesetter
+@direntry
+* LilyPond Handbuch zum Lernen: (lilypond-learning). Hier beginnen.
+@end direntry
+
@macro manualIntro
Diese Datei stellt eine Einleitung für LilyPond Version
@version{} zur Verfügung.
@setfilename lilypond.info
@settitle LilyPond Benutzerhandbuch
+@dircategory GNU LilyPond --- the music typesetter
+@direntry
+* LilyPond Notationshandbuch: (lilypond-notation). LilyPond Notationshandbuch.
+@end direntry
+
@c Translators: Till Paala
@afourpaper
@settitle GNU LilyPond Programmbenutzung
@afourpaper
-
+@dircategory GNU LilyPond --- the music typesetter
+@direntry
+* LilyPond Application Usage: (lilypond-usage). Programme installieren und benutzen.
+* lilypond: (lilypond-usage)LilyPond starten. Das LilyPond-Programm aufrufen.
+* abc2ly: (lilypond-usage)abc2ly starten. ABC-Notation importieren.
+* convert-ly: (lilypond-usage)Dateien mit convert-ly aktualisieren. Ältere LilyPond-Versionen
+* etf2ly: (lilypond-usage)etf2ly starten. Finale-Dateien importieren.
+* lilypond-book: (lilypond-usage)LilyPond-book. Text und Musik integrieren.
+* midi2ly: (lilypond-usage)midi2ly starten. MIDI importieren.
+* musicxml2ly: (lilypond-usage)musicxml2ly starten. MusicXML-Dateien importieren.
+@end direntry
@macro manualIntro
Diese Datei erklärt, wie man die Programme, die mit LilyPond
@c expected to be found in lilypond/ subdirectory.
@dircategory GNU LilyPond --- the music typesetter
@direntry
-* LilyPond Handbuch zum Lernen: (lilypond-learning). Hier beginnen.
* Glossar: (music-glossary). Begriffsübersetzungen von Englisch in andere Sprachen.
-* LilyPond Notationshandbuch: (lilypond-notation). LilyPond Notationshandbuch.
* LilyPond Schnipsel: (lilypond-snippets). Viele Tricks, Tipps und Beispiele.
* LilyPond Referenz der Interna: (lilypond-internals). Definitionen zum Einstellen.
-* LilyPond Application Usage: (lilypond-usage). Programme installieren und benutzen.
* LilyPond Webseite: (lilypond-web). Vorschau der neuen Webseite.
-* lilypond: (lilypond-usage)LilyPond starten. Das LilyPond-Programm aufrufen.
-* abc2ly: (lilypond-usage)abc2ly starten. ABC-Notation importieren.
-* convert-ly: (lilypond-usage)Dateien mit convert-ly aktualisieren. Ältere LilyPond-Versionen
-* etf2ly: (lilypond-usage)etf2ly starten. Finale-Dateien importieren.
-* lilypond-book: (lilypond-usage)LilyPond-book. Text und Musik integrieren.
-* midi2ly: (lilypond-usage)midi2ly starten. MIDI importieren.
-* musicxml2ly: (lilypond-usage)musicxml2ly starten. MusicXML-Dateien importieren.
@end direntry
@end macro
+@dircategory GNU LilyPond --- the music typesetter
+@direntry
+* LilyPond Changes: (lilypond-changes). Funcionalidades nuevas.
+@end direntry
+
@documentencoding UTF-8
@documentlanguage es
@afourpaper
@documentlanguage es
@afourpaper
+@dircategory GNU LilyPond --- the music typesetter
+@direntry
+* Las funciones de grabado musical automatizado: (lilypond-essay). Las funciones de grabado musical automatizado dentro de LilyPond.
+@end direntry
+
@c translator: Francisco Vila
@macro manualIntro
@documentlanguage es
@afourpaper
+@dircategory GNU LilyPond --- the music typesetter
+@direntry
+* LilyPond Extensión: (lilypond-extending). Extender las funcionalidades de LilyPond.
+@end direntry
+
@c translator: Francisco Vila
@macro manualIntro
@documentlanguage es
@afourpaper
+@dircategory GNU LilyPond: el tipografiador de música
+@direntry
+* Manual de aprendizaje de LilyPond: (lilypond-learning). Comience por aquí.
+@end direntry
+
@macro manualIntro
Este archivo ofrece una introducción al programa LilyPond versión
@version{}.
@documentlanguage es
@afourpaper
+@dircategory GNU LilyPond: el tipografiador de música
+@direntry
+* LilyPond: (lilypond-notation). Referencia de la notación con LilyPond.
+@end direntry
+
@macro manualIntro
Este manual ofrece una referencia para toda la notación musical que se
puede producir con LilyPond versión @version{}. Da por sentado que el
@documentlanguage es
@afourpaper
+@dircategory GNU LilyPond: el tipografiador de música
+@direntry
+* Utilización del programa: (lilypond-usage). Instalación y ejecución de las aplicaciones.
+* lilypond: (lilypond-usage)Ejecutar LilyPond. Invocar el programa LilyPond.
+* abc2ly: (lilypond-usage)Invocación de abc2ly. Importación de ABC.
+* convert-ly: (lilypond-usage)Actualización de archivos mediante convert-ly. Versiones antiguas de LilyPond.
+* etf2ly: (lilypond-usage)Invocar etf2ly. Importación de Finale.
+* lilypond-book: (lilypond-usage)LilyPond-book. Intergrar texto y música.
+* midi2ly: (lilypond-usage)Invocar midi2ly. Importación de MIDI.
+* musicxml2ly: (lilypond-usage)Invocar musicxml2ly. Importación de MusicXML.
+@end direntry
+
@c Translators: Francisco Vila
@macro manualIntro
@c expected to be found in lilypond/ subdirectory.
@dircategory GNU LilyPond: el tipografiador de música
@direntry
-* Manual de aprendizaje de LilyPond: (lilypond-learning). Comience por aquí.
* Glosario musical: (music-glossary). Para usuarios de habla no inglesa.
-* LilyPond: (lilypond-notation). Referencia de la notación con LilyPond.
* Fragmentos de código de LilyPond: (lilypond-snippets). Consejos, trucos y ejemplos cortos.
* Referencia de funcionamiento interno: (lilypond-internals). Definiciones para la construcción de trucos.
-* Utilización del programa: (lilypond-usage). Instalación y ejecución de las aplicaciones.
* Página web: (lilypond-web). Vista previa de la nueva página.
-* lilypond: (lilypond-usage)Ejecutar LilyPond. Invocar el programa LilyPond.
-* abc2ly: (lilypond-usage)Invocación de abc2ly. Importación de ABC.
-* convert-ly: (lilypond-usage)Actualización de archivos mediante convert-ly. Versiones antiguas de LilyPond.
-* etf2ly: (lilypond-usage)Invocar etf2ly. Importación de Finale.
-* lilypond-book: (lilypond-usage)LilyPond-book. Intergrar texto y música.
-* midi2ly: (lilypond-usage)Invocar midi2ly. Importación de MIDI.
-* musicxml2ly: (lilypond-usage)Invocar musicxml2ly. Importación de MusicXML.
@end direntry
@documentlanguage en
@afourpaper
+@dircategory GNU LilyPond --- the music typesetter
+@direntry
+* LilyPond Engraving Functions: (lilypond-essay). Automatic engraving functions within LilyPond.
+@end direntry
+
@macro manualIntro
This essay discusses automatic music engraving functions within
LilyPond version @version{}.
@documentlanguage en
@afourpaper
+@dircategory GNU LilyPond --- the music typesetter
+@direntry
+* LilyPond Extending: (lilypond-extending). How to extend LilyPond's functionality.
+@end direntry
+
@macro manualIntro
This file explains how to extend the functionality of
LilyPond version @version{}.
@documentlanguage fr
@afourpaper
+@dircategory GNU LilyPond --- the music typesetter
+@direntry
+* La gravure musicale automatisée: (lilypond-essay). La gravure musicale automatisée de LilyPond.
+@end direntry
+
@macro manualIntro
Cet essai traite de la gravure de la musique et de la notation assistée
par ordinateur à l'aide de LilyPond version @version{}.
@afourpaper
+@dircategory GNU LilyPond -- le typographe de musique
+@direntry
+* Manuel d'initiation à LilyPond: (lilypond-learning). Les premiers pas.
+@end direntry
+
@macro manualIntro
Ce document constitue le manuel d'initiation à GNU LilyPond
@version{}.
@documentlanguage fr
@afourpaper
+@dircategory GNU LilyPond -- le typographe de musique
+@direntry
+* Manuel de notation: (lilypond-notation). Gravure de musique avec LilyPond.
+@end direntry
+
@macro manualIntro
Ce document constitue le manuel de notation de GNU LilyPond
@version{}. Sa lecture requiert une familiarité avec le contenu
@documentlanguage fr
@afourpaper
+@dircategory GNU LilyPond -- le typographe de musique
+@direntry
+* Manuel d'utilisation: (lilypond-usage). Installation et exécution des programmes.
+* abc2ly: (lilypond-usage) Lancement de abc2ly. Import de fichier ABC.
+* convert-ly: (lilypond-usage) Mise à jour de fichiers. Pour d'anciens fichiers LilyPond.
+* etf2ly: (lilypond-usage) Lancement de etf2ly. Import de fichier Finale.
+* lilypond-book: (lilypond-usage) LilyPond-book. Association musique-texte.
+* midi2ly: (lilypond-usage) Lancement de midi2ly. Import de fichier MIDI.
+* musicxml2ly: (lilypond-usage) Lancement de musicxml2ly. Import de fichier MusicXML.
+@end direntry
+
@c Translators: John Mandereau, Jean-Charles Malahieude
@macro manualIntro
@c expected to be found in lilypond/ subdirectory.
@dircategory GNU LilyPond -- le typographe de musique
@direntry
-* Manuel d'initiation à LilyPond: (lilypond-learning). Les premiers pas.
* Glossaire musicologique: (music-glossary). Pour l'utilisateur non anglophone.
-* Manuel de notation: (lilypond-notation). Gravure de musique avec LilyPond.
* Morceaux choisis de LilyPond: (lilypond-snippets). Petits trucs, astuces et exemples.
* Référence des propriétés internes: (lilypond-internals). Définitions pour les retouches.
-* Manuel d'utilisation: (lilypond-usage). Installation et exécution des programmes.
* LilyPond Website: (lilypond-web). Prévisualisation du site.
-* abc2ly: (lilypond-usage) Lancement de abc2ly. Import de fichier ABC.
-* convert-ly: (lilypond-usage) Mise à jour de fichiers. Pour d'anciens fichiers LilyPond.
-* etf2ly: (lilypond-usage) Lancement de etf2ly. Import de fichier Finale.
-* lilypond-book: (lilypond-usage) LilyPond-book. Association musique-texte.
-* midi2ly: (lilypond-usage) Lancement de midi2ly. Import de fichier MIDI.
-* musicxml2ly: (lilypond-usage) Lancement de musicxml2ly. Import de fichier MusicXML.
@end direntry
@documentlanguage hu
@afourpaper
+@dircategory GNU LilyPond --- the music typesetter
+@direntry
+* Tankönyv: (lilypond-learning). Itt kezdd az olvasást.
+@end direntry
+
@c Translators: Harmath Dénes
@macro manualIntro
@documentlanguage hu
@afourpaper
+@dircategory GNU LilyPond --- the music typesetter
+@direntry
+* Használat: (lilypond-usage). Az alkalmazás használata.
+* lilypond: (lilypond-usage)A lilypond futtatása. Kották szedése.
+* abc2ly: (lilypond-usage)Az abc2ly futtatása. ABC fájlok importálása.
+* convert-ly: (lilypond-usage)A convert-ly futtatása. Konvertálás régebbi verziókról.
+* etf2ly: (lilypond-usage)Az etf2ly futtatása. Finale fájlok importálása.
+* lilypond-book: (lilypond-usage)A lilypond-book futtatása. Szöveg és zene integrálása.
+* midi2ly: (lilypond-usage)A midi2ly futtatása. MIDI fájlok importálása.
+* musicxml2ly: (lilypond-usage)A musicxml2ly futtatása. MusicXML fájlok importálása.
+@end direntry
+
@c translator: Team-hu
@macro manualIntro
@c expected to be found in lilypond/ subdirectory.
@dircategory GNU LilyPond --- the music typesetter
@direntry
-* Tankönyv: (lilypond-learning). Itt kezdd az olvasást.
* Fogalomtár: (music-glossary). Többnyelvű szószedet.
* Kottaírás: (lilypond-notation). A kottaírás kézikönyve.
* Kódrészletek: (lilypond-snippets). Tippek, trükkök, példák.
* Belső működés: (lilypond-internals). A belső működés referenciája.
-* Használat: (lilypond-usage). Az alkalmazás használata.
* Web: (lilypond-web). A weboldal.
-* lilypond: (lilypond-usage)A lilypond futtatása. Kották szedése.
-* abc2ly: (lilypond-usage)Az abc2ly futtatása. ABC fájlok importálása.
-* convert-ly: (lilypond-usage)A convert-ly futtatása. Konvertálás régebbi verziókról.
-* etf2ly: (lilypond-usage)Az etf2ly futtatása. Finale fájlok importálása.
-* lilypond-book: (lilypond-usage)A lilypond-book futtatása. Szöveg és zene integrálása.
-* midi2ly: (lilypond-usage)A midi2ly futtatása. MIDI fájlok importálása.
-* musicxml2ly: (lilypond-usage)A musicxml2ly futtatása. MusicXML fájlok importálása.
@end direntry
@documentlanguage it
@afourpaper
+@dircategory GNU LilyPond --- il compositore tipografico di musica
+@direntry
+* Manuale di Apprendimento di LilyPond: (lilypond-learning). Comincia da qui.
+@end direntry
+
@macro manualIntro
Questo file fornisce un'introduzione alla versione di LilyPond
@version{}.
@documentlanguage it
@afourpaper
+@dircategory GNU LilyPond --- il compositore tipografico di musica
+@direntry
+* Uso del Programma: (lilypond-usage). Istallazione e esecuzione delle applicazioni.
+* lilypond: (lilypond-usage)Eseguire lilypond. Invocare il programma LilyPond.
+* abc2ly: (lilypond-usage)Invocare abc2ly. Importare ABC.
+* convert-ly: (lilypond-usage)Aggiornare i file con convert-ly. Versioni precedenti di LilyPond.
+* etf2ly: (lilypond-usage)Invocare etf2ly. Importare Finale.
+* lilypond-book: (lilypond-usage)lilypond-book. Integrare testo e musica.
+* midi2ly: (lilypond-usage)Invocare midi2ly. Importare MIDI.
+* musicxml2ly: (lilypond-usage)Invocare musicxml2ly. Importare MusicXML.
+@end direntry
+
@c Translators: Federico Bruni
@c Translation checkers: Luca Rossetto Casel
* LilyPond: (lilypond-notation). Guida alla Notazione di LilyPond.
* Frammenti di Codice di LilyPond: (lilypond-snippets). Piccoli trucchi, consigli, e esempi.
* Guida al Funzionamento Interno: (lilypond-internals). Definizioni per le modifiche manuali.
-* Uso del Programma: (lilypond-application). Istallazione e esecuzione delle applicazioni.
* Sito web: (lilypond-web). Anteprima del nuovo sito.
-* lilypond: (lilypond-usage)Eseguire lilypond. Invocare il programma LilyPond.
-* abc2ly: (lilypond-usage)Invocare abc2ly. Importare ABC.
-* convert-ly: (lilypond-usage)Aggiornare i file con convert-ly. Versioni precedenti di LilyPond.
-* etf2ly: (lilypond-usage)Invocare etf2ly. Importare Finale.
-* lilypond-book: (lilypond-usage)lilypond-book. Integrare testo e musica.
-* midi2ly: (lilypond-usage)Invocare midi2ly. Importare MIDI.
-* musicxml2ly: (lilypond-usage)Invocare musicxml2ly. Importare MusicXML.
@end direntry
@documentlanguage ja
@afourpaper
+@dircategory GNU LilyPond --- 楽譜譜刻プログラム
+@direntry
+* LilyPond 学習マニュアル: (lilypond-learning). ここから始めてください。
+@end direntry
+
@macro manualIntro
このマニュアルは LilyPond バージョン @version{} の導入部です。
@end macro
@documentlanguage ja
@afourpaper
+@dircategory GNU LilyPond --- 楽譜譜刻プログラム
+@direntry
+* LilyPond: (lilypond-notation). LilyPond 記譜法リファレンス。
+@end direntry
+
@macro manualIntro
このマニュアルは LilyPond バージョン @version{} で提供される@c
すべての記譜法についての参照を提供します。@c
@documentlanguage ja
@afourpaper
+@dircategory GNU LilyPond --- 楽譜譜刻プログラム
+@direntry
+* LilyPond アプリケーション使用方法: (lilypond-usage). アプリケーションを@c
+インスールして、実行する方法。
+* lilypond: (lilypond-usage)lilypond を実行する. LilyPond を呼び出す。
+* abc2ly: (lilypond-usage)abc2ly を呼び出す. ABC をインポートする。
+* convert-ly: (lilypond-usage)convert-ly でファイルを更新する. 古い LilyPond バージョン。
+* etf2ly: (lilypond-usage)etf2ly を呼び出す. Finale をインポートする。
+* lilypond-book: (lilypond-usage)lilypond-book. 文章と楽譜を統合する。
+* midi2ly: (lilypond-usage)midi2ly を呼び出す. MIDI をインポートする。
+* musicxml2ly: (lilypond-usage)musicxml2ly を呼び出す. MusicXML をインポートする。
+@end direntry
+
@macro manualIntro
このマニュアルは LilyPond バージョン @version{} で配布される@c
プログラムの実効方法について説明します。@c
--- /dev/null
+@c -*- coding: utf-8; mode: texinfo; -*-
+@ignore
+ Translation of GIT committish: 499a511d4166feaada31114e097f86b5e0c56421
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+
+@include version.itexi
+
+@c Translators: Yoshiki Sawada
+
+@c Don't replace quotes with directed quotes.
+
+@set txicodequoteundirected
+@set txicodequotebacktick
+
+
+
+@c ***** Displaying text *****
+
+@c We need this since @q{\} doesn't work with makeinfo 4.11 --
+@c say @q{@bs{}} instead.
+
+@macro bs
+\\
+@end macro
+
+@macro hash
+\#
+@end macro
+
+@c To get decent quotes in `foo' and ``foo''.
+@c FIXME: Use thin spaces for @qq.
+
+@ifnotinfo
+
+@macro q{TEXT}
+@quoteleft{}\TEXT\@quoteright{}
+@end macro
+
+@macro qq{TEXT}
+@quotedblleft{}\TEXT\@quotedblright{}
+@end macro
+
+@end ifnotinfo
+
+@ifinfo
+
+@macro q{TEXT}
+`\TEXT\'
+@end macro
+
+@macro qq{TEXT}
+« \TEXT\ »
+@end macro
+
+@end ifinfo
+
+
+@ifhtml
+
+@macro warning{TEXT}
+@cartouche
+@b{Note:} \TEXT\
+@end cartouche
+@end macro
+
+@end ifhtml
+
+@ifnothtml
+
+@macro warning{TEXT}
+@quotation
+@quotation
+@cartouche
+@b{Note:} \TEXT\
+@end cartouche
+@end quotation
+@end quotation
+@end macro
+
+@end ifnothtml
+
+
+@ifnotinfo
+
+@macro notation{TEXT}
+@var{\TEXT\}
+@end macro
+
+@end ifnotinfo
+
+@ifinfo
+
+@macro notation{TEXT}
+\TEXT\
+@end macro
+
+@end ifinfo
+
+
+@macro smallspace
+@sp 1
+@end macro
+
+
+
+@c ***** Displaying images not generated by lilypond-book *****
+
+@c Current installation setup of Info docs requires that all images are
+@c expected to be found in the `lilypond/' subdirectory. `lilypond-book'
+@c already generates proper @image commands for images of music; these
+@c macro definitions do the same for other images.
+
+@ifnotinfo
+
+@macro sourceimage{FILENAME,WIDTH,HEIGHT,ALTTEXT}
+@image{\FILENAME\,\WIDTH\,\HEIGHT\,\ALTTEXT\}
+@end macro
+
+@end ifnotinfo
+
+@ifinfo
+
+@macro sourceimage{FILENAME,WIDTH,HEIGHT,ALTTEXT}
+@image{lilypond/\FILENAME\,\WIDTH\,\HEIGHT\,\ALTTEXT\}
+@end macro
+
+@end ifinfo
+
+
+
+@c ***** Headings in a doc subsection *****
+
+@c Don't insert an empty line after @predefined! Right now
+@c it doesn't matter, but a future implementation will probably
+@c add some code which needs this restriction.
+
+@macro predefined
+@noindent
+@subsubheading Predefined commands
+@end macro
+
+@c The next macro is a dummy currently since texinfo doesn't
+@c provide a real ragged-right environment yet.
+@c
+@c Due to a bug in texi2html (texi2html.pl CVS versions <= 1.245)
+@c the macro must not be empty.
+
+@macro endpredefined
+@c
+@end macro
+
+
+@macro snippets
+@noindent
+@subsubheading Selected Snippets
+@end macro
+
+
+@c Don't insert an empty line after @seealso! Otherwise we get
+@c unwanted extra vertical space in the PDF output.
+
+@macro seealso
+@noindent
+@subsubheading See also
+@indent
+@end macro
+
+
+@macro knownissues
+@noindent
+@subsubheading Known issues and warnings
+@end macro
+
+
+@macro lydoctitle {TEXT}
+@emph{\TEXT\}
+@end macro
+
+
+@c Don't remove the `@c' within the macro definition! See section 19.3,
+@c `Macro Details and Caveats', in the texinfo info file for explanation.
+
+@macro funindex {TEXT}
+@findex \TEXT\
+@kindex \TEXT\
+@c
+@end macro
+
+
+
+@c ***** Links and references *****
+
+@c Definitions for references:
+@c
+@c @rglos
+@c @rlearning
+@c @ruser
+@c @rprogram
+@c @rlsr
+@c @rinternals
+@c
+@c All these also have a @...named version which allows to specify the
+@c displayed text for the reference as second argument.
+@c
+@c ***** HTML + bigpage is a special case (other manual names); all other
+@c formats are treated similarly.
+
+
+@c *** not TeX ***
+
+@ifnottex
+
+@c ** bigpage **
+
+@ifset bigpage
+
+@macro rglos{TEXT}
+@vindex \TEXT\
+@ref{\TEXT\,,,music-glossary-big-page,Music Glossary}
+@end macro
+
+@macro rglosnamed{TEXT,DISPLAY}
+@vindex \TEXT\
+@ref{\TEXT\,,\DISPLAY\,music-glossary-big-page,Music Glossary}
+@end macro
+
+@macro rlearning{TEXT}
+@vindex \TEXT\
+@ref{\TEXT\,,,lilypond-learning-big-page,Learning Manual}
+@end macro
+
+@macro rlearningnamed{TEXT,DISPLAY}
+@vindex \TEXT\
+@ref{\TEXT\,,\DISPLAY\,lilypond-learning-big-page,Learning Manual}
+@end macro
+
+@macro ruser{TEXT}
+@vindex \TEXT\
+@ref{\TEXT\,,,lilypond-big-page,Notation Reference}
+@end macro
+
+@macro rusernamed{TEXT,DISPLAY}
+@vindex \TEXT\
+@ref{\TEXT\,,\DISPLAY\,lilypond-big-page,Notation Reference}
+@end macro
+
+@macro rprogram{TEXT}
+@vindex \TEXT\
+@ref{\TEXT\,,,lilypond-program-big-page,Application Usage}
+@end macro
+
+@macro rprogramnamed{TEXT,DISPLAY}
+@vindex \TEXT\
+@ref{\TEXT\,,\DISPLAY\,lilypond-program-big-page,Application Usage}
+@end macro
+
+@macro rlsr{TEXT}
+@ref{\TEXT\,,,lilypond-snippets-big-page,Snippets}
+@end macro
+
+@macro rlsrnamed{TEXT,DISPLAY}
+@ref{\TEXT\,,\DISPLAY\,lilypond-snippets-big-page,Snippets}
+@end macro
+
+@macro rinternals{TEXT}
+@vindex \TEXT\
+@ref{\TEXT\,,,lilypond-internals-big-page,Internals Reference}
+@end macro
+
+@macro rinternalsnamed{TEXT,DISPLAY}
+@vindex \TEXT\
+@ref{\TEXT\,,\DISPLAY\,lilypond-internals-big-page,Internals Reference}
+@end macro
+
+@end ifset
+
+
+@c ** not bigpage **
+
+@ifclear bigpage
+
+@macro rglos{TEXT}
+@vindex \TEXT\
+@ref{\TEXT\,,,music-glossary,Music Glossary}
+@end macro
+
+@macro rglosnamed{TEXT,DISPLAY}
+@vindex \TEXT\
+@ref{\TEXT\,,\DISPLAY\,music-glossary,Music Glossary}
+@end macro
+
+@macro rlearning{TEXT}
+@vindex \TEXT\
+@ref{\TEXT\,,,lilypond-learning,Learning Manual}
+@end macro
+
+@macro rlearningnamed{TEXT,DISPLAY}
+@vindex \TEXT\
+@ref{\TEXT\,,,lilypond-learning,Learning Manual}
+@end macro
+
+@macro ruser{TEXT}
+@vindex \TEXT\
+@ref{\TEXT\,,,lilypond,Notation Reference}
+@end macro
+
+@macro rusernamed{TEXT,DISPLAY}
+@vindex \TEXT\
+@ref{\TEXT\,,\DISPLAY\,lilypond,Notation Reference}
+@end macro
+
+@macro rprogram{TEXT}
+@vindex \TEXT\
+@ref{\TEXT\,,,lilypond-program,Application Usage}
+@end macro
+
+@macro rprogramnamed{TEXT,DISPLAY}
+@vindex \TEXT\
+@ref{\TEXT\,,\DISPLAY\,lilypond-program,Application Usage}
+@end macro
+
+@macro rlsr{TEXT}
+@ref{\TEXT\,,,lilypond-snippets,Snippets}
+@end macro
+
+@macro rlsrnamed{TEXT,DISPLAY}
+@ref{\TEXT\,,\DISPLAY\,lilypond-snippets,Snippets}
+@end macro
+
+@macro rinternals{TEXT}
+@vindex \TEXT\
+@ref{\TEXT\,,,lilypond-internals,Internals Reference}
+@end macro
+
+@macro rinternalsnamed{TEXT,DISPLAY}
+@vindex \TEXT\
+@ref{\TEXT\,,\DISPLAY\,lilypond-internals,Internals Reference}
+@end macro
+
+@end ifclear
+
+@end ifnottex
+
+
+@c *** TeX ***
+
+@iftex
+
+@macro rglos{TEXT}
+@vindex \TEXT\
+@ref{\TEXT\,,,music-glossary,Music Glossary}
+@end macro
+
+@macro rglosnamed{TEXT,DISPLAY}
+@vindex \TEXT\
+@ref{\TEXT\,,\DISPLAY\,music-glossary,Music Glossary}
+@end macro
+
+@macro rlearning{TEXT}
+@ref{\TEXT\,,,lilypond-learning,Learning Manual}
+@end macro
+
+@macro rlearningnamed{TEXT,DISPLAY}
+@ref{\TEXT\,,\DISPLAY\,lilypond-learning,Learning Manual}
+@end macro
+
+@macro ruser{TEXT}
+@ref{\TEXT\,,,lilypond,Notation Reference}
+@end macro
+
+@macro rusernamed{TEXT,DISPLAY}
+@ref{\TEXT\,,\DISPLAY\,lilypond,Notation Reference}
+@end macro
+
+@macro rprogram{TEXT}
+@ref{\TEXT\,,,lilypond-program,Application Usage}
+@end macro
+
+@macro rprogramnamed{TEXT,DISPLAY}
+@ref{\TEXT\,,\DISPLAY\,lilypond-program,Application Usage}
+@end macro
+
+@macro rlsr{TEXT}
+@ref{\TEXT\,,,lilypond-snippets,Snippets}
+@end macro
+
+@macro rlsrnamed{TEXT,DISPLAY}
+@ref{\TEXT\,,\DISPLAY\,lilypond-snippets,Snippets}
+@end macro
+
+@macro rinternals{TEXT}
+@vindex \TEXT\
+@ref{\TEXT\,,,lilypond-internals,Internals Reference}
+@end macro
+
+@macro rinternalsnamed{TEXT,DISPLAY}
+@vindex \TEXT\
+@ref{\TEXT\,,\DISPLAY\,lilypond-internals,Internals Reference}
+@end macro
+
+@end iftex
+
+
+
+
+
+@c ***** Macros specific to translated docs *****
+
+@c ugh, cannot set/define global variable 'translationof' in some way?
+
+@iftex
+
+@macro translationof{TEXT}
+@end macro
+
+@end iftex
+
+@ifinfo
+
+@macro translationof{TEXT}
+@set translationof \TEXT\
+@end macro
+
+@end ifinfo
+
+
+@c TODO: If @translationof is used in translated docs
+@c see whether it is feasible to say @value{translationof}.
+
+@macro englishref
+Cette section n'est pas encore encore traduite, veuillez
+vous reporter à la documentation correspondante en anglais.
+@end macro
+
+
+@ifhtml
+
+@ifset bigpage
+@macro untranslated
+@end macro
+@end ifset
+
+@ifclear bigpage
+@macro untranslated
+UNTRANSLATED NODE: IGNORE ME
+@end macro
+@end ifclear
+
+@end ifhtml
+
+@ifnothtml
+
+@macro untranslated
+@end macro
+
+@end ifnothtml
@documentlanguage en
@afourpaper
+@dircategory GNU LilyPond --- the music typesetter
+@direntry
+* LilyPond Learning Manual: (lilypond-learning). Start here.
+@end direntry
+
@macro manualIntro
This file provides an introduction to LilyPond version
@version{}.
@documentlanguage en
@afourpaper
+@dircategory GNU LilyPond --- the music typesetter
+@direntry
+* Music Glossary: (music-glossary). For non-English users.
+@end direntry
+
@macro manualIntro
This glossary provides definitions and translations of musical
terms used in the documentation manuals for LilyPond version
@documentlanguage nl
@afourpaper
+@dircategory GNU LilyPond --- the music typesetter
+@direntry
+* LilyPond Learning Manual: (lilypond-learning). Start here.
+@end direntry
+
@macro manualIntro
This file provides an introduction to LilyPond version
@version{}.
@documentlanguage en
@afourpaper
+@dircategory GNU LilyPond --- the music typesetter
+@direntry
+* LilyPond: (lilypond-notation). LilyPond Notation Reference.
+@end direntry
+
@macro manualIntro
This manual provides a reference for all notation that can be
produced with LilyPond version @version{}. It assumes that
@documentlanguage en
@afourpaper
+@dircategory GNU LilyPond --- the music typesetter
+@direntry
+* LilyPond Snippets: (lilypond-snippets). Short tricks, tips, and examples.
+@end direntry
+
@macro manualIntro
This document shows a selected set of LilyPond snippets from the
@uref{http://lsr@/.dsi@/.unimi@/.it,LilyPond Snippet Repository}
@documentlanguage en
@afourpaper
+@dircategory GNU LilyPond --- the music typesetter
+@direntry
+* LilyPond Application Usage: (lilypond-usage). Installing and running applications.
+* lilypond: (lilypond-usage)Running lilypond. Invoking the LilyPond program.
+* abc2ly: (lilypond-usage)Invoking abc2ly. Importing ABC.
+* convert-ly: (lilypond-usage)Updating files with convert-ly. Older LilyPond versions.
+* etf2ly: (lilypond-usage)Invoking etf2ly. Importing Finale.
+* lilypond-book: (lilypond-usage)lilypond-book. Integrating text and music.
+* midi2ly: (lilypond-usage)Invoking midi2ly. Importing MIDI.
+* musicxml2ly: (lilypond-usage)Invoking musicxml2ly. Importing MusicXML.
+@end direntry
+
@macro manualIntro
This file explains how to execute the programs distributed with
LilyPond version @version{}. In addition, it suggests some
@c expected to be found in lilypond/ subdirectory.
@dircategory GNU LilyPond --- the music typesetter
@direntry
-* LilyPond Learning Manual: (lilypond-learning). Start here.
-* Music Glossary: (music-glossary). For non-English users.
-* LilyPond: (lilypond-notation). LilyPond Notation Reference.
-* LilyPond Snippets: (lilypond-snippets). Short tricks, tips, and examples.
* LilyPond Internals Reference: (lilypond-internals). Definitions for tweaking.
-* LilyPond Application Usage: (lilypond-usage). Installing and running applications.
* LilyPond Website: (lilypond-web). Preview of new website.
-* lilypond: (lilypond-usage)Running lilypond. Invoking the LilyPond program.
-* abc2ly: (lilypond-usage)Invoking abc2ly. Importing ABC.
-* convert-ly: (lilypond-usage)Updating files with convert-ly. Older LilyPond versions.
-* etf2ly: (lilypond-usage)Invoking etf2ly. Importing Finale.
-* lilypond-book: (lilypond-usage)lilypond-book. Integrating text and music.
-* midi2ly: (lilypond-usage)Invoking midi2ly. Importing MIDI.
-* musicxml2ly: (lilypond-usage)Invoking musicxml2ly. Importing MusicXML.
@end direntry
| z8k-* | z80-*)
;;
# Recognize the basic CPU types without company name, with glob match.
+ xtensa*)
+ basic_machine=$basic_machine-unknown
+ ;;
+ # Recognize the basic CPU types without company name, with glob match.
xtensa*)
basic_machine=$basic_machine-unknown
;;
basic_machine=tile-unknown
os=-linux-gnu
;;
+ tic55x | c55x*)
+ basic_machine=tic55x-unknown
+ os=-coff
+ ;;
+ tic6x | c6x*)
+ basic_machine=tic6x-unknown
+ os=-coff
+ ;;
+ tile*)
+ basic_machine=tile-unknown
+ os=-linux-gnu
+ ;;
tx39)
basic_machine=mipstx39-unknown
;;
--- /dev/null
+lilypond for Debian
+-------------------
+
+Dear music lover:
+
+ Welcome to the wonderful world of music typesetting! ^_^
+ This is the Debian package of GNU LilyPond.
+ Hope you enjoy producing beautiful music scores with GNU LilyPond
+ and other related packages! ^_^
+
+ Note:
+ If you experience problems about missing EC fonts during the TeX run,
+ please make sure you have the tetex-extra package installed.
+
+Old LilyPond Fonts Issue:
+~~~~~~~~~~~~~~~~~~~~~~~~~
+
+ If you installed the lilypond_0.1.48-1 or previous versions of the
+ Debian GNU LilyPond package, please note the following:
+
+ LilyPond comes with its own MF fonts starting with version 0.1.12.
+
+ The old lilypond fonts were not listed in
+ /usr/lib/texmf/fontname/special.map (from the teTeX 0.4 package),
+ therefore the fonts were created in a non-standard directory
+ somewhere under /var/spool/texmf. The problem was usually only
+ aesthetic. TeTeX could create and find the *.tfm and *.pk files
+ without any problems.
+
+ However, if you experience any font problems (such as the note
+ heads not showing up, characters in the wrong places, error
+ messages from TeX), especially after upgrading to a new version of
+ LilyPond, you may need to delete the relevant *.tfm and *.pk files
+ under the directory /var/spool/texmf. You may also file a bug
+ report about this if you like.
+
+ Nonetheless, GNU LilyPond now comes with the standard "feta" fonts,
+ and they are already listed in the latest teTeX 0.9 / Web2C 7.2
+ /usr/share/texmf/fontname/special.map file, so there shouldn't be any
+ more problems! Enjoy! :-)
+
+
+Anthony Fok <foka@debian.org>, Wed, 7 Jul 1999 15:19:48 -0600
--- /dev/null
+lilypond (2.16.2-3) unstable; urgency=low
+
+ * Do not include non-existant paths in lilypond-doc.doc-base-special
+ (closes: #693238)
+ * Breaks/Replaces lilypond-doc in html packages to stop problems on
+ wheezy upgrade. (Closes: #718013)
+ * Fix freetype path by applying patch from upstream (Closes: #733399)
+ * Fix bison build failures with 42cb7d44
+
+ -- Don Armstrong <don@debian.org> Tue, 31 Dec 2013 09:44:05 -0800
+
+lilypond (2.16.2-2) unstable; urgency=low
+
+ * Fix bad syntax in texinfo documentation exposed by texinfo >= 5.1
+ (closes: #707190)
+ * Patch around using PATH_MAX in flower/file-name.cc to have builds work
+ on hurd (hopefully).
+
+ -- Don Armstrong <don@debian.org> Wed, 15 May 2013 11:40:14 -0700
+
+lilypond (2.16.2-1) unstable; urgency=low
+
+ * Release 2.16.2-1 to unstable
+
+ -- Don Armstrong <don@debian.org> Mon, 06 May 2013 10:15:36 -0700
+
+lilypond (2.16.2-1~exp+1) experimental; urgency=low
+
+ * New upstream release (closes: #705895)
+ * Put languages in their own subdocument to work around doc-base not
+ having a language specifier (closes: #698435)
+
+ -- Don Armstrong <don@debian.org> Wed, 24 Apr 2013 21:53:13 -0700
+
+lilypond (2.16.1-1~exp+2) experimental; urgency=low
+
+ * New upstream release
+ * netpbm and fonts are required to run the tests during the binary
+ build; migrate the Build-Depends-Indep to Build-Depends.
+ * Switch to dh style rules
+
+ -- Don Armstrong <don@debian.org> Tue, 02 Oct 2012 17:33:29 -0700
+
+lilypond (2.16.0-1~exp+1) experimental; urgency=low
+
+ * New upstream release (Closes: #686788)
+ * Fix "warnings from install-info" by splitting the direntry sections
+ across the texinfo files (Closes: #648689). Thanks to Julian Gilbey
+ for the patch.
+ * Fix noopt support to use --disable-optimising as ./configure does
+ crazy things.
+ * Apply patch from 13fc2437e2aaa9 to fix segfault in font-mark where a
+ garbage collection can trigger a null pointer dereference (closes:
+ #684817)
+ * Split out lilypond-doc packages (Closes: #443915)
+
+ -- Don Armstrong <don@debian.org> Tue, 04 Sep 2012 11:16:50 -0700
+
+lilypond (2.14.2-3) unstable; urgency=low
+
+ * Fix redefinition of s in Music_sequence::first_start. (Closes:
+ #672087).
+
+ -- Don Armstrong <don@debian.org> Sun, 13 May 2012 16:07:16 -0700
+
+lilypond (2.14.2-2) unstable; urgency=low
+
+ * Disable optimization on i386 and kfreebsd-i386 to avoid segfaults with
+ python7; thanks to Matthias Klose and Scott Kitterman for the
+ temporary solution. (Closes: #643664)
+
+ -- Don Armstrong <don@debian.org> Wed, 28 Sep 2011 09:44:40 -0700
+
+lilypond (2.14.2-1) unstable; urgency=low
+
+ * New upstream release (Closes: #629520)
+ * Fix bad Recommends on texlive-latex-base (Closes: #594403)
+ * Ditch useless links (Closes: #522120)
+ * Apply patch from 77c34ddc (Werner Lemberg <wl@gnu.org>)
+ to fix compilation with g++ 4.5 (Closes: #606642).
+ Thanks to Colin Watson for an alternative patch.
+ * Add parts of patch f113bf2f (Benjamin Peterson <benjamin@python.org>)
+ to fix segfaults on invalid engraver names.
+ * Update standards version; no changes
+ * Specify source version 1
+ * No need to conflict with ancient versions of lilypond anymore
+
+ -- Don Armstrong <don@debian.org> Tue, 02 Aug 2011 13:14:29 -0700
+
+lilypond (2.12.3-7) unstable; urgency=low
+
+ * Use /dev/stderr instead of /dev/tty (Closes: #574629)
+ * Use py_support to require rebuilds when python's API changes (Closes:
+ #380855)
+ * Properly remove empty /usr/share/info/lilypond directory and replace
+ with symlink
+
+ -- Don Armstrong <don@debian.org> Tue, 24 Aug 2010 15:52:59 -0700
+
+lilypond (2.12.3-6) unstable; urgency=low
+
+ * Fix syntax error in scm/lily.scm. Thanks to dann frazier for pointing
+ out the fix. (Closes: #574629)
+ * Depend on ghostscript (Closes: #575906)
+
+ -- Don Armstrong <don@debian.org> Wed, 31 Mar 2010 20:57:04 -0700
+
+lilypond (2.12.3-5) unstable; urgency=low
+
+ * Its guile that's being used, not MIT scheme; use access? instead of
+ file-writable? (Closes: #572290)
+
+ -- Don Armstrong <don@debian.org> Thu, 04 Mar 2010 23:38:32 -0800
+
+lilypond (2.12.3-4) unstable; urgency=low
+
+ * Scheme uses file-writeable for some reason (Closes: #572290)
+
+ -- Don Armstrong <don@debian.org> Thu, 04 Mar 2010 08:38:33 -0800
+
+lilypond (2.12.3-3) unstable; urgency=low
+
+ * Use /dev/null if /dev/tty isn't writable (Closes: #572290)
+
+ -- Don Armstrong <don@debian.org> Wed, 03 Mar 2010 17:56:55 -0800
+
+lilypond (2.12.3-2) unstable; urgency=low
+
+ * Build-Depend on rsync (Closes: #571670)
+ * Ditch unneded Build-Conflict
+
+ -- Don Armstrong <don@debian.org> Fri, 26 Feb 2010 17:32:22 -0800
+
+lilypond (2.12.3-1) unstable; urgency=low
+
+ * New upstream release
+ - Ditch claop.py (Closes: #545911)
+ - fix FTBFS (Closes: #560487)
+ * Always suppress gs startup output
+ * Build-Depend on texlive-latex-recommended
+ * Move Pre-Depends: for kpsewhich to Depends: (we no longer ship a preinst)
+ * Update standards version
+ - Stop calling install-info directly; use triggers instead
+
+ -- Don Armstrong <don@debian.org> Tue, 23 Feb 2010 00:12:21 -0800
+
+lilypond (2.12.2-1) unstable; urgency=low
+
+ * New maintainer
+ * Use patches from Raphael Geissert to fix bashism and remove path to
+ commands
+ - Fix bashism in debian/rules. Closes: #535404
+ - Remove the path to the commands in the maintainer scripts
+
+ -- Don Armstrong <don@debian.org> Wed, 08 Jul 2009 16:01:06 -0700
+
+lilypond (2.12.2-0.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * New upstream release (closes: #506936)
+ - Resolves issue with guile 1.8.6 (closes: #524023)
+ - Fixes FTBFS (closes: #524086)
+ * Remove build-coonflicts indep on gs-gpl as the conflicting versions
+ aren't distributed anymore
+ * Remove versioned build dependencies (all of the requirements are older
+ than the oldest we distribute)
+ * Add Build-Depends on texi2html and texlive-metapost
+ * Move Homepage: to a control header (closes: #474262)
+ * Add ja/user/macros.texi and python/langdefs from git commit
+ 4ee200780114be081a73cae3f7bf6bbc84a30b53 (Allows building the ja texi
+ documentation)
+
+ -- Don Armstrong <don@debian.org> Sat, 06 Jun 2009 13:49:11 -0700
+
+lilypond (2.10.33-2.3) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Fix double build problem as patched by Peter Eisentraut
+ <petere@debian.org> (Closes: #482911).
+ * Do not list transitional package first in Pre-Depends
+ line (Closes: #481776).
+ * Changed build dependency from gs-gpl|gs-esp to ghostscript
+ to not reference transitional packages.
+
+ -- Michael Meskes <meskes@debian.org> Sun, 05 Oct 2008 13:48:20 +0200
+
+lilypond (2.10.33-2.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix FTBFS with dash (Closes: #471757).
+
+ -- Peter Eisentraut <petere@debian.org> Sun, 25 May 2008 03:27:26 +0200
+
+lilypond (2.10.33-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix FTBFS with GCC 4.3 (Closes: #413427).
+ * Copy config.{guess,sub} to fix FTBFS on GNU/kFreeBSD (Closes: #404441).
+
+ -- Luk Claes <luk@debian.org> Sat, 08 Mar 2008 13:43:35 +0000
+
+lilypond (2.10.33-2) unstable; urgency=low
+
+ * debian/control (Build-Depends-Indep): Use ttf-dejavu instead of
+ ttf-bitstream-vera. (Closes: #461271)
+
+ * debian/control (Standards-Version): Update to 3.7.3. (No changes needed.)
+
+ * debian/rules (clean): Don't ignore all errors on recursive make invocations.
+
+ * debian/rules (binary-indep): Use $(CURDIR) instead of $(PWD).
+
+ * debian/copyright: Update FSF address to Franklin St.
+
+ * debian/changelog: Fix syntax for trailer line for 2.8.7-3.1 record.
+
+ -- Thomas Bushnell, BSG <tb@debian.org> Thu, 17 Jan 2008 10:24:27 -0800
+
+lilypond (2.10.33-1) unstable; urgency=low
+
+ * New upstream release.
+
+ * debian/control (lilypond Depends): Use source:Version instead of
+ Source-Version.
+ (lilypond-doc Suggests): Likewise.
+ (lilypond-data Recommends): Likewise, but with >= in place of = as well.
+ (Closes: #380071). Thanks to Lior Kaplan for the patch.
+
+ -- Thomas Bushnell, BSG <tb@debian.org> Wed, 02 Jan 2008 10:11:04 -0700
+
+lilypond (2.10.29-2) unstable; urgency=low
+
+ * debian/control: Drop gs-afpl from Build-Conflicts-Indep, since that package
+ no longer exists. (Closes: #447460).
+ * debian/control: Build-Conflict with guile-1.8-dev version 1.8.2+1-2,
+ which had an ABI-incompatible change by mistake. Likewise, lilypond
+ package Conflicts with guile-1.8 version 1.8.2+1-2. (Closes: #452647)
+
+ -- Thomas Bushnell, BSG <tb@debian.org> Fri, 30 Nov 2007 22:20:42 -0500
+
+lilypond (2.10.29-1) unstable; urgency=low
+
+ * New upstream release. Require at least version 1.1.19 of mftrace.
+ Require at least version 2.4 of python-dev. (Closes: #396889,
+ #399356, #400335)
+ * debian/control (Build-Depends-Indep): Add rsync.
+
+ * Acknowledge NMU (Closes: #422395).
+
+ -- Thomas Bushnell, BSG <tb@debian.org> Sat, 08 Sep 2007 20:08:21 -0400
+
+lilypond (2.8.7-3.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * FTBFS: ! I cannot find file 'lcircle10'. (Closes: #422395)
+
+ -- Neil Williams <codehelp@debian.org> Tue, 17 Jul 2007 12:59:43 +0100
+
+lilypond (2.8.7-3) unstable; urgency=medium
+
+ * scripts/midi2ly.py: When setting DATADIR, find Lilypond python files
+ in the @TOPLEVEL_VERSION@ directory, not 'current'. Patch thanks to
+ Chris Lamb (chris@chris-lamb.co.uk). (Closes: #400550)
+
+ -- Thomas Bushnell, BSG <tb@debian.org> Tue, 19 Dec 2006 10:18:12 -0800
+
+lilypond (2.8.7-2) unstable; urgency=low
+
+ * debian/control (Build-Depends-Indep): Drop gs alternative for
+ Ghostscript. Move gs-gpl | gs-esp to Build-Depends.
+ (Build-Depends): Put gs-gpl | gs-esp here; require at least version
+ 8.50 of either. Require version 2.1 at least of python-dev.
+
+ -- Thomas Bushnell, BSG <tb@debian.org> Sat, 11 Nov 2006 21:11:48 -0800
+
+lilypond (2.8.7-1) unstable; urgency=low
+
+ * New upstream release. (Closes: #357057, #358663)
+ * debian/control (Build-Depends): Require at least version
+ 0.0.20060125-1 of fontforge. Require at least version 4.8.dfsg.1-1 of
+ texinfo. Require guile-1.8-dev instead of guile-1.6-dev.
+ * debian/control (Build-Depends-Indep): Require gsfonts | gsfonts-x11 to
+ fetch New Century Schoolbook fonts.
+ * debian/control (lilypond/Depends): Require guile-1.8 instead of guile-1.6.
+ * debian/rules (install): Don't delete texinfo.tex anymore, upstream is
+ no longer shipping it.
+
+ * debian/control (Build-Depends): Add libgmp3-dev and libltdl3-dev,
+ temporarily. to workaround missing dependencies in guile-1.8-dev.
+
+ * debian/control (lilypond-data/Pre-Depends): Allow texlive-base as an
+ alternative to tetex-bin. (Closes: #386589)
+
+ -- Thomas Bushnell, BSG <tb@debian.org> Wed, 25 Oct 2006 23:26:15 -0700
+
+lilypond (2.6.5-3) unstable; urgency=medium
+
+ * debian/rules (install): Don't install .pyc files.
+ * debian/control (Build-Depends): Require python-support and at least
+ version 5 of debhelper.
+ (lilypond-data/Depends): Add ${python:Depends}.
+ * debian/rules (binary-indep): Call dh_pysupport on our private modules
+ directory. (Closes: #392488)
+
+ * debian/compat: Bump to version 5.
+
+ -- Thomas Bushnell, BSG <tb@debian.org> Thu, 12 Oct 2006 11:59:58 -0700
+
+lilypond (2.6.5-2) unstable; urgency=low
+
+ * debian/rules (HOME): Set this environment variable to a usable value
+ to avoid a fontconfig buglet.
+
+ -- Thomas Bushnell, BSG <tb@debian.org> Mon, 18 Sep 2006 23:01:35 -0700
+
+lilypond (2.6.5-1) unstable; urgency=low
+
+ * New upstream release. Lilypond 2.8 for Debian is currently stalled
+ because guile-1.8 is required for it, and the Debian builds of
+ guile-1.8 are encountering bugs. So let's at least get the last
+ lilypond-2.6 into etch in case guile-1.8 doesn't get there in time.
+ * stepmake/bin/config.sub, stepmake/bin/config.guess: Use debian
+ versions, from autotools-dev 20060702.1.
+
+ * lily/include/accidental-interface.hh (Accidental_interface): Declare
+ member accurate_boxes without qualification.
+ * lily/include/stem.hh (Stem): Declare member beam_multiplicity without
+ qualification.
+ * lily/include/slur-scoring.hh (Slur_score_state): Declare member
+ generate_avoid_offsets without qualification.
+ (Thanks to Martin Michlmayr <tbm@cyrius.com> for the patch.)
+ (Closes: #357057, #387644)
+
+ * mf/GNUmakefile (pfa_warning): Select only the first line of mftrace
+ --version output for mftrace check, since mftrace now prints more than
+ just one line.
+
+ * debian/control (Build-Depends-Indep): Add ttf-bitstream-vera and
+ ttf-freefont. (Many thanks to Bill Allombert <allomber@math.u-bordeaux>
+ for the fix.) (Closes: #359855)
+
+ * debian/control (Build-Depends): Require at least version 2.4.1-1 of
+ libfontconfig1-dev; 2.4.0 was missing FcConfigAppFontAddDir, which we
+ need.
+
+ * debian/rules (binary-indep): Don't symlink logos anymore.
+
+ -- Thomas Bushnell, BSG <tb@debian.org> Thu, 7 Sep 2006 22:34:19 -0700
+
+lilypond (2.6.3-10) unstable; urgency=low
+
+ * debian/control (Build-Depends): Drop explicit dependency on
+ g++-3.4.
+ * debian/rules: No longer set CXX demanding g++-3.4 on certain
+ archs. (Closes: #343007)
+
+ * debian/lilypond-data.postrm: Don't set TEXMFMAIN at all (it isn't
+ used). Don't try and set VARTEXFONTS if $1 is "purge". Don't remove
+ fonts on a purge command; it gets done at remove time and that's
+ sufficient. (All this is necessary because postrm scripts cannot
+ depend on non-essential packages at purge time.) (Closes: #325907)
+
+ * debian/control (lilypond-data): Pre-Depends on tetex-bin to make sure
+ kpsewhich is available for the maintainer scripts. (Closes: #336052,
+ #343182, #335847).
+
+ * debian/control (Build-Depends): No longer accept libguile-dev for
+ guile support, and require at least version 1.6.7 of guile-1.6-dev.
+ (lilypond): Likewise here, require version 1.6.7 of guile-1.6.
+ (Closes: #337597)
+
+ * debian/control (lilypond): Spell "seamlessly" correctly. (Closes:
+ #327675)
+
+ -- Thomas Bushnell, BSG <tb@debian.org> Fri, 13 Jan 2006 12:59:15 -0800
+
+lilypond (2.6.3-9) unstable; urgency=low
+
+ * Packaging suggestions from upstream:
+ * debian/control (Build-Depends): Drop ec-fonts-mftraced,
+ libkpathsea-dev, tetex-bin, tetex-extra.
+ (Build-Depends-Indep): Add emacs-intl-fonts, xfonts-intl-arabic,
+ xfonts-intl-asian, xfonts-intl-chinese, xfonts-intl-chinese-big,
+ xfonts-intl-european, xfonts-intl-japanese, xfonts-intl-japanese-big,
+ xfonts-intl-phonetic, ttf-kochi-gothic, ttf-kochi-mincho. (These
+ get embedded into the generated webpage.)
+ (lilypond): Don't depend on ec-fonts-mftraced, tetex-bin, or tetex-extra.
+ (lilypond-data): Don't depend on tetex-bin.
+
+ * debian/control (Build-Depends): Drop long-unneeded version dependency
+ on binutils and libc6-dev and its variants.
+
+ * debian/gui-2.6.patch: New file, provided by upstream. Applied, with
+ suitable massaging of ChangeLog.
+ * debian/rules, scm/lily.scm: Revert change from 2.6.3-7.
+
+ * debian/python-2.6.patch: New file, provided by upstream. Applied, with
+ suitable massaging of ChangeLog.
+ * debian/rules (install): Revert change from 3.6.3-6.
+
+ -- Thomas Bushnell, BSG <tb@debian.org> 23 Oct 2005 15:22:34 -0700
+
+lilypond (2.6.3-8) unstable; urgency=low
+
+ * Avoid GCC 4.0 bug on arm, hppa, and m68k.
+ * debian/control (Build-Depends): Add g++-3.4 on arm, hppa, and m68k.
+ * debian/rules: On arm, hppa, and m68k, use g++-3.4 for CXX.
+ (Closes: #335287)
+
+ -- Thomas Bushnell, BSG <tb@debian.org> Sat, 22 Oct 2005 23:18:36 -0700
+
+lilypond (2.6.3-7) unstable; urgency=low
+
+ * debian/rules (build, build-doc): Abandon attempts to have a terminal
+ set as stdin. Instead, set and export environment variable
+ LILYPONDNOGUI.
+ * scm/lily.scm (running-from-gui?): Return #f anytime LILYPONDNOGUI
+ environment variable is set. (Closes: #334877)
+
+ -- Thomas Bushnell, BSG <tb@debian.org> Sat, 22 Oct 2005 15:18:35 -0700
+
+lilypond (2.6.3-6) unstable; urgency=low
+
+ * debian/rules (install): Move midi.so from /usr/share into /usr/lib and
+ leave behind a symlink to find it.
+ * debian/lilypond.install: Add usr/lib.
+ (Closes: #335207)
+
+ * debian/rules (build, build-doc): Use screen to set up a tty for input
+ instead of relying on /dev/tty; that will work in more environments.
+ * debian/control (Build-Depends, Build-Depends-Indep): Add screen. Gak.
+
+ -- Thomas Bushnell, BSG <tb@debian.org> Sat, 22 Oct 2005 10:51:49 -0700
+
+lilypond (2.6.3-5) unstable; urgency=low
+
+ * debian/rules (build, build-doc): Redirect input from /dev/tty in MAKE
+ invocations. It seems that lilypond assumes that, if stdin is not a
+ terminal, we must be running under a gui. This changes the behavior
+ of the program in several fundamental ways, causing the scripts used
+ for generating documentation to fail. (Closes: #334877)
+
+ -- Thomas Bushnell, BSG <tb@debian.org> Fri, 21 Oct 2005 20:33:11 -0700
+
+lilypond (2.6.3-4) unstable; urgency=low
+
+ * debian/control (Build-Depends): Require libfreetype6-dev,
+ libpango1.0-dev, and libfontconfig-dev. Grr, I think this does it.
+
+ -- Thomas Bushnell, BSG <tb@debian.org> Wed, 19 Oct 2005 20:48:51 -0700
+
+lilypond (2.6.3-3) unstable; urgency=low
+
+ * debian/control (Build-Depends): Require pkg-config, at least version
+ 0.9.0.
+
+ * debian/control (Build-Depends): Accept libc0.1-dev (>= 2.2.4-6) as a
+ libc alternative.
+ * stepmake/bin/config.guess, stepmake/bin/config.sub: Use debian
+ versions, from autotools-dev 20050803.1. (Closes: #334786)
+
+ -- Thomas Bushnell, BSG <tb@debian.org> Wed, 19 Oct 2005 16:40:21 -0700
+
+lilypond (2.6.3-2) unstable; urgency=low
+
+ * debian/rules (clean): Don't fail if lib/python isn't hanging around.
+ (Closes: #334725).
+
+ -- Thomas Bushnell, BSG <tb@debian.org> Wed, 19 Oct 2005 09:41:10 -0700
+
+lilypond (2.6.3-1) unstable; urgency=low
+
+ * New upstream release. (Closes: #323526, #315970, #316125, #314242)
+ * upstream-debian: holds the "debian" directory that upstream insists on
+ packaging, and which makes updating versions a royal PITA. So we'll just
+ store what they do there, and then let them do what they want, and build
+ ourselves for the Debian way.
+ * debian/rules (binary-indep): No longer look for lilypond.map file or
+ install it.
+ * debian/lilypond-data.dirs: Drop etc/texmf/dvips.
+ * debian/watch: Look in the v2.6 download directory now.
+ * debian/lilypond.install: Don't worry about usr/lib anymore.
+ * debian/rules (binary-indep): No longer does upstream build PS docs, so
+ we no longer make symlinks to them.
+
+ * debian/control (clean): Remove annoying lib/python symlink.
+
+ * debian/control (lilypond): Update description to mention SVG.
+
+ * debian/control (lilypond1.3): Drop transitional package.
+ * debian/lilypond1.3.copyright: Remove file. (Closes: #308709)
+ * debian/control (lilypond): Don't conflict with lilypond1.3 or
+ musixtex-fonts anymore.
+
+ * debian/control (lilypond-data): Depend on texinfo | texlive-texinfo.
+ * debian/rules (install): Don't install texinfo.tex. (Closes: #322338)
+
+ * debian/control (Build-Depends): Require version 0.0.20050911-1 of
+ fontforge, or greater, to avoid crashes during building.
+
+ * debian/control (Build-Depends): Require at least version 1.1.17-1 of
+ mftrace, to avoid a gcc4-related bug that was only fixed in that version.
+
+ -- Thomas Bushnell, BSG <tb@debian.org> Tue, 18 Oct 2005 19:33:41 -0700
+
+lilypond (2.4.5-2) unstable; urgency=low
+
+ * debian/control (Build-Depends): Build system demands you have
+ ec-fonts-mftraced installed to build, so do it.
+
+ -- Thomas Bushnell, BSG <tb@debian.org> Fri, 8 Apr 2005 04:38:44 -0700
+
+lilypond (2.4.5-1) unstable; urgency=low
+
+ * New upstream release. (Closes: #285370, #296034, #300609)
+ * debian/control (Build-Depends): Remove fontforge, autotrace, t1utils,
+ imagemagick.
+ (Build-Depends-Indep): Add imagemagick.
+ (lilypond Depends): Add ec-fonts-mftraced.
+ * debian/rules (binary-indep): Get lilypond.map from its new location.
+
+ -- Thomas Bushnell, BSG <tb@debian.org> Thu, 7 Apr 2005 12:48:17 -0700
+
+lilypond (2.2.6-3) unstable; urgency=low
+
+ * New maintainer. (Closes: #278502).
+
+ * debian/control: Build-Depends on autotrace. (Closes: #289376).
+
+ * mf/GNUmakefile (.pfa generic rule): Use "--formats=pfa" instead of "--pfa."
+ * stepmake/metafont-rules.make: Likewise; also for .pfb generic rule.
+ * debian/control: Require at least version 1.1.5-1 of mftrace.
+
+ -- Thomas Bushnell, BSG <tb@debian.org> Mon, 14 Mar 2005 10:44:03 -0800
+
+lilypond (2.2.6-2.1) unstable; urgency=high
+
+ * Non-maintainer upload during BSP
+ * Version build-dep on fontforge, only newest upstream seems to be able to
+ build this package. Thanks Bastian Kleineidam <calvin@debian.org> for
+ fixing fontforge and suggesting this fix (Closes:#278502)
+
+ -- Jeroen van Wolffelaar <jeroen@wolffelaar.nl> Sat, 8 Jan 2005 19:54:27 +0100
+
+lilypond (2.2.6-2) unstable; urgency=high
+
+ * Added the Werner Lemberg's Asian scripts examples. He e-mailed me
+ and said, "I suggest that you add the two example files to the
+ Debian package also -- the mailing list archive of the lilypond
+ list shows garbage only (at least for me)." Yes, ditto here.
+ So yes, xiao-haizi-guai-guai.ly and sakura-sakura.ly are in! :-)
+ * The "-sDEVICE=bbox" bug has been fixed in gs-gpl (8.01-5), so I have
+ adjusted debian/control accordingly. (Note to self: Need to check
+ gs-afpl (8.14-3) to see if it too can be taken off the blacklist.)
+
+ -- Anthony Fok <foka@debian.org> Sun, 19 Sep 2004 06:39:07 +0800
+
+lilypond (2.2.6-1) unstable; urgency=high
+
+ * New upstream stable release. (Closes: Bug#264263)
+ * urgency=high to ensure entrance into Debian Sarge.
+ * Special thanks to Daniel Burrows for the previous NMUs! :-)
+ (Closes: #257335, #261861)
+ * Added patch by Werner Lemberg to lilypond.py so that Asian scripts
+ may be used with LilyPond. Need to "apt-get install latex-ucs"! See
+ http://lists.gnu.org/archive/html/lilypond-devel/2004-07/msg00071.html
+ * Thanks to Ferenc Wagner for letting me know of some packaging bugs
+ that I have introduced over the years:
+ - Removed obsolete MAKE_PFA_FILES=1 from "make" invocations.
+ - s/--enable-optimise/--enable-optimising/;
+ - Removed Build-Depends: autotrace; mftrace prefers potrace.
+ * Let's follow Han-wen's Red Hat SPECS file too: --disable-checking.
+
+ -- Anthony Fok <foka@debian.org> Thu, 26 Aug 2004 02:30:04 +0800
+
+lilypond (2.2.3-1.3) unstable; urgency=low
+
+ * The doc-base file was coming from upstream! Kill it dead in
+ debian/rules clean so that it doesn't keep coming back from
+ the grave to haunt me. (Closes: #261861)
+
+ -- Daniel Burrows <dburrows@debian.org> Mon, 2 Aug 2004 16:03:32 -0400
+
+lilypond (2.2.3-1.2) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Added Replaces: lilypond (<= 2.2.3-1), lilypond-data (<= 2.2.3-1) to
+ lilypond-doc. (Closes: #261861)
+
+ -- Daniel Burrows <dburrows@debian.org> Wed, 28 Jul 2004 13:08:57 -0400
+
+lilypond (2.2.3-1.1) unstable; urgency=low
+
+ * Non-maintainer upload
+ * Removed doc-base files for the lilypond and lilypond-data packages;
+ moved the description of the info files to the doc-base file of the
+ lilypond-doc package, which actually contains them; corrected the
+ location of the info files in the doc-base file. (Closes: #257335)
+
+ -- Daniel Burrows <dburrows@debian.org> Sat, 17 Jul 2004 12:55:57 -0400
+
+lilypond (2.2.3-1) unstable; urgency=low
+
+ * New upstream release.
+
+ -- Anthony Fok <foka@debian.org> Sun, 27 Jun 2004 16:53:06 +0800
+
+lilypond (2.2.2-2) unstable; urgency=low
+
+ * New upstream release. (Closes: Bug#242861)
+ - Thanks to Pedro Kroeger for providing interim sid packages while
+ I was away for an extended period of time.
+ * Copied some ideas from Ferenc Wagner's LilyPond for woody (Thanks!):
+ - Split out shared data to lilypond-data package. (Closes: Bug#233406)
+ - Make lilypond-data conflict with earlier lilypond versions.
+ - debian/control: Relaxed autotrace Build-Depends (>= 0.29).
+ - debian/control: Added imagemagick Build-Depends (>= 5.4.4.5).
+ * Added more details to lilypond package description. (Closes: Bug#245370)
+ * gs-gpl 8.01 (and gs-afpl 8.14) dies when building LilyPond docs.
+ (Known -sDEVICE=bbox bug in gs 8.01 and newer, see gs-gpl Bug#250290.)
+ Added Build-Conflict-Indep: gs-gpl (>= 8.01) | gs-afpl (Closes: Bug#250622)
+ * Build-Depends: fontforge | pfaedit.
+ * debian/watch: Updated to new URL and new format.
+ * vim/GNUmakefile: Install $(vimdir)/*/lilypond.vim scripts with "-m 644".
+
+ -- Anthony Fok <foka@debian.org> Fri, 18 Jun 2004 02:39:58 +0800
+
+lilypond (2.1.0-2) unstable; urgency=low
+
+ * A few HTML links in Documentation/user/{introduction,tutorial}.itely
+ went up one too few level in the directory tree, i.e. broken links.
+ Thanks to D. Raleigh Arnold for the bug report. (Closes: Bug#208208)
+ * Build-Depends: imagemagick; lilypond uses "convert" nowadays.
+ Thanks to Daniel Schepler for the bug report. (Closes: Bug#221062)
+
+ -- Anthony Fok <foka@debian.org> Wed, 19 Nov 2003 10:12:16 +0800
+
+lilypond (2.1.0-1) unstable; urgency=low
+
+ * New upstream release.
+ * Build-Requires: pfaedit (>= 0.0.20031020-3) to prevent FTBFS on alpha.
+ Thanks to Petter Reinholdtsen for the bug report, and thanks to
+ Peter Hawkins for adopting the PfaEdit package! (Closes: Bug#217216)
+ * Build process used to redirect to /dev/stderr which does not exist in
+ all environments. Upstream replaced it with ">&2" in 1.9.0 in August.
+ Thanks to Daniel Schepler for the bug report. (Closes: #215481)
+ * Added symlink from /usr/share/lilypond/$(VERSION)/fonts/type1 to
+ /usr/share/texmf/fonts/type1/public/lilypond. Thanks to Pedro Kroger
+ and Mats Bengtsson's discussion on the lilypond-devel:
+ http://mail.gnu.org/archive/html/lilypond-devel/2003-10/msg00016.html
+
+ -- Anthony Fok <foka@debian.org> Sat, 25 Oct 2003 19:34:41 +0800
+
+lilypond (1.8.1-1) unstable; urgency=low
+
+ * New upstream release.
+ * Thanks to Jan Nieuwenhuizen for the following fixes:
+ debian/control (Build-Depends): Add flex-old as alternative to flex.
+ Deprecate bison 1.75.
+
+ -- Anthony Fok <foka@debian.org> Wed, 27 Aug 2003 00:24:20 +0800
+
+lilypond (1.8.0-1) unstable; urgency=low
+
+ * New upstream release.
+
+ -- Anthony Fok <foka@debian.org> Wed, 13 Aug 2003 00:23:36 +0800
+
+lilypond (1.7.29-1) unstable; urgency=medium
+
+ * New upstream release, preparing for lilypond-1.8. :-)
+ * stepmake/bin/add-html-footer.py: Use LOGNAME only if it exists.
+ pbuilder unsets LOGNAME and Python returns KeyError.
+ Thanks to Daniel Schepler for the report. (Closes: Bug#193065)
+ * debian/rules: Revert to calling ./configure rather than ./autogen.sh.
+ * An issue with autoconf <= 2.57 and g++ >= 3.3 has been preventing
+ getopt-long.cc from compiling. A workaround was checked in by upstream
+ author Jan Nieuwenhuizen on 2003-06-08, and the fix in aclocal.m4 was
+ backported from 1.7.29. (Closes: Bug#197761)
+ * Mark Brown says 1.7.27 has fixed FTBFS on m86k too. Thanks for the
+ note! (Closes: Bug#200510)
+ * Run dh_scrollkeeper to register *.omf files.
+
+ -- Anthony Fok <foka@debian.org> Fri, 1 Aug 2003 05:40:04 +0800
+
+lilypond (1.6.9-2) unstable; urgency=medium
+
+ * CVS updates as of 2003-04-29. (Thanks, Jan!)
+ * "Empty midi2ly.1" problem has been fixed upstream. (Closes: Bug#181927)
+ * Build-Depends: autoconf2.13 and run autogen.sh in debian/rules
+ to ensure this package passes the auto-build daemons. :-)
+
+ -- Anthony Fok <foka@debian.org> Thu, 1 May 2003 13:18:57 +0800
+
+lilypond (1.6.9-1) unstable; urgency=medium
+
+ * New upstream release with CVS updates as of 2003-04-15.
+ Jan Nieuwenhuizen has backported fixes to deal with build problems
+ with flex (>= 2.5.29).
+ * Rebuild with guile-1.6 packages.
+ * Merged debian/* fixes by upstream author Jan Nieuwenhuizen (Thanks!):
+ - Depend on mftrace (>= 1.0.17-1) instead of pktrace.
+ - Add guile-1.6-dev as alternative dependency to libguile-dev
+ - Bugfix for docdir when with changed package name.
+ - Remove bibtex2html dependencies. (LilyPond has come with its own
+ bib2html for some time now. However, xpmtoppm and pnmtopng from
+ netpbm is still needed - foka)
+ - Remove gcc-3.x/lexer kludge.
+ * midi2ly.1 was empty because help2man calls midi2ly but it couldn't
+ "import midi": python/out/midi.so wasn't built until later. Added
+ a kludge in debian/rules to regenerate midi2ly.1 manually.
+ Thanks to Colin Watson for reporting the bug. (See Bug#181927)
+
+ -- Anthony Fok <foka@debian.org> Mon, 28 Apr 2003 03:50:50 +0800
+
+lilypond (1.6.6-2) unstable; urgency=high
+
+ * Hmm, so /usr/share/texmf/dvips/config is an symlink, and thus
+ /usr/share/lilypond/1.6.6/dvips/lilypond.map conflicts with tetex-base.
+ Let's move it to /etc/texmf/dvips/lilypond.map then, and make it a
+ conffile. Thanks for all the (duplicate) bug reports! ;-)
+ (Closes: Bug#169811, #169812, #169877, #169946)
+
+ -- Anthony Fok <foka@debian.org> Sat, 23 Nov 2002 19:21:04 +0800
+
+lilypond (1.6.6-1) unstable; urgency=medium
+
+ * New upstream release.
+ * Updated Debian section in Documentation/topdocs/INSTALL.texi.
+ * FTBFS bug due to bugs in bison-1.50. Now explicitly Build-Depends
+ on bison << 1:1.50 or >= 1:1.75-1. (Closes: Bug#165662)
+
+ -- Anthony Fok <foka@debian.org> Tue, 22 Oct 2002 02:05:33 +0800
+
+lilypond (1.6.4-1) unstable; urgency=medium
+
+ * New upstream release.
+ * Higher urgency because of memory corruption bugs in previous releases.
+
+ -- Anthony Fok <foka@debian.org> Sun, 22 Sep 2002 01:55:29 +0800
+
+lilypond (1.6.3-1) unstable; urgency=low
+
+ * New upstream release.
+
+ -- Anthony Fok <foka@debian.org> Sat, 21 Sep 2002 11:14:48 +0800
+
+lilypond (1.6.2-1) unstable; urgency=low
+
+ * New upstream release.
+ * Check g++ version and run lexer-gcc-3.1.sh if necessary.
+
+ -- Anthony Fok <foka@debian.org> Tue, 10 Sep 2002 23:37:27 +0800
+
+lilypond (1.6.0-1) unstable; urgency=medium
+
+ * New upstream release.
+ * binary-arch: Changed "DH_OPTIONS=-a" to "DH_OPTIONS=-s" so that
+ dpkg-gencontrol would not choke on lilypond1.3 for unlisted
+ architectures. Thanks to Ryan Murray for the report and suggested
+ fix. (Closes: Bug#157766)
+
+ -- Anthony Fok <foka@debian.org> Sun, 25 Aug 2002 11:59:01 +0800
+
+lilypond (1.5.68-2) unstable; urgency=low
+
+ * Oops, I was missing Build-Depends on python-dev. Thanks to LaMont
+ Jones and his hppa build daemon for the report. (Closes: Bug#153402)
+ * lilypond should Depends instead of Recommends tetex-extra.
+ Thanks to Russell Neches for the report. (Closes: Bug#152228)
+ * lilypond-indent.el is now installed in lilypond 1.5.x.
+ Thanks to Christophe Rhodes for the report. (Closes: Bug#139070)
+
+ -- Anthony Fok <foka@debian.org> Thu, 18 Jul 2002 23:41:44 +0800
+
+lilypond (1.5.68-1) unstable; urgency=low
+
+ * New upstream release, gearing up for 1.6.0.
+ * Thanks to upstream author Jan Nieuwenhuizen for updating the Debian
+ package to work with 1.5.68.
+ * As per Jan's suggestion, now Build-Depends: pktrace (>= 1.0.3-1),
+ pfaedit (>= 0.0.20020312-1), autotrace, t1utils
+
+ -- Anthony Fok <foka@debian.org> Wed, 17 Jul 2002 03:20:23 +0800
+
+lilypond (1.4.13-1) unstable; urgency=low
+
+ * New upstream release.
+ * Depends: pktrace
+
+ -- Anthony Fok <foka@debian.org> Mon, 6 May 2002 04:09:32 +0800
+
+lilypond (1.4.12-1) unstable; urgency=high
+
+ * New upstream maintenance release.
+ * Several important fixes (including our bison-related patch added
+ to 1.4.10-1) are included since 1.4.11 this release. (Now, I
+ don't even need to increase teTeX's extra_mem_top, extra_mem_bot
+ or pool_size! :-) Please include in Woody.
+ * Fixed a typo in lilypond-doc package description: typestting ->
+ typesetting. Thanks, Matt Zimmerman! (Closes: Bug#125083)
+
+ -- Anthony Fok <foka@debian.org> Sun, 24 Feb 2002 02:06:15 +0800
+
+lilypond (1.4.10-1) unstable; urgency=high
+
+ * New upstream release.
+ * lilypond failed to build with bison >= 1.30 because bison's output file
+ has been renamed. Applied an upstream fix. (Closes: Bug#133692)
+ * lilypond's documentation also failed to build with the latest
+ tetex or texinfo package. Instead of increasing extra_mem_top and
+ extra_mem_bot, increasing pool_size does the trick.
+
+ -- Anthony Fok <foka@debian.org> Mon, 18 Feb 2002 11:41:31 +0800
+
+lilypond (1.4.9-1) unstable; urgency=high
+
+ * New upstream release.
+ * Oops, libc6-dev is known as libc6.1-dev and libc-dev on some
+ architectures. Fixed Build-Depends so that lilypond can be built
+ on all platforms. Thanks to Colin Watson for reporting the bug.
+ (Closes: Bug#120208)
+
+ -- Anthony Fok <foka@debian.org> Tue, 27 Nov 2001 23:28:11 +0800
+
+lilypond (1.4.8-2) unstable; urgency=high
+
+ * [debian/rules]: Use -s instead of -a so that lilypond would get built
+ on all architectures even when the dummy lilypond1.3 package isn't
+ built. Thanks to Ryan Murray for the report. (Closes: Bug#117622)
+ * Depends on python instead of python-base. The python scripts in
+ lilypond work with old and new Python versions.
+ * Build-Depends on "-z combreloc"-enabled binutils (>= 2.11.92.0.10-2)
+ and libc6-dev (>= 2.2.4-5) so that lily runs faster! :-)
+
+ -- Anthony Fok <foka@debian.org> Sun, 11 Nov 2001 10:45:10 +0800
+
+lilypond (1.4.8-1) unstable; urgency=high
+
+ * New upstream release. (Closes: Bug#111132)
+ * Stopped using $(PWD) in make, as it doesn't seems to work on
+ potato systems with older "make". Reverted to `pwd`.
+ Thanks to Wolfgang Schnitker for notifying me this problem.
+ * Changed the lilypond1.3 dummy package's Architecture from "all"
+ to "arm i386 m68k powerpc sparc". Also, as upstream updated
+ config.sub and config.guess to recognize ia64 and hppa.
+ Thanks to Anthony Towns for the bug report. (Closes: Bug#114266)
+ * Versioned Build-Depends: flex (>= 2.5.4a-14) to ensure gcc-3.0
+ compatibility.
+
+ -- Anthony Fok <foka@debian.org> Sun, 14 Oct 2001 18:28:45 +0800
+
+lilypond (1.4.5-1) unstable; urgency=low
+
+ * New upstream release.
+ * Upstream includes lexer-gcc-3.0.patch which should fix compilation
+ problems with g++-3.0. (Closes: Bug#105001)
+ * Hurray! texinfo-4.0b is finally in Debian! Thanks, Josip! :-)
+ Updated Build-Depends.
+
+ -- Anthony Fok <foka@debian.org> Wed, 25 Jul 2001 03:04:37 +0800
+
+lilypond (1.4.3-1) unstable; urgency=high
+
+ * New upstream release.
+ * Urgency high because LilyPond-1.2.17 is too buggy and yet it has
+ been stuck in testing forever. LilyPond-1.4.x fixes multiple
+ serious bugs. :-)
+ * Ah, silly me, lilypond was conflicting against itself! I forgot
+ to remove this relics during the switch from lilypond1.3 to lilypond.
+ * Fixed a new bug in lily/main.cc which caused lilypond to skip over every
+ other command-line argument.
+ * [configure.in]: Added -mieee to CFLAGS and CXXFLAGS when building on
+ Alpha to prevent FP exception. Thanks to Christopher C. Chimelis
+ for the fix!
+
+ -- Anthony Fok <foka@debian.org> Fri, 15 Jun 2001 00:42:46 -0600
+
+lilypond (1.4.2-1) unstable; urgency=low
+
+ * New upstream release.
+ * Moved "bibtex2html, gs | gs-aladdin, netpbm (>= 2:9.10-1)"
+ from Build-Depends to Build-Depends-Indep because these packages
+ are only needed for building lilypond-doc.
+
+ -- Anthony Fok <foka@debian.org> Tue, 29 May 2001 02:26:58 -0600
+
+lilypond (1.4.1-1) unstable; urgency=low
+
+ * New upstream release. (Closes: Bug#97598)
+ * export extra_mem_top=100000 and extra_mem_bot=100000, otherwise
+ latex runs out of memory when processing standchen.dvi.latex.
+ * Split the documentation into the "lilypond-doc" package, which
+ provides the LilyPond website in /usr/share/doc/lilypond/html.
+
+ -- Anthony Fok <foka@debian.org> Wed, 16 May 2001 16:03:40 -0600
+
+lilypond (1.3.150-1) unstable; urgency=low
+
+ * New upstream version.
+ * Renamed package from lilypond1.3 back to lilypond.
+ This also fixes a lot of bugs from the old lilypond-1.2.17 package.
+ lilypond1.3 is temporarily provided as a dummy transitional package.
+ Closes: Bug#67697, 84352, 48731, 72223, 85834.
+ * [debian/rules]:
+ - No longer blindly copy intermediate DVI files into
+ the deb package. Thanks to Daniel Burrows for the reminder.
+ Closes: Bug#87852.
+ - Added "export MODE=ljfour" and "export BDPI=600" because I use
+ something different in my local /etc/texmf/mktex.cnf and that
+ broke the build.
+ * Fixed Build-Depends because pnmtopng has been merged into the netpbm
+ package. Thanks to Adrian Bunk for the notice. Closes: Bug#93961.
+ * [lily/kpath.cc]: Modified to better conform to web2c fontpath policy.
+
+ -- Anthony Fok <foka@debian.org> Thu, 26 Apr 2001 03:25:50 -0600
+
+lilypond1.3 (1.3.132-1) unstable; urgency=medium
+
+ * New upstream version.
+ * Oops, in 1.3.129-1, the "(setq auto-mode-alist (append ..." line in
+ /etc/emacs/site-start.d/50lilypond1.3.el (debian/emacsen-startup)
+ and in FAQ.txt was buggy. Thanks to Erik Demaine for the bug report.
+ Closes: Bug#86685.
+
+ -- Anthony Fok <foka@debian.org> Sun, 25 Feb 2001 20:27:09 -0700
+
+lilypond1.3 (1.3.129-1) unstable; urgency=low
+
+ * In memory of Werner Icking + (August 26, 1943 - February 8, 2001),
+ a dear friend, a kind educator, and a hard worker in sharing beautiful
+ typeset music to the world. (Maintainer of the GMD Music Archive,
+ http://www.gmd.de/Misc/Music/).
+
+ * New upstream release.
+ * Upstream has changed from "lilypond-mode" to the "studly caps name"
+ "LilyPond-mode". Fixed /etc/emacs/site-start.d/50lilypond1.3.el
+ (debian/emacsen-startup). Thanks to Christophe Rhodes for the bug
+ report. Closes: Bug#83732.
+ * Added "Build-Conflicts: lilypond, lilypond1.3" to prevent old
+ lilypond font files from potentially interfering with the build on
+ other Debian ports autobuilders.
+ * Built with libguile-dev (1:1.4-9) or newer to ensure correct
+ linkage to libqthreads.so.9. Also updated the Build-Depends and
+ Depends fields accordingly. Thanks to guile1.4 package maintainer
+ Rob Browning for his notification and to Daniel Burrows for his bug
+ report. Closes: Bug#85896.
+
+ -- Anthony Fok <foka@debian.org> Sat, 10 Feb 2001 01:38:36 -0700
+
+lilypond1.3 (1.3.121-1) unstable; urgency=low
+
+ * New upstream release.
+ * Added more detailed instruction for building lilypond1.3 on Debian
+ in Documentation/topdocs/INSTALL.texi (hence INSTALL.txt).
+ * Applied Han-wen's one-line patch to lily/system-start-delimiter.cc
+ to remove bracket-width.
+ * It seems that bracket-width needs to be removed from
+ scm/grob-description.scm and scm/interface-description.scm too.
+
+ -- Anthony Fok <foka@debian.org> Sun, 7 Jan 2001 02:34:46 -0700
+
+lilypond1.3 (1.3.119-1) unstable; urgency=low
+
+ * New upstream release.
+ * Merged debian/* fixes by upstream author Jan Nieuwenhuizen. Thanks!
+ - The lilypond info files are back! Partially fixed Bug#72233.
+ - Uses the new libguile9 instead of the old libguile6.
+ * Depends on libkpathsea3 instead of the old tetex-lib; Build-Depends
+ is also changed accordingly. Closes: Bug#79469, Bug#79837.
+ * Edited Documentation/user/development.itexi so that it builds
+ without error.
+
+ -- Anthony Fok <foka@debian.org> Fri, 22 Dec 2000 12:54:49 -0700
+
+lilypond1.3 (1.3.107) unstable; urgency=low
+
+ * Fixed watch location.
+ * Local build, not uploaded to Debian.
+
+ -- Jan Nieuwenhuizen <janneke@gnu.org> Mon, 13 Nov 2000 13:33:53 +0100
+
+lilypond1.3 (1.3.103) unstable; urgency=low
+
+ * Re-enabled info doc rules.
+ * Local build, not uploaded to Debian.
+
+ -- Jan Nieuwenhuizen <janneke@gnu.org> Sun, 5 Nov 2000 22:15:57 -0100
+
+lilypond1.3 (1.3.99-1) unstable; urgency=low
+
+ * New upstream release.
+
+ -- Anthony Fok <foka@debian.org> Tue, 31 Oct 2000 00:48:20 -0700
+
+lilypond1.3 (1.3.94-1) unstable; urgency=low
+
+ * New upstream release.
+
+ -- Anthony Fok <foka@debian.org> Sun, 8 Oct 2000 12:36:52 -0600
+
+lilypond1.3 (1.3.80.jcn1-1) unstable; urgency=low
+
+ * New upstream release.
+ * s/tetex-devel/tetex-dev/ in Build-Depends. Thanks to bug report
+ filed by fellow developer Roman Hodek (closes: Bug#69772).
+
+ -- Anthony Fok <foka@debian.org> Sun, 27 Aug 2000 06:11:22 -0600
+
+lilypond1.3 (1.3.79-1) unstable; urgency=low
+
+ * New upstream release.
+ * Added tetex-dev to Build-Depends. Thanks to bug report by fellow
+ developer Daniel Jacobowitz (closes: Bug#68441).
+ * Install two documentation files NEWS and ROADMAP.
+
+ -- Anthony Fok <foka@debian.org> Thu, 17 Aug 2000 22:57:57 -0600
+
+lilypond1.3 (1.3.78-1) unstable; urgency=low
+
+ * New upstream release.
+
+ -- Anthony Fok <foka@debian.org> Wed, 16 Aug 2000 06:32:14 -0600
+
+lilypond1.3 (1.3.75-1) unstable; urgency=low
+
+ * New upstream release.
+ * Updated the link to the http://sca.uwaterloo.ca/lilypond/ mirror in
+ the package description.
+
+ -- Anthony Fok <foka@debian.org> Wed, 26 Jul 2000 01:56:28 -0600
+
+lilypond1.3 (1.3.58-1) unstable; urgency=low
+
+ * New upstream release with patch from Han-wen.
+
+ -- Anthony Fok <foka@debian.org> Thu, 8 Jun 2000 17:19:08 -0600
+
+lilypond1.3 (1.3.48-1) unstable; urgency=low
+
+ * New upstream release.
+ * [debian/control]: Added Depends: guile, for /usr/bin/as2text (Lintian).
+ * [debian/rules]: Changed the symlink /usr/share/lilypond/cmtfm from
+ absolute to relative.
+
+ -- Anthony Fok <foka@debian.org> Wed, 10 May 2000 12:17:54 -0600
+
+lilypond1.3 (1.3.45-1) unstable; urgency=low
+
+ * New upstream release.
+
+ -- Anthony Fok <foka@debian.org> Fri, 14 Apr 2000 21:39:40 -0600
+
+lilypond1.3 (1.3.44-1) unstable; urgency=low
+
+ * New upstream development release with numerous bug fixes, small
+ enhancements, and updates to documentation.
+ * [debian/postinst]: Fixed the pathname to README.Debian. Thanks to
+ Olivier Abad for the bug report (closes: Bug#58674).
+ * [debian/rules]: Now configure with --enable-optimise again.
+ Yes, it appears that LilyPond and glibc2.1.3 finally get along
+ nicely even with optimisation turned on. Hurray! :-)
+ * [Documentation/user/*]: Fixed some formatting bugs in the texinfo files.
+ * [debian/control]: Modified description to hint that 1.3.43 is better
+ than 1.2.17. :-)
+ * [debian/{rules,emacsen-startup}]: Added an Emacs startup file
+ /etc/emacs/site-start.d/50lilypond1.3.el so that lilypond-mode is
+ automatically loaded for *.ly files.
+
+ -- Anthony Fok <foka@debian.org> Wed, 12 Apr 2000 21:22:31 -0600
+
+lilypond1.3 (1.3.24-1) frozen unstable; urgency=low
+
+ * New upstream development release with lots of bug fixes. :-)
+ * [debian/control]: Added missing build dependencies. Thanks to
+ Roman Hodek for the bug report and solution (closes: Bug#58078).
+
+ -- Anthony Fok <foka@debian.org> Sat, 19 Feb 2000 15:14:31 -0700
+
+lilypond1.3 (1.3.17-1) unstable; urgency=low
+
+ * New upstream release. Merry Christmas!
+
+ -- Anthony Fok <foka@debian.org> Fri, 24 Dec 1999 08:59:21 -0700
+
+lilypond1.3 (1.3.16-1) unstable; urgency=low
+
+ * New upstream release.
+
+ -- Anthony Fok <foka@debian.org> Wed, 22 Dec 1999 22:12:30 -0700
+
+lilypond1.3 (1.3.12-1) unstable; urgency=low
+
+ * New upstream release.
+ * [debian/rules]: Commented out "$(MAKE) -C Documentation/programmer ps"
+ temporarily because of error making lilypond-overview.dvi.
+
+ -- Anthony Fok <foka@debian.org> Fri, 17 Dec 1999 00:33:47 -0700
+
+lilypond1.3 (1.3.5-1) unstable; urgency=low
+
+ * New upstream release. lilypond1.3 is the developmental branch.
+ * [debian/rules]: Removed "install-stamp".
+ * [debian/control]:
+ - Standards-Version: 3.1.0
+ - Added the Build-Depends field.
+ - Updated dependencies of tetex-{base,bin,extra} packages to
+ 1.0*-1.
+
+ -- Anthony Fok <foka@debian.org> Sat, 13 Nov 1999 23:25:42 -0700
+
+lilypond (1.2.17-1) unstable; urgency=low
+
+ * New upstream release.
+ * [debian/rules]:
+ - Reverted to configuring with --disable-optimise.
+ - The documentation files are now built properly, and both
+ ps and dvi versions are included.
+ * Standards-Version: 3.0.1
+
+ -- Anthony Fok <foka@debian.org> Sat, 30 Oct 1999 06:57:04 -0600
+
+lilypond (1.2.2-1) unstable; urgency=low
+
+ * New upstream release.
+ * [debian/control]:
+ - Removed recommendation for python-misc (>= 1.5.1)
+ and updated the recommendation of python-base to 1.5.2-4.
+ Thanks to Gregor Hoffleit for the note (closes: Bug#41343).
+ - Updated package description to that provided by the upstream
+ authors in the new version.
+ * [debian/rules]: Now configure with --enable-optimise.
+
+ -- Anthony Fok <foka@debian.org> Tue, 24 Aug 1999 22:05:12 -0600
+
+lilypond (1.1.53-1) unstable; urgency=low
+
+ * New upstream release.
+ * Partially upgraded to standards version 3.0.0:
+ - Updated copyright to point to /usr/share/common-licenses
+ - First step towards FHS-compliance: Man pages are now installed
+ under /usr/share/man.
+
+ -- Anthony Fok <foka@debian.org> Wed, 7 Jul 1999 15:23:57 -0600
+
+lilypond (1.1.47-1) unstable; urgency=low
+
+ * New upstream release.
+
+ -- Anthony Fok <foka@debian.org> Thu, 10 Jun 1999 18:10:13 -0600
+
+lilypond (1.1.42-1) unstable; urgency=low
+
+ * New upstream release.
+ * [postinst]: Runs "/usr/bin/mktexlsr /usr/share/texmf" to save time.
+ * [postrm]: Removed the unnecessary "/usr/bin/mktexlsr" call.
+ * The segfault problem has disappeared on my computer (running
+ the latest potato system). Please test.
+
+ -- Anthony Fok <foka@debian.org> Tue, 11 May 1999 11:16:58 -0600
+
+lilypond (1.1.37-1) unstable; urgency=low
+
+ * New upstream release.
+ * Known problem: LilyPond simply segfaults under glibc 2.1 on my i386
+ system, and I don't know how to fix the problem yet. I hope users of
+ other platforms have better luck.
+ * [debian/rules]:
+ - Make and install info files.
+ - Removed "CC=egcc" because the default gcc on all platforms is
+ now the one from egcs.
+ - Install *.png instead of *.xpm.
+ - Minor clean-ups.
+ * Added debian/compress to make sure *.png are not compressed.
+ * Added debian/doc-base and postinst/prerm for the LilyPond info files.
+ * s!usr/lib/texmf!usr/share/texmf!g and cleaned up old hacks
+ in {pre,post}{inst,rm} files due to tetex's new FHS-compliant
+ directory structure.
+ * [debian/control]: Now Depends/Recommends the latest FHS-compliant
+ tetex-{bin,base,extra} (>= 0.9.99031{0,1}-1) packages.
+
+ -- Anthony Fok <foka@debian.org> Mon, 5 Apr 1999 20:43:30 -0600
+
+lilypond (1.1.31-1) unstable; urgency=low
+
+ * New upstream release.
+ * Re-incorporated the changes in debian/rules and debian/postinst
+ from lilypond_1.0.xx series. I forgot these changes when I moved
+ from 1.0.19.uu3-1 to 1.1.29-1. Sorry! :-)
+ * [make/lilypond-vars.make]: Copied the definition of TEX_TFMDIR from
+ make/toplevel.make.in and added it to LILYINCLUDE...
+ * Applied the patch lilypond-1.1.31.jcn1.diff from Jan Nieuwenhuizen.
+ * [debian/rules]:
+ - Temporarily use "-$(MAKE) -k -C Documentation/tex dvi" to
+ circumvent the occasional \times segfault problem when building
+ refman.dvi.
+ - Added symlink /usr/lib/texmf/fonts/tfm/public/lilypond.
+
+ -- Anthony Fok <foka@debian.org> Thu, 18 Feb 1999 00:25:04 -0700
+
+lilypond (1.1.29-1) unstable; urgency=low
+
+ * New upstream release.
+ * [stepmake/aclocal.m4]: AC_STEPMAKE_GUILE now calls the GUILE_FLAGS
+ macro to set -lqthreads etc., otherwise Guile would not be detected
+ by the configure script.
+
+ -- Anthony Fok <foka@debian.org> Sun, 14 Feb 1999 09:05:00 -0700
+
+lilypond (1.0.19.uu3-1) frozen unstable; urgency=low
+
+ * New upstream bug-fix release.
+
+ -- Anthony Fok <foka@debian.org> Sat, 12 Dec 1998 04:23:15 -0700
+
+lilypond (1.0.19.uu1-2) frozen unstable; urgency=low
+
+ * [debian/rules]: Now builds the LilyPond documentation in dvi format.
+ Thanks to Roland Rosenfeld <roland@spinnaker.rhein.de>
+ for the bug report. (closes: Bug#30123).
+ * [debian/control]: Now also Recommends: tetex-extra (>= 0.9.981030-1)
+ because the .dvi documentation uses the EC fonts in that package.
+
+ -- Anthony Fok <foka@debian.org> Thu, 10 Dec 1998 17:43:57 -0700
+
+lilypond (1.0.19.uu1-1) frozen unstable; urgency=low
+
+ * New upstream bug-fix release.
+
+ -- Anthony Fok <foka@debian.org> Mon, 7 Dec 1998 13:12:02 -0700
+
+lilypond (1.0.18-2) frozen unstable; urgency=low
+
+ * [debian/rules]: Added symlink /usr/lib/texmf/fonts/afm/public/lilypond.
+ Thanks to Julian Gilbey <jdg@maths.qmw.ac.uk> for the bug report
+ (closes: Bug#29407).
+ * [scripts/ly2dvi.py]: Re-added a patch similar to the one in 1.0.17-1,
+ but teTeX's default search path is now placed *before* the ones that
+ ly2dvi adds. Thanks to Roland Rosenfeld <roland@spinnaker.rhein.de>
+ for the bug report. (closes: Bug#29459).
+
+ -- Anthony Fok <foka@debian.org> Mon, 23 Nov 1998 21:29:25 -0700
+
+lilypond (1.0.18-1) frozen unstable; urgency=low
+
+ * New upstream bug-fix release.
+ * [debian/control]:
+ - Upgraded to standards version 2.5.0.0 (no changes).
+ - Recommends: python-misc (>= 1.5.1) because ly2dvi needs the glob
+ module in the python-misc package (closes: Bug#29283).
+ - Updated dependencies on tetex* to the latest versions:
+ Depends: tetex-bin (>= 0.9.981031-2)
+ Recommends: tetex-base (>= 0.9.981030-1)
+ due to changes in tetex's directory structure.
+ * [debian/rules]:
+ - The symlink ../../../../../share/lilypond/mf is now named
+ /usr/lib/texmf/fonts/source/public/lilypond instead of
+ /usr/lib/texmf/fonts/source/public/mf (Bug#29284).
+ - In the latest tetex-base package, /usr/lib/texmf/doc is now a
+ symlink to /usr/doc/texmf. Therefore, we now install lilypond's
+ documentation into /usr/doc/texmf/musixtex/lilypond.
+ (closes: Bug#28999, Bug#29326)
+ * [debian/preinst]:
+ - The script now removes the directories
+ /var/spool/texmf/pk/*/public/mf and /var/spool/texmf/tfm/public/mf
+ created inadvertently by Debian's buggy lilypond 1.0.17-1. :-)
+ (Bug#29284)
+ - Since 1.0.17-1, /usr/lib/texmf/tex/lilypond has been changed to a
+ symbolic directory. The script now removes the old real directory
+ to prevent problems during upgrade (closes: Bug#29284).
+ * [debian/postinst]: I copied a few lines from tetex-nonfree's postinst
+ to remove the old directory /usr/lib/texmf/doc if lilypond is the
+ last package to use that directory, and create a symlink to
+ /usr/doc/texmf. :-)
+ * Rebuilt with yodl (1.31.7-1) installed to ensure the documentations
+ are compiled properly (closes: Bug#29285).
+ * Thanks to Fabien Ninoles <fab@tzone.org>, Roland Rosenfeld
+ <roland@spinnaker.rhein.de> and Julian Gilbey <jdg@maths.qmw.ac.uk>
+ for reporting the bugs listed above. :-)
+
+ -- Anthony Fok <foka@debian.org> Thu, 12 Nov 1998 03:14:25 -0700
+
+lilypond (1.0.17-1) frozen unstable; urgency=low
+
+ * New upstream "stable" release.
+ * [debian/{copyright,control}]: pcnov095.win.tue.nl -> ftp.cs.uu.nl
+ (New upstream master FTP site). Also updated JCN's web site URL.
+ * [debian/rules]:
+ - Now, in the "clean:" target, runs either
+ "find . -user root | xargs -r chown $$SUDO_USER.$$SUDO_GID" or
+ "find . -user root | xargs -r chown $$LOGNAME" to deal with all those
+ root-owned "out/*" files generated during a "sudo debian/rules clean"
+ run. Thanks to Roman Hodek <Roman.Hodek@informatik.uni-erlangen.de>
+ for reporting the problem! (closes: Bug#27044)
+ - Updated debian/rules according to the new debhelper rules example.
+ - Now configures with --disable-optimise instead of --enable-optimise,
+ otherwise it would not compile.
+ - Added symlinks to directories under /usr/lib/texmf because lilypond
+ now puts everything under /usr/share/lilypond.
+ * [Documentation/topdocs/AUTHORS.yo]: Added a trailing "/" on URLs.
+ * [scripts/ly2dvi.py]: Added a hack to add an extra os.pathsep (":" on
+ Linux) to TEXINPUTS and MFINPUTS, otherwise ly2dvi and TeX would fail
+ to find the necessary files.
+ * Compiled with libstdc++2.9. :-)
+
+ -- Anthony Fok <foka@debian.org> Tue, 3 Nov 1998 14:31:18 -0700
+
+lilypond (1.0.2-1) unstable; urgency=low
+
+ * New upstream release.
+
+ -- Anthony Fok <foka@debian.org> Sat, 15 Aug 1998 04:32:08 -0600
+
+lilypond (1.0.1-1) unstable; urgency=low
+
+ * New upstream release.
+ * [aclocal.m4]: Temporarily changed OPTIMIZE="-O2" to OPTIMIZE="-O"
+ to avoid egcs (c++) complaint of "Internal compiler error"
+ on my computer.
+ * [scripts/mudela-book.py]: Added "#!@PYTHON@" at the top. This string
+ expands to "#!/usr/bin/python" in /usr/bin/mudela-book.
+ (Thanks to Lintian. :-)
+ * [debian/control]: Recommends: python-base (>= 1.5.1).
+ (Again, thanks to Lintian. :-)
+ * [debian/postrm]: Now also removes the generated LilyPond fonts
+ *.{tfm,pk} under /var/spool/texmf when called as "postrm remove".
+ * [debian/preinst]: Yes, have to bring this back to remove the generated
+ LilyPond fonts in /var/spool/texmf because "postrm remove" didn't do
+ its jobs in previous versions. Oops. :-)
+ * [debian/rules]: Installs a few new upstream documentation files, and
+ the example files in out/ directories are moved to parent directories.
+
+ -- Anthony Fok <foka@debian.org> Fri, 14 Aug 1998 03:30:05 -0600
+
+lilypond (0.1.76-1) unstable; urgency=low
+
+ * support for 'make deb' target
+ * Not uploaded to Debian's FTP site.
+
+ -- Jan Nieuwenhuizen <janneke@gnu.org> Fri, 3 Jul 1998 17:53:37 +0200
+
+lilypond (0.1.71-1) unstable; urgency=low
+
+ * New upstream release.
+
+ -- Anthony Fok <foka@debian.org> Sat, 6 Jun 1998 00:00:00 -0600
+
+lilypond (0.1.66-1) unstable; urgency=low
+
+ * New upstream release.
+
+ -- Anthony Fok <foka@debian.org> Wed, 20 May 1998 06:50:12 -0600
+
+lilypond (0.1.61-1) frozen unstable; urgency=low
+
+ * New upstream release with tons of bug fixes.
+ Please put this in Hamm.
+ * Revised debian/rules w.r.t. make/lilypond.spec.in.
+
+ -- Anthony Fok <foka@debian.org> Mon, 4 May 1998 03:36:06 -0600
+
+lilypond (0.1.60-1) frozen unstable; urgency=medium
+
+ * New upstream release with lots of bug fixes, including the MIDI
+ generation bug in 0.1.48. Please put this in Hamm.
+ * debian/control:
+ - Upgraded to standards version 2.4.1.0 (no changes).
+ * debian/rules:
+ - lilypond now also depends on tetex-base (>= 0.9-5)
+ and conflicts with tetex-base (<< 0.9).
+ * Modified postinst and postrm to work with teTeX 0.9 / Web2C 7.2:
+ - Removed all the *ugly* kludges and functions that were supposed to
+ deal with non-Debian teTeX installations. Those kludges were
+ specifically made for teTeX 0.4, but they failed to work as intended
+ due to the changes in teTeX 0.9.
+ - No longer messes with special.map because the standard
+ Web2C 7.2 special.map already lists the feta fonts.
+ - Since postinst is so much simpler, it is now a sh script! :-)
+ * Removed preinst which contained yet another obsolete kludge to clean
+ obsolete/ancient lilypond fonts.
+ * Updated the GNU LilyPond Home Page URIs.
+
+ -- Anthony Fok <foka@debian.org> Fri, 1 May 1998 01:14:49 -0600
+
+lilypond (0.1.48-1) unstable; urgency=low
+
+ * New upstream release.
+
+ -- Anthony Fok <foka@debian.org> Fri, 13 Mar 1998 22:15:11 -0800
+
+lilypond (0.1.46-1) unstable; urgency=low
+
+ * New upstream release.
+
+ -- Anthony Fok <foka@debian.org> Fri, 27 Feb 1998 22:43:41 -0800
+
+lilypond (0.1.45-1) unstable; urgency=low
+
+ * New upstream "The Utrecht Release".
+ * Compiled on va.debian.org because egcs 1.0.1 on my computer
+ no longer comes with libg++. :-( But hey, va.debian.org
+ sure is fast! <grin>
+ * Temporarily includes *.xpm instead of *.gif files because
+ the netpbm package is not installed on va.debian.org, and
+ also because it violates Policy 2.1.2. Thanks to
+ James Troup <J.J.Troup@scm.brad.ac.uk> for bug report! :-)
+ (Fixes Bug#18212)
+ * debian/rules: Added "dh_undocumented ly2dvi.1".
+
+ -- Anthony Fok <foka@debian.org> Sat, 21 Feb 1998 01:37:57 -0700
+
+lilypond (0.1.44-1) unstable; urgency=low
+
+ * New upstream release.
+
+ -- Anthony Fok <foka@debian.org> Fri, 6 Feb 1998 22:07:39 -0700
+
+lilypond (0.1.43-1) unstable; urgency=low
+
+ * New upstream release.
+ * Upgraded to standards version 2.4.0.0 (no changes).
+ * Minor fixes to the copyright file (GPL.gz -> GPL).
+ * Revised the package description based on the new lilypond.lsm.
+ * Now includes *.gif instead of *.xpm files.
+ * Other minor revisions to debian/rules.
+ * Added version numbering to the libflower shared library.
+ * Now installs /usr/lib/emacs/site-lisp/mudela-mode.el,
+ but I haven't figured out how to use it myself. <grin>
+
+ -- Anthony Fok <foka@debian.org> Fri, 6 Feb 1998 17:26:55 -0700
+
+lilypond (0.1.42-1) unstable; urgency=low
+
+ * New upstream release.
+ * Now places ly2dvi in /usr/bin.
+
+ -- Anthony Fok <foka@debian.org> Thu, 29 Jan 1998 02:50:36 -0700
+
+lilypond (0.1.41-1) unstable; urgency=low
+
+ * New upstream "The Birthday Release".
+
+ -- Anthony Fok <foka@debian.org> Wed, 21 Jan 1998 02:20:00 -0700
+
+lilypond (0.1.40-1) unstable; urgency=low
+
+ * New upstream release.
+
+ -- Anthony Fok <foka@debian.org> Mon, 12 Jan 1998 19:19:50 -0700
+
+lilypond (0.1.39-2) unstable; urgency=low
+
+ * debian/control:
+ - Description: Remove the note about installing musixtex or
+ musixtex-fonts.
+ - Added "Conflicts: musixtex-fonts".
+
+ -- Anthony Fok <foka@debian.org> Tue, 6 Jan 1998 02:42:56 -0700
+
+lilypond (0.1.39-1) unstable; urgency=low
+
+ * New upstream LilyPond '98 "New Year Gift" release.
+ * debian/control:
+ - No longer Recommends: "musixtex" or "musixtex-fonts" because
+ LilyPond no longer needs them.
+ - Therefore, Section: is changed from "contrib/tex" to "tex".
+ LilyPond can finally go into the main distribution. Hurray!
+ * debian/rules: Now also dh_installdocs ANNOUNCE-0.1 and ONEWS.
+ * preinst, postinst, postrm: Added #DEBHELPER#.
+ * preinst, postrm: Changed #!/bin/bash to #!/bin/sh.
+
+ -- Anthony Fok <foka@debian.org> Mon, 5 Jan 1998 18:42:30 -0700
+
+lilypond (0.1.38-1) unstable; urgency=low
+
+ * New upstream Xmas release.
+ * Applied patch patch-0.1.38.jcn1 from Jan Nieuwenhuizen.
+ * Have fun, Merry Christmas and a Happy 1998. -- Han-Wen Nienhuys
+
+ -- Anthony Fok <foka@debian.org> Wed, 24 Dec 1997 16:38:14 -0700
+
+lilypond (0.1.37-1) unstable; urgency=low
+
+ * New upstream release
+ * Minor modifications to debian/rules due to changes in
+ debhelper 0.32.
+
+ -- Anthony Fok <foka@debian.org> Fri, 12 Dec 1997 11:11:12 -0700
+
+lilypond (0.1.36-1) unstable; urgency=low
+
+ * New upstream release
+
+ -- Anthony Fok <foka@debian.org> Tue, 9 Dec 1997 18:33:50 -0700
+
+lilypond (0.1.35-1) unstable; urgency=low
+
+ * New upstream release
+
+ -- Anthony Fok <foka@debian.org> Fri, 5 Dec 1997 21:06:31 -0700
+
+lilypond (0.1.34-1) unstable; urgency=low
+
+ * New upstream release
+
+ -- Anthony Fok <foka@debian.org> Thu, 4 Dec 1997 19:42:22 -0700
+
+lilypond (0.1.33-1) unstable; urgency=low
+
+ * New upstream release
+ * Changed my maintainer e-mail address to <foka@debian.org>. :)
+
+ -- Anthony Fok <foka@debian.org> Tue, 25 Nov 1997 00:22:57 -0700
+
+lilypond (0.1.32-2) unstable; urgency=low
+
+ * Commented out run_texhash() in postinst by mistake. Fixed.
+
+ -- Anthony Fok <foka@gpu.srv.ualberta.ca> Sun, 23 Nov 1997 03:04:29 -0700
+
+lilypond (0.1.32-1) unstable; urgency=low
+
+ * New upstream release
+ * Applied a small fix to postinst. The font-entries-search-and-replace
+ add_fonts() subroutine was slightly buggy.
+ * Unpatched ./configure. It turned out that I spelt "--enable-optimise"
+ as "--enable-optimize" in debian/rules by mistake. Oops! :) Thanks
+ to the upstream author for pointing this out! :)
+ * The upstream authors has included the ./debian/* files in the pristine
+ source archive! They also fixed some minor errors in README.debian
+ and copyright. Thanks a lot! :)
+ * Removed the line "dh_clean" from "binary-arch:" and switched the order
+ of dh_clean in "clean:" in debian/rules. dh_clean was deleting
+ the zero-byte file ./make/out/Site.make, causing the build to fail.
+
+ -- Anthony Fok <foka@gpu.srv.ualberta.ca> Sun, 23 Nov 1997 01:39:31 -0700
+
+lilypond (0.1.29-1) unstable; urgency=low
+
+ * New upstream release
+ * Patched ./configure in source package to make c++ use the -O2 -g options
+ on all the files. Now, /usr/bin/lilypond is a lot leaner! <smile>
+ (I will discuss it with the upstream author.)
+ * Adapted postinst (a Perl script) from the musixtex package for lilypond.
+ Now postinst adds the new LilyPond font entries into
+ /usr/lib/texmf/fontname/special.map.
+ * Added preinst to clean up my mess from previous releases: the old
+ "stray" automatically generated TFM and PK font files were placed in
+ the wrong directories because they were not listed in
+ /usr/lib/texmf/fontname/special.map.
+ * Did some minor clean-up in debian/rules and switched to debhelper.
+ * Updated Standards-Version to 2.3.0.1
+
+ -- Anthony Fok <foka@gpu.srv.ualberta.ca> Tue, 11 Nov 1997 02:31:33 -0700
+
+lilypond (0.1.25-1) unstable; urgency=low
+
+ * Added a note in README.debian about the possibility of some LilyPond
+ fonts not showing up after an upgrade, and a possible solution to this
+ problem.
+ * New upstream release
+
+ -- Anthony Fok <foka@gpu.srv.ualberta.ca> Thu, 23 Oct 1997 17:00:14 -0600
+
+lilypond (0.1.24-1) unstable; urgency=low
+
+ * New upstream release
+
+ -- Anthony Fok <foka@gpu.srv.ualberta.ca> Tue, 21 Oct 1997 04:12:01 -0600
+
+lilypond (0.1.23-1) unstable; urgency=low
+
+ * New upstream release
+
+ -- Anthony Fok <foka@gpu.srv.ualberta.ca> Thu, 16 Oct 1997 02:15:55 -0600
+
+lilypond (0.1.22-1) unstable; urgency=low
+
+ * New upstream release
+
+ -- Anthony Fok <foka@gpu.srv.ualberta.ca> Mon, 13 Oct 1997 23:51:01 -0600
+
+lilypond (0.1.21-1) unstable; urgency=low
+
+ * New upstream release
+
+ -- Anthony Fok <foka@gpu.srv.ualberta.ca> Thu, 9 Oct 1997 22:58:26 -0600
+
+lilypond (0.1.18.jcn1-1) unstable; urgency=low
+
+ * New upstream release
+
+ -- Anthony Fok <foka@gpu.srv.ualberta.ca> Sat, 4 Oct 1997 03:48:45 -0600
+
+lilypond (0.1.17-1) unstable; urgency=low
+
+ * New upstream release
+ * Remove redundancy in package's description (Fixed bug #12511)
+ * Added a note about the new LilyPond MF fonts which are not yet listed
+ in the current standard special.map (in the teTeX package)
+ * Added SHELL=/bin/bash to debian/rules because I use bashism. <smile>
+
+ -- Anthony Fok <foka@gpu.srv.ualberta.ca> Sun, 28 Sep 1997 01:41:15 -0600
+
+lilypond (0.1.12-1) unstable; urgency=low
+
+ * New upstream release
+ * Updated the mailing address of the Free Software Foundation
+ listed in /usr/doc/lilypond/copyright
+ * Updated Standards-Version to 2.3.0.0
+ * Built with debmake 3.3.14 and fakeroot 0.0-9 <grin>
+
+ -- Anthony Fok <foka@gpu.srv.ualberta.ca> Sun, 7 Sep 1997 23:00:53 -0600
+
+lilypond (0.1.9-1) unstable; urgency=low
+
+ * New upstream release
+
+ -- Anthony Fok <foka@gpu.srv.ualberta.ca> Mon, 18 Aug 1997 15:14:24 -0600
+
+lilypond (0.1.7-1) unstable; urgency=low
+
+ * New upstream release
+
+ -- Anthony Fok <foka@gpu.srv.ualberta.ca> Thu, 14 Aug 1997 15:18:40 -0600
+
+lilypond (0.1.6-1) unstable; urgency=low
+
+ * New upstream release
+
+ -- Anthony Fok <foka@gpu.srv.ualberta.ca> Thu, 14 Aug 1997 05:14:06 -0600
+
+lilypond (0.1.3-1) unstable; urgency=low
+
+ * New upstream release
+
+ -- Anthony Fok <foka@gpu.srv.ualberta.ca> Sat, 9 Aug 1997 14:15:11 -0600
+
+lilypond (0.1.2-1) unstable; urgency=low
+
+ * New upstream release
+
+ -- Anthony Fok <foka@gpu.srv.ualberta.ca> Thu, 7 Aug 1997 22:54:20 -0600
+
+lilypond (0.1.0-1) unstable; urgency=low
+
+ * Initial Release.
+
+ -- Anthony Fok <foka@gpu.srv.ualberta.ca> Wed, 6 Aug 1997 04:40:57 -0600
--- /dev/null
+Source: lilypond
+Build-Depends: debhelper (>= 9), quilt, python-all-dev (>= 2.6.6-3~), guile-1.8-dev,
+ flex, bison, texinfo, groff, m4, gettext, mftrace, fontforge,
+ pkg-config, libfreetype6-dev, libpango1.0-dev,
+ libfontconfig1-dev, help2man,
+ libgmp3-dev, libltdl-dev, ghostscript, texlive-latex-base,
+ texlive-generic-recommended, texlive-latex-recommended, autotools-dev, texi2html, texlive-metapost,
+ zip, rsync, texlive-fonts-recommended, dblatex, netpbm, imagemagick,
+ emacs-intl-fonts, xfonts-intl-arabic, xfonts-intl-asian,
+ xfonts-intl-chinese, xfonts-intl-chinese-big, xfonts-intl-european,
+ xfonts-intl-japanese, xfonts-intl-japanese-big, xfonts-intl-phonetic,
+ ttf-kochi-gothic, ttf-kochi-mincho, ttf-dejavu, ttf-freefont,
+ gsfonts | gsfonts-x11
+Section: tex
+Priority: optional
+Maintainer: Don Armstrong <don@debian.org>
+Standards-Version: 3.9.3
+Homepage: http://lilypond.org/
+Vcs-Git: git://git.donarmstrong.com/lilypond.git
+Vcs-Browser: http://git.donarmstrong.com/lilypond.git
+
+Package: lilypond
+Architecture: any
+Replaces: lilypond1.3
+Provides: lilypond1.3
+Depends: ${shlibs:Depends}, ${python:Depends}, guile-1.8, ${misc:Depends}, lilypond-data (= ${source:Version}), ghostscript
+Breaks: ${python:Breaks}
+Recommends: lilypond-doc, texlive-latex-base
+Description: program for typesetting sheet music
+ LilyPond is a music typesetter, an automated engraving system. It
+ produces beautiful sheet music using a high level description file as input.
+ .
+ LilyPond supports many forms of music notation constructs, including
+ chord names, drum notation, figured bass, grace notes, guitar tablature,
+ modern notation (cluster notation and rhythmic grouping), tremolos,
+ (nested) tuplets in arbitrary ratios, and more.
+ .
+ LilyPond's text-based music input language support can integrate into
+ LaTeX, HTML and Texinfo seamlessly, allowing single sheet music
+ or musicological treatises to be written from a single source. Form and
+ content are separate, and with LilyPond's expert automated formatting,
+ users don't need typographical expertise to produce good notation.
+ .
+ LilyPond produces PDF, PostScript, SVG, or TeX printed output, as well
+ as MIDI for listening pleasures. LilyPond is exported from the
+ RoseGarden and NoteEdit GUIs, and can import ABC, ETF and MIDI.
+ .
+ LilyPond is part of the GNU Project.
+ .
+ Authors: Han-Wen Nienhuys <hanwen@cs.uu.nl>
+ Jan Nieuwenhuizen <janneke@gnu.org>
+
+Package: lilypond-data
+Architecture: all
+Depends: texinfo | texlive-texinfo, texlive-base-bin, ${python:Depends}, ${misc:Depends}
+Breaks: ${python:Breaks}
+Recommends: lilypond (>= ${source:Version})
+Description: LilyPond music typesetter (data files)
+ LilyPond is a music typesetter, an automated engraving system. It
+ produces beautiful sheet music using a high level description file as input.
+ .
+ This package contains architecture-independent data files for LilyPond.
+
+Package: lilypond-doc
+Section: doc
+Architecture: all
+Depends: ${misc:Depends}, dpkg (>= 1.15.4) | install-info
+Recommends: lilypond-doc-html, lilypond-doc-pdf
+Suggests: lilypond (>= ${source:Version})
+Description: LilyPond Documentation in info format (and meta package)
+ LilyPond is a music typesetter, an automated engraving system. It
+ produces beautiful sheet music using a high level description file as input.
+ .
+ This package includes the info documentation and recommends the html
+ and pdf documentation for the LilyPond music typesetting software.
+
+Package: lilypond-doc-pdf
+Section: doc
+Architecture: all
+Depends: ${misc:Depends}, dpkg (>= 1.15.4) | install-info
+Recommends: evince | pdf-viewer
+Suggests: lilypond (>= ${source:Version})
+Description: LilyPond PDF Documentation
+ LilyPond is a music typesetter, an automated engraving system. It
+ produces beautiful sheet music using a high level description file as input.
+ .
+ This package contains the PDF documentation for the LilyPond music
+ typesetting software.
+
+Package: lilypond-doc-html
+Section: doc
+Architecture: all
+Depends: ${misc:Depends}, dpkg (>= 1.15.4) | install-info
+Recommends: mozilla-browser | www-browser
+Suggests: lilypond (>= ${source:Version})
+Replaces: lilypond-doc (< 2.16.2-1~exp+1)
+Breaks: lilypond-doc (< 2.16.2-1~exp+1)
+Description: LilyPond HTML Documentation
+ LilyPond is a music typesetter, an automated engraving system. It
+ produces beautiful sheet music using a high level description file as input.
+ .
+ This package contains the HTML documentation for the LilyPond music
+ typesetting software.
+
+Package: lilypond-doc-html-cs
+Section: doc
+Architecture: all
+Depends: ${misc:Depends}, dpkg (>= 1.15.4) | install-info, lilypond-doc-html
+Suggests: lilypond (>= ${source:Version})
+Replaces: lilypond-doc (< 2.16.2-1~exp+1)
+Breaks: lilypond-doc (< 2.16.2-1~exp+1)
+Description: LilyPond HTML Documentation in Czech
+ LilyPond is a music typesetter, an automated engraving system. It
+ produces beautiful sheet music using a high level description file as input.
+ .
+ This package contains the HTML documentation in Czech for the
+ LilyPond music typesetting software.
+
+Package: lilypond-doc-html-de
+Section: doc
+Architecture: all
+Depends: ${misc:Depends}, dpkg (>= 1.15.4) | install-info, lilypond-doc-html
+Suggests: lilypond (>= ${source:Version})
+Replaces: lilypond-doc (< 2.16.2-1~exp+1)
+Breaks: lilypond-doc (< 2.16.2-1~exp+1)
+Description: LilyPond HTML Documentation in German
+ LilyPond is a music typesetter, an automated engraving system. It
+ produces beautiful sheet music using a high level description file as input.
+ .
+ This package contains the HTML documentation in German for the
+ LilyPond music typesetting software.
+
+Package: lilypond-doc-html-es
+Section: doc
+Architecture: all
+Depends: ${misc:Depends}, dpkg (>= 1.15.4) | install-info, lilypond-doc-html
+Suggests: lilypond (>= ${source:Version})
+Replaces: lilypond-doc (< 2.16.2-1~exp+1)
+Breaks: lilypond-doc (< 2.16.2-1~exp+1)
+Description: LilyPond HTML Documentation in Spanish
+ LilyPond is a music typesetter, an automated engraving system. It
+ produces beautiful sheet music using a high level description file as input.
+ .
+ This package contains the HTML documentation in Spanish for the
+ LilyPond music typesetting software.
+
+Package: lilypond-doc-html-fr
+Section: doc
+Architecture: all
+Depends: ${misc:Depends}, dpkg (>= 1.15.4) | install-info, lilypond-doc-html
+Suggests: lilypond (>= ${source:Version})
+Replaces: lilypond-doc (< 2.16.2-1~exp+1)
+Breaks: lilypond-doc (< 2.16.2-1~exp+1)
+Description: LilyPond HTML Documentation in French
+ LilyPond is a music typesetter, an automated engraving system. It
+ produces beautiful sheet music using a high level description file as input.
+ .
+ This package contains the HTML documentation in French for the
+ LilyPond music typesetting software.
+
+Package: lilypond-doc-html-hu
+Section: doc
+Architecture: all
+Depends: ${misc:Depends}, dpkg (>= 1.15.4) | install-info, lilypond-doc-html
+Suggests: lilypond (>= ${source:Version})
+Replaces: lilypond-doc (< 2.16.2-1~exp+1)
+Breaks: lilypond-doc (< 2.16.2-1~exp+1)
+Description: LilyPond HTML Documentation in Hungarian
+ LilyPond is a music typesetter, an automated engraving system. It
+ produces beautiful sheet music using a high level description file as input.
+ .
+ This package contains the HTML documentation in Hungarian for the
+ LilyPond music typesetting software.
+
+Package: lilypond-doc-html-it
+Section: doc
+Architecture: all
+Depends: ${misc:Depends}, dpkg (>= 1.15.4) | install-info, lilypond-doc-html
+Suggests: lilypond (>= ${source:Version})
+Replaces: lilypond-doc (< 2.16.2-1~exp+1)
+Breaks: lilypond-doc (< 2.16.2-1~exp+1)
+Description: LilyPond HTML Documentation in Italian
+ LilyPond is a music typesetter, an automated engraving system. It
+ produces beautiful sheet music using a high level description file as input.
+ .
+ This package contains the HTML documentation in Italian for the
+ LilyPond music typesetting software.
+
+Package: lilypond-doc-html-ja
+Section: doc
+Architecture: all
+Depends: ${misc:Depends}, dpkg (>= 1.15.4) | install-info, lilypond-doc-html
+Suggests: lilypond (>= ${source:Version})
+Replaces: lilypond-doc (< 2.16.2-1~exp+1)
+Breaks: lilypond-doc (< 2.16.2-1~exp+1)
+Description: LilyPond HTML Documentation in Japanese
+ LilyPond is a music typesetter, an automated engraving system. It
+ produces beautiful sheet music using a high level description file as input.
+ .
+ This package contains the HTML documentation in Japanese for the
+ LilyPond music typesetting software.
+
+Package: lilypond-doc-html-nl
+Section: doc
+Architecture: all
+Depends: ${misc:Depends}, dpkg (>= 1.15.4) | install-info, lilypond-doc-html
+Suggests: lilypond (>= ${source:Version})
+Replaces: lilypond-doc (< 2.16.2-1~exp+1)
+Breaks: lilypond-doc (< 2.16.2-1~exp+1)
+Description: LilyPond HTML Documentation in Dutch
+ LilyPond is a music typesetter, an automated engraving system. It
+ produces beautiful sheet music using a high level description file as input.
+ .
+ This package contains the HTML documentation in Dutch for the
+ LilyPond music typesetting software.
+
+Package: lilypond-doc-html-zh
+Section: doc
+Architecture: all
+Depends: ${misc:Depends}, dpkg (>= 1.15.4) | install-info, lilypond-doc-html
+Suggests: lilypond (>= ${source:Version})
+Replaces: lilypond-doc (< 2.16.2-1~exp+1)
+Breaks: lilypond-doc (< 2.16.2-1~exp+1)
+Description: LilyPond HTML Documentation in Chinese
+ LilyPond is a music typesetter, an automated engraving system. It
+ produces beautiful sheet music using a high level description file as input.
+ .
+ This package contains the HTML documentation in Chinese for the
+ LilyPond music typesetting software.
+
+Package: lilypond-doc-pdf-de
+Section: doc
+Architecture: all
+Depends: ${misc:Depends}, dpkg (>= 1.15.4) | install-info
+Recommends: evince | pdf-viewer
+Suggests: lilypond (>= ${source:Version})
+Replaces: lilypond-doc (< 2.16.2-1~exp+1)
+Breaks: lilypond-doc (< 2.16.2-1~exp+1)
+Description: LilyPond PDF Documentation in German
+ LilyPond is a music typesetter, an automated engraving system. It
+ produces beautiful sheet music using a high level description file as input.
+ .
+ This package contains the PDF documentation in German for the
+ LilyPond music typesetting software.
+
+Package: lilypond-doc-pdf-es
+Section: doc
+Architecture: all
+Depends: ${misc:Depends}, dpkg (>= 1.15.4) | install-info
+Recommends: evince | pdf-viewer
+Suggests: lilypond (>= ${source:Version})
+Replaces: lilypond-doc (< 2.16.2-1~exp+1)
+Breaks: lilypond-doc (< 2.16.2-1~exp+1)
+Description: LilyPond PDF Documentation in Spanish
+ LilyPond is a music typesetter, an automated engraving system. It
+ produces beautiful sheet music using a high level description file as input.
+ .
+ This package contains the PDF documentation in Spanish for the
+ LilyPond music typesetting software.
+
+Package: lilypond-doc-pdf-fr
+Section: doc
+Architecture: all
+Depends: ${misc:Depends}, dpkg (>= 1.15.4) | install-info
+Recommends: evince | pdf-viewer
+Suggests: lilypond (>= ${source:Version})
+Replaces: lilypond-doc (< 2.16.2-1~exp+1)
+Breaks: lilypond-doc (< 2.16.2-1~exp+1)
+Description: LilyPond PDF Documentation in French
+ LilyPond is a music typesetter, an automated engraving system. It
+ produces beautiful sheet music using a high level description file as input.
+ .
+ This package contains the PDF documentation in French for the
+ LilyPond music typesetting software.
+
+Package: lilypond-doc-pdf-hu
+Section: doc
+Architecture: all
+Depends: ${misc:Depends}, dpkg (>= 1.15.4) | install-info
+Recommends: evince | pdf-viewer
+Suggests: lilypond (>= ${source:Version})
+Replaces: lilypond-doc (< 2.16.2-1~exp+1)
+Breaks: lilypond-doc (< 2.16.2-1~exp+1)
+Description: LilyPond PDF Documentation in Hungarian
+ LilyPond is a music typesetter, an automated engraving system. It
+ produces beautiful sheet music using a high level description file as input.
+ .
+ This package contains the PDF documentation in Hungarian for the
+ LilyPond music typesetting software.
+
+Package: lilypond-doc-pdf-it
+Section: doc
+Architecture: all
+Depends: ${misc:Depends}, dpkg (>= 1.15.4) | install-info
+Recommends: evince | pdf-viewer
+Suggests: lilypond (>= ${source:Version})
+Replaces: lilypond-doc (< 2.16.2-1~exp+1)
+Breaks: lilypond-doc (< 2.16.2-1~exp+1)
+Description: LilyPond PDF Documentation in Italian
+ LilyPond is a music typesetter, an automated engraving system. It
+ produces beautiful sheet music using a high level description file as input.
+ .
+ This package contains the PDF documentation in Italian for the
+ LilyPond music typesetting software.
+
+Package: lilypond-doc-pdf-nl
+Section: doc
+Architecture: all
+Depends: ${misc:Depends}, dpkg (>= 1.15.4) | install-info
+Recommends: evince | pdf-viewer
+Suggests: lilypond (>= ${source:Version})
+Replaces: lilypond-doc (< 2.16.2-1~exp+1)
+Breaks: lilypond-doc (< 2.16.2-1~exp+1)
+Description: LilyPond PDF Documentation in Dutch
+ LilyPond is a music typesetter, an automated engraving system. It
+ produces beautiful sheet music using a high level description file as input.
+ .
+ This package contains the PDF documentation in Dutch for the
+ LilyPond music typesetting software.
+
--- /dev/null
+Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Upstream-Name: lilypond
+Upstream-Contact: lilypond-devel@gnu.org
+Source: http://www.lilypond.org/
+
+Files: *
+Copyright: 1993--2012, Han-Wen Nienhuys <hanwen@lilypond.org>,
+ 1996--2012, Jan Nieuwenhuizen <janneke@gnu.org>,
+License: GPL-3+
+
+Files: debian/*
+Copyright: 2010-2012 Don Armstrong <don@debian.org>,
+ 2005-2010 Anthony Fok <foka@debian.org>
+License: GPL-2+
+
+Files: Documentation/*
+Copyright: Han-Wen Nienhuys, Jan Nieuwenhuizen and Graham Percival
+License: GFDL-1.3+
+
+Files: Documentation/snippet
+Copyright: Han-Wen Nienhuys, Jan Nieuwenhuizen and Graham Percival
+License: GFDL-1.3+
+
+Files: input/regression/musicxml/*
+Copyright: 2008-2010, Reinhold Kainhofer
+License: MIT
+
+
+Files: flower/include/matrix.hh
+ lily/constrained-breaking.cc
+ lily/include/constrained-breaking.hh
+ lily/include/one-line-page-breaking.hh
+ lily/include/optimal-page-breaking.hh
+ lily/include/page-breaking.hh
+ lily/include/page-layout-problem.hh
+ lily/include/page-spacing.hh
+ lily/include/page-turn-page-breaking.hh
+ lily/include/skyline.hh
+ lily/include/staff-grouper-interface.hh
+ lily/keep-alive-together-engraver.cc
+ lily/one-line-page-breaking.cc
+ lily/optimal-page-breaking.cc
+ lily/page-breaking-scheme.cc
+ lily/page-breaking.cc
+ lily/page-layout-problem-scheme.cc
+ lily/page-layout-problem.cc
+ lily/page-spacing.cc
+ lily/page-turn-engraver.cc
+ lily/page-turn-page-breaking.cc
+ lily/skyline.cc
+ lily/spacing-interface.cc
+ lily/spring.cc
+ lily/staff-grouper-interface.cc
+Copyright: 2006--2012, Joe Neeman <joeneeman@gmail.com>
+ 2007--2012, Joe Neeman <joeneeman@gmail.com>
+ 2009--2012, Joe Neeman <joeneeman@gmail.com>
+ 2010--2012, Joe Neeman <joeneeman@gmail.com>
+ 2011--2012, Joe Neeman <joeneeman@gmail.com>
+ 2012, Joe Neeman <joeneeman@gmail.com>
+License: GPL-3+
+
+Files: lily/ambitus-engraver.cc
+ lily/cluster-engraver.cc
+ lily/cluster.cc
+ lily/coherent-ligature-engraver.cc
+ lily/custos-engraver.cc
+ lily/custos.cc
+ lily/gregorian-ligature-engraver.cc
+ lily/include/cluster.hh
+ lily/include/coherent-ligature-engraver.hh
+ lily/include/custos.hh
+ lily/include/gregorian-ligature-engraver.hh
+ lily/include/gregorian-ligature.hh
+ lily/include/ligature-engraver.hh
+ lily/include/mensural-ligature.hh
+ lily/include/vaticana-ligature.hh
+ lily/ligature-bracket-engraver.cc
+ lily/ligature-engraver.cc
+ lily/mensural-ligature-engraver.cc
+ lily/mensural-ligature.cc
+ lily/vaticana-ligature-engraver.cc
+ lily/vaticana-ligature.cc
+Copyright: 2000--2012, Juergen Reuter <reuter@ipd.uka.de>
+ 2002--2012, Juergen Reuter <reuter@ipd.uka.de>
+ 2003--2012, Juergen Reuter <reuter@ipd.uka.de>
+License: GPL-3+
+
+Files: lily/beam-collision-engraver.cc
+ lily/concurrent-hairpin-engraver.cc
+ lily/footnote-engraver.cc
+ lily/include/interval-minefield.hh
+ lily/include/pure-from-neighbor-interface.hh
+ lily/include/rhythmic-music-iterator.hh
+ lily/interval-minefield.cc
+ lily/pure-from-neighbor-engraver.cc
+ lily/pure-from-neighbor-interface.cc
+ lily/rhythmic-music-iterator.cc
+ lily/span-bar-stub-engraver.cc
+ lily/unpure-pure-container.cc
+Copyright: 2011--2012, Mike Solomon <mike@apollinemike.com>
+ 2012, Mike Solomon <mike@apollinemike.com>
+License: GPL-3+
+
+Files: lily/dispatcher-scheme.cc
+ lily/dispatcher.cc
+ lily/include/dispatcher.hh
+ lily/include/listener.hh
+ lily/include/scheme-listener.hh
+ lily/include/stream-event.hh
+ lily/listener.cc
+ lily/scheme-listener-scheme.cc
+ lily/scheme-listener.cc
+ lily/stream-event-scheme.cc
+ lily/stream-event.cc
+Copyright: 2005, Erik Sandberg <mandolaerik@gmail.com>
+ 2005--2012, Erik Sandberg <mandolaerik@gmail.com>
+ 2006--2012, Erik Sandberg <mandolaerik@gmail.com>
+License: GPL-3+
+
+Files: lily/include/minimal-page-breaking.hh
+ lily/include/page-marker.hh
+ lily/minimal-page-breaking.cc
+ lily/note-column-scheme.cc
+ lily/page-marker-scheme.cc
+ lily/page-marker.cc
+Copyright: 2007--2012, Nicolas Sceaux <nicolas.sceaux@free.fr>
+ 2010--2012, Nicolas Sceaux <nicolas.sceaux@free.fr>
+License: GPL-3+
+
+Files: scripts/abc2ly.py
+ scripts/auxiliar/check_translation.py
+ scripts/auxiliar/fixcc.py
+ scripts/etf2ly.py
+ scripts/lilypond-book.py
+Copyright: *No copyright*
+License: GPL-3+
+
+Files: tex/txi-en.tex
+ tex/txi-fr.tex
+ tex/txi-it.tex
+ tex/txi-nl.tex
+ tex/txi-de.tex
+ tex/txi-hu.tex
+Copyright: 1999, 2007-2008, Free Software Foundation
+License: GPL-3+
+
+Files: lily/extender-engraver.cc
+ lily/hyphen-engraver.cc
+ lily/include/lyric-hyphen.hh
+Copyright: 1999--2012, Glen Prideaux <glenprideaux@iname.com>
+License: GPL-3+
+
+Files: lily/double-percent-repeat-engraver.cc
+ lily/episema-engraver.cc
+ lily/partial-iterator.cc
+Copyright: 2010--2012, Neil Puttock <n.puttock@gmail.com>
+ 2011--2012, Neil Puttock <n.puttock@gmail.com>
+License: GPL-3+
+
+Files: lily/context-mod.cc
+ lily/include/context-mod.hh
+ lily/pdf-scheme.cc
+Copyright: 2010--2012, Reinhold Kainhofer <reinhold@kainhofer.com>
+License: GPL-3+
+
+Files: lily/out/parser.cc
+ lily/out/parser.hh
+Copyright: 1984, 1989-1990, 2000-2006 Free Software Foundation
+License: GPL-2+
+
+Files: scripts/lilymidi.py
+ scripts/lilysong.py
+Copyright: 2006--2012, Brailcom, o.p.s
+License: GPL-3+
+
+Files: lily/articulations.cc
+ lily/include/articulations.hh
+Copyright: 2010--2012, Carl Sorensen <c_sorensen@byu.edu>
+License: GPL-3+
+
+Files: elisp/lilypond-mode.el
+ lily/include/lyric-extender.hh
+Copyright: 1998--2012, Jan Nieuwenhuizen <janneke@gnu.org>
+ 1999--2012, Jan Nieuwenhuizen <janneke@gnu.org>
+License: GPL-3+
+
+Files: flower/include/yaffut.hh
+Copyright: 2006, Rutger E.W. van Beusekom
+License: BSL-1.0
+
+Files: scripts/build/help2man.pl
+Copyright: 1997-2002, Free Software
+ 1997-2002, Free Software Foundation, Inc
+License: GPL-2+
+
+Files: tex/texinfo.tex
+Copyright: 1985-1986, 1988, 1990-1995
+License: GPL-3+
+
+Files: scripts/convert-ly.py
+Copyright: 1998--2012, Han-Wen Nienhuys <hanwen@xs4all.nl>
+ = ('Jan Nieuwenhuizen <janneke@gnu.org>'
+License: GPL-3+
+
+Files: tex/txi-es.tex
+Copyright: 1999, 2007-2008, Adrian Perez Jorge
+License: GPL-3+
+
+Files: lily/tab-tie-follow-engraver.cc
+Copyright: 2010--2012, Carl D. Sorensen
+License: GPL-3+
+
+Files: scripts/build/yyout2grammar.py
+Copyright: 2005, Carl D. Sorensen <c_sorensen@byu.edu>
+License: GPL-3+
+
+Files: lily/cue-clef-engraver.cc
+Copyright: 1997--2012, Han-Wen Nienhuys <hanwen@xs4all.nl>
+ 2010--2012, Reinhold Kainhofer <reinhold@kainhofer.com>
+License: GPL-3+
+
+Files: lily/slash-repeat-engraver.cc
+Copyright: 2000--2012, Han-Wen Nienhuys <hanwen@xs4all.nl>, Erik Sandberg <mandolaerik@gmail.com>
+License: GPL-3+
+
+Files: lily/percent-repeat-engraver.cc
+Copyright: 2000--2012, Han-Wen Nienhuys <hanwen@xs4all.nl>, Erik Sandberg <mandolaerik@gmail.com>
+License: GPL-3+
+
+Files: lily/stanza-number-engraver.cc
+Copyright: 2000--2012, Han-Wen Nienhuys <hanwen@xs4all.nl>, Glen Prideaux <glenprideaux@iname.com>
+License: GPL-3+
+
+Files: flower/getopt-long.cc
+Copyright: 1996--2012, Han-Wen Nienhuys, <hanwen@xs4all.nl>
+License: GPL-3+
+
+Files: lily/tab-note-heads-engraver.cc
+Copyright: 2002--2012, Han-Wen Nienhuys, Jean-Baptiste Lamy <jiba@tuxfamily.org>
+License: GPL-3+
+
+Files: lily/breathing-sign.cc
+Copyright: 1999--2012, Michael Krause
+ 2003--2012, Juergen Reuter
+License: GPL-3+
+
+Files: lily/breathing-sign-engraver.cc
+Copyright: 1999--2012, Michael Krause
+License: GPL-3+
+
+Files: lily/forbid-break-engraver.cc
+Copyright: 2002--_2005 Han-Wen Nienhuys <hanwen@xs4all.nl>
+License: GPL-3+
+
+Files: scripts/auxiliar/makelsr.py
+Copyright: *No copyright*
+License: GPL-3+
+
+Files: elisp/lilypond-font-lock.el
+Copyright: 1997: Han-Wen Nienhuys, 1995-1996 Barry A. Warsaw,1992-1994 Tim Peters
+License: GPL-3+
+
+Files: elisp/lilypond-song.el
+Copyright: 2006, Brailcom, o.p.s
+License: GPL-3+
+
+Files: lily/include/breathing-sign.hh
+Copyright: 1999--2012, Michael Krause
+License: GPL-3+
+
+Files: scripts/build/mf2pt1.pl
+Copyright: 2012, Scott Pakin
+License: LPPL-1.3c+
+
+Files: scripts/build/website_post.py
+Copyright: UNKNOWN
+License: GPL-3+
+
+
+License: BSL-1.0
+ Boost Software License - Version 1.0 - August 17th, 2003
+ .
+ Permission is hereby granted, free of charge, to any person or organization
+ obtaining a copy of the software and accompanying documentation covered by
+ this license (the "Software") to use, reproduce, display, distribute,
+ execute, and transmit the Software, and to prepare derivative works of the
+ Software, and to permit third-parties to whom the Software is furnished to
+ do so, all subject to the following:
+ .
+ The copyright notices in the Software and this entire statement, including
+ the above license grant, this restriction and the following disclaimer,
+ must be included in all copies of the Software, in whole or in part, and
+ all derivative works of the Software, unless such copies or derivative
+ works are solely in the form of machine-executable object code generated by
+ a source language processor.
+ .
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+ FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT. IN NO EVENT
+ SHALL THE COPYRIGHT HOLDERS OR ANYONE DISTRIBUTING THE SOFTWARE BE LIABLE
+ FOR ANY DAMAGES OR OTHER LIABILITY, WHETHER IN CONTRACT, TORT OR OTHERWISE,
+ ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
+ DEALINGS IN THE SOFTWARE.
+
+License: GFDL-1.3+
+ Permission is granted to copy, distribute and/or modify the
+ documentation for GNU LilyPond under the terms of the GNU Free
+ Documentation License as published by the Free Software Foundation,
+ either version 1.3, or (at your option) any later version; with no
+ Invariant Sections, no Front-Cover Texts and no Back-Cover Texts.
+ .
+ On Debian systems, the complete text of version 1.3 of the GNU Free
+ Documenation License can be found in
+ `/usr/share/common-licenses/GFDL-1.3'.
+
+
+License: GPL-3+
+ 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.
+ .
+ On Debian systems, the complete text of version 3 of the GNU General
+ Public License can be found in `/usr/share/common-licenses/GPL-3'.
+
+License: GPL-2+
+ 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 2 of the License, or
+ (at your option) any later version.
+ .
+ On Debian systems, the complete text of version 3 of the GNU General
+ Public License can be found in `/usr/share/common-licenses/GPL-3'.
+
+License: LPPL-1.3c+
+ The LaTeX Project Public License
+ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
+ .
+ LPPL Version 1.3c 2008-05-04
+ .
+ Copyright 1999 2002-2008 LaTeX3 Project
+ Everyone is allowed to distribute verbatim copies of this
+ license document, but modification of it is not allowed.
+ .
+ .
+ PREAMBLE
+ ========
+ .
+ The LaTeX Project Public License (LPPL) is the primary license under
+ which the LaTeX kernel and the base LaTeX packages are distributed.
+ .
+ You may use this license for any work of which you hold the copyright
+ and which you wish to distribute. This license may be particularly
+ suitable if your work is TeX-related (such as a LaTeX package), but
+ it is written in such a way that you can use it even if your work is
+ unrelated to TeX.
+ .
+ The section `WHETHER AND HOW TO DISTRIBUTE WORKS UNDER THIS LICENSE',
+ below, gives instructions, examples, and recommendations for authors
+ who are considering distributing their works under this license.
+ .
+ This license gives conditions under which a work may be distributed
+ and modified, as well as conditions under which modified versions of
+ that work may be distributed.
+ .
+ We, the LaTeX3 Project, believe that the conditions below give you
+ the freedom to make and distribute modified versions of your work
+ that conform with whatever technical specifications you wish while
+ maintaining the availability, integrity, and reliability of
+ that work. If you do not see how to achieve your goal while
+ meeting these conditions, then read the document `cfgguide.tex'
+ and `modguide.tex' in the base LaTeX distribution for suggestions.
+ .
+ .
+ DEFINITIONS
+ ===========
+ .
+ In this license document the following terms are used:
+ .
+ `Work'
+ Any work being distributed under this License.
+ . `Derived Work'
+ Any work that under any applicable law is derived from the Work.
+ .
+ `Modification'
+ Any procedure that produces a Derived Work under any applicable
+ law -- for example, the production of a file containing an
+ original file associated with the Work or a significant portion of
+ such a file, either verbatim or with modifications and/or
+ translated into another language.
+ .
+ `Modify'
+ To apply any procedure that produces a Derived Work under any
+ applicable law.
+ . `Distribution'
+ Making copies of the Work available from one person to another, in
+ whole or in part. Distribution includes (but is not limited to)
+ making any electronic components of the Work accessible by
+ file transfer protocols such as FTP or HTTP or by shared file
+ systems such as Sun's Network File System (NFS).
+ .
+ `Compiled Work'
+ A version of the Work that has been processed into a form where it
+ is directly usable on a computer system. This processing may
+ include using installation facilities provided by the Work,
+ transformations of the Work, copying of components of the Work, or
+ other activities. Note that modification of any installation
+ facilities provided by the Work constitutes modification of the Work.
+ .
+ `Current Maintainer'
+ A person or persons nominated as such within the Work. If there is
+ no such explicit nomination then it is the `Copyright Holder' under
+ any applicable law.
+ .
+ `Base Interpreter'
+ A program or process that is normally needed for running or
+ interpreting a part or the whole of the Work.
+ .
+ A Base Interpreter may depend on external components but these
+ are not considered part of the Base Interpreter provided that each
+ external component clearly identifies itself whenever it is used
+ interactively. Unless explicitly specified when applying the
+ license to the Work, the only applicable Base Interpreter is a
+ `LaTeX-Format' or in the case of files belonging to the
+ `LaTeX-format' a program implementing the `TeX language'.
+ .
+ .
+ .
+ CONDITIONS ON DISTRIBUTION AND MODIFICATION
+ ===========================================
+ .
+ 1. Activities other than distribution and/or modification of the Work
+ are not covered by this license; they are outside its scope. In
+ particular, the act of running the Work is not restricted and no
+ requirements are made concerning any offers of support for the Work.
+ .
+ 2. You may distribute a complete, unmodified copy of the Work as you
+ received it. Distribution of only part of the Work is considered
+ modification of the Work, and no right to distribute such a Derived
+ Work may be assumed under the terms of this clause.
+ .
+ 3. You may distribute a Compiled Work that has been generated from a
+ complete, unmodified copy of the Work as distributed under Clause 2
+ above, as long as that Compiled Work is distributed in such a way that
+ the recipients may install the Compiled Work on their system exactly
+ as it would have been installed if they generated a Compiled Work
+ directly from the Work.
+ .
+ 4. If you are the Current Maintainer of the Work, you may, without
+ restriction, modify the Work, thus creating a Derived Work. You may
+ also distribute the Derived Work without restriction, including
+ Compiled Works generated from the Derived Work. Derived Works
+ distributed in this manner by the Current Maintainer are considered to
+ be updated versions of the Work.
+ .
+ 5. If you are not the Current Maintainer of the Work, you may modify
+ your copy of the Work, thus creating a Derived Work based on the Work,
+ and compile this Derived Work, thus creating a Compiled Work based on
+ the Derived Work.
+ .
+ 6. If you are not the Current Maintainer of the Work, you may
+ distribute a Derived Work provided the following conditions are met
+ for every component of the Work unless that component clearly states
+ in the copyright notice that it is exempt from that condition. Only
+ the Current Maintainer is allowed to add such statements of exemption
+ to a component of the Work.
+ .
+ a. If a component of this Derived Work can be a direct replacement
+ for a component of the Work when that component is used with the
+ Base Interpreter, then, wherever this component of the Work
+ identifies itself to the user when used interactively with that
+ Base Interpreter, the replacement component of this Derived Work
+ clearly and unambiguously identifies itself as a modified version
+ of this component to the user when used interactively with that
+ Base Interpreter.
+ . b. Every component of the Derived Work contains prominent notices
+ detailing the nature of the changes to that component, or a
+ prominent reference to another file that is distributed as part
+ of the Derived Work and that contains a complete and accurate log
+ of the changes.
+ . c. No information in the Derived Work implies that any persons,
+ including (but not limited to) the authors of the original version
+ of the Work, provide any support, including (but not limited to)
+ the reporting and handling of errors, to recipients of the
+ Derived Work unless those persons have stated explicitly that
+ they do provide such support for the Derived Work.
+ .
+ d. You distribute at least one of the following with the Derived Work:
+ .
+ 1. A complete, unmodified copy of the Work;
+ if your distribution of a modified component is made by
+ offering access to copy the modified component from a
+ designated place, then offering equivalent access to copy
+ the Work from the same or some similar place meets this
+ condition, even though third parties are not compelled to
+ copy the Work along with the modified component;
+ .
+ 2. Information that is sufficient to obtain a complete,
+ unmodified copy of the Work.
+ .
+ 7. If you are not the Current Maintainer of the Work, you may
+ distribute a Compiled Work generated from a Derived Work, as long as
+ the Derived Work is distributed to all recipients of the Compiled
+ Work, and as long as the conditions of Clause 6, above, are met with
+ regard to the Derived Work.
+ .
+ 8. The conditions above are not intended to prohibit, and hence do not
+ apply to, the modification, by any method, of any component so that it
+ becomes identical to an updated version of that component of the Work as
+ it is distributed by the Current Maintainer under Clause 4, above.
+ .
+ 9. Distribution of the Work or any Derived Work in an alternative
+ format, where the Work or that Derived Work (in whole or in part) is
+ then produced by applying some process to that format, does not relax or
+ nullify any sections of this license as they pertain to the results of
+ applying that process.
+ . 10. a. A Derived Work may be distributed under a different license
+ provided that license itself honors the conditions listed in
+ Clause 6 above, in regard to the Work, though it does not have
+ to honor the rest of the conditions in this license.
+ . b. If a Derived Work is distributed under a different license, that
+ Derived Work must provide sufficient documentation as part of
+ itself to allow each recipient of that Derived Work to honor the
+ restrictions in Clause 6 above, concerning changes from the Work.
+ .
+ 11. This license places no restrictions on works that are unrelated to
+ the Work, nor does this license place any restrictions on aggregating
+ such works with the Work by any means.
+ .
+ 12. Nothing in this license is intended to, or may be used to, prevent
+ complete compliance by all parties with all applicable laws.
+ .
+ .
+ NO WARRANTY
+ ===========
+ .
+ There is no warranty for the Work. Except when otherwise stated in
+ writing, the Copyright Holder provides the Work `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 Work is with you. Should the Work prove defective, you assume
+ the cost of all necessary servicing, repair, or correction.
+ .
+ In no event unless required by applicable law or agreed to in writing
+ will The Copyright Holder, or any author named in the components of the
+ Work, or any other party who may distribute and/or modify the Work as
+ permitted above, be liable to you for damages, including any general,
+ special, incidental or consequential damages arising out of any use of
+ the Work or out of inability to use the Work (including, but not limited
+ to, loss of data, data being rendered inaccurate, or losses sustained by
+ anyone as a result of any failure of the Work to operate with any other
+ programs), even if the Copyright Holder or said author or said other
+ party has been advised of the possibility of such damages.
+ .
+ .
+ MAINTENANCE OF THE WORK
+ =======================
+ .
+ The Work has the status `author-maintained' if the Copyright Holder
+ explicitly and prominently states near the primary copyright notice in
+ the Work that the Work can only be maintained by the Copyright Holder
+ or simply that it is `author-maintained'.
+ .
+ The Work has the status `maintained' if there is a Current Maintainer
+ who has indicated in the Work that they are willing to receive error
+ reports for the Work (for example, by supplying a valid e-mail
+ address). It is not required for the Current Maintainer to acknowledge
+ or act upon these error reports.
+ .
+ The Work changes from status `maintained' to `unmaintained' if there
+ is no Current Maintainer, or the person stated to be Current
+ Maintainer of the work cannot be reached through the indicated means
+ of communication for a period of six months, and there are no other
+ significant signs of active maintenance.
+ .
+ You can become the Current Maintainer of the Work by agreement with
+ any existing Current Maintainer to take over this role.
+ .
+ If the Work is unmaintained, you can become the Current Maintainer of
+ the Work through the following steps:
+ .
+ 1. Make a reasonable attempt to trace the Current Maintainer (and
+ the Copyright Holder, if the two differ) through the means of
+ an Internet or similar search.
+ .
+ 2. If this search is successful, then enquire whether the Work
+ is still maintained.
+ .
+ a. If it is being maintained, then ask the Current Maintainer
+ to update their communication data within one month.
+ . b. If the search is unsuccessful or no action to resume active
+ maintenance is taken by the Current Maintainer, then announce
+ within the pertinent community your intention to take over
+ maintenance. (If the Work is a LaTeX work, this could be
+ done, for example, by posting to comp.text.tex.)
+ .
+ 3a. If the Current Maintainer is reachable and agrees to pass
+ maintenance of the Work to you, then this takes effect
+ immediately upon announcement.
+ .
+ b. If the Current Maintainer is not reachable and the Copyright
+ Holder agrees that maintenance of the Work be passed to you,
+ then this takes effect immediately upon announcement.
+ .
+ 4. If you make an `intention announcement' as described in 2b. above
+ and after three months your intention is challenged neither by
+ the Current Maintainer nor by the Copyright Holder nor by other
+ people, then you may arrange for the Work to be changed so as
+ to name you as the (new) Current Maintainer.
+ .
+ 5. If the previously unreachable Current Maintainer becomes
+ reachable once more within three months of a change completed
+ under the terms of 3b) or 4), then that Current Maintainer must
+ become or remain the Current Maintainer upon request provided
+ they then update their communication data within one month.
+ .
+ A change in the Current Maintainer does not, of itself, alter the fact
+ that the Work is distributed under the LPPL license.
+ .
+ If you become the Current Maintainer of the Work, you should
+ immediately provide, within the Work, a prominent and unambiguous
+ statement of your status as Current Maintainer. You should also
+ announce your new status to the same pertinent community as
+ in 2b) above.
+ .
+ .
+ WHETHER AND HOW TO DISTRIBUTE WORKS UNDER THIS LICENSE
+ ======================================================
+ .
+ This section contains important instructions, examples, and
+ recommendations for authors who are considering distributing their
+ works under this license. These authors are addressed as `you' in
+ this section.
+ .
+ Choosing This License or Another License
+ ----------------------------------------
+ .
+ If for any part of your work you want or need to use *distribution*
+ conditions that differ significantly from those in this license, then
+ do not refer to this license anywhere in your work but, instead,
+ distribute your work under a different license. You may use the text
+ of this license as a model for your own license, but your license
+ should not refer to the LPPL or otherwise give the impression that
+ your work is distributed under the LPPL.
+ .
+ The document `modguide.tex' in the base LaTeX distribution explains
+ the motivation behind the conditions of this license. It explains,
+ for example, why distributing LaTeX under the GNU General Public
+ License (GPL) was considered inappropriate. Even if your work is
+ unrelated to LaTeX, the discussion in `modguide.tex' may still be
+ relevant, and authors intending to distribute their works under any
+ license are encouraged to read it.
+ .
+ A Recommendation on Modification Without Distribution
+ -----------------------------------------------------
+ .
+ It is wise never to modify a component of the Work, even for your own
+ personal use, without also meeting the above conditions for
+ distributing the modified component. While you might intend that such
+ modifications will never be distributed, often this will happen by
+ accident -- you may forget that you have modified that component; or
+ it may not occur to you when allowing others to access the modified
+ version that you are thus distributing it and violating the conditions
+ of this license in ways that could have legal implications and, worse,
+ cause problems for the community. It is therefore usually in your
+ best interest to keep your copy of the Work identical with the public
+ one. Many works provide ways to control the behavior of that work
+ without altering any of its licensed components.
+ .
+ How to Use This License
+ -----------------------
+ .
+ To use this license, place in each of the components of your work both
+ an explicit copyright notice including your name and the year the work
+ was authored and/or last substantially modified. Include also a
+ statement that the distribution and/or modification of that
+ component is constrained by the conditions in this license.
+ .
+ Here is an example of such a notice and statement:
+ .
+ %% pig.dtx
+ %% Copyright 2005 M. Y. Name
+ %
+ % This work may be distributed and/or modified under the
+ % conditions of the LaTeX Project Public License, either version 1.3
+ % of this license or (at your option) any later version.
+ % The latest version of this license is in
+ % http://www.latex-project.org/lppl.txt
+ % and version 1.3 or later is part of all distributions of LaTeX
+ % version 2005/12/01 or later.
+ %
+ % This work has the LPPL maintenance status `maintained'.
+ %
+ % The Current Maintainer of this work is M. Y. Name.
+ %
+ % This work consists of the files pig.dtx and pig.ins
+ % and the derived file pig.sty.
+ .
+ Given such a notice and statement in a file, the conditions
+ given in this license document would apply, with the `Work' referring
+ to the three files `pig.dtx', `pig.ins', and `pig.sty' (the last being
+ generated from `pig.dtx' using `pig.ins'), the `Base Interpreter'
+ referring to any `LaTeX-Format', and both `Copyright Holder' and
+ `Current Maintainer' referring to the person `M. Y. Name'.
+ .
+ If you do not want the Maintenance section of LPPL to apply to your
+ Work, change `maintained' above into `author-maintained'.
+ However, we recommend that you use `maintained', as the Maintenance
+ section was added in order to ensure that your Work remains useful to
+ the community even when you can no longer maintain and support it
+ yourself.
+ .
+ Derived Works That Are Not Replacements
+ ---------------------------------------
+ .
+ Several clauses of the LPPL specify means to provide reliability and
+ stability for the user community. They therefore concern themselves
+ with the case that a Derived Work is intended to be used as a
+ (compatible or incompatible) replacement of the original Work. If
+ this is not the case (e.g., if a few lines of code are reused for a
+ completely different task), then clauses 6b and 6d shall not apply.
+ .
+ .
+ Important Recommendations
+ -------------------------
+ .
+ Defining What Constitutes the Work
+ .
+ The LPPL requires that distributions of the Work contain all the
+ files of the Work. It is therefore important that you provide a
+ way for the licensee to determine which files constitute the Work.
+ This could, for example, be achieved by explicitly listing all the
+ files of the Work near the copyright notice of each file or by
+ using a line such as:
+ .
+ % This work consists of all files listed in manifest.txt.
+ .
+ in that place. In the absence of an unequivocal list it might be
+ impossible for the licensee to determine what is considered by you
+ to comprise the Work and, in such a case, the licensee would be
+ entitled to make reasonable conjectures as to which files comprise
+ the Work.
+
+
+License: MIT
+ Permission is hereby granted, free of charge, to any person obtaining a copy
+ of this software and associated documentation files (the "Software"), to deal
+ in the Software without restriction, including without limitation the rights
+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+ copies of the Software, and to permit persons to whom the Software is
+ furnished to do so, subject to the following conditions:
+ .
+ The above copyright notice and this permission notice shall be included in
+ all copies or substantial portions of the Software.
+ .
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+ THE SOFTWARE.
--- /dev/null
+pdf de German
+pdf es Spanish
+pdf fr French
+pdf hu Hungarian
+pdf it Italian
+pdf nl Dutch
+html cs Czech
+html de German
+html es Spanish
+html fr French
+html hu Hungarian
+html it Italian
+html ja Japanese
+html nl Dutch
+html zh Chinese
--- /dev/null
+(autoload 'LilyPond-mode "lilypond-mode" nil t)
+(setq auto-mode-alist (cons '("\\.ly$" . LilyPond-mode) auto-mode-alist))
+(add-hook 'LilyPond-mode-hook (lambda () (turn-on-font-lock)))
--- /dev/null
+usr/share/lilypond
+usr/share/emacs/site-lisp
--- /dev/null
+#!/bin/sh
+#
+# postinst script for the Debian GNU/Linux lilypond-data package
+# by Anthony Fok <foka@debian.org>
+# Initial release: Sun, 26 Oct 1997 03:23:00 -0700
+# Last modified: Thu, 17 Jun 2004 11:40:36 +0800
+
+set -e
+
+package=lilypond # This is used for filenames! Don't change it!
+pkg_name="GNU LilyPond"
+
+std_TEXMFMAIN=/usr/share/texmf # Debian's standard $TEXMFMAIN
+
+TEXMFMAIN=`kpsewhich -expand-var '$TEXMFMAIN'`
+: ${TEXMFMAIN:=$std_TEXMFMAIN}
+
+echo " Running mktexlsr $TEXMFMAIN..."
+mktexlsr $TEXMFMAIN
+
+#DEBHELPER#
+# echo
+# echo " $pkg_name configuration completed."
+# echo " Please read /usr/share/doc/lilypond/README.Debian to get started."
+
+if [ "$1" = "configure" ]; then
+ if [ -d /usr/share/info/lilypond ] && [ ! -L /usr/share/info/lilypond ] \
+ && rmdir /usr/share/lilypond; then
+ (cd /usr/share/info; ln -s ../doc/lilypond/html/Documentation/user/ lilypond;)
+ fi;
+fi;
--- /dev/null
+#!/bin/sh
+#
+# postrm script for the Debian GNU/Linux lilypond package
+# by Anthony Fok <foka@debian.org>
+# This is free software; see the GNU General Public Licence
+# version 2 or later for copying conditions. There is NO warranty.
+# Last modified: Tue, 11 May 1999 11:16:35 -0600
+
+set -e
+
+package=lilypond
+font_supplier=public
+font_typeface=lilypond
+std_VARTEXFONTS=/var/spool/texmf
+
+#DEBHELPER#
+if [ "$1" != purge ]; then
+ VARTEXFONTS=`kpsewhich -expand-var '$VARTEXFONTS'`
+ : ${VARTEXFONTS=$std_VARTEXFONTS}
+fi
+
+case "$1" in
+ upgrade)
+ # Clear out the old TFM and PK files in case the fonts were modified
+ rm -rf $VARTEXFONTS/tfm/$font_supplier/$font_typeface
+ rm -rf $VARTEXFONTS/pk/*/$font_supplier/$font_typeface
+ ;;
+
+ remove)
+ # Clear out the old TFM and PK files in case the fonts were modified
+ rm -rf $VARTEXFONTS/tfm/$font_supplier/$font_typeface
+ rm -rf $VARTEXFONTS/pk/*/$font_supplier/$font_typeface
+ ;;
+
+ failed-upgrade|purge|abort-install|abort-upgrade|disappear)
+ ;;
+
+ *)
+ echo "postrm called with unknown argument \`$1'" >&2
+ exit 0
+ ;;
+esac
--- /dev/null
+Document: lilypond.cs
+Title: GNU LilyPond, the music typesetter
+Author: Various
+Abstract: This documentation describes LilyPond (the GNU Project music
+ typesetter), the LilyPond music input language, and the Mutopia project,
+ a.k.a. "Music To the People."
+Section: Typesetting
+
+Format: HTML
+Index: /usr/share/doc/lilypond/html/index.cs.html
+Files: /usr/share/doc/lilypond/html/*/*/*.cs.html /usr/share/doc/lilypond/html/*/*.cs.html /usr/share/doc/lilypond/html/*.cs.html
--- /dev/null
+usr/share/doc/lilypond/html/*/*/*.cs.html
+usr/share/doc/lilypond/html/*/*.cs.html
+usr/share/doc/lilypond/html/*.cs.html
--- /dev/null
+Document: lilypond.de
+Title: GNU LilyPond, the music typesetter
+Author: Various
+Abstract: This documentation describes LilyPond (the GNU Project music
+ typesetter), the LilyPond music input language, and the Mutopia project,
+ a.k.a. "Music To the People."
+Section: Typesetting
+
+Format: HTML
+Index: /usr/share/doc/lilypond/html/index.de.html
+Files: /usr/share/doc/lilypond/html/*/*/*.de.html /usr/share/doc/lilypond/html/*/*.de.html /usr/share/doc/lilypond/html/*.de.html
--- /dev/null
+usr/share/doc/lilypond/html/*/*/*.de.html
+usr/share/doc/lilypond/html/*/*.de.html
+usr/share/doc/lilypond/html/*.de.html
--- /dev/null
+Document: lilypond.es
+Title: GNU LilyPond, the music typesetter
+Author: Various
+Abstract: This documentation describes LilyPond (the GNU Project music
+ typesetter), the LilyPond music input language, and the Mutopia project,
+ a.k.a. "Music To the People."
+Section: Typesetting
+
+Format: HTML
+Index: /usr/share/doc/lilypond/html/index.es.html
+Files: /usr/share/doc/lilypond/html/*/*/*.es.html /usr/share/doc/lilypond/html/*/*.es.html /usr/share/doc/lilypond/html/*.es.html
--- /dev/null
+usr/share/doc/lilypond/html/*/*/*.es.html
+usr/share/doc/lilypond/html/*/*.es.html
+usr/share/doc/lilypond/html/*.es.html
--- /dev/null
+Document: lilypond.fr
+Title: GNU LilyPond, the music typesetter
+Author: Various
+Abstract: This documentation describes LilyPond (the GNU Project music
+ typesetter), the LilyPond music input language, and the Mutopia project,
+ a.k.a. "Music To the People."
+Section: Typesetting
+
+Format: HTML
+Index: /usr/share/doc/lilypond/html/index.fr.html
+Files: /usr/share/doc/lilypond/html/*/*/*.fr.html /usr/share/doc/lilypond/html/*/*.fr.html /usr/share/doc/lilypond/html/*.fr.html
--- /dev/null
+usr/share/doc/lilypond/html/*/*/*.fr.html
+usr/share/doc/lilypond/html/*/*.fr.html
+usr/share/doc/lilypond/html/*.fr.html
--- /dev/null
+Document: lilypond.hu
+Title: GNU LilyPond, the music typesetter
+Author: Various
+Abstract: This documentation describes LilyPond (the GNU Project music
+ typesetter), the LilyPond music input language, and the Mutopia project,
+ a.k.a. "Music To the People."
+Section: Typesetting
+
+Format: HTML
+Index: /usr/share/doc/lilypond/html/index.hu.html
+Files: /usr/share/doc/lilypond/html/*/*/*.hu.html /usr/share/doc/lilypond/html/*/*.hu.html /usr/share/doc/lilypond/html/*.hu.html
--- /dev/null
+usr/share/doc/lilypond/html/*/*/*.hu.html
+usr/share/doc/lilypond/html/*/*.hu.html
+usr/share/doc/lilypond/html/*.hu.html
--- /dev/null
+Document: lilypond.it
+Title: GNU LilyPond, the music typesetter
+Author: Various
+Abstract: This documentation describes LilyPond (the GNU Project music
+ typesetter), the LilyPond music input language, and the Mutopia project,
+ a.k.a. "Music To the People."
+Section: Typesetting
+
+Format: HTML
+Index: /usr/share/doc/lilypond/html/index.it.html
+Files: /usr/share/doc/lilypond/html/*/*/*.it.html /usr/share/doc/lilypond/html/*/*.it.html /usr/share/doc/lilypond/html/*.it.html
--- /dev/null
+usr/share/doc/lilypond/html/*/*/*.it.html
+usr/share/doc/lilypond/html/*/*.it.html
+usr/share/doc/lilypond/html/*.it.html
--- /dev/null
+Document: lilypond.ja
+Title: GNU LilyPond, the music typesetter
+Author: Various
+Abstract: This documentation describes LilyPond (the GNU Project music
+ typesetter), the LilyPond music input language, and the Mutopia project,
+ a.k.a. "Music To the People."
+Section: Typesetting
+
+Format: HTML
+Index: /usr/share/doc/lilypond/html/index.ja.html
+Files: /usr/share/doc/lilypond/html/*/*/*.ja.html /usr/share/doc/lilypond/html/*/*.ja.html /usr/share/doc/lilypond/html/*.ja.html
--- /dev/null
+usr/share/doc/lilypond/html/*/*/*.ja.html
+usr/share/doc/lilypond/html/*/*.ja.html
+usr/share/doc/lilypond/html/*.ja.html
--- /dev/null
+Document: lilypond.nl
+Title: GNU LilyPond, the music typesetter
+Author: Various
+Abstract: This documentation describes LilyPond (the GNU Project music
+ typesetter), the LilyPond music input language, and the Mutopia project,
+ a.k.a. "Music To the People."
+Section: Typesetting
+
+Format: HTML
+Index: /usr/share/doc/lilypond/html/index.nl.html
+Files: /usr/share/doc/lilypond/html/*/*/*.nl.html /usr/share/doc/lilypond/html/*/*.nl.html /usr/share/doc/lilypond/html/*.nl.html
--- /dev/null
+usr/share/doc/lilypond/html/*/*/*.nl.html
+usr/share/doc/lilypond/html/*/*.nl.html
+usr/share/doc/lilypond/html/*.nl.html
--- /dev/null
+Document: lilypond.zh
+Title: GNU LilyPond, the music typesetter
+Author: Various
+Abstract: This documentation describes LilyPond (the GNU Project music
+ typesetter), the LilyPond music input language, and the Mutopia project,
+ a.k.a. "Music To the People."
+Section: Typesetting
+
+Format: HTML
+Index: /usr/share/doc/lilypond/html/index.zh.html
+Files: /usr/share/doc/lilypond/html/*/*/*.zh.html /usr/share/doc/lilypond/html/*/*.zh.html /usr/share/doc/lilypond/html/*.zh.html
--- /dev/null
+usr/share/doc/lilypond/html/*/*/*.zh.html
+usr/share/doc/lilypond/html/*/*.zh.html
+usr/share/doc/lilypond/html/*.zh.html
--- /dev/null
+Document: lilypond
+Title: GNU LilyPond, the music typesetter
+Author: Various
+Abstract: This documentation describes LilyPond (the GNU Project music
+ typesetter), the LilyPond music input language, and the Mutopia project,
+ a.k.a. "Music To the People."
+Section: Typesetting
+
+Format: HTML
+Index: /usr/share/doc/lilypond/html/index.html
+Files: /usr/share/doc/lilypond/html/*.html /usr/share/doc/lilypond/html/Documentation/*.html /usr/share/doc/lilypond/html/Documentation/*/*.html
--- /dev/null
+# This install file is overwritten in the override_dh_install rule in
+# debian/rules. Do not attempt to modify what is installed in the
+# lilypond-doc-html package here.
--- /dev/null
+Document: lilypond.de
+Title: GNU LilyPond, the music typesetter
+Author: Various
+Abstract: This documentation describes LilyPond (the GNU Project music
+ typesetter), the LilyPond music input language, and the Mutopia project,
+ a.k.a. "Music To the People."
+Section: Typesetting
+
+Format: PDF
+Files: /usr/share/doc/lilypond/html/Documentation/*.de.pdf*
--- /dev/null
+usr/share/doc/lilypond/html/*/*.de.pdf
--- /dev/null
+Document: lilypond.es
+Title: GNU LilyPond, the music typesetter
+Author: Various
+Abstract: This documentation describes LilyPond (the GNU Project music
+ typesetter), the LilyPond music input language, and the Mutopia project,
+ a.k.a. "Music To the People."
+Section: Typesetting
+
+Format: PDF
+Files: /usr/share/doc/lilypond/html/Documentation/*.es.pdf*
--- /dev/null
+usr/share/doc/lilypond/html/*/*.es.pdf
--- /dev/null
+Document: lilypond.fr
+Title: GNU LilyPond, the music typesetter
+Author: Various
+Abstract: This documentation describes LilyPond (the GNU Project music
+ typesetter), the LilyPond music input language, and the Mutopia project,
+ a.k.a. "Music To the People."
+Section: Typesetting
+
+Format: PDF
+Files: /usr/share/doc/lilypond/html/Documentation/*.fr.pdf*
--- /dev/null
+usr/share/doc/lilypond/html/*/*.fr.pdf
--- /dev/null
+Document: lilypond.hu
+Title: GNU LilyPond, the music typesetter
+Author: Various
+Abstract: This documentation describes LilyPond (the GNU Project music
+ typesetter), the LilyPond music input language, and the Mutopia project,
+ a.k.a. "Music To the People."
+Section: Typesetting
+
+Format: PDF
+Files: /usr/share/doc/lilypond/html/Documentation/*.hu.pdf*
--- /dev/null
+usr/share/doc/lilypond/html/*/*.hu.pdf
--- /dev/null
+Document: lilypond.it
+Title: GNU LilyPond, the music typesetter
+Author: Various
+Abstract: This documentation describes LilyPond (the GNU Project music
+ typesetter), the LilyPond music input language, and the Mutopia project,
+ a.k.a. "Music To the People."
+Section: Typesetting
+
+Format: PDF
+Files: /usr/share/doc/lilypond/html/Documentation/*.it.pdf*
--- /dev/null
+usr/share/doc/lilypond/html/*/*.it.pdf
--- /dev/null
+Document: lilypond.nl
+Title: GNU LilyPond, the music typesetter
+Author: Various
+Abstract: This documentation describes LilyPond (the GNU Project music
+ typesetter), the LilyPond music input language, and the Mutopia project,
+ a.k.a. "Music To the People."
+Section: Typesetting
+
+Format: PDF
+Files: /usr/share/doc/lilypond/html/Documentation/*.nl.pdf*
--- /dev/null
+usr/share/doc/lilypond/html/*/*.nl.pdf
--- /dev/null
+Document: lilypond
+Title: GNU LilyPond, the music typesetter
+Author: Various
+Abstract: This documentation describes LilyPond (the GNU Project music
+ typesetter), the LilyPond music input language, and the Mutopia project,
+ a.k.a. "Music To the People."
+Section: Typesetting
+
+Format: PDF
+Files: /usr/share/doc/lilypond/html/Documentation/*.pdf* /usr/share/doc/lilypond/html/Documentation/*/*.pdf* /usr/share/doc/lilypond/html/Documentation/*/*/*.pdf*
--- /dev/null
+# This install file is overwritten in the override_dh_install rule in
+# debian/rules. Do not attempt to modify what is installed in the
+# lilypond-doc-html package here.
--- /dev/null
+lilypond-doc for Debian
+-----------------------
+
+The HTML, PostScript and DVI documentation files are installed under
+`/usr/share/doc/lilypond', not `/usr/share/doc/lilypond-doc'.
+
+Anthony Fok <foka@debian.org>, Wed, 16 May 2001 01:37:00 -0600
--- /dev/null
+usr/share/doc/lilypond/html
+usr/share/info
--- /dev/null
+Document: lilypond
+Title: GNU LilyPond, the music typesetter
+Author: Various
+Abstract: This documentation describes LilyPond (the GNU Project music
+ typesetter), the LilyPond music input language, and the Mutopia project,
+ a.k.a. "Music To the People."
+Section: Typesetting
+
+Format: Text
+Files: /usr/share/doc/lilypond/html/Documentation/*.txt*
+
+Format: Info
+Index: /usr/share/info/lilypond-usage.info.gz
+Files: /usr/share/info/lilypond-*.info*
--- /dev/null
+usr/share/info
+usr/share/doc/lilypond/html/VERSION
+usr/share/doc/lilypond/html/Documentation/*.txt
--- /dev/null
+# we ship usr/share/info/lilypond as a symlink into the documentation
+# for images in info documents
+lilypond-doc binary: info-document-not-compressed usr/share/info/lilypond
--- /dev/null
+AUTHORS.txt
+NEWS.txt
+README.txt
+DEDICATION
+THANKS
--- /dev/null
+usr/bin
+usr/share/locale
+usr/share/man
+usr/lib
--- /dev/null
+lilypond binary: spelling-error-in-binary usr/bin/lilypond This packages These packages
--- /dev/null
+From 42cb7d446827dce32a42b5b243bda522518b3d46 Mon Sep 17 00:00:00 2001
+From: Julien Rioux <julien.rioux@gmail.com>
+Date: Mon, 2 Sep 2013 10:41:50 +0200
+Subject: [PATCH] Keep bison-generated files in sync.
+
+Use a single rule to build header and source files from
+the syntax file, thus avoiding any possibility to have
+`make' rebuild one but not the other, which might happen
+if the syntax and target files have almost the same but
+slightly differing timestamps.
+
+See http://www.mail-archive.com/bug-lilypond@gnu.org/msg37081.html
+
+Fixes issue 3528: Keep bison-generated files in sync.
+http://code.google.com/p/lilypond/issues/detail?id=3528
+---
+ stepmake/stepmake/c++-rules.make | 9 ++-------
+ stepmake/stepmake/c-rules.make | 10 ++--------
+ 2 files changed, 4 insertions(+), 15 deletions(-)
+
+diff --git a/stepmake/stepmake/c++-rules.make b/stepmake/stepmake/c++-rules.make
+index a368f4f..8de00bc 100644
+--- a/stepmake/stepmake/c++-rules.make
++++ b/stepmake/stepmake/c++-rules.make
+@@ -12,13 +12,8 @@ $(outdir)/%.lo: %.cc
+ $(outdir)/%.lo: $(outdir)/%.cc
+ $(DO_LO_DEP) $(CXX) -c $(ALL_CXXFLAGS) $(PIC_FLAGS) -o $@ $<
+
+-$(outdir)/%.cc: %.yy
+- $(BISON) -o $@ $<
+-
+-$(outdir)/%.hh: %.yy
+- $(BISON) -o $(subst .hh,-tmp.cc,$@) -d $<
+- rm $(subst .hh,-tmp.cc,$@)
+- mv $(subst .hh,-tmp.hh,$@) $@
++$(outdir)/%.cc $(outdir)/%.hh: %.yy
++ $(BISON) -d -o $(outdir)/$*.cc $<
+
+ $(outdir)/%.cc: %.ll
+ $(FLEX) -Cfe -p -p -o$@ $<
+diff --git a/stepmake/stepmake/c-rules.make b/stepmake/stepmake/c-rules.make
+index 620275b..954e7a3 100644
+--- a/stepmake/stepmake/c-rules.make
++++ b/stepmake/stepmake/c-rules.make
+@@ -12,14 +12,8 @@ $(outdir)/%.lo: %.c
+ $(outdir)/%.lo: %.c
+ $(DO_LO_DEP) $(CC) -c $(ALL_CFLAGS) $(PIC_FLAGS) -o $@ $<
+
+-$(outdir)/%.c: %.y
+- $(BISON) $<
+- mv $(*F).tab.c $@
+-
+-$(outdir)/%.h: %.y
+- $(BISON) -d $<
+- mv $(*F).tab.h $@
+- rm -f $(*F).tab.c # if this happens in the wrong order it triggers recompile of the .cc file
++$(outdir)/%.c $(outdir)/%.h: %.y
++ $(BISON) -d -o $(outdir)/$*.c $<
+
+ $(outdir)/%.c: %.l
+ $(FLEX) -Cfe -p -p -o$@ $<
+--
+1.8.4.rc3
--- /dev/null
+--- a/lily/freetype.cc
++++ b/lily/freetype.cc
+@@ -20,6 +20,9 @@
+ #include "freetype.hh"
+ #include "warn.hh"
+
++#include FT_OUTLINE_H
++#include FT_BBOX_H
++
+ FT_Library freetype2_library;
+
+ void
+--- a/lily/freetype-error.cc
++++ b/lily/freetype-error.cc
+@@ -31,7 +31,7 @@
+ const char *err_msg;
+ } ft_errors[] =
+
+-#include <freetype/fterrors.h>
++#include FT_ERRORS_H
+
+ ;
+
+--- a/lily/open-type-font.cc
++++ b/lily/open-type-font.cc
+@@ -23,7 +23,7 @@
+
+ using namespace std;
+
+-#include <freetype/tttables.h>
++#include FT_TRUETYPE_TABLES_H
+
+ #include "dimensions.hh"
+ #include "international.hh"
+--- a/lily/pango-font.cc
++++ b/lily/pango-font.cc
+@@ -22,7 +22,7 @@
+ #define PANGO_ENABLE_BACKEND
+
+ #include <pango/pangoft2.h>
+-#include <freetype/ftxf86.h>
++#include FT_XFREE86_H
+
+ #include <map>
+ #include <cstdio>
+--- a/lily/ttf.cc
++++ b/lily/ttf.cc
+@@ -20,7 +20,7 @@
+ #include <cstdio>
+ #include "freetype.hh"
+
+-#include <freetype/tttables.h>
++#include FT_TRUETYPE_TABLES_H
+
+ #include "international.hh"
+ #include "memory-stream.hh"
--- /dev/null
+fix_freetype_inclusions
+fix_bison_parser_generation_rules
--- /dev/null
+#!/bin/sh
+#
+# preinst script for the Debian GNU/Linux lilypond package
+# by Anthony Fok <foka@debian.org>
+# This is free software; see the GNU General Public Licence
+# version 2 or later for copying conditions. There is NO warranty.
+# Last modified: Mon, 5 Apr 1999 20:30:12 -0600
+
+set -e
+
+package=lilypond
+font_supplier=public
+font_typeface=lilypond
+std_TEXMFMAIN=/usr/share/texmf
+std_VARTEXFONTS=/var/spool/texmf
+
+#DEBHELPER#
+
+TEXMFMAIN=`kpsewhich -expand-var '$TEXMFMAIN'`
+: ${TEXMFMAIN:=$std_TEXMFMAIN}
+VARTEXFONTS=`kpsewhich -expand-var '$VARTEXFONTS'`
+: ${VARTEXFONTS=$std_VARTEXFONTS}
+
+LILYTEXINPUTS=$TEXMFMAIN/tex/$package
+LILYMFINPUTS=$TEXMFMAIN/fonts/source/$font_supplier/$font_typeface
+
+case "$1" in
+ install|upgrade)
+ # Clear out the old TFM and PK files in case the fonts were
+ # left-over from previous installations
+ rm -rf $VARTEXFONTS/tfm/$font_supplier/$font_typeface
+ rm -rf $VARTEXFONTS/pk/*/$font_supplier/$font_typeface
+
+ # Fix a silly bug in Debian's lilypond 1.0.17-1. :-)
+ if [ "$2" = "1.0.17-1" ]; then
+ rm -rf $VARTEXFONTS/tfm/$font_supplier/mf
+ rm -rf $VARTEXFONTS/pk/*/$font_supplier/mf
+ fi
+ ;;
+
+ abort-upgrade)
+ ;;
+
+ *)
+ echo "$0 called with unknown argument \`$1'" >&2
+ exit 0
+ ;;
+
+esac
--- /dev/null
+#!/usr/bin/make -f
+# debian/rules for LilyPond in Debian.
+#
+# This is free software; see the GNU General Public Licence
+# version 2 or later for copying conditions. There is NO warranty.
+#
+
+export MAILADDRESS = lilypond@packages.debian.org
+
+# fontconfig blows chunks if it can't write to $HOME; and some
+# buildds set it to a bogus value.
+export HOME = /tmp
+
+DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH)
+CFLAGS := $(shell dpkg-buildflags --get CFLAGS)
+CXXFLAGS := $(shell dpkg-buildflags --get CXXFLAGS)
+ifneq (,$(filter $(DEB_HOST_ARCH), i386 kfreebsd-i386))
+ config_opt = --disable-optimising
+ CFLAGS := $(filter-out -O%, $(CFLAGS))
+ CXXFLAGS := $(filter-out -O%, $(CXXFLAGS))
+else
+ifneq (,$(filter $(DEB_BUILD_OPTIONS),noopt))
+ config_opt = --disable-optimising
+else
+ config_opt = --enable-optimising
+endif
+endif
+
+DOC_OPTIONS := WEB_TARGETS="offline"
+ifneq (,$(filter parallel=%,$(DEB_BUILD_OPTIONS)))
+ DOC_OPTIONS := $(DOC_OPTIONS) CPU_COUNT=$(firstword $(patsubst parallel=%,%,$(filter parallel=%,$(DEB_BUILD_OPTIONS))))
+endif
+
+%:
+ dh $@ --parallel --with autotools-dev --with python2 --with quilt
+
+
+## we need to nuke the parser files, because if there is a mistmatch
+## between upstreams bison and our bison, the build will fail epically
+override_dh_auto_configure:
+ rm -f lily/out/parser.*
+ dh_auto_configure -- --disable-checking --enable-debugging $(config_opt)
+
+override_dh_auto_build-indep:
+ dh_auto_build
+ $(MAKE) doc $(DOC_OPTIONS)
+
+override_dh_auto_install-indep:
+ $(MAKE) install-doc $(DOC_OPTIONS) prefix=$(CURDIR)/debian/tmp/usr/
+ $(MAKE) install-info $(DOC_OPTIONS) prefix=$(CURDIR)/debian/tmp/usr
+ rm -rf $(CURDIR)/debian/tmp/usr/share/omf
+ rm -rf $(CURDIR)/debian/tmp/usr/share/doc/lilypond/html/input
+
+## Unfortunately, lilypond is kind of broken, and installs the wrong
+## info documentation (missing images) if we call their makefile
+## directly. They also don't provide an install rule which doesn't
+## install the documentation, which we don't care about for the
+## architecture dependent build
+override_dh_auto_install-arch:
+ for dir in `echo */*makefile|xargs -n 1 dirname|grep -v Documentation`; do \
+ $(MAKE) --no-builtin-rules PACKAGE=LILYPOND package=lilypond -C $$dir install $(DOC_OPTIONS) prefix=$(CURDIR)/debian/tmp/usr/; \
+ done;
+
+## we need to nuke the parser files, because if there is a mistmatch
+## between upstreams bison and our bison, the build will fail epically
+override_dh_auto_clean:
+ rm -f lily/out/parser.*
+ dh_auto_clean
+
+## we need to install only the png, jpg, css, ly and english html
+## files into the doc-html package, and only the english pdfs into the
+## doc-pdf package. Because dh_install doesn't support regexes, we'll
+## use find to replace the contents of the .install file before we
+## call dh_install
+override_dh_install:
+ /bin/echo -e 'usr/share/doc/lilypond/html/*/*/*.ly\nusr/share/doc/lilypond/html/*/*/*.png' \
+ > $(CURDIR)/debian/lilypond-doc-html.install
+ /bin/echo -e 'usr/share/doc/lilypond/html/*/*/*.jpg\nusr/share/doc/lilypond/html/*/*/*.css' \
+ >> $(CURDIR)/debian/lilypond-doc-html.install
+ find $(CURDIR)/debian/tmp/ -type f \
+ -regex '.*usr/share/doc/lilypond/.*/[^\.]+.html' \
+ -printf '%P\n' >> $(CURDIR)/debian/lilypond-doc-html.install
+ /bin/echo -e ''> $(CURDIR)/debian/lilypond-doc-pdf.install
+ find $(CURDIR)/debian/tmp/ -type f \
+ -regex '.*usr/share/doc/lilypond/.*/[^\.]+.pdf' \
+ -printf '%P\n' >> $(CURDIR)/debian/lilypond-doc-pdf.install
+ find $(CURDIR)/debian/tmp/ -type f \
+ -regex '.*usr/share/doc/lilypond/.*/[^\.]+.preview.pdf' \
+ -printf '%P\n' >> $(CURDIR)/debian/lilypond-doc-pdf.install
+ dh_install --list-missing
+
+override_dh_python2:
+ dh_python2
+ dh_python2 usr/share/lilypond/*/python/
+
+override_dh_compress:
+ dh_compress -X.ly
+
+override_dh_installdocs:
+ dh_installdocs
+ for a in $(wildcard $(CURDIR)/debian/*.doc-base-special); do \
+ package=`basename $$a .doc-base-special`; \
+ install -d debian/$$package/usr/share/doc-base; \
+ install -m0644 $$a debian/$$package/usr/share/doc-base/$$package; \
+ done;
+
+## this rule will update debian/control and the per-language install
+## files; all of the files it generates/modifies should be included in
+## the Debian package and should not need to be regenerated or
+## modified.
+update-doc-packages:
+ perl debian/update_doc_packages
--- /dev/null
+#!/usr/bin/perl
+# update_doc_packages updates debian/control for the lilypond debian
+# package, and is released under the terms of the GPL version 2, or
+# any later version, at your option. See the file README and COPYING
+# for more information.
+# Copyright 2012 by Don Armstrong <don@debian.org>.
+
+use warnings;
+use strict;
+
+use IO::File;
+
+my $cfh = IO::File->new("debian/control",'r') or
+ die "Unable to open debian/control for reading: $!";
+
+my $dfh = IO::File->new("debian/doc_languages.txt",'r') or
+ die "Unable to open debian/doc_languages.txt for reading: $!";
+
+# read in languages
+my %languages;
+while (<$dfh>) {
+ chomp;
+ my ($type,$short,$long) = split /\s+/;
+ $languages{$type}{$short} = $long;
+}
+
+# parse control file
+my $new_control_file;
+my $discard_stanza = 0;
+while (<$cfh>) {
+ if (/^Package: lilypond-doc-(pdf|html)-.*/) {
+ $discard_stanza = 1;
+ }
+ if (/^\n?$/) {
+ if ($discard_stanza) {
+ $discard_stanza = 0;
+ next;
+ }
+ }
+ next if $discard_stanza;
+ $new_control_file .= $_;
+}
+close($cfh);
+
+for my $type (sort keys %languages) {
+ my $uc_type = uc($type);
+ my $recommends = '';
+ my $depends = '';
+ if ($type eq 'html') {
+ $recommends = '';
+ # this is required because the images are only in the -html
+ # package
+ $depends = ', lilypond-doc-html'
+ } else {
+ $recommends = "\nRecommends: evince | pdf-viewer";
+ }
+ for my $lang (sort keys %{$languages{$type}}) {
+ my $ucfirst_long_lang = ucfirst($languages{$type}{$lang});
+ # write out the control file stanza
+ $new_control_file .= <<EOF;
+Package: lilypond-doc-$type-$lang
+Section: doc
+Architecture: all
+Depends: \${misc:Depends}, dpkg (>= 1.15.4) | install-info${depends}${recommends}
+Suggests: lilypond (>= \${source:Version})
+Replaces: lilypond-doc (< 2.16.2-1~exp+1)
+Breaks: lilypond-doc (< 2.16.2-1~exp+1)
+Description: LilyPond $uc_type Documentation in $ucfirst_long_lang
+ LilyPond is a music typesetter, an automated engraving system. It
+ produces beautiful sheet music using a high level description file as input.
+ .
+ This package contains the $uc_type documentation in $ucfirst_long_lang for the
+ LilyPond music typesetting software.
+
+EOF
+ # write out the package.install file for this example
+ my $install_fh = IO::File->new("debian/lilypond-doc-$type-${lang}.install",'w') or
+ die "Unable to open debian/lilypond-doc-$type-${lang}.install for writing: $!";
+ if ($type eq 'html') {
+ print {$install_fh} <<EOF;
+usr/share/doc/lilypond/html/*/*/*.${lang}.html
+usr/share/doc/lilypond/html/*/*.${lang}.html
+usr/share/doc/lilypond/html/*.${lang}.html
+EOF
+
+ } else {
+ print {$install_fh} <<EOF;
+usr/share/doc/lilypond/html/*/*.${lang}.pdf
+EOF
+ }
+ close($install_fh);
+ my $docbase_fh = IO::File->new("debian/lilypond-doc-$type-${lang}.doc-base-special",'w') or
+ die "Unable to open debian/lilypond-doc-$type-${lang}.doc-base-special for writing: $!";
+ print {$docbase_fh} <<EOF;
+Document: lilypond.${lang}
+Title: GNU LilyPond, the music typesetter
+Author: Various
+Abstract: This documentation describes LilyPond (the GNU Project music
+ typesetter), the LilyPond music input language, and the Mutopia project,
+ a.k.a. "Music To the People."
+Section: Typesetting
+
+EOF
+ if ($type eq 'html') {
+ print {$docbase_fh} <<EOF;
+Format: HTML
+Index: /usr/share/doc/lilypond/html/index.${lang}.html
+Files: /usr/share/doc/lilypond/html/*/*/*.${lang}.html /usr/share/doc/lilypond/html/*/*.${lang}.html /usr/share/doc/lilypond/html/*.${lang}.html
+EOF
+
+ } else {
+ print {$docbase_fh} <<EOF;
+Format: PDF
+Files: /usr/share/doc/lilypond/html/Documentation/*.${lang}.pdf*
+EOF
+ }
+ close ($docbase_fh);
+ }
+}
+
+$cfh = IO::File->new('debian/control','w') or
+ die "Unable to open debian/control for writing: $!";
+print {$cfh} $new_control_file;
+
+close($cfh);
--- /dev/null
+# LilyPond watch control file for uscan
+# Rename this file to "watch" and then you can run the "uscan" command
+# to check for upstream updates and more.
+# Site Directory Pattern Version Script
+# we will ignore all odd minor version numbers, because they are developmental versions
+version=3
+http://lilypond.org/download/sources/v(\d+\.\d*[02468])/lilypond-(.*)\.tar\.gz debian uupdate
string
get_working_directory ()
{
+#ifdef _GNU_SOURCE_
+ return string (get_current_dir_name());
+#else
char cwd[PATH_MAX];
// getcwd returns NULL upon a failure, contents of cwd would be undefined!
return string (getcwd (cwd, PATH_MAX));
+#endif
}
/* Join components to full file_name. */
*/
#include "midi-stream.hh"
-
+#include <cstring>
#include <cerrno>
using namespace std;
#include "item.hh"
#include "translator.icc"
+#include <cstring>
#include <string.h>
#include "item.hh"
#include "input.hh"
#include "profile.hh"
-
+#include <cstring>
#include "ly-smobs.icc"
IMPLEMENT_SMOBS (Prob);
/* TODO: autoconf support */
+#include <ctype.h>
#include <sys/types.h>
#include <dirent.h>
+#include <cstring>
#if HAVE_GETTEXT
#include <libintl.h>
#endif /* GCC_MAJOR < 4 */
#include "source-file.hh"
-
+#include <cstring>
#include "config.hh"
#include <cstdio>
*/
#include "translator.hh"
-
+#include <cstring>
#include "context-def.hh"
#include "dispatcher.hh"
#include "global-context.hh"
~a\
~a\
-dGraphicsAlphaBits=4\
+ -q\
-dTextAlphaBits=4\
-dNOPAUSE\
-sDEVICE=~a\
RetVal=$? # captures the return value of the command
if [ $RetVal -ne 0 ]; then
echo
- echo "Please check the logfile" $2 "for errors"
+ echo "Please check the logfile" $2 "for errors:"
+ cat $2
echo
fi
exit $RetVal
-# We must invoke the generated $(outdir)/help2man script instead of
-# the help2man.pl source, which means that the scripts/build directory
-# must be built first.
-#
-# From the perlrun man-page:
-#
-# If the #! line does not contain the word "perl", the
-# program named after the #! is executed instead of the Perl
-# interpreter. This is slightly bizarre, but it helps
-#
-# Indeed it is. Perl sucks.
-#
-# Two screenfulls explaining that the otherwise standard #! is broken
-# for perl, and arguing that this broken magic is better in some
-# cases. Four more explaining what a line comment is, and that it may
-# be parsed, same here.
-
+# The distributed help2man sucks; use the Debian version instead.
ifeq ($(PYTHON),$(TARGET_PYTHON))
-HELP2MAN_COMMAND = $(buildscript-dir)/help2man $< > $@
+HELP2MAN_COMMAND = help2man $< > $@
else
-HELP2MAN_COMMAND = $(buildscript-dir)/help2man "env $$(basename $$(head -1 $<)) $<" > $@
+HELP2MAN_COMMAND = help2man "env $$(basename $$(head -1 $<)) $<" > $@
endif
ifeq ($(strip $(CROSS)),no)
$(outdir)/%.1: out/%.1
cp $< $@
endif
-
-$(buildscript-dir)/help2man:
- $(MAKE) -C $(depth)/scripts/build
projects / lilypond.git / commitdiff