[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
8 doc edits (NR4 & NR5)
From: |
Trevor Bača |
Subject: |
8 doc edits (NR4 & NR5) |
Date: |
Tue, 17 Dec 2024 11:27:59 -0500 |
Hi,
The document attached here suggests edits to 8 examples in NR4 and NR5.
Summary (numbering continued from 36 earlier edits to NR1 & NR2):
Edits 37- 40: NR 4.3.1: Line breaking: notation examples 2, 3, 4, 5.
These four examples show different things about how *automatic*
line-breaking works (as contrasted with *manual* line-breaking
with the \break command, which is the point of notation example 1)
These four examples are good, but there is a presentational
problem:
The reason that LilyPond line-breaks where it does in these examples
is because of the line-width setting, which is not shown
in any of the four examples
Easy solution is to add a one-item \paper { } block to each example.
Edit 41: NR 4.3.1: Line breaking: notation example 6: ``Using an extra
voice for breaks''
The purpose of the example is to show how to manually line-break
the music into four separate systems.
But note that the example shows FIVE systems of music, not four.
The reason for this is that line-width is set to 160\mm.
(And this setting is not included where users can see it.)
Edit 42: NR 5.3.6: \tweak and \single: notation example 6.
This page only exists in the 2.25 version of the docs;
page does not exist in the 2.24 version of the docs
* The example clips \relative from user-visible input;
this means that the user-visible music input in the example is in the
wrong octave
Edit 43: NR 5.3.7: The \offset command
This page is NR 5.3.7 in the 2.25 version of the docs;
it is NR 5.3.6 in the 2.25 version of the docs
* All chords in the example are correct, except the last one.
The final chord in the example (root-position C-major triad)
purports to show arpeggio-lengthening done with
\once \override Arpeggio.positions = #'(-3.5 . -0.5)
But this doesn't work; the offset positions have to be
greater to lengthen the arpeggio
Edit 44: NR 5.4.6: Line spanners: notation example 2.
* The code contains \override Glissando.breakable = ##t,
which is no longer necessary when using a manual \break command
Suggested edits for these 8 examples are included in the .ly file attached
here.
This concludes the list of edits I found when reviewing all 5 chapters of
the Notation Reference.
--
Trevor Bača
www.trevorbaca.com
soundcloud.com/trevorbaca
NR4-NR5-doc-edits.ly
Description: Binary data
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- 8 doc edits (NR4 & NR5),
Trevor Bača <=