Using mscore.ttf "Emmentaler" glyphs (characters) in Windows 10
Trouble accessing all the cool glyphs (characters) I see in the SMUFL reference.
-
I downloaded and installed https://github.com/musescore/MuseScore/blob/master/fonts/mscore/mscore…
-
I downloaded and referred to http://www.smufl.org/files/smufl-1.18.pdf It has apparently thousands of glyphs. Very nice. Maybe the wrong reference?
-
I modified my registry to create a string registry value in Computer\HKEY_CURRENT_USER\Control Panel\Input Method called EnableHexNumpad with the value of 1
-
a) I found double sharp U+E263 under Standard Accidentals in the reference and tried typing "+E263" using the number pad for numbers while holding the [ALT] key. I got a dot. Something, but not what I expected.
b) I found time signature 0 (small staff) uniE080.ss01 under Recommended stylistic alternates and tried typing "+E080" using the number pad for numbers while holding the [ALT] key. I got a nice picture, but it wasn't a 0. Apparently I am accessing the wrong glyphs, and they don't even seem musical though they are coming from MScore.ttf. -
I used the Windows native Character Map program to see and use a few hundred glyphs from MScore. But I do not see all the glyphs in the SMUFL document including leger [sic] lines.
I am getting value from mscore.ttf, but not all the value I see in the SMUFL reference.
A. Do I have the wrong reference?
B. Do I have the wrong ttf font file?
C. Am I using the wrong Windows 10 entry methods?
Comments
use MScoreText.ttf instead
The Musical Font ones are not meant to get used in text
In reply to use MScoreText.ttf instead by Jojo-Schmitz
I get the same result as with MScore.ttf. Some codes create pretty pictures that are not musical. Other codes create nothing. The character map is still partial and goes from U+E003 to U+EC98 (no leger [sic] lines, no brackets, no staves, etc). The reference goes from U+E000 to U+ECB7.
In reply to I installed MScoreText.ttf I… by hawstom
MSCoreText.ttf is far less complete that BravuraText.otf, maybe that's the reason?
In reply to MSCoreText.ttf is far less… by Jojo-Schmitz
It's useful, even if it's not complete. I just wish I could use the keyboard to access it in Windows 10.