We should standardize our use of unicode accidentals versus keyboard equivalents.
Why there's a problem
Questions and Answers that use the unicode sharp (♯) and flat (♭) symbols (for example) are not directly findable in search results.
I posted an answer to this question: Is there such a thing as F♯ position on the piano?
Originally, the question and answer used the keyboard # sign. Later, they were edited to use the unicode ♯ symbol.
Now if I search for "user:70803 is:answer [piano] F#", the answer does not show up in the results.
However, if I search for "user:70803 is:answer [piano] F", it does.
As best I can tell, the ♯ unicode character is ignored in searches. Searching for "user:70803 is:answer [piano] F♯" gives the same results as "user:70803 is:answer [piano] F".
This is true generally, not just for my intentionally limited search.
I propose a vote. Suggested solutions would be posted as Answers to this Question, with the top vote-getter being the solution adopted by MP&T. Discussion of solutions can happen in comments and/or chat. The voting period would initially be open-ended to allow for as much participation as possible.
I've included a few Answers, but please add others. If you want to be able to vote for your own solution, let me know in the comments or on chat, and I'll post it for you.
Related questions and issues
- Do we accept edits that simply update the characters used for accidentals?
- Improved support for displaying accidentals
- Inserting musical symbols directly into the discussion
- Suggestion: Make music symbols available to copy in to text. (♭ ♮ ♯ ♪ ♩)
UPDATE: So far, there is some support for requesting that unicode accidentals and their #/b substitutes be made equivalent in searches. Just bumping the question to see if there's any more input from the community.