A couple of suggestions: Was Word running when you installed the font? Word
won't recognize a new font unless you quit it while you're installing the
font. Try restarting Word. If that doesn't work make sure the font got put in
your system library and restart the computer.
I'm sorry. Both of those suggestions are almost complete malarkey.
Word *does* recognise fonts which have been installed or activated
while Word is running. Most of the time - which is what justifies that
adjective in front of 'complete malarkey'.
You will find it impossible to place a user font in the
System/Library/Fonts directory.
(unless you enable the root account, do some serious geekery and pooch
your operating system) That directory is for last ditch emergency fonts
that the system might need at boot fail or kernel panic time.
There are three normal repositories for fonts, one of which is for the
terminally masochistic.
They are /Library/Fonts, for fonts intended to be available to all
users on the machine; and ~/Library/Fonts for those intended to be
private to a single user. The masochist's one is the network directory
tree if you have one. Word will happily look in those directories, and
depending on the current level of font brain-damage in your version,
only there. (There do exist version of Word that insist on vandalising
your carefully crafted and maintained font regimen, with
out-of-date-error-filled versions of its fonts with the same name, but
that is another sorry tale.)
To the original poster:-
Word and a few other Carbon applications sometime sulk and refuse to
see some fonts, usually open-type but some truetype and postscript,
more or less at random. On desultory testing I have done over many
years, it sometimes related to the number of other fonts of the same
type with names earlier in the alphabet. Warnock Pro is one of mine
that frequently goes walkabout, as does Minion Pro. Interestingly,
today it is showing 10 of the available 32 weights of Warnock - this is
another delightful idiosyncrasy of Microsoft's attitude to quality
control that blights later versions than your v.X.
No amount of cache scrubbing or other folk remedy makes the slightest
difference. As noted above, disabling fonts early in the alphabet may
help, but that gets old rather quickly.
Look at it this way. If you are using a swash font, you have long
outgrown Word's typographical ability. which continues to languish at
Ransom Note 101.
Oh, and v.X does not do Unicode. It will try to use a unicode font, but
you can bet your LATIN SMALL LETTER S WITH A SWASH TAIL to a lower case
e, that it won't be seen among v.X's miserly 250mumble glyphs per font.
