Kenneth Wolcott <kennethwolc...@gmail.com> writes:
> Hi;
>
> This is an extremely minor bug.
>
> Which version of "English" is the Lilypond documentation written in?
>
> If it is American English, then:
>
> NR: Usage of British English: "centre" instead of "center" (both 2.22.2 and
> 2.23.12)
>
> A hairpin that is terminated with \! will end at the right edge of the note
> that has the \! assigned to it. In the case where it is terminated with the
> start of another crescendo or decrescendo mark, it will end at the *centre*
> of the note that has the next \< or \> assigned to it. The next hairpin
> will then start at the right edge of the same note instead of the usual
> left edge had it been terminated with \! before. A hairpin ending on a
> downbeat will stop at the preceding bar line.
>
> There are about 50 instances of "center" and only one instance of
> "centre".
dak@lola:/usr/local/tmp/lilypond$ git grep 'tre\b' Documentation/en
Documentation/en/learning/tweaks.itely:centre line and the right end to 4.5
above, and LilyPond will
Documentation/en/music-glossary.tely:F: contre-tenor,
Documentation/en/notation/contemporary.itely: Pierre Boulez (Le Marteau
Sans Maître?)
Documentation/en/notation/expressive.itely:or @notation{decrescendo} mark, it
will end at the centre of the note
Documentation/en/notation/keyboards.itely:@cindex tre corde
Documentation/en/notation/vocal.itely:@cindex musical theatre
Documentation/en/web/introduction.itexi:@uref{https://www.opera-orchestre-montpellier.fr/,
L'Opéra National de
Documentation/en/web/introduction.itexi:@subsubheading
@uref{https://www.troff.org/whoswho.html#werner, Werner Lemberg}, Conductor at
the Theatre in Koblenz, Germany and distinguished GNU Hacker
dak@lola:/usr/local/tmp/lilypond$ git grep '[^yfYFh]\Bour\b' Documentation/en
Documentation/en/contributor/issues.itexi:I believe that this is the expected
behaviour -- please read our
Documentation/en/essay/engraving.itely:aligned in vertical columns, making the
contour of the melody disappear
Documentation/en/extending/programming-interface.itely:title, composer, etc.
It is also a way to configure the behaviour of a
Documentation/en/extending/programming-interface.itely:the value of the font
size property in order to change the behaviour.
Documentation/en/included/authors.itexi:Vincent Le Ligeour,
Documentation/en/learning/tweaks.itely:behaviour, and the following two bars
shows the effect of
Documentation/en/notation/changing-defaults.itely:to control their appearance
and behaviour, as well as special
Documentation/en/notation/changing-defaults.itely:This behaviour is controlled
by the @code{break-visibility}
Documentation/en/notation/fretted-strings.itely:possible. This behaviour can
be changed by setting @code{restrainOpenStrings}
Documentation/en/notation/input.itely:The default behaviour is to append a
version number suffix for each
Documentation/en/notation/pitches.itely:@code{\set Staff.forceClef = ##t}
changes this behaviour.
Documentation/en/notation/pitches.itely:will be smaller than normal. This
behaviour can be overridden.
Documentation/en/notation/staff.itely:This behaviour can be changed by
contracting all empty
Documentation/en/notation/world.itely:the automatic beaming behaviour and/or
use compound time signatures.
Documentation/en/usage/latex-lilypond-example.latex:correct behaviour because
it follows La\TeX{} convention that an
Documentation/en/web/introduction.itexi:@subsubheading Paul Davis, developer of
@uref{https://jackaudio.org/, JACK} and @uref{https://www.ardour.org/, Ardour}
Documentation/en/web/introduction.itexi:of LilyPond's behaviour. Please read
this manual before doubting
Ok, essentially just "behaviour".
--
David Kastrup
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
