Hi Mike,

Adding Unicode support to Finale 2012 has, uh, "complicated" the use of Bill 
Duncan's fonts, which have always been a bit buggy from a font-encoding 
perspective.

First, quit Finale, then make sure all the Duncan fonts are listed in the 
MacSymbolFonts.txt document -- located at ~/Library/Application 
Support/MakeMusic/Finale 2012/Configuration Files. (If you're on Lion or 
Mountain Lion, the user Library folder is hidden -- you'll need to hold down 
the option key while invoking the "Go" menu to access your Library.)

After relaunching Finale, this should fix the problem with the suffix not 
displaying, even if it's already in your library -- or you should be able to 
create a new suffix from scratch.

You still won't be able to use "Type Into Score" anymore for most Duncan 
suffixes, that is completely broken using this font in Finale 2012. You'll have 
to use the colon-followed-by-chord-ID method.

I'd hoped that switching to the new OTF versions from NPC Imaging would fix 
these issues with the Bill Duncan fonts once and for all. Unfortunately, the 
NPC versions of the chord fonts are actually even worse, with many glyphs not 
displaying at all in Finale 2012. 

It would be great if these fonts could be fixed at some point, but I'm not sure 
whether demand for these fonts (only available as part of the Finale 
Productivity bundle) warrants the expense of sorting all these issues out once 
and for all.

Cheers,

- DJA
-----
WEB: http://www.secretsocietymusic.org

On Dec 17, 2012, at 12:02 PM, Mike Casteel <[email protected]> wrote:

> Hello all,
> 
> I have encountered a problem with Bill Duncan's ChordSuf font- namely the 
> (addX) suffix (it is not recognized, even if it is already in my library when 
> "typing into score"). I can create it easily if I enter it manually (in the 
> chord definition dialog box) but if I "type into score" it will not work. Nor 
> will it work if I create the suffix from scratch in the chord suffix editor 
> window. In each of those cases, I get unwanted characters. I suppose this has 
> something to do with Finale's Unicode font support?
> 
> Has anyone encountered this specific problem and is there a way around it?
> 
> Many thanks!
> Mike Casteel
> _______________________________________________
> Finale mailing list
> [email protected]
> http://lists.shsu.edu/mailman/listinfo/finale


_______________________________________________
Finale mailing list
[email protected]
http://lists.shsu.edu/mailman/listinfo/finale

Reply via email to