Double sharp (𝄪) is unicode U+1D12A, and double flat (𝄫) is unicode U+1D12B (from here). I’ve noticed other chords use # or b sometimes instead of ♭ or ♯. Could Hookpad be changed to consistently use the correct characters throughout?
Would you like me to rewrite this as a feature request? I’m not sure how you keep track these things.
Just one complication to that. I can see advantages to having it typeable. Having to type one thing with the display being something else is rough. Not to mention that people don’t have the unicode character codes memorized.
Sometimes an approximation is easier to deal with.
Displaying the correct notation won’t necessarily affect its ability to accept typeable substitutes in the search box.
When I type bVI into the search box now, my result is ♭VI, which is useful and not what I want to have changed. Hookpad already displays the correct notation in many cases without affecting your ability to type it in.
Maybe the solution is to have a settings option and let the individual users decide which they wish to see?
You are right for experienced users. Yes, it should have been fixed with the widespread adoption of unicode. The whole idea behind their products it to bring a wider audience into music theory. For naïve users that don’t already have that knowledge it is opaque.
But that is just my opinion and you know how that goes, everybody has one.
They will make whatever decision that they think is best for their product.
hey all, the truth is that we simply haven’t given this issue a ton of thought. @neurozero thank you for the info on the unicode characters, I hadn’t realized that double flats and sharps had their own characters. Right now, we use a music font to write flats and sharps, but I’ve noticed that these do get messed up sometimes. Probably the right thing to do is to swap these all out for their unicode equivalents to make everything more consistent.