David Fenton wrote:
> Matthew Hindson Fastmail Account wrote:
>> It's
>> Makemusic's fault that the Opus font doesn't work anyway, as they
>> limited which properties of fonts may be used in Finale (OS X).
>
>
> Care to elaborate on *that* accusation? I promise I won't tell
> Sibelius.
Well, I'll just quote a passage from the Fonts.pdf file in the Finale
2005 Help files, pp.37-38. On the one hand it's great they support
Unicode I suppose, but all I know is that the Opus font worked fine
before Finale 2004 OS X.
And please note that I'm not telling anyone how to do anything - just
reproducing information from the Mac Finale help files. If you can
understand all of this font jargon it's not like you'd need my help anyway.
Developing Fonts for Finale 2005 29-37...
Why do I need to change my fonts?
The main reason that the Macintosh fonts used by Finale need to change
is that Finale has adopted Apple's Type Services for Unicode Imaging
(ATSUI) for rendering text (more information on ATSUI is available at
http://developer.apple.com/intl/atsui.html ). Since ATSUI is capable of
rendering text using Unicode, rather than the older Macintosh script and
language information, information within the old fonts that was
previously ignored is now read by ATSUI. The old music fonts, containing
inaccuracies that had no ill effects when used with Finale 2003, may not
render correctly when used with the Carbon version of Finale. The most
common symptom of this is that music characters would be rendered in a
non-music font. Specifically, older music fonts shipped with Finale had
(in many cases) character mapping tables (CMAPs) which specified the
music characters in the Unicode Private Use range (UE000 - UF800). This
range should be handled as application-specific font encoding data, and
should cause no problems, but when this character encoding is present in
a Macintosh font, it overrides other encodings present in the font (that
is, it takes precedence over them), which means that characters may not
render correctly when called out by another encoding. Other music fonts
that were modeled after Finale's fonts may contain the same inaccuracies.
The short explanation is that the additional CMAP made the music
characters that are currently mapped in the range of 129-254 not render
correctly with ATSUI unless those characters were explicitly referenced
with the values in the Private Use range. This would be fine if the
fonts had only been used in Finale documents, but the fonts have also
been used in documents created by other applications, so we needed to
create fonts that would allow users to continue to view, edit and print
those documents.
Our solution was to build fonts which only contain the standard MacRoman
encoding, and which preserve the character mappings used in the older
versions of our fonts.
What font formats should I build? Based on our experience, the best and
simplest solution is to build Macintosh TrueType fonts, contained within
font suitcases. This font suitcase can also contain the bitmap sizes
needed so ATM can render Type 1 fonts correctly, and can be supplemented
by Adobe Type 1 format fonts for use with ATM and PostScript printers on
Mac OS 9. This combination of fonts works well for both Mac OS 9 and Mac
OS X.
[snip about Opentype fonts]
What changes do I have to make to my fonts?
If you are currently developing fonts that consist of bitmap fonts with
Adobe Type 1 printer fonts, you should rebuild your font to include a
Macintosh TrueType font within the font suitcase. If you are already
shipping Macintosh TrueType fonts, all you need to do is delete any
character mapping tables (CMAPs) other than the default MacRoman table
from the font, and make sure that all characters are mapped correctly
within this table.
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.338 / Virus Database: 267.9.7/60 - Release Date: 28/07/2005
_______________________________________________
Finale mailing list
[email protected]
http://lists.shsu.edu/mailman/listinfo/finale
