Whether that made it PageMaker's fault or not was a matter of some debate between various good folks at Aldus and Adobe.) (Adobe did release a fixed version of the font.) PageMaker was the only app we ever discovered that actually *read* this particular bit of code, so PageMaker crashed and nobody else did. I was working in Aldus Tech Support at the time, and I was the one who discovered this bad code. (There was an Adobe font* ~20 years ago that had some improper code at the very end of the FOND. But my theory is that there must be some minor weirdness in this particular font that Word is ignoring but Sibelius isn't.

Normally, of course, if MS Word is capable of handling a font properly, almost any other app in the world will also be able to handle that font properly. But Adobe Garamond and Adobe Caslon are sort of 'sister' or 'twin' fonts, in that they were the very first two 'Adobe'-named fonts and came out at about the same time.

(I don't have Adobe Garamond Pro, or I'd let you know whether it works for me, of course. Do you happen to also have Adobe Caslon Pro? That's what I have (and use), and I've never had any problems with it, with any version of Mac OSX, including 10.5.8.

Download adobe garamond pro bold