Re: Style for Editorial Rests
Gabriel Ellsworth <[email protected]> Mon, 22 Jun 2026 13:08:13 -0400
| Newsgroups | gmane.comp.gnu.lilypond.general |
|---|---|
| Message-ID | <CAHavgtV_xLyNrv+LmEkQOc-s1PE1h1WH7pc1wrgXXG+k+-jdOg@mail.gmail.com> |
I asked this question in May:
On Thu, 7 May 2026, Gabriel Ellsworth wrote:
> What are best practices for indicating which rests in a LilyPond score
> are editorial?
>
For the full message:
https://lists.gnu.org/archive/html/lilypond-user/2026-05/threads.html#00080
I think I have just figured out a possible “best” answer to my own question:
*a comma over rests that represent editorial early releases*.
I think that the following is a better solution than any of the four
approaches that I had proposed in my previous message.
I welcome thoughts if you have any!
Gabriel
[image: image.png]
%%% SNIPPET BEGINS
\version "2.27.1"
\markup \override #'(line-width . 53) \wordwrap {
In this score,
if the rest is an editorial
early release, a comma is printed
over the rest glyph:
}
\fixed c' {
* % If the original source had a whole note % (the quarter rest is an
editorial % early release):*
d2.
r4-\tweak TextScript.self-alignment-X #CENTER
% (the default is #LEFT or #-1)
-\tweak TextScript.parent-alignment-X #CENTER
% (the default is #LEFT or #-1)
* ^\markup { \musicglyph "comma" }* |
* % If the original source has the rest, % then do *not* print a comma:*
b2. r4 |
}
%%% SNIPPET ENDS
image.png
(image/png, 52.2 KB) - not displayed