My workaround for font problems like these is to open the MIF file in Notepad++ and replace all the "Stag-Book" font tags with tags of a font which I do have, for example Myriad Pro:
<FPlatformName `W.Myriad Pro.R.400'>
<FFamily `Myriad Pro'>
<FSize 12.0 pt>
> # end of Font
> ... open the MIF file in Notepad++ and replace all the "Stag-Book" font tags ...
And if that doesn't stick, the font invocation is probably coming in from an external object.
Text insets are an obvious candidate, but this can also happen with imported graphics from file formats that support text as fonts, such as EPS, PDF, and perhaps DXF or DWG.
"...but this can also happen with imported graphics from file formats that support text as fonts, such as EPS, PDF, and perhaps DXF or DWG..."
Yeah, this can be a problem when you save the file as PDF, you won't see the font tags of those graphics in the MIF file:
<FPlatformName `W.Stag Book.R.400'>
<FFamily `Stag Book'>
Places fonts can hide include:
- Left master Pages not accessible because document is in single-sided mode.
- Table format defaults that are not part of any Table Designer menus (create a table for each format with ample rows, columns, header and footer to see what it's using).
> <PgfFont <FTag `'>
Is that really an empty font tag?
My mistake, and my apologies: what I failed to make clear was that the PC does have a font called Stag Book, which generally behaves as it should. The error message, however, mentions Stag-Book with a hyphen; which I can only find as the FPostScriptName – whatever that is.
<PgfFont <FTag `'> is just copy/paste from the .mif file, as far as I remember. I'll check.
That's just one of the quirks of the postscript font naming system. You have a PS_FullName, PS_FamilyName and PS_FontName each with length and character restrictions. It's up to each individual font creator to establish their own names for these. For Linotype fonts, here's a document that explains the house rules for the various namings (since you asked...): http://image.linotype.com/files/pdf/LN0005_V1_2.pdf