I have a similar problem with sus4 suffixes. I assumed that it was because of
the special keystrokes required to create the superscript text, key
combinations I don't have reason to remember after having created the suffixes
I need. I always have to enter those suffixes by going into dialog
Hi Chuck and Mike,
While this won't solve the underlying issue you're both talking about, I
thought it would be worth mentioning another input method that can work in
these situations that doesn't require using the mouse (which you may already
know about). The drag is that is requires
Hi Doug,
I do remember I used to do it this way, but it stopped working when I forgot
that I needed to include the colon. Thanks for the reminder. This can be
quicker if you memorize the slots for complex suffixes, so I will find this
useful for things like 7#5#9 too.
Thanks again,
Chuck
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
Thanks for the tip, Doug. I will definitely be using this until we (hopefully)
find a solution.
It makes no sense to me how creating it in the chord definition dialog box
garners the desired results but in other places there seems to be this
disconnect. Nick Carter even sent me an updated
Thanks Darcy! You and Chuck were the ones I had hoped to hear from about this.
Unfortunately, it looks like we're stuck. I had already taken all of the steps
you mentioned below. I had just hoped that I had missed a step in the process.
Bummer.
Thanks again to Doug for refreshing my memory
...@shsu.edu] On Behalf Of
|Chuck Israels
|Sent: Monday, December 17, 2012 3:06 PM
|To: finale@shsu.edu
|Subject: Re: [Finale] Bill Duncan chord suffix woes
|
|Hi Doug,
|
|I do remember I used to do it this way, but it stopped working when I
forgot that I
|needed to include the colon. Thanks
