Skip to content

Fixed: Fermata encoding#205

Open
ahankinson wants to merge 2 commits into
mainfrom
fixed-202-fermatas-on-rests
Open

Fixed: Fermata encoding#205
ahankinson wants to merge 2 commits into
mainfrom
fixed-202-fermatas-on-rests

Conversation

@ahankinson
Copy link
Copy Markdown
Contributor

Clarifies that fermatas are available on rests and measure rests Re-works the fermata section to point to how to encode them on notes, rests, and chords.

Fixed #202

Clarifies that fermatas are available on rests and measure rests
Re-works the fermata section to point to how to encode them on notes, rests, and chords.

Fixed #202
@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 28, 2026

PR Preview Action v1.6.3

🚀 View preview at
https://rism-digital.github.io/pae-code-spec/pr-preview/pr-205/

Built to branch gh-pages at 2026-05-28 08:40 UTC.
Preview will be ready when the GitHub Pages deployment is complete.

Comment thread v2/index.html Outdated
@ahankinson ahankinson added the Type: Spec Clarification Clarifications to existing content in the spec label May 28, 2026
Comment thread v2/index.html
The lower-case character <code>p</code> is used to indicate a fermata.
</p>
<p>
For notes, the <code>p</code> MUST immediately follow the note name; however, If there is also
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of "; however, if there is also" It would sound better to say in a single sentence "unless there is also (...) in which case"

Comment thread v2/index.html
Comment on lines +2063 to +2070
a <a href="#trills">trill</a>, the <code>p</code> MUST follow the trill character.
</p>
<p>
For rests, see the <a href="#single-rests">single rests</a> section for how fermatas are encoded.
For multi-measure rests, see the <a href="#measure-rests">measure rests</a> section for details.
</p>
<p>
For chords, see the <a href="#chords">chords</a> section for how fermatas are encoded.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is all quite clumsy -- perhaps better pull it together into a single sentence? I mean something ike this: "For the use of fermatas on rests, multi-measure rests, and chords, see the sections on single rests, measure rests, and chords, respectively."

Comment thread v2/index.html
</p>
<p>
A <a href="#fermatas">fermata</a> for a measure rest MAY be supplied. If provided, the <code>p</code>
MUST immediately follow the <code>=</code>, or, if given, MUST immediately follow the number of
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Alternatively: "or, if the number of bars is specified, MUST immediately follow this number."

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Type: Spec Clarification Clarifications to existing content in the spec

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Fermata on rest and measure rest

3 participants