This also removes excess spaces at line ends in the affected files.
25 files changed:
@seealso
Glossar:
@rglos{ligature}.
@seealso
Glossar:
@rglos{ligature}.
Notationsreferenz:
@ref{Weiße Mensuralligaturen},
@ref{Ligaturen der gregorianischen Quadratnotation}.
Notationsreferenz:
@ref{Weiße Mensuralligaturen},
@ref{Ligaturen der gregorianischen Quadratnotation}.
@seealso
Glossar:
@rglos{ligature}.
@seealso
Glossar:
@rglos{ligature}.
Notationreferenz:
@ref{ Ligaturen der gregorianischen Quadratnotation},
@ref{Weiße Mensuralligaturen},
Notationreferenz:
@ref{ Ligaturen der gregorianischen Quadratnotation},
@ref{Weiße Mensuralligaturen},
@c try Till Rettig
@c Add example of white noteheads:
@c In the french baroque some composers used white noteheads in slow pieces,
@c try Till Rettig
@c Add example of white noteheads:
@c In the french baroque some composers used white noteheads in slow pieces,
-@c mainly in 3/2-time. A quarter looks there like a eighth with a white
+@c mainly in 3/2-time. A quarter looks there like an eighth with a white
@c notehead. (Franz-Rudolf Kuhnen)
@c TODO Add example of this:
@c notehead. (Franz-Rudolf Kuhnen)
@c TODO Add example of this:
- note = {This paper provides a overview of the algorithm used in LIME
+ note = {This paper provides an overview of the algorithm used in LIME
for spacing individual lines. HWN},
year = {1991},
title = {Justification of Printed Music},
for spacing individual lines. HWN},
year = {1991},
title = {Justification of Printed Music},
@Book{wanske88,
annote = {I. A very thorough overview of engraving practices of various
craftsmen. It includes detailed specs of characters, dimensions
@Book{wanske88,
annote = {I. A very thorough overview of engraving practices of various
craftsmen. It includes detailed specs of characters, dimensions
-etc. II. a thorough overview of a anonymous (by now antiquated)
+etc. II. a thorough overview of an anonymous (by now antiquated)
automated system. EDV Means e(lektronischen) D(aten)v(erarbeitung),
electronic data processing HWN.},
year = {1988},
automated system. EDV Means e(lektronischen) D(aten)v(erarbeitung),
electronic data processing HWN.},
year = {1988},
@code{Voice} approprié, le graveur @code{Ligature_bracket_engraver} par
le graveur de ligature qui convient -- voir les rubriques
@ref{Ligatures mensurales} et @ref{Neumes et ligatures grégoriennes} à
@code{Voice} approprié, le graveur @code{Ligature_bracket_engraver} par
le graveur de ligature qui convient -- voir les rubriques
@ref{Ligatures mensurales} et @ref{Neumes et ligatures grégoriennes} à
@seealso
Glossaire musicologique :
@seealso
Glossaire musicologique :
de la portée. Le chiffre porté en suffixe permet alors de les
différencier. Vous pouvez forcer le positionnement du glyphe sur une
ligne, comme expliqué à la section @ref{Clefs}. Dans la colonne
de la portée. Le chiffre porté en suffixe permet alors de les
différencier. Vous pouvez forcer le positionnement du glyphe sur une
ligne, comme expliqué à la section @ref{Clefs}. Dans la colonne
-exemple, la note suivant la clé est un do médium.
+exemple, la note suivant la clé est un do médium.
Les clés d'ut de Petrucci avaient une hampe gauche différente selon
leur ligne de rattachement.
Les clés d'ut de Petrucci avaient une hampe gauche différente selon
leur ligne de rattachement.
@end lilypond
La rubrique @ref{Métrique} expose les principes généraux sur
@end lilypond
La rubrique @ref{Métrique} expose les principes généraux sur
-l'utilisation des indications de métrique.
+l'utilisation des indications de métrique.
@seealso
Glossaire musicologique :
@seealso
Glossaire musicologique :
Pour de la musique ancienne, vous disposez de plusieurs styles de tête
de note, en plus du style par défaut @code{default}. Vous pouvez
affecter à la propriété @code{style} de l'objet @code{NoteHead}
Pour de la musique ancienne, vous disposez de plusieurs styles de tête
de note, en plus du style par défaut @code{default}. Vous pouvez
affecter à la propriété @code{style} de l'objet @code{NoteHead}
-les valeurs @code{baroque}, @code{neomensural}, @code{mensural},
+les valeurs @code{baroque}, @code{neomensural}, @code{mensural},
@code{petrucci}, @code{blackpetrucci} ou @code{semipetrucci}.
Le style @code{baroque} diffère du style @code{default} par
@code{petrucci}, @code{blackpetrucci} ou @code{semipetrucci}.
Le style @code{baroque} diffère du style @code{default} par
@knownissues
L'espacement des ligatures n'est pas des meilleurs.
@knownissues
L'espacement des ligatures n'est pas des meilleurs.
@node Réédition de musique ancienne
@subsection Réédition de musique ancienne
@node Réédition de musique ancienne
@subsection Réédition de musique ancienne
@c try Till Rettig
@c Add example of white note heads:
@c In the french baroque some composers used white note heads in slow pieces,
@c try Till Rettig
@c Add example of white note heads:
@c In the french baroque some composers used white note heads in slow pieces,
-@c mainly in 3/2-time. A quarter looks there like a eighth with a white
+@c mainly in 3/2-time. A quarter looks there like an eighth with a white
@c note head. (Franz-Rudolf Kuhnen)
@c TODO Add example of this:
@c note head. (Franz-Rudolf Kuhnen)
@c TODO Add example of this:
@code{\context} block within a @code{\layout} block. Each
@code{\context} block will affect all contexts of the type specified
throughout the @code{\score} or @code{\book} block in which the
@code{\context} block within a @code{\layout} block. Each
@code{\context} block will affect all contexts of the type specified
throughout the @code{\score} or @code{\book} block in which the
-@code{\layout} block appears. Here is a example to show the format:
+@code{\layout} block appears. Here is an example to show the format:
@lilypond[verbatim,quote]
\score {
@lilypond[verbatim,quote]
\score {
correct processing. For example, errors will be generated if the
@code{stencil} property of the @code{NoteHead} object is set to
@code{#f}. If this is the case, you can instead use the
correct processing. For example, errors will be generated if the
@code{stencil} property of the @code{NoteHead} object is set to
@code{#f}. If this is the case, you can instead use the
-@code{point-stencil} function, which sets the stencil to a object
+@code{point-stencil} function, which sets the stencil to an object
with zero size:
@lilypond[quote,verbatim,relative=2]
with zero size:
@lilypond[quote,verbatim,relative=2]
handle_broken_smobs (); should conserve a little memory.
* Fixed handling of orphaned score-elements. Any element that does
handle_broken_smobs (); should conserve a little memory.
* Fixed handling of orphaned score-elements. Any element that does
-not have its Line_of_score as a ancestor in both directions, is silently
+not have its Line_of_score as an ancestor in both directions, is silently
removed from the output. This guarantees that programming errors
don't result in coredumps from Dimension_cache::common_refpoint ():
element->line_l () is always a common reference point.
removed from the output. This guarantees that programming errors
don't result in coredumps from Dimension_cache::common_refpoint ():
element->line_l () is always a common reference point.
-Indicator for a indeterminately rising pitch bend. Compare with
+Indicator for an indeterminately rising pitch bend. Compare with
@emph{glissando}, which has determinate starting and ending pitches.
@seealso
@emph{glissando}, which has determinate starting and ending pitches.
@seealso
-Indicator for a indeterminately falling pitch bend. Compare with
+Indicator for an indeterminately falling pitch bend. Compare with
@emph{glissando}, which has determinate starting and ending pitches.
@seealso
@emph{glissando}, which has determinate starting and ending pitches.
@seealso
@code{\context} block within a @code{\layout} block. Each
@code{\context} block will affect all contexts of the type specified
throughout the @code{\score} or @code{\book} block in which the
@code{\context} block within a @code{\layout} block. Each
@code{\context} block will affect all contexts of the type specified
throughout the @code{\score} or @code{\book} block in which the
-@code{\layout} block appears. Here is a example to show the format:
+@code{\layout} block appears. Here is an example to show the format:
@lilypond[verbatim,quote]
\score {
@lilypond[verbatim,quote]
\score {
correct processing. For example, errors will be generated if the
@code{stencil} property of the @code{NoteHead} object is set to
@code{#f}. If this is the case, you can instead use the
correct processing. For example, errors will be generated if the
@code{stencil} property of the @code{NoteHead} object is set to
@code{#f}. If this is the case, you can instead use the
-@code{point-stencil} function, which sets the stencil to a object
+@code{point-stencil} function, which sets the stencil to an object
with zero size:
@lilypond[quote,verbatim,relative=2]
with zero size:
@lilypond[quote,verbatim,relative=2]
@c try Till Rettig
@c Add example of white note heads:
@c In the french baroque some composers used white note heads in slow pieces,
@c try Till Rettig
@c Add example of white note heads:
@c In the french baroque some composers used white note heads in slow pieces,
-@c mainly in 3/2-time. A quarter looks there like a eighth with a white
+@c mainly in 3/2-time. A quarter looks there like an eighth with a white
@c note head. (Franz-Rudolf Kuhnen)
@c TODO Add example of this:
@c note head. (Franz-Rudolf Kuhnen)
@c TODO Add example of this:
- This is a isolated dynamic apparently, and does not even have
+ This is an isolated dynamic apparently, and does not even have
any interesting support item.
*/
Grob *cc = unsmob_grob (get_property ("currentMusicalColumn"));
any interesting support item.
*/
Grob *cc = unsmob_grob (get_property ("currentMusicalColumn"));
- The definition of a interpretation context as given in the
+ The definition of an interpretation context as given in the
input. The lists are stored in order of definition.
*/
struct Context_def
input. The lists are stored in order of definition.
*/
struct Context_def
#include "simple-music-iterator.hh"
/**
#include "simple-music-iterator.hh"
/**
- Walk through a Event_chord
+ Walk through an Event_chord
*/
class Event_chord_iterator : public Simple_music_iterator
{
*/
class Event_chord_iterator : public Simple_music_iterator
{
#include "grob-info.hh"
#include "translator.hh"
#include "grob-info.hh"
#include "translator.hh"
-/* Convert a music definition into a audio representation.
+/* Convert a music definition into an audio representation.
A baseclass. */
class Performer : public Translator
{
A baseclass. */
class Performer : public Translator
{
- Item copy ctor. Copy nothing: everything should be a elt property
+ Item copy ctor. Copy nothing: everything should be an elt property
or a special purpose pointer (such as broken_to_drul_[]) */
Item::Item (Item const &s)
: Grob (s)
or a special purpose pointer (such as broken_to_drul_[]) */
Item::Item (Item const &s)
: Grob (s)
- Should insert a adjustable space here? For excercises, you might want to
+ Should insert an adjustable space here? For exercises, you might want to
use a staff without a clef in the beginning.
*/
use a staff without a clef in the beginning.
*/
{
if (prev_prefix_set & VIRGA)
/*
{
if (prev_prefix_set & VIRGA)
/*
- * After a virga, make a an additional small space such that the
+ * After a virga, make an additional small space such that the
* appendix on the right side of the head does not touch the
* following head.
*/
* appendix on the right side of the head does not touch the
* following head.
*/
if ((context_info & FLEXA_LEFT) && ! (context_info & PES_UPPER))
/*
if ((context_info & FLEXA_LEFT) && ! (context_info & PES_UPPER))
/*
- * Before a flexa (but not within a torculus), make a an
+ * Before a flexa (but not within a torculus), make an
* additional small space such that the appendix on the left side
* of the flexa does not touch the this head.
*/
* additional small space such that the appendix on the left side
* of the flexa does not touch the this head.
*/
;; the size of the staff lines is evaluated as 0, which results in a
;; solid span bar line with faulty y coordinate.
;;
;; the size of the staff lines is evaluated as 0, which results in a
;; solid span bar line with faulty y coordinate.
;;
-;; This routine was originally by Juergen Reuter, but it was a on the
+;; This routine was originally by Juergen Reuter, but it was on the
;; bulky side. Rewritten by Han-Wen. Ported from c++ to Scheme by Marc Hohl.
(define-public (ly:span-bar::print grob)
"The print routine for span bars."
;; bulky side. Rewritten by Han-Wen. Ported from c++ to Scheme by Marc Hohl.
(define-public (ly:span-bar::print grob)
"The print routine for span bars."
"
@cindex drawing oval around text
"
@cindex drawing oval around text
-Draw a oval around @var{arg}. Use @code{thickness},
+Draw an oval around @var{arg}. Use @code{thickness},
@code{x-padding}, @code{x-padding} and @code{font-size} properties to determine
line thickness and padding around the markup.
@code{x-padding}, @code{x-padding} and @code{font-size} properties to determine
line thickness and padding around the markup.
(lambda (x) (apply music-property-description x))
`(
(absolute-octave ,integer?
(lambda (x) (apply music-property-description x))
`(
(absolute-octave ,integer?
- "The absolute octave for a octave check note.")
+ "The absolute octave for an octave check note.")
(alteration ,number? "Alteration for figured bass.")
(alternative-dir ,ly:dir? "Indicates if an AlternativeMusic is the
First (-1), Middle (0), or Last (1) of group of alternate endings.")
(alteration ,number? "Alteration for figured bass.")
(alternative-dir ,ly:dir? "Indicates if an AlternativeMusic is the
First (-1), Middle (0), or Last (1) of group of alternate endings.")
(pitch ,ly:pitch? "The pitch of this note.")
(pitch-alist ,list? "A list of pitches jointly forming the scale
of a key signature.")
(pitch ,ly:pitch? "The pitch of this note.")
(pitch-alist ,list? "A list of pitches jointly forming the scale
of a key signature.")
- (pop-first ,boolean? "Do a revert before we try to do a override
+ (pop-first ,boolean? "Do a revert before we try to do an override
on some grob property.")
(prob-property ,symbol? "The symbol of the prob property to set.")
(procedure ,procedure? "The function to run with @code{\\applycontext}.
on some grob property.")
(prob-property ,symbol? "The symbol of the prob property to set.")
(procedure ,procedure? "The function to run with @code{\\applycontext}.
- . ((description . "Create a alternative event.")
+ . ((description . "Create an alternative event.")
(types . (general-music event alternative-event))
))
(types . (general-music event alternative-event))
))
;;; Commentary:
;;; This file provides the support routines for a guile debugger called
;;; Commentary:
;;; This file provides the support routines for a guile debugger called
-;;; from a environment controlled by LilyPond. It works in conjunction
+;;; from an environment controlled by LilyPond. It works in conjunction
;;; with file guile-debugger.ly.
;;; Code:
;;; with file guile-debugger.ly.
;;; Code:
pred))
(cons type signature)))
(if (and (pair? body) (pair? (car body)) (eqv? '_i (caar body)))
pred))
(cons type signature)))
(if (and (pair? body) (pair? (car body)) (eqv? '_i (caar body)))
- ;; When the music function definition contains a i10n doc string,
+ ;; When the music function definition contains an i10n doc string,
;; (_i "doc string"), keep the literal string only
(let ((docstring (cadar body))
(body (cdr body)))
;; (_i "doc string"), keep the literal string only
(let ((docstring (cadar body))
(body (cdr body)))
(make-vcenter-markup
(format #f "~a" fret-number)))
(make-vcenter-markup
(format #f "~a" fret-number)))
-;; The 5-string banjo has got a extra string, the fifth (duh), which
+;; The 5-string banjo has got an extra string, the fifth (duh), which
;; starts at the fifth fret on the neck. Frets on the fifth string
;; are referred to relative to the other frets:
;; the "first fret" on the fifth string is really the sixth fret
;; starts at the fifth fret on the neck. Frets on the fifth string
;; are referred to relative to the other frets:
;; the "first fret" on the fifth string is really the sixth fret
projects / lilypond.git / commitdiff