diff options
| author | Carl Sorensen <carl.d.sorensen@gmail.com> | 2016-08-06 12:37:49 -0600 |
|---|---|---|
| committer | Carl Sorensen <carl.d.sorensen@gmail.com> | 2016-08-06 21:04:26 -0600 |
| commit | 8c1840ca28a05b3dad8d595e04d03779ba0a286a (patch) | |
| tree | 3e26ac418fb2b568127fbe57896575aa8ec60b07 | |
| parent | 05d4dc393a4fa09b354470ab629d67ff1e7e05e8 (diff) | |
Change Lilypond to LilyPond where it refers to the software
68 files changed, 249 insertions, 249 deletions
diff --git a/Documentation/ca/learning/tutorial.itely b/Documentation/ca/learning/tutorial.itely index 054ef1acf9..bfa1adeef0 100644 --- a/Documentation/ca/learning/tutorial.itely +++ b/Documentation/ca/learning/tutorial.itely @@ -16,7 +16,7 @@ @chapter Tutorial @translationof Tutorial -Aquest capítol ofereix una introducció bàsica al treball amb el Lilypond. +Aquest capítol ofereix una introducció bàsica al treball amb el LilyPond. @menu * Compilació d'un fitxer:: @@ -78,7 +78,7 @@ El resultat té aquest aspecte: @end lilypond @warning{la música i la lletra escrita al codi d'entrada del -Lilypond ha d'anar sempre entre @w{@strong{@{ claudàtors @}}}. +LilyPond ha d'anar sempre entre @w{@strong{@{ claudàtors @}}}. Els claudàtors haurien també d'estar rodejats per espais a no ser que es trobin al principi o al final d'una línia, per evitar ambigüitats. És possible que s'ometen en alguns exemples del @@ -87,7 +87,7 @@ Per veure més informació sobre la presentació dels exemples del manual, consulteu @ref{Com llegir els manuals}.} -A més, l'entrada del Lilypond és @strong{sensible a les majúscules}. +A més, l'entrada del LilyPond és @strong{sensible a les majúscules}. @w{@samp{ @{ c d e @}}} és una entrada vàlida; @w{@samp{@{ C D E @}}} produeix un missatge d'error. diff --git a/Documentation/ca/learning/tweaks.itely b/Documentation/ca/learning/tweaks.itely index 51ed7395fc..450f030b70 100644 --- a/Documentation/ca/learning/tweaks.itely +++ b/Documentation/ca/learning/tweaks.itely @@ -78,7 +78,7 @@ són fonamentals per comprendre i construir els ajustaments. @cindex objecte de disposició L'ajustament consisteix en modificar el funcionament i estructure -interna del programa Lilypond, per la qual cosa en primer lloc +interna del programa LilyPond, per la qual cosa en primer lloc introduirem alguns termes que es fan servir per descriure aquestes operacions i estructures internes. @@ -269,7 +269,7 @@ bàsiques com ara números, cadenes de caràcters i llistes, es processen al @q{mode de l'Scheme}, que s'invoca mitjançant del prefix @samp{#} escrit abans del valor. Tot i que els valors poden tenir a vegades una representació vàlida al mode de música -del Lilypond, aquest manual utilitza sempre @samp{#} per a +del LilyPond, aquest manual utilitza sempre @samp{#} per a l'escriptura, per coherència. Per obtenir més informació sobre el mode de l'Scheme, consulteu @rextendnamed{LilyPond Scheme-Syntax,Sintaxi de l'Scheme del LilyPond}. @@ -4665,7 +4665,7 @@ fitxers de música amb un @code{\include "../global.ily"}, que conté @translationof Other sources of information La documentació del manual de Referència de Funcionament Intern -conté muntanyes d'informació sobre el Lilypond, però es pot +conté muntanyes d'informació sobre el LilyPond, però es pot obtenir més informació encara llegint els fitxers interns del LilyPond. Per donar-los una ullada, en primer lloc heu de buscar la carpeta corresponent al seu sistema. La ubicació d'aquesta @@ -4713,7 +4713,7 @@ compilat a partir de la font Dirigiu-vos a @file{@var{PREFIX}/share/lilypond/@var{X.Y.Z}/}, on @var{PREFIX} s'ha establert pel vostre administrador de paquets o guió @code{configure}, i @var{X.Y.Z} es el número de la versió del -Lilypond. +LilyPond. @smallspace diff --git a/Documentation/ca/notation.tely b/Documentation/ca/notation.tely index 86298d8c25..90f9207a45 100644 --- a/Documentation/ca/notation.tely +++ b/Documentation/ca/notation.tely @@ -15,7 +15,7 @@ @macro manualIntro Aquest manual ofereix una referència per a tota la notació musical que -es pot produir amb el Lilypond versió @version{}. S'entén que el +es pot produir amb el LilyPond versió @version{}. S'entén que el lector està familiaritzat amb el material que hi ha a @rlearningnamed{Top, Manual d'aprenentatge}. @end macro @@ -94,7 +94,7 @@ Annexos @translationof LilyPond command index Aquest índex fa una relació de totes les ordres i paraules clau -del Lilypond, amb enllaços a aquelles seccions del manual que +del LilyPond, amb enllaços a aquelles seccions del manual que descriuen o s'ocupen del seu ús. Cadascú d'aquests enllaços consta de dues parts. La primera part apunta a la situació exacta del manual en el qual apareix l'ordre o paraula clau; la segona diff --git a/Documentation/ca/usage/running.itely b/Documentation/ca/usage/running.itely index 7d4f3b9abe..bcf55d0963 100644 --- a/Documentation/ca/usage/running.itely +++ b/Documentation/ca/usage/running.itely @@ -435,7 +435,7 @@ cada pàgina de sortida. Es recomana instal·lar el tipus de lletra Century Schoolbook, que està inclòs a la instal·lació del LilyPond, per a un renderitzat òptim. Sota l'UNIX, bastarà amb que copieu aquests fitxers de tipus de lletra del directori del -Lilypond (normalment @file{/usr/share/lilypond/VERSION/fonts/otf/}) +LilyPond (normalment @file{/usr/share/lilypond/VERSION/fonts/otf/}) al directori @file{~/.fonts/}. La sortida @code{SVG} hauria de ser compatible amb qualsevol editor o client de SVG. També hi ha una opció @code{svg-woff} (vegeu més avall) per usar els fitxers diff --git a/Documentation/ca/web.texi b/Documentation/ca/web.texi index 377a1b6fd8..e271246048 100644 --- a/Documentation/ca/web.texi +++ b/Documentation/ca/web.texi @@ -56,16 +56,16 @@ Free Documentation License''. @c expected to be found in lilypond/ subdirectory. @dircategory GNU LilyPond: el gravador de música @direntry -* Manual d'aprenentatge del Lilypond:(lilypond-learning). Comenceu per aquí. +* Manual d'aprenentatge del LilyPond:(lilypond-learning). Comenceu per aquí. * Glosari musical: (music-glossary). Per a usuaris de parla no anglesa -* LilyPond: (lilypond-notation). Referència de la notació amb el Lilypond. +* LilyPond: (lilypond-notation). Referència de la notació amb el LilyPond. * Fragments de codi del LilyPond: (lilypond-snippets). Consells, trucs i exemples curts. * Referència de funcionament intern: (lilypond-internals). Definicions pera a la construcció de trucs. * Utilització del prrograma: (lilypond-usage). Instal·lació i execució de les aplicacions * Pàgina web: (lilypond-web). Vista prèvia de la nova pàgina. -* lilypond: (lilypond-usage)Executar el Lilypond. Invocar el programa LilyPond. +* lilypond: (lilypond-usage)Executar el LilyPond. Invocar el programa LilyPond. * abc2ly: (lilypond-usage)Invocació d'abc2ly. Importació d'ABC. -* convert-ly: (lilypond-usage)Actualització de fitxers mitjançant convert-ly. Versions antigues del Lilypond. +* convert-ly: (lilypond-usage)Actualització de fitxers mitjançant convert-ly. Versions antigues del LilyPond. * etf2ly: (lilypond-usage)Invocar etf2ly. Importació del Finale. * lilypond-book: (lilypond-usage)LilyPond-book. Intergrar text i música. * midi2ly: (lilypond-usage)Invocar midi2ly. Importació de MIDI. @@ -119,13 +119,13 @@ Per al LilyPond versió @version{} @divId{quickSummary} @subheading ¿Què és el LilyPond? -El Lilypond és un programa de gravat musical +El LilyPond és un programa de gravat musical (tipografia musical o edició de partitures), consagrat a la producció de partitures de la qualitat més alta possible. Introdueix l'estètica de la música gravada de la forma tradicional a les partitures impreses mijtançant l'ordinador. -Lilypond és programari lliure i forma part del +LilyPond és programari lliure i forma part del @uref{http://www.gnu.org/home.ca.html,Projecte GNU}. diff --git a/Documentation/ca/web/community.itexi b/Documentation/ca/web/community.itexi index 8264c97144..c8eba165de 100644 --- a/Documentation/ca/web/community.itexi +++ b/Documentation/ca/web/community.itexi @@ -201,7 +201,7 @@ fòrum d'holandès} @divClass{column-right-top} @subheading Esteu sempre informat -@subsubheading LilyPond Report (l'Informe Lilypond) +@subsubheading LilyPond Report (l'Informe LilyPond) La manera més fàcil d'estar en contacte és llegir el butlletí de la nostra comunitat, l'Informe LilyPond: diff --git a/Documentation/ca/web/introduction.itexi b/Documentation/ca/web/introduction.itexi index cc928d34f7..cd7236fc4f 100644 --- a/Documentation/ca/web/introduction.itexi +++ b/Documentation/ca/web/introduction.itexi @@ -33,7 +33,7 @@ les millors tradicions del gravat musical clàssic. @divClass{link-headings} @divClass{column-left-top} -@subheading Què fa el Lilypond +@subheading Què fa el LilyPond @itemize @@ -86,14 +86,14 @@ les millors tradicions del gravat musical clàssic. @c menu. -JM @divClass{hide} @menu -* Possibilitats:: Què pot fer el Lilypond? +* Possibilitats:: Què pot fer el LilyPond? * Exemples:: Vull veure alguna música! * Llibertat:: La llibertat i la GPL. * Rerefons:: Estètica computacional. * Produccions:: Ús del LilyPond a la vida real. -* Ressenyes:: Què diu la gent sobre el Lilypond? +* Ressenyes:: Què diu la gent sobre el LilyPond? * Entrada de text:: Escriviu música com si fos @emph{text}?! -* Entorns millorats:: Altres formes de treballar amb el Lilypond. +* Entorns millorats:: Altres formes de treballar amb el LilyPond. @end menu @divEnd @@ -116,7 +116,7 @@ empleat milers d'hores a desenvolupar un programa de gravat musical que produeix com a resultat música impresa de forma bella. Tots els ajustos d'estil del LilyPond, el disseny dels tipus de lletra i els algoritmes s'han inspirat en la millor -música gravada a mà. La sortida del Lilypond té el mateix aspecte +música gravada a mà. La sortida del LilyPond té el mateix aspecte robust, equilibrat i elegant que les partitures clàssiques millor gravades. Tot això s'explica amb detall a la nostra @ressaynamed{Essay,Monografia}. @@ -163,7 +163,7 @@ amb alguna dificultat manual que no poden teclejar o usar un ratolí d'ordinador, poden usar programari de reconeixement de veu per editar els fitxers del LilyPond. Fins i tot les persones totalment cegues poden usar lectors de pantalla per escriure els fitxers del -Lilypond (una tasca impossible als programes d'edició de +LilyPond (una tasca impossible als programes d'edició de partitures basats en gràfics). @subsubheading Disseny ampliable @@ -207,7 +207,7 @@ que els problemes es resolen amb rapidesa. @subsubheading Editors millorats Diversos desenvolupadors que són a l'hora usuaris actius del -Lilypond han escrit eines orientades específicament a fer més +LilyPond han escrit eines orientades específicament a fer més fàcil i efectiu el procés d'editar fitxers del LilyPond. Per veure alguns exemples, consulteu @ref{Entorns millorats}. @@ -639,7 +639,7 @@ Montpellier}, a França. El @uref{http://www.mutopiaproject.org/index.html, Projecte Mutopia} inclou més de 1500 partitures de música clàssica per a la seva descàrrega lliure, i és el principal aparador de partitures del -Lilypond. +LilyPond. @c don't make this "Mutopia" a link, since that looks silly. @item @@ -802,7 +802,7 @@ partitures produïdes pel LilyPond son excepcionalment boniques Juliol/agost de 2004 Dave Phillips va escriure un article introductori per a Linux -Journal At the Sounding edge: Lilypond, +Journal At the Sounding edge: LilyPond, @uref{http://www.linuxjournal.com/article/7657, primera} i @uref{http://www.linuxjournal.com/article/7719, segona} part. @@ -950,7 +950,7 @@ bellesa. Això és massa modèstia! (@dots{}) a mesura que el LilyPond millora contínuament i observo com es fan les coses amb el Scheme, tinc cada cop menys frustracions. De totes maneres el que vull dir és: gràcies per -donar-nos el Lilypond, és realment bo.} +donar-nos el LilyPond, és realment bo.} @divEnd diff --git a/Documentation/ca/web/manuals.itexi b/Documentation/ca/web/manuals.itexi index ef979eb764..32ef0021b7 100644 --- a/Documentation/ca/web/manuals.itexi +++ b/Documentation/ca/web/manuals.itexi @@ -133,7 +133,7 @@ Versions estables anteriors i versió actual com un fitxer comprimit. estat del procés de traducció per a lectors no anglòfons. @item -@uref{http://lsr@/.dsi@/.unimi@/.it,LilyPond Snippet Repository (el magatzem de fragments de codi del Lilypond)}: +@uref{http://lsr@/.dsi@/.unimi@/.it,LilyPond Snippet Repository (el magatzem de fragments de codi del LilyPond)}: exemples, consells, i trucs creats pels usuaris. @item diff --git a/Documentation/ca/web/news-front.itexi b/Documentation/ca/web/news-front.itexi index 8fe5d07c28..0a0869026c 100644 --- a/Documentation/ca/web/news-front.itexi +++ b/Documentation/ca/web/news-front.itexi @@ -30,7 +30,7 @@ l'ús de la versió 2.18. @newsEnd @newsItem -@subsubheading Lilypond 2.18.2 llençat el @emph{23 de març de 2014}! +@subsubheading LilyPond 2.18.2 llençat el @emph{23 de març de 2014}! Estem orgullosos d'anunciar el llançament del GNU LilyPond 2.18.2. El LilyPond és un programa de gravat musical dedicat a la @@ -73,7 +73,7 @@ aportant una contribució a la campanya Indiegogo [5]! @newsItem -@subsubheading Lilypond 2.18.0 llençat el @emph{29 de Desembre de 2013}! +@subsubheading LilyPond 2.18.0 llençat el @emph{29 de Desembre de 2013}! Estem orgullosos d'anunciar el llançament del GNU LilyPond 2.18.0. El LilyPond és un programa de gravat musical dedicat a la @@ -216,7 +216,7 @@ aquesta versió. @newsEnd @newsItem -@subsubheading Lilypond 2.16.0 llençat el @emph{24 d'agost de 2012}! +@subsubheading LilyPond 2.16.0 llençat el @emph{24 d'agost de 2012}! Estem orgullosos d'anunciar el llançament del GNU LilyPond 2.16.1. El LilyPond és un programa de gravat musical, dedicat a diff --git a/Documentation/cs/learning/fundamental.itely b/Documentation/cs/learning/fundamental.itely index 4efdc777bc..e112ed471e 100644 --- a/Documentation/cs/learning/fundamental.itely +++ b/Documentation/cs/learning/fundamental.itely @@ -112,7 +112,7 @@ ale tento příklad slouží jako jednoduchý výchozí bod. @cindex score Až dosud ještě žádný z příkladů příkaz @code{\score@{@}} -nepoužil, neboť Lilypond takové dodatečné příkazy automaticky +nepoužil, neboť LilyPond takové dodatečné příkazy automaticky vkládá v případě potřeby, když má vstupní soubor jednoduchou stavbu. @@ -226,7 +226,7 @@ začátku tohoto oddílu. Pracuje to právě tak dobře. Dvěma dosud neviděnými příkazy jsou @code{\layout @{ @}} a @code{\midi @{@}}. Když se objeví v nějakém -souboru, vede to k tomu, že Lilypond vytvoří tisknutelný soubor PDF +souboru, vede to k tomu, že LilyPond vytvoří tisknutelný soubor PDF popřípadě soubor MIDI. Přesněji jsou popsány v uživatelské příručce - notace -- @ruser{Rozvržení notového zápisu} a @ruser{Vytváření souborů MIDI}. diff --git a/Documentation/cs/learning/tutorial.itely b/Documentation/cs/learning/tutorial.itely index b0de130457..a11e6b6da5 100644 --- a/Documentation/cs/learning/tutorial.itely +++ b/Documentation/cs/learning/tutorial.itely @@ -56,7 +56,7 @@ aby byl vytvořen výstupní soubor. @cindex Malá písmena @qq{Sestavení} je pojem, který se používá pro -přeměnu vstupního souboru pro Lilypond programem LilyPond do +přeměnu vstupního souboru pro LilyPond programem LilyPond do notového výstupu. Výstupními soubory jsou v první řadě soubory PDF (pro prohlížení a tisku), MIDI (pro přehrávání) a PNG (pro používání na internetových stránkách). Vstupními soubory diff --git a/Documentation/cs/usage/running.itely b/Documentation/cs/usage/running.itely index a11801f05f..5d7aee756c 100644 --- a/Documentation/cs/usage/running.itely +++ b/Documentation/cs/usage/running.itely @@ -16,7 +16,7 @@ @chapter Spouštíme @command{lilypond} @translationof Running lilypond -Dieses Kapitel behandelt die technischen Details, wie Lilypond ausgeführt werden kann. +Dieses Kapitel behandelt die technischen Details, wie LilyPond ausgeführt werden kann. @menu @@ -87,7 +87,7 @@ Standarderweiterung für LilyPond-Dateien benutzt. Um Daten von @code{stdin} einzulesen, benutzen Sie einfach einen Bindestrich (@code{-}) als @var{Dateiname}. -Wenn Lilypond die Datei @file{Dateiname.ly} verarbeitet, werden daraus +Wenn LilyPond die Datei @file{Dateiname.ly} verarbeitet, werden daraus die Dateien @file{Dateiname.ps} und @file{Dateiname.pdf} erzeugt. Es können an @code{lilypond} auch mehrere @file{.ly} Dateien übergeben werden, die dann einzeln und voneinander unabhängig abgearbeitet @@ -99,7 +99,7 @@ Falls @file{Dateiname.ly} mehr als eine @code{\book}-Umgebung enthält, werden die weiteren Stücke in durchnummerierte Dateien der Form @file{Dateiname-1.pdf} ausgegeben. Zusätzlich wird der Wert der Variable @code{output-suffix} zwischen den ursprünglichen Dateinamen -und der Zahl eingefügt. Eine Lilypond-Datei @file{Dateiname.ly} mit dem Inhalt +und der Zahl eingefügt. Eine LilyPond-Datei @file{Dateiname.ly} mit dem Inhalt @example #(define output-suffix "Geige") @@ -437,7 +437,7 @@ Dateien müssen in das Jail-Verzeichnis kopiert werden (mit denselben Pfaden wie im tatsächlichen Wurzel-Dateisystem). Die gesamte LilyPond-Installation (typischerweise @file{/usr/share/lilypond}) sollte kopiert werden. -Falls Probleme auftreten, ist es am einfachsten, Lilypond mittels +Falls Probleme auftreten, ist es am einfachsten, LilyPond mittels @command{strace} zu starten, wodurch Sie relativ leicht feststellen können, welche Dateien im Jail noch fehlen. @@ -478,7 +478,7 @@ Zeigt die Garantiebedingungen an, unter denen GNU LilyPond steht. (Es besteht @command{lilypond} erkennt und benützt die folgenden proměnné prostředí: @table @code @item LILYPOND_DATADIR -Diese Variable gibt das Verzeichnis an, wo Lilypond seine eigenen Dateien, +Diese Variable gibt das Verzeichnis an, wo LilyPond seine eigenen Dateien, Meldungen und Übersetzungen finden kann. Dieses Verzeichnis sollte Unterverzeichnisse @file{ly/}, @file{ps/}, @file{tex/}, etc. beinhalten. @@ -693,7 +693,7 @@ test.ly:2:19: Fehler: keine gültige Dauer: 5 Diese Stellen sind LilyPonds Vermutung, wo die Warnung oder der Fehler aufgetreten ist, allerdings treten Warnungen und Fehler ja gerade in -unerwarteten Fällen auf. Manchmal kann Lilypond auch eine fehlerhafte +unerwarteten Fällen auf. Manchmal kann LilyPond auch eine fehlerhafte Stelle zwar noch problemlos verarbeiten, ein paar Zeilen später wirkt sich der Fehler aber dann doch noch aus. In solchen Fällen, wo Sie in der angegebenen Zeile keinen Fehler erkennen, sollten Sie auch die Zeilen diff --git a/Documentation/cs/web/introduction.itexi b/Documentation/cs/web/introduction.itexi index 7aedbb9b1a..0415c206a4 100644 --- a/Documentation/cs/web/introduction.itexi +++ b/Documentation/cs/web/introduction.itexi @@ -48,7 +48,7 @@ celém souhrnu zkušeností a zvyklostech klasické notové sazby. @divEnd @divClass{column-right-top} -@subheading Nasazení Lilypondu +@subheading Nasazení LilyPondu @itemize @@ -124,7 +124,7 @@ Více k tomu v našem @ref{Článek,,článku}. Travte méně času tím, že budete dodatečně měnit notovou sazbu: LilyPond upravuje noty správně hned od začátku. -Rozdělení místa vypočítá sám a rovněž spočítá +Rozdělení místa vypočítá sám a rovněž spočítá zalomení řádků a stran, aby vytvořil hustý a pravidelný obraz not. Střety mezi textem písně, notami a akordy jsou vyřešeny a všechny obloučky jsou automaticky @@ -584,7 +584,7 @@ přímé stažení tak i k dostání na papíře. @uref{http://shadylane.fr/, The Shady Lane Publishing}, @qq{Mikrovydavatelství not}, které si dalo za cíl -podporu nové ekonomie hudby, které stojí hudebníkům a +podporu nové ekonomie hudby, které stojí hudebníkům a milovníkům hudby blíže. @end itemize @@ -661,7 +661,7 @@ Prosinec 2005 Schenker Graphs with GNU LilyPond}. Jedná se o do hloubky jdoucí, ale velmi účelný článek s vyrytými ostrými obrázky LilyPondu. Autor Kris Shaffer poznamenává: -»GNU Lilypond vytváří krásnou grafiku, která se ve vztahu k obchodním nabídkám +»GNU LilyPond vytváří krásnou grafiku, která se ve vztahu k obchodním nabídkám jeví jako druhá volba.« @item @@ -750,7 +750,7 @@ překvapit.} @qq{I když jej [LilyPond] ještě tak dobře neznám, udělal na mě již teď neobyčejný dojem. Použil jsem tento program pro zápis not jednoho moteta od Josquina Despreze - v menzurálním notovém zápisu. Je mimo veškerou pochybnost, že LilyPond v + v menzurálním notovém zápisu. Je mimo veškerou pochybnost, že LilyPond v rychlosti, v jednoduchosti používání a notové sazbě snadno předčí jiné notační programy.} @divEnd @@ -795,7 +795,7 @@ překvapit.} @subsubheading Chris Snyder, @uref{https://twitter.com/adoromusic, Adoro Music Publishing} @qq{Způsob, jakým jsou noty v LilyPondu zadávány, mi dovoluje -myslet hudebně -- byly doby, kdy jsem se LilyPondu marně +myslet hudebně -- byly doby, kdy jsem se LilyPondu marně pokoušel vysvětlit, jak se má v notách něco vysázet, jen abych zjistil, že, i kdybych to dokázal udělat přesně tak, jak to chtěl skladatel, noty by přesto byly pro čtení velmi @@ -843,7 +843,7 @@ tím více jej mám rád!} první list s notami, který jsem uviděl, vypadal tak dobře. Popis lže, když jde o krásu LilyPondu -- je v tomto příliš skromný! [...] protože LilyPond se pořád zlepšuje, - a jak se důkladně zabývám tím, jak se věci ve + a jak se důkladně zabývám tím, jak se věci ve Scheme dělají, mám mnohem méně pocitů marnosti. Na každý pád bych chtěl říci: Děkuji vám za to, že LilyPond nabízíte, je skutečně báječný!} @@ -921,7 +921,7 @@ zpětným (obráceným) lomítkem. Předznamenání jsou přidávána pomocí různých koncovek: @code{-is} za notou sází křížek, @code{-es} zato béčko (-- toto jsou české koncovky, -koncovky v jiných jazycích jsou možné také). LilyPond sám rozhodne o tom, kde +koncovky v jiných jazycích jsou možné také). LilyPond sám rozhodne o tom, kde předznamenání umístí. @imageFloat{text-input-2-annotate,png,center} diff --git a/Documentation/de/extending/programming-interface.itely b/Documentation/de/extending/programming-interface.itely index c5d0381bf2..ba9c3c348d 100644 --- a/Documentation/de/extending/programming-interface.itely +++ b/Documentation/de/extending/programming-interface.itely @@ -41,7 +41,7 @@ es eine grundlegende Einleitung in LilyPonds Codeabschnitte in LilyPond sehen etwa so aus: @example - #@{ @var{Lilypond code} #@} + #@{ @var{LilyPond code} #@} @end example Sie können überall eingesetzt werden, wo man Scheme-Code schreiben diff --git a/Documentation/de/texidocs/snap-pizzicato-bartok-pizzicato.texidoc b/Documentation/de/texidocs/snap-pizzicato-bartok-pizzicato.texidoc index c57267d2cd..8ceb822786 100644 --- a/Documentation/de/texidocs/snap-pizzicato-bartok-pizzicato.texidoc +++ b/Documentation/de/texidocs/snap-pizzicato-bartok-pizzicato.texidoc @@ -6,6 +6,6 @@ Spieler die Saite auf das Griffbrett aufschlagen lässt, sodass zusätzlich zum angeschlagenen Ton ein scharfes, knallendes Geräusch ertönt} (Wikipedia). Es wird dargestellt als kleiner Kreis mit einer vertikalen Linie, die vom Kreiszentrum aus nach oben weist und ein Stück außerhalb des -Kreises endet. Lilypond hat keinen eigenen Glyphen für dieses Symbol; es +Kreises endet. LilyPond hat keinen eigenen Glyphen für dieses Symbol; es ist aber einfach, direkt eine Definition in die Eingabedatei einzufügen. " diff --git a/Documentation/de/usage/lilypond-book.itely b/Documentation/de/usage/lilypond-book.itely index 964bfb70dc..5c40607888 100644 --- a/Documentation/de/usage/lilypond-book.itely +++ b/Documentation/de/usage/lilypond-book.itely @@ -1017,7 +1017,7 @@ version, the format @code{texi-html} must be used instead. @item -F @var{Filter} @itemx --filter=@var{Filter} Leitet die Musikfragmente durch das Programm @var{filter} anstatt sie -mit Lilypond zu einer Grafik zu verarbeiten. @option{--filter} und +mit LilyPond zu einer Grafik zu verarbeiten. @option{--filter} und @option{--process} kann nicht gleichzeitig benutzt werden. Beispielaufruf: @example diff --git a/Documentation/de/usage/running.itely b/Documentation/de/usage/running.itely index ff5bdb67be..fb0030b709 100644 --- a/Documentation/de/usage/running.itely +++ b/Documentation/de/usage/running.itely @@ -17,7 +17,7 @@ @chapter @command{lilypond} starten @translationof Running lilypond -Dieses Kapitel behandelt die technischen Details, wie Lilypond ausgeführt werden kann. +Dieses Kapitel behandelt die technischen Details, wie LilyPond ausgeführt werden kann. @menu @@ -89,7 +89,7 @@ Standarderweiterung für LilyPond-Dateien benutzt. Um Daten von @code{stdin} einzulesen, benutzen Sie einfach einen Bindestrich (@code{-}) als @var{Dateiname}. -Wenn Lilypond die Datei @file{Dateiname.ly} verarbeitet, werden daraus +Wenn LilyPond die Datei @file{Dateiname.ly} verarbeitet, werden daraus die Dateien @file{Dateiname.ps} und @file{Dateiname.pdf} erzeugt. Es können an @code{lilypond} auch mehrere @file{.ly} Dateien übergeben werden, die dann einzeln und voneinander unabhängig abgearbeitet @@ -101,7 +101,7 @@ Falls @file{Dateiname.ly} mehr als eine @code{\book}-Umgebung enthält, werden die weiteren Stücke in durchnummerierte Dateien der Form @file{Dateiname-1.pdf} ausgegeben. Zusätzlich wird der Wert der Variable @code{output-suffix} zwischen den ursprünglichen Dateinamen -und der Zahl eingefügt. Eine Lilypond-Datei @file{Dateiname.ly} mit dem Inhalt +und der Zahl eingefügt. Eine LilyPond-Datei @file{Dateiname.ly} mit dem Inhalt @example #(define output-suffix "Geige") @@ -295,7 +295,7 @@ Dateien müssen in das Jail-Verzeichnis kopiert werden (mit denselben Pfaden wie im tatsächlichen Wurzel-Dateisystem). Die gesamte LilyPond-Installation (typischerweise @file{/usr/share/lilypond}) sollte kopiert werden. -Falls Probleme auftreten, ist es am einfachsten, Lilypond mittels +Falls Probleme auftreten, ist es am einfachsten, LilyPond mittels @command{strace} zu starten, wodurch Sie relativ leicht feststellen können, welche Dateien im Jail noch fehlen. @@ -727,7 +727,7 @@ Log-Daten in die Dateien @code{Datei1.log}, @code{Datei2.log} ... schreiben. @item @code{strict-infinity-checking} @tab @code{#f} -@tab Erzwinge einen Programmabsturz wenn @code{Inf} und @code{NaN} +@tab Erzwinge einen Programmabsturz wenn @code{Inf} und @code{NaN} Fließkommaausnahmen gefunden werden. @item @code{strip-output-dir} @@ -772,7 +772,7 @@ wird in die Dateien @code{FILE.stacks} und @code{FILE.graph} ausgegeben. @command{lilypond} erkennt und benützt die folgenden Umgebungsvariablen: @table @code @item LILYPOND_DATADIR -Diese Variable gibt das Verzeichnis an, wo Lilypond seine eigenen Dateien, +Diese Variable gibt das Verzeichnis an, wo LilyPond seine eigenen Dateien, Meldungen und Übersetzungen finden kann. Dieses Verzeichnis sollte Unterverzeichnisse @file{ly/}, @file{ps/}, @file{tex/}, etc. beinhalten. @@ -990,7 +990,7 @@ test.ly:2:19: Fehler: keine gültige Dauer: 5 Diese Stellen sind LilyPonds Vermutung, wo die Warnung oder der Fehler aufgetreten ist, allerdings treten Warnungen und Fehler ja gerade in -unerwarteten Fällen auf. Manchmal kann Lilypond auch eine fehlerhafte +unerwarteten Fällen auf. Manchmal kann LilyPond auch eine fehlerhafte Stelle zwar noch problemlos verarbeiten, ein paar Zeilen später wirkt sich der Fehler aber dann doch noch aus. In solchen Fällen, wo Sie in der angegebenen Zeile keinen Fehler erkennen, sollten Sie auch die Zeilen diff --git a/Documentation/de/web/introduction.itexi b/Documentation/de/web/introduction.itexi index 2aa6439992..fd1c88ed28 100644 --- a/Documentation/de/web/introduction.itexi +++ b/Documentation/de/web/introduction.itexi @@ -56,7 +56,7 @@ der Musik konzentrieren. @divEnd @divClass{column-right-top} -@subheading Lilypond im Einsatz +@subheading LilyPond im Einsatz @itemize @item @@ -395,7 +395,7 @@ Die Farben wurden zur Verdeutlichung hinzugefügt. @subheading Individuelle Ausgabe Ein kurzer Auszug aus Stockhausen's Klavierstück II zeigt die -Fähigkeiten von Lilypond eine individuelle Ausgabe zu erzeugen. +Fähigkeiten von LilyPond eine individuelle Ausgabe zu erzeugen. @exampleImage{Stockhausen_Klavierstueck2} @divEnd @@ -878,7 +878,7 @@ Artikel unter dem Titel Schenker Graphs with GNU LilyPond}. Es handelt sich um einen tiefgehenden, aber sehr praktischen Artikel mit gestochen scharfen LilyPond-Graphiken. Der Autor Kris Shaffer merkt an: -»GNU Lilypond erstellt schöne Graphik, die kommerzielle Alternativen +»GNU LilyPond erstellt schöne Graphik, die kommerzielle Alternativen als zweite Wahl erscheinen lassen.« @item diff --git a/Documentation/es/notation/changing-defaults.itely b/Documentation/es/notation/changing-defaults.itely index 05efdbdbde..62aaf8785f 100644 --- a/Documentation/es/notation/changing-defaults.itely +++ b/Documentation/es/notation/changing-defaults.itely @@ -4975,7 +4975,7 @@ debe devolver @code{#t}. @item @code{@var{@dots{}música@dots{}}} @tab código de entrada normal de LilyPond, que utiliza @code{$} (en los -lugares en que sólo se permiten construcciones de Lilypond) o +lugares en que sólo se permiten construcciones de LilyPond) o @code{#} (para usarlo como un valor de Scheme o un argumento de función musical o música dentro de listas de música) para referenciar argumentos (p.ej. @samp{#arg1}). diff --git a/Documentation/es/notation/fretted-strings.itely b/Documentation/es/notation/fretted-strings.itely index 62f92f0fbc..facc1aaedd 100644 --- a/Documentation/es/notation/fretted-strings.itely +++ b/Documentation/es/notation/fretted-strings.itely @@ -1904,7 +1904,7 @@ music = \relative { Otra téctnica de ejecución (utilizada especialmente en la guitarra eléctrica) se llama @notation{tapado de palma}. La cuerda es parcialmente tapada por la palma de la mano que pulsa (de ahí el -nombre). Lilypond contempla la notación de las notas de estilo de +nombre). LilyPond contempla la notación de las notas de estilo de tapado de palma mediante el cambio de la forma de la cabeza de nota a un triángulo. diff --git a/Documentation/es/notation/input.itely b/Documentation/es/notation/input.itely index 665876d4cb..88e9d7600f 100644 --- a/Documentation/es/notation/input.itely +++ b/Documentation/es/notation/input.itely @@ -247,7 +247,7 @@ archivo como un solo bloque @code{\book}, véase @ref{Estructura del archivo}. Al producir varios archivos a partir de un solo archivo fuente, -Lilypond se asegura de que ninguno de los archivos de salida de +LilyPond se asegura de que ninguno de los archivos de salida de ningún bloque @code{\book} sobreescribe el archivo de salida producido por un @code{\book} anterior del mismo archivo de entrada. @@ -293,11 +293,11 @@ en el archivo fuente @file{eightminiatures.ly}, produce @funindex \bookOutputSuffix @funindex \bookOutputName -Lilypond le ofrece unos mecanismos que le permiten controlar los +LilyPond le ofrece unos mecanismos que le permiten controlar los nombres de archivo que se utilizan por parte de los diversos motores finales al producir los archivos de salida. -En la sección anterior vimos cómo Lilypond evita las +En la sección anterior vimos cómo LilyPond evita las coincidencias de nombres al producir varias salidas a partir de un único archivo fuente de entrada. También podemos especificar nuestros propios sufijos para cada bloque @code{\book}, de manera @@ -3905,7 +3905,7 @@ lilypond archivo.ly >resultado.txt @end example @funindex \void -Observe que Lilypond no se limita a mostrar la expresión musical, +Observe que LilyPond no se limita a mostrar la expresión musical, sino que también la interpreta (porque @code{\displayLilyMusic} la devuelve además de mostrarla). Simplemente inserte @code{\displayLilyMusic} dentro de diff --git a/Documentation/es/usage/suggestions.itely b/Documentation/es/usage/suggestions.itely index 89cc34cb28..3024ff3453 100644 --- a/Documentation/es/usage/suggestions.itely +++ b/Documentation/es/usage/suggestions.itely @@ -338,7 +338,7 @@ define las relaciones de dependencia entre los archivos y qué instrucciones necesitamos dar al sistema operativo para producir un archivo a partir de otro. Por ejemplo, el archivo de make detallaría cómo obtener @file{balada.pdf} y @file{balada.midi} a -partir de @file{balada.ly} mediante la ejecución de Lilypond. +partir de @file{balada.ly} mediante la ejecución de LilyPond. Existen ocasiones en las que es buena idea crear un @code{Makefile} para nuestro proyecto, bien sea por nuestra propia diff --git a/Documentation/es/web/news-front.itexi b/Documentation/es/web/news-front.itexi index ae822ccffb..6db036faff 100644 --- a/Documentation/es/web/news-front.itexi +++ b/Documentation/es/web/news-front.itexi @@ -70,7 +70,7 @@ codificados directamente dentro de la partitura de LilyPond. @newsItem -@subheading Lanzado Lilypond 2.18.0 @emph{29 de diciembre de 2013} +@subheading Lanzado LilyPond 2.18.0 @emph{29 de diciembre de 2013} Nos llena de orgullo anunciar el lanzamiento de GNU LilyPond 2.18.0. LilyPond es un programa de tipografía musical para editar @@ -212,7 +212,7 @@ actualicen a esta versión. @newsEnd @newsItem -@subheading ¡Lanzado Lilypond 2.16.0! @emph{24 de agosto de 2012} +@subheading ¡Lanzado LilyPond 2.16.0! @emph{24 de agosto de 2012} Nos llena de orgullo anunciar el lanzamiento de GNU LilyPond 2.16.0. LilyPond es un programa de tipografía musical para editar partituras, diff --git a/Documentation/es/web/news.itexi b/Documentation/es/web/news.itexi index 60497e625b..61d5b8d891 100644 --- a/Documentation/es/web/news.itexi +++ b/Documentation/es/web/news.itexi @@ -1055,7 +1055,7 @@ lugar. @newsEnd @newsItem -@subheading ¡Lanzado Lilypond 2.16.0! @emph{24 de agosto de 2012} +@subheading ¡Lanzado LilyPond 2.16.0! @emph{24 de agosto de 2012} Nos llena de orgullo anunciar el lanzamiento de GNU LilyPond 2.16.0. LilyPond es un programa de tipografía musical para editar partituras, @@ -4387,7 +4387,7 @@ in-depth but hands-on feature article with crisp LilyPond graphics. @* Author Kris Shaffer remarks -“GNU Lilypond generates beautiful graphics that make commercial +“GNU LilyPond generates beautiful graphics that make commercial alternatives seem second-rate.” This article is now available @uref{http://www.linuxjournal.com/article/8583,on-line}. @newsEnd @@ -4995,10 +4995,10 @@ file and download @ref{Descargas antiguas}! @newsItem @subheading February 26, 2005 -The @uref{http://lsr.di.unimi.it/,Lilypond Snippet -Repository (LSR)} is a searchable database of Lilypond code +The @uref{http://lsr.di.unimi.it/,LilyPond Snippet +Repository (LSR)} is a searchable database of LilyPond code snippets. You can add snippets too, so join the LSR project, and -contribute creative ideas for using Lilypond. +contribute creative ideas for using LilyPond. @newsEnd @@ -5219,7 +5219,7 @@ the @uref{http://git.savannah.gnu.org/cgit/lilypond.git/plain/ChangeLog?id=abfdd @newsItem @subheading October 29, 2004 -2.3.25 is the final release candidate for Lilypond 2.4. +2.3.25 is the final release candidate for LilyPond 2.4. Werner has been overhauling the TeX macros and lilypond-book. In addition, this release contains an important fix for raggedbottom page-layout. diff --git a/Documentation/fr/essay/literature.itely b/Documentation/fr/essay/literature.itely index 226120d936..fb343aa850 100644 --- a/Documentation/fr/essay/literature.itely +++ b/Documentation/fr/essay/literature.itely @@ -18,7 +18,7 @@ @chapter Références bibliographiques @translationof Literature list -Voici des listes de références utilisées dans Lilypond. +Voici des listes de références utilisées dans LilyPond. @menu * Bibliographie succincte:: diff --git a/Documentation/fr/extending/programming-interface.itely b/Documentation/fr/extending/programming-interface.itely index 938212ab92..a08b493280 100644 --- a/Documentation/fr/extending/programming-interface.itely +++ b/Documentation/fr/extending/programming-interface.itely @@ -360,7 +360,7 @@ fonction = @noindent de manière similaire aux @ref{Définition de fonctions Scheme, fonctions Scheme}. La plupart du temps, le @var{corps} sera constitué d'un -@ref{Blocs de code LilyPond, bloc de code Lilypond}. +@ref{Blocs de code LilyPond, bloc de code LilyPond}. Les différents types des prédicat sont recensés à l'annexe @ruser{Types de prédicats prédéfinis}. diff --git a/Documentation/fr/learning/templates.itely b/Documentation/fr/learning/templates.itely index 34fa67f93b..3b076756c9 100644 --- a/Documentation/fr/learning/templates.itely +++ b/Documentation/fr/learning/templates.itely @@ -17,7 +17,7 @@ @translationof Templates Cette annexe du manuel d'initiation propose des patrons de partition -Lilypond, prets à l'emploi. Il vous suffira d'y ajouter quelques notes, +LilyPond, prets à l'emploi. Il vous suffira d'y ajouter quelques notes, de lancer LilyPond, et d'aprécier le résultat. @menu diff --git a/Documentation/fr/learning/tutorial.itely b/Documentation/fr/learning/tutorial.itely index 25bcb5ccc3..12b468b30b 100644 --- a/Documentation/fr/learning/tutorial.itely +++ b/Documentation/fr/learning/tutorial.itely @@ -592,7 +592,7 @@ opérations de mise à jour automatisée au fil de l'évolution de la syntaxe de LilyPond. Ensuite, cela met en évidence le minimum requis pour pouvoir compiler votre fichier. -Si vous ne le mentionnez pas, Lilypond vous rappellera à l'ordre durant +Si vous ne le mentionnez pas, LilyPond vous rappellera à l'ordre durant la compilation. @item diff --git a/Documentation/fr/learning/tweaks.itely b/Documentation/fr/learning/tweaks.itely index cbe04d3f1e..1a22df2087 100644 --- a/Documentation/fr/learning/tweaks.itely +++ b/Documentation/fr/learning/tweaks.itely @@ -270,7 +270,7 @@ mise en forme et l'utilisation de ces commandes, nous nous limiterons à n'employer que quelques propriétés et valeurs simples, facilement compréhensibles. -Lilypond reconnaît comme expression primaire les éléments musicaux tels +LilyPond reconnaît comme expression primaire les éléments musicaux tels que les notes, durées et annotations (les @emph{markups}). D'autres expressions de base comme les nombres, chaînes de caractères et listes sont gérées en « mode Scheme », mode appelé en faisant précéder une diff --git a/Documentation/fr/notation/fretted-strings.itely b/Documentation/fr/notation/fretted-strings.itely index 098877d098..06c19286e0 100644 --- a/Documentation/fr/notation/fretted-strings.itely +++ b/Documentation/fr/notation/fretted-strings.itely @@ -579,7 +579,7 @@ donnée est calculée automatiquement. Pour ce faire, l'accordage doit LilyPond possède des accordages prédéfinis pour le banjo, la mandoline, la guitare et la guitare basse ainsi que le ukulele et les cordes -d'orchestre. Lilypond calcule automatiquement la transposition +d'orchestre. LilyPond calcule automatiquement la transposition correspondant à ces accordages. L'exemple ci-dessous est pour guitare basse, il sonnera donc une octave en dessous de ce qui est écrit. @@ -688,7 +688,7 @@ de type @emph{pitch}. Les objets @emph{pitch} sont créés par la fonction La fonction @code{\stringTuning} permet de créer de tels objets à partir de la saisie d'un accord. -Lilypond calcule automatiquement le nombre de cordes à représenter dans +LilyPond calcule automatiquement le nombre de cordes à représenter dans la tablature (@code{TabStaff}) ainsi que dans le @code{FretBoard} en comptant le nombre d'éléments définis dans le @code{stringTunings}. diff --git a/Documentation/fr/notation/rhythms.itely b/Documentation/fr/notation/rhythms.itely index 5a41c47c0a..2a11c5c78a 100644 --- a/Documentation/fr/notation/rhythms.itely +++ b/Documentation/fr/notation/rhythms.itely @@ -2824,7 +2824,7 @@ vous invitons dans ce cadre particulier à plutôt utiliser @code{\divisioMinima}, comme indiqué au paragraphe @ref{Divisions} du chapitre consacré au grégorien. -Lilypond prend en charge la notation kiévienne, qui dispose d'une +LilyPond prend en charge la notation kiévienne, qui dispose d'une barre de mesure spécifique : @lilypond[quote,fragment,verbatim] diff --git a/Documentation/fr/notation/vocal.itely b/Documentation/fr/notation/vocal.itely index cd40e7872f..d86e216d1d 100644 --- a/Documentation/fr/notation/vocal.itely +++ b/Documentation/fr/notation/vocal.itely @@ -421,7 +421,7 @@ voir @ref{Positionnement vertical des paroles}. @funindex \addlyrics La commande @code{\addlyrics} n'est en fait qu'une manière plus aisée -d'écrire de la musique vocale dans une structure Lilypond plus complexe. +d'écrire de la musique vocale dans une structure LilyPond plus complexe. @example @{ MUSIQUE @} diff --git a/Documentation/fr/web/introduction.itexi b/Documentation/fr/web/introduction.itexi index 8ebffbf836..1c4c5915a1 100644 --- a/Documentation/fr/web/introduction.itexi +++ b/Documentation/fr/web/introduction.itexi @@ -1040,10 +1040,10 @@ retouches, que les musiciens ont utilisé.} @qq{Merci et encore merci à l'équipe des développeurs pour leur admirable travail. Je n'ai jamais rien vu qui approche le résultat que -j'obtiens avec Lilypond — je suis absolument convaincu que mes besoins +j'obtiens avec LilyPond — je suis absolument convaincu que mes besoins en terme d'édition musicale seront largement satisfaits par cette superbe application. [@dots{}] une partition de base générée par -Lilypond [@dots{}] a meilleure mine que la plupart des publications +LilyPond [@dots{}] a meilleure mine que la plupart des publications ❝professionnelles❞ auxquelles je l'ai comparée, aussi bien de chez Warner Bros., que même les plus récentes productions des ❝bonnes vieilles maisons❞ [@dots{}]} @@ -1055,7 +1055,7 @@ vieilles maisons❞ [@dots{}]} @divClass{testimonial-item} @subsubheading Chris Cannam, programmeur en chef du projet @uref{http://www.rosegardenmusic.com/, RoseGarden} -@qq{Lilypond est clairement le ténor brillantissime [de la gravure +@qq{LilyPond est clairement le ténor brillantissime [de la gravure musicale de qualité].} @divEnd diff --git a/Documentation/hu/web/community.itexi b/Documentation/hu/web/community.itexi index 73efbec681..5b897bfd44 100644 --- a/Documentation/hu/web/community.itexi +++ b/Documentation/hu/web/community.itexi @@ -848,7 +848,7 @@ PDF 1095k}) @item Erik Sandberg: @emph{A bemeneti nyelv és a formázó szétválasztása a -GNU Lilypondban}. Diplomaterv, Uppsalai Egyetem, Információtechnológiai +GNU LilyPondban}. Diplomaterv, Uppsalai Egyetem, Információtechnológiai Tanszék, 2006. március (@uref{http://lilypond.org/website/pdf/thesis-erik-sandberg.pdf, PDF 750k}) @@ -898,7 +898,7 @@ A Linux Journal közzétesz egy cikket @uref{http://www.linuxjournal.com/article/8364, Schenker-diagramok készítése GNU LilyPonddal} címen. Ez egy gyakorlatias cikk igen szép LilyPond grafikákkal. -A szerző, Kris Shaffer megjegyzi: @qq{A GNU Lilypond gyönyörű kottaképe után a +A szerző, Kris Shaffer megjegyzi: @qq{A GNU LilyPond gyönyörű kottaképe után a kereskedelmi alternatívák másodosztályúnak tűnnek.} A cikk elérhető @uref{http://www.linuxjournal.com/article/8583, online}. diff --git a/Documentation/hu/web/introduction.itexi b/Documentation/hu/web/introduction.itexi index b75a4c9f11..c25ceaf6fa 100644 --- a/Documentation/hu/web/introduction.itexi +++ b/Documentation/hu/web/introduction.itexi @@ -180,7 +180,7 @@ feladatra alkalmas. Gyönyörködj az alábbi példákban, és meríts ihletet b @ignore Here is a passage from Franz Liszt's solo piano transcription of the Overture to Wagner's @emph{Tannhäuser}. The spacing -in this example was all performed by Lilypond's formatting +in this example was all performed by LilyPond's formatting algorithms, without tweaks of any kind. It handles cross-staff beaming gracefully and puts the system brace perfectly around all three staves. @@ -820,7 +820,7 @@ mutatja a kottát és a LilyPond forrást. @ignore Import: LilyPond, MIDI -Export: Lilypond, MIDI, ABC, CSound Score File, PDF +Export: LilyPond, MIDI, ABC, CSound Score File, PDF @end ignore @divEnd diff --git a/Documentation/included/compile.itexi b/Documentation/included/compile.itexi index 76bd48cd2f..b198e40c6e 100644 --- a/Documentation/included/compile.itexi +++ b/Documentation/included/compile.itexi @@ -1461,10 +1461,10 @@ installation directory structure. It can be useful to have both the stable and the development versions -of Lilypond available at once. One way to do this on GNU/Linux is to +of LilyPond available at once. One way to do this on GNU/Linux is to install the stable version using the precompiled binary, and run the development version from the source tree. After running @command{make -all} from the top directory of the Lilypond source files, there will +all} from the top directory of the LilyPond source files, there will be a binary called @code{lilypond} in the @code{out} directory: @example diff --git a/Documentation/it/learning/fundamental.itely b/Documentation/it/learning/fundamental.itely index dd89ae5049..fafe6ac59c 100644 --- a/Documentation/it/learning/fundamental.itely +++ b/Documentation/it/learning/fundamental.itely @@ -1623,7 +1623,7 @@ partire dal nome, o viceversa. @smallspace -Vedremo in seguito come cambiare l'output di Lilypond +Vedremo in seguito come cambiare l'output di LilyPond modificando il comportamento degli incisori. diff --git a/Documentation/it/notation/changing-defaults.itely b/Documentation/it/notation/changing-defaults.itely index d6cb5b7742..1cd155d37a 100644 --- a/Documentation/it/notation/changing-defaults.itely +++ b/Documentation/it/notation/changing-defaults.itely @@ -4515,7 +4515,7 @@ deve ritornare @code{#t}. @item @code{@var{@dots{}musica@dots{}}} @tab il normale input LilyPond, usando @code{$} (nei punti in cui sono -consentiti solo i costrutti Lilypond) o @code{#} (per usarlo come un valore +consentiti solo i costrutti LilyPond) o @code{#} (per usarlo come un valore Scheme o come argomento di una funzione musicale o come musica all'interno di liste di musica) per riferirsi agli argomenti (es: @samp{#arg1}). @end multitable diff --git a/Documentation/it/notation/input.itely b/Documentation/it/notation/input.itely index fab37f78b2..e4664f0ac4 100644 --- a/Documentation/it/notation/input.itely +++ b/Documentation/it/notation/input.itely @@ -237,7 +237,7 @@ Se non è specificato alcun blocco @code{\book} nel file di input, LilyPond tratterà implicitamente l'intero file come un singolo blocco @code{\book}, come è spiegato in @ref{File structure}. -Nel generare molteplici file da un singolo file sorgente, Lilypond +Nel generare molteplici file da un singolo file sorgente, LilyPond controlla che nessuno dei file di output di alcun blocco @code{\book} sovrascriva il file di output prodotto da un blocco @code{\book} precedente dello stesso file di input. @@ -283,10 +283,10 @@ genererà @funindex \bookOutputSuffix @funindex \bookOutputName -Lilypond permette di decidere quali nomi di file debbano essere +LilyPond permette di decidere quali nomi di file debbano essere usati dai vari backend quando questi generano i file di output. -Nella sezione precedente abbiamo visto come Lilypond prevenga i +Nella sezione precedente abbiamo visto come LilyPond prevenga i conflitti di nome quando genera molti file di output da un singolo file sorgente. È possibile anche specificare un proprio suffisso per ogni blocco @code{\book}. Quindi si possono, per esempio, @@ -3697,7 +3697,7 @@ lilypond file.ly >display.txt @funindex \void @c tradotto un po' liberamente, dato che il paragrafo in inglese è poco chiaro: @c https://lists.gnu.org/archive/html/lilypond-user/2015-12/msg00141.html -Nota bene che Lilypond non soltanto mostra in console l'espressione musicale, ma +Nota bene che LilyPond non soltanto mostra in console l'espressione musicale, ma la interpreta anche (infatti l'espressione musicale di @code{\displayLilyMusic} appare nell'output oltre a essere mostrata in console). Basta inserire @code{\displayLilyMusic} in file esistenti, senza doverne modificare le diff --git a/Documentation/it/notation/pitches.itely b/Documentation/it/notation/pitches.itely index 53ef1ad1f4..7c2d839a45 100644 --- a/Documentation/it/notation/pitches.itely +++ b/Documentation/it/notation/pitches.itely @@ -477,7 +477,7 @@ non si riferisce ad alcuno standard. @cindex lingua, nomi delle note in un'altra @cindex lingua, nomi delle altezze in un'altra -Lilypond comprende insiemi predefiniti di nomi di note e alterazioni in +LilyPond comprende insiemi predefiniti di nomi di note e alterazioni in altre lingue. La scelta della lingua si fa solitamente all'inizio del file; l'esempio seguente è scritto in notazione italiana: diff --git a/Documentation/it/notation/rhythms.itely b/Documentation/it/notation/rhythms.itely index 0a66c9b26e..3cff8040ae 100644 --- a/Documentation/it/notation/rhythms.itely +++ b/Documentation/it/notation/rhythms.itely @@ -2780,7 +2780,7 @@ Tuttavia,dato che questi segni di spunta sono tipicamente usati nella notazione gregoriana, è preferibile usare @code{\divisioMinima}, come è descritto nella sezione @ref{Divisiones} della parte dedicata al canto gregoriano. -Lilypond supporta la notazione gregoriana russa e fornisce una stanghetta speciale per +LilyPond supporta la notazione gregoriana russa e fornisce una stanghetta speciale per questo tipo di notazione: @lilypond[quote,fragment,verbatim] f'1 \bar "k" diff --git a/Documentation/it/usage/external.itely b/Documentation/it/usage/external.itely index ac306ccb6c..1535ff8933 100644 --- a/Documentation/it/usage/external.itely +++ b/Documentation/it/usage/external.itely @@ -741,7 +741,7 @@ dal metodo automatizzato di @command{lilypond-book}. @cindex LuaTex @cindex lyluatex -Per integrare l'output di Lilypond in un documento, oltre a +Per integrare l'output di LilyPond in un documento, oltre a @code{lilypond-book}, esiste un programma alternativo che può essere usato con LuaTex: @uref{https://github.com/jperon/lyluatex/blob/master/README.en.md,lyluatex}. @@ -829,7 +829,7 @@ usare anche la funzione di ritaglio dei sistemi; si veda Alcuni utenti hanno creato file che possono essere inclusi in LilyPond tramite @code{\include} per produrre certi effetti. Quelli elencati -in questo capitolo fanno parte di Lilypond. Maggiori informazioni +in questo capitolo fanno parte di LilyPond. Maggiori informazioni in @ruser{Lavorare coi file di input}. @menu @@ -845,7 +845,7 @@ in @ruser{Lavorare coi file di input}. @cindex Articulate, progetto Il progetto @uref{http://www.nicta.com.au/articulate,Articulate} è un -tentativo di migliorare l'output MIDI di Lilypond. Aggiusta la durata +tentativo di migliorare l'output MIDI di LilyPond. Aggiusta la durata delle note (che non si trovano in una legatura di portamento) in base ai segni di articolazione attaccati ad esse. Per esempio, @q{staccato} dimezza il valore della nota, @q{tenuto} assegna alla nota la sua diff --git a/Documentation/it/usage/lilypond-book.itely b/Documentation/it/usage/lilypond-book.itely index ce0aea77ee..848be1e563 100644 --- a/Documentation/it/usage/lilypond-book.itely +++ b/Documentation/it/usage/lilypond-book.itely @@ -1228,7 +1228,7 @@ esempio, </p> <p> -Ancora un po' di Lilypond, questa volta con delle opzioni: +Ancora un po' di LilyPond, questa volta con delle opzioni: <lilypond fragment quote staffsize=26 verbatim> a4 b c d diff --git a/Documentation/it/web/introduction.itexi b/Documentation/it/web/introduction.itexi index e04da75106..f61466cbf1 100644 --- a/Documentation/it/web/introduction.itexi +++ b/Documentation/it/web/introduction.itexi @@ -270,7 +270,7 @@ che usano LilyPond. LilyPond gira su tutte le piattaforme più note: GNU/Linux, MacOS X, e Windows. LilyPond include un'ampia documentazione e centinaia di file di esempio. C'è un'attiva comunità di utenti che risponde alle -domande nella mailing list internazionale dedicata agli utenti Lilypond, +domande nella mailing list internazionale dedicata agli utenti LilyPond, offrendo gentilmente il proprio aiuto. I tempi di risposta sono solitamente molto brevi e spesso vengono suggerite brillanti soluzioni dei problemi segnalati. Grazie alla stretta interazione col team di sviluppo, tali @@ -308,7 +308,7 @@ già deciso di provare LilyPond, per prima cosa informati sul nostro @subheading Begli esempi -Lilypond è uno strumento potente e flessibile per scrivere ogni tipo +LilyPond è uno strumento potente e flessibile per scrivere ogni tipo di musica. Dai un'occhiata alla galleria di esempi e lasciati ispirare! @divEnd @@ -318,7 +318,7 @@ di musica. Dai un'occhiata alla galleria di esempi e lasciati ispirare! @subheading Musica Classica Questo brano per organo di J.S. Bach rappresenta un tipico esempio di -progetto Lilypond. +progetto LilyPond. @exampleImage{bach-bwv610} @divEnd @@ -337,7 +337,7 @@ mediante tratti spezzati. @divClass{column-center-middle-color2} @subheading Musica Antica -Lilypond supporta anche vari tipi di notazione antica, come +LilyPond supporta anche vari tipi di notazione antica, come questo passaggio di canto gregoriano. @exampleImage{ancient-headword} @@ -346,7 +346,7 @@ questo passaggio di canto gregoriano. @divClass{column-center-middle-color2} @subheading Musica Moderna -I compositori contemporanei ritengono che Lilypond sia molto adatto a +I compositori contemporanei ritengono che LilyPond sia molto adatto a visualizzare notazioni non convenzionali. Ecco un estratto dal @emph{Čáry} di Trevor Bača, per flauto basso non accompagnato. @@ -374,7 +374,7 @@ completa, riduzione per canto e pianoforte, e parte per violino. @divClass{column-center-middle-color2} @subheading Intavolatura -Lilypond supporta la notazione per intavolatura, che può essere personalizzata +LilyPond supporta la notazione per intavolatura, che può essere personalizzata per adattarsi a ogni strumento che ne fa uso. Il rigo dell'intavolatura viene generato automaticamente dalle note inserite per il pentagramma. @@ -397,7 +397,7 @@ I colori sono stati aggiunti per migliorare la visibilità. @subheading Output personalizzato Un breve estratto del Klavierstück II di Stockhausen per dimostrare la -capacità di Lilypond di fornire output personalizzato. +capacità di LilyPond di fornire output personalizzato. @exampleImage{Stockhausen_Klavierstueck2} @divEnd @@ -406,11 +406,11 @@ capacità di Lilypond di fornire output personalizzato. @divClass{column-center-middle-color2} @subheading Musica Vocale -Lilypond è eccellente per la musica vocale di tutti i generi, dagli inni +LilyPond è eccellente per la musica vocale di tutti i generi, dagli inni sacri all'opera. Ecco un mottetto medievale con requisiti leggermente insoliti. Il tenor è scritto in un metro diverso dagli altri, ma deve essere allineato come se fosse nello stesso tempo. -Lilypond gestisce questo aspetto in modo molto elegante. Si notino anche gli +LilyPond gestisce questo aspetto in modo molto elegante. Si notino anche gli incipit con chiave in stile Vaticana, i gambi barrati a indicare note plicate, e le parentesi quadre sulle sezioni legate. @@ -420,7 +420,7 @@ e le parentesi quadre sulle sezioni legate. @divClass{column-center-middle-color2} @subheading Applicazioni didattiche -Lilypond è molto indicato anche per applicazioni didattiche. +LilyPond è molto indicato anche per applicazioni didattiche. Ecco un esempio di un semplice esercizio di contrappunto. @exampleImage{theory} @@ -440,7 +440,7 @@ personalizzati per adattarsi a quasi ogni situazione. @divClass{column-center-middle-color2} @subheading Grandi Progetti -Lilypond è ottimo anche per progetti ad ampio respiro come opere o lavori per +LilyPond è ottimo anche per progetti ad ampio respiro come opere o lavori per un'orchestra sinfonica al completo. Inoltre l'input testuale permette una maggiore accessibilità -- questo esempio è stato realizzato da Hu Haipeng, un compositore cieco. @@ -612,7 +612,7 @@ che per le partiture pubblicate. @divClass{column-left-top} @subheading Concerti -Lilypond è stato usato per esecuzioni in tutto il mondo. +LilyPond è stato usato per esecuzioni in tutto il mondo. In evidenza: @divClass{keep-bullets} @@ -852,7 +852,7 @@ Dicembre 2005 intitolato @uref{http://www.linuxjournal.com/article/8364, Crea dei fantastici grafici Schenker con GNU LilyPond}. È un articolo approfondito e pratico con attraenti grafici di LilyPond. L'autore -Kris Shaffer commenta @qq{GNU Lilypond genera una grafica splendida +Kris Shaffer commenta @qq{GNU LilyPond genera una grafica splendida che fa sembrare le alternative commerciali di second'ordine.} @item @@ -951,7 +951,7 @@ quanto riguarda la velocità, la facilità d'uso e la resa grafica!} @qq{[@dots{}dopo la prima prova d'orchestra] ho ricevuto molti complimenti per la qualità degli spartiti. Ancora più -importante: sebbene Lilypond fornisca molti trucchi per migliorare +importante: sebbene LilyPond fornisca molti trucchi per migliorare l'aspetto degli spartiti, quello che l'orchestra ha ricevuto da me è l'output grezzo e privo di ritocchi.} @divEnd @@ -962,9 +962,9 @@ l'output grezzo e privo di ritocchi.} @qq{grazie e complimenti al team di sviluppo per il suo incredibile lavoro. Non ho mai visto niente che possa avvicinarsi all'output di -Lilypond -- sono assolutamente sicuro che le mie necessità nel campo +LilyPond -- sono assolutamente sicuro che le mie necessità nel campo dell'editoria musicale saranno soddisfatte oltre ogni aspettativa usando -questo fantastico programma. [@dots{}] l'output predefinito di Lilypond [@dots{}] ha +questo fantastico programma. [@dots{}] l'output predefinito di LilyPond [@dots{}] ha un aspetto migliore delle recenti pubblicazioni @q{professionali} con cui l'ho confrontato (ovvero quasi qualsiasi spartito della Warner Bros, e anche molti dei più recenti delle @q{vecchie case editrici}). [@dots{}]} @@ -976,7 +976,7 @@ dei più recenti delle @q{vecchie case editrici}). [@dots{}]} @divClass{testimonial-item} @subsubheading Chris Cannam, principale programmatore di @uref{http://www.rosegardenmusic.com/, RoseGarden} -@qq{Lilypond è ovviamente il super gorilla [della +@qq{LilyPond è ovviamente il super gorilla [della grande tipografia musicale].} @divEnd @@ -1006,7 +1006,7 @@ farlo. Sono sicuro che nessun prodotto commerciale può avvicinarsi a questo.} @divClass{testimonial-item} @subsubheading David Bobroff, trombone basso, Iceland Symphony Orchestra -@qq{Credo che Lilypond sia un grande programma [@dots{}] Più imparo LilyPond +@qq{Credo che LilyPond sia un grande programma [@dots{}] Più imparo LilyPond e più mi piace!} @divEnd @@ -1321,7 +1321,7 @@ Emacs è un editor di testo che ha la capacità di comprendere molti diversi linguaggi informatici. Emacs è un editor molto estendibile e può essere usato come ambiente di sviluppo integrato (IDE). C'è una @q{modalità lilypond} che fornisce le definizioni del -linguaggio per poter lavorare con i file sorgente di Lilypond. +linguaggio per poter lavorare con i file sorgente di LilyPond. Uno sviluppatore ha scritto @uref{https://github.com/nsceaux/lyqi,lyqi}, una modalità primaria di Emacs. diff --git a/Documentation/ja/notation/input.itely b/Documentation/ja/notation/input.itely index b020dd547c..42f6efcab1 100644 --- a/Documentation/ja/notation/input.itely +++ b/Documentation/ja/notation/input.itely @@ -2188,7 +2188,7 @@ LilyPond は UTF-8 エンコーディング LilyPond は多言語テキストを、Pango ライブラリを用いて、@c レイアウトして描画します。 -Lilypond は入力のエンコーディング変換をまったく行いません。@c +LilyPond は入力のエンコーディング変換をまったく行いません。@c これは非 ASCII 文字を含むすべてのテキスト -- タイトル、歌詞テキストあるいは演奏指示 -- を UTF-8 でエンコードして入力する必要があるということを意味します。@c diff --git a/Documentation/ja/notation/rhythms.itely b/Documentation/ja/notation/rhythms.itely index 95b1ce959b..4193aa328b 100644 --- a/Documentation/ja/notation/rhythms.itely +++ b/Documentation/ja/notation/rhythms.itely @@ -3212,7 +3212,7 @@ c1 | c | c | c @emph{acciaccatura} のようにスラッシュ付きの符幹を持つが@c スラーは付かない装飾小音符を譜刻することもできます。 -Lilypond はさらに 2 つ特殊なタイプの装飾小音符をサポートします: +LilyPond はさらに 2 つ特殊なタイプの装飾小音符をサポートします: @emph{acciaccatura} (長さを持たない装飾小音符で、@c スラッシュ付きの符幹を持つスラーでつなげられる小さな音符) と @emph{appoggiatura} (一定の比率で主音符から演奏時間をとり、@c diff --git a/Documentation/ja/notation/spacing.itely b/Documentation/ja/notation/spacing.itely index a7bcbafe56..dad396f717 100644 --- a/Documentation/ja/notation/spacing.itely +++ b/Documentation/ja/notation/spacing.itely @@ -3128,7 +3128,7 @@ Essay on automated music engraving: @subsection プロポーショナル ノーテーション @translationof Proportional notation -Lilypond はプロポーショナル ノーテーションをサポートします。@c +LilyPond はプロポーショナル ノーテーションをサポートします。@c この記譜法では、各音符は演奏時間に相当する水平方向のスペースをとります。@c このタイプの水平スペースは、方眼紙上の水平方向スペースと同等です。@c 20 世紀後半、21 世紀前半の楽譜の中には、@c diff --git a/Documentation/ja/usage/running.itely b/Documentation/ja/usage/running.itely index 980d2a5cf0..c0bfd3f1ef 100644 --- a/Documentation/ja/usage/running.itely +++ b/Documentation/ja/usage/running.itely @@ -184,7 +184,7 @@ forfiles /s /p "C:\Documents\My Scores" /M *.ly /c "cmd /c lilypond @@file" @node LilyPond の基本的なコマンド ライン オプション -@unnumberedsubsec Lilypond の基本的なコマンド ライン オプション +@unnumberedsubsec LilyPond の基本的なコマンド ライン オプション @translationof Basic command line options for LilyPond @cindex Invoking @command{lilypond} (@command{lilypond} を呼び出す) diff --git a/Documentation/ja/web/introduction.itexi b/Documentation/ja/web/introduction.itexi index 7fa0d615ae..ba880085f0 100644 --- a/Documentation/ja/web/introduction.itexi +++ b/Documentation/ja/web/introduction.itexi @@ -298,7 +298,7 @@ LilyPond を使ったオンラインツールがいくつかあります。 LilyPond は一般的なプラットフォーム全て (GNU/Linux, MacOS, そして Windows) で動きます。@c LilyPond には広範囲のドキュメントと数百の実例ファイルが付属します。@c -Lilypond ユーザー メーリング リストで質問に答えてくれる@c +LilyPond ユーザー メーリング リストで質問に答えてくれる@c 活発なユーザ コミュニティがあります。@c 開発チームは問題が早期に解決されるよう活動しています。@c 通常はすぐに回答がありますし、しばしば報告された問題に対する@c @@ -452,7 +452,7 @@ LilyPond は聖歌からオペラまですべての種類の声楽に対して 少し変わった要求をする中世のモテットを示します。@c テナー ボイスの拍子は他と異なりますが、@c 同じ拍子であるかのように揃っています。@c -Lilypond はこれをすっきりと処理します +LilyPond はこれをすっきりと処理します ヴァチカン様式の音部記号、ゆらぎのある音符を表すスラッシュ付きの@c 符幹、ある特定の音符グループ上の連結線ににも注目してください。 @@ -1022,7 +1022,7 @@ LilyPond が、スピード、使い易さ、見栄えにおいて、 @qq{[..最初のオーケストラリハーサルの後で] 私は楽譜の出来について@c たくさんの賛辞をいただきました。@c 重要なのは、@c -Lilypondには楽譜の見栄えをより良くするための数多くの方法があるのですが、@c +LilyPondには楽譜の見栄えをより良くするための数多くの方法があるのですが、@c 私がオーケストラに渡したのは@c 基本的に生の、そのままの出力結果だったということです。} @divEnd @@ -1032,10 +1032,10 @@ Lilypondには楽譜の見栄えをより良くするための数多くの方法 @subsubheading Kieren MacMillan, 作曲家 (カナダ トロント) @qq{この素晴らしい仕事をした開発チームに感謝と賛辞の意を。@c -Lilypondで得られる結果に近い物は他ではありません +LilyPondで得られる結果に近い物は他ではありません -- この偉大なアプリケーションは、私の楽譜出版の必要性に対して、@c 期待以上の結果を間違いなくもたらしてくれます。@c -[..] 基本的に、いじっていない Lilypond の出力は [..] +[..] 基本的に、いじっていない LilyPond の出力は [..] 私が比較した最近の @q{プロ} の出版物 (Warner Bros. の楽譜、それから @q{老舗} の最近の楽譜の大多数) よりも良いです。[..]} diff --git a/Documentation/nl/web/introduction.itexi b/Documentation/nl/web/introduction.itexi index d45ea1361b..9ba487b72f 100644 --- a/Documentation/nl/web/introduction.itexi +++ b/Documentation/nl/web/introduction.itexi @@ -15,7 +15,7 @@ @node Inleiding @unnumbered Inleiding @translationof Introduction - + @divClass{column-center-top} @subheading Ons Doel @imageFloat{flat-design,png,right} @@ -211,9 +211,9 @@ actieve gebruikersgroep die antwoorden geeft op de lilypond-user mailinglijst, terwijl het ontwikkelingsteam ervoor zorgt dat problemen snel worden opgelost. - + @subsubheading Verbeterde editors - + Verscheidene ontwikkelaars, zelf actieve gebruikers van LilyPond, hebben ook gereedschappen geschreven die speciaal bedoeld zijn om het invoeren van LilyPond-bestanden sneller @@ -228,7 +228,7 @@ vinden in @ref{Eenvoudiger bewerken}. Nog steeds niet overtuigd? Bekijk dan maar eens enkele specifieke @ref{Voorbeelden}. Heb je al besloten LilyPond -te gaan proberen, lees dan eerst over onze +te gaan proberen, lees dan eerst over onze @ref{Tekstinvoer}. @divEnd @@ -710,7 +710,7 @@ Association}'s jaarblad, legt de Franse componist en LilyPond-bijdrager Valentin Villenave uit waarom Vrije licenties, en in het bijzonder LilyPond-gegraveerde partituren, van instrumenteel belang zijn in het voor iedereen toegankelijk maken van genoteerde muziek. - + @item februari 2008 @@ -832,7 +832,7 @@ hun gegraveerde versie niet half zo gelikt is als de mijne!} @qq{Hoewel ik [LilyPond] nog niet zo goed ken, ben ik @strong{erg} onder de indruk. Ik heb het programma gebruikt om een motet van Josquin Desprez in te voeren in mensurale -notatie. Lilypond overtreft zonder twijfel en met gemak +notatie. LilyPond overtreft zonder twijfel en met gemak alle andere muzieknotatieprogramma's voor wat betreft snelheid, gebruiksgemak en schoonheid!} @divEnd @@ -843,7 +843,7 @@ snelheid, gebruiksgemak en schoonheid!} @qq{[..na de eerste orkestrepetitie] kreeg ik heel veel complimenten over de kwaliteit van de partituren. En wat -nog veel mooier is: terwijl Lilypond allerlei manieren +nog veel mooier is: terwijl LilyPond allerlei manieren biedt om te zorgen dat de partituren er nog mooier uitzien, kreeg het orkest van mij slechts de ruwe, ongewijzigde LilyPond-output.} @@ -853,10 +853,10 @@ LilyPond-output.} @subsubheading Kieren MacMillan, componist (Toronto, Canada) @qq{Dank en lof voor het ontwikkelteam voor hun fantastische werk. Ik heb nog nooit iets gezien wat maar in de buurt -komt van de output die ik bereik met Lilypond -- Ik ben er +komt van de output die ik bereik met LilyPond -- Ik ben er zeker van dat dit fantastische programma aan al mijn muziekpublicatie-wensen kan voldoen en deze zelfs zal -overtreffen. [..] hoofdzakelijk pure Lilypond output [..] +overtreffen. [..] hoofdzakelijk pure LilyPond output [..] ziet er beter uit dan de meeste recente @q{professionele} uitgaven waarmee ik het heb vergeleken (q.v., zo ongeveer elke Warner Bros. partituur, en zelfs een groot deel van de @@ -902,7 +902,7 @@ enigszins in de buurt kan komen.} @divClass{testimonial-item} @subsubheading David Bobroff, bastrombonist, Iceland Symphony Orchestra -@qq{Ik vind Lilypond fantastisch [..] Hoe beter ik het +@qq{Ik vind LilyPond fantastisch [..] Hoe beter ik het programma leer kennen, hoe mooier ik het vind!} @divEnd @@ -1128,7 +1128,7 @@ zie @ref{Eenvoudiger bewerken}. @subheading En nu? Je bent nu zover om @ref{Download, LilyPond te downloaden}. -Nog steeds niet overtuigd? +Nog steeds niet overtuigd? Lees over @ref{Eenvoudiger bewerken}. @divEnd @@ -1360,7 +1360,7 @@ constraint-gebaseerde programmeertaal. LilyKDE3 voor KDE 3.5 en lilypond-KDE4 voor KDE 4.1. @item -@uref{https://sourceforge.net/projects/noteedit.berlios/,NoteEdit}, dat +@uref{https://sourceforge.net/projects/noteedit.berlios/,NoteEdit}, dat @uref{http://www.musicxml.com/xml.html,MusicXML} importeerde, is geforkt in @uref{http://vsr.informatik.tu-chemnitz.de/staff/jan/nted/nted.xhtml,NtEd} @@ -1393,7 +1393,7 @@ beschreven in @ref{Achtergrond}. @subheading Legalese -@divClass{legal} +@divClass{legal} All logos and product images are copyright and trademark acknowledged. diff --git a/Documentation/notation/changing-defaults.itely b/Documentation/notation/changing-defaults.itely index d213342754..c8f9ebc510 100644 --- a/Documentation/notation/changing-defaults.itely +++ b/Documentation/notation/changing-defaults.itely @@ -4546,7 +4546,7 @@ layout. Settings chosen for @code{\alterBroken} may be unsuitable for a spanner that is no longer broken or is split into more segments than before. Explicit use of @code{\break} can guard against this situation. - + The @code{\alterBroken} command is ineffective for spanner properties accessed before line-breaking such as @code{direction}. @@ -4712,7 +4712,7 @@ must return @code{#t}. @item @code{@var{@dots{}music@dots{}}} @tab normal LilyPond input, using @code{$} (in places where only -Lilypond constructs are allowed) or @code{#} (to use it as a Scheme +LilyPond constructs are allowed) or @code{#} (to use it as a Scheme value or music function argument or music inside of music lists) to reference arguments (eg. @samp{#arg1}). @@ -4743,7 +4743,7 @@ are also allowed. Notation Reference: @ref{Predefined type predicates}. -Extending Lilypond: +Extending LilyPond: @rextend{Music functions}. Installed Files: diff --git a/Documentation/notation/fretted-strings.itely b/Documentation/notation/fretted-strings.itely index bd0dfca32d..5a7676d646 100644 --- a/Documentation/notation/fretted-strings.itely +++ b/Documentation/notation/fretted-strings.itely @@ -1825,7 +1825,7 @@ music = \relative { Another playing technique (especially used on electric guitars) is called @notation{palm mute}. The string is hereby partly muted by the -palm of the striking hand (hence the name). Lilypond supports +palm of the striking hand (hence the name). LilyPond supports the notation of palm mute-style notes by changing the note head to a triangle shape. diff --git a/Documentation/notation/input.itely b/Documentation/notation/input.itely index 0a873317d4..f131cd6012 100644 --- a/Documentation/notation/input.itely +++ b/Documentation/notation/input.itely @@ -228,7 +228,7 @@ input file, LilyPond will implicitly treat the whole file as a single \book block, see @ref{File structure}. -When producing multiple files from a single source file, Lilypond +When producing multiple files from a single source file, LilyPond ensures that none of the output files from any @code{\book} block overwrites the output file produced by a preceding @code{\book} from the same input file. @@ -273,10 +273,10 @@ will produce @funindex \bookOutputSuffix @funindex \bookOutputName -Lilypond provides facilities to allow you to control what file names +LilyPond provides facilities to allow you to control what file names are used by the various back-ends when producing output files. -In the previous section, we saw how Lilypond prevents name-clashes when +In the previous section, we saw how LilyPond prevents name-clashes when producing several outputs from a single source file. You also have the ability to specify your own suffixes for each @code{\book} block, so for example you can produce files called @@ -3629,7 +3629,7 @@ lilypond file.ly >display.txt @end example @funindex \void -Note that Lilypond does not just display the music expression, but +Note that LilyPond does not just display the music expression, but also interprets it (since @code{\displayLilyMusic} returns it in addition to displaying it). Just insert @code{\displayLilyMusic} into the existing music in order to get information about it. diff --git a/Documentation/notation/rhythms.itely b/Documentation/notation/rhythms.itely index cc282e1e16..2df6cbaee7 100644 --- a/Documentation/notation/rhythms.itely +++ b/Documentation/notation/rhythms.itely @@ -2758,7 +2758,7 @@ However, as such ticks are typically used in Gregorian chant, it is preferable to use @code{\divisioMinima} there instead, described in the section @ref{Divisiones} in Gregorian chant. -Lilypond supports kievan notation and provides a special kievan +LilyPond supports kievan notation and provides a special kievan bar line: @lilypond[quote,fragment,verbatim] f'1 \bar "k" diff --git a/Documentation/po/ca.po b/Documentation/po/ca.po index 034a146cb4..ff8e942dc9 100644 --- a/Documentation/po/ca.po +++ b/Documentation/po/ca.po @@ -532,7 +532,7 @@ msgstr "Interfícies per a programadors" #. @node in Documentation/extending/programming-interface.itely #. @section in Documentation/extending/programming-interface.itely -msgid "Lilypond code blocks" +msgid "LilyPond code blocks" msgstr "Blocs de codi del LilyPond" #. @node in Documentation/extending/programming-interface.itely @@ -6480,7 +6480,7 @@ msgstr "Inserció de la sortida del LilyPond dins d'altres programes" #. @node in Documentation/usage/external.itely #. @unnumberedsubsec in Documentation/usage/external.itely msgid "Inserting LilyPond output into other programs" -msgstr "Inserció de la sortida del Lilypond dins d'altres programes" +msgstr "Inserció de la sortida del LilyPond dins d'altres programes" #. @node in Documentation/usage/external.itely msgid "Independent includes" @@ -11343,7 +11343,7 @@ msgstr "estigui al domini públic i pugui formar part, usar-se i presentar-se di #. Documentation/snippets/unfretted-headword.ly:37 (comment) msgid "the LilyPond Documention Project." -msgstr "Projecte de Documentació del Lilypond." +msgstr "Projecte de Documentació del LilyPond." #. Documentation/snippets/unfretted-headword.ly:39 (comment) msgid "Statement Date: Octber the 9th, 2008" diff --git a/Documentation/po/cs.po b/Documentation/po/cs.po index 466ac3afaa..50d0b4c65d 100644 --- a/Documentation/po/cs.po +++ b/Documentation/po/cs.po @@ -528,7 +528,7 @@ msgstr "Rozhraní pro programátory" #. @node in Documentation/extending/programming-interface.itely #. @section in Documentation/extending/programming-interface.itely #, fuzzy -msgid "Lilypond code blocks" +msgid "LilyPond code blocks" msgstr "Složené proměnné v LilyPondu" #. @node in Documentation/extending/programming-interface.itely diff --git a/Documentation/po/de.po b/Documentation/po/de.po index 9d2033aa3a..ae9c105c7e 100644 --- a/Documentation/po/de.po +++ b/Documentation/po/de.po @@ -523,7 +523,7 @@ msgstr "Schnittstellen für Programmierer" #. @node in Documentation/extending/programming-interface.itely #. @section in Documentation/extending/programming-interface.itely #, fuzzy -msgid "Lilypond code blocks" +msgid "LilyPond code blocks" msgstr "Zusammengesetzte LilyPond-Variablen" #. @node in Documentation/extending/programming-interface.itely diff --git a/Documentation/po/es.po b/Documentation/po/es.po index ccde9e84a3..1bd8ddb3f7 100644 --- a/Documentation/po/es.po +++ b/Documentation/po/es.po @@ -536,7 +536,7 @@ msgstr "Interfaces para programadores" #. @node in Documentation/extending/programming-interface.itely #. @section in Documentation/extending/programming-interface.itely -msgid "Lilypond code blocks" +msgid "LilyPond code blocks" msgstr "Bloques de código de LilyPond" #. @node in Documentation/extending/programming-interface.itely diff --git a/Documentation/po/fr.po b/Documentation/po/fr.po index 5553c33154..dcc94ff474 100644 --- a/Documentation/po/fr.po +++ b/Documentation/po/fr.po @@ -514,7 +514,7 @@ msgstr "Interfaces pour programmeurs" #. @node in Documentation/extending/programming-interface.itely #. @section in Documentation/extending/programming-interface.itely -msgid "Lilypond code blocks" +msgid "LilyPond code blocks" msgstr "Blocs de code lilyPond" #. @node in Documentation/extending/programming-interface.itely diff --git a/Documentation/po/hu.po b/Documentation/po/hu.po index abfdfb7078..ddddf92454 100644 --- a/Documentation/po/hu.po +++ b/Documentation/po/hu.po @@ -537,7 +537,7 @@ msgstr "" #. @node in Documentation/extending/programming-interface.itely #. @section in Documentation/extending/programming-interface.itely #, fuzzy -msgid "Lilypond code blocks" +msgid "LilyPond code blocks" msgstr "lilypond-book sablonok" #. @node in Documentation/extending/programming-interface.itely diff --git a/Documentation/po/it.po b/Documentation/po/it.po index 710e4b35a1..1fbf062985 100644 --- a/Documentation/po/it.po +++ b/Documentation/po/it.po @@ -519,7 +519,7 @@ msgstr "" #. @node in Documentation/extending/programming-interface.itely #. @section in Documentation/extending/programming-interface.itely -msgid "Lilypond code blocks" +msgid "LilyPond code blocks" msgstr "" #. @node in Documentation/extending/programming-interface.itely diff --git a/Documentation/po/ja.po b/Documentation/po/ja.po index 76ffe4467f..588306bcdb 100644 --- a/Documentation/po/ja.po +++ b/Documentation/po/ja.po @@ -558,7 +558,7 @@ msgstr "" #. @node in Documentation/extending/programming-interface.itely #. @section in Documentation/extending/programming-interface.itely #, fuzzy -msgid "Lilypond code blocks" +msgid "LilyPond code blocks" msgstr "環境変数" #. @node in Documentation/extending/programming-interface.itely diff --git a/Documentation/po/nl.po b/Documentation/po/nl.po index 0ce4b27c82..ae8d4bb1a8 100644 --- a/Documentation/po/nl.po +++ b/Documentation/po/nl.po @@ -518,7 +518,7 @@ msgstr "" #. @node in Documentation/extending/programming-interface.itely #. @section in Documentation/extending/programming-interface.itely -msgid "Lilypond code blocks" +msgid "LilyPond code blocks" msgstr "" #. @node in Documentation/extending/programming-interface.itely diff --git a/Documentation/po/zh.po b/Documentation/po/zh.po index aaa66c2b1c..1da3bcfe81 100644 --- a/Documentation/po/zh.po +++ b/Documentation/po/zh.po @@ -515,7 +515,7 @@ msgstr "面向程序员的界面" #. @node in Documentation/extending/programming-interface.itely #. @section in Documentation/extending/programming-interface.itely -msgid "Lilypond code blocks" +msgid "LilyPond code blocks" msgstr "LilyPond 代码块" #. @node in Documentation/extending/programming-interface.itely diff --git a/Documentation/usage/suggestions.itely b/Documentation/usage/suggestions.itely index 56ddfe24c8..73de64e0f9 100644 --- a/Documentation/usage/suggestions.itely +++ b/Documentation/usage/suggestions.itely @@ -296,13 +296,13 @@ Another very useful debugging technique is constructing @cindex makefiles @cindex make -Pretty well all the platforms Lilypond can run on support a software +Pretty well all the platforms LilyPond can run on support a software facility called @code{make}. This software reads a special file called a @code{Makefile} that defines what files depend on what others and what commands you need to give the operating system to produce one file from another. For example the makefile would spell out how to produce @file{ballad.pdf} and @file{ballad.midi} from @file{ballad.ly} by -running Lilypond. +running LilyPond. There are times when it is a good idea to create a @code{Makefile} for your project, either for your own convenience or diff --git a/Documentation/web/introduction.itexi b/Documentation/web/introduction.itexi index 77eda53f3a..2ea2085ab9 100644 --- a/Documentation/web/introduction.itexi +++ b/Documentation/web/introduction.itexi @@ -391,7 +391,7 @@ The colors have been added for better visibility. @subheading Customized Output A short excerpt from Stockhausen's Klavierstück II to demonstrate -Lilypond's ability to provide customised output. +LilyPond's ability to provide customised output. @exampleImage{Stockhausen_Klavierstueck2} @divEnd @@ -612,8 +612,8 @@ Some highlights: version of Richard Strauss's @emph{Der Rosenkavalier} for four singers and a chamber orchestra of thirteen players. This has been commissioned by the Berlin Philharmonic Orchestra whose members will be the performers on -@uref{http://www.festspielhaus.de/veranstaltung/der-kleine-rosenkavalier-02-04-2015-1100/,April 2nd and 6th} -at the Festspielhaus, Baden-Baden, and on +@uref{http://www.festspielhaus.de/veranstaltung/der-kleine-rosenkavalier-02-04-2015-1100/,April 2nd and 6th} +at the Festspielhaus, Baden-Baden, and on @uref{http://www.berliner-philharmoniker.de/konzerte/kalender/details/21070/,April 26th} in the @emph{Philharmonie (großer Saal)}, Berlin. We are pleased to see musicians of such reputation playing from LilyPond scores -- and they are diff --git a/Documentation/web/news-front.itexi b/Documentation/web/news-front.itexi index 49cdaab35f..69d6fb2dfc 100644 --- a/Documentation/web/news-front.itexi +++ b/Documentation/web/news-front.itexi @@ -15,13 +15,13 @@ We are happy to announce the release of LilyPond 2.19.46. This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you -require a stable version of Lilypond, we recommend using the 2.18 +require a stable version of LilyPond, we recommend using the 2.18 version. @newsEnd @newsItem -@subheading Lilypond 2.18.2 released! @emph{March 23, 2014} +@subheading LilyPond 2.18.2 released! @emph{March 23, 2014} We are proud to announce the release of GNU LilyPond 2.18.2. LilyPond is a music engraving program devoted to producing the @@ -53,7 +53,7 @@ from data encoded directly in the LilyPond score. @newsItem -@subheading Lilypond 2.18.0 released! @emph{December 29, 2013} +@subheading LilyPond 2.18.0 released! @emph{December 29, 2013} We are proud to announce the release of GNU LilyPond 2.18.0. LilyPond is a music engraving program devoted to producing the diff --git a/Documentation/web/news.itexi b/Documentation/web/news.itexi index da830d3e15..dfff7af3d0 100644 --- a/Documentation/web/news.itexi +++ b/Documentation/web/news.itexi @@ -33,7 +33,7 @@ We are happy to announce the release of LilyPond 2.19.45. This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you -require a stable version of Lilypond, we recommend using the 2.18 +require a stable version of LilyPond, we recommend using the 2.18 version. @newsEnd @@ -45,7 +45,7 @@ We are happy to announce the release of LilyPond 2.19.44. This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you -require a stable version of Lilypond, we recommend using the 2.18 +require a stable version of LilyPond, we recommend using the 2.18 version. @newsEnd @@ -57,7 +57,7 @@ We are happy to announce the release of LilyPond 2.19.43. This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you -require a stable version of Lilypond, we recommend using the 2.18 +require a stable version of LilyPond, we recommend using the 2.18 version. @newsEnd @@ -69,7 +69,7 @@ We are happy to announce the release of LilyPond 2.19.42. This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you -require a stable version of Lilypond, we recommend using the 2.18 +require a stable version of LilyPond, we recommend using the 2.18 version. @newsEnd @@ -81,7 +81,7 @@ We are happy to announce the release of LilyPond 2.19.41. This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you -require a stable version of Lilypond, we recommend using the 2.18 +require a stable version of LilyPond, we recommend using the 2.18 version. @newsEnd @@ -93,7 +93,7 @@ We are happy to announce the release of LilyPond 2.19.40. This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you -require a stable version of Lilypond, we recommend using the 2.18 +require a stable version of LilyPond, we recommend using the 2.18 version. @newsEnd @@ -105,7 +105,7 @@ We are happy to announce the release of LilyPond 2.19.39. This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you -require a stable version of Lilypond, we recommend using the 2.18 +require a stable version of LilyPond, we recommend using the 2.18 version. @newsEnd @@ -117,7 +117,7 @@ We are happy to announce the release of LilyPond 2.19.38. This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you -require a stable version of Lilypond, we recommend using the 2.18 +require a stable version of LilyPond, we recommend using the 2.18 version. @newsEnd @@ -129,7 +129,7 @@ We are happy to announce the release of LilyPond 2.19.37. This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you -require a stable version of Lilypond, we recommend using the 2.18 +require a stable version of LilyPond, we recommend using the 2.18 version. @newsEnd @@ -141,7 +141,7 @@ We are happy to announce the release of LilyPond 2.19.36. This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you -require a stable version of Lilypond, we recommend using the 2.18 +require a stable version of LilyPond, we recommend using the 2.18 version. @newsEnd @@ -153,7 +153,7 @@ We are happy to announce the release of LilyPond 2.19.35. This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you -require a stable version of Lilypond, we recommend using the 2.18 +require a stable version of LilyPond, we recommend using the 2.18 version. @newsEnd @@ -165,7 +165,7 @@ We are happy to announce the release of LilyPond 2.19.34. This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you -require a stable version of Lilypond, we recommend using the 2.18 +require a stable version of LilyPond, we recommend using the 2.18 version. @newsEnd @@ -177,7 +177,7 @@ We are happy to announce the release of LilyPond 2.19.33. This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you -require a stable version of Lilypond, we recommend using the 2.18 +require a stable version of LilyPond, we recommend using the 2.18 version. @newsEnd @@ -189,7 +189,7 @@ We are happy to announce the release of LilyPond 2.19.32. This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you -require a stable version of Lilypond, we recommend using the 2.18 +require a stable version of LilyPond, we recommend using the 2.18 version. @newsEnd @@ -201,7 +201,7 @@ We are happy to announce the release of LilyPond 2.19.31. This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you -require a stable version of Lilypond, we recommend using the 2.18 +require a stable version of LilyPond, we recommend using the 2.18 version. @newsEnd @@ -213,7 +213,7 @@ We are happy to announce the release of LilyPond 2.19.30. This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you -require a stable version of Lilypond, we recommend using the 2.18 +require a stable version of LilyPond, we recommend using the 2.18 version. @newsEnd @@ -225,7 +225,7 @@ We are happy to announce the release of LilyPond 2.19.29. This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you -require a stable version of Lilypond, we recommend using the 2.18 +require a stable version of LilyPond, we recommend using the 2.18 version. @newsEnd @@ -237,7 +237,7 @@ We are happy to announce the release of LilyPond 2.19.28. This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you -require a stable version of Lilypond, we recommend using the 2.18 +require a stable version of LilyPond, we recommend using the 2.18 version. @newsEnd @@ -249,7 +249,7 @@ We are happy to announce the release of LilyPond 2.19.27. This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you -require a stable version of Lilypond, we recommend using the 2.18 +require a stable version of LilyPond, we recommend using the 2.18 version. @newsEnd @@ -261,7 +261,7 @@ We are happy to announce the release of LilyPond 2.19.26. This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you -require a stable version of Lilypond, we recommend using the 2.18 +require a stable version of LilyPond, we recommend using the 2.18 version. @newsEnd @@ -273,7 +273,7 @@ We are happy to announce the release of LilyPond 2.19.25. This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you -require a stable version of Lilypond, we recommend using the 2.18 +require a stable version of LilyPond, we recommend using the 2.18 version. @newsEnd @@ -285,7 +285,7 @@ We are happy to announce the release of LilyPond 2.19.24. This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you -require a stable version of Lilypond, we recommend using the 2.18 +require a stable version of LilyPond, we recommend using the 2.18 version. @newsEnd @@ -297,7 +297,7 @@ We are happy to announce the release of LilyPond 2.19.23. This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you -require a stable version of Lilypond, we recommend using the 2.18 +require a stable version of LilyPond, we recommend using the 2.18 version. @newsEnd @@ -309,7 +309,7 @@ We are happy to announce the release of LilyPond 2.19.22. This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you -require a stable version of Lilypond, we recommend using the 2.18 +require a stable version of LilyPond, we recommend using the 2.18 version. @newsEnd @@ -321,7 +321,7 @@ We are happy to announce the release of LilyPond 2.19.21. This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you -require a stable version of Lilypond, we recommend using the 2.18 +require a stable version of LilyPond, we recommend using the 2.18 version. @newsEnd @@ -333,7 +333,7 @@ We are happy to announce the release of LilyPond 2.19.20. This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you -require a stable version of Lilypond, we recommend using the 2.18 +require a stable version of LilyPond, we recommend using the 2.18 version. @newsEnd @@ -345,7 +345,7 @@ We are happy to announce the release of LilyPond 2.19.19. This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you -require a stable version of Lilypond, we recommend using the 2.18 +require a stable version of LilyPond, we recommend using the 2.18 version. @newsEnd @@ -357,7 +357,7 @@ We are happy to announce the release of LilyPond 2.19.18. This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you -require a stable version of Lilypond, we recommend using the 2.18 +require a stable version of LilyPond, we recommend using the 2.18 version. @newsEnd @@ -369,7 +369,7 @@ We are happy to announce the release of LilyPond 2.19.17. This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you -require a stable version of Lilypond, we recommend using the 2.18 +require a stable version of LilyPond, we recommend using the 2.18 version. @newsEnd @@ -381,7 +381,7 @@ At long last, we are very happy to announce the release of LilyPond 2.19.16. This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you -require a stable version of Lilypond, we recommend using the 2.18 +require a stable version of LilyPond, we recommend using the 2.18 version. We would like to acknowledge and thank Masamichi Hosoda for making this @@ -396,7 +396,7 @@ We are happy to announce the release of LilyPond 2.19.15. This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you -require a stable version of Lilypond, we recommend using the 2.18 +require a stable version of LilyPond, we recommend using the 2.18 version. @newsEnd @@ -408,7 +408,7 @@ We are happy to announce the release of LilyPond 2.19.14. This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you -require a stable version of Lilypond, we recommend using the 2.18 +require a stable version of LilyPond, we recommend using the 2.18 version. @newsEnd @@ -420,7 +420,7 @@ We are happy to announce the release of LilyPond 2.19.13. This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you -require a stable version of Lilypond, we recommend using the 2.18 +require a stable version of LilyPond, we recommend using the 2.18 version. @newsEnd @@ -432,7 +432,7 @@ We are happy to announce the release of LilyPond 2.19.12. This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you -require a stable version of Lilypond, we recommend using the 2.18 +require a stable version of LilyPond, we recommend using the 2.18 version. @newsEnd @@ -444,7 +444,7 @@ We are happy to announce the release of LilyPond 2.19.11. This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you -require a stable version of Lilypond, we recommend using the 2.18 +require a stable version of LilyPond, we recommend using the 2.18 version. @newsEnd @@ -456,7 +456,7 @@ We are happy to announce the release of LilyPond 2.19.10. This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you -require a stable version of Lilypond, we recommend using the 2.18 +require a stable version of LilyPond, we recommend using the 2.18 version. @newsEnd @@ -468,7 +468,7 @@ We are happy to announce the release of LilyPond 2.19.9. This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you -require a stable version of Lilypond, we recommend using the 2.18 +require a stable version of LilyPond, we recommend using the 2.18 version. @newsEnd @@ -480,7 +480,7 @@ We are happy to announce the release of LilyPond 2.19.8. This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you -require a stable version of Lilypond, we recommend using the 2.18 +require a stable version of LilyPond, we recommend using the 2.18 version. @newsEnd @@ -492,7 +492,7 @@ We are happy to announce the release of LilyPond 2.19.7. This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you -require a stable version of Lilypond, we recommend using the 2.18 +require a stable version of LilyPond, we recommend using the 2.18 version. @newsEnd @@ -504,7 +504,7 @@ We are happy to announce the release of LilyPond 2.19.6. This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you -require a stable version of Lilypond, we recommend using the 2.18 +require a stable version of LilyPond, we recommend using the 2.18 version. @newsEnd @@ -516,7 +516,7 @@ We are happy to announce the release of LilyPond 2.19.5. This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require -a stable version of Lilypond, we recommend using the 2.18 version. +a stable version of LilyPond, we recommend using the 2.18 version. @newsEnd @@ -527,7 +527,7 @@ We are happy to announce the release of LilyPond 2.19.4. This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require -a stable version of Lilypond, we recommend using the 2.18 version. +a stable version of LilyPond, we recommend using the 2.18 version. @newsEnd @@ -560,7 +560,7 @@ We are happy to announce the release of LilyPond 2.19.3. This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require -a stable version of Lilypond, we recommend using the 2.18 version. +a stable version of LilyPond, we recommend using the 2.18 version. @newsEnd @@ -585,7 +585,7 @@ We are happy to announce the release of LilyPond 2.19.2. This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require -a stable version of Lilypond, we recommend using the 2.18 version. +a stable version of LilyPond, we recommend using the 2.18 version. @newsEnd @@ -596,7 +596,7 @@ We are happy to announce the release of LilyPond 2.19.1. This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require -a stable version of Lilypond, we recommend using the 2.18 version. +a stable version of LilyPond, we recommend using the 2.18 version. @newsEnd @@ -607,7 +607,7 @@ We are happy to announce the release of LilyPond 2.19.0. This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require -a stable version of Lilypond, we recommend using the 2.18 version. +a stable version of LilyPond, we recommend using the 2.18 version. @newsEnd @@ -661,7 +661,7 @@ We are happy to announce the release of LilyPond 2.17.29. This release contains the usual number of bugfixes and enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require -a stable version of Lilypond, we recommend using the 2.16 version. +a stable version of LilyPond, we recommend using the 2.16 version. @newsEnd @@ -672,7 +672,7 @@ We are happy to announce the release of LilyPond 2.17.28. This release contains the usual number of bugfixes and enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require -a stable version of Lilypond, we recommend using the 2.16 version. +a stable version of LilyPond, we recommend using the 2.16 version. @newsEnd @@ -683,7 +683,7 @@ We are happy to announce the release of LilyPond 2.17.27. This release contains the usual number of bugfixes and enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require -a stable version of Lilypond, we recommend using the 2.16 version. +a stable version of LilyPond, we recommend using the 2.16 version. @newsEnd @@ -694,7 +694,7 @@ We are happy to announce the release of LilyPond 2.17.26. This release contains the usual number of bugfixes and enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require -a stable version of Lilypond, we recommend using the 2.16 version. +a stable version of LilyPond, we recommend using the 2.16 version. @newsEnd @@ -705,7 +705,7 @@ We are happy to announce the release of LilyPond 2.17.25. This release contains the usual number of bugfixes and enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require -a stable version of Lilypond, we recommend using the 2.16 version. +a stable version of LilyPond, we recommend using the 2.16 version. @newsEnd @@ -716,7 +716,7 @@ We are happy to announce the release of LilyPond 2.17.24. This release contains the usual number of bugfixes and enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require -a stable version of Lilypond, we recommend using the 2.16 version. +a stable version of LilyPond, we recommend using the 2.16 version. @newsEnd @@ -727,7 +727,7 @@ We are happy to announce the release of LilyPond 2.17.23. This release contains the usual number of bugfixes and enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require -a stable version of Lilypond, we recommend using the 2.16 version. +a stable version of LilyPond, we recommend using the 2.16 version. @newsEnd @@ -738,7 +738,7 @@ We are happy to announce the release of LilyPond 2.17.22. This release contains the usual number of bugfixes and enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require -a stable version of Lilypond, we recommend using the 2.16 version. +a stable version of LilyPond, we recommend using the 2.16 version. This update cures the issue with the Windows version crashing with a problem with positioning text. @@ -752,7 +752,7 @@ We are happy to announce the release of LilyPond 2.17.21. This release contains the usual number of bugfixes and enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require -a stable version of Lilypond, we recommend using the 2.16 version. +a stable version of LilyPond, we recommend using the 2.16 version. @newsEnd @@ -763,7 +763,7 @@ We are happy to announce the release of LilyPond 2.17.20. This release contains the usual number of bugfixes and enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require -a stable version of Lilypond, we recommend using the 2.16 version. +a stable version of LilyPond, we recommend using the 2.16 version. @newsEnd @@ -782,7 +782,7 @@ We are happy to announce the release of LilyPond 2.17.19. This release contains the usual number of bugfixes and enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require -a stable version of Lilypond, we recommend using the 2.16 version. +a stable version of LilyPond, we recommend using the 2.16 version. @newsEnd @@ -793,7 +793,7 @@ We are happy to announce the release of LilyPond 2.17.18. This release contains the usual number of bugfixes and enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require -a stable version of Lilypond, we recommend using the 2.16 version. +a stable version of LilyPond, we recommend using the 2.16 version. @newsEnd @@ -804,7 +804,7 @@ We are happy to announce the release of LilyPond 2.17.17. This release contains the usual number of bugfixes and enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require -a stable version of Lilypond, we recommend using the 2.16 version. +a stable version of LilyPond, we recommend using the 2.16 version. @newsEnd @@ -815,7 +815,7 @@ We are happy to announce the release of LilyPond 2.17.16. This release contains the usual number of bugfixes and enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require -a stable version of Lilypond, we recommend using the 2.16 version. +a stable version of LilyPond, we recommend using the 2.16 version. @newsEnd @@ -826,7 +826,7 @@ We are happy to announce the release of LilyPond 2.17.15. This release contains the usual number of bugfixes and enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require -a stable version of Lilypond, we recommend using the 2.16 version. +a stable version of LilyPond, we recommend using the 2.16 version. @newsEnd @@ -838,7 +838,7 @@ release contains the usual number of bugfixes (including putting span bars back where they should be) and enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require -a stable version of Lilypond, we recommend using the 2.16 version. +a stable version of LilyPond, we recommend using the 2.16 version. @newsEnd @@ -849,7 +849,7 @@ We are happy to announce the release of LilyPond 2.17.13. This release contains the usual number of bugfixes and enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require -a stable version of Lilypond, we recommend using the 2.16 version. +a stable version of LilyPond, we recommend using the 2.16 version. @newsEnd @@ -860,7 +860,7 @@ We are happy to announce the release of LilyPond 2.17.12. This release contains the usual number of bugfixes and enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require -a stable version of Lilypond, we recommend using the 2.16 version. +a stable version of LilyPond, we recommend using the 2.16 version. @newsEnd @@ -871,7 +871,7 @@ We are happy to announce the release of LilyPond 2.17.11. This release contains the usual number of bugfixes and enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require -a stable version of Lilypond, we recommend using the 2.16 version. +a stable version of LilyPond, we recommend using the 2.16 version. @newsEnd @@ -882,7 +882,7 @@ We are happy to announce the release of LilyPond 2.17.10. This release contains the usual number of bugfixes and enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require -a stable version of Lilypond, we recommend using the 2.16 version. +a stable version of LilyPond, we recommend using the 2.16 version. @newsEnd @@ -902,7 +902,7 @@ We are happy to announce the release of LilyPond 2.17.9. This release contains the usual number of bugfixes and enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require -a stable version of Lilypond, we recommend using the 2.16 version. +a stable version of LilyPond, we recommend using the 2.16 version. @newsEnd @@ -913,7 +913,7 @@ We are happy to announce the release of LilyPond 2.17.8. This release contains the usual number of bugfixes and enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require -a stable version of Lilypond, we recommend using the 2.16 version. +a stable version of LilyPond, we recommend using the 2.16 version. @newsEnd @@ -924,7 +924,7 @@ We are happy to announce the release of LilyPond 2.17.7. This release contains the usual number of bugfixes and enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require -a stable version of Lilypond, we recommend using the 2.16 version. +a stable version of LilyPond, we recommend using the 2.16 version. @newsEnd @@ -968,7 +968,7 @@ We are happy to announce the release of LilyPond 2.17.6. This release contains the usual number of bugfixes and enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require -a stable version of Lilypond, we recommend using the 2.16 version. +a stable version of LilyPond, we recommend using the 2.16 version. @newsEnd @@ -979,7 +979,7 @@ We are happy to announce the release of LilyPond 2.17.5. This release contains the usual number of bugfixes and enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require -a stable version of Lilypond, we recommend using the 2.16 version. +a stable version of LilyPond, we recommend using the 2.16 version. @newsEnd @@ -1035,7 +1035,7 @@ and instead use the stable 2.16 version. @newsEnd @newsItem -@subheading Lilypond 2.16.0 released! @emph{August 24, 2012} +@subheading LilyPond 2.16.0 released! @emph{August 24, 2012} We are proud to announce the release of GNU LilyPond 2.16.0. LilyPond is a music engraving program, devoted to producing the @@ -1098,7 +1098,7 @@ Jean-Charles Malahieude, Till Paala, Yoshiki Sawada @newsEnd @newsItem -@subheading Lilypond 2.15.95 released! @emph{August 11, 2012} +@subheading LilyPond 2.15.95 released! @emph{August 11, 2012} We are excited to announce the release of LilyPond 2.15.95. With this release, development on version 2.15 is frozen for the |