My thoughts about using "R" for rests.

[GoodClover]

Personally I dislike the use of R for rests as it blends in with the other capital letters used for notes, making it hard to see the basic structure of the music as it all blurs together.

From a computers perspective it's fine, they couldn't care less what character it is, but to a human letters are grouped together in the brain.

I suggest either using a lowercase letter r or preferably some other, more distinct, character.

Here are my thoughts on some alternatives:

• ; (A B bB .+; #C)
  • ➕ Just feels like a rest-y symbol.
  • ➕ Distinct / wouldn't blend in with other symbols.
  • ➖ Looks like a separator or the end of something (as is used in programming).
  • ➖ In a non-monospaced font it's alot thinner than the other characters.
• * (A B bB .+* #C)
  • ➕ Just feels like a rest-y symbol.
  • ➕ Distinct / wouldn't blend in with other symbols.
  • ➖ Looks like another "note modifier"(+,-,#)
  • ➖ In a non-monospaced font it's alot thinner than the other characters.
• = (A B bB .+= #C)
  • ➕ Just feels like a rest-y symbol.
  • ➕ Distinct / wouldn't blend in with other symbols.
  • ➕ Not really mistakable as something else.
  • ➕ In a non-monospaced font it fits well.

Alot of other things like @, >, &, feel like they have other purposes to me.

This is all just my personal opinion

*Edit: change from tick boxes to ➕/➖as GitHub does task managing things with tick boxes now...*

[GoodClover]

Re-reading this alot of my +/- points are a bit random, but you should get the gist.

[PelleJuul]

Thanks a lot for your thoughts! I originally used R because it was the most obvious glyph to use. Also, r is used for rests in LilyPond.

However, I do agree that R blends too much with the note characters, so I'll consider changing it to =.