NOTATIO

Hi. I have purchased Glyphs Mini to be able to adjust some of fonts for my need.
When I edited Maestro, and saved it as another font, I get many symbols messed up, so instead of -notehead I get fff

Anyone using Glyphs Mini, and how to adjust fonts to be compatible with Finale? Does OTF work?
I have to send my edited font to my copyist, and he uses Windows (I use OS X Yosemite). I guess there will be some discrepancy?

It is very strange.
Here is a screenshot from Glyphs, clearly the notehead is œ, unicode 0153: In Finale the normal Maestro shows as well œ symbol at place 207: But when I change to my edited Maestro the œ symbol remains the same notehead, but the symbols get to fff, choosing letter Ï: So my question: why does Finale choose "slot" but not the symbol? And WHAT is the slot in Finale? Why it is not as simple as "letter œ means the black notehead" instead?

I think this is a fabulous reason for the SMuFL. Lots of people bash it, but it would be awfully nice to have some agreement on the font glyph locations and areas.

DatOrganistTho wrote:Lots of people bash it,

Really? On what grounds?
I completely agree with your assessment, though.

i suggest fontlab to edit or create the fonts, and dont forget to set Symbol for the Encoding and Unicode

odod wrote:i suggest fontlab to edit or create the fonts, and dont forget to set Symbol for the Encoding and Unicode

The price of FontLab is $649, while Glyphs Mini is available for only 44.99 €. If the functionality of Glyphs Mini covers your needs, FontLab is both bloated and very expensive.

Symbol encoding is only relevant on Windows, while OCTO is a Mac user.

That said, this does indeed seems to be an issue with the selected encoding. Basically, the slots in Finale represent a way to index the font, and as such, the order and number of symbols will depend on the codepage(s) supported. To replicate the Maestro indexing on a mac, you'll need to make sure to select codepage 1252 Latin 1 only. I can't speak to where or how to do this in Glyphs, unfortunately. The chosen font format is nevertheless irrelevant.

Ahh forgot that octo uses mac .. But, eveyone has their own preference .. Anyway i followed wesselin's and other members guide about making music font on other forum, for mac ocot needs to set MACOS ROMAN Encoding and generate as suit format not ttf (works for me on mac).. Sorry if the comment was useless


Sent from my iPhone using Tapatalk

Thanks Knut.
I purchased Glyphs Mini in hope to easily create symbols for my needs. It seems I wasted money since there are no settings for such things.
I used FontForge but now it is very unstable, takes time to load and so on.
Back to the subject I now wonder why does Finale look at position 207 but not at the code name?

Also, when I open Maestro in FF many symbols are duplicated. How that can be possible?

OCTO wrote:Thanks Knut.
I purchased Glyphs Mini in hope to easily create symbols for my needs. It seems I wasted money since there are no settings for such things.

Really? That sounds very unlikely. Are you sure you've checked every nuke and cranny?

Back to the subject I now wonder why does Finale look at position 207 but not at the code name?

I think this has to do with Finale's very limited support for Unicode. There still is no added control over extended unicode ranges with this implementation, and such fonts still can't be selected as the default music font. Basically, this has strictly been a back-end change with no adds or changes to the UI. As such, Finale's own indexing of fonts still is a reflection of the program pre Unicode.

Also, when I open Maestro in FF many symbols are duplicated. How that can be possible?

I have no idea, unfortunately. Theoretically, I guess this could happen if multiple code points where selected for certain symbols in the original font file, but Maestro has none of those, at least not in the PostScript file (which is the only one I have installed).

Knut wrote:

OCTO wrote:Also, when I open Maestro in FF many symbols are duplicated. How that can be possible?

I have no idea, unfortunately. Theoretically, I guess this could happen if multiple code points where selected for certain symbols in the original font file, but Maestro has none of those, at least not in the PostScript file (which is the only one I have installed).

I just opened Maestro.ttf (MAC encoding) with FF (v.20150824 and v.20160407) and I can confirm to not see any duplicate glyphs either. So, not sure what is causing you to see duplicates. Here's what I see:
For some reason, the fonts that come with Sibelius DO show duplicates:
I'm not sure why Sibelius requires the alternate code points, but I've noticed that if I remove the alternate encodings, then Sibelius can't see the glyphs. I haven't tried the other way around yet.